From: Ben Greear <greearb@candelatech.com>
To: Patrick McHardy <kaber@trash.net>
Cc: NetDev <netdev@vger.kernel.org>
Subject: ARP table question
Date: Wed, 12 Nov 2008 11:43:39 -0800 [thread overview]
Message-ID: <491B31EB.4050304@candelatech.com> (raw)
In-Reply-To: <491B1841.9050404@candelatech.com>
I have 500 mac-vlans on a system talking to 500 other
mac-vlans. My problem is that the arp-table gets extremely
huge because every time an arp-request comes in on all mac-vlans,
a stale arp entry is added for each mac-vlan. I have filtering
turned on, but that doesn't help because the neigh_event_ns call
below will cause a stale neighbor entry to be created regardless
of whether a replay will be sent or not.
Maybe the neigh_event code should be below the checks for dont_send,
and only create check neigh_event_ns if we are !dont_send?
This is the code I'm talking about, in arp.c (in kernel 2.6.25.15)
if (arp->ar_op == htons(ARPOP_REQUEST) &&
ip_route_input(skb, tip, sip, 0, dev) == 0) {
rt = (struct rtable*)skb->dst;
addr_type = rt->rt_type;
if (addr_type == RTN_LOCAL) {
n = neigh_event_ns(&arp_tbl, sha, &sip, dev);
int dont_send = 0;
if (!dont_send)
dont_send |= arp_ignore(in_dev,sip,tip);
if (!dont_send && IN_DEV_ARPFILTER(in_dev))
dont_send |= arp_filter(sip,tip,dev);
if (!dont_send)
arp_send(ARPOP_REPLY,ETH_P_ARP,sip,dev,tip,sha,dev->dev_addr,sha);
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next parent reply other threads:[~2008-11-12 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <491B1600.4080505@candelatech.com>
[not found] ` <491B1841.9050404@candelatech.com>
2008-11-12 19:43 ` Ben Greear [this message]
2008-11-12 22:10 ` ARP table question Ben Greear
2008-11-17 3:16 ` David Miller
2008-11-17 18:17 ` Ben Greear
2008-11-18 0:33 ` Ben Greear
2008-11-18 0:51 ` Rick Jones
2008-11-18 1:23 ` Ben Greear
2008-11-18 1:39 ` Rick Jones
2008-11-18 1:50 ` Ben Greear
2008-11-20 8:33 ` David Miller
2008-11-20 17:23 ` Ben Greear
2008-11-20 17:33 ` Benjamin LaHaise
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=491B31EB.4050304@candelatech.com \
--to=greearb@candelatech.com \
--cc=kaber@trash.net \
--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).