We simply don't need one now that we're sharing the netDb.
Additionally, it also allows us to leave "onBoot" away in the client config.
With it, client apps might started before it's possible to open tunnels
since we have no active connections to other routers.
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
We now let I2P choose the UDP ports and also decide if it's firewalled or not.
Additionally, we add 2 floodfill routers.
We still have to determine if every router can be a floodfill router, but probably only 2 is cleaner.
#5 - Create SAM server tunnels in trans-proxy
Since IFS also has newline now, it was creating an array.
When simply echoing an array, it just echos the first element - always...
there was thus always only 1 element.
That's fixed now.
#5 - Create SAM server tunnels in trans-proxy
The reseeder includes fixes to run from bisentenialwrug/i2p-reseed until the official image has merged them.
Fixes are:
- autogenerating keys for TLS
- calling the right command to start the reseeder
The I2P routers are also configured to reseed from a single reseed host.
And finally the keys the reseeder uses to sign the su3 payloads are shared in a volume with the I2P routers.
Unfortunately, it still doesn't work as the reseeder sends empty packers or something. Stil trying to figure that out.
#5 - Create SAM server tunnels in trans-proxy
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
The protocol_factory doesn't support `Protocol`s with async handlers
e.g `async def connection_made` won't actually be awaited and thus nothing ever happens.
Now there's a pretty ugly solution with one long-ass method, but maybe that can be trimmed
or a callable can be used.
#4 - Investigate extending pr0xy to use SAM
Otherwise strings are passed and it can't start up.
Sockets can't be created when a string is passed as the port param
#4 - Investigate extending pr0xy to use SAM
The transparent proxy creates a client tunnel to the requested destination for each client connection.
This is untested for now, but a server tunnel is also incoming if this works well.
#4 - Investigate extending pr0xy to use SAM
It should be possible to replace networking functions, just like pr0xy
and SocksiPy do to let all communication of a program pass through I2P
#4 - Investigate extending pr0xy to use SAM
It can get called in quick succession and overwrite assignments if the
checks aren't done at the right time
#4 - Investigate extending pr0xy to use SAM
