On Sat, Oct 22, 2005 at 09:30:37AM +0800, Ronald Wiplinger wrote:
I get some troubles with dhcpd. It takes a long time till some of the clients are served! Sometimes not at all, and I have to reboot the client to get it to work. I would like to understand the log file more. Below are the last entries of dhcpd.
What means Ping timeout: 1 ? What can I do?
It is just an informational message telling you that the server does a ping check to see whether an address it is about to hand out might already be (illegally) in use. The informational message was present only in certain dhcpd versions. The ping check is always there.
What does DHCPACK means after the DHCPREQUEST? What means DHCPDISCOVER?
The usual sequence ;) discover -> offer -> request -> ack
What means (WGR614v4) via eth3 ?
The sent hostname
As you can see the entries for some of the clients repeats all the time, why?
Oct 22 09:19:12 dns dhcpd: DHCPREQUEST for 192.168.250.100 from 00:0e:7a:69:08:0b via eth3 Oct 22 09:19:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3 Oct 22 09:19:41 dns dhcpd: DHCPDISCOVER from 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:19:41 dns dhcpd: Ping timeout: 1 Oct 22 09:19:42 dns dhcpd: DHCPOFFER on 192.168.250.112 to 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:20:12 dns dhcpd: DHCPREQUEST for 192.168.250.100 from 00:0e:7a:69:08:0b via eth3 Oct 22 09:20:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3
You seem to have lease duration of 1 minute only. That is very short.
Oct 22 09:20:23 dns dhcpd: DHCPREQUEST for 192.168.250.114 from 00:09:5b:dc:fe:7d (WGR614v4) via eth3 Oct 22 09:20:23 dns dhcpd: DHCPACK on 192.168.250.114 to 00:09:5b:dc:fe:7d (WGR614v4) via eth3 Oct 22 09:20:44 dns dhcpd: DHCPDISCOVER from 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:20:44 dns dhcpd: Ping timeout: 1 Oct 22 09:20:45 dns dhcpd: DHCPOFFER on 192.168.250.112 to 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:21:12 dns dhcpd: DHCPREQUEST for 192.168.250.100 from 00:0e:7a:69:08:0b via eth3 Oct 22 09:21:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3 Oct 22 09:21:47 dns dhcpd: DHCPREQUEST for 192.168.250.107 from 00:0f:ea:80:b7:f4 (user-8ee849e5ee) via eth3 Oct 22 09:21:47 dns dhcpd: DHCPACK on 192.168.250.107 to 00:0f:ea:80:b7:f4 (user-8ee849e5ee) via eth3 Oct 22 09:21:48 dns dhcpd: DHCPDISCOVER from 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:21:48 dns dhcpd: Ping timeout: 1 Oct 22 09:21:49 dns dhcpd: DHCPOFFER on 192.168.250.112 to 00:0f:d3:00:0c:b5 via eth3 Oct 22 09:21:52 dns dhcpd: DHCPDISCOVER from 00:0b:82:00:8f:44 via eth3 Oct 22 09:21:52 dns dhcpd: Ping timeout: 1 Oct 22 09:21:53 dns dhcpd: DHCPOFFER on 192.168.250.75 to 00:0b:82:00:8f:44 via eth3 Oct 22 09:21:53 dns dhcpd: DHCPREQUEST for 192.168.250.75 (192.168.250.254) from 00:0b:82:00:8f:44 via eth3 Oct 22 09:21:53 dns dhcpd: DHCPACK on 192.168.250.75 to 00:0b:82:00:8f:44 via eth3
Everything looks completely normal. Peter -- the tasty cardinal imitated the tasty can of spam