From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: nicolas.dichtel@6wind.com, dsa@cumulusnetworks.com,
netdev@vger.kernel.org, hannes@redhat.com
Subject: Re: [PATCH net-next v5] net: ipv6: Make address flushing on ifdown optional
Date: Wed, 14 Oct 2015 06:00:07 -0700 (PDT) [thread overview]
Message-ID: <20151014.060007.594576048227764026.davem@davemloft.net> (raw)
In-Reply-To: <1444824845.2190190.409937049.5F844219@webmail.messagingengine.com>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 14 Oct 2015 14:14:05 +0200
> I can bring up the rp_filter setting, too. It currently gets
> unconditional set to strict mode in systemd on all interfaces.
Sigh...
> The question is, if we should care about people enabling forwarding by
> simply toggling the sysctl forwarding knob? Essentially in the kernel we
> could provide two sysctl knobs, one for forwarding and one for local
> reception. So people following the guidelines how to enable forwarding
> could automatically have rp_filter enabled while host mode does not
> because we leave the forwarding rp_filter setting enabled. This at the
> same time seems unnecessary complex and maybe we should simply talk to
> distributions. ;)
>
> What do you think?
We could make rp_filter only apply when something more than default and
subnet routes are configured. Another bypass might be when only one
interface other than loopback is up and enabled for ipv4.
next prev parent reply other threads:[~2015-10-14 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 16:33 [PATCH net-next v5] net: ipv6: Make address flushing on ifdown optional David Ahern
2015-10-14 1:45 ` David Miller
2015-10-14 9:34 ` Hannes Frederic Sowa
2015-10-14 10:08 ` Nicolas Dichtel
2015-10-14 11:03 ` Hannes Frederic Sowa
2015-10-14 12:18 ` David Miller
2015-10-14 12:14 ` Hannes Frederic Sowa
2015-10-14 13:00 ` David Miller [this message]
2015-10-14 16:09 ` David Ahern
2015-10-15 1:06 ` David Miller
2015-10-15 2:46 ` David Ahern
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=20151014.060007.594576048227764026.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=hannes@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.