mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-09-14 18:30:52 +02:00
tor: Allow direct connections to clearnet targets
This commit is contained in:
@@ -827,6 +827,13 @@ litecoin.node=ltcd
|
||||
; Allow outbound and inbound connections to be routed through Tor
|
||||
; tor.active=true
|
||||
|
||||
; Allow the node to connect to non-onion services directly via clearnet. This
|
||||
; allows the node operator to use direct connections to peers not running behind
|
||||
; Tor, thus allowing lower latency and better connection stability.
|
||||
; WARNING: This option will reveal the source IP address of the node, and should
|
||||
; be used only if privacy is not a concern.
|
||||
; tor.directconnections=true
|
||||
|
||||
; The port that Tor's exposed SOCKS5 proxy is listening on. Using Tor allows
|
||||
; outbound-only connections (listening will be disabled) -- NOTE port must be
|
||||
; between 1024 and 65535
|
||||
@@ -841,6 +848,9 @@ litecoin.node=ltcd
|
||||
; connection. With this mode active, each connection will use a new circuit.
|
||||
; This means that multiple applications (other than lnd) using Tor won't be mixed
|
||||
; in with lnd's traffic.
|
||||
;
|
||||
; This option may not be used while direct connections are enabled, since direct
|
||||
; connections compromise source IP privacy by default.
|
||||
; tor.streamisolation=true
|
||||
|
||||
; The host:port that Tor is listening on for Tor control connections (default:
|
||||
|
Reference in New Issue
Block a user