This is a bag of curiosities... first, you shouldn't have any issue acting as a relay with a non-rooted device. The port you are trying to open is high enough, and there are no iptables or other root related permissions required for this capability.
The message that stands out for me is: "Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory" Perhaps the ReachableAddresses setting somehow stops the check for resolve.conf? I also need to verify whether it is standard or not for Android to have a resolv.conf in that location. I will do some testing on my Nexus and a Motorola Droid (Milestone) and see what I find. +n On 11/11/2010 04:24 PM, Berglind Ósk Bergsdóttir wrote: > > I've been looking at ticket #2069 (Orbot fails to start if configured as > a relay) https://trac.torproject.org/projects/tor/ticket/2069 > and found out that if you check ReachableAddresses (Run as a client > behind a firewall with restrictive policies) the error goes away and you > are succesfully connected. > > I was wondering what the normal behaviour is with these issues with > Tor(if ports are blocked that is). Maybe I could just somehow check if > the phone is blocking ports and show an error about it so the user knows > what's going on? > > Also I'm using an unrooted phone, HTC Hero 2.1, so I was wondering if > this just happens on unrooted phones? > > - Berglind aka beggaboo > > > > > *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/
