dhclient DHCPREQUEST in logs

Hi,

I have a server which runs under dhcp with dhclient. In the logs I find
the following:

Aug 9 22:27:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:28:11 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:28:26 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:30:37 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:31:45 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:34:16 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:37:13 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:40:24 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:41:24 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:42:33 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:44:06 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:47:16 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:54:59 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:58:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:59:31 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 22:59:57 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:00:32 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:01:42 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:03:50 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:06:59 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:15:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:20:38 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:25:26 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:31:34 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:41:46 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 9 23:50:32 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 00:00:18 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 00:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 00:35:42 ns dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port 67
Aug 10 00:35:42 ns dhclient: DHCPACK from 117.160.206.250
Aug 10 00:35:42 ns dhclient: bound to 117.160.111.9 -- renewal in 66270
seconds.
Aug 10 19:00:12 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 19:02:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 19:03:23 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67
Aug 10 19:04:00 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
port 67


So my server asks the dhcp server for an IP-Address. After one day of
asking it gets it. Why that server does not response on the first
question. Is it wrong in my dhclient setup?

Thanks...

hakim wrote:
> Hi,
>
> I have a server which runs under dhcp with dhclient. In the logs I find
> the following:
>
> Aug 9 22:27:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67

( plenty of similar entries clipped)

> Aug 10 00:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPREQUEST on eth0 to 255.255.255.255
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPACK from 117.160.206.250
> Aug 10 00:35:42 ns dhclient: bound to 117.160.111.9 -- renewal in 66270
> seconds.
> Aug 10 19:00:12 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:02:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:03:23 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:04:00 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
>
>
> So my server asks the dhcp server for an IP-Address. After one day of
> asking it gets it. Why that server does not response on the first
> question. Is it wrong in my dhclient setup?


A sensible client asks for lease renewal from the place
it received the previous one, it's OK.

The server does not behave properly if it does not
respond to an addressed request, but responds to a broadcast.

--

Tauno Voipio
tauno voipio (at) iki fi

"hakim" wrote
> Hi,
>
> I have a server which runs under dhcp with dhclient. In the logs I find
> the following:
>
> Aug 9 22:27:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
(....)
> Aug 10 00:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPREQUEST on eth0 to 255.255.255.255
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPACK from 117.160.206.250
> Aug 10 00:35:42 ns dhclient: bound to 117.160.111.9 -- renewal in 66270
> seconds.
> Aug 10 19:00:12 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:02:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:03:23 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:04:00 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
>
>
> So my server asks the dhcp server for an IP-Address. After one day of
> asking it gets it. Why that server does not response on the first
> question. Is it wrong in my dhclient setup?
>
> Thanks...
>
Maybe the server was run out of IP addresses.
Maybe the lease time was set for example one day and after that day the
lease time for the leased-out IP address expired, and the server leased
it
out with the first next DHCP request.

Note that this was a DCHPDiscover - so it seems a renewal. This seems
to be
the case:
"Aug 10 00:35:42 ns dhclient: bound to 117.160.111.9 -- renewal in
66270
seconds."

Another possiblity is that the DHCPserver was off-line (maybe the IP
address
was reachable). A DHCP client will try to renew the DHCP address when
50(?)%
(not sure if it 50) of the time is expired.

Altough I find it strange that the time intervals are not all the same
or
have some logic.

I suggest to check:
* dhcp pool - which addresses could be leased, how many are leased at
this
moment and to who
* what is the lease time
* does the dhcpclient still have an IP addresss

Michael

hakim wrote:
> Hi,
>
> I have a server which runs under dhcp with dhclient. In the logs I find
> the following:
>
> Aug 9 22:27:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:28:11 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:28:26 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:30:37 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:31:45 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:34:16 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:37:13 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:40:24 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:41:24 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:42:33 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:44:06 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:47:16 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:54:59 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:58:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:59:31 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 22:59:57 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:00:32 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:01:42 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:03:50 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:06:59 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:15:02 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:20:38 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:25:26 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:31:34 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:41:46 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 9 23:50:32 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 00:00:18 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 00:17:49 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPREQUEST on eth0 to 255.255.255.255
> port 67
> Aug 10 00:35:42 ns dhclient: DHCPACK from 117.160.206.250
> Aug 10 00:35:42 ns dhclient: bound to 117.160.111.9 -- renewal in 66270
> seconds.
> Aug 10 19:00:12 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:02:47 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:03:23 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
> Aug 10 19:04:00 ns dhclient: DHCPREQUEST on eth0 to 117.160.206.250
> port 67
>
>
> So my server asks the dhcp server for an IP-Address. After one day of
> asking it gets it. Why that server does not response on the first
> question. Is it wrong in my dhclient setup?
>
> Thanks...
>

What a coincidence. My server also started doing that about a month ago.
I get an address from RoadRunner (Cable modem). I think they changed
their DHCP server configuration. Don't know what.

It seems dhclient sends a DHCPREQUEST repeatedly when renewal time is
up. The server is apparently not replying so it just keeps trying. When
the lease time is up, dhclient sends a DHCPDISCOVER, gets its lease
renewed and all is good until the next round.

I have switched to dhcpcd. The difference is that when it gets no reply
to a DHCPREQUEST (renewal request), it seems to just shrug its shoulders
and waits until lease time is up before trying again.

Either way, it all works. I just found those messages annoying.

Rich Piotrowski
--
"Now are you talking about what it is you know
or just repeating what it was you heard."
Grace Slick
To E-mail use: rpiotro(at)wi(dot)rr(dot)com

Hi,

I will try that. The messages are really annoying...

Thanks...