-
Notifications
You must be signed in to change notification settings - Fork 913
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
ipdiscovery: adds autobool config switch #5841
ipdiscovery: adds autobool config switch #5841
Conversation
8452aa1
to
7a7adaf
Compare
1fa96b1
to
25d00bf
Compare
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.
Very nice change, I like the autobool behavior, though in order places we simply set AUTO = NULL
so we can distinguish optional values from their default value. Checking #5843 as an alternative next.
d0cab87
to
8061db1
Compare
I rephased the doc changes so its more clear. |
8061db1
to
cc3929c
Compare
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.
I like this approach, esp with the fixes at the end, but I think the name of the option is wrong, and the autobool should be in common/ or something, not ccan/
7c01005
to
d340cba
Compare
@rustyrussell Thanks. Addressed your input.... |
0a4b834
to
54e887f
Compare
This fixes the CI errors when doing `make check-source` steps 'schema-added-check' and 'schema-removed-check'. These errors prevented CI from performing these steps correctly: ``` fatal: ambiguous argument 'main': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' ``` I changed it so that CI does a `git fetch origin` at first and do the `git diff` against 'origin/master' (which then exist). Also fixed a bug in the script that was missing $$master in the same line. Also I added that the script shows the actual diff before failing, so the user quickly sees whats wrong.
824252b
to
89a35dd
Compare
This adds the option to explicitly enable ip-discovery, which maybe helpful for example when a user wants TOR announced along with discovered IPs to improve connectivity and have TOR just as a fallback. Changelog-Added: Adds config switch 'announce-addr-discovered': on/off/auto
This switch was not doing anything useful anymore. We deprecate it anyways to notify the user about the new switch. Changelog-Deprecated: The old --disable-ip-discovery config switch
89a35dd
to
e57527a
Compare
@ALL Or should we go back to |
No preference on my side, I like the explicit nature of the first couple of names, and the brevity of the latter ones, so count me as undecided :-) |
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.
I like announce-addr-discovered
but don't have strong feelings on it. Looks good to me apart from the typo.
ACK e57527a |
This adds an 'AUTOBOOL' config switch that explicitly enables the IP discovery feature by
announce-addr-discovered
, as users may also want to have IP discovery plus TOR just as fallback to increase overall connectivity.Currently its still a bit tricky to use IP discovery as one need to disable any usable addresses i.e. by binding just to a specific interface and configure without TOR. This will enable 'default' behavior: when there are no usable addresses try ip discovery. Without this trick, when a node finds just a single (a likely changing IP address), it will announce this forever and IP discovery is disabled and never rechecks addresses bound to initially.
If unset, the default/auto behavior stays the same, meaning only do IP discovery when there are no usable addresses.
NOTE: there is a simpler version of this PR in #5843 that does the same but without the
autobool
, thus defaulting to disabled IP discovery.