netdev - Re: [PATCH net-next v2] IPv6: add option to use Subnet-Router anycast addresses as source addresses

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]

Date:	Fri, 3 Jan 2014 00:19:21 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	François-Xavier Le Bail <fx.lebail@...oo.com>,
	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	Alexey Kuznetsov <kuznet@....inr.ac.ru>,
	James Morris <jmorris@...ei.org>,
	Hideaki Yoshifuji <yoshfuji@...ux-ipv6.org>,
	Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH net-next v2] IPv6: add option to use Subnet-Router anycast addresses as source addresses

On Fri, Jan 03, 2014 at 12:17:30AM +0100, Hannes Frederic Sowa wrote:
> On Thu, Jan 02, 2014 at 10:56:17AM -0800, François-Xavier Le Bail wrote:
> > > I wouldn't actually add this knob, we can just enable that by default.
> > 
> > I think we need to keep by default the existing behaviour (ICMPv6 echo reply with unicast)
> > in case some setups use it, and use "enable_anycast_src" to change the behaviour 
> > according to RFC4942.
> 
> We try to extract the destination address and reuse it in the reply. The
> other system should not notice if it communicates with a unicast or
> anycast address. Am I missing something?

Ah, I guess you are hinting at the situation where you ping a pre-defined
anycast address and expect back a unicast address for discovering the unicast
address of a router e.g.? Ok, I see...

--
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