mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-11-19 09:54:16 +01:00
532544ce4f
This is cleaner because, the `remote_addr` and `discovered_ip` are related but two different things. Within connectd and lightningd we use the peers `remote_addr` feature to validate (and guess a port) to be used for IP discovery. Also when a peer reports us a `remote_addr`, this is given to the plugin API via the `peer_connected` hook. The network port here is not modified for godd reason! This can be used i.e. to detect if we are behind a NAT. But once lightningd figures enough peers report the same `remote_addr`, it sets the port to the selected network and tells gossipd to use that for `node_announcement` updates. Hence, within gossipd, there is no (should not be) `remote_addr`. Changelog-None |
||
|---|---|---|
| .. | ||
| test | ||
| broadcast.h | ||
| gossip_generation.c | ||
| gossip_generation.h | ||
| gossip_store_wire.csv | ||
| gossip_store.c | ||
| gossip_store.h | ||
| gossipd_peerd_wire.csv | ||
| gossipd_wire.csv | ||
| gossipd.c | ||
| gossipd.h | ||
| Makefile | ||
| queries.c | ||
| queries.h | ||
| routing.c | ||
| routing.h | ||
| seeker.c | ||
| seeker.h | ||