Performance/lockup issues with FreeBSD as a router

[T.D.Wipnet (H.M.)]

On Thursday 26 May 2005 14:47, Peter Kieser wrote: 
> however I'm currently running into issues where one, or both of the
> NICs will stop transmitting traffic. When I go onto the machine,
> and try to ping something I get "No buffer space available"
>

stopping transmitting anything or only your ping tries?

> net.inet.ip.rtexpire=1800
> net.inet.ip.rtminexpire=1800
> kern.maxfiles=32768
> kern.maxfilesperproc=32768
> kern.ipc.somaxconn=32767
> net.inet.tcp.sendspace=256000
> net.inet.tcp.recvspace=256000
> kern.ipc.maxsockbuf=2097152
> net.inet.ip.fastforwarding=1
> net.inet.tcp.rfc1323=1
> net.link.ether.inet.max_age=600
> net.inet.tcp.msl=7500
> net.inet.ip.fw.dyn_udp_lifetime=10
> net.inet.ip.fw.dyn_buckets=1024
>
> And here's my /boot/loader.conf:
>
> kern.ipc.maxsockets="163840"
> kern.maxusers="2048"
>

if your pc is really only a router you probably have a lot of 
unessessary stuff in here, your extremly high settings for maxuser, 
maxfiles and somaxcons is somewhat useless here and could slow your 
machine down, anyway, this is not a p-III 600 with 128MB of ram isn't 
it?

"no buffer space available" appears often when the buffer is used so 
that means that if your connections are bad the buffer gets filled 
because if your connections are good why the buffer should be used? - 
then it goes straight out  ... I guess that probably your Nics, 
cables, hubs or even the "where it goes" may have a problem

Hans


-- 

WIPNET Telecom Ltda. http://wip.mega.net.br
http://wip.mega.net.br/tec.asc