-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Websockets draft address in node_announcement rejected? #6432
Comments
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Apr 19, 2022
This seems to prevent broad propagation, due to LND not allowing it. See lightningnetwork/lnd#6432 We still announce it if you disable deprecated-apis, so tests still work, and hopefully we can enable it in future. Fixes: ElementsProject#5196 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
So looks like we reject unknown address types: https://github.com/lightningnetwork/lnd/blob/master/lnwire/lnwire.go#L805-L808 We should just be ignoring it though:
|
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Apr 19, 2022
This seems to prevent broad propagation, due to LND not allowing it. See lightningnetwork/lnd#6432 We still announce it if you disable deprecated-apis, so tests still work, and hopefully we can enable it in future. Fixes: ElementsProject#5196 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: Protocol: disabled websocket announcement due to LND propagation issues
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Apr 20, 2022
This seems to prevent broad propagation, due to LND not allowing it. See lightningnetwork/lnd#6432 We still announce it if you disable deprecated-apis, so tests still work, and hopefully we can enable it in future. Fixes: ElementsProject#5196 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: Protocol: disabled websocket announcement due to LND propagation issues
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Apr 20, 2022
This seems to prevent broad propagation, due to LND not allowing it. See lightningnetwork/lnd#6432 We still announce it if you disable deprecated-apis, so tests still work, and hopefully we can enable it in future. Fixes: ElementsProject#5196 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: Protocol: disabled websocket announcement due to LND propagation issues
Ok we have a fix here #6435, it'll land in 0.15 which will drop in ~May-ish. |
rustyrussell
added a commit
to ElementsProject/lightning
that referenced
this issue
Apr 20, 2022
This seems to prevent broad propagation, due to LND not allowing it. See lightningnetwork/lnd#6432 We still announce it if you disable deprecated-apis, so tests still work, and hopefully we can enable it in future. Fixes: #5196 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: Protocol: disabled websocket announcement due to LND propagation issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
The following node_announcement doesn't seem to be accepted by LND:
This is with the draft websocket address type (6) (experimental reckless core-lightning mode enabled!):
In particular, the addrlen here is 001d (29), and the addr is
0180c7caa826070224006180000000d0000000005cd2a001260706204c
which breaks down to:01
: IPv4.80c7caa8
= ip address.2607
= port.02
: IPv6.24006180000000d0000000005cd2a001
= ipv6 address.2607
= port06
: Websocket.204c
= portI think we'll remove the code which advertizes this for the coming Core Lightning release, since it prevents broad propagation (see ElementsProject/lightning#5196 ).
The text was updated successfully, but these errors were encountered: