<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Daniel<br>
</p>
<p>One thing first: If you want to actively participate on this
mailing list on a regular basis, it would be best if you switched
your mailing-list-setting from digest to the actual mails (you can
then either configure your inbox to put everything containing
[tor-relays] into its own folder, or use a seperate
email-address). This way, the Subject-lines are preserved when you
answer, so it's easier to group the right messages together,
automatically.</p>
<p><br>
</p>
<p>Regarding relay vs. exit: <br>
</p>
<p>Yes, there's a difference. I assume you're familiar with the
basic workings of Tor (otherwise, read
<a class="moz-txt-link-freetext" href="https://www.torproject.org/docs/faq.html.en#Torisdifferent">https://www.torproject.org/docs/faq.html.en#Torisdifferent</a> and
check out <a class="moz-txt-link-freetext" href="https://www.eff.org/pages/tor-and-https">https://www.eff.org/pages/tor-and-https</a>).<br>
An exit is a special kind of relay, as it is the one where your
traffic leaves the Tor network and gets sent to the actual
destination. This means that the destination sees the exit as the
source of this traffic. So when somebody sends bad or illegal
traffic, e.g. a hacker or someone downloading a movie, it looks
like your exit is doing these things.<br>
Depending on the competence of your local law enforcement
agencies, this could mean your computer (or all your computers in
your home) might get seized, and you'll be a suspect.<br>
Therefore, it is not advisable to run an exit from home (since
then you'll get all your computers taken away), or put anything
else on the same server.<br>
Also, lawyers will file abuse complaints against your exit, which
you'll have to deal with.</p>
<p>It's perfectly fine to simply run a "normal" relay (you'll then
be the middle hop), especially if you're running Tor on a system
that's not online 24/7.</p>
<p>Nice to see your relay is running now! Though I must admit that I
have no idea what these "connection speed" notices mean. Probably
nothing important, or they'd be warnings. <br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 04.09.2016 um 06:52 schrieb daniel
boone:<br>
</div>
<blockquote
cite="mid:trinity-cb55d2ee-a0d5-4ad2-8f07-61ebe185a1e7-1472964763811@3capp-mailcom-bs12"
type="cite">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Ok, 1st on to MATT <br>
"I missed your SOCKS question."<br>
Well that doesnt matter because I took you advice on the
first reply you sent explaing things so I commented all
again as suggested. So all is well now on that part of the
torrc file.<br>
What I did do was kept the ORPort at 9001. I tried 443 but
in the terminal it showed me it could not bind so it would
not work.<br>
As for the question on "hope this helps" you bet and well
appricated. Thank you.</div>
<div><strong>What I did on the exit on lines 186-190 here is
what it is set at</strong></div>
<div><strong>"#ExitPolicy accept *:6660-6667,reject *:* #
allow irc ports on IPv4 and IPv6 but no more<br>
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and
IPv6 as well as default exit policy<br>
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only
as well as default exit policy<br>
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6
only as well as default exit policy<br>
ExitPolicy reject *:0 #no exits allowed: Minus the quotes
natrually. this line is line 190</strong></div>
<div>The links you sent me to look thru was interesting. Per
what it says I believe port 443 for the ORPort would be best
but until I get the bind issue I need to learn to do I best
leave it set at 9001 for now.</div>
<div>As for the reading on the relay</div>
<div>ORPort 443<br>
Exitpolicy reject *:* <stock in the
box><br>
Nickname ididnotconfig<br>
ContactInfo human@...</div>
<div> </div>
<div><strong>{ORPort 9001<br>
Exitpolicy reject *:* <how i set mine><br>
Nickname danielboon<br>
ContactInfo human@...}</strong></div>
<div><strong>back to line 190 I do have it UNCOMMENTED as you
can see.</strong></div>
<div><strong>{ExitPolicy reject *:0 #no exits allowed}</strong></div>
<div><strong>Maybe i can comment line 190, I am not sure but u
or Jen will get me right.</strong><br>
................................................................................................</div>
<div>This part is Addressed to Jen</div>
<div> </div>
<div>Regarding the exit settings:<br>
Is this relay running on a computer at your home, Daniel? <strong><answer
is yes, my tower with a 64bit linux system duel core></strong></div>
<div> </div>
<div>Is there other important stuff stored/running on that
computer? <strong><basically no important stuff. I do
have some stuff but only mount the partitons when I need.
Think I'm safe on that></strong></div>
<div> </div>
<div>If the answer to AT LEAST ONE of those two questions is
yes, you should definitely set<br>
"ExitRelay 0" and "ExitPolicy reject *:*".<br>
Actually, you should set this, regardless of the answers,
unless you<br>
know exactly, what it means to run an exit-relay and are
willing and<br>
prepared to do this.</div>
<div> </div>
<div><strong><what I want to do is run a relay to help fuel
the system. So is a relay and exit different?></strong></div>
<div><strong>and to the both of you I too will enjoying
working with the group. I'm interested in many things at
my age. I am self taught on all with books and just
working with various OS's. Windows has been out for my
many years once I got to now linux.</strong></div>
<div><strong>As for both if you 2 are good enough to give me
your names I can to that too. It is David so we can use
that.</strong></div>
<div> </div>
<div>I do have a setback here in the terminal I will post
it></div>
<div> </div>
<div><strong>{Sep 03 23:57:39.000 [notice] Bootstrapped 0%:
Starting<br>
Sep 03 23:57:47.000 [notice] Bootstrapped 80%: Connecting
to the Tor network<br>
Sep 03 23:57:48.000 [notice] Bootstrapped 85%: Finishing
handshake with first hop<br>
Sep 03 23:57:49.000 [notice] Guessed our IP address as
108.79.14.224 (source: 154.35.175.225).<br>
Sep 03 23:57:49.000 [notice] Bootstrapped 90%:
Establishing a Tor circuit<br>
Sep 03 23:57:51.000 [notice] Tor has successfully opened a
circuit. Looks like client functionality is working.<br>
Sep 03 23:57:51.000 [notice] Bootstrapped 100%: Done<br>
Sep 03 23:57:51.000 [notice] Now checking whether ORPort
108.79.14.224:9001 is reachable... (this may take up to 20
minutes -- look for log messages indicating success)<br>
Sep 03 23:59:07.000 [notice] Your network connection speed
appears to have changed. Resetting timeout to 60s after 18
timeouts and 1000 buildtimes.<br>
Sep 04 00:07:45.000 [notice] Your network connection speed
appears to have changed. Resetting timeout to 60s after 18
timeouts and 100 buildtimes.<br>
Sep 04 00:11:48.000 [notice] Self-testing indicates your
ORPort is reachable from the outside. Excellent.
Publishing server descriptor.<br>
Sep 04 00:11:49.000 [notice] Performing bandwidth
self-test...done.</strong></div>
<div> </div>
<div><strong>{</strong>Sep 04 00:11:56.000 [notice] Your
network connection speed appears to have changed. Resetting
timeout to 60s after 18 timeouts and 104 buildtimes.} </div>
<div> </div>
<div><strong><what is going on with that. I did not change
anything and I am not doing or using anything to set it
back. Right with the MB too.}</strong></div>
<div> </div>
<div>I'll check back in the morn. 21 hrs today is enough for
my butt. C/Ya</div>
<div> </div>
<div><b>[snip quote of digest]</b><br>
</div>
</div>
</div>
<pre wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
<br>
</body>
</html>