From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>,
Jesper Dangaard Brouer <hawk@diku.dk>
Cc: netdev@vger.kernel.org
Subject: [PATCH] ip: add loose reverse path filtering
Date: Fri, 20 Feb 2009 10:25:36 -0800 [thread overview]
Message-ID: <20090220102536.2d39ddb9@extreme> (raw)
Extend existing reverse path filter option to allow strict or loose
filtering. (See http://en.wikipedia.org/wiki/Reverse_path_filtering).
For compatibility with existing usage, the value 1 is chosen for strict mode
and 2 for loose mode.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
---
Documentation/networking/ip-sysctl.txt | 22 ++++++++++++++--------
net/ipv4/fib_frontend.c | 2 +-
2 files changed, 15 insertions(+), 9 deletions(-)
--- a/Documentation/networking/ip-sysctl.txt 2009-02-20 10:24:04.128692016 -0800
+++ b/Documentation/networking/ip-sysctl.txt 2009-02-20 10:24:09.733192268 -0800
@@ -699,16 +699,22 @@ accept_source_route - BOOLEAN
default TRUE (router)
FALSE (host)
-rp_filter - BOOLEAN
- 1 - do source validation by reversed path, as specified in RFC1812
- Recommended option for single homed hosts and stub network
- routers. Could cause troubles for complicated (not loop free)
- networks running a slow unreliable protocol (sort of RIP),
- or using static routes.
-
+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.
+
+ Current recommended practice in RFC3704 is to enable strict mode
+ to prevent IP spoofin from DDos attacks. If using asymmetric routing
+ or other complicated routing,t hen loose mode is recommended.
- conf/all/rp_filter must also be set to TRUE to do source validation
+ conf/all/rp_filter must also be set to non-zero to do source validation
on the interface
Default value is 0. Note that some distributions enable it
--- a/net/ipv4/fib_frontend.c 2009-02-20 10:24:04.140692744 -0800
+++ b/net/ipv4/fib_frontend.c 2009-02-20 10:24:09.733192268 -0800
@@ -275,7 +275,7 @@ int fib_validate_source(__be32 src, __be
fib_res_put(&res);
if (no_addr)
goto last_resort;
- if (rpf)
+ if (rpf == 1)
goto e_inval;
fl.oif = dev->ifindex;
next reply other threads:[~2009-02-20 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 18:25 Stephen Hemminger [this message]
2009-02-21 13:09 ` [PATCH] ip: add loose reverse path filtering Herbert Xu
2009-02-22 7:56 ` David Miller
2009-02-22 8:34 ` Herbert Xu
2009-02-23 21:46 ` Stephen Hemminger
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=20090220102536.2d39ddb9@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=hawk@diku.dk \
--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 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.