From mboxrd@z Thu Jan  1 00:00:00 1970
From: "raptor@tvskat.net" <raptor@tvskat.net>
Date: Thu, 12 Aug 2004 12:01:55 +0000
Subject: Re: [LARTC] ARP limit ?
Message-Id: <20040812150155.5286f0cf@bugs>
List-Id: <lartc.vger.kernel.org>
References: <4119C13F.2090906@drugphish.ch>
In-Reply-To: <4119C13F.2090906@drugphish.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

from make config --> arpd -> help

....
 This code is experimental and also obsolete.
.....

2.4.22
That is why I try to use bogger gc_*
thanx for the links.. reading now..


> Hello,
> 
> > yep, i'm using them, i needed to know the max and anyone experiencing 
> 
> Those are int and nothing in the kernel code prevents them having 
> MAX_INT-1 assigned as a value. However you have a rather serious 
> networking problem anyway if you exceed the predefined gc* values.
> 
> Some more information (besides reading the related kernel code):
> 
> http://www.rstack.net/arp.html
> http://www.rstack.net/tuning_proc_for_arp.html
> 
> > problems with very big arp's
> 
> Yes, the time spent in the GC to reach the equilibrium is rather high 
> with a high number of stale cache entries. Once gc_tresh3 threshold 
> kicks in you get an aggressive table flush concurrent with the new 
> neighbour entries.
> 
> > arpd is marked as depricated or so!?
> 
> No, not at all ;).
> 
> Best regards,
> Roberto Nibali, ratz
> -- 
> echo 
> '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/