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!
> 
> 

-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCrnSuIblXXKfZFgIRAtKGAJ0SkPSa+fSsnsW+4Kw00hosnf/HdwCg1aaX
OpduBqY1TPzUuRFtTCBPFbM=
=8qpW
-----END PGP SIGNATURE-----