Commit 5920fdb3 authored by Matt Traudt's avatar Matt Traudt
Browse files

Learned that cannot be the location of the sbws server

GH: closes #90
parent 524e263c
Deploying Simple Bandwidth Scanner
.. todo::
Determine if the helper exit can specify as the location of
the sbws server. Replace all instances of **XX1** with the answer.
.. todo::
Determine if the sbws client and server can be on the same machine.
......@@ -91,8 +86,6 @@ those passwords you generated earlier.
``server_host`` can be an IP address. IPv4 will work. IPv6 will work
without ``[brackets]``
At this point you are done on ClientMachine for now. You should verify that the
configuration is most likely valid by running a simple sbws command and seeing
if it complains. The following indicates there is no problem.
......@@ -132,7 +125,6 @@ torrc options.
# End modifications needed for a non-exit sbws helper relay
Replace ```` with the IP address of this machine.
If this is an exit relay, you will still need to set
``ExitPolicyRejectPrivate 0`` and allow exiting to a local IP address on a single
......@@ -157,7 +149,6 @@ manually. The exit part of your torrc should look something like this.
# End exit relay config and modifications needed for an exit sbws helper relay
Again, replacing ```` with the IP address of this machine.
Once you are done editing your torrc, reload Tor. Make sure Tor is still
......@@ -175,7 +166,9 @@ for this machine.
bind_ip =
You can set the ``bind_ip`` to ```` if you would like. It does not need
to be reachable from the Internet, so you probably want to make sure your
firewall does not allow incoming connections to sbws server's port.
Now it's time to tell the sbws which clients we want to allow to use our
server. Gather the 64 character passwords from all the clients you want to
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment