Re: [tor-relays] Home broadband - worth running a relay?
On Tue, 30 Jul 2013 19:48:22 +, Gordon Morehouse wrote: ... True. And veering OT, but have you tried mosh yet? It's ideal for some situations over Tor, or where the client changes connections often. No, I built something for that situation myself around the same time and am just rewriting it. (Just a transport, no terminal prediction, with the intention of also using it as a transport plugin for tor bridge access.) Btw. if mosh 'works over tor' you may want to check if you're not just sending the UDP around tor. Andreas -- Totally trivial. Famous last words. From: Linus Torvalds torvalds@*.org Date: Fri, 22 Jan 2010 07:29:21 -0800 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] VPN termination on relays
Mosh is great, but it still relies exclusively on UDP, right? So no over Tor... Somewhat related to things that don't work via exits... So who wants to offer VPN termination as part of their exit service? User tunnels VPN to you, you give back a bound port, or a natted 10 address, somethings of that sort. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] What to do about port scans?
On 31.07.2013 20:48, Steve Snyder wrote: I know I can limit the rate of connections using iptables. What's the consensus on this? Is this considered advisable, or a breach of expected exit node behavior? You should not interfere with traffic other than the means you get by Tor, ie. block IP/Ports. If your ISP has problems with port scanning you should find a better one. :) -- Moritz Bartl https://www.torservers.net/ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Diagnosing relay unresponsive messages
So, I've got my relay back up on a Raspberry Pi and I'm working on figuring out the optimizations I made to it, and continuing to tune it. Out of the box these machines have some difficulty even offering a couple Mbps, but they can be greatly improved. I will post all details when done. I see a fair amount of this, much less than after some tweaks, but it still happens: 20:27:36 [ARM_NOTICE] Relay resumed [1 duplicate hidden] 20:27:30 [ARM_NOTICE] Relay unresponsive (last heartbeat: Wed Jul 31 20:27:19 2013) 19:50:57 [ARM_NOTICE] Relay unresponsive (last heartbeat: Wed Jul 31 19:50:4 This often happens at the same time as 'arm' (the monitoring program) may stutter, fail to render a few frames, then 'catch up' or redraw the screen. I'm trying to figure out what's going on so I can prevent it. It doesn't always correlate with traffic - it happens more often when there's more traffic but can happen even with very little. Tor is taking about 10% RAM, there's plenty free, and load is under 1.0. Best, -Gordon M. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
