All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marco C. Coelho" <maillist1@argontech.net>
To: lartc@vger.kernel.org
Subject: [LARTC] neighbor table overflow
Date: Mon, 22 Oct 2007 21:46:44 +0000	[thread overview]
Message-ID: <471D1A44.40503@argontech.net> (raw)
In-Reply-To: <200710230146.27081.peet@altlinux.org>

I've got a linux router pushing 600-1000 pppoe connections through it.  
I'm getting a screen error "Neighbor Table Overflow" after this box has 
been up for between 1 week and 1 month.  When this is happening, routing 
slows to a crawl if at all.  Then dies.  I've added:

# Added to stop "neighbor table overflow" messages in the kernel
net.ipv4.neigh.default.gc_thresh1Q2
net.ipv4.neigh.default.gc_thresh2 48
net.ipv4.neigh.default.gc_thresh3@96
# Added to increase IP contrack number (was getting to max)
net.ipv4.ip_conntrack_max™999

to sysctl.conf to increase the size, but this only seems to delay the 
problem.

Any thoughts?

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

  reply	other threads:[~2007-10-22 21:46 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 [this message]
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
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=471D1A44.40503@argontech.net \
    --to=maillist1@argontech.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.