[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor server on NSLU2: ORPort unreachable
- To: Scott Bennett <bennett@xxxxxxxxxx>
- Subject: Re: Tor server on NSLU2: ORPort unreachable
- From: Eugen <eugenrn@xxxxxxxxx>
- Date: Sat, 07 Jun 2008 16:15:10 +0300
- Cc: or-talk@xxxxxxxxxxxxx
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sat, 07 Jun 2008 09:15:15 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=I32Y55a14n+5bRS2f48GM/Glc1tozOhUK0u6QV99SDQ=; b=P9nrBAO1b/sbhgYzavtdvSpfLgpMP4qt2rKjj+O6TBqEuOHdvKVuznHwP3yjn0BteA cexjCg0PsNdG1/4+PdU+2q23cUgHGmwV7JDPoNdG5wiHrlq4Ue1D5t264teg6UseqOV2 1T3rlihuDxWVHrCK96olRtU5g9ihD9fGbT2EY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=YJcF2vDkVBTi1zg7pqg4wlTn7ecsQnqouGWoUE6dP+Fbe+Ll/AE8JVN17hvUlNXEMe QrpBpDAk15a7VQYCJ8aEaEHG5uxNeVzWikSJGgZOvDkGozQAgThiMS2iXSkm1vdPMk9k lyIbXZ59VZ/y4dknB47CN0FyjYJPdN+QXqZKw=
- In-reply-to: <200806071231.m57CVBxx024963@xxxxxxxxxxxxx>
- References: <200806071231.m57CVBxx024963@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Icedove 220.127.116.11eol (X11/20080509)
Scott Bennett wrote:
Currently, I have no Address set in torrc. But Tor is guessing it quite
On Sat, 07 Jun 2008 14:00:05 +0300 Eugen <eugenrn@xxxxxxxxx> wrote:
I want to run a Tor middle node on a NSLU2 device (266Mhz, 32 MB RAM).
I installed Debian etch version on it for ARM platform, and it works great..
But reachability of the ORPort fails...
In the following log lines, 18.104.22.168 is *currently* my router's IP,
and it is *dynamic* IP.
That could be the problem right there. Does the Address line in your
torrc currently match the actual IP address?
In a past test I did set it to what IP router had then, and it didn't help.
If not, then it means that
the test is trying to connect to an address that is not the address of
your router. Whatever it is trying to connect to is most likely not
listening on 9001, so the connection gets denied, and the test fails.
As shown by netstat, connections are established on my port 9001 from remote
Also, using the same network configuration (router, dynamic IPs, etc..),
I tested Tor
on my laptop, and it reported successful reachability for ORPort.
Yes, my router supports dyndns.org, but since Tor guesses it's IP
If you're dealing with dynamically assigned IP addresses, then you
need to set up a phony host+domainname at one of the organizations that
offers such a service.
I prefer not to use dyndns.org yet...