Tunnel configuration is loaded only after selecting the router commant "Reload tunnels configuration" #2277
Description
I have a i2pd service running in a docker container (from the Alpine package).
There is a file with tunnels configuration, passed to i2pd as --tunconf=/home/i2pd/data/tunnels.conf.
The file seems to be correct as will be seen below. However, it does not seem to be processed on i2pd startup, and is not mentioned it the logs at log level debug. Neither it is visible in the Purple I2P Webconsole.
But if I activate the router command "Reload tunnels configuration" from the webconsole, the tunnel appears, with the right b32 key and the corresponding eepsite becomes openable in the browser (via a local I2P proxy, of course). From this, I presume that the tunnel is configured correctly.
The configuration file /etc/i2pd/i2pd.conf is
daemon = false
service = false
log = stdout
upnp.enabled = true
[http]
enabled = true # HTTP management console.
address = 0.0.0.0 # Listen on all addresses.
[sam]
enabled = true
[httpproxy]
enabled = true
address = 0.0.0.0 # Listen on all addresses.
[socksproxy]
enabled = true
address = 0.0.0.0 # Listen on all addresses.
plus parametres passed to i2pd:
/usr/sbin/i2pd \
--conf=/etc/i2pd/i2pd.conf \
--tunconf=/home/i2pd/data/tunnels.conf \
--datadir=/home/i2pd/data \
--certsdir /var/lib/i2pd/certificates \
--loglevel=debug \
--http.hostname=(skipped) \
--port=(skipped) \
--bandwidth=P \
--limits.transittunnels=10000 \
--ipv4=true --ipv6=true --floodfill=true \
--http.port=7070 --httpproxy.port=false --socksproxy.enabled=false
Why is the only tunnel activated on startup? Am I missing anything?