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 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 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
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
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 Oct 22 09:19:12 dns dhcpd: DHCPACK on 192.168.250.100 to 00:0e:7a:69:08:0b via eth3 The client is requesting 192.168.250.100 -- probably it was assigned
Ronald Wiplinger
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 Here the client is hunting for any DHCP server it can find, and at the same time it is requesting a brand new IP. The server selects an IP from its pool and checks (ICMP Ping) to see if the IP is in use; it is not (ping timeout), so the server offers the IP to the client. You do not need to worry about the Ping timeout, it is quite normal.
[Sidebar comment: You *do* need to worry if you see a "ping" here that did -not- timeout, because that would mean the DHCP server has an IP listed as "free" in its pool, but the IP is actually in use somewhere in the network. Restarting all the clients should resolve such a problem (no need to reboot, just restart their DHCP client scripts).] The very next thing that should happen is that the client announces it accepts the IP (by sending a DHCPREQUEST to the server), or refuses it (with a DHCPDECLINE). Neither of these happens, so the OFFER message is not getting to the client at all. About a minute later, the client starts again with a brand new DISCOVER message, which makes me think the client's firewall is blocking incoming DHCP traffic. Check your firewall on this client to make sure that TCP and UDP ports 67 and 68 (bootps and bootpc) are open for incoming traffic (also see below).
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 This IP was assigned to the same client only a minute ago; as Ulf says, your lease time is only 60 seconds. Check the DHCP server config file and set it to 86400 (seconds, or one day).
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 This is what the sequence should look like when a client starts with a DISCOVER message. This client most likely is not giving you any problems at all.
If you are using the ISC dhclient/server you will have package dhcp installed (the common files used by both client and server packages). This package includes RFC 2131, which is the RFC for DHCP stuff. It might help to read this document in conjunction with the manpages for your client and server. Also examining the DHCP lease file (which is in /var/lib/dhcp/) should give you some assistance in properly configuring your server. And finally, make sure your firewall isn't blocking the ports DHCP uses -- 67 and 68, for both tcp and udp. If you are using SuSEfirewall2, there should not be any problems (it's what I use), unless you are specifically blocking port 67 for INPUT.
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
participants (4)
-
Darryl Gregorash -
poeml＠cmdline.net -
Ronald Wiplinger -
Ulf Rasch