[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor server on NSLU2: ORPort unreachable
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor server on NSLU2: ORPort unreachable
- From: Eugen <eugenrn@xxxxxxxxx>
- Date: Sun, 15 Jun 2008 13:26:50 +0300
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sun, 15 Jun 2008 06:27:08 -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:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=bGq0V5ORfP3SNzTZ5OKHbzEDYjC+YxNqJrIR6hJ6RZw=; b=X1q3Zqgncjwy2jk46gxNrmoeGmJ1vS8c8tOjcihramXVTxhl388rF9vw0mnON2Uyga Hni9qg6UbjDC7ukm2wcfGMPmlQEguHGV0uuAwAgxd/4rO7fUBDMH6wyQayK4bPLV5GZ+ pmWYgFSurnzuHAxiKrf9myoDQ/RTqXKPpOzss=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=WJZunHD/O2f95ecxa0tbnLnGX1nrIj9UJqhAIQ1U4Zlvugxr+xcUunM8OE0NFkiO8o GrJ28l8X9cQlUmtDsgCrngUau7EVuifDBsu9MQzfkKHO2OgyoxyZzqheQuB2rIa2ykuc ziJKtiw3+IPRz82sxYk8v7B3JgfmgNP09mVNo=
- In-reply-to: <484A8561.8090706@xxxxxxxxxxxxx>
- References: <484A6A35.6050206@xxxxxxxxx> <484A8561.8090706@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Icedove 220.127.116.11eol (X11/20080509)
Stephen Hildrey 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
But reachability of the ORPort fails...
I tried this a year or two ago and experienced the same problem. Like
you say, client functionality was fine (though slow) but it didn't
want to work as a Tor node itself.
I don't believe the problem is a network (e.g. port forwarding) issue.
I believe the problem is caused by either a) some incompatibility
between the current implementation of the OpenSSL libraries and
armv5tel, or b) the low spec of the device rendering key generation
too slow for the reachability checks.
Ultimately I didn't have time to investigate further, and I have no
hard evidence to support either of my theories. That said, I have a
known-good Tor configuration that worked on an x86 desktop machine,
but not on an armv5tel NSLU2.
Interested to hear how you get on,
I tried different things, and it still not working.
I'm also sure it is not a network configuration issue. So I tried these:
I compiled myself on the device, the development version of tor
0.2.0.27-rc. Running it has the same behaviour as stable version:
ORPort not reachable.
I upgrade the Debian distribution from etch(stable) to lenny (testing)
so I could use the new ARM port "armel" (
http://wiki.debian.org/ArmEabiPort ). It says here that the floating
point performance is "very much faster", and also that "armel" adds
I'm not sure if and how much Tor uses floating point operations, but I
said I'll give it a try.
So, I installed lenny, armel port, and Tor 0.1.2.19-3 package. Again,
same behaviour: everything looks fine, except Tor fails to see if ORPort
No progress so far...