Date: 11 Jul 2002 17:04:14 +0400 From: "Vladimir B. " Grebenschikov <vova@sw.ru> To: Andreas Gerstenberg <andy@andy.de> Cc: freebsd-net@freebsd.org Subject: Re: limits in routing table? Message-ID: <1026392654.790.46.camel@vbook.express.ru> In-Reply-To: <10400000.1026292734@ag.intra> References: <10400000.1026292734@ag.intra>
next in thread | previous in thread | raw e-mail | index | archive | help
χ Wed, 10.07.2002, Χ 13:18, Andreas Gerstenberg ΞΑΠΙΣΑΜ:
> Hi,
>
> I got the following error while figuring out the maximum amount of routes
> in the kernel routing table:
>
> # route add 192.168.1.1/32 10.0.0.1
> route: writing to routing socket: No buffer space available
> add net 192.168.1.1: gateway 10.0.0.1: routing table overflow
>
> # netstat -rn | wc -l
> 299448
First, you can see is it route area limit with:
# vmstat -m | fgrep routetbl\
routetbl 6907 942K 1678K102400K 4870047 0 0
16,32,64,128,256,512
legend is:
# vmstat -m | fgrep HighUse
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
On -CURRENT, as I understand there no limit for routetbl zone:
# vmstat -m | fgrep rou
routetbl 87 12K 13K 267490 16,32,64,128,256
# vmstat -m | fgrep MemUse
Type InUse MemUse HighUse Requests Size(s)
> How can I set a higher limit?
for 4.x you can use following define in kernel config:
options VM_KMEM_SIZE_SCALE="(1)"
# VM_KMEM_SIZE_SCALE can be set to adjust the auto-tuning factor, which
# typically defaults to 4 (kernel malloc area size is physical memory
# divided by the scale factor).
It works for me (see above)
Or you can use -CURRENT to large routing tables, but not sure that it is
good idea for production routers.
> System: XP1700+, 512 MB DDR-RAM, FreeBSD 4.6p1 (RELENG_4_6)
> Maxusers is set to 512
>
> regards,
> Andy
--
Vladimir B. Grebenschikov
vova@sw.ru, SWsoft, Inc.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1026392654.790.46.camel>