I2P SAM parameters (within Docker)

[deavmi]

I am putting together an integrated Docker compose service file to satisfy my needs. One of these things includes the fact that I will be running rnsd and i2pd in seperate containers. The reticulum daemon, when setting up a type = I2PInterface assumes localhost address and a fixed SAM port.

Would it be possible to get these two parameters as options:

[[I2p Interface]]
type = I2PInterface
sam_addr = i2pd.machine
sam_port = 2121

[faragher]

I know Mark's been working on support for externally defined (not part of the core package) interfaces, so this may be addressed soon. That being said, it gets the address from an environment variable called I2P_SAM_ADDRESS, so you might be able to just set that. Looks like it's x.x.x.x:port with IPv4.

[deavmi]

Hey, quick question on this @markqvist .

Does your code resolve hostnames in the I2P_SAM_ADDRESS environment variable?
I am asking as I have a dockerized setup and i2pd runs in a seperate container with,
a hostname as original as, well, i2pd. But I don't see any attempts to connect to the
SAM port when running rnsd -vvv.

[deavmi]

Hey, quick question on this @markqvist .

Does your code resolve hostnames in the I2P_SAM_ADDRESS environment variable? I am asking as I have a dockerized setup and i2pd runs in a seperate container with, a hostname as original as, well, i2pd. But I don't see any attempts to connect to the SAM port when running rnsd -vvv.

Nvm, I tried and got it working. :)

[deavmi]

Oh, that is a perfect solution for me then. Thanks!

…

On 03 September 2024 22:13:25 SAST, faragher ***@***.***> wrote: I know Mark's been working on support for externally defined (not part of the core package) interfaces, so this may be addressed soon. That being said, it gets the address from an environment variable called I2P_SAM_ADDRESS, so you might be able to just set that. Looks like it's `x.x.x.x:port` with IPv4. -- Reply to this email directly or view it on GitHub: #540 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

---- Tristan B. Velloza Kildaire Web: https://deavmi.assigned.network BNET IRC: deavmi Email: ***@***.***

[deavmi]

What I need to figure out for my particular setup is the following:

SAM is accessible ✔️

However, it seems that I can make working outbound I2P connections via peers=b32 b32 b32.... But inbound seems to be problematic 🤔

[markqvist]

Have you set the I2PInterface to be connectable? Like this, for example:

  [[I2P]]
    type = I2PInterface
    enabled = yes
    connectable = yes

In general, it can take a while before the I2P daemon is able to accept incoming connections when first started. In some cases, I've experienced delays up to 15-20 minutes before the I2P network can resolve the inbound address. Also, using the Purple I2Pd implementation seems to work a lot better than the old Java version.