All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] neighbor table overflow
Date: Tue, 23 Oct 2007 21:23:41 +0000	[thread overview]
Message-ID: <471E665D.10307@riverviewtech.net> (raw)
In-Reply-To: <200710230146.27081.peet@altlinux.org>

On 10/23/07 16:27, Marco C. Coelho wrote:
> Is there a way to probe the kernel to find out how big the neighbor 
> table is on a regular basis?  Without making a smoking hole of course.

Other than querying the ARP cache, I'm not aware of any thing.  I'm sure 
there is a way with in the kernel to see how many entries are in the ARP 
cache, but I am the wrong person to ask.

> BTW, Traffic shaping is also controlled via Radius.

*nod*

> It's actually pretty happy on a single processor, single core AMD 3000 
> with 1.5 G of RAM (it was not happy with 512K!!!).   I've actually got a 
> new Dual Core, Dual Processor box loaded and ready to place in 
> production, but would like to fix this problem first.  Unfortunately it 
> takes between a week and a month for the problem to surface.

Good.  It is nice to see Linux doing some things that Cisco and others 
tried to dominate for so long.

> I'm working on it, but time is slim today (but not me)!

I wonder if you can turn up debugging on your OSPF daemon to see who / 
what is being advertised.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-10-23 21:23 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 [this message]
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=471E665D.10307@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.