On Sep 16, 2009, at 10:25 AM, Evan Daniel <eva...@gmail.com> wrote: > Message: 6 > Date: Wed, 16 Sep 2009 12:46:22 -0400 > From: Evan Daniel <eva...@gmail.com> > Subject: Re: [freenet-support] My node keeps loosing all it's opennet > connections > To: support@freenetproject.org > Message-ID: > <4f9383510909160946r5bbe70f6rc6eb5069e95...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Sep 16, 2009 at 11:10 AM, Matthew Toseland > <t...@amphibian.dyndns.org> wrote: >> On Tuesday 15 September 2009 15:15:47 freenet wrote: >>> Every few days my node just looses all it's connections. >>> >>> Restarting the node does not solve the problem. Usually I have to >>> shut >>> the node down completely for about two days. When I restart it, >>> after >>> about 10 minutes it starts getting connections. One time I >>> downloaded >>> a new seednodes.fref file and that seemed to get the connections >>> started again. >>> >>> I think there is a bug where the node keeps trying to contact one or >>> two nodes on IP addresses that are no longer valid. For example, >>> this >>> time I see the following two errors over and over and over and over >>> again in the logs: >>> >>> Sep 15, 2009 04:10:05:527 (freenet.io.comm.UdpSocketHandler, >>> PacketSender thread for 60973, ERROR): Error while sending packet to >>> 128.222.3.103:18143: java.io.IOException: No route to host >>> java.io.IOException: No route to host >>> ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) >>> ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) >>> ? ? ? at >>> freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: >>> 247) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: >>> 1781) >>> ? ? ? at >>> freenet >>> .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: >>> 1739) >>> ? ? ? at >>> freenet >>> .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: >>> 2876) >>> ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) >>> ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) >>> ? ? ? at java.lang.Thread.run(Thread.java:637) >>> ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) >>> Sep 15, 2009 04:10:10:555 (freenet.node.PeerManager, PacketSender >>> thread for 60973, NORMAL): Connected: 0 ?Routing Backed Off: 0 ?Too >>> New: 0 ?Too Old: 0 Disconnected: 14 ?Never Connected: 18 ? >>> Disabled: 0 >>> Bursting: 1 ?Listening: 0 ?Listen Only: 0 ?Clock Problem: 0 >>> Connection Problem: 0 ?Disconnecting: 0 >>> Sep 15, 2009 04:10:13:471 (freenet.io.comm.UdpSocketHandler, >>> PacketSender thread for 60973, ERROR): Error while sending packet to >>> 5.4.174.104:60115: java.io.IOException: No route to host >>> java.io.IOException: No route to host >>> ? ? ? at java.net.PlainDatagramSocketImpl.send(Native Method) >>> ? ? ? at java.net.DatagramSocket.send(DatagramSocket.java:612) >>> ? ? ? at >>> freenet.io.comm.UdpSocketHandler.sendPacket(UdpSocketHandler.java: >>> 247) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendPacket(FNPPacketMangler.java:1794) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendAuthPacket(FNPPacketMangler.java: >>> 1781) >>> ? ? ? at >>> freenet >>> .node.FNPPacketMangler.sendAnonAuthPacket(FNPPacketMangler.java: >>> 1739) >>> ? ? ? at >>> freenet >>> .node.FNPPacketMangler.sendJFKMessage1(FNPPacketMangler.java:839) >>> ? ? ? at >>> freenet.node.FNPPacketMangler.sendHandshake(FNPPacketMangler.java: >>> 2876) >>> ? ? ? at freenet.node.PacketSender.realRun(PacketSender.java:247) >>> ? ? ? at freenet.node.PacketSender.run(PacketSender.java:126) >>> ? ? ? at java.lang.Thread.run(Thread.java:637) >>> ? ? ? at freenet.support.io.NativeThread.run(NativeThread.java:100) >>> >>> >>> My Internet connection is working fine. Those two IP addresses are >>> not >>> reachable and the node is stuck in a loop trying to get to them. One >>> other temporary fix was to edit the seednodes.fref file and remove >>> the >>> nodes with the unreachable IP addresses. >>> >>> Freenet 0.7.5 Build #1233 build01233 >>> Freenet-ext Build #26 r23771 >>> >>> # Java Version: 1.6.0_15 >>> # JVM Vendor: Apple Inc. >>> # JVM Version: 14.1-b02-92 >>> # OS Name: Mac OS X >>> # OS Version: 10.5.8 >>> # OS Architecture: x86_64 >>> >>> Sure seems like a serious bug to me. >> >> Sounds like a serious bug in your internet connection. We do indeed >> repeatedly send handshaking packets to all our peers' IP addresses >> and this is normal and expected behaviour if two of them have >> invalid addresses. > > The first of those IP addresses listed looks like my node. I'm not > sure why it made that one public; it should be using > evanbd.dyndns.org. That IP is indeed not routable to the outside > world; apparently my noderef is from when I was running on my father's > strangely configured network (something about needing to be able to > VPN into networks that collectively used all the various > reserved-for-private nets address spaces, so he chose something > unreserved that he knew to be unroutable). > > My updated noderef is below. I've manually examined it for obvious > errors. I've left the ip address in it; that is the correct external > ip for my node. However, it's a dhcp address (though an infrequently > changing one), so it should probably removed to leave only the dyndns > name if that won't cause any problems. > > Evan Daniel > > opennet=true > identity=hP0uNEAg4CgfqeovGWyB0N2EbOy2WpnD6bihF1kOP3k > lastGoodVersion=Fred,0.7,1.0,1231 > sig > = > 00836e49c913c22ef4308e6a372a9e1835c04b1d51debfe6e4373a07bfccb99072,3e6c1c4be3c306a681d6e95194c45c11c161f7df147043b8de3c14f353e56b42 > version=Fred,0.7,1.0,1233 > dsaPubKey.y=fYa~LlT1nhk6pwTO9JH2cXij31vb7hDBClqHPXklROVIue3gtktZhvjBfNzop6FyBojzhOPOpiwqlQfnUPwdjt~aVg~5Ws7OgUxl4hp9BdXOaQbdYM9W~6XtnMx3a4jiyTAkJUU8rIA8VWPUsNChGx1KVwNU2FP-rKJzWeG-sgXpLBF657OZ1c1OujYnd1aBM6XwhJcSdicVi-SmXr5OnDbSnFQI6Jv1wFn3vMIYIOjAdVZ03VnzhmMdCDvUvUIG9Q66xKJe05S0D90~LMfIeRRZOFNa8lz3pJRbby1OR1K6cMdsXIEgt2PtJ1BDYw8vGt-ee-k2KBDSDSeg--NcKw > physical.udp=evanbd.dyndns.org:18143;71.65.197.250:18143 > dsaGroup.g=UaRatnDByf0QvTlaaAXTMzn1Z15LDTXe-J~gOqXCv0zpz83CVngSkb-- > bVRuZ9R65OFg~ATKcuw8VJJwn1~A9p5jRt2NPj2EM7bu72O85- > mFdBhcav8WHJtTbXb4cxNzZaQkbPQUv > ~ > gEnuEeMTc80KZVjilQ7wlTIM6GIY > ~ > ZJVHMKSIkEU87YBRtIt1R > ~ > BJcnaDAKBJv > ~ > oXv1PS > -6iwQRFMynMEmipfpqDXBTkqaQ8ahiGWA41rY8d4jDhrzIgjvkzfxkkcCpFFOldwW8w8MEecUoRLuhKnY1sm8nnTjNlYLtc1Okeq > > -ba0mvwygSAf4wxovwY6n1Fuqt8yZe1PDVg > dsaGroup.q=ALFDNoq81R9Y1kQNVBc5kzmk0VvvCWosXY5t9E9S1tN5 > dsaGroup.p=AIYIrE9VNhM38qPjirGGT-PJjWZBHY0q- > JxSYyDFQfZQeOhrx4SUpdc~SppnWD~UHymT7WyX28eV3YjwkVyc~-- > H5Tc83hPjx8qQc7kQbrMb~CJy7QBX~YSocKGfioO- > pwfRZEDDguYtOJBHPqeenVDErGsfHTCxDDKgL2hYM8Ynj8Kes0OcUzOIVhShFSGbOAjJKjeg82XNXmG1hhdh2tnv8M4jJQ9ViEj425Mrh6O9jXovfPmcdYIr3C > > ~3waHXjQvPgUiK4N5Saf~FOri48fK-PmwFZFc- > YSgI9o2-70nVybSnBXlM96QkzU6x4CYFUuZ7-B~je0ofeLdX7xhehuk > ark > .pubURI > = > SSK > @hkXLMqgdrQ4GCdaa3sh0Yx8knHp5ceV5K3GNXrVVsYU > ,SjgGDqmUmCD7kfiE6TiFrpk4UlNY-bZ5YdbFuQ2Pgbc,AQACAAE/ark > ark.number=350 > auth.negTypes=2;4 > End
But is it normal for all connections to stop functioning and the node to only try to contact the two nodes that it can not contact? Still seems like a bug. A guess: Both those noderefs seem to be dynamic DNS type domain names. If the node's IP address changes and the dynamic DNS entry is not correctly updated, it triggers some bug where another node only tries to contact those two seednodes. I entered Evan's new node ref into my seednodes.fref file. The other unreachable node ref has been deleted from the seednodes.fref file. We'll see what happens. Paul _______________________________________________ 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
