Send dhcp-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Dhclient not sending DHCPDISCOVER after reason=TIMEOUT
(Vasanth Ragavendran)
2. Re: Dhclient not sending DHCPDISCOVER after reason=TIMEOUT
(Vasanth Ragavendran)
----------------------------------------------------------------------
Message: 1
Date: Thu, 27 Oct 2016 16:01:02 +0800
From: Vasanth Ragavendran <[email protected]>
To: [email protected]
Subject: Dhclient not sending DHCPDISCOVER after reason=TIMEOUT
Message-ID:
<CADfuMF4xNXW+pOScCwreRKAEM9Qhc=0bzr7_guuwxq7jgoa...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi,
I am using ISC dhclient 4.3.1 on my debian 8.3 Linux. When the reason
reported by dhclient is TIMEOUT (as there is a valid lease in leases
file), and if the DHCP server is unreachable(from which the last time
the lease was obtained) then the dhclient-script exits with status 2.
The dhclient is not sending DHCPDISCOVER msgs after this. Why is this
so?
However, when the reason reported by dhclient is FAILED, the dhclient
keeps sending DHCPDISCOVER msgs periodically. Note that the timeout
and retry values in dhclient.conf are 8 seconds and 1 second
respectively.
There can be a scenario where the DHCP server is unreachable now (from
last time when a valid lease was obtained from the DHCP server),
because its down or something, but can be available later. In such a
case, with valid lease in leases file if $reason is TIMEOUT, the
dhclient is not sending DHCPDISCOVER periodically. I am using
ifup/ifdown scripts to manage the network connectivity. Awaiting your
reply.
Thanks and Regards,
R. Vasanth Ragavendran.
------------------------------
Message: 2
Date: Thu, 27 Oct 2016 17:18:10 +0800
From: Vasanth Ragavendran <[email protected]>
To: [email protected]
Subject: Re: Dhclient not sending DHCPDISCOVER after reason=TIMEOUT
Message-ID:
<CADfuMF4uxtVHmJG74Kxn_zQ5_dhSS=b4xp7zsyzrn4cyjde...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Found the issue. It was due to dhclient-script wrongly interpreting
the exit status, due to which the exit status always turned out to be
0 and hence "if (!script_go (client))" in state_panic function always
turned out to be true, there by putting the dhclient in BOUND state
and not starting a timer to send the DHCPDISCOVER.
On Thu, Oct 27, 2016 at 4:01 PM, Vasanth Ragavendran
<[email protected]> wrote:
> Hi,
>
> I am using ISC dhclient 4.3.1 on my debian 8.3 Linux. When the reason
> reported by dhclient is TIMEOUT (as there is a valid lease in leases
> file), and if the DHCP server is unreachable(from which the last time
> the lease was obtained) then the dhclient-script exits with status 2.
> The dhclient is not sending DHCPDISCOVER msgs after this. Why is this
> so?
> However, when the reason reported by dhclient is FAILED, the dhclient
> keeps sending DHCPDISCOVER msgs periodically. Note that the timeout
> and retry values in dhclient.conf are 8 seconds and 1 second
> respectively.
>
> There can be a scenario where the DHCP server is unreachable now (from
> last time when a valid lease was obtained from the DHCP server),
> because its down or something, but can be available later. In such a
> case, with valid lease in leases file if $reason is TIMEOUT, the
> dhclient is not sending DHCPDISCOVER periodically. I am using
> ifup/ifdown scripts to manage the network connectivity. Awaiting your
> reply.
>
> Thanks and Regards,
> R. Vasanth Ragavendran.
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 96, Issue 24
******************************************
