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
