mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-18 21:35:11 +01:00
Fix typos and options
--proxy= instead of --proxy: --always-use-proxy needs value (true)
This commit is contained in:
parent
068b593d98
commit
ab52638f93
@ -170,7 +170,7 @@ A non-persistent .onion address is generated by accessing an [auto service](#cre
|
||||
|
||||
4. In all the "Incoming" use case, the node can also make "Outgoing" Tor
|
||||
connections (connect to a .onion address) by adding the
|
||||
`--proxy:127.0.0.1:9050` option.
|
||||
`--proxy=127.0.0.1:9050` option.
|
||||
|
||||
#### Case 1 c-lightning has a public IP address and no Tor hidden service address, but can connect to an onion address via a Tor socks 5 proxy.
|
||||
|
||||
@ -188,7 +188,7 @@ proxy.
|
||||
Tor capabilities.**
|
||||
|
||||
If you want to `connect` to nodes ONLY via the Tor proxy, you have to add the
|
||||
`--always-use-proxy` option.
|
||||
`--always-use-proxy=true` option.
|
||||
|
||||
You can announce your public IP address through the usual method:
|
||||
|
||||
@ -334,7 +334,7 @@ or `--addr=yourexternalIPAddress:port` if the node is not inside an internal net
|
||||
|
||||
The node can connect to any V4/6 ip address via a IPV4/6 socks 5 proxy by specifing
|
||||
```
|
||||
--proxy=127.0.0.1:9050 --always-use-proxy
|
||||
--proxy=127.0.0.1:9050 --always-use-proxy=true
|
||||
```
|
||||
|
||||
## References
|
||||
|
Loading…
Reference in New Issue
Block a user