From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 21:08:29 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 937D637B401; Tue, 29 Jul 2003 21:08:29 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A650543F75; Tue, 29 Jul 2003 21:08:27 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6U48LFL013845; Tue, 29 Jul 2003 22:08:22 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 29 Jul 2003 22:07:03 -0600 (MDT) Message-Id: <20030729.220703.22439221.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <3F26D244.7060905@tcoip.com.br> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2003 04:08:29 -0000 In message: Robert Watson writes: : : On Tue, 29 Jul 2003, Daniel C. Sobral wrote: : : > > 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. : > : > Instead of just adding the stuff to devd? : : Currently, devd is in the business of dealing with attachment and removal : from the hardware management subsystem. currently, that's true. : Network subsystem events, such as : "interface has arrived" are semantically different, but "close enough" in : many cases. I've been pondering making devd grok such events, as well as other power events. Eg, it will be a place that acpi could route acpi events to replace apm. : In the past, routing sockets have been the means by which : topology-relevant changes are announced to the user processes. More : recently, kqueue has permitted monitoring of a plethora of event types. I : think there's a decent argument for a neteventd, perhaps integrated as a : thread into devd, listening on network events rather than device : attach/detach events. I think that would be a good idea.... Don't know if there's a 'thread' or a virtual thread-like thing. : The only real problem is that it would be very nice : if the DHCP client code were available in a library so it could be linked : into a network event manager. It would make things a lot easier. Warner