From owner-freebsd-questions@FreeBSD.ORG Mon Jul 30 20:14:26 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 7BAB016A419 for ; Mon, 30 Jul 2007 20:14:26 +0000 (UTC) (envelope-from bbdl21548@blueyonder.co.uk) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.freebsd.org (Postfix) with ESMTP id 1C6D513C467 for ; Mon, 30 Jul 2007 20:14:26 +0000 (UTC) (envelope-from bbdl21548@blueyonder.co.uk) Received: from [172.23.170.147] (helo=anti-virus03-10) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1IFbdI-00086h-OZ for freebsd-questions@freebsd.org; Mon, 30 Jul 2007 21:14:24 +0100 Received: from [82.37.197.203] (helo=atlantis) by asmtp-out1.blueyonder.co.uk with smtp (Exim 4.52) id 1IFbdI-0005J8-81 for freebsd-questions@freebsd.org; Mon, 30 Jul 2007 21:14:24 +0100 Message-ID: <000401c7d2e6$2bdaf770$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> Date: Mon, 30 Jul 2007 21:14:02 +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 20:14:26 -0000 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. Oh, and i'm absolutely sure that the interface is configured to use DHCP. i.e... ------ /etc/rc.conf snippet ------------------- network_interfaces="ed1 ed2 lo0" ifconfig_ed1="DHCP" ifconfig_ed2="inet 10.1.0.1 netmask 255.255.255.0" ifconfig_lo0="inet 127.0.0.1" ---------------------------------------------- I added the dhclient_flags line you suggested, after the ifconfig_lo0 line shown above, though as far as I know the order does not matter. Thanks for the suggestion though. Anyone have anymore ideas? Regards, Jazz ----- Original Message ----- From: "Chuck Swiger" To: "Jasvinder S. Bahra" Cc: Sent: Monday, July 30, 2007 8:25 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > Terry, > > > > I tried adding the interface line to the dhclient configuration file (and > > then rebooting), but it had no effect. Entering the "sockstat -l4" command > > showed that local address was still "*:68". > > "man dhclient" suggests that the interface needs to be specified on the > command line. Try adding: > > dhclient_flags="ed1" > > ...to /etc/rc.conf, and double-check that you already have that interface > configured to use DHCP while you're there. :-) > > Regards, > -- > -Chuck