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.
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
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
