Re: Tor Server Affecting Net Access
You have total transfer per day limited, but do you have total transfer per second limited using BandwidthRate and BandwidthBurst? From my /etc/tor/torrc BandwidthRate 75 KB AccountingStart day 12:00 AccountingMax 1 GB -- To the agents of the N.S.A. reading this email: The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. 4th Amendment to the United States Constitution.
Re: Tor Server Affecting Net Access
It could be that your router is struggling with the amount of connections Tor generates. Consumer class routers are known to have a relatively low number of max. connections or connections per second. You have total transfer per day limited, but do you have total transfer per second limited using BandwidthRate and BandwidthBurst? From my /etc/tor/torrc BandwidthRate 75 KB AccountingStart day 12:00 AccountingMax 1 GB -- To the agents of the N.S.A. reading this email: The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. 4th Amendment to the United States Constitution.
Re: [or-talk] Tor Server Affecting Net Access
On Thu, Mar 22, 2007 at 11:54:11PM -0700, [EMAIL PROTECTED] wrote: snip However, if the issue is simply that having a couple hundred people's tor traffic running on your home DSL connection just gums up the works, and even segregating the tor server to its own IP won't address the issue, then I may have to sadly stop running it as I have to keep everything else functioning too. Thanks for any suggestions. First note -- I've noticed that the IP I'm using for my exit node is defintely blocked some places. I've not noticed any effects on the other IP's, so it doesn't look like anyone is going through the insanity of knocking out whole subnets yet, but... Anyway, I'm assuming people are simply blocking all servers in the TOR directory listing... Or have people observed that non-exit nodes are actually not being blocked? (my point here being that you should probably consider the additional static IP anyway...) The IP address probably won't help your bandwidth issue though. You could try turning down your bandwidth rate from 75KB and see if ths helps, but that should be sufficiently low to keep things from grinding to a halt (I personally noticed that I could run apps like bittorrent at 80+% of my home bandwidth without killing online games and VoIP). I'll admit the possibility that the max connections per second issue is a problem for a home gateway... but my exit server is on a fairly low-power machine (Linux/UltraSPARC 300mhz box), which is actually comparable to some home routers these days in sheer MIPS. Call me paranoid, but I'd actually be a little concerned about upstream traffic shaping from your ISP if they're trying to throttle back file sharers at the like. Ok, probably not a helpful message for troubleshooting, just my own $0.02. -- Sam
Re: Tor Server Affecting Net Access
On Fri, Mar 23, 2007 at 01:54:38AM -0700, [EMAIL PROTECTED] wrote: You have total transfer per day limited, but do you have total transfer per second limited using BandwidthRate and BandwidthBurst? From my /etc/tor/torrc BandwidthRate 75 KB AccountingStart day 12:00 AccountingMax 1 GB Suggestions, to try in order. Let me know which one of these solves it, so we have another data point. :) 1) Add BandwidthBurst 75 KB to your torrc too. Right now your BandwidthBurst is at the default, which is 6 MB, which is certainly enough to saturate your upstream during bursts. 2) Upgrade to 0.1.2.12-rc, or if you can't, turn off your DirPort. The 0.1.1.x release only rate limits incoming traffic, whereas 0.1.2.x rate limits both, including handling directory traffic well. Outgoing traffic is probably causing your problem, whatever it is. 3) Try reducing the number 75 to a lower number. Maybe you don't have the upstream bandwidth you think you have. 4) Drake had a good question, which was does having Tor running degrade your connectivity even when it's known to be hibernating? 5) Your DSL router may have problems handling hundreds of TCP connections at once. Are you running the most recent bios? I don't think getting a separate IP will do much. But hey, if you get to this point in the list, who knows. :) But once you've figured out the issue, yay exit nodes, we could use more. Hope that helps, --Roger
