[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor server crashes on a Linksys WRT54GL
The WRT54GL has about 16MB RAM. I was using an OpenWRT package of TOR version,
0.1.0.17. There is no gcc etc. on the box, and I doubt whether the thing
could be compiled on it: will TOR run on such as puny system?
Thanks for the tips about bandwidth changes. If I ever get this thing working,
I could donate more bandwidth when I ought be sleeping...
BTW nmap can scan higher port nos if you set with a port range (-p1-65535 )
but I take your point about netstat (on the box itself).
Thanks for the tips
On Wednesday 14 March 2007 08:20, Roger Dingledine (Roger Dingledine
<arma@xxxxxxx>) may have written:
> On Wed, Mar 14, 2007 at 07:57:24AM +0100, Mark Furner wrote:
> > I am experimenting with a tor server on my Linux router, but it starts 5
> > processes and hogs all my CPU before crashing.
> Try the 0.1.2.10-rc release -- it will start only 2 processes and then
> hog all your cpu. ;)
> > I am using a Linksys WRT54GL
> > with OpenWRT (White Russian RC6).
> How much ram does your linksys have? I hear they have been selling them
> with less and less ram to discourage people from using them for anything,
> so the newer it is the less likely it will run Tor (or heck, Linux) well.
> > An nmap scan did not show the port open (I
> > have opened TCP ports 9001 and 9030 on my firewall). Any tips so I can
> > get this working?
> nmap won't scan all the ports. It is the wrong tool for that purpose.
> Try netstat instead.
> > I would like to donate more bandwidth during the night, and think I could
> > start/stop the tor server with a different torrc config file. If someone
> > has a better idea how to do this, then please also let me know.
> You may find
> > Thanks for any help or pointers,
> Good luck,
Mark Furner, PhD
CH 8400 Winterthur
T. 0041 (0)78 641 15 92