@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+cims
+dr|z3d
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme3
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
zzz
eyedeekay, how is ntcp2 handshake going?
eyedeekay
Better than it has in 2 years, I have intelligible failures on both sides when I try to make go-i2p talk to Java I2P
zzz
nice
zzz
the key to debugging is to log the failure on the java side that pukes out the handshake state, and log it on your side in the same way
zzz
s/rs/e/re/ck/h/polykey, all in base64
zzz
then see what doesn't match
zzz
are you doing that?
eyedeekay
Right now I have all logging for ntcp enabled, it's a little noisy but I am grepping for the elements I get from the RI so I think so
zzz
look for "State at failure" which is a WARN
zzz
see that output?
eyedeekay
I do now, looks like it's in ./router/java/src/net/i2p/router/transport/udp/InboundEstablishState2.java
zzz
yeah but the code is in the toString() of various noise classes. no matter though
zzz
what you want to do is mave a routine to dump out the same data in the same format (i2p base64) on your side
zzz
then when something goes wrong, spit it out, look for mismatches in values on the other side
zzz
look in your logs to find an example
zzz
find one?
eyedeekay
At last, got it to show me one
eyedeekay
I see what you mean, this is helpful, I can use it to figure out what I should be looking at
zzz
yeah after doing this with i2pd on 4 different protocols, we got pretty good at it
zzz
look for mismatched values, work backwards, add the same logging to the intermediate steps, see where things diverged