Michael Schmoock 532544ce4f gossipd: rename remote_addr to discovered_ip within gossipd ...

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

2022-09-15 13:30:06 +09:30

..

Makefile

common: clean up json routine locations.

2022-07-15 12:24:00 -05:00

run-find_my_abspath.c

lightningd: more graceful shutdown.

2022-09-12 14:00:41 +02:00

run-invoice-select-inchan.c

gossipd: rename remote_addr to discovered_ip within gossipd

2022-09-15 13:30:06 +09:30

run-jsonrpc.c

lightningd/json.h: remove.

2022-07-15 12:24:00 -05:00

run-log-pruning.c

lightningd: don't explicitly tell connectd to disconnect, have it do it on sending error/warning.

2022-07-18 20:50:04 -05:00

run-shuffle_fds.c

common: clean up json routine locations.

2022-07-15 12:24:00 -05:00