From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Francois-Xavier Le Bail <fx.lebail@yahoo.com>
Cc: netdev@vger.kernel.org, Bill Fink <billfink@mindspring.com>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki Yoshifuji <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>
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 [thread overview]
Message-ID: <20140114131344.GR6586@order.stressinduktion.org> (raw)
In-Reply-To: <1389633764-5210-1-git-send-email-fx.lebail@yahoo.com>
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@mindspring.com>
> Signed-off-by: Francois-Xavier Le Bail <fx.lebail@yahoo.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
next prev parent reply other threads:[~2014-01-14 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 17:22 [PATCH net-next] IPv6: add option to use anycast addresses as source addresses in icmp error messages Francois-Xavier Le Bail
2014-01-14 13:13 ` Hannes Frederic Sowa [this message]
2014-01-14 23:38 ` Hannes Frederic Sowa
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 9:46 François-Xavier Le Bail
2014-01-15 11:44 ` Hannes Frederic Sowa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140114131344.GR6586@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=fx.lebail@yahoo.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox