From owner-freebsd-current@FreeBSD.ORG  Tue Jul 29 07:25:17 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C62F937B401
	for <current@freebsd.org>; Tue, 29 Jul 2003 07:25:17 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1843543F75
	for <current@freebsd.org>; Tue, 29 Jul 2003 07:25:17 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h6TEONai075362;
	Tue, 29 Jul 2003 10:24:23 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)h6TEONYx075359;
	Tue, 29 Jul 2003 10:24:23 -0400 (EDT)
Date: Tue, 29 Jul 2003 10:24:23 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Terry Lambert <tlambert2@mindspring.com>
In-Reply-To: <3F262E1E.9936E5D7@mindspring.com>
Message-ID: <Pine.NEB.3.96L.1030729102329.75304D-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Martin Blapp <mb@imp.ch>
cc: current@freebsd.org
Subject: Re: STEP 2, fixing dhclient behaviour with multiple interfaces
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:25:18 -0000


On Tue, 29 Jul 2003, Terry Lambert wrote:

> Martin Blapp wrote:
> > I't is my goal to make dhclient really functional, so it can not only
> > be used with one interface, but several.
> > 
> > On a well known OS this works just fine. A first interface gets
> > initialized and the GW gets set as usual. But if a second interface
> > gets added, and the first one is still active and has a working lease,
> > the GW will not be overwriten. If you remove now the first interface,
> > the default GW changes to the one of the second interface.
> [ ... ]
> > If there are other ideas, I'm open to them.
> 
> You could add kevents for interface arrival and departure, and add a
> kqueue to the dhcpd to catch the arrival/departure events, and then just
> act on them. 

Some of those events already exist for routing sockets, so in a worst case
scenario, you can hook up a routing socket to a kqueue :-).

Martin -- you might want to try the "route monitor" command sometime and
take a look at the vent stream there for things to consider.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories