Date: Mon, 30 Jul 2007 16:38:03 -0400 From: Chuck Swiger <cswiger@mac.com> To: "Jasvinder S. Bahra" <bbdl21548@blueyonder.co.uk> Cc: FreeBSD-questions List <freebsd-questions@freebsd.org> Subject: Re: Binding dhclient to a particular network interface Message-ID: <46AE4C2B.2040603@mac.com> In-Reply-To: <000401c7d2e6$2bdaf770$0600010a@atlantis> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46AE4C2B.2040603>