Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    tcode Kea truncate after comma

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 26 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z Offline
      ZzDown
      last edited by

      I'm trying to add this:

      {
      "option-data": [
      {
      "name": "time-offset",
      "data": "3600",
      "always-send": true
      },
      {
      "name": "tcode",
      "data": "CET-1CEST,M3.5.0/2,M10.5.0/3",
      "always-send": true
      },
      {
      "name": "pcode",
      "data": "CET-1CEST,M3.5.0/2,M10.5.0/3",
      "always-send": true
      }
      ]
      }

      But Kea seems to truncate everything after the first comma in the string, so it only sends CET-1CEST for tcode and pcode. Is there a solution for this?

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @ZzDown
        last edited by

        @ZzDown said in tcode Kea truncate after comma:

        Is there a solution for this?

        Maybe this :

        Here : https://kb.isc.org/docs/standard-dhcp-options and locate :

        6429e342-d0f9-4f6a-8b59-82164a2fc48a-image.png

        Check this RFC4833 : https://datatracker.ietf.org/doc/html/rfc4833

        and you find an example (and use it ones to check if kea accepts this string) :

        EST5EDT4,M3.2.0/02:00,M11.1.0/02:00
        

        Compare with what you used :

        CET-1CEST,M3.5.0/2,M10.5.0/3
        

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        Z 1 Reply Last reply Reply Quote 0
        • Z Offline
          ZzDown @Gertjan
          last edited by

          @Gertjan Thanks for the hint! I saw that I had TCode wrong, but even with the example, PCode still gets truncated:

          {
          "option-data": [
          {
          "name": "time-offset",
          "data": "3600"
          },
          {
          "name": "tcode",
          "data": "Europe/Zurich",
          "always-send": true
          },
          {
          "code": 100,
          "data": "EST5EDT4,M3.2.0/02:00,M11.1.0/02:00"
          }
          ]
          }

          This is what Wireshark sees:

          Option: (100) PCode
              Length: 8
              TZ PCode: EST5EDT4
          Option: (101) TCode
              Length: 13
              TZ TCode: Europe/Zurich
          Option: (255) End
          
          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.