Title: Connect bitcoind to i2p network - problems with i2pd Post by: RequestPrivacy on June 28, 2022, 08:12:56 AM I want to support bitcoin over the i2p network and minimize my reliance on tor and its continued DDoS attacks.
As I see it, my current problem is running i2p, specifically the i2pd implementation, NOT a problem with my bitcoind (running v.22). But since the intention is to use i2p primarily for bitcoin, I will post my question here in the forum. What I did up until now I tried to follow 402 Payment Requireds guide https://bitcointv.com/w/tdi2BXqPF2fhj6991Qn8vM (https://bitcointv.com/w/tdi2BXqPF2fhj6991Qn8vM) (thank you) to enable bitcoin with i2p. I didn't add a new repository as suggested in his guide since I'm a bit hesitant to include third party ones. But the Debian repository of my Raspberry Pi 4 has an older v2.39 version of the i2pd included though. Once installed I added following lines to the bitcoin.conf file: Code: debug=i2p I pulled the i2p nodes from the bitcoin repository https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt (https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt). Then I did: Code: pi@debian:~ $ sudo systemctl enable i2pd and started bitcoind. Sadly no outbound connections where made via i2p. Troubleshooting I noticed that i2p kept quitting after a couple of minutes. Code: pi@debian:~ $ systemctl status i2pd In the logs a bunch of following output is provided (note, the first block was where I originally started i2pd first, the second block shows the output once I restart it now): Code: pi@debian:~ $ sudo cat /var/log/i2pd/i2pd.log If I try to acccess the i2pd router webconsole on 127.0.0.1:7070 it works but says my network is firewalled. Questions 1) Is somebody running bitcoind with i2pd? Is there the need to configure some i2pd conf files? 2) Do I need to open ports on the router of my home network? My intention would be to have only outgoing bitcoind traffic. Not sure why I would need open ports for incoming one - but maybe I don't understand how i2p works?! Title: Re: Connect bitcoind to i2p network - problems with i2pd Post by: NotATether on June 29, 2022, 05:49:21 AM The config directive to add nodes is called addnodes not addnotes (there is a d not a t).
Also, you should check if the nodes that you are directly connecting to are online, you can do this by either pinging the address, or attempt to directly make a connection to the I2P node by itself. Firewalls should not be blocking the control panel because it is hosted on localhost. But try disabling the firewall anyway and see what happens. Title: Re: Connect bitcoind to i2p network - problems with i2pd Post by: vv181 on June 29, 2022, 09:25:05 AM 1) Is somebody running bitcoind with i2pd? Is there the need to configure some i2pd conf files? I tried i2pd today, and I also notice it keeps quitting. Seems there is something wrong with ip2d v2.39 and Bitcoin Core. The last log before it got SEGV was: Code: 15:52:25@973/error - Garlic: Failed to decrypt message 2) Do I need to open ports on the router of my home network? My intention would be to have only outgoing bitcoind traffic. Not sure why I would need open ports for incoming one - but maybe I don't understand how i2p works?! Nope. Quote from: http://localhost:7657/help#reachabilityhelp I2P will work fine when firewalled, there is no reason for concern. When firewalled, the router uses "introducers" to relay inbound connections. You might want to try to update it to the latest version. Or just use the official implementation, I2P Router, I do use it, and so far there haven't been any problems. The installation could be done by following: https://geti2p.net/en/download/debian#debian. Then enable the SAM on the configuration page(http://127.0.0.1:7657/configclients). With the corrected bitcoin config, you should be good to go. Title: Re: Connect bitcoind to i2p network - problems with i2pd Post by: RequestPrivacy on June 29, 2022, 02:50:07 PM The config directive to add nodes is called addnodes not addnotes (there is a d not a t). Good catch, thanks for that. I disabled all of them now though, since I wanted to try if bitcoind finds nodes without my help once I got my i2p problem sorted out (I initially added them bc I thought i2pd may need some traffic to prevent the automatic stopping of the i2pd.service. Turns out that isn't true and the problem was rooted in the i2pd since the standard I2P router works).You might want to try to update it to the latest version. Or just use the official implementation, I2P Router, I do use it, and so far there haven't been any problems. I followed your provided resources and installed the official java I2P router and enabled the SAM bridge. The i2p side of things seem to work now. I can see bandwidth and memory usage, as well as peer count and tunnels in the I2P Router Console. Thanks for that!The installation could be done by following: https://geti2p.net/en/download/debian#debian. Then enable the SAM on the configuration page(http://127.0.0.1:7657/configclients). With the corrected bitcoin config, you should be good to go. My bitconid seems to prefer onion sites though. I haven't seen it to connect to i2p bitcoin nodes i.e. Code: bitcoin@debian:~/.bitcoin $ bitcoin-cli -addrinfo How does bitcoind choose to distribute peers across networks? Do I have to change the available bandwidth of my i2p router so it can "compete" better with e.g. tor? Title: Re: Connect bitcoind to i2p network - problems with i2pd Post by: vv181 on June 30, 2022, 07:01:25 PM Do I have to change the available bandwidth of my i2p router so it can "compete" better with e.g. tor? I don't think that would do much help. I guess that's more on the current availability of i2p peers on bitcoin rather than on the i2p itself. |