rTorrent + FreeBSD + pf = freeze?

[Michael K. Smith]

On 11/23/09 2:28 PM, "Michael Schaefer" <utf128 at googlemail.com> wrote:

> On 22.11.2009 23:11, cpghost wrote:
>>> Have you tried to run rtorrent and the router on two different
>>> FreeBSD machines? Does it lock the router, or does it crash the
>>> rtorrent box only, or both?
> 
> even though i haven't been asked i might want to answer  ;)  Since my
> box really exclusively does rtorrent i don't think it's related to
> routing or NAT. pf is not active at all. Routing and NAT for my setup is
> done by a dedicated different box (which isn't affected by all this,
> apart from that it doesn't run freebsd).
> 
> so for me this really looks like a /networking/ issue, which is not
> dedicated to routing or NAT in particular..
> for me this now becomes kinda problematic, since i cannot even start the
>  second rtorrent instance without crashing the machine immediately..  :(
> 
> regards - michael

We had similar crashes with PF, although not related to rtorrent
specifically.  However, we use the following sysctl values that have helped
stability and performance immensely.

net.inet.carp.preempt=1
net.inet.carp.arpbalance=0
net.inet.icmp.icmplim=2000
net.inet.tcp.sendspace=65536
net.inet.tcp.recvspace=65536
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=1
kern.ipc.somaxconn=32768
net.inet.tcp.mssdflt=1460
kern.ipc.maxsockbuf=16777216
kern.ipc.nmbclusters=32768
kern.maxfiles=65536
kern.maxfilesperproc=32768
kern.maxvnodes=600000
net.inet.tcp.delayed_ack=0
net.inet.tcp.inflight.enable=0
net.inet.tcp.path_mtu_discovery=0
net.inet.tcp.recvbuf_auto=1
net.inet.tcp.recvbuf_inc=16384
net.inet.tcp.recvbuf_max=16777216
net.inet.tcp.rfc1323=1
net.inet.tcp.sendbuf_auto=1
net.inet.tcp.sendbuf_inc=8192
net.inet.udp.maxdgram=57344
net.inet.udp.recvspace=65536
net.local.stream.recvspace=65536
net.inet.tcp.sendbuf_max=16777216

Regards,

Mike