lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070213182208.GA25362@hmsreliant.homelinux.net>
Date:	Tue, 13 Feb 2007 13:22:08 -0500
From:	Neil Horman <nhorman@...driver.com>
To:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
Cc:	vladislav.yasevich@...com, sri@...ibm.com, davem@...emloft.net,
	kuznet@....inr.ac.ru, pekkas@...core.fi, jmorris@...ei.org,
	kaber@...eworks.de, netdev@...r.kernel.org
Subject: Re: [PATCH] IPv6: Implement RFC 4429 Optimistic Duplicate Address Detection

On Tue, Feb 13, 2007 at 08:27:59AM +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <20070208130715.GA27267@...reliant.homelinux.net> (at Thu, 8 Feb 2007 08:07:15 -0500), Neil Horman <nhorman@...driver.com> says:
> 
> > > I still have a question.  Now, who will install the kernel route for
> > > the incoming packet?  Can we get packet for our unicast address during
> > > optimistic DAD period?
> > > 
> > Not sure what you're getting at here.  RFC 4429 makes no distinction between
> > optimistic and non-optimistic packets for recevied frames, so routes for
> > received packets will be added by the same code that does it currently (which I
> > admittedly haven't looked into to closely).  Packets received for our unicast
> > address (even if it is optimistic) are handled just as any other packet is (same
> > as it is for TENTATIVE addresses, as I understand it). 
> 
> I think it is clear.
> 
> In tentative state, we do not receive any packet.
> After finishind DAD process, we install kernel route for that address
> in net/ipv6/addrconf.c:__ipv6_ifa_notify(), and we start receiving
> packet for that address.
> 
> On the other hand, optimistic addresses are like in deprecated state.
> So, we should be able to receive frames for those addresses.
> 
I'm sorry, you're right, it is clear now.  I hadn't considered the need for a
route to receive frames, and the point at which we insert it.  I'm puting
together a new patch for this right now and will post it as soon as I've built
and started testing it.

Thanks & Regards
Neil


> --yoshfuji
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ