From: "darko" <darko@veze.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] neighbor table overflow
Date: Mon, 19 Nov 2007 23:15:04 +0000 [thread overview]
Message-ID: <20071119225501.M90713@veze.net> (raw)
In-Reply-To: <200710230146.27081.peet@altlinux.org>
> Still beating the same bush!
>
> I've done all the possible suggestions so far. I still was getting
> a neighbor table overflow. ...
If this can help. Have same problem when testing new server in network (kernel
is 2.6.21.5) - everything seems OK in system except neighbor table overflow,
and as consequence buffer overflow. Situation was next:
Server Internet port was connected in network where logically local port of
the server belong. There are mostly 10.x.0.0/16 addresses. Also on that
network was one client with some viruses which produce excessive ARP scanning
of 10.x.0.0/16 clients.
In situation when local port of server is connected where it's belonging,
there is no overflow messages, nor any problems.
Also there are no problem in situation when problematic client was offline.
Darko
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-11-19 23:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 21:46 [LARTC] neighbor table overflow Peter V. Saveliev
2007-10-22 21:46 ` Marco C. Coelho
2007-10-22 22:35 ` Grant Taylor
2007-10-23 11:56 ` Alexandru Dragoi
2007-10-23 20:32 ` Grant Taylor
2007-10-23 20:43 ` Jeff Welling
2007-10-23 21:04 ` Grant Taylor
2007-10-23 21:10 ` Marco C. Coelho
2007-10-23 21:23 ` Grant Taylor
2007-10-23 21:27 ` Marco C. Coelho
2007-10-24 10:19 ` Alexandru Dragoi
2007-10-24 15:19 ` Marco C. Coelho
2007-10-24 16:06 ` Alexandru Dragoi
2007-10-25 15:08 ` Marco C. Coelho
2007-10-25 16:30 ` Alexandru Dragoi
2007-11-19 22:36 ` Marco C. Coelho
2007-11-19 23:15 ` darko [this message]
2007-12-07 17:17 ` Marco C. Coelho
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=20071119225501.M90713@veze.net \
--to=darko@veze.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 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.