Your message dated Tue, 14 Jun 2005 16:09:50 +1000
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #270890,
regarding dhcp3-client: starts all interfaces specified in dhclient.conf
regardless of command-line parameters
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---------------------------------------
Received: (at 270890-forwarded) by bugs.debian.org; 14 Jun 2005 06:10:11 +0000
>From [EMAIL PROTECTED] Mon Jun 13 23:10:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-202-45-98-132.act.netspace.net.au (caesar.andrew.net.au)
[202.45.98.132]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Di4cj-0007JY-00; Mon, 13 Jun 2005 23:10:10 -0700
Received: from localhost.localdomain ([172.16.1.13])
by caesar.andrew.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id
j5E6A66q022375
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
Tue, 14 Jun 2005 16:10:06 +1000
Received: from apollock by localhost.localdomain with local (Exim 4.50)
id 1Di4cQ-0002RW-5x; Tue, 14 Jun 2005 16:09:50 +1000
Date: Tue, 14 Jun 2005 16:09:50 +1000
From: Andrew Pollock <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Tim Riker <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: dhclient starts on all interfaces referred to in dhclient.conf
regardless of command-line parameters
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
X-Scanned-By: MIMEDefang 2.51 on 172.16.1.1
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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
>=20
> debian kernel:
>=20
> [EMAIL PROTECTED]:~# uname -a
> Linux cn014a0868018l1 2.6.8-1-686 #1 Sat Aug 28 14:11:39 EDT 2004 i686=20
> GNU/Linux
>=20
> kernel-image-2.6.8-1-686 2.6.8-2
>=20
> dhclient version:
>=20
> [EMAIL PROTECTED]:~$ dhclient --help
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
>=20
> My host has both wifi (eth1) and 100bT (eth0) interfaces. I need to=20
> specify a different hostname when making requests on each interface so I=
=20
> have:
>=20
> interface "eth0" {
> send host-name "cn014a0868018l1-eth0";
> }
>=20
> interface "eth1" {
> send host-name "cn014a0868018l1-eth1";
> }
>=20
> in my /etc/dhcp3/dhclient.conf
>=20
> If I leave these enabled and run:
>=20
> [EMAIL PROTECTED]:~# 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
>=20
> 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.
>=20
> So dhclient is requesting eth0 even though I gave it eth1 on the command=
=20
> line. If I remove the interface sections it behaves as expected. The man=
=20
> page for dhclient.conf states that only matching interface configuration=
=20
> will be used.
>=20
> -- 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=3DC, LC_CTYPE=3DC
>=20
> 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
> --=20
> Tim Riker - http://rikers.org/ - [EMAIL PROTECTED]
> Linux Technologist - [EMAIL PROTECTED] - http://www.TI.com/
> BZFlag maintainer - http://BZFlag.org/ - for fun!
>=20
>=20
--Nq2Wo0NMKNjxTN9z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCrnSuIblXXKfZFgIRAtKGAJ0SkPSa+fSsnsW+4Kw00hosnf/HdwCg1aaX
OpduBqY1TPzUuRFtTCBPFbM=
=8qpW
-----END PGP SIGNATURE-----
--Nq2Wo0NMKNjxTN9z--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
