i2pd: Speed is very slow

The webconsole reports speeds of up to 60 KiB/s even after letting i2pd run for days and with floodfill enabled. The only parameters I changed in the configuration file are bandwidth = X, daemon = true, floodfill = true and I also input a port number which I opened in the firewall. Network status varies from OK to sometimes Unknown, but if I restart the i2pd service it turns to OK, the firewall allows incoming connections to i2pd port so the NAT is unfiltered. Why then am I getting such low speeds?

About this issue

Original URL
State: closed
Created a year ago
Comments: 17 (9 by maintainers)

Most upvoted comments

Could this be due to some kind of error in my environment?

Enabling floodfill with NAT address makes no sense - i2pd will ignore such nodes.

How can I check this?

What exactly? Speed? Run http://speed-test.i2p, probably several times during different times of the day. Ask your friend to do the same. Compare results.

I forgot to attach the config & logs.

Low amount of transit on Firewalled nodes is known problem, your config won’t help to solve it.

Vort on Feb 6, 2024

is that the maximum I should expect?

It varies. Demand for tunnel count can be even higher than 5000 sometimes.

I’m still not satisfied with the speeds (less than 200 KiB/s)

It varies too. For me Transit speed is usually 500-2000 KiB/s.

And why is my tunnel creation success rate so low?

It may be because of two reasons:

It calculates slowly. This value starts to reflect reality after ~6 hours of uptime.
Your network may be slow and drop packets.

I suggest you to wait more with transittunnels = 5000. Most likely, both transit speed and success rate will go up within half of the day or so.

Vort on Jan 13, 2023