Update sample config file with recent changes.

This commit updates the sample config file to add the new listen option
and update the semantics regarding the combination of --proxy and --tor
flags.
This commit is contained in:
Dave Collins 2013-11-13 20:20:32 -06:00
parent 7b86bec825
commit 50484c5841

View file

@ -21,22 +21,22 @@
; Use testnet.
; testnet=1
; Connect via a SOCKS5 proxy. NOTE: Specifying a proxy without the 'tor' option
; below will disable listening for incoming connections.
; Connect via a SOCKS5 proxy. NOTE: Specifying a proxy will disable listening
; for incoming connections unless listen addresses are provided via the 'listen'
; option.
; proxy=127.0.0.1:9050
; proxyuser=
; proxypass=
; The SOCKS5 proxy above is Tor (https://www.torproject.org).
; Although not required if the proxy set is indeed Tor, setting this option
; does the following:
; - Sends DNS queries over the Tor network (during DNS seed lookup). This
; stops your IP from being leaked via DNS.
; - Does not disable the listening port. This allows the hidden services
; feature of Tor to be used.
; improves anonymity by sending DNS queries over the Tor network (during DNS
; seed lookup). This stops your IP from being leaked via DNS.
; tor=1
; ******************************************************************************
; Summary of 'addpeer' versus 'connect'.
;
; Only one of the following two options, 'addpeer' and 'connect', may be
; specified. Both allow you to specify peers that you want to stay connected
; with, but the behavior is slightly different. By default, btcd will query DNS
@ -50,10 +50,11 @@
; reason (perhaps due to a firewall).
;
; 'connect', on the other hand, will ONLY connect to the specified peers and
; no others. It also disables listening and DNS seeding, so you will not be
; no others. It also disables listening (unless you explicitly set listen
; addresses via the 'listen' option) and DNS seeding, so you will not be
; advertised as an available peer to the peers you connect to and won't accept
; connections from any other peers. So, the 'connect' option effectively allows
; you to only connect to "trusted" peers.
; you to only connect to "trusted" peers
; ******************************************************************************
; Add persistent peers to connect to as desired. One peer per line.
@ -67,8 +68,8 @@
; Add persistent peers that you ONLY want to connect to as desired. One peer
; per line. You may specify each IP address with or without a port. The
; default port will be added automatically if one is not specified here.
; NOTE: Specifying this option will disable listening for incoming connections
; and DNS seeding for peers.
; NOTE: Specifying this option has other side effects as described above in
; the 'addpeer' versus 'connect' summary section.
; connect=192.168.1.1
; connect=10.0.0.2:8333
; connect=fe80::1
@ -86,7 +87,24 @@
; DNS to query for available peers to connect with.
; nodnsseed=1
; Disable listening for incoming connections.
; Specify the interfaces to listen on. One listen address per line.
; NOTE: The default port is modified by the 'testnet' and 'regtest' options
; so it is recommended to not specify a port and allow a proper default to be
; chosen unless you have a specific reason to do otherwise.
; listen= ; all interfaces on default port (this is the default)
; listen=0.0.0.0 ; all ipv4 interfaces on default port
; listen=:: ; all ipv6 interfaces on default port
; listen=:8333 ; all interfaces on port 8333
; listen=0.0.0.0:8333 ; all ipv4 interfaces on port 8333
; listen=[::]:8333 ; all ipv6 interfaces on port 8333
; listen=127.0.0.1:8333 ; only ipv4 localhost on port 8333
; listen=[::1]:8333 ; only ipv6 localhost on port 8333
; listen=127.0.0.1:8336 ; only ipv4 localhost on port 8336
; listen=:8336 ; all interfaces on non-standard port 8336
; listen=0.0.0.0:8336 ; all ipv4 interfaces on non-standard port 8336
; listen=[::]:8336 ; all ipv6 interfaces on non-standard port 8336
; Disable listening for incoming connections. This will override all listeners.
; nolisten=1