NAK Message ignored

Keith kwoody at citytel.net
Wed May 21 23:04:49 UTC 2008


Have a problem thats happening to a few DSL clients. At first I think
there was a router plugged in backwards, which I think we got nailed down
but there some clients doing the following:


May 21 15:27:57 netreg1 dhcpd: DHCPDISCOVER from 00:e0:4c:0a:34:dc
(D2WL8P91) via 69.176.178.1

Discover comes in.

May 21 15:27:57 netreg1 dhcpd: DHCPREQUEST for 192.168.0.115 (0.0.0.0)
from 00:e0:4c:0a:34:dc via 69.176.178.1: wrong network.

But the client appears to also send in a Request at the same time.

May 21 15:27:57 netreg1 dhcpd: DHCPNAK on 192.168.0.115 to
00:e0:4c:0a:34:dc via 69.176.178.1

Server NAKs.

May 21 15:27:58 netreg1 dhcpd: DHCPOFFER on 69.176.178.61 to
00:e0:4c:0a:34:dc (D2WL8P91) via 69.176.178.1

But sends back an Offer, which the client appears to ignore because the
client sends a Discover again a few mins later:

May 21 15:33:55 netreg1 dhcpd: DHCPDISCOVER from 00:e0:4c:0a:34:dc
(D2WL8P91) via 69.176.178.1

May 21 15:33:55 netreg1 dhcpd: DHCPREQUEST for 192.168.0.115 (0.0.0.0)
from 00:e0:4c:0a:34:dc via 69.176.178.1: wrong network.

Server does a NAK again, and sends an Offer, client ignores. Lather, rinse
repeat.

This happens with both off the shelf consumer routers and PC's.

Also the dhcp server ACK's IP's it shouldnt.

May 21 15:32:59 netreg1 dhcpd: DHCPDISCOVER from 00:10:dc:dd:08:94 (HOME)
via 69.176.178.1

May 21 15:32:59 netreg1 dhcpd: DHCPREQUEST for 192.168.0.118 (0.0.0.0)
from 00:10:dc:dd:08:94 via 69.176.178.1: wrong network.

May 21 15:32:59 netreg1 dhcpd: DHCPNAK on 192.168.0.118 to
00:10:dc:dd:08:94 via 69.176.178.1

May 21 15:33:00 netreg1 dhcpd: DHCPOFFER on 69.176.178.39 to
00:10:dc:dd:08:94 (HOME) via 69.176.178.1

May 21 15:33:18 netreg1 dhcpd: DHCPACK to 192.168.0.117
(00:10:dc:dd:08:94) via 69.176.178.1
May 21 15:33:21 netreg1 dhcpd: DHCPACK to 192.168.0.117
(00:10:dc:dd:08:94) via 69.176.178.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Should not be ACK'ing 192.168.0.117.

I dont get what is happening with the dhcp server. It serves about 14
/24's and it doesnt appear any other networks are affected.

Anyone have any pointers on what might be going on here? Ive not seen a
situation like this before.

Thanks,
Keith


More information about the dhcp-users mailing list