I2P: connection issues #23018

ghost commented at 5:16 PM on September 17, 2021: none

OS: Debian bullseye

My bitcoin.conf:

addnode=4hllr6w55mbtemb3ebvlzl4zj6qke4si7zcob5qdyg63mjgq624a.b32.i2p:0
addnode=6s33jtpvwzkiej3nff5qm72slgqljxhxn62hdt6m7nvynqsxqdda.b32.i2p:0
addnode=a5qsnv3maw77mlmmzlcglu6twje6ttctd3fhpbfwcbpmewx6fczq.b32.i2p:0
addnode=bitcornrd36coazsbzsz4pdebyzvaplmsalq4kpoljmn6cg6x5zq.b32.i2p:0
addnode=c4gfnttsuwqomiygupdqqqyy5y5emnk5c73hrfvatri67prd7vyq.b32.i2p:0
addnode=dhtq2p76tyhi442aidb3vd2bv7yxxjuddpb2jydnnrl2ons5bhha.b32.i2p:0
addnode=gehtac45oaghz54ypyopim64mql7oad2bqclla74l6tfeolzmodq.b32.i2p:0
addnode=h3r6bkn46qxftwja53pxiykntegfyfjqtnzbm6iv6r5mungmqgmq.b32.i2p:0
addnode=hnbbyjpxx54623l555sta7pocy3se4sdgmuebi5k6reesz5rjp6q.b32.i2p:0
addnode=i3hcdakiz2tyvggkwefvdjoi7444kgvd2mbdfizjvv43q7zukezq.b32.i2p:0
addnode=jz3s4eurm5vzjresf4mwo7oni4bk36daolwxh4iqtewakylgkxmq.b32.i2p:0
addnode=kokkmpquqlkptu5hkmzqlttsmtwxicldr4so7wqsufk6bwf32nma.b32.i2p:0
addnode=kvrde7mcgjhz3xzeltwy4gs2rxdfbnbs2wc67mh2pt43wjmjnmbq.b32.i2p:0
addnode=shh2ewyegnuwnmdse5kl5toybdvzkvk2yj4zcowz6iwhhh3ykdfa.b32.i2p:0
addnode=wwbw7nqr3ahkqv62cuqfwgtneekvvpnuc4i4f6yo7tpoqjswvcwa.b32.i2p:0
addnode=zsxwyo6qcn3chqzwxnseusqgsnuw3maqnztkiypyfxtya4snkoka.b32.i2p:0
i2psam=127.0.0.1:7656
i2pacceptincoming=1
debug=i2p

After bitcoind restart, it can't connect to any i2p peers, the following messages noticed in the bitcoind output:

2021-09-17T16:38:26Z I2P: Error connecting to a5qsnv3maw77mlmmzlcglu6twje6ttctd3fhpbfwcbpmewx6fczq.b32.i2p:0: "STREAM STATUS RESULT=CANT_REACH_PEER MESSAGE="Connection timed out""
...
2021-09-17T16:39:48Z I2P: Error connecting to dhtq2p76tyhi442aidb3vd2bv7yxxjuddpb2jydnnrl2ons5bhha.b32.i2p:0: "STREAM STATUS RESULT=CANT_REACH_PEER MESSAGE="Connection timed out""
...
2021-09-17T16:42:10Z I2P: Error connecting to shh2ewyegnuwnmdse5kl5toybdvzkvk2yj4zcowz6iwhhh3ykdfa.b32.i2p:0: Unexpected reply to "NAMING LOOKUP NAME=shh2ewyegnuwnmdse5kl5toybdvzkvk2yj4zcowz6iwhhh3ykdfa.b32.i2p": "NAMING REPLY RESULT=KEY_NOT_FOUND NAME=shh2ewyegnuwnmdse5kl5toybdvzkvk2yj4zcowz6iwhhh3ykdfa.b32.i2p"

'bitcoin-cli -netinfo 4' showing no i2p peers.

After another restart, bitcoind connects to i2p peers and I see them in 'bitcoin-cli -netinfo 4' output. However, I don't see any i2p inbound connections.

        ipv4    ipv6   onion     i2p   total   block  manual
in        12       0       0       0      12
out       10       0       0       8      18       2       8
total     22       0       0       8      30

My node is behind the NAT. I've forwarded 8333 port and TCP/UDP I2P port. Is there anything else I should do to see incoming i2p peers?

unknown added the label Bug on Sep 17, 2021

jonatack commented at 5:30 PM on September 17, 2021: member

Which I2P router/version are you using? There are not yet many I2P peers, but if you ping me on IRC (nick jonatack) I'll try to connect so that you see an inbound peer.

ghost commented at 5:51 PM on September 17, 2021: none

I'm using the official Java router 1.5.0.

jonatack commented at 6:08 PM on September 17, 2021: member

We're connected since ten minutes :partying_face:

ghost commented at 6:10 PM on September 17, 2021: none

jonatack made a connection to my node and now I see one i2p peer on my end. Error messages in bitcoind output seems i2p router related. Closing the issue.

unknown closed this on Sep 17, 2021

DrahtBot locked this on Oct 30, 2022