booting disallowed

Chuck Anderson cra at WPI.EDU
Tue Dec 11 13:28:01 UTC 2007


On Tue, Dec 11, 2007 at 11:58:20AM +0100, Simon Schlumpf wrote:
> Since some days, users on our network have problems getting an IP 
> address via DHCP. Some users get an IP address without a problem other's 
> don't.
> If a user comes with an DHCPREQUEST:
> 
> 08:20:22 intranet dhcpd: DHCPREQUEST for 192.168.178.22 from 
> 00:16:41:59:25:ec via eth0: unknown lease 192.168.178.22.
> 
> then, he gets no answer. (authoritative; is set)
> 
> Later, 30 seconds, the clients tried again, but:
> 
> Dec 10 08:20:55 intranet dhcpd: DHCPDISCOVER from 00:16:41:59:25:ec via 
> eth0: booting disallowed
> 
> This message apears several time in the next hour, until:
> 
> Dec 10 09:09:26 intranet dhcpd: DHCPOFFER on 131.152.195.216 to 
> 00:16:41:59:25:ec (lphoffmann) via eth0
> Dec 10 09:09:26 intranet dhcpd: DHCPREQUEST for 131.152.195.216 
> (131.152.195.23) from 00:16:41:59:25:ec (lphoffmann) via eth0
> Dec 10 09:09:26 intranet dhcpd: DHCPACK on 131.152.195.216 to 
> 00:16:41:59:25:ec (lphoffmann) via eth0
> 
> What's going on?

Is there a rogue DHCP server on the network giving some clients 
192.168 addresses?

What does your dhcpd.conf look like?  Are there any allow/deny 
statements in it?


More information about the dhcp-users mailing list