[Kea-users] Client-ID (option 61)
Juan Settecase - Interlink S.R.L.
juan at interlink.com.ar
Thu Aug 10 12:56:55 UTC 2017
Hi Duane,
I'm using Kea 1.2 and I didnt have problem provisioning CMs and CPEs on
Our DOCSIS/HFC networks. I didnt need to disable Client-ID on DHCP
Offers packets. Write me on private if you like.
Kea docs are well documented, I suggest to check it again.
I attach an simple and working example for provisioning CMs and CPES in
Kea 1.2 and dhcpdump capture (my Kea responses DHCP Client-ID -option 61-)
El 09/08/17 a las 17:57, Duane Wylie escribió:
>
> We're evaluating KEA (version 1.2.0) as our DHCP platform moving
> forward. In my testing with our Docsis/HFC network, I am not able to
> have a docsis modem respond to a DHCPOFFER message from KEA. I can
> get the same modem to respond to a similarly formatted DHCPOFFER from
> ISC DHCP.
>
>
> Looking at the tcpdump output from the server, the only difference
> that stands out is the Client-ID (option 61). While, in both cases,
> the docsis modem does supply the Client-ID in the DHCPDISCOVER packet,
> the KEA server DOES include the Client-ID in the resulting DHCPOFFER
> where the ISC DHCP server DOES NOT include the Client-ID in
> it's DHCPOFFER.
>
>
> (Interesting note: RFC 2131 (Draft Standard) states that the server
> "MUST NOT" include the Client-ID in the DHCPOFFER. At the same time,
> RFC 6842 (Proposed Standard) indicates the server MUST include the
> Client-ID IF the client provided it in the DHCPDISCOVER.)
>
>
> I need to determine why the KEA offer is not 'working'. Admittedly, I
> do not know for certain that the Client-ID is the root of my problem.
> I think the next step is to somehow prove that success or failure
> does indeed hinge on the inclusion of the Client-ID field in the
> DHCPOFFER. I'm at somewhat of an impasse, as I cannot figure out how
> to tell KEA to NOT include the option. (At the same time, I cannot
> figure out how to tell ISC DHCP to include the option - though this is
> off topic for the Kea-users list.)
>
>
> Does anyone have any insight into a configuration option to disable
> option 61? Is there a generic way to disable a certain option via the
> kea.conf file? Or, where in the code can I 'flip the switch' the turn
> option 61 off on an offer?
>
>
>
> Thanks in advance,
>
> Duane
>
>
>
>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170810/a78ee2a4/attachment.htm>
-------------- next part --------------
---------------------------------------------------------------------------
TIME: 2017-08-10 09:43:41.701
IP: 200.123.33.2 (0:c:42:9a:6e:75) > 10.10.0.2 (82:de:11:bc:9a:44)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 0ee59ebd
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 10.40.0.2
CHADDR: 00:05:ca:9d:11:60:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 60 ( 10) Vendor class identifier docsis3.0:
OPTION: 0 ( 61) pad
OPTION: 61 ( 7) Client-identifier 01:00:05:ca:9d:11:60
OPTION: 125 (141) ??? 0000118b88010102 ........
0583058101010102 ........
0103030101040101 ........
0501010601010701 ........
180801080901000a ........
01010b01180c0101 ........
0d0200400e020010 ... at ....
0f01011004000000 ........
0411010112071000 ........
05ca9d1161130101 ....a...
1401001501381601 .....8..
0117010118010419 ........
01041a01041b0128 .......(
1c01021d01041e01 ........
201f011020011821 ... ..!
0102220101230101 .."..#..
2401182501012602 $..%..&.
0040270101 .@'..
OPTION: 0 ( 43) pad
OPTION: 43 (121) Vendor specific info 020345434d030845 ..ECM..E
434d3a454d544104 CM:EMTA.
0c32353231303430 .2521040
3136373939050231 16799..1
410616322e302e30 A..2.0.0
2e31352d70726533 .15-pre3
2d4d4743502d5456 -MGCP-TV
4e0717505350552d N..PSPU-
426f6f7420312e30 Boot 1.0
2e392e31352d4832 .9.15-H2
2e33080630303035 .3..0005
434109084256472d CA..BVG-
333635330a134869 3653..Hi
74726f6e20546563 tron Tec
686e6f6c6f676965 hnologie
73 s
OPTION: 55 ( 8) Parameter Request List 1 (Subnet mask)
2 (Time offset)
3 (Routers)
4 (Time server)
7 (Log server)
54 (Server identifier)
125 (???)
122 (???)
OPTION: 82 ( 32) Relay Agent Information
Circuit-ID 54:6f:70:76:69:73:69:6f:6e
Remote-ID 00:05:ca:9d:11:60
Chaos 00:00:11:8b:06:01:04:01:02:03:00
---------------------------------------------------------------------------
TIME: 2017-08-10 09:43:41.701
IP: 10.10.0.2 (82:de:11:bc:9a:44) > 10.40.0.2 (0:c:42:9a:6e:75)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 0ee59ebd
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 10.40.0.10
SIADDR: 10.10.0.2
GIADDR: 10.40.0.2
CHADDR: 00:05:ca:9d:11:60:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: test.bin.
OPTION: 1 ( 4) Subnet mask 255.255.0.0
OPTION: 2 ( 4) Time offset -7200 ()
OPTION: 3 ( 4) Routers 10.40.0.1
OPTION: 4 ( 4) Time server 10.10.0.2
OPTION: 7 ( 4) Log server 10.10.0.2
OPTION: 51 ( 4) IP address leasetime 3600 (60m)
OPTION: 53 ( 1) DHCP message type 2 (DHCPOFFER)
OPTION: 54 ( 4) Server identifier 10.10.0.2
OPTION: 58 ( 4) T1 900 (15m)
OPTION: 59 ( 4) T2 1800 (30m)
OPTION: 61 ( 7) Client-identifier 01:00:05:ca:9d:11:60
OPTION: 82 ( 32) Relay Agent Information
Circuit-ID 54:6f:70:76:69:73:69:6f:6e
Remote-ID 00:05:ca:9d:11:60
Chaos 00:00:11:8b:06:01:04:01:02:03:00
---------------------------------------------------------------------------
TIME: 2017-08-10 09:43:41.802
IP: 200.123.33.2 (0:c:42:9a:6e:75) > 10.10.0.2 (82:de:11:bc:9a:44)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 0ee59ebd
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 10.40.0.2
CHADDR: 00:05:ca:9d:11:60:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST)
OPTION: 60 ( 10) Vendor class identifier docsis3.0:
OPTION: 0 ( 61) pad
OPTION: 61 ( 7) Client-identifier 01:00:05:ca:9d:11:60
OPTION: 125 (141) ??? 0000118b88010102 ........
0583058101010102 ........
0103030101040101 ........
0501010601010701 ........
180801080901000a ........
01010b01180c0101 ........
0d0200400e020010 ... at ....
0f01011004000000 ........
0411010112071000 ........
05ca9d1161130101 ....a...
1401001501381601 .....8..
0117010118010419 ........
01041a01041b0128 .......(
1c01021d01041e01 ........
201f011020011821 ... ..!
0102220101230101 .."..#..
2401182501012602 $..%..&.
0040270101 .@'..
OPTION: 0 ( 43) pad
OPTION: 43 (121) Vendor specific info 020345434d030845 ..ECM..E
434d3a454d544104 CM:EMTA.
0c32353231303430 .2521040
3136373939050231 16799..1
410616322e302e30 A..2.0.0
2e31352d70726533 .15-pre3
2d4d4743502d5456 -MGCP-TV
4e0717505350552d N..PSPU-
426f6f7420312e30 Boot 1.0
2e392e31352d4832 .9.15-H2
2e33080630303035 .3..0005
434109084256472d CA..BVG-
333635330a134869 3653..Hi
74726f6e20546563 tron Tec
686e6f6c6f676965 hnologie
73 s
OPTION: 50 ( 4) Request IP address 10.40.0.10
OPTION: 54 ( 4) Server identifier 10.10.0.2
OPTION: 55 ( 8) Parameter Request List 1 (Subnet mask)
2 (Time offset)
3 (Routers)
4 (Time server)
7 (Log server)
54 (Server identifier)
125 (???)
122 (???)
OPTION: 82 ( 32) Relay Agent Information
Circuit-ID 54:6f:70:76:69:73:69:6f:6e
Remote-ID 00:05:ca:9d:11:60
Chaos 00:00:11:8b:06:01:04:01:02:03:00
---------------------------------------------------------------------------
TIME: 2017-08-10 09:43:41.802
IP: 10.10.0.2 (82:de:11:bc:9a:44) > 10.40.0.2 (0:c:42:9a:6e:75)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 0ee59ebd
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 10.40.0.10
SIADDR: 10.10.0.2
GIADDR: 10.40.0.2
CHADDR: 00:05:ca:9d:11:60:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: test.bin.
OPTION: 1 ( 4) Subnet mask 255.255.0.0
OPTION: 2 ( 4) Time offset -7200 ()
OPTION: 3 ( 4) Routers 10.40.0.1
OPTION: 4 ( 4) Time server 10.10.0.2
OPTION: 7 ( 4) Log server 10.10.0.2
OPTION: 51 ( 4) IP address leasetime 3600 (60m)
OPTION: 53 ( 1) DHCP message type 5 (DHCPACK)
OPTION: 54 ( 4) Server identifier 10.10.0.2
OPTION: 58 ( 4) T1 900 (15m)
OPTION: 59 ( 4) T2 1800 (30m)
OPTION: 61 ( 7) Client-identifier 01:00:05:ca:9d:11:60
OPTION: 82 ( 32) Relay Agent Information
Circuit-ID 54:6f:70:76:69:73:69:6f:6e
Remote-ID 00:05:ca:9d:11:60
Chaos 00:00:11:8b:06:01:04:01:02:03:00
-------------- next part --------------
{
"Dhcp4": {
"interfaces-config": {
"interfaces": [ "eth0" ],
"dhcp-socket-type": "udp"
},
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/kea-dhcp4-ctrl.sock"
},
"lease-database": {
"type": "memfile"
},
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
"renew-timer": 900,
"rebind-timer": 1800,
"valid-lifetime": 3600,
"client-classes": [
{
"name": "Cablemodem",
"test": "substring(option[60].hex,0,6) == 'docsis'",
"next-server": "10.10.0.2",
"boot-file-name": "test.bin"
}
],
"subnet4": [
{
"subnet": "10.40.0.0/16",
"pools": [
{ "pool": "10.40.0.10 - 10.40.0.10" },
{ "pool": "10.40.0.30 - 10.40.0.32" } ],
"next-server": "10.10.0.2",
"client-class": "Cablemodem",
"option-data": [
{
"name": "routers",
"data": "10.40.0.1"
},
{
"name": "time-servers",
"data": "10.10.0.2"
},
{
"name": "log-servers",
"data": "10.10.0.2"
},
{
"name": "time-offset",
"data": "-7200"
},
{
"name": "broadcast-address",
"data": "10.40.255.255"
}
],
"relay": {
"ip-address": "10.40.0.2"
}
},
{
"subnet": "10.60.0.0/16",
"id": 1010,
"pools": [ { "pool": "10.60.0.10 - 10.60.10.254" } ],
"relay": {
"ip-address": "10.60.0.1"
},
"option-data": [
{
"name": "time-servers",
"data": "10.10.0.2"
},
{
"name": "routers",
"data": "10.60.0.1"
},
{
"name": "time-offset",
"data": "-7200"
},
{
"name": "log-servers",
"data": "10.10.0.2"
},
{
"name": "broadcast-address",
"data": "10.60.255.255"
},
{
"name": "domain-name-servers",
"data": "8.8.8.8,8.8.4.4"
}
]
}
]
}
}
More information about the Kea-users
mailing list