Yes, it's Win2K, and yes, netstat -a gives <myhostname>:0 instead of 0.0.0.0:0 with netstat -a -n.
I've currently got 300+ entries connected to the listenPort and a fair number are transferring data so yes again, my node is currently working well. BUT. This is with the firewall switched off. If I switch the firewall on the number of connections to listenPort dwindles over time to 0 and then never increases, and the firewall log fills up with thousands of those "TCP Syn Packet on non-listening port. Packet has been dropped" errors. There are, so far as I can tell, three things which might have changed to cause this behaviour: 1. The OS. I can rule that out since I haven't run any updates during the period that this started to happen. 2. The firewall. Again, no changes to the firewall were made. 3. Fred. This is the only thing that's changed. When running 5028, the unstable builds until NGR was merged into stable, and then 5029/30, everything was working as expected. Then I changed to 5031 and bang, no incoming connections. (Or it might have been 5032. I'm not sure exactly when this happened as I only noticed it by accident when checking the connection manager page, something which I didn't do more than once or twice a day before this happened.) To me this suggests that the problem lies somewhere with the way that Fred is listening, but if not it wouldn't be the first time I've been wrong about something :) Thanks for your help so far, Kevin. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Edward J. Huff Sent: 16 November 2003 21:49 To: [EMAIL PROTECTED] Subject: RE: [freenet-support] Freenet port not listening according tofirewall. On Sun, 2003-11-16 at 03:37, Kevin Bennett wrote: > I only used the -a switch. If I add -n as well it becomes: > > TCP 0.0.0.0:49247 0.0.0.0:0 LISTENING. > > and many > > TCP <myIP>:49247 <foreignIP>:<port> ESTABLISHED ... I suppose that 0.0.0.0:0 means the same thing as 0.0.0.0:*, i.e. that it will accept connections on any IP and any port. Is this windows? Try without -n. Does 0.0.0.0:0 change to <myhostname>:0? That would be kind of weird, but MS$ has done weirder things. On the other hand, it might be that the situation is different now and you get 0.0.0.0:0 with -a -n and with -a. If you have established connections on your listenPort, they must be incoming so your system seems to be working. Is the firewall on? -- Ed Huff _______________________________________________ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
