diva-exchange / i2p Goto Github PK

Hi,

I've got the following error when using ENABLE_UPNP=1 as environment variable with the latest divax/i2p:current-i2p-tor docker image.

[01/Jan/2024:16:23:22 +0000]@579/warn - UPnP: this module was disabled at compile-time

Kind Regards,
Danny

Because of #5, only settings which are exposed as environment variables are available for configuration.
This doesn't include the ifname, ifname4, or ifname6. A very common option needing configuration is the interface binding to ensure traffic goes thru a specific network.

There seems to be an attempt to set this automatically that's only half setup. The entrypoint.sh parses the default route interface as IP_BRIDGE and does a sed replacement of it in the copy of the i2pd.org.conf, but there's no appearance of that variable anywhere in the i2pd.org.conf.

I'm not sure this is even necessary, I believe the i2pd application will use the default route if none is specified.

The README.md says to mount over the /home/i2pd/conf/ folder, but the entrypoint.sh is always unconditionally overwriting the i2pd.conf in this folder based on the /home/i2pd/i2pd.org.conf template file and then substituting the variables in it.

I think the intent was to make the i2pd.conf configurable, but it's not at all based on the entrypoint.sh.

It seems that Reseed's websites are all blocked in my country. The log says " Reseed: SU3 download failed" and I can't access the webconsole.

I ran this in docker using your beginner instructions and unfortunately it errors out. Have you seen this before?

`darkhttpd/1.12, copyright (c) 2003-2016 Emil Mikulic.

listening on: http://0.0.0.0:8080/

[14:50:29.608126] STUBBY: Stubby version: Stubby 0.3.0

[14:50:29.610035] STUBBY: Read config from file /home/i2pd/network/stubby.yml

[14:50:29.610171] STUBBY: DNSSEC Validation is OFF

[14:50:29.610177] STUBBY: Transport list is:

[14:50:29.610180] STUBBY: - TLS

[14:50:29.610184] STUBBY: Privacy Usage Profile is Strict (Authentication required)

[14:50:29.610187] STUBBY: (NOTE a Strict Profile only applies when TLS is the ONLY transport!!)

[14:50:29.610190] STUBBY: Starting DAEMON....

Oct 18 14:50:29.611 [notice] Tor 0.4.3.5 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.5, and Libzstd 1.4.5.

Oct 18 14:50:29.611 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Oct 18 14:50:29.611 [warn] Tor was compiled with zstd 1.4.4, but is running with zstd 1.4.5. For safety, we'll avoid using advanced zstd functionality.

Oct 18 14:50:29.611 [notice] Read configuration file "/home/i2pd/network/torrc".

Oct 18 14:50:29.614 [notice] Wow! I detected that you have 24 CPUs. I will not autodetect any more than 16, though. If you want to configure more, set NumCPUs in your torrc

Oct 18 14:50:29.614 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.

Oct 18 14:50:29.614 [notice] Opening Socks listener on 0.0.0.0:9050

Oct 18 14:50:29.614 [notice] Opened Socks listener on 0.0.0.0:9050

Illegal instruction (core dumped)
`

Because of #5, it's not possible to configure any setting that's not exposed explicitly via the entrypoint.sh.

Binding the host network IP that's allowed is a standard feature most users will need. It's currently not settable.

The port for accessing the configuration webconsole appears to be port 7070 according to the hardcoded i2pd.org.conf. This isn't documented anywhere in the README.md.

• 2023 - Migrate Tests to be ESM compatible (handle related Testdeck, Mocha, Chai issues)
• 2023 - Migrate to ESM (remove CommonJS support)