[Kea-users] Need help defining custom options

James Sumners JamesSumners at clayton.edu
Mon Jan 30 19:30:06 UTC 2017


In the old DHCPd server I have defined a couple vendor specific options like so:

# *snip*

option option-176 code 176 = string;
option option-242 code 242 = string;

# *snip*

subnet 10.10.0.0 netmask 255.255.255.0 {
  pool {
    range dynamic-bootp 10.10.0.30 10.10.0.254;
  }
  option routers 10.10.0.1;
  option subnet-mask 255.255.255.0;
  option option-176 "MCIPADD=172.24.10.143,MCPORT=1719,TFTPDIR=/phones/,TFTPSRVR=10.0.0.73,IRSTAT=0,PROCSTAT=0,L2Q=1,L2QVLAN=101";
  option option-242 "MCIPADD=172.24.10.143,MCPORT=1719,HTTPDIR=/,DOT1XSTAT=0,HTTPSRVR=10.0.0.73,IRSTAT=0,PROCSTAT=0,L2Q=1,L2QVLAN=101,VLANTEST=0";
}

# *snip*


With Kea 1.1.0, I have attempted to replicate this configuration in the following manner under “Dhcp4”:

    "option-def": [
      {
        "name": "option-242",
        "code": 242,
        "type": "string"
      },
      {
        "name": "option-176",
        "code": 176,
        "type": "string"
      }
    ],

    "option-data": [
      {"name": "domain-name-servers", "data": "10.0.0.2,10.0.0.3"}
    ],

    "subnet4": [
      {
        "id": 1,
        "subnet": "172.28.206.0/24",
        "pools": [{"pool": "172.28.206.10 - 172.28.206.254"}],
        "option-data": [
          {"name": "routers", "data": "172.28.206.254"},
          {
            "name": "option-242",
            "code": 242,
            "data": "MCIPADD=172.24.11.15,172.24.11.16,MCPORT=1719,HTTPSRVR=172.24.11.15,L2Q=1,L2QVLAN=3060 VLANTEST=0"
          },
          {
            "name": "option-176",
            "code": 176,
            "data": "MCIPADD=172.24.11.15,172.24.11.16,MCPORT=1719,TFTPSRVR=172.24.11.15,L2Q=1,L2QVLAN=3060 VLANTEST=0"
          }
        ]
      },
      {
        "id": 2,
        "subnet": "172.28.205.0/24",
        "pools": [{"pool": "172.28.205.10 - 172.28.205.254"}],
        "option-data": [
          {"name": "routers", "data": "172.28.205.1"}
        ],
        "reservations": []
      }
    ]


However, this does not seem to be sending full string to requesting clients.

Am I defining these options correctly?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170130/0cb809e0/attachment.htm>


More information about the Kea-users mailing list