From: Ulrich Weber <uweber@astaro.com>
To: netdev@vger.kernel.org
Subject: [RFC PATCH] dont create cached routes from ARP requests
Date: Wed, 22 Sep 2010 18:22:09 +0200 [thread overview]
Message-ID: <20100922162209.GA10281@babylon> (raw)
Do we really have to cache routes based on ARP requests?
Are there any other reasons than expecting new connections?
Attached is a patch to skip caching for ARP requests
not related to local IP addresses or ARP proxy.
Background: At home I have two Internet connections, DSL and Cable.
DSL is the primary uplink while Cable is the secondary.
My Cable ISP is flooding me with ARP request from 10.0.0.0/8,
which creates routes via the primary uplink.
There are thousands of cached routes and after some time
I get "Neighbour table overflow" messages.
Cheers
Ulrich
---
[PATCH] dont create cached routes from ARP requests
except for local destination or enabled ARP proxy. Otherwise
Neighbour table can overflow on broken network setups.
Signed-off-by: Ulrich Weber <uweber@astaro.com>
---
include/linux/in_route.h | 1 +
net/ipv4/route.c | 5 ++++-
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/include/linux/in_route.h b/include/linux/in_route.h
index b261b8c..d97dd35 100644
--- a/include/linux/in_route.h
+++ b/include/linux/in_route.h
@@ -18,6 +18,7 @@
#define RTCF_MASQ 0x00400000 /* unused */
#define RTCF_SNAT 0x00800000 /* unused */
#define RTCF_DOREDIRECT 0x01000000
+#define RTCF_NOCACHE 0x02000000
#define RTCF_DIRECTSRC 0x04000000
#define RTCF_DNAT 0x08000000
#define RTCF_BROADCAST 0x10000000
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index e24d48d..7f05e45 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -1090,7 +1090,7 @@ restart:
candp = NULL;
now = jiffies;
- if (!rt_caching(dev_net(rt->dst.dev))) {
+ if (rt->rt_flags & RTCF_NOCACHE || !rt_caching(dev_net(rt->dst.dev))) {
/*
* If we're not caching, just tell the caller we
* were successful and don't touch the route. The
@@ -2001,6 +2001,9 @@ static int __mkroute_input(struct sk_buff *skb,
err = -EINVAL;
goto cleanup;
}
+ if (!(out_dev->dev->flags & IFF_LOOPBACK) &&
+ !IN_DEV_PROXY_ARP(in_dev) && !IN_DEV_PROXY_ARP_PVLAN(in_dev))
+ flags |= RTCF_NOCACHE;
}
--
1.7.0.4
next reply other threads:[~2010-09-22 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 16:22 Ulrich Weber [this message]
2010-09-23 3:34 ` [RFC PATCH] dont create cached routes from ARP requests David Miller
2010-09-23 14:47 ` Ulrich Weber
2010-09-23 15:05 ` Eric Dumazet
2010-09-24 15:00 ` Ulrich Weber
2010-09-24 15:28 ` Eric Dumazet
2010-09-24 15:34 ` Eric Dumazet
2010-09-24 15:43 ` Ulrich Weber
2010-09-24 15:38 ` Ulrich Weber
2010-09-24 16:05 ` Eric Dumazet
2010-09-24 16:40 ` Ulrich Weber
2010-09-24 16:58 ` Eric Dumazet
2010-09-27 13:11 ` Ulrich Weber
2010-09-23 19:04 ` 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=20100922162209.GA10281@babylon \
--to=uweber@astaro.com \
--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;
as well as URLs for NNTP newsgroup(s).