[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140114131344.GR6586@order.stressinduktion.org>
Date: Tue, 14 Jan 2014 14:13:44 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: Francois-Xavier Le Bail <fx.lebail@...oo.com>
Cc: netdev@...r.kernel.org, Bill Fink <billfink@...dspring.com>,
"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] IPv6: add option to use anycast addresses as source addresses in icmp error messages
On Mon, Jan 13, 2014 at 06:22:44PM +0100, Francois-Xavier Le Bail wrote:
> - Add "anycast_src_icmp_error" sysctl to control the use of anycast addresses
> as source addresses for ICMPv6 error messages. This sysctl is false by
> default to preserve existing behavior.
> - Use it in icmp6_send().
>
> Suggested-by: Bill Fink <billfink@...dspring.com>
> Signed-off-by: Francois-Xavier Le Bail <fx.lebail@...oo.com>
Regarding the anycast patches, I contacted someone from IETF.
The number of sysctls needed to get introduced to have all the flexibility
regarding source address selection and don't break backward compatibility
concerns me a bit.
Especially on end hosts, where those switches will be important, I think we
really have to think about sensible defaults without breaking current
software.
I currently consider a per-address flag, if those anycast addresses
should be available in source address selection (also with an enhancement to
current IPV6_JOIN_ANYCAST logic).
Greetings,
Hannes
--
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