Thanks, quoted for reference. Will come in handy.
Anyone setting-up a 'Dual Stack' Masternode / Tor VPS might also consider running the node as a
Tor Relay, providing bandwidth to other Tor users.
Client Only torrc (example) config:
ClientOnly 1
SOCKSPort 9050
SOCKSPolicy accept 127.0.0.1/8
Log notice file /var/log/tor/notices.log
ControlPort 9051
HiddenServiceDir /var/lib/tor/dnet/
HiddenServicePort 989 127.0.0.1:51472
HiddenServiceStatistics 0
ORPort 9001
LongLivedPorts 989
ExitPolicy reject *:*
DisableDebuggerAttachment 0
NumEntryGuards 8
Amendments / additions to run as a
Tor Relay (example):
SOCKSPort 9050
SOCKSPolicy accept 127.0.0.1/8
Log notice file /var/log/tor/notices.log
ControlPort 9051
HiddenServiceDir /var/lib/tor/dnet/
HiddenServicePort 989 127.0.0.1:51472
HiddenServiceStatistics 0
ORPort 443
DirPort 80
LongLivedPorts 989
BandwidthRate 256 KB
BandwidthBurst 512 KB
MaxAdvertisedBandwidth 256 KB
RelayBandwidthRate 256 KB
RelayBandwidthBurst 512 KB
ExitPolicy reject *:*
DisableDebuggerAttachment 0
NumEntryGuards 8
## A handle for your relay, so people don't have to refer to it by key.
Nickname MyDnetRelayExample
## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
ContactInfo Random Person <nobody AT example dot com>
Notice that with a Tor Relay this info. is included in the Tor Atlas and with the Tor directories (example);
-
https://atlas.torproject.org/#details/7FBBEAF3011C0E8498214611B1601AB0BB0420A9-
https://atlas.torproject.org/#details/8B1434497F187A5E10756F5227764324D13CC68FWhereas CLIENT only (or Tor Bridge info. is private). So, If you can't be a Relay - be a Bridge:
-
https://www.torproject.org/docs/bridges#RunningABridgeExample Bandwidth setting:
## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 kilobytes per second.
## Note that units for these config options are bytes (per second), not
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
## 2^20, etc.
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
EDIT:
BandwidthRate 256 KB
BandwidthBurst 2048 KB
MaxAdvertisedBandwidth 256 KB
RelayBandwidthRate 256 KB
RelayBandwidthBurst 2048 KB
-
https://bitcointalk.org/index.php?topic=1262920.msg14155533#msg14155533These settings enable a Relay to be 'useful' in terms of bandwidth, although still very unlikely to exceed the 1 TB bandwidth limits of VPS providers such as Vultr or Digital Ocean (including the dnet node bandwidth). N.B. Do not run a Tor Exit node at either Vultr or Digital Ocean, they only tolerate Tor Relays (non-exits).
Anyhow, if your not going to be running a web server on the VPS then this is perhaps a good way to utilize the bandwidth and get your 'moneys worth' from the hosting provider. 300+ masternodes, all running as Tor Relays would make for a very useful addition to the existing Tor network and for users privacy!
-
https://www.torproject.org/docs/tor-relay-debian.html-
https://www.torproject.org/getinvolved/tshirt.html ![Cool](https://bitcointalk.org/Smileys/default/cool.gif)
-
https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs