this post was submitted on 17 Dec 2024
13 points (93.3% liked)

The Invisible Internet Project

1476 readers
8 users here now

I2P Community Edition

This isn't the official I2P channel, if you want go there then you can find it in the links below.

Rules

"Don't be a dick" - Wil Wheaton

General

Media:

File Hosting and Pastebins

Torrents

Social Networks and Microblogging

Exploring I2P

I2P Name Registries

Search engines

IRC

Irc2P comes pre-configured with I2P. To connect with other networks, please follow this tutorial.

Syndie

An open source system for operating distributed forums in anonymous networks

Inproxies

You can use inproxies to surf the I2P network without having to have an I2P router.

Follow us on Twitter

founded 2 years ago
MODERATORS
13
submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/i2p
 

I used i2p from InviZible Pro (F-Droid).

I was trying to connect my Monero wallet to a Monero RPC Damon that somebody I know runs and while it did connect the absolute best speed I could ever achieve through it was 45KiB/s. I changed no settings at all and just used the defaults. Turned it on and had 33 client tunnels.

Tor usually gets me ~400KiB/s to the hs, but i thought i2p would be faster.

Edit: it used 2 hops as default and i left it that way.

top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 1 day ago (1 children)

I've never used this app, but it looks like its using i2pd, I would look for the i2pd.conf, and change the bandwidth flag from L (32kb/s) to like O (256kb/s) or P (2048kb/s), but performance may still not be very good if your router is firewalled.

But you might just be getting bad peers, the speed of a tunnel will be limited by its weakest peer, I would try increasing tunnel quantity on both sides, and allowing inbound traffic on both routers if they arent un-firewalled already, if possible.

[–] [email protected] 1 points 1 day ago (1 children)

I really don't feel as though I should have to change the default settings in order to make the experience good enough to be usable. That seems a bit counterintuitive. Also, wouldn't increasing the tunnel hops, make the tunnel longer and therefore slower, because of going through more peers.

[–] [email protected] 1 points 1 day ago (1 children)

Increasing the tunnel length add more peers per tunnel, but increasing the tunnel quantity will add more tunnels, which will allow more throughput.

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago) (1 children)

Oh, my bad. I misunderstood when you said tunnel quantity and was thinking you were talking about tunnel hops. Unfortunately, I can't do anything about the firewall aspect because over IPv4 I am behind CGNAT and on IPv6 I absolutely refuse to turn on UPNP of any kind because UPNP is dangerous to have enabled and I haven't manually forwarded any ports

[–] [email protected] 1 points 1 day ago (1 children)

No worries, hopefully increasing the tunnel quantity will get you acceptable speeds, I could be missing something, but thats all I can think of besides allowing inbound traffic.

Something I forgot to mention, there is the Java I2P router, its availiable in the default f-droid repo, I havent tested it out on Android, but it has a fancy gui on desktop where everything can be configured, it some blocklists of tor exit nodes and stuff, I think that helps performance, I'm not totally sure tho, I dont use the Java versions, they have too many buttons and switches, and its kinda overwhelming for me.

[–] [email protected] 2 points 1 day ago* (last edited 1 day ago) (1 children)

I didn't see anything about tunnel quantity, specifically for the socks proxy. I did see something about it for HTTP, but I'm not using HTTP.

[httpproxy]
enabled = true
address = 127.0.0.1
port = 4444
inbound.length = 1
inbound.quantity = 5
outbound.length = 1
outbound.quantity = 5
signaturetype=7
i2cp.leaseSetType=3
i2cp.leaseSetEncType=0,4
keys = proxy-keys.dat
addresshelper = true
#outproxy = http://false.i2p
## httpproxy section also accepts I2CP parameters, like "inbound.length" etc.

[socksproxy]
enabled = true
address = 127.0.0.1
port = 4447
keys = socks-proxy-keys.dat
#outproxy.enabled = false
#outproxy = 127.0.0.1
#outproxyport = 9050
##socksproxy section also accepts I2CP parameters, like inbound.length etc

However, since that socks proxy section says that it takes I2CP commands, I wonder if I could just paste the info from the HTTP part above.

[–] [email protected] 1 points 1 day ago (1 children)

Yes, you can take the quantity and length options from the http proxy and just paste it into the socks proxy section, I think tunnel quantity can go up to 16, I recommend 8 for high bandwidth stuff like torrenting, but it will use more CPU and battery, but lowering length from the default of 3 to 1 should help a lot.

[–] [email protected] 1 points 23 hours ago (1 children)

I got no help from that whatsoever. It's still extremely slow even after letting my clients sit there and integrate for over 30 minutes and seeing over a thousand routers.

[–] [email protected] 1 points 21 hours ago

Idk then, I've easily gotten speeds of upto 1.2 MiB/s while torrenting, uploading and downloading, I just downloaded a book from a webserver with wget to test my speed through the HTTP proxy, and I got about 150-300 KB/s throughout the whole transfer, I'm using the default settings of 3 hops, and my router isnt firewalled, no clue what the servers settings are.