From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 10:44:26 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 2504E37B401 for ; Tue, 29 Jul 2003 10:44:26 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C9D243F75 for ; Tue, 29 Jul 2003 10:44:25 -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 h6THhVai076806; Tue, 29 Jul 2003 13:43:31 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h6THhUKm076803; Tue, 29 Jul 2003 13:43:31 -0400 (EDT) Date: Tue, 29 Jul 2003 13:43:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Terry Lambert In-Reply-To: <3F26A06C.D1E66484@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: Tue, 29 Jul 2003 17:44:26 -0000 On Tue, 29 Jul 2003, Terry Lambert wrote: > > 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. got message of size 24 on Tue Jul 29 13:27:59 2003 RTM_IFANNOUNCE: interface arrival/departure: len 24, if# 6, what: arrival got message of size 96 on Tue Jul 29 13:28:45 2003 RTM_IFINFO: iface status change: len 96, if# 6, flags: got message of size 24 on Tue Jul 29 13:28:45 2003 RTM_IFANNOUNCE: interface arrival/departure: len 24, if# 6, what: departure The event that you currently have to get using kqueue() is the link state, which isn't announced using routing sockets. If only for consistency, I'd like it if there were an ifnet level announcement in routing sockets for a link state change on capable interfaces. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories