From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 14:40:16 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 EE5CA37B401 for ; Tue, 29 Jul 2003 14:40:16 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1221343F75 for ; Tue, 29 Jul 2003 14:40:14 -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 h6TLdHai078188; Tue, 29 Jul 2003 17:39:17 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h6TLdGTC078185; Tue, 29 Jul 2003 17:39:16 -0400 (EDT) Date: Tue, 29 Jul 2003 17:39:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Daniel C. Sobral" In-Reply-To: <3F26D244.7060905@tcoip.com.br> 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: Tue, 29 Jul 2003 21:40:17 -0000 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. Network subsystem events, such as "interface has arrived" are semantically different, but "close enough" in many cases. 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. 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. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories