From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: [PATCH net-next] IPv6: add option to use anycast addresses as source addresses in icmp error messages Date: Tue, 14 Jan 2014 14:13:44 +0100 Message-ID: <20140114131344.GR6586@order.stressinduktion.org> References: <1389633764-5210-1-git-send-email-fx.lebail@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: netdev@vger.kernel.org, Bill Fink , "David S. Miller" , Alexey Kuznetsov , James Morris , Hideaki Yoshifuji , Patrick McHardy To: Francois-Xavier Le Bail Return-path: Received: from order.stressinduktion.org ([87.106.68.36]:35722 "EHLO order.stressinduktion.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751683AbaANNNq (ORCPT ); Tue, 14 Jan 2014 08:13:46 -0500 Content-Disposition: inline In-Reply-To: <1389633764-5210-1-git-send-email-fx.lebail@yahoo.com> Sender: netdev-owner@vger.kernel.org List-ID: 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 > Signed-off-by: Francois-Xavier Le Bail 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