From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexandru Dragoi <alex@zoomnet.ro>
Date: Tue, 23 Oct 2007 11:56:48 +0000
Subject: Re: [LARTC] neighbor table overflow
Message-Id: <471DE180.5040708@zoomnet.ro>
List-Id: <lartc.vger.kernel.org>
References: <200710230146.27081.peet@altlinux.org>
In-Reply-To: <200710230146.27081.peet@altlinux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
To: lartc@vger.kernel.org

Marco C. Coelho wrote:
> 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=99999
>
> 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
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.


# ip rou |grep link
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc