Re: Design misfeature of dhclient for multiple interfaces

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Thu, 11 Sep 2008 07:21:57 +1000
Daniel Carosone <dan%geek.com.au@localhost> wrote:

> On Tue, Sep 09, 2008 at 11:46:41AM -0400, Steven M. Bellovin wrote:
> > I think there are several separate issues.  One is fail-over, which
> > is indeed important.  A second is what to do when there are multiple
> > interfaces, which has several aspects: which has priority, when are
> > leases negotiated, how is auxiliary data bound to the current
> > default route, etc.  My current failure is with this last point,
> > though (as has been noted) I'm still grasping for a solution to all
> > of them.
> 
> The cheesy approach might work; it's not suitable for all
> requirements, but does pretty well for the common case: disable
> wireless when there's a wired connection.  Some ifwatchd scripts
> should deal with that, including making dhcp release and renew leases
> after a change (so the right *.conf contents are left at the end).
> 
I don't think we're very far from what we really need, at least for
simple cases; as best I can tell, Ubuntu does much more of the right
thing (again, for simple cases) with ISC dhclient.


                --Steve Bellovin, http://www.cs.columbia.edu/~smb