Bug #36169 for dhcp-public: DHCP 4.1-ESV-R9 - dhclient exits immediately

# Mon, 02 Jun 2014 14:21:58 -0400 John Newlin <jnewlin@google.com> - Ticket created [Reply] [Comment]

CC:	marketing@isc.org
Subject:	DHCP 4.1-ESV-R9 - dhclient exits immediately
Date:	Mon, 2 Jun 2014 18:23:45 +0000
To:	dhcp-bugs@isc.org
From:	John Newlin <jnewlin@google.com>

Download (untitled) / with headers
text/html 1.3KiB

Bug Report from www.isc.org:

Name: John Newlin
Email: jnewlin@google.com
Software Version: DHCP 4.1-ESV-R9
OS: Linux versions: 3.2.26 and 2.6.32.11
Subject:dhclient exits immediately

Bug Detail

If dhclient -6 is started immediately after ifup, dhclient exits with the message:
[ 19.510927] dhclient6.wan0: Can't bind to dhcp address: Cannot assign requested address
[ 19.510954] dhclient6.wan0: Please make sure there is no other dhcp server
[ 19.510970] dhclient6.wan0: running and that there's no entry for dhcp or
[ 19.510987] dhclient6.wan0: bootp in /etc/inetd.conf. Also make sure you
[ 19.511003] dhclient6.wan0: are not running HP JetAdmin software, which
[ 19.511017] dhclient6.wan0: includes a bootp server.

If I wait a bit and run it, it runs fine. I think it's because when the interface comes up the local link address is marked "tentative" and not really usable until the multiple address detection has finished running.

---

This email was received through isc.org Bug Submission Form

All information within this email is considered confidential and for internal use only.

# Fri, 03 Oct 2014 07:01:22 -0400 Chuck Aurora <chucka@isc.org> - Taken

# Sat, 04 Oct 2014 20:59:44 -0400 Chuck Aurora <chucka@isc.org> - Correspondence added [Reply] [Comment]

Download (untitled) / with headers
text/html 1.9KiB

On 06/02/2014 01:21 PM, John Newlin via RT wrote:
> If dhclient -6 is started immediately after ifup, dhclient exits
> with the message:
> [ 19.510927] dhclient6.wan0: Can't bind to dhcp address: Cannot assign requested address
> [ 19.510954] dhclient6.wan0: Please make sure there is no other dhcp server
> [ 19.510970] dhclient6.wan0: running and that there's no entry for dhcp or
> [ 19.510987] dhclient6.wan0: bootp in /etc/inetd.conf. Also make sure you
> [ 19.511003] dhclient6.wan0: are not running HP JetAdmin software, which
> [ 19.511017] dhclient6.wan0: includes a bootp server.
>
> If I wait a bit and run it, it runs fine. I think it's because
> when the interface comes up the local link address is marked
> "tentative" and not really usable until the multiple address
> detection has finished running.

Hi John, thank you for the report, and please accept my apology
for the long delay in response. This was assigned to me back in
June, and actually a bit before that because someone was asking
what was fundamentally the same question in response to a post
on our ISC.org blog. It got lost among other issues.

The answer is: you are right. IPv6 must first be enabled on an
interface before you can use DHCPv6. If there is a delay in
your link-local address coming up, your OS should wait before
trying to run "dhclient -6". (Perhaps this is worth filing a
bug with Debian?)

This new Knowledge Base article explains it:

https://kb.isc.org/article/AA-01212

Thanks again for the report, and for your use of and interest in
ISC software. I am marking this bug as resolved.
--
Chuck Aurora : ISC Software Support : chucka@isc.org
Internet Systems Consortium, Inc.

# Sat, 04 Oct 2014 20:59:45 -0400 The RT System itself - Status changed from 'new' to 'open'

# Sat, 04 Oct 2014 20:59:46 -0400 Chuck Aurora <chucka@isc.org> - Status changed from 'open' to 'rejected'

# Sun, 05 Oct 2014 10:11:18 -0400 John Newlin <jnewlin@google.com> - Correspondence added [Reply] [Comment]

Subject:	Re: [ISC-Bugs #36169] DHCP 4.1-ESV-R9 - dhclient exits immediately
Date:	Sun, 5 Oct 2014 07:11:13 -0700
To:	dhcp-bugs@isc.org, chucka@isc.org
From:	John Newlin <jnewlin@google.com>

Download (untitled) / with headers
text/plain 2.1KiB

Download (untitled) / with headers
text/html 2.7KiB

Hmm interesting thanks. It might be better if instead of exiting dhclient just waited for a link local address, or had an option to do that. I can add that and submit a patch back to isc. Otherwise I'll need to write a wrapper around dhclient to do the same thing.

This is for an embedded system so I doubt debian is going to fix it for us. :)

On Sat, Oct 4, 2014 at 5:59 PM, Chuck Aurora via RT <dhcp-bugs@isc.org> wrote:

On 06/02/2014 01:21 PM, John Newlin via RT wrote:
> If dhclient -6 is started immediately after ifup, dhclient exits
> with the message:
> [ 19.510927] dhclient6.wan0: Can't bind to dhcp address: Cannot assign
requested address
> [ 19.510954] dhclient6.wan0: Please make sure there is no other dhcp server
> [ 19.510970] dhclient6.wan0: running and that there's no entry for dhcp or
> [ 19.510987] dhclient6.wan0: bootp in /etc/inetd.conf. Also make sure you
> [ 19.511003] dhclient6.wan0: are not running HP JetAdmin software, which
> [ 19.511017] dhclient6.wan0: includes a bootp server.
>
> If I wait a bit and run it, it runs fine. I think it's because
> when the interface comes up the local link address is marked
> "tentative" and not really usable until the multiple address
> detection has finished running.

Hi John, thank you for the report, and please accept my apology
for the long delay in response. This was assigned to me back in
June, and actually a bit before that because someone was asking
what was fundamentally the same question in response to a post
on our ISC.org blog. It got lost among other issues.

The answer is: you are right. IPv6 must first be enabled on an
interface before you can use DHCPv6. If there is a delay in
your link-local address coming up, your OS should wait before
trying to run "dhclient -6". (Perhaps this is worth filing a
bug with Debian?)

This new Knowledge Base article explains it:

https://kb.isc.org/article/AA-01212

Thanks again for the report, and for your use of and interest in
ISC software. I am marking this bug as resolved.
--
Chuck Aurora : ISC Software Support : chucka@isc.org
Internet Systems Consortium, Inc.

# Sun, 05 Oct 2014 10:11:19 -0400 The RT System itself - Status changed from 'rejected' to 'open'

# Thu, 09 Oct 2014 12:12:46 -0400 Chuck Aurora <chucka@isc.org> - Correspondence added [Reply] [Comment]

Subject:	Re: [ISC-Bugs #36169] DHCP 4.1-ESV-R9 - dhclient exits immediately
Date:	Thu, 09 Oct 2014 11:12:19 -0500
To:	dhcp-bugs@isc.org
From:	Chuck Aurora <chucka@isc.org>

Download (untitled) / with headers
text/plain 679B

On 10/05/2014 09:11 AM, John Newlin via RT wrote: > Hmm interesting thanks. It might be better if instead of > exiting dhclient just waited for a link local address, or had > an option to do that. I can add that and submit a patch back > to isc. Otherwise I'll need to write a wrapper around > dhclient to do the same thing. Ah, that makes sense. We like patches, of course. We'd be most likely to accept something with a command line option to do some sort of wait after the attempt to open the link-local socket fails. Thanks again; we're looking forward to your patch. -- Chuck Aurora : ISC Software Support : chucka@isc.org Internet Systems Consortium, Inc.

# Thu, 09 Oct 2014 12:14:45 -0400 Chuck Aurora <chucka@isc.org> - Severity S2 Normal added

# Thu, 09 Oct 2014 12:14:46 -0400 Chuck Aurora <chucka@isc.org> - Given to Nobody in particular

# Wed, 25 Mar 2015 02:37:54 -0400 Shawn Routhier <sar@isc.org> - FinalPriority changed from '50' to '60'

# Wed, 25 Mar 2015 02:37:54 -0400 Shawn Routhier <sar@isc.org> - Priority changed from '50' to '60'

# Wed, 25 Mar 2015 02:37:54 -0400 Shawn Routhier <sar@isc.org> - Versions Planned 4.3.3 added

# Thu, 26 Mar 2015 01:01:04 -0400 Shawn Routhier <sar@isc.org> - FinalPriority changed from '60' to '30'

# Thu, 26 Mar 2015 01:01:04 -0400 Shawn Routhier <sar@isc.org> - Priority changed from '60' to '30'

# Thu, 26 Mar 2015 22:51:58 -0400 Shawn Routhier <sar@isc.org> - TimeEstimated changed from (no value) to '720'

# Thu, 30 Jul 2015 00:54:35 -0400 Shawn Routhier <sar@isc.org> - Versions Planned 4.3.3 changed to 4.3.4

# Wed, 19 Aug 2015 01:41:11 -0400 Shawn Routhier <sar@isc.org> - TimeLeft changed from (no value) to '720'

# Thu, 21 Apr 2016 12:59:55 -0400 Shawn Routhier <sar@isc.org> - Versions Planned 4.3.4 changed to 4.3.5

# Wed, 30 Nov 2016 10:00:01 -0500 Thomas Markwalder <tmark@isc.org> - Versions Planned 4.3.5 changed to 4.3.6

# Wed, 17 May 2017 03:59:11 -0400 Marcin Siodelski <marcin@isc.org> - Taken

# Thu, 18 May 2017 08:27:18 -0400 Thomas Markwalder <tmark@isc.org> - Versions Planned 4.3.6 changed to 4.4.0 4.3.6 4.1-ESV-R15

# Thu, 18 May 2017 08:27:18 -0400 Thomas Markwalder <tmark@isc.org> - Area bug added

# Thu, 18 May 2017 08:27:19 -0400 Thomas Markwalder <tmark@isc.org> - Component DHCP Client added

# Mon, 22 May 2017 10:38:06 -0400 Marcin Siodelski <marcin@isc.org> - Worked 24 hours (1,440 minutes) 1,440 minutes

# Mon, 22 May 2017 10:38:06 -0400 Marcin Siodelski <marcin@isc.org> - Queue changed from #8 to #9

# Mon, 05 Jun 2017 12:56:00 -0400 Marcin Siodelski <marcin@isc.org> - Version Fixed 4.1-ESV-R15, 4.3.6, 4.4.0 added

# Mon, 05 Jun 2017 12:56:01 -0400 Marcin Siodelski <marcin@isc.org> - Worked 6.33 hours (380 minutes) 380 minutes

# Mon, 05 Jun 2017 12:56:01 -0400 Marcin Siodelski <marcin@isc.org> - Status changed from 'open' to 'resolved'

# Mon, 05 Jun 2017 13:34:31 -0400 Marcin Siodelski <marcin@isc.org> - Correspondence added [Reply] [Comment]

Download (untitled) / with headers
text/plain 1.1KiB

Hello John, We are pleased to inform you that we've addressed your issue in our next releases of ISC DHCP: 4.3.6 (July 2017), 4.1-ESV-R15 (July 2017) and 4.4.0 (around Q4'17). We have added a new command line option for the dhclient, --dad-wait-time, which allows you to specify a maximum time that the dhclient process should wait for the duplicate address detection to complete before initiating any DHCP transactions. The actual wait is performed in a dhclient-script, so you have to make sure that the script you're using supports this new parameter. The good news is that we have updated dhclient-scripts that we're shipping with ISC DHCP and you can use them as reference in case you're using some custom script. We like to give our contributors credit for their submissions by citing them in the release notes. If you would like to be recognized in this manner, please respond with how you wish to be identified. Typically it is by name and/or organization. Thank you for interest and for taking the time and effort to report the issue. We welcome any future submissions you choose to make. Sincerely, Marcin Siodelski ISC Software Engineering

# Mon, 05 Jun 2017 13:34:32 -0400 The RT System itself - Status changed from 'resolved' to 'open'

# Mon, 05 Jun 2017 13:34:43 -0400 Marcin Siodelski <marcin@isc.org> - Status changed from 'open' to 'resolved'

# Wed, 21 Jun 2017 15:40:12 -0400 Brian Conry <bconry@isc.org> - Queue changed from #9 to #8

# Tue, 12 Dec 2017 07:38:36 -0500 Thomas Markwalder <tmark@isc.org> - Queue changed from #8 to dhcp-public

Bug #36169 for dhcp-public: DHCP 4.1-ESV-R9 - dhclient exits immediately

This bug tracker is no longer active.

Bug Report from www.isc.org:

Bug Detail