From: Andi Kleen <ak@suse.de>
To: Pekka Savola <pekkas@netcore.fi>
Cc: "David S. Miller" <davem@redhat.com>,
timg@tpi.com, anton@samba.org, netdev@oss.sgi.com,
linux-net@vger.kernel.org
Subject: Re: [PATCH} ARP auto-sizing for 2.4.24 - 2.4.26-pre3
Date: Mon, 15 Mar 2004 23:00:11 +0100 [thread overview]
Message-ID: <20040315220011.GC20830@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0403152350260.6903-100000@netcore.fi>
> Isn't there a problem when an outside attacker brute-force pings every
> IP address in some order? The intent here is to overload the router
> to do a lot of ARP/ND requests which result to nothing.
Note that the max number of active neighbours per interface is limited. There
is a natural limit on how many entries the hash tables can have.
The user can increase this with sysctls, but the defaults should be
safe.
-Andi
next prev parent reply other threads:[~2004-03-15 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 19:10 [PATCH} ARP auto-sizing for 2.4.24 - 2.4.26-pre3 Tim Gardner
2004-03-15 21:44 ` David S. Miller
2004-03-15 21:55 ` Pekka Savola
2004-03-15 21:57 ` David S. Miller
2004-03-15 22:21 ` Pekka Savola
2004-03-15 22:00 ` Andi Kleen [this message]
2004-03-16 16:05 ` Tim Gardner
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=20040315220011.GC20830@wotan.suse.de \
--to=ak@suse.de \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=timg@tpi.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 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).