From owner-freebsd-current@FreeBSD.ORG  Wed Jul 26 16:45:09 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
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 8C92C16A4DF
	for <freebsd-current@freebsd.org>; Wed, 26 Jul 2006 16:45:09 +0000 (UTC)
	(envelope-from fli+freebsd-current@shapeshifter.se)
Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 887FF43D53
	for <freebsd-current@freebsd.org>; Wed, 26 Jul 2006 16:45:04 +0000 (GMT)
	(envelope-from fli+freebsd-current@shapeshifter.se)
Received: from localhost (localhost [127.0.0.1])
	by mx1.h3q.net (Postfix) with ESMTP id 85A5C1A734;
	Wed, 26 Jul 2006 18:45:03 +0200 (CEST)
Received: from mx1.h3q.net ([127.0.0.1])
	by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP
	id 65761-10; Wed, 26 Jul 2006 18:45:01 +0200 (CEST)
Received: from [192.168.1.91] (217-208-33-252-o926.tbon.telia.com
	[217.208.33.252])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.h3q.net (Postfix) with ESMTP id 2B7081A6B2;
	Wed, 26 Jul 2006 18:45:01 +0200 (CEST)
Message-ID: <44C79C0B.6060900@shapeshifter.se>
Date: Wed, 26 Jul 2006 18:44:59 +0200
From: Fredrik Lindberg <fli+freebsd-current@shapeshifter.se>
User-Agent: Thunderbird 1.5.0.2 (X11/20060423)
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <44C61470.3070005@shapeshifter.se>
	<20060725173924.GR96589@funkthat.com> <44C68602.50105@elischer.org>
In-Reply-To: <44C68602.50105@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at h3q.net
Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-current@freebsd.org
Subject: Re: Extending EVFILT_NETDEV to support ip-address changes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2006 16:45:09 -0000

Julian Elischer wrote:
> 
> I may be wrong but doesn't an address change already trigger a routing 
> socket event?
> 

Yes, a routing message is sent on address addition/removal, but
the point (as I noted in my first mail) was to avoid the routing
socket-read-parse dance and provide a lightweight and direct
(the routing socket broadcasts events about all interfaces) mechanism
for address addition/removal events.
Also, the NOTE_ADDR{NEW,DEL} are sent AFTER interface configuration is
complete, at least RTM_DELADDR is broadcasted before the ip-address
actually is removed from the interface because it's sent from the
routing code and not the interface configuration code.

Fredrik Lindberg