From: Eric Dumazet <eric.dumazet@gmail.com>
To: Eric Leblond <eric@regit.org>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] ipv6: basic implementation of reverse path filtering
Date: Mon, 06 Jun 2011 14:22:37 +0200 [thread overview]
Message-ID: <1307362957.3098.7.camel@edumazet-laptop> (raw)
In-Reply-To: <1307360074-25473-1-git-send-email-eric@regit.org>
Le lundi 06 juin 2011 à 13:34 +0200, Eric Leblond a écrit :
> This patch provides a basic implementation of reverse path filtering
> for IPv6. Functionnality can be activatedor desactivated through an
> rp_filter entry similar to the IPv4 one.
>
> The functionnality is disabled by default for backward compatibility
> but should be enable on all IPv6 routers/firewalls for security reason.
>
> This implementation is heavily based on the patch Denis Semmau proposed
> in 2006.
>
> Signed-off-by: Eric Leblond <eric@regit.org>
> ---
> include/linux/ipv6.h | 2 ++
> include/linux/sysctl.h | 1 +
> net/ipv6/addrconf.c | 10 ++++++++++
> net/ipv6/ip6_output.c | 32 ++++++++++++++++++++++++++++++++
> 4 files changed, 45 insertions(+), 0 deletions(-)
>
Hmm, is it matching ipv4 one really ?
vi +855 Documentation/networking/ip-sysctl.txt
rp_filter - INTEGER
0 - No source validation.
1 - Strict mode as defined in RFC3704 Strict Reverse Path
Each incoming packet is tested against the FIB and if the interface
is not the best reverse path the packet check will fail.
By default failed packets are discarded.
2 - Loose mode as defined in RFC3704 Loose Reverse Path
Each incoming packet's source address is also tested against the FIB
and if the source address is not reachable via any interface
the packet check will fail.
next prev parent reply other threads:[~2011-06-06 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 11:34 [RFC PATCH] ipv6: basic implementation of reverse path filtering Eric Leblond
2011-06-06 12:22 ` Eric Dumazet [this message]
2011-06-06 17:53 ` [RFC PATCHv2] ipv6: " Eric Leblond
2011-06-06 18:18 ` Eric Dumazet
2011-06-06 19:29 ` David Miller
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=1307362957.3098.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=eric@regit.org \
--cc=netdev@vger.kernel.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