Tor From SVN on Weelky Basis
Is there any good reason not to build Tor from the SVN on a weekly basis or so? I understand stability, issues, etc., but are there are other reasons? I am building only for the server; I use a stable client on a different computer. -madjon
Re: Problems starting relay
I can only be of so much help compared to many of the others on this list but I'll give it a shot as I am posting as it. On Sat, Nov 1, 2008 at 11:50 PM, Geoff Down [EMAIL PROTECTED] wrote: Hi, I'm having trouble starting up a Tor relay. Once I set up port forwarding (I've tried to set it up for TCP and UDP), should I be able to Tor only operates in TCP, you don't need to set yourself up UDP. a) Ping myself from a looking-glass service b) Traceroute myself from a looking glass ? At the moment neither of these work. I get 'cannot confirm you can be seen from the outside world' errors. I'm on a dynamic IP, Mac OSX, I haven't changed any of the defaults from the Vidalia bundle. the logs say 'Nov 02 04:35:41.569 [Notice] Opening OR listener on 0.0.0.0:9001' It probably shouldn't be listening on 0.0.0.0. localhost:9001 or 127.0.0.1:9001 are normal unless OS X is different from Windows Linux (sorry, not real familiar with Macs). Changing that may be enough. It would mean editing your torrc file so the ORListenAddress line is something like ORListenAddress localhost:9001 -or--not both- ORListenAddress 127.0.0.1:9001 Also, your ORPort line (default: ORPort 9001) must match the above lines. E.g., if ORPort 2394 then ORListenAddress localhost:2394 Thanks, downie Hopefully this helps. If not, it is possible your port forwarding is setup incorrectly. If your computer gets a different IP from your router every so often it can cause problems (depending on the router). I have found it is easier to make sure my Tor server has a static IP *inside* my network. E.g., my Tor server always has the address 192.168.1.xxx. This is is easy to configure with most routers. If you need to configure it this way and have not I or someone else on this list ought to be able to help you. Other questions for you to answer: 1) Whatever version or Tor/Vidalia are you running? 2) What router do you use? -madjon
Re: Problems starting relay
all snipped Another thing (sometimes the obvious things are what kill you), is your firewall setup on your computer to allow incoming connections to port 9001? Or to allow Tor as a server? I have no idea how the OS X firewall works (or whatever firewall you use, for that matter) but it is an easy thing to overlook. -madjon
Re: Problems starting relay
I downloaded the Vidlalia/Tor/Privoxy bundle all together. I'm pretty sure my PC hasn't changed from 192.168.1.2 from the point of view of the router (there's nothing else on the LAN). It's a Safecom SWART2-54125 BTW. Other than port forwarding, I have no idea what other settings there could be. I have software to prevent outgoing connections, but no software firewall to prevent incoming ones as far as I know - the router is supposed to handle that. GD On 2 Nov 2008, at 05:30, Jonathan Addington wrote: On Sun, Nov 2, 2008 at 12:21 AM, Geoff Down [EMAIL PROTECTED] wrote: Hi, thanks for the response. I have no ORListenAddress line in the torrc file - I will try adding that line. The OrPort line is ORPort 9001 as expected for non-windows Versions are Tor v0.2.0.31 (r16744) Vidalia 0.1.9 Did you download Tor and Vidalia separately? I assume this is the stable version of Tor? Also, post if these changes (or others) work for you. Finally, I obviously have no idea you are setup. But if your computer gets a dynamic address from the router (standard DHCP setup) you may want to check the port forward part again. It is *possible* that your computer changes IP's (again, internally) since you set up the port forwarding. GD On 2 Nov 2008, at 05:09, Jonathan Addington wrote: I can only be of so much help compared to many of the others on this list but I'll give it a shot as I am posting as it. On Sat, Nov 1, 2008 at 11:50 PM, Geoff Down [EMAIL PROTECTED] wrote: Hi, I'm having trouble starting up a Tor relay. Once I set up port forwarding (I've tried to set it up for TCP and UDP), should I be able to Tor only operates in TCP, you don't need to set yourself up UDP. a) Ping myself from a looking-glass service b) Traceroute myself from a looking glass ? At the moment neither of these work. I get 'cannot confirm you can be seen from the outside world' errors. I'm on a dynamic IP, Mac OSX, I haven't changed any of the defaults from the Vidalia bundle. the logs say 'Nov 02 04:35:41.569 [Notice] Opening OR listener on 0.0.0.0:9001' It probably shouldn't be listening on 0.0.0.0. localhost:9001 or 127.0.0.1:9001 are normal unless OS X is different from Windows Linux (sorry, not real familiar with Macs). Changing that may be enough. It would mean editing your torrc file so the ORListenAddress line is something like ORListenAddress localhost:9001 -or--not both- ORListenAddress 127.0.0.1:9001 Also, your ORPort line (default: ORPort 9001) must match the above lines. E.g., if ORPort 2394 then ORListenAddress localhost:2394 Thanks, downie Hopefully this helps. If not, it is possible your port forwarding is setup incorrectly. If your computer gets a different IP from your router every so often it can cause problems (depending on the router). I have found it is easier to make sure my Tor server has a static IP *inside* my network. E.g., my Tor server always has the address 192.168.1.xxx. This is is easy to configure with most routers. If you need to configure it this way and have not I or someone else on this list ought to be able to help you. Other questions for you to answer: 1) Whatever version or Tor/Vidalia are you running? 2) What router do you use? -madjon
Re: Problems starting relay
On Sun, Nov 02, 2008 at 05:45:40AM +, [EMAIL PROTECTED] wrote 3.5K bytes in 113 lines about: I downloaded the Vidlalia/Tor/Privoxy bundle all together. Then all you need to do to run a relay is configure one via the Vidalia Setup Relaying button in the Vidalia Control Panel. Tor will generally figure out the rest. If your router supports upnp, Vidalia will attempt to configure any port forwarding for you. If not, then yes, you need to port forward your orport and dirport from the external router to your machine. If for some reason you use the osx firewall, you'll also need to open the tcp ports for the orport and dirport. If you are using 10.5 (leopard), when you configure a relay through vidalia, the system should ask you to allow or deny the correct ports. The easiest next step may be to start with a fresh torrc and let Vidalia do the work of configuring the relay. -- Andrew
