On Saturday 22 October 2005 03:30, 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? What does DHCPACK means after the DHCPREQUEST? What means DHCPDISCOVER? ..... What means (WGR614v4) via eth3 ? 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 your dhcpd received a request for the MAC 00:0e:7a:69:08:0b to get a lease for
I am by far no expert in dhcp but that is how I interpret your logs: the IP 192.168.250.100. The request was received through the device eth3.
Oct 22 09:19:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3 Your dhcps acknowledges the request.
Oct 22 09:19:41 dns dhcpd: DHCPDISCOVER from 00:0f:d3:00:0c:b5 via eth3 server received a broadcast request for a DHCP server from 00:0f:d3:00:0c:b5. 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 your server offers to that client the IP 192.168.250.112 Oct 22 09:20:12 dns dhcpd: DHCPREQUEST for 192.168.250.100 from 00:0e:7a:69:08:0b via eth3 00:0e:7a:69:08:0b is asking again to lease the IP 192.168.250.100 Seams that your lease time is set to 60 seconds for clients. If the clients on your network are not changing that frequently try to set it to something higher. (eg: one hour or one day)
Oct 22 09:20:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3 Oct 22 09:20:23 dns dhcpd: DHCPREQUEST for 192.168.250.114 from 00:09:5b:dc:fe:7d (WGR614v4) via eth3 On my network are only windows clients and the (WGR614v4) is their netbios name. (computer name)
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
I do not know what the "Ping timeout: 1" means. Could be that some firewall on the client is in the way but not sure about that. What do you mean that it takes a long time until you clients are served? As you can see in the logs your server responds right away to the requests. ( Response within a second) What kind of clients do you have? Ulf