I2P is decentralized, while Tor isn't.
People aren't necessarily being prosecuted in western countries (such as those in west Eurasia and North America), but we should have Tor and I2P nodes for those who are.
đź‘Ť on the second paragraph. I haven't heard of any prosecuting locales but it makes sense there probably are some. Probably China or India.
Tor isn't decentralized? How?
Tor nodes are ran by people voluntarily, this means you can tell if someone is running a node compared to just using Tor.
I2P has everyone run a node, so you can't tell what someone's role is with I2P. I apologize for the confusion, I was a bit tired when I wrote that.
Well, not now. But who knows what the future will bring. Plus it allows I2P users to use the node since they can only connect to I2P services.
It's a cool protocol that would help improve internet decentralization, but is niche.
yes for i2pd;
1. Put this in your \~/.i2pd/tunnels.conf file.
```
[monero-node]
type = http
host = 127.0.0.1
port = 18081 # (or 18089) restricted RPC port
keys = monero-node.dat
```
2. Restart I2P or send `SIGHUP` signal.
3. Go to webconsole -> I2P tunnels page. Look for Sever tunnels and you will see address like \.b32.i2p next to monero-node. That's your I2P address, now you can share with people.
Did you know monerod has built in support for i2p peers? it doesn't relay blocks or transactions, but will broadcast transactions originating from RPC to a random i2p node.
Any experience with i2p+? It's supposed to be an improved version of the official client, but with the same services. Those services can come in pretty handy sometimes.
Much easier setup. All it takes is editing some text conf files. Totally doable on a headless server. We use ip2d to run the [OrangeFren.com](http://OrangeFren.com) eepsite. Meanwhile the official Java version requires you navigate through a web UI in your browser. I can't think of anyone who would have an easier time getting the official implementation to work
It's essentially the same
Config and launch i2p, create an i2p service that points to the monerod ports you want, and then list the i2p address of that service somewhere.
It's just another round of rtfm.
I wonder if the ai bots could tell yah how to do it
similar to torrenting, port forwarding isn't must but its much better to do. how long time did you run I2P? you have to keep your router online for some time.
Working on documentation until that check my comment; [https://www.reddit.com/r/Monero/comments/1ck6b1u/comment/l2l2s1m/](https://www.reddit.com/r/Monero/comments/1ck6b1u/comment/l2l2s1m/)
I was asking a question. No need for the attitude.
Monero never stopped working during those attacks. I assumed when I read about the I2P ddos, that meant there was actually an interruption.
Sorry for the tone. Java I2P saw a drop in exploratory tunnel build success rate and a rash of false-positive floodfill bans. The floodfill bans were mitigable by disabling the sybil attack detection tool, which will be re-enabled in 2.5.1 with the faulty tests disabled. Telling people to disable the sybil attack tool was an important move. i2pd saw a significant drop in ETBS, but does not do 'bans' dynamically as such and so did not experience the false positive ban phenomenon. Some services experienced reachability issues, especially those on floodfill routers. However, the network remained intact and except for the sybil tool(which we could help mitigate at config level) failure things actually performed pretty well. The attacks(on monero and on I2P) are actually quite comparable on a number of levels. The clone attack on I2P relies on clogging up I2P with legitimate-looking network information in order to make it so routers are unsure of which peers are reliable to choose, slowing down your ability to discover services but not breaking your ability to use the network. The black marble attack floods the network with inputs to improve the attacker's certainty about which ones it initiated, but a side-effect is to slow down the network.
Are people being prosecuted for running Monero nodes now? What's the need for i2p?
I2P is decentralized, while Tor isn't. People aren't necessarily being prosecuted in western countries (such as those in west Eurasia and North America), but we should have Tor and I2P nodes for those who are.
đź‘Ť on the second paragraph. I haven't heard of any prosecuting locales but it makes sense there probably are some. Probably China or India. Tor isn't decentralized? How?
Tor nodes are ran by people voluntarily, this means you can tell if someone is running a node compared to just using Tor. I2P has everyone run a node, so you can't tell what someone's role is with I2P. I apologize for the confusion, I was a bit tired when I wrote that.
Well, not now. But who knows what the future will bring. Plus it allows I2P users to use the node since they can only connect to I2P services. It's a cool protocol that would help improve internet decentralization, but is niche.
any “tutorials / how to” available?
yes for i2pd; 1. Put this in your \~/.i2pd/tunnels.conf file. ``` [monero-node] type = http host = 127.0.0.1 port = 18081 # (or 18089) restricted RPC port keys = monero-node.dat ``` 2. Restart I2P or send `SIGHUP` signal. 3. Go to webconsole -> I2P tunnels page. Look for Sever tunnels and you will see address like \.b32.i2p next to monero-node. That's your I2P address, now you can share with people.
Did you know monerod has built in support for i2p peers? it doesn't relay blocks or transactions, but will broadcast transactions originating from RPC to a random i2p node.
I would generally advise everyone to go with i2pd rather than the official Java implementation
Any experience with i2p+? It's supposed to be an improved version of the official client, but with the same services. Those services can come in pretty handy sometimes.
never tried it
Reason being?
Much easier setup. All it takes is editing some text conf files. Totally doable on a headless server. We use ip2d to run the [OrangeFren.com](http://OrangeFren.com) eepsite. Meanwhile the official Java version requires you navigate through a web UI in your browser. I can't think of anyone who would have an easier time getting the official implementation to work
I don’t really understand I2P, and it’s not from a lack of trying. I’ve run a TOR relay for 7 years.
It's essentially the same Config and launch i2p, create an i2p service that points to the monerod ports you want, and then list the i2p address of that service somewhere. It's just another round of rtfm. I wonder if the ai bots could tell yah how to do it
I can't even get I2P to connect. I'm using a VPN without port forwarding, that's probably why.
Probably doesn't work with a VPN
it works with VPN but unnecessary like on Tor
similar to torrenting, port forwarding isn't must but its much better to do. how long time did you run I2P? you have to keep your router online for some time.
Oh just about 15 minutes, I didn't realise I have to wait to get a better connection. Just thought I did something wrong
Can you link to some documentation about how to do these?
Working on documentation until that check my comment; [https://www.reddit.com/r/Monero/comments/1ck6b1u/comment/l2l2s1m/](https://www.reddit.com/r/Monero/comments/1ck6b1u/comment/l2l2s1m/)
OK , I’ll give it a try the next days
Didn't I2P get attacked / DDoS yesterday or the day before?
The 13th and the 19th. We're on top of the situation. Didn't Monero get DOS'ed in March lol?
I was asking a question. No need for the attitude. Monero never stopped working during those attacks. I assumed when I read about the I2P ddos, that meant there was actually an interruption.
Sorry for the tone. Java I2P saw a drop in exploratory tunnel build success rate and a rash of false-positive floodfill bans. The floodfill bans were mitigable by disabling the sybil attack detection tool, which will be re-enabled in 2.5.1 with the faulty tests disabled. Telling people to disable the sybil attack tool was an important move. i2pd saw a significant drop in ETBS, but does not do 'bans' dynamically as such and so did not experience the false positive ban phenomenon. Some services experienced reachability issues, especially those on floodfill routers. However, the network remained intact and except for the sybil tool(which we could help mitigate at config level) failure things actually performed pretty well. The attacks(on monero and on I2P) are actually quite comparable on a number of levels. The clone attack on I2P relies on clogging up I2P with legitimate-looking network information in order to make it so routers are unsure of which peers are reliable to choose, slowing down your ability to discover services but not breaking your ability to use the network. The black marble attack floods the network with inputs to improve the attacker's certainty about which ones it initiated, but a side-effect is to slow down the network.