Op 13-jan-2011, om 20:04 heeft Daxter het volgende geschreven:
On Jan 12, 2011, at 3:41 PM, Edzard Pasma wrote:
Op 12-jan-2011, om 19:32 heeft Daxter het volgende geschreven:
I can't figure out what exactly is the cause, so I'll just
explain the symptoms. Freenet is running fine, but most attempts
to load a "normal" (WWW) web page either stall or load very
slowly. My guess is that, starting somewhere around build 1315,
my node started creating so many connections that it borders the
max number my router supports, thus leaving little room for other
applications to create their own connections. I am sure that
Freenet is the issue because as soon as I shut down my node,
pages load at their normal rate.
This leads to two questions:
1. How can I determine that this is indeed the issue? (that my
router's connection limit is maxed out, and/or that Freenet is
causing it)
2. What might my node be doing to cause in the first place? An
alternate theory would be that it isn't properly terminating old
connections to my router's liking.
Here is an answer to question 1, but just for Linux.
On Linux you have netstat to find out about open connections. The
plain command returns some hundred lines, on a quiet system. I
think the limit is in the order of the number of available ports
or at least those in the dynamic range (5.000?).
Netstat -p prints the process id that owns a connection. Grep and
co should find the freenet processes. On my system this yields
just 5 connections.
I'm running Mac OS X, but it already has netstat installed. The
problem is that "-p" refers to something to do with protocols,
instead of processes. I searched the man page and couldn't find any
reference to an ability to show the processes holding the connections.
I don't know how large the limit of connections is, but the range
of ports at least goes to 65,535 (according to what I could find on
a quick web search).
Oddly there weren't that many connections (a few hundred). Now I'm
really confused; how, then, is Freenet preventing other
applications from communicating? This symptom only exists when it's
running... Freenet rarely even uses 1/4 of my download bandwidth.
May be more convenient than netstat is list open "files"::
lsof -p <freenet process id's> | grep -e TCP -e UDP -e COMMAND
There must be more advanced options but I'am not using these commands
very often and use grep to filter the report. Lsof also shows UDP
connections that I missed yesterday (should have used netstat-a to
include these)._______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
