New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable/fix ports with I2P #9138
Conversation
I just marked this as ready for review, and force pushed one last fix. I confirmed that: (1) i2p has no field for port when configuring a tunnel, (2) that multiple instances of an address appear with different port numbers, (3) that this patch "collapses" on address where port 1 is used as a placeholder. Unfortunately both the p2p protocol and storage mechanism will continue to read/write port for backwards compatibility. This is trivial as its only a 16-bit integer. |
Force pushed a change to improve backwards compatibility. |
Updated the comment about returning |
built master with this yesterday, everything seems ok. just have a question, does this have any effect or change the docs for i2p https://github.com/monero-project/monero/blob/master/docs/ANONYMITY_NETWORKS.md ?
stats/info:
|
Yes, looks like the documentation needs to be updated to omit the port number with I2P. Will do that (hopefully today). |
This should fix #8918 , but I am soliciting for tests before marking this as ready. Basically, I only know this passes the unit tests at this point.
The patch is pretty simple, I2P ports are now fixed at
0
, so opening the new pearliest manager should collapse the overloads on port once it goes into the internal map.