From: Oscar Mechanic <oscar@ufomechanic.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] arp flood (offtopic?)
Date: Thu, 20 Oct 2005 08:33:08 +0000 [thread overview]
Message-ID: <1129797188.14822.187.camel@OSCARLAPLIN> (raw)
In-Reply-To: <032b01c5d4bb$a8837ed0$020c0c0a@admin>
Has anyone tried ebtables and the limit target to control the rate
On Thu, 2005-10-20 at 00:09 +0200, Carl-Daniel Hailfinger wrote:
> Alex schrieb:
> > Now the thing is that the load average goes up to 30 and the gateway
> > doesn't even respond to ping after a while.
> > The arp-requests are not only for ips that are assigned to hosts but
> > even for un-allocated ips in the same subnet.
>
> Ah. Classical problem. There are only two realistic explanations for it:
> - the source of the arp flood is scanning the local net
> - the source of the arp flood has been infected with a virus.
> In my experience, only viruses generate real floods, scans are much more
> friendly to the network. So just clean the viruses from the flooding
> machines.
>
> > Maybe dividing into multiple vlans would be a better idea?
>
> Yes, that would somewhat help, but not solve the problem completely.
> Besides, I'd go for fixing the real problem instead of some symptoms.
>
>
> Regards,
> Carl-Daniel
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-20 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 14:44 [LARTC] arp flood (offtopic?) Alex
2005-10-19 14:51 ` Carl-Daniel Hailfinger
2005-10-19 18:04 ` Marek Kierdelewicz
2005-10-19 20:55 ` Alex
2005-10-19 22:09 ` Carl-Daniel Hailfinger
2005-10-20 8:33 ` Oscar Mechanic [this message]
2005-10-20 22:19 ` Peter Surda
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=1129797188.14822.187.camel@OSCARLAPLIN \
--to=oscar@ufomechanic.net \
--cc=lartc@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