Closed h-phil closed 8 months ago
Using the range10.8.0.0/16
worked after implementing the reservedrange
option check everywhere i2pd calls i2p::util::net::IsInReservedRange
.
https://github.com/h-phil/i2pd/commit/144c5f04246dcca536652c2594f6f8aeae319712
Router count initially increased, but dropped after a few seconds to 1.
Router reseeding works as expected. End-to-End test seems to work as well.
Fix for the reservedrange
is in the openssl
branch.
Merging https://github.com/h-phil/i2pd-testnet-kubernetes/commit/dce2348e8c23ba809cdd9b15d9e3389a1ad840a4 once it is released as container image.
Test using current latest
docker.io/purplei2p/i2pd@sha256:392545df631612ac65ddcf2e43926a3df85ce0c4830d967d0fc380a3e0b5e66d" works as expected.
The current setup with i2pd restricts users to using only a "fake" public range network (ex.
123.8.0.0/16
). There should be a way to use private ranges (rfc1918) instead.