> > > Also, a side note, Linux 2.4.21 connection manager (turns on when you > have NAT) does this: > > $ grep ASSUR /proc/net/ip_conntrack | wc -l > 7329 > > when you run freenet for a little while and you have 14 days of > uptime, yet, when I look at it, there are more things in this list > than open network connections: > > $ ls -ltR /proc/ | more | grep socket | sort | more | wc -l > 2812 > > which seems like they are leaking. Also, I can restart freenet and > most all the entries stay in the conntrack list. I did this to side > step the issue, and not have my machine DOS all network connectivity > on me: > > $ cat /proc/sys/net/ipv4/ip_conntrack_max > 30000 > > :-(
Worse then that, walking the hashtable collisions starts to eat massive amounts of CPU after a while. It's a ip_conntrack bug, not a freenet bug. (They're staying around after being closed for hours. That's way out of spec) --Dan
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
