I2P connection fails with "failed to listen on ip"

[0xf0xx0]

After a couple minutes of operation, libtorrent seems to drop the connection to the i2p host. qBittorrent fails with Failed to listen on IP. IP: "0.0.0.0". Port: "I2P/0". Reason: "End of file" in its logs. Similarly, client_test errors with a "Timed out".

to reproduce:

1. start client_test or your favorite i2p-aware torrent client.
2. torrent something. anything works, ive been using the i2p+ torrent as a test.
3. leave it running. after ~5-10 mins the client will fail.

libtorrent version (or branch): c2012b0
platform/architecture: Linux x86_64
compiler and compiler version: GCC 13.1.1

[Vort]

In previous issue you said that you use --i2p_hostname="localhost" option. I tried it and can't get it to work. Maybe that's a reason? Can you try --i2p_hostname=127.0.0.1 instead?
It may be also important to know what I2P software you are using - i2pd or java i2p, versions may be important too. I don't see such behaviour with i2pd 2.48.0, but I did not tested java i2p yet.

[0xf0xx0]

In previous issue you said that you use --i2p_hostname="localhost" option. I tried it and can't get it to work. Maybe that's a reason? Can you try --i2p_hostname=127.0.0.1 instead?

ill try that and see what happens.

It may be also important to know what I2P software you are using - i2pd or java i2p, versions may be important too. I don't see such behaviour with i2pd 2.48.0, but I did not tested java i2p yet.

ah, thanks for reminding me, i went and tested java i2p 2.3.0 and i wasn't able to get libtorrent to connect to SAM, even though i was able to manually netcat and create a session.

i also run i2pd 2.48.0, i'll give my config a reset and see if its something i may have misconfigured.

E: testing a fresh i2pd config, it's fine so far. i have a feeling my connection was being reset serverside...

[Vort]

i went and tested java i2p 2.3.0

I decided to test it too, but for some reason developers did not published I2P Easy Install Bundle for 2.3.0, so I downloaded I2P-Easy-Install-Bundle-2.2.0.exe instead.
I enabled SAM, started client_test, downloaded 37533aa1c010678587a4a2966e29ad56f0bd0043 torrent, waited for 10 minutes - everything went fine.
What was not fine is that Java I2P failed to remember autostartup settings for SAM and when I restart I2P, it starts without SAM.
Another difference from your test is that I used Windows for test, not Linux - it may be that bug is specific to OS type.

[0xf0xx0]

it may be...

using my remote i2pd peer is stable so far. Looking at the i2pd logs, SAM reports that the acceptor was reset each time it fails. This seems to be related to #7453, as i2pd will accept a new connection, but I'm still unable to pin down why it resets in the first place...