Your message dated Tue, 13 Sep 2005 21:27:17 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#325865: dhcp3-client: static ip not working
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(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 submit) by bugs.debian.org; 31 Aug 2005 12:01:36 +0000
>From [EMAIL PROTECTED] Wed Aug 31 05:01:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (localhost.localdomain) [193.146.157.2] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EARHc-0002u2-00; Wed, 31 Aug 2005 05:01:36 -0700
Received: from ghe by localhost.localdomain with local (Exim 4.52)
        id 1EARH8-0004HV-7S; Wed, 31 Aug 2005 14:01:06 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ghe rivero <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: dhcp3-client: static ip not working
X-Mailer: reportbug 3.17
Date: Wed, 31 Aug 2005 14:01:06 +0200
Message-Id: <[EMAIL PROTECTED]>
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-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: dhcp3-client
Version: 3.0.3-2
Severity: normal


The dhcp server is a Cisco switch. Some servers have "static" ip given
by a dhcp server (based on mac). 

When asking for such ip, if retrieves another and not the assigened one.
With Windows and RedHat System, everything works properly.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages dhcp3-client depends on:
ii  debconf                       1.4.58     Debian configuration management sy
ii  debianutils                   2.14.2     Miscellaneous utilities specific t
ii  dhcp3-common                  3.0.3-2    Common files used by all the dhcp3
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an

dhcp3-client recommends no packages.

-- no debconf information

---------------------------------------
Received: (at 325865-done) by bugs.debian.org; 13 Sep 2005 11:26:24 +0000
>From [EMAIL PROTECTED] Tue Sep 13 04:26:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-202-45-99-131.act.netspace.net.au (caesar.andrew.net.au) 
[202.45.99.131] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EF8vf-0004vQ-00; Tue, 13 Sep 2005 04:26:24 -0700
Received: from caesar.andrew.net.au (localhost [127.0.0.1])
        by caesar.andrew.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id 
j8DBRJNm014624
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
        Tue, 13 Sep 2005 21:27:19 +1000
Received: (from [EMAIL PROTECTED])
        by caesar.andrew.net.au (8.13.4/8.13.4/Submit) id j8DBRHGa014623;
        Tue, 13 Sep 2005 21:27:17 +1000
Date: Tue, 13 Sep 2005 21:27:17 +1000
From: Andrew Pollock <[EMAIL PROTECTED]>
To: Andrew Pollock <[EMAIL PROTECTED]>
Cc: Ghe Rivero <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#325865: dhcp3-client: static ip not working
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL 
PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
X-Scanned-By: MIMEDefang 2.51 on 172.16.0.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-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Hi again,

On Sat, Sep 03, 2005 at 03:48:31PM +1000, Andrew Pollock wrote:
> 
> Hi again,
> 
> So I've had a bit of a read up on the "dhcp-client-identifier" attribute,
> and it appears that you can use this as an alternative to client MAC address
> to identify clients. It sounds to me like this is how your DHCP server is
> configured - it's not actually interested in the MAC address.
> 
> If you could mail me a dhclient.conf from a SuSE or RedHat box that works,
> I'd be interested to see how you have these configured. I can't imagine that
> either distribution is putting something unique and useful in an
> out-of-the-box configuration file.

I'd really like to see one of these dhclient.conf files from another
distribution if possible.
 
> If it's okay with you, I'd like to close this bug, as I don't think it's a
> problem with the software's functionality, it's a configuration issue.

I'm going to go ahead and close this bug.

regards

Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to