From owner-freebsd-net@FreeBSD.ORG Wed Jan 15 09:18:32 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25ADEE4F for ; Wed, 15 Jan 2014 09:18:32 +0000 (UTC) Received: from mail.ipfw.ru (mail.ipfw.ru [IPv6:2a01:4f8:120:6141::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B27521CDE for ; Wed, 15 Jan 2014 09:18:31 +0000 (UTC) Received: from [2a02:6b8:0:401:222:4dff:fe50:cd2f] (helo=ptichko.yndx.net) by mail.ipfw.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1W3ImX-000Lap-LU; Wed, 15 Jan 2014 09:12:49 +0400 Message-ID: <52D6519D.2050400@FreeBSD.org> Date: Wed, 15 Jan 2014 13:15:09 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Roy Marples , freebsd-net@freebsd.org Subject: Re: IPv6: report address flag changes to userland References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 09:18:32 -0000 On 13.01.2014 19:36, Roy Marples wrote: > Hi List Hello! > > There is zero point as I see it in announcing newly added tentative > addresses to userland. > It's not as if userland can actually use the address at this point. > However, there is immense benefit in announcing address flag changes, > such as removal of tentative, or addition of the other flags. This looks very reasonable. > > The main benefit for this patch is so that dhcpcd(8) listen for when > the kernel has completed DAD and has announced the result. > dhcpcd can then react immediately instead of having to wait for the > full time as dictated by the RFC. This can also help when doing IPv6 netmap forwarding to sync kernel and userland records. > > The attached patch addresses the above and was cut from FreeBSD-9 - > there is a small adjustment needed for -current which is noted in the > patch. > The patch is based on the work I did in NetBSD a few months ago > documented here: > http://netbsd.2816.n7.nabble.com/PATCH-to-only-announce-RTM-NEWADDR-once-IPv6-DAD-completes-tp281110.html > > > Comments? I'll do some tests and merge it. > > Roy > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"