zlatinb
I can't bootstrap the i2pd part of the testnet now
zlatinb
what happens is when a node comes up it does a peer test with itself and makes itself firewalled, which means it does not publish the ip in the RI
zlatinb
which means I can't load the reseeder
zzz
zlatinb, did you see my comments on the wiki?
zlatinb
yeah I did that
zzz
also, I didn't mention it because I thought I was going to test it on my lxc, but I never got to it... I did hopefully fix the NTCP-only thing
zlatinb
saw that too, thanks
zlatinb
but as it stands now I can't do any interop testing
zzz
not surprising there's still some gotchas with i2pd on testnet
zzz
or is this a new problem?
zlatinb
it's either new or somehow it didn't happen last time
zlatinb
there is a very short interval of time during which the RI on disk is good, i.e. contains a valid NTCP address
zlatinb
maybe I was lucky last time
zzz
so it's peer testing with itself before it knows any peers?
zlatinb
I just know I see that it establishes an SSU session with itself, then sends a peer test
zzz
that sounds like a flat-out bug
zlatinb
that throws it back into "Testing" state and erases the address from the RI, replacing it with itself as an introducer
zzz
once you connect to yourself, chaos comes next
zlatinb
zzz orignal: Test report here git.idk.i2p/i2p-hackers/i2p.i2p/-/wikis/I2P-I2Pd-interoperability-testnet-scenarios
zzz
well done zlatinb, I think it's definitely worth it, especially since you found a bug
zzz
NTCP-only testnet testing/fixing on my list for the next release
zzz
to make testing easier next time, hopefully you can work with i2pd to add a config option to allow local IPs
orignal
good