From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 09:28:24 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 A5E7037B401; Tue, 29 Jul 2003 09:28:24 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id F193743F3F; Tue, 29 Jul 2003 09:28:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfk39.dialup.mindspring.com ([165.247.208.105] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19hXKn-0002Bw-00; Tue, 29 Jul 2003 09:28:22 -0700 Message-ID: <3F26A06C.D1E66484@mindspring.com> Date: Tue, 29 Jul 2003 09:27:24 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4371d5244c74fbb498c3ba05e41cefd95350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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: Tue, 29 Jul 2003 16:28:25 -0000 Robert Watson wrote: > > [ ... ] > > > 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. Does that work if you don't have an IP address assigned to the interface at all yet? I was under the impression that it only sent out route change events (maybe I need to update my copy of the -current sources, though). What I was talking about is the idea that naked interface (0.0.0.0) arrivals and departures could be signalled, which would cause dhclient to try to get a lease on the interface. I'm afraid there's still a chicken-and-egg problem over devices that you want to be able to come and go, without attempting to get a lease. Probably the way to handle them is with an explicit "not this device" list, since it would let unknown devices "just work" by default, which is kind of what you want. Presumably, if you don't want a lease it's because you've got a static assignment for that particular device that you want used instead. I can't wait for IPv6 stateless autoconfiguration plus SLPv2 so we can get rid of all this DHCP crap once and for all. 8-(. SLPv2 is used to find the gateway and DNS server, and after that, everything "magically works". If you get a lease in a zone, then because the forward record exists (because you have a Cert. for your own zone, the local DNS server should be willing to perform updates for your reverse record which it knows matcheds the forward record that lives in its zone but exists back on your home domain. Of course, this only works with IPv6, unless you use IPv4 with a link.local net plus integrated NAT in the gateway box. -- Terry