From owner-freebsd-questions@FreeBSD.ORG Mon Jul 30 22:00:59 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50E5316A53B for ; Mon, 30 Jul 2007 22:00:59 +0000 (UTC) (envelope-from bbdl21548@blueyonder.co.uk) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.freebsd.org (Postfix) with ESMTP id E720813C465 for ; Mon, 30 Jul 2007 22:00:58 +0000 (UTC) (envelope-from bbdl21548@blueyonder.co.uk) Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1IFdIP-0006yk-Uy for freebsd-questions@freebsd.org; Mon, 30 Jul 2007 23:00:57 +0100 Received: from [82.37.197.203] (helo=atlantis) by asmtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1IFdIO-0006ox-Ry for freebsd-questions@freebsd.org; Mon, 30 Jul 2007 23:00:57 +0100 Message-ID: <000401c7d2f5$0ddbd640$0600010a@atlantis> From: "Jasvinder S. Bahra" To: References: <002301c7d10a$09ee5180$0600010a@atlantis> <46ACF835.7040402@crackmonkey.us> <000601c7d238$065da370$0600010a@atlantis> <001101c7d23e$ea6e2200$bf4a6600$@com> <001901c7d2da$1cc36760$0600010a@atlantis> <46AE3B2A.4050306@mac.com> <000401c7d2e6$2bdaf770$0600010a@atlantis> <46AE4C2B.2040603@mac.com> Date: Mon, 30 Jul 2007 22:59:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Re: Binding dhclient to a particular network interface X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2007 22:00:59 -0000 Chuck, Oddly enough, after the system has finished starting up, running "dhclient ed1" on the command line does work (though "sockstat -l4" still shows local address as "*:68"). I could I have sworn that when I tried doing this the first time I added the dhclient_flags line, it failed. One thing I noticed as the system was starting up (after adding the dhclient_flags entry into /etc/rc.conf), was that dhclient completed too quickly. Normally when dhclient runs, it usually takes several seconds to do its thing (i.e... a noticeable delay between the "Starting dhclient" message appearing and the message immediately after it), however there was no delay between the appearance of the two messages - dhclient fails instantly. I doubt its relevant, but keep in mind this is a very old machine - an Intel Pentium 120MHz, 48MB RAM equipped with two ISA network cards, running FreeBSD 5.5. I'm afraid I cant run the command you suggested on the DHCP server, as the DHCP server in this case is built into the cable modem (to which I do not have shell access, if it even provides such). As for sticking a switch in between and connecting an a third PC to monitor - i'd prefer to leave that as a last resort for the time being as finding and setting up the additional hardware will be a bit of a pain. If you (or indeed anyone else) has any other suggestions, please do share. Thanks, Jazz ----- Original Message ----- From: "Chuck Swiger" To: "Jasvinder S. Bahra" Cc: "FreeBSD-questions List" Sent: Monday, July 30, 2007 9:38 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > Chuck, > > > > I gave this a shot, but this stopped the interface being assigned an IP > > address at all (i.e... before the change, the interface had a valid IP > > address assigned by the DHCP server in my cable modem, but after making the > > change and restarting, the "ifconfig" command shows the interface having an > > IP address of 0.0.0.0). > > > > I do agree though - the man page explicitly says that this should work. > > Does running "dhclient ed1" from the command line work? > Is the DHCP server providing the right answer? > > Running "tcpdump -s 0 arp or port bootps" would give you insight into what the > network is seeing, at least. Doing this from your DHCP server or a laptop on > a hub with the interface in question would be useful vantages, or a "trunk" or > "span" port on a smart switch, depending on what you might have handy. > > -- > -Chuck