Now the project will always start in the testnet instead of trying to connect
to the live, production I2P environment.
This reduces startup time and allows faster testing.
In the future, it will be possible to automate tests and put them into the CI
It just works as opposed to:
geti2p/i2p: Can't write /usr/share/i2p/router.info which stores peers
Something's wrong with the configuration and it should be trying to write to /var/lib/i2p/i2p-config/router.info
meeh/i2p.i2p: The themes for the router console aren't copied and the web UI just looks terrible
#4 - Investigate extending pr0xy to use SAM
DNS doesn't work so there was an attempt at just forcing
stats.i2p to localhost, with no success.
A tcpdump is created on the host machine at /tmp/contained/tcp.dmp
to try and figure out what is being sent where, but
it doesn't seem like any HTTP traffice is being sent at all.
`iptables` is logged to /var/log/ so maybe that'll give a hint
as to where the stuff is going.
Maybe the rules are just bad too 🤷♂
