Conversation
a9e9da5 to
3f91255
Compare
|
Hey @t-bast , We can do cross compat tests when you are ready. |
|
@m-schmoock cool, we're mostly at the same point then. I think it's worth shipping the part where we just send/receive that field whenever possible, and we can decide later how to act on it based on what we see in the wild. This branch is ready for cross compat tests if you want. You can build it, run it locally and test it against your c-lightning branch. I have a lot of sample scripts to do cross-compat tests here if that can help. I'll do the same on my side, I'll compile your branch and test it with mine. |
|
Nice, just remember to compile it with |
|
@m-schmoock I tested this between eclair and c-lightning, we correctly parse the tlvs 👍 However your implementation currently sends back private addresses (e.g. 127.0.0.1), I think you should filter these and not include them in the tlv stream, right? It is filtered out on the eclair side, but it would be better if it wasn't sent in the first place? |
|
@t-bast |
3f91255 to
49846f5
Compare
|
Hi @t-bast |
No worries, there's no rush here, whenever you're ready.
To be honest I'm not that interested in the DNS one for now, that's not something our users have been asking for at all and we don't have a good use for it in the short term, so it's lower on my priority list. |
49846f5 to
bdd00f7
Compare
|
@m-schmoock cross-compatibility with ElementsProject/lightning#4864 is working like a charm, I tested in both directions, the reported IP address is correctly logged. |
bdd00f7 to
ecb36b1
Compare
Codecov Report
@@ Coverage Diff @@
## master #1973 +/- ##
==========================================
- Coverage 87.62% 87.55% -0.08%
==========================================
Files 166 166
Lines 12886 12900 +14
Branches 543 543
==========================================
+ Hits 11292 11295 +3
- Misses 1594 1605 +11
|
This adds the option to report a remote IP address back to a connecting peer using the `init` message. A node can decide to use that information to discover a potential update to its public IP address (NAT) and use that for a `node_announcement` update message containing the new address. See lightning/bolts#917
ecb36b1 to
69943ce
Compare
This adds the option to report a remote IP address back to a connecting peer using the
initmessage.A node can decide to use that information to discover a potential update to its public IP address (NAT) and use that for a
node_announcementupdate message containing the new address.See lightning/bolts#917
I have successfully tested cross-compatibility with c-lightning ElementsProject/lightning#4864