mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-01-18 13:25:43 +01:00
Code Issues Projects Releases Wiki Activity

doc: mention ip discovery only active when no addresses are announced

Browse Source 
Changelog-None
This commit is contained in:
Michael Schmoock 2022-07-11 11:40:22 +02:00 committed by neil saitug
parent 301acc9556
commit b3177e945f
3 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/FAQ.md
View File

@ -73,7 +73,8 @@ There is no risk to your channels if your IP address changes.
Other nodes might not be able to connect to you, but your node can still connect to them.
But Core Lightning also has an integrated IPv4/6 address discovery mechanism.
If your node detects an new public address, it will update its announcement.
For this to work binhind a NAT router you need to forward the TCP port 9735 to your node.
For this to work binhind a NAT router you need to forward the default TCP port 9735 to your node.
IP discovery is only active if no other addresses are announced.
Alternatively, you can [setup a TOR hidden service](TOR.md) for your node that
will also work well behind NAT firewalls.

3
doc/TOR.md
View File

@ -48,8 +48,9 @@ network between you and the Internet, as long as you can use Tor you can
be connected to.
Note: Core Lightning also support IPv4/6 address discovery behind NAT routers.
For this to work you need to forward the TCP port 9735 to your node.
For this to work you need to forward the default TCP port 9735 to your node.
In this case you don't need TOR to punch through your firewall.
IP discovery is only active if no other addresses are announced.
This usually has the benefit of quicker and more stable connections but does not
offer additional privacy.

3
doc/lightningd-config.5.md
View File

@ -380,7 +380,8 @@ as described below).
Core Lightning also support IPv4/6 address discovery behind NAT routers.
If your node detects an new public address, it will update its announcement.
For this to work you need to forward the TCP port 9735 to your node.
For this to work you need to forward the default TCP port 9735 to your node.
IP discovery is only active if no other addresses are announced.
You can instead use *addr* to override this (eg. to change the port), or
precisely control where to bind and what to announce with the