-
Notifications
You must be signed in to change notification settings - Fork 912
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
Polish feature remote_addr #5244
Merged
rustyrussell
merged 6 commits into
ElementsProject:master
from
m-schmoock:fix/remote_addr
Jun 17, 2022
Merged
Polish feature remote_addr #5244
rustyrussell
merged 6 commits into
ElementsProject:master
from
m-schmoock:fix/remote_addr
Jun 17, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changelog-Changed: connectd: prefer IPv6 connections when available.
...So it can be reused somewhere else Changelog-None
Changelog-Fixed: JSON-RPC: Adds dynamically detected public IP addresses to `getinfo`
m-schmoock
force-pushed
the
fix/remote_addr
branch
from
June 1, 2022 10:17
eb902fd
to
82f6289
Compare
Before this fix, there was the situation where a DEVELOPER=1 node would announce non-public addresses on mainnet if detected. Since there are some nodes on the internet that falsely report local addresses we move this 'testing feature' to 'dev-allow-locahost' nodes. Changelog-None
m-schmoock
force-pushed
the
fix/remote_addr
branch
from
June 1, 2022 11:20
82f6289
to
38a0032
Compare
Changelog-Added: jsonrpc: adds optional `remote_addr` to listpeers
m-schmoock
force-pushed
the
fix/remote_addr
branch
from
June 1, 2022 13:27
38a0032
to
36baf23
Compare
rustyrussell
approved these changes
Jun 17, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack 36baf23
Nice work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that the feature is out in the wild, I see several improvements that can be made:
getinfo
RPC. This was missed in prior PR.remote_addr
from peers that cannot be confirmed other peers (see Fill ininit.remote_addr
from front machines ACINQ/eclair#2256 ). Note: This currently does not produce false positives, but 'interrupts' the detection of the correct address.remote_addr
field tolistpeers
RPC.