[Kea-users] Invalid DHCP Server Identifier: 0.0.0.0

[Todd Simmons (todsimmo)]

Adam,

When you say you have the router acting as a relay, do you mean you have a
sub-interface on the router for the subnet and it has the Kea IP as the
helper address?



Todd Simmons
CCIE Wireless #42411
Network Consulting Engineer
Advanced Services WWWP - Wireless LAN
Cisco Systems, Inc.
todsimmo at cisco.com
Phone: +1 469 255 0183
Mobile: +1 512 749 7167

Cisco.com <http://cisco.com/> - http://www.cisco.com
<http://www.cisco.com/>

http://wwwin-tools.cisco.com/dir/vcard/todsimmo.vcf

This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient
(or authorized to receive for the recipient), please contact the sender by
reply email and delete all copies of this message.
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html





On 8/30/16, 8:42 AM, "Kea-users on behalf of Adam Twardowski"
<kea-users-bounces at lists.isc.org on behalf of atwardowski at choopa.com>
wrote:

>I am running kea on FreeBSD.  I have a cisco router configured as a dhcp
>relay, forwarding requests to Kea.  Kea receives the requests and sends
>out a reply, but the reply has option 54 set to 0.0.0.0, which as far as
>I know doesn't make any sense.  The DHCP client can't continue the
>transaction because it obviously can't send a packet to 0.0.0.0.  Is
>there any way I can tell kea to send a valid server identifier?
>
>
>Config:
>
>{
>"Dhcp4":
>{
>   "interfaces-config": {
>     "interfaces": [ "em0" ],
>     "dhcp-socket-type": "udp"
>   },
>   "lease-database": {
>     "type": "memfile",
>     "lfc-interval": 1800
>   },
>   "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
>   },
>
>   "valid-lifetime": 4000,
>
>   "subnet4": [
>   {    "subnet": "10.128.224.0/20",
>        "pools": [ { "pool": "10.128.239.3 - 10.128.239.254" } ],
>        "option-data": [
>             { "name": "routers", "data": "10.128.224.1" },
>             { "name": "domain-name-servers", "data": "8.8.8.8, 8.8.4.4"
>},
>         ]
>   }
>   ]
>},
>
>
>
>Kea Reply:
>
>Bootstrap Protocol (Offer)
>     Message type: Boot Reply (2)
>     Hardware type: Ethernet (0x01)
>     Hardware address length: 6
>     Hops: 1
>     Transaction ID: 0xccc20000
>     Seconds elapsed: 0
>     Bootp flags: 0x0000 (Unicast)
>         0... .... .... .... = Broadcast flag: Unicast
>         .000 0000 0000 0000 = Reserved flags: 0x0000
>     Client IP address: 0.0.0.0
>     Your (client) IP address: 10.128.239.4
>     Next server IP address: 0.0.0.0
>     Relay agent IP address: 10.128.224.1
>     Client MAC address: ---------- DELETED -----------
>     Client hardware address padding: 00000000000000000000
>     Server host name not given
>     Boot file name not given
>     Magic cookie: DHCP
>     Option: (1) Subnet Mask
>         Length: 4
>         Subnet Mask: 255.255.240.0
>     Option: (3) Router
>         Length: 4
>         Router: 10.128.224.1
>     Option: (6) Domain Name Server
>         Length: 8
>         Domain Name Server: 8.8.8.8
>         Domain Name Server: 8.8.4.4
>     Option: (51) IP Address Lease Time
>         Length: 4
>         IP Address Lease Time: (4000s) 1 hour, 6 minutes, 40 seconds
>     Option: (53) DHCP Message Type (Offer)
>         Length: 1
>         DHCP: Offer (2)
>     Option: (54) DHCP Server Identifier
>         Length: 4
>         DHCP Server Identifier: 0.0.0.0
>     Option: (255) End
>         Option End: 255
>
>_______________________________________________
>Kea-users mailing list
>Kea-users at lists.isc.org
>https://lists.isc.org/mailman/listinfo/kea-users