On Dec 28, 2007, at 7:41 PM, robert at freenetproject.org wrote: > Author: robert > Date: 2007-12-29 01:41:06 +0000 (Sat, 29 Dec 2007) > New Revision: 16833 > > Modified: > trunk/freenet/src/freenet/node/PeerNode.java > Log: > maybe help wont-fetch-ark deadlock
I just recently noticed that two of my nodes on the same lan have not connected to each other in weeks. After a bit of investigating (and trudging through much logging) I located four symptoms. Keep in mind that both nodes (A & B) are connected to freenet-at-large: (1) 'A' does not ever fetch arks, but 'B' does? > A sees B as v1090 (old & incompatible, does not fetch ark as > verifiedIncompatibleVersion is set w/o handshake) > B sees A as v1096 (the newest, newer than last connection) I think that I have fixed this in r16833-4 (2) Both nodes attempt to handshake, but both are rejected for an odd cause. AFIACS the furthest point into authentication they get is this: > Invalid data length 43557 (145) in tryProcessAuth Which appears to mean that the data was not decrypted with the right key. (3) Insane values for time period since last-packet (fixed in r16832) (4) Re-adding node B's reference to node A repairs the connection, but then node A sees to references to B (one that works and one that does not). So... that adding B's reference again succeeded (in #4) and #2 suggests a bad key, I suppose that means that sometime at the transition to 1091 node B changed it's one or more of it's keys, and node A never caught it? -- Robert Hailey
