Binding dhclient to a particular network interface
Jasvinder S. Bahra
bbdl21548 at blueyonder.co.uk
Mon Jul 30 18:26:08 UTC 2007
No problem *smiles*. I'm at the same limit myself after all, and I do
appreciate you stepping forward with your suggestions.
----- Original Message -----
From: "Adam J Richardson" <fatman.uk at gmail.com>
To: "Jasvinder S. Bahra" <bbdl21548 at blueyonder.co.uk>
Cc: <freebsd-questions at freebsd.org>
Sent: Monday, July 30, 2007 1:02 AM
Subject: Re: Binding dhclient to a particular network interface
> > The DHCP reference for ed1 means dhclient is started (thereafter running
> > continuously as a daemon), which sets ed1's IP address to that assigned
> > the cable modem.
> > Note that dhclient generally runs as a daemon because it has to handle
> > renewals and/or expiration. I have no issues with it running as a
> Oh, interesting. I had assumed the interface called dhclient itself if
> the lease expired, or something.
> > As you can see, local address is listed as "*:68", which means its
> > on port 68 on all interfaces. I want to instruct dhclient to only
> > my cable-modem facing network card. If this were the case, issuing the
> > "sockstat -l4" command would return as above, but with local address
> > "<<CABLE-MODEM-ASSIGNED-IP-ADDRESS>>:68" (where
> > <<CABLE-MODEM-ASSIGNED-IP-ADDRESS>> is, unsurprisingly, the IP address
> > assigned to the network card by the DHCP server in the cable modem).
> Is there a dhclient.conf somewhere in your /etc? That would surely hold
> the answer. Possibly editing /etc/rc.d/dhclient or /etc/netstart might
> help? I'm at the edge of my FreeBSD knowledge and in danger of falling
> off, so I'll stop with the suggestions now. :)
> Adam J Richardson
More information about the freebsd-questions