Hello everybody after some trouble with our Linux Exit Node, we hope that you can point the finger at the problem.
We changed from a Windows Server 2003 + Vidalia Exit Node to a Linux System.
With the Windows Server everything went fine no problems. Since we got the Linux server there are a lot of problems.
When the relay starts our Internet goes down. Its more like some DNS problem but i cant point the finger on it. The connection is still there but he need a lot of time to resolve the names.
Is this a overkill for our router?
Any suggestions?
Need more info?
Cheers guys&girls
VarVarna
Hi,
Am 15.08.2013 10:22 schrieb var:
We changed from a Windows Server 2003 + Vidalia Exit Node to a Linux System.
What GNU/Linux distribution do you use? How did you install Tor? How did you configure Tor in the torrc?
Lutz
Am 15.08.2013 10:31, schrieb Lutz Horn:
Hi,
Am 15.08.2013 10:22 schrieb var:
We changed from a Windows Server 2003 + Vidalia Exit Node to a Linux System.
What GNU/Linux distribution do you use? How did you install Tor? How did you configure Tor in the torrc?
Lutz
Log output would be quite valuable, too.
Norman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
var:
When the relay starts our Internet goes down. Its more like some DNS problem but i cant point the finger on it. The connection is still there but he need a lot of time to resolve the names.
Is this a overkill for our router?
My first question is, what kind of router are you using, and does the problem go away (for a short time or a long time) if you reset the router? I am assuming a consumer-type router.
Sometimes a lot of connections can overload consumer routers, this has definitely happened to mine with both Tor and Bittorrent.
* The router can become overloaded and respond slowly or drop packets * The connection table can fill up, allowing existing connections to work fine, but new connections fail intermittently (web pages half load, DNS gets weird, etc)
Some versions of Windows limited # of connections per second or something like that, where as Linux does not.
Aside from all the logs and config settings the other people on the list asked for - what make and model of router are you using, and are you running anything like OpenWRT, DD-WRT, Tomato on it?
Best, - -Gordon M.
var:
When the relay starts our Internet goes down. Its more like some DNS problem but i cant point the finger on it. The connection is still there but he need a lot of time to resolve the names.
Is this a overkill for our router?
My first question is, what kind of router are you using, and does the problem go away (for a short time or a long time) if you reset the router? I am assuming a consumer-type router.
Sometimes a lot of connections can overload consumer routers, this has definitely happened to mine with both Tor and Bittorrent.
- The router can become overloaded and respond slowly or drop packets
- The connection table can fill up, allowing existing connections to work fine, but new connections fail intermittently (web pages half load, DNS gets weird, etc)
I bought a ASUS RT-N56U based on the router ranking on smallnetbuilder: http://www.smallnetbuilder.com/rankers/router/result/1045-multi-functional-g... The important numbers for me was the routing throughput (1268 Mbps) and connections (35k). The routers ISPs provide are usually cheap garbage, very low number of connections and bad throughput. Wi-Fi was not important to me so a N600 router was fine. If you want better Wi-Fi you can find modern "ac" routers ranked there as well. Just make sure you get good routing throughput and lots of connections.
tor-relays@lists.torproject.org
-
Gordon Morehouse -
Logforme -
Lutz Horn -
Norman Rieß -
var