<font color="#663333"><font size="2"><font face="comic sans ms,sans-serif"><b>Roger<br><br>I just got back home and tried to implement your suggestion. On the settings for Vidalia 0.2.9/Tor0.2.1.26 under Sharing there is no place to enter or not enter an IP. I see nothing in the user interface that equates to "the Address line in Vidalia". Looking through all the Settings panes the only place that has an IP is under "Advanced" "Control Port" "Address". The entry that was there was <a href="http://127.0.0.1:9051">127.0.0.1:9051</a>. On the chance that this was the Address you were referring to I attempted to delete the entry but Vidalia would not accept it giving me the error message " "" is not a valid IP". I then tried entering my external IP, which was accepted, but TOR could not connect. I put 127.0.0.1 back in and now TOR connects just fine as a client but still fails to set up a private relay.<br>
<br>Message log:<br><br>Jul 09 17:21:53.515 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.<br>Jul 09 17:21:53.515 [Notice] Bootstrapped 100%: Done.<br>Jul 09 17:21:53.529 [Notice] Now checking whether ORPort <a href="http://10.0.1.3:9001">10.0.1.3:9001</a> and DirPort <a href="http://10.0.1.3:9030">10.0.1.3:9030</a> are reachable... (this may take up to 20 minutes -- look for log messages indicating success)<br>
Jul 09 17:21:53.530 [Notice] No Tor server allows exit to [scrubbed]:9030. Rejecting.<br>Jul 09 17:21:53.530 [Warning] Making tunnel to dirserver failed.<br>Jul 09 17:22:51.725 [Notice] No Tor server allows exit to [scrubbed]:9030. Rejecting.<br>
Jul 09 17:22:51.726 [Warning] Making tunnel to dirserver failed.<br><br>Any suggestions?<br><br>Thanks!<br>Jim<br></b></font></font></font><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 09:09, Jim Julian <span dir="ltr"><<a href="mailto:j.a.julian@gmail.com">j.a.julian@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><font color="#663333"><font size="2"><font face="comic sans ms,sans-serif"><b>Roger<br><br>Thanks, you're always very helpful! I'm on the road for a couple of days but I'll try the IP fixes when I get home later this week, first trying it with a blank and if that doesn't work I'll try entering the external IP manually. FYI, I did uncheck the "automatically distribute my bridge address" as the people I'm supporting are in China.<br>
<br>Thanks again<br><font color="#888888">Jim<br></font></b></font></font></font><div><div></div><div class="h5"><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 08:40, Roger Dingledine <span dir="ltr"><<a href="mailto:arma@mit.edu" target="_blank">arma@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Mon, Jul 05, 2010 at 01:04:38PM -0700, Jim Julian wrote:<br>
> Jul 05 12:01:48.158 [Notice] Tor has successfully opened a circuit. Looks<br>
> like client functionality is working.<br>
> Jul 05 12:01:48.159 [Notice] Bootstrapped 100%: Done.<br>
> Jul 05 12:01:48.174 [Notice] Now checking whether ORPort <a href="http://10.0.1.3:9001" target="_blank">10.0.1.3:9001</a> and<br>
> DirPort <a href="http://10.0.1.3:9030" target="_blank">10.0.1.3:9030</a> are reachable... (this may take up to 20 minutes --<br>
> look for log messages indicating success)<br>
<br>
</div>This line means that Tor guessed your external IP address as 10.0.1.3.<br>
That's not your external IP address -- if somebody else on the Internet<br>
tries to go to that IP address, they won't make it to you.<br>
<br>
You can read about RFC 1918 at<br>
<a href="https://secure.wikimedia.org/wikipedia/en/wiki/Private_network" target="_blank">https://secure.wikimedia.org/wikipedia/en/wiki/Private_network</a><br>
<br>
So the question is: what made Tor guess 10.0.1.3? My first thought is<br>
that you typed that into the Address line in Vidalia. You should try<br>
leaving that line blank. Then Tor will be willing to make better guesses<br>
(by asking the other Tor relays that it connects to what address it's<br>
connecting from).<br>
<div><br>
> Jul 05 12:01:48.175 [Notice] No Tor server allows exit to [scrubbed]:9030.<br>
> Rejecting.<br>
> Jul 05 12:01:48.175 [Warning] Making tunnel to dirserver failed.<br>
<br>
</div>Ah ha. This one stymied me for a bit, but I have an answer here too.<br>
Your Tor is trying to connect back to <a href="http://10.0.1.3:9030" target="_blank">10.0.1.3:9030</a>, to see if it's<br>
reachable. But every exit relay is refusing 10.* in their exit policy<br>
(they don't want to let anybody connect to private services inside their<br>
network), so your Tor can't even try it. This is normal, and the warning<br>
should go away once your Tor starts guessing the correct external address.<br>
<br>
And last, if you actually want this to be a private bridge (meaning you<br>
have somebody in mind that you're going to give your bridge address to),<br>
you should uncheck the "automatically distribute my bridge address"<br>
checkbox on the Vidalia bridge setup page. If your Vidalia doesn't have<br>
that checkbox, consider upgrading to a newer Vidalia bundle.<br>
<br>
Hope that helps,<br>
<font color="#888888">--Roger<br>
<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>