On Thursday 16 December 2010 13:06:10 arra...@gmx.net wrote: > On some day not that long ago, Juiceman wrote: > > > > On Dec 1, 2010 11:13 AM, <arra...@gmx.net> wrote: > > > Hi folks! > > > Why can't I tell Freenet to use the port I want it to by altering > > > the freenet.ini ? > > > E.g.: Let's say I want to hide the Freenet traffic by using the > > > typical DirectX-ports, like 47624 or 2300-2400 ... doesn't work, > > > after changing the ini Freenet does not connect any more and I > > > have to reinstall ... > > > > Make sure you are not changing the FCP or fproxy ports by mistake and > > you edit the ini file when Freenet is shutdown. > > I'm pretty sure I edited the INI while the service was shut down, and I > was editing the right entry ... . > > I've come to the conclusion that it was pure coincidence that the node > refused to connect just after I altered the port entry, because since > then, the node has only connected successfully twice, but most times > fails to get any response ... as described below :
If you edit the port numbers (listenPort or opennet listenPort) you will also need to move all the files which contain those numbers in their filenames. Did you? > > > On Mon, Dec 13, 2010 at 4:53 AM, <arra...@gmx.net> wrote: > > > > > Anyhow, my node exhibits some strange behaviour lately: > > > > > > One day, it sits there, and "annouces" for half an hour, without > > > receiving any reply. After manually updating to 1309, then 1310 > > > there's no change for several days. (that's when I sent the log file). > > > > > > Next day, without any change, just started the PC in the morning as > > > ususal, it connects fine within 2 minutes. > > > > > > Next day, it sits there for 2 hours, "announcing" and claiming that it > > > doesn't know if the opennet-port 64782 is forwarded or not (which it > > > is). > > > > I wouldn't be too worried about the node not knowing about the port > > being forwarded if you are sure you configured it. > > As soon as it connects, it realises the NATed port just fine. > But that happens only sparingly ... most times the node simply cannot > connect at all ... Are you 100% sure it's not a networking problem? Does it ever manage to connect to any seeds and do announcements, however unsuccessful, according to wrapper.log? > > > > NO change to router, PC or whatever. > > > > > > A look into the latest log shows that the node insists on trying IP6 > > > (which isn't installed on my machine), and does not get any replies to > > > its announcements, and maybe lots more what I don't understand ;-) > > > > I'm guessing you are running Windows Vista or Seven which iirc enable > > IP6 by default... > > > Guessed wrong ;-) > It's WinXP Prof SP3, with dedicated Admin/User account. > I'm starting the freenet service by running the management console as > admin, and connect with the browser from the user account as usual. > And there's nothing ip6 installed ... It should be harmless. It's not that easy to detect whether IPv6 is enabled so we just assume it is since failing to send packets over it is harmless. > > > I'm not sure, but try looking in your Freenet.ini file for the lines > > node.opennet.bindTo=0.0.0.0 and node.bindTo=0.0.0.0 These are IP4 type > > addresses, if you have longer ones like 0:0:0:0:0:0:0:1 you will need to > > shutdown your node and edit those lines to only have the IP4 style. > > Those looked ok (0.0.0.0 only), and I went and removed all ip6 entries > from the fproxy, fcp etc. entries as well - to no avail: > > The node still does not connect after running 2 hours straight, and > fills the log with entries like this (and only this): > -------------------------------------------------------- > Dez 16, 2010 12:35:37:531 (freenet.node.PeerManager, Scheduled job: > freenet.node.packetsende...@7770d(102), NORMAL): Connected: 0 Routing > Backed Off: 0 Too New: 0 Too Old: 0 Disconnected: 14 Never > Connected: 10 Disabled: 0 Bursting: 0 Listening: 0 Listen Only: 0 > Clock Problem: 0 Connection Problem: 0 Disconnecting: 0 > > Dez 16, 2010 12:35:37:593 (freenet.io.comm.UdpSocketHandler, > PacketSender thread for 60940, NORMAL): Error while sending packet to > IPv6 address: 2a01:e35:243b:a2b0:604f:a85d:275e:cb55:10559: > java.net.SocketException: Protocol not allowed > > Dez 16, 2010 12:35:39:218 (freenet.io.comm.UdpSocketHandler, > PacketSender thread for 60940, NORMAL): Error while sending packet to > IPv6 address: 2001:0:4137:9e76:3429:1598:63dd:5f9a:5813: > java.net.SocketException: Protocol not allowed > > Dez 16, 2010 12:35:42:625 (freenet.io.comm.UdpSocketHandler, > PacketSender thread for 60940, NORMAL): Error while sending packet to > IPv6 address: 2001:0:4137:9e76:64:17e5:b489:dfc3:48449: > java.net.SocketException: Protocol not allowed > --------------------------------------------------------- > > > > The ROUTER log says my PC is sending packets on port 1026, which it > > > drops because it's not allowed to. As soon as I stop the freenet > > > service, those strange packets disappear ... so most likely it IS the > > > node sending on a port that he isn't configured to use?! I wonder why your router has a problem with port 1026 anyway? I mean, only 1 to 1024 are normally regarded as reserved? > > > > This is probably the node trying to connect to a stun server to resolve > > it's IP address. > > There's nothing in the logs about this - and is this configurable > somehow? Yes, you can either use (load) the STUN plugin or not. > > Is this adress resolving somehow blocking all Ip4 connection making? > > Port 1026 is and ALWAYS WAS closed on the router for this machine, so > why did it work some time ago, and why did it stop working even before > I updated to 1309, and why did it work for some time 4 days ago, but > not today (again no changes to router or PC made ...) ?!?! Sounds like a networking problem on your end. No other obvious ideas except maybe try to watch the network traffic, see what packets are being sent/received. :|
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
