From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] neighbor table overflow
Date: Tue, 23 Oct 2007 20:32:19 +0000 [thread overview]
Message-ID: <471E5A53.3000405@riverviewtech.net> (raw)
In-Reply-To: <200710230146.27081.peet@altlinux.org>
On 10/23/07 06:56, Alexandru Dragoi wrote:
> What about checking your routing table? you may have link routes for
> massive subnets (like 85.0.0.0/8 or 140.20.0.0/16). Some programs
> prefer to use "standard" netmask of classes A and B.
I'm betting that the OP has other things going on seeing has how s/he
mentioned PPPoE, which to my knowledge is a layer 2 protocol, and thus
not subject to typical routing scenarios. In essence the OP could have
thousands of PPPoE connections terminating on one system with the ARP
cache having to deal with where to send traffic to which MAC address.
There is not a lot of room for routing in such a scenario.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-10-23 20:32 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 [this message]
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
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=471E5A53.3000405@riverviewtech.net \
--to=gtaylor@riverviewtech.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.