Re: DHCP slow renewal, actually times out but mysteriously still gets an IP
On Friday 21 May 2004 12:55 pm, Stalks wrote:
> # I first restarted the dhcp3-server process
> May 21 14:24:13 nooblet dhcpd: Wrote 0 deleted host decls to leases file.
> May 21 14:24:13 nooblet dhcpd: Wrote 0 new dynamic host decls to leases file.
> May 21 14:24:13 nooblet dhcpd: Wrote 0 leases to leases file.
> # ipconfig /release
> May 21 14:24:53 nooblet dhcpd: DHCPRELEASE of 81.168.82.220 from 00:0c:6e:70:29:33 via br0 (not found)
> # ipconfing /renew (start)
> May 21 14:25:00 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via br0
> May 21 14:25:00 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> May 21 14:25:05 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via br0
> May 21 14:25:05 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> May 21 14:25:13 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via br0
> May 21 14:25:13 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> May 21 14:25:30 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via br0
> May 21 14:25:30 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> May 21 14:26:06 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via br0
> May 21 14:26:06 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> May 21 14:26:06 nooblet dhcpd: DHCPREQUEST for 81.168.82.220 (0.0.0.0) from 00:0c:6e:70:29:33 via br0
> May 21 14:26:06 nooblet dhcpd: DHCPACK on 81.168.82.220 to 00:0c:6e:70:29:33 via br0
> # ipconfig /renew (end, finally get an ACK)
Maybe a firewall is getting in the way or another device is acting as a
DHCP server also. What does the output of iptables -nvL look like?
--
Rob
Reply to: