From owner-freebsd-current@FreeBSD.ORG Wed Jul 30 06:50:09 2003 Return-Path: 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 1513F37B404 for ; Wed, 30 Jul 2003 06:50:09 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BAF443FCB for ; Wed, 30 Jul 2003 06:50:08 -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 h6UDnAai090672; Wed, 30 Jul 2003 09:49:10 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h6UDn8j9090669; Wed, 30 Jul 2003 09:49:08 -0400 (EDT) Date: Wed, 30 Jul 2003 09:49:08 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Terry Lambert In-Reply-To: <3F275AB9.C7614E22@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Martin Blapp 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2003 13:50:09 -0000 On Tue, 29 Jul 2003, Terry Lambert wrote: > This is part of the problem. The other parts are that this is really > networking code, and should be a separate thing, if possible, and, as > Martin just pointed out, the OMAPI stuff is not really cooked yet. Hence the notion of a neteventd -- I don't really mind what container it's in, as long as its structured around the network-centric pieces. > It's really a lot easier the process a small list of events in dhacpd as > a result of a kqueue or kqueue/select combo, if you want to avoid > rewriting as much code as humanly possible, and still be able to pull > this feature out of the project. Absolutely agreed. If OMAPI is working well, that may well provide a lot of what we want. One benefit to central management of the network configuration would be that we'd get things like GUI control and profiles a lot more easily. > I still haven't been able to repeat your test; are you sure you are > listening on a routing socket for the configuration change events? > Maybe I'm doing something silly with my dumb little test program that > you aren't doing with yours? I'm not seeing my Linksys my 3COM > interfaces showing up and disappearing as kevents, but they are > definitely still being seen by the laptop. Maybe it's my local hacks to > make it work at all (it's an older Sony VAIO PCG-XG29). I can't speak to your configuration, but I can describe mine :-). I've tested two different situations with "route monitor" creation and removal of virtual interfaces (in this case, vlan interfaces), and physical interfaces (in this case, my wi0 card in my notebook). Both appear to be generating proper notifications during arrival and departure. The only events that I expected to see, but didn't, were IPv6 link layer address arrival and departure. I ran these tests with 5.0-CURRENT from around July 3, but I seem to recall seeing this work properly previously. I don't have any RELENG_4 boxes with removable physical interfaces at this point. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories