dhcpd ACKing wrong network.

Keith kwoody at citytel.net
Fri Nov 23 18:06:14 UTC 2007


Have a strange problem:

Nov 23 07:49:11 netreg1 dhcpd: DHCPREQUEST for 192.168.0.110 (192.168.0.1)
from 00:02:55:79:55:51 via 69.176.178.1: wrong network.

Server gets a request above.

Nov 23 07:49:11 netreg1 dhcpd: DHCPNAK on 192.168.0.110 to
00:02:55:79:55:51 via 69.176.178.1

Which the server NAK's. Dont see anything again from this machine until a
few hours later.

Nov 23 09:39:56 netreg1 dhcpd: DHCPINFORM from 192.168.0.110 via
69.176.178.1
Nov 23 09:39:56 netreg1 dhcpd: DHCPACK to 192.168.0.110
(00:02:55:79:55:51) via 69.176.178.1

And then out of the blue a few hours later, same machine shows up with an
INFORM, using the same IP the server NAK'd before, but the server ACK's
the INFORM.

It appears someone has a Linksys/Dlink/whatever router plugged in
wrong and is giving out 192.168 space, which I'm trying to track down
now.

If the server knows that 192.168 is not part of its network and NAK'd the
REQUEST, why did it ACK the INFORM? Any way to prevent it?

Thanks,
Keith





More information about the dhcp-users mailing list