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.

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.

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

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.

Tor hidden service