Re: dhclient DHCPREQUEST in logs
sp1471_at_zonnet.nl
Date: 08/10/05
- Next message: RobO: "Re: Samba timestamps wrong!"
- Previous message: Justin Todd: "TCP timeouts"
- In reply to: Tauno Voipio: "Re: dhclient DHCPREQUEST in logs"
- Next in thread: Rich Piotrowski: "Re: dhclient DHCPREQUEST in logs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 10 Aug 2005 13:20:57 -0700
"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
- Next message: RobO: "Re: Samba timestamps wrong!"
- Previous message: Justin Todd: "TCP timeouts"
- In reply to: Tauno Voipio: "Re: dhclient DHCPREQUEST in logs"
- Next in thread: Rich Piotrowski: "Re: dhclient DHCPREQUEST in logs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|