Debian Bug report logs -
#270890
dhcp3-client: starts all interfaces specified in dhclient.conf regardless of command-line parameters
Reported by: Tim Riker <Tim@Rikers.org>
Date: Thu, 9 Sep 2004 20:18:01 UTC
Severity: important
Tags: confirmed
Done: Michael Gilbert <mgilbert@debian.org>
Bug is archived. No further changes may be made.
Forwarded to dhcp-bugs@isc.org
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, peloy@debian.org (Eloy A. Paris):
Bug#270890; Package dhcp3-client.
(full text, mbox, link).
Acknowledgement sent to Tim Riker <Tim@Rikers.org>:
New Bug report received and forwarded. Copy sent to peloy@debian.org (Eloy A. Paris).
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Subject: dhcp3-client: bug
Package: dhcp3-client
Version: 3.0.1-1
Severity: important
debian kernel:
root@cn014a0868018l1:~# uname -a
Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686
GNU/Linux
kernel-image-2.6.8-1-686 2.6.8-2
dhclient version:
timr@cn014a0868018l1:~$ dhclient --help
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to
specify a different hostname when making requests on each interface so I
have:
interface "eth0" {
send host-name "cn014a0868018l1-eth0";
}
interface "eth1" {
send host-name "cn014a0868018l1-eth1";
}
in my /etc/dhcp3/dhclient.conf
If I leave these enabled and run:
root@cn014a0868018l1:~# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:08:74:97:c9:9e
Sending on LPF/eth0/00:08:74:97:c9:9e
Listening on LPF/eth1/00:0b:fd:f8:b4:da
Sending on LPF/eth1/00:0b:fd:f8:b4:da
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 156.117.114.4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 156.117.114.3
bound to 156.117.114.96 -- renewal in 140123 seconds.
So dhclient is requesting eth0 even though I gave it eth1 on the command
line. If I remove the interface sections it behaves as expected. The man
page for dhclient.conf states that only matching interface configuration
will be used.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dhcp3-client depends on:
ii debconf 1.4.30 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii dhcp3-common 3.0.1-1 Common files used by all the dhcp3
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
--
Tim Riker - http://rikers.org/ - TimR@Debian.org
Linux Technologist - Tim@TI.com - http://www.TI.com/
BZFlag maintainer - http://BZFlag.org/ - for fun!
Information forwarded to debian-bugs-dist@lists.debian.org, peloy@debian.org (Eloy A. Paris):
Bug#270890; Package dhcp3-client.
(full text, mbox, link).
Acknowledgement sent to Andrew Pollock <apollock@debian.org>:
Extra info received and forwarded to list. Copy sent to peloy@debian.org (Eloy A. Paris).
(full text, mbox, link).
Message #10 received at 270890@bugs.debian.org (full text, mbox, reply):
tags 270890 + moreinfo
thanks
Hi Tim,
Could you possibly send your entire dhclient.conf?
I've just tried adding
interface "eth0" {
send host-name "eth0";
}
interface "eth1" {
send host-name "eth1";
}
and I get a lot of complaints from dhclient (3.0.2) about the config
file being invalid.
regards
Andrew
On Thu, Sep 09, 2004 at 03:07:08PM -0500, Tim Riker wrote:
> Subject: dhcp3-client: bug
> Package: dhcp3-client
> Version: 3.0.1-1
> Severity: important
>
> debian kernel:
>
> root@cn014a0868018l1:~# uname -a
> Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686
> GNU/Linux
>
> kernel-image-2.6.8-1-686 2.6.8-2
>
> dhclient version:
>
> timr@cn014a0868018l1:~$ dhclient --help
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
>
> My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to
> specify a different hostname when making requests on each interface so I
> have:
>
> interface "eth0" {
> send host-name "cn014a0868018l1-eth0";
> }
>
> interface "eth1" {
> send host-name "cn014a0868018l1-eth1";
> }
>
> in my /etc/dhcp3/dhclient.conf
>
> If I leave these enabled and run:
>
> root@cn014a0868018l1:~# dhclient eth1
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/products/DHCP
>
> wifi0: unknown hardware address type 801
> sit0: unknown hardware address type 776
> wifi0: unknown hardware address type 801
> sit0: unknown hardware address type 776
> Listening on LPF/eth0/00:08:74:97:c9:9e
> Sending on LPF/eth0/00:08:74:97:c9:9e
> Listening on LPF/eth1/00:0b:fd:f8:b4:da
> Sending on LPF/eth1/00:0b:fd:f8:b4:da
> Sending on Socket/fallback
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
> DHCPOFFER from 156.117.114.4
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPACK from 156.117.114.3
> bound to 156.117.114.96 -- renewal in 140123 seconds.
>
> So dhclient is requesting eth0 even though I gave it eth1 on the command
> line. If I remove the interface sections it behaves as expected. The man
> page for dhclient.conf states that only matching interface configuration
> will be used.
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.8-1-686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages dhcp3-client depends on:
> ii debconf 1.4.30 Debian configuration management sy
> ii debianutils 2.8.4 Miscellaneous utilities specific t
> ii dhcp3-common 3.0.1-1 Common files used by all the dhcp3
> ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
> --
> Tim Riker - http://rikers.org/ - TimR@Debian.org
> Linux Technologist - Tim@TI.com - http://www.TI.com/
> BZFlag maintainer - http://BZFlag.org/ - for fun!
>
>
Tags added: moreinfo
Request was from Andrew Pollock <apollock@debian.org>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, peloy@debian.org (Eloy A. Paris):
Bug#270890; Package dhcp3-client.
(full text, mbox, link).
Acknowledgement sent to Tim Riker <Tim@Rikers.org>:
Extra info received and forwarded to list. Copy sent to peloy@debian.org (Eloy A. Paris).
(full text, mbox, link).
Message #17 received at 270890@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
I get the same results with a really small dhclient.conf. Note that my
eth1 is a cisco wireless card (from kernel-image-2.6.10-1-686). script
log attached.
I'm TimRiker on irc.debian.org just FYI.
--
Tim Riker - http://Rikers.org/ - TimR@Debian.org
Embedded Linux Technologist - http://eLinux.org/
BZFlag maintainer - http://BZFlag.org/ - for fun!
[dhclient3bug.txt (text/plain, inline)]
Script started on Mon 13 Jun 2005 03:02:32 PM CDT
root@cn014a0868018l1:/etc/dhcp3# cat /etc/dhcp3/dhclient.conf
interface "eth0" {
send host-name "cn014a0868018l1-eth0";
}
interface "eth1" {
send host-name "cn014a0868018l1-eth1";
}
root@cn014a0868018l1:/etc/dhcp3# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:0F:97:C9:9E
inet6 addr: fe80::200:fff:fe97:c99e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:6453 errors:0 dropped:0 overruns:0 frame:0
TX packets:6737 errors:0 dropped:0 overruns:0 carrier:8
collisions:3 txqueuelen:1000
RX bytes:1902275 (1.8 MiB) TX bytes:1125008 (1.0 MiB)
Interrupt:11 Base address:0xec80
eth1 Link encap:Ethernet HWaddr 00:0B:FD:F8:B4:DA
inet6 addr: fe80::20b:fdff:fef8:b4da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:5 dropped:0 overruns:0 frame:5
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4754 (4.6 KiB) TX bytes:2946 (2.8 KiB)
Interrupt:3 Base address:0x100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:290 errors:0 dropped:0 overruns:0 frame:0
TX packets:290 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18333 (17.9 KiB) TX bytes:18333 (17.9 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wifi0 Link encap:UNSPEC HWaddr 00-0B-FD-F8-B4-DA-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:2312 Metric:1
RX packets:21 errors:5 dropped:0 overruns:0 frame:5
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:4754 (4.6 KiB) TX bytes:2946 (2.8 KiB)
Interrupt:3 Base address:0x100
root@cn014a0868018l1:/etc/dhcp3# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:00:0f:97:c9:9e
Sending on LPF/eth0/00:00:0f:97:c9:9e
Listening on LPF/eth1/00:0b:fd:f8:b4:da
Sending on LPF/eth1/00:0b:fd:f8:b4:da
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
root@cn014a0868018l1:/etc/dhcp3# dpkg -l dhcp3-client
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-========================================================================
ii dhcp3-client 3.0.1-2 DHCP Client
root@cn014a0868018l1:/etc/dhcp3#
Script done on Mon 13 Jun 2005 03:04:24 PM CDT
Information forwarded to debian-bugs-dist@lists.debian.org, peloy@debian.org (Eloy A. Paris):
Bug#270890; Package dhcp3-client.
(full text, mbox, link).
Acknowledgement sent to Andrew Pollock <apollock@debian.org>:
Extra info received and forwarded to list. Copy sent to peloy@debian.org (Eloy A. Paris).
(full text, mbox, link).
Message #22 received at 270890@bugs.debian.org (full text, mbox, reply):
On Mon, Jun 13, 2005 at 05:20:57PM -0500, Tim Riker wrote:
> I get the same results with a really small dhclient.conf. Note that my
> eth1 is a cisco wireless card (from kernel-image-2.6.10-1-686). script
> log attached.
Thanks for the log.
I've just tested this with 3.0.2, and it appears to be behaving as it
should. I added two entries to an otherwise empty dhclient.conf, and when I
ran dhclient on eth1, it used the hostname specified for eth1.
Could you possibly test the 3.0.2 package? (Note, this isn't exactly what
will be uploaded yet, I'm working my way through all the open bugs, looking
at fixing easy stuff)
If you add
deb http://people.debian.org/~apollock/dhcp3 ./
to your sources.list, you can pull the 3.0.2 packages.
regards
Andrew
Information forwarded to debian-bugs-dist@lists.debian.org, peloy@debian.org (Eloy A. Paris):
Bug#270890; Package dhcp3-client.
(full text, mbox, link).
Acknowledgement sent to Tim Riker <Tim@Rikers.org>:
Extra info received and forwarded to list. Copy sent to peloy@debian.org (Eloy A. Paris).
(full text, mbox, link).
Message #27 received at 270890@bugs.debian.org (full text, mbox, reply):
Andrew Pollock wrote:
> Could you possibly test the 3.0.2 package? (Note, this isn't exactly what
> will be uploaded yet, I'm working my way through all the open bugs, looking
> at fixing easy stuff)
Tested with same incorrect result. Both eth0 and eth1 are started. Have
you tested on a machine with with ipv6 running and a sit0 interface?
Perhaps it's the cisco which lists the wifi0 interface?
Sorry this is so tough to track down. I'm in process of moving so I
don't have the time at present to dig into the source. =/
--
Tim Riker - http://Rikers.org/ - TimR@Debian.org
Embedded Linux Technologist - http://eLinux.org/
BZFlag maintainer - http://BZFlag.org/ - for fun!
Changed Bug title.
Request was from Andrew Pollock <apollock@andrew.net.au>
to control@bugs.debian.org.
(full text, mbox, link).
Tags added: confirmed
Request was from Andrew Pollock <apollock@andrew.net.au>
to control@bugs.debian.org.
(full text, mbox, link).
Reply sent to Andrew Pollock <apollock@debian.org>:
You have marked Bug as forwarded.
(full text, mbox, link).
Message #34 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi,
One of our users has reported a problem whereby when he specifically
mentions interfaces in his dhclient.conf file, and then later runs
dhclient on a specific interface, dhclient actually tries to send
requests out all interfaces.
The scenario in this case is interface-specific hostnames are required
to be sent in the DHCP requests.
I have confirmed this behavior with 3.0.2.
A full log of the correspondence is at http://bugs.debian.org/270890
Is this intended behavior, or is it a bug?
If you maintain the Cc to this email, all correspondence will be
captured in our bug tracking system.
regards
Andrew
On Thu, Sep 09, 2004 at 03:07:08PM -0500, Tim Riker wrote:
> Subject: dhcp3-client: bug
> Package: dhcp3-client
> Version: 3.0.1-1
> Severity: important
>
> debian kernel:
>
> root@cn014a0868018l1:~# uname -a
> Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686
> GNU/Linux
>
> kernel-image-2.6.8-1-686 2.6.8-2
>
> dhclient version:
>
> timr@cn014a0868018l1:~$ dhclient --help
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
>
> My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to
> specify a different hostname when making requests on each interface so I
> have:
>
> interface "eth0" {
> send host-name "cn014a0868018l1-eth0";
> }
>
> interface "eth1" {
> send host-name "cn014a0868018l1-eth1";
> }
>
> in my /etc/dhcp3/dhclient.conf
>
> If I leave these enabled and run:
>
> root@cn014a0868018l1:~# dhclient eth1
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/products/DHCP
>
> wifi0: unknown hardware address type 801
> sit0: unknown hardware address type 776
> wifi0: unknown hardware address type 801
> sit0: unknown hardware address type 776
> Listening on LPF/eth0/00:08:74:97:c9:9e
> Sending on LPF/eth0/00:08:74:97:c9:9e
> Listening on LPF/eth1/00:0b:fd:f8:b4:da
> Sending on LPF/eth1/00:0b:fd:f8:b4:da
> Sending on Socket/fallback
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
> DHCPOFFER from 156.117.114.4
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPACK from 156.117.114.3
> bound to 156.117.114.96 -- renewal in 140123 seconds.
>
> So dhclient is requesting eth0 even though I gave it eth1 on the command
> line. If I remove the interface sections it behaves as expected. The man
> page for dhclient.conf states that only matching interface configuration
> will be used.
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.8-1-686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages dhcp3-client depends on:
> ii debconf 1.4.30 Debian configuration management sy
> ii debianutils 2.8.4 Miscellaneous utilities specific t
> ii dhcp3-common 3.0.1-1 Common files used by all the dhcp3
> ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
> --
> Tim Riker - http://rikers.org/ - TimR@Debian.org
> Linux Technologist - Tim@TI.com - http://www.TI.com/
> BZFlag maintainer - http://BZFlag.org/ - for fun!
>
>
[signature.asc (application/pgp-signature, inline)]
Message #35 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
On Tue, Jun 14, 2005 at 04:09:50PM +1000, Andrew Pollock wrote:
> One of our users has reported a problem whereby when he specifically
> mentions interfaces in his dhclient.conf file, and then later runs
> dhclient on a specific interface, dhclient actually tries to send
> requests out all interfaces.
>
> The scenario in this case is interface-specific hostnames are required
> to be sent in the DHCP requests.
>
> I have confirmed this behavior with 3.0.2.
>
> A full log of the correspondence is at http://bugs.debian.org/270890
>
> Is this intended behavior, or is it a bug?
It is an intended behaviour. The user (via the configuration file)
is informing the client of an interface it expects to use. I think
it may be possible with the current implementation that interfaces
added from config can be distinguished from interfaces added by
command line, and adjustments made, but this is a change in behaviour
and fairly hairy to boot, so is best dealt with in a feature release.
What's happening is that dhclient only tracks one list of interfaces.
Interfaces added to this list by being mentioned in the config is
not distinguished from interfaces added to the list from the command
line. It's hard to tell what a user would want here anyway, since
they are entering configuration for the interface, and presumably the
interface does indeed exist.
A common workaround is to use different dhclient.conf files for each
interface you wish to configure with separate dhclient daemons. If
somehow you need to only sometimes use separate daemons and sometimes
use one unified daemon, you can use a third config file which merely
includes the other two.
A similar problem exists in that the way dhclient/dhcpd/dhcrelay
relate to these interfaces is decided only at compile time - you
cannot choose to use berkeley sockets, raw interfaces, or etc at
config time.
I hope someday to solve both issues at the same time - by allowing
a set of configuration syntax to relate the way in which the various
daemons interact with the network. This includes segregating yet
another related issue, choosing what interfaces the daemon should
'receive' and 'transmit' upon (a common complaint of dhcrelay when
it shares a broadcast domain with its parent dhcp server).
--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
Message #36 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
On Jun 13, 2005, at 11:09 PM, Andrew Pollock wrote:
> Is this intended behavior, or is it a bug?
>
It's a bug. That code is complicated by the fact that it has to
work for both the client and server - if you're doing a client-only
package, you might want to just hack it to death so that it makes
more sense from the perspective of a DHCP client.
Message #37 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
From the man page:
interface "name" { declarations ... }
A client with more than one network interface may require different
behaviour depending on which interface is being configured. All timing
parameters and declarations other than lease and alias declarations can
be enclosed in an interface declaration, and those parameters will then
be used only for the interface that matches the specified name.
Interfaces for which there is no interface declaration will use the
parameters declared outside of any interface declaration, or the default
settings.
note the text "those parameters will then be used only for the interface
that matches the specified name."
I read this to mean that since I only told it to bring up eth1 (on the
command line) that the section for eth0 would be ignored. There is no
text in the description that states that the command line interface list
will be ignored or merged with any interface sections in the config.
There is nothing that states that adding an interface section is just
like adding the interface on the command line. Things like the alias
code lead me to this understanding.
David W. Hankins wrote:
> It is an intended behaviour. The user (via the configuration file)
> is informing the client of an interface it expects to use.
Not at all what I intended. I added configuration parameters for an
interface that I might tell it to use.
I tried to use this config on a laptop which sometimes uses eth0 (wired)
and sometimes eth1 (wifi).
dhclient3 gets called from "ifup" and "ifdown" on debian, and there is
no method that I am aware of to pass different config files based on the
interface in use.
I can see your view on this completely. If this is the intended
behaviour then the man pages should be updated to reflect that.
Thanx for the reply!
--
Tim Riker - http://Rikers.org/ - TimR@Debian.org
Embedded Linux Technologist - http://eLinux.org/
BZFlag maintainer - http://BZFlag.org/ - for fun!
Message #38 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
On Tue, Jun 14, 2005 at 01:17:16PM -0500, Tim Riker wrote:
> note the text "those parameters will then be used only for the interface
> that matches the specified name."
>
> I read this to mean that since I only told it to bring up eth1 (on the
> command line) that the section for eth0 would be ignored. There is no
That's not the intended meaning of the documentation. 'specified name'
refers to the name specified in the interface declaration in question.
Parameters within the interface declaration will be applied only to
the interface of the specified name...
It says nothing about the selection of interfaces to use based on either
commad line or configuration file inputs.
> There is nothing that states that adding an interface section is just
> like adding the interface on the command line. Things like the alias
> code lead me to this understanding.
I agree, this area is not well documented.
> I can see your view on this completely. If this is the intended
> behaviour then the man pages should be updated to reflect that.
I'll see what I can do to clarify it.
--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
Message #39 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
Ted Lemon wrote:
> On Jun 13, 2005, at 11:09 PM, Andrew Pollock wrote:
>
>> Is this intended behavior, or is it a bug?
>>
> It's a bug. That code is complicated by the fact that it has to work
> for both the client and server - if you're doing a client-only package,
> you might want to just hack it to death so that it makes more sense
> from the perspective of a DHCP client.
David W. Hankins wrote:
> On Tue, Jun 14, 2005 at 01:17:16PM -0500, Tim Riker wrote:
>>note the text "those parameters will then be used only for the interface
>>that matches the specified name."
>>
>>I read this to mean that since I only told it to bring up eth1 (on the
>>command line) that the section for eth0 would be ignored. There is no
>
> That's not the intended meaning of the documentation. 'specified name'
> refers to the name specified in the interface declaration in question.
Seems David and Ted don't agree on this?
> Parameters within the interface declaration will be applied only to
> the interface of the specified name...
agreed. that much is clear.
> It says nothing about the selection of interfaces to use based on either
> commad line or configuration file inputs.
More specifically, is says nothing about the interfaces in the config
actually selecting those interfaces. The dhclient man page does say that
the one(s) listed on the command line will be selected.
>>There is nothing that states that adding an interface section is just
>>like adding the interface on the command line. Things like the alias
>>code lead me to this understanding.
>
> I agree, this area is not well documented.
>
>>I can see your view on this completely. If this is the intended
>>behaviour then the man pages should be updated to reflect that.
>
> I'll see what I can do to clarify it.
Perhaps folks should agree on how it should work first? Agreed, though,
the docs and implementation should match. Either way the docs should
state the expected behavior.
Again, thanx! None of this is intended as a dig. I use and appreciate
dhclient and dhcpd.
--
Tim Riker - http://Rikers.org/ - TimR@Debian.org
Embedded Linux Technologist - http://eLinux.org/
BZFlag maintainer - http://BZFlag.org/ - for fun!
Message #40 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
Just to be clear, the way I think it should work is this:
* If you specify no interfaces in the config file or on the
command line, you get all interfaces on which DHCP makes sense
(generally speaking, all broadcast interfaces).
* If you specify interfaces in the config, and no interfaces on
the command line, you get the interfaces you specified in the
config, and no others.
* If you specify one or more interfaces on the command line, you
get only those interfaces, regardless of what it says in the
config file.
I consider it a bug that it doesn't currently work this way. However,
as I say, David is the authority here, not me.
Message #41 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
On Tue, Jun 14, 2005 at 12:43:09PM -0700, Ted Lemon wrote:
> Just to be clear, the way I think it should work is this:
I'll agree and add to this the other modifications I've suggested;
> * If you specify no interfaces in the config file or on the
> command line, you get all interfaces on which DHCP makes sense
> (generally speaking, all broadcast interfaces).
And they use a network I/O method that will result in RFC2131
compliance (notoriously in regard to broadcast address), or what
is available, whatever that means for the build environment.
> * If you specify interfaces in the config, and no interfaces on
> the command line, you get the interfaces you specified in the
> config, and no others.
>
> * If you specify one or more interfaces on the command line, you
> get only those interfaces, regardless of what it says in the
> config file.
If a network I/O method is specified in config, it is used,
otherwise the default is again the best method available to
acheive RFC2131 compliance.
It's plainly visible at this point that part of my reason for eliding
this to a feature release is combining effort. This is much easier to
do if you're already planning on making sweeping changes to related
sources.
> I consider it a bug that it doesn't currently work this way. However,
> as I say, David is the authority here, not me.
But I also can't speak for what was intended when it was written,
Ted is often the authority there, and more often than not I'm just
guessing.
Again in the interests of being clear, I agree that this is not the
desired behaviour, but I do not presently believe that this is
appropriate to address in a maintenance release.
For better or worse, this 'undesirable feature', and we do have a
few others, is it's current behaviour, and it's possible that it
may be relied upon.
People allow us to amaze them when behaviours change between feature
releases, and scripts or methodologies they devised for them break.
People are not so forgiving with maintenance releases, particularly
for features/behaviours that have been in the released software for
a nontrivial number of years.
The exception is the severity of the problem - security, crash bugs,
protocol violations...
As always, I'm open to arguments to the contrary, but the last time
dhcp-server spoke about this no one objected, to my memory.
--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
Message #42 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
On Jun 14, 2005, at 1:59 PM, David W. Hankins wrote:
> But I also can't speak for what was intended when it was written,
> Ted is often the authority there, and more often than not I'm just
> guessing.
I imagine this being said in a somewhat bewildered tone of voice,
after hours of trying to figure out what that code is supposed to
do. :')
> Again in the interests of being clear, I agree that this is not the
> desired behaviour, but I do not presently believe that this is
> appropriate to address in a maintenance release.
Can't argue with that.
Tags removed: moreinfo
Request was from Andrew Pollock <apollock@debian.org>
to control@bugs.debian.org.
(full text, mbox, link).
Acknowledgement sent to Andrew Pollock <apollock@debian.org>:
Extra info received and filed, but not forwarded.
(full text, mbox, link).
Message #49 received at 270890-quiet@bugs.debian.org (full text, mbox, reply):
So, in short, upstream agree that this is a bug, however the behaviour will
not be changed in maintenance releases (so 3.0.x), but in a future feature
release (so 3.1.x).
Message #50 received at 270890-forwarded@bugs.debian.org (full text, mbox, reply):
Hello,
This bug was received some time ago, and I forwarded it on to
dhcp-hackers, because I wasn't aware of dhcp-bugs at the time.
There was a fairly lengthy discourse between Ted Lemon and David Hankins on
this particular bug, all of which is captured at http://bugs.debian.org/270890
My understanding is that it was to be left for a new feature release of DHCP.
I'm reforwarding it as an upstream bug so it gets tracked properly.
Please maintain the Cc on correspondence to keep our bug tracking system
in the loop.
regards
Andrew
----- Forwarded message from Tim Riker <Tim@Rikers.org> -----
Subject: Bug#270890: dhclient 3 starts eth0 when given eth1 on command line
Reply-To: Tim Riker <Tim@Rikers.org>, 270890@bugs.debian.org
Resent-From: Tim Riker <Tim@Rikers.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: peloy@debian.org (Eloy A. Paris)
Resent-Date: Thu, 09 Sep 2004 20:18:01 UTC
Resent-Message-ID: <handler.270890.B.109476057323610@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 270890
X-Debian-PR-Package: dhcp3-client
X-Debian-PR-Keywords:
From: Tim Riker <Tim@Rikers.org>
To: dhcp-bugs@isc.org, Debian Bug Tracking System <submit@bugs.debian.org>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Subject: dhcp3-client: bug
Package: dhcp3-client
Version: 3.0.1-1
Severity: important
debian kernel:
root@cn014a0868018l1:~# uname -a
Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686
GNU/Linux
kernel-image-2.6.8-1-686 2.6.8-2
dhclient version:
timr@cn014a0868018l1:~$ dhclient --help
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to
specify a different hostname when making requests on each interface so I
have:
interface "eth0" {
send host-name "cn014a0868018l1-eth0";
}
interface "eth1" {
send host-name "cn014a0868018l1-eth1";
}
in my /etc/dhcp3/dhclient.conf
If I leave these enabled and run:
root@cn014a0868018l1:~# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:08:74:97:c9:9e
Sending on LPF/eth0/00:08:74:97:c9:9e
Listening on LPF/eth1/00:0b:fd:f8:b4:da
Sending on LPF/eth1/00:0b:fd:f8:b4:da
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 156.117.114.4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 156.117.114.3
bound to 156.117.114.96 -- renewal in 140123 seconds.
So dhclient is requesting eth0 even though I gave it eth1 on the command
line. If I remove the interface sections it behaves as expected. The man
page for dhclient.conf states that only matching interface configuration
will be used.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dhcp3-client depends on:
ii debconf 1.4.30 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii dhcp3-common 3.0.1-1 Common files used by all the dhcp3
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
--
Tim Riker - http://rikers.org/ - TimR@Debian.org
Linux Technologist - Tim@TI.com - http://www.TI.com/
BZFlag maintainer - http://BZFlag.org/ - for fun!
----- End forwarded message -----
Forwarded-to-address changed from dhcp-hackers@isc.org to dhcp-bugs@isc.org.
Request was from Andrew Pollock <apollock@debian.org>
to control@bugs.debian.org.
(Tue, 15 Jan 2008 06:12:03 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian ISC DHCP maintainers <pkg-dhcp-devel@lists.alioth.debian.org>:
Bug#270890; Package dhcp3-client.
(Wed, 15 Oct 2014 04:21:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Mike <debian@good-with-numbers.com>:
Extra info received and forwarded to list. Copy sent to Debian ISC DHCP maintainers <pkg-dhcp-devel@lists.alioth.debian.org>.
(Wed, 15 Oct 2014 04:21:05 GMT) (full text, mbox, link).
Message #57 received at 270890@bugs.debian.org (full text, mbox, reply):
Was there a resolution to this bug? Because the behavior still seems to be
present according to the documentation in 4.2.2.dfsg.1-5+deb70u6, see
"Note well:" in dhclient.conf(5).
I don't see a public website of DHCP bugs where I could search for this.
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian ISC DHCP maintainers <pkg-dhcp-devel@lists.alioth.debian.org>:
Bug#270890; Package dhcp3-client.
(Wed, 15 Oct 2014 09:48:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Andrew Pollock <apollock@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian ISC DHCP maintainers <pkg-dhcp-devel@lists.alioth.debian.org>.
(Wed, 15 Oct 2014 09:48:04 GMT) (full text, mbox, link).
Message #62 received at 270890@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Wed, Oct 15, 2014 at 04:03:05AM +0000, Mike wrote:
> Was there a resolution to this bug? Because the behavior still seems to be
> present according to the documentation in 4.2.2.dfsg.1-5+deb70u6, see
> "Note well:" in dhclient.conf(5).
>
> I don't see a public website of DHCP bugs where I could search for this.
Yeah their RT instance isn't public. I just rummaged through my 2008 email
and found the ISC bug number for the forwarded bug (I've now captured it in
the BTS). They're usually pretty good about looping in our BTS on responses,
so this one may have gone unresponded upstream.
[signature.asc (application/pgp-signature, inline)]
Information stored
:
Bug#270890; Package dhcp3-client.
(Wed, 15 Oct 2014 09:48:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Andrew Pollock <apollock@debian.org>:
Extra info received and filed, but not forwarded.
(Wed, 15 Oct 2014 09:48:08 GMT) (full text, mbox, link).
Message #67 received at 270890-quiet@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
----- Forwarded message from DHCP Bugs via RT <dhcp-bugs@isc.org> -----
Date: Tue, 15 Jan 2008 05:16:05 +0000
From: DHCP Bugs via RT <dhcp-bugs@isc.org>
To: apollock@debian.org
Subject: [ISC-Bugs #17490] AutoReply: dhclient starts eth0 when given eth1 on command line
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"dhclient starts eth0 when given eth1 on command line",
a summary of which appears below.
There is no need to reply to this message right now. Your ticket has been
assigned an ID of [ISC-Bugs #17490].
Please include the string:
[ISC-Bugs #17490]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
Thank you,
dhcp-bugs@isc.org
-------------------------------------------------------------------------
Hello,
This bug was received some time ago, and I forwarded it on to
dhcp-hackers, because I wasn't aware of dhcp-bugs at the time.
There was a fairly lengthy discourse between Ted Lemon and David Hankins on
this particular bug, all of which is captured at http://bugs.debian.org/270890
My understanding is that it was to be left for a new feature release of DHCP.
I'm reforwarding it as an upstream bug so it gets tracked properly.
Please maintain the Cc on correspondence to keep our bug tracking system
in the loop.
regards
Andrew
----- Forwarded message from Tim Riker <Tim@Rikers.org> -----
Subject: Bug#270890: dhclient 3 starts eth0 when given eth1 on command line
Reply-To: Tim Riker <Tim@Rikers.org>, 270890@bugs.debian.org
Resent-From: Tim Riker <Tim@Rikers.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: peloy@debian.org (Eloy A. Paris)
Resent-Date: Thu, 09 Sep 2004 20:18:01 UTC
Resent-Message-ID: <handler.270890.B.109476057323610@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 270890
X-Debian-PR-Package: dhcp3-client
X-Debian-PR-Keywords:
From: Tim Riker <Tim@Rikers.org>
To: dhcp-bugs@isc.org, Debian Bug Tracking System <submit@bugs.debian.org>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Subject: dhcp3-client: bug
Package: dhcp3-client
Version: 3.0.1-1
Severity: important
debian kernel:
root@cn014a0868018l1:~# uname -a
Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686
GNU/Linux
kernel-image-2.6.8-1-686 2.6.8-2
dhclient version:
timr@cn014a0868018l1:~$ dhclient --help
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to
specify a different hostname when making requests on each interface so I
have:
interface "eth0" {
send host-name "cn014a0868018l1-eth0";
}
interface "eth1" {
send host-name "cn014a0868018l1-eth1";
}
in my /etc/dhcp3/dhclient.conf
If I leave these enabled and run:
root@cn014a0868018l1:~# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:08:74:97:c9:9e
Sending on LPF/eth0/00:08:74:97:c9:9e
Listening on LPF/eth1/00:0b:fd:f8:b4:da
Sending on LPF/eth1/00:0b:fd:f8:b4:da
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 156.117.114.4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 156.117.114.3
bound to 156.117.114.96 -- renewal in 140123 seconds.
So dhclient is requesting eth0 even though I gave it eth1 on the command
line. If I remove the interface sections it behaves as expected. The man
page for dhclient.conf states that only matching interface configuration
will be used.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dhcp3-client depends on:
ii debconf 1.4.30 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii dhcp3-common 3.0.1-1 Common files used by all the dhcp3
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
--
Tim Riker - http://rikers.org/ - TimR@Debian.org
Linux Technologist - Tim@TI.com - http://www.TI.com/
BZFlag maintainer - http://BZFlag.org/ - for fun!
----- End forwarded message -----
----- End forwarded message -----
[signature.asc (application/pgp-signature, inline)]
No longer marked as found in versions 3.0.1-1.
Request was from Michael Gilbert <mgilbert@debian.org>
to control@bugs.debian.org.
(Sat, 05 Sep 2015 20:48:22 GMT) (full text, mbox, link).
Reply sent
to Michael Gilbert <mgilbert@debian.org>:
You have taken responsibility.
(Sat, 14 Jan 2017 23:21:08 GMT) (full text, mbox, link).
Notification sent
to Tim Riker <Tim@Rikers.org>:
Bug acknowledged by developer.
(Sat, 14 Jan 2017 23:21:08 GMT) (full text, mbox, link).
Message #76 received at 270890-close@bugs.debian.org (full text, mbox, reply):
Upstream intends this to be correct behavior, and updated
documentation to reflect that.
Best wishes,
Mike
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sun, 12 Feb 2017 07:37:59 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Mar 9 06:41:17 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.