- tor-relays - lists.torproject.org

Failure from drain-fd
by starlight.2015q3＠binnacle.cx 29 Oct '15

29 Oct '15

On 27 Oct 2015, at 15:42, Brian Walker <torrelay(a)outlook.com> wrote: > >I've updated Tor to the newest beta: >Tor v0.2.7.4-rc (git-f55d23e1e66e9b0f) running > on Windows 8 [server] > with Libevent 2.1.5-beta, > OpenSSL 1.0.2d and Zlib 1.2.8. > >I'm still experiencing errors: >Oct 27 01:22:29.000 [warn] Failure from drain_fd. . . >Oct 27 03:22:31.000 [warn] Failure from drain_fd. . . >Oct 27 05:22:33.000 [warn] Failure from drain_fd. . . > >Is there something else to try? Perhaps a debug-level log will shed some light. Message volume is too huge for anything but file logging. You can configure it in 'torrc' LogTimeGranularity=1 Log debug file logfile001 dynamically on a control channel: SETCONF LogTimeGranularity=1 Log="debug file logfile001" When done: SETCONF Log="notice syslog" LogTimeGranularity=1000 Never tried this on Windows. Perhaps 'syslog' does not apply. . .use whatever's in 'torrc'.

1 0

Unsubscribe
by OM Healing 28 Oct '15

28 Oct '15

On Tuesday, October 27, 2015, Eran Sandler <eran(a)sandler.co.il> wrote: > Hi all, > > I got a Tor Weather alert that my node is down: > > https://atlas.torproject.org/#details/98F44299592FC31FD3F2F8969D27374D00E96… > > Looking at it - it seems to have no flags at all (not sure why). > It is tunnelling ~8-10Mb/sec so I assume its being used as a relay. > > Is there a way to understand why it has no flags? > > Eran >

1 0

Free Domain for Tor Nodes
by Eran Sandler 28 Oct '15

28 Oct '15

Hi all, I recently bought torexitnode.net to make it abundantly clear in reverse DNS lookup that this is a Tor exit node. I've set both of my exit relays tor4thepeople1.torexitnode.net and tor4thepeople2.torexitnode.net to use it and I was wondering if it would be interesting for other Tor relay users to use it as well. If so, I'll write a small something that will allow adding new subdomains to it. So that you can always add and update subdomains on it. Once its running you can ask your service provider (if they don't provide an interface already) to make a reverse lookup on the IP to that address. What do you think? Is this something people would want to use? Thanks, Eran

11 15

Failure from drain-fd
by Brian Walker 27 Oct '15

27 Oct '15

Anybody know what this means? My logs are littered with it. Tor v2.6.9 with Libevent 2.0.21-stable, OpenSSL 1.0.1o and Zlib 1.2.8 on Windows Server 2012 R2. Aug 06 13:26:35.000 [warn] Failure from drain_fd [3892 similar message(s) suppressed in last 7200 seconds] Aug 06 15:26:37.000 [warn] Failure from drain_fd [3526 similar message(s) suppressed in last 7200 seconds] Thanks

3 6

debian tor package comes with multi-instance support as of 0.2.7.4-rc-1
by nusenu 27 Oct '15

27 Oct '15

Hi, the debian tor package maintainer implemented the multi-instance feature request [1][2][3]. Thanks Peter! If you want to learn more about it, have a look at tor-instance-create(8): https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-creat… Once tor 0.2.7.x stable is release I'll start playing with it and change ansible-relayor [4] to make use of that new functionality on debian systems by default - instead of implementing it via the ansible role itself (current behavior). We have quite good multi-instance support across multiple systems now (Fedora, CentOS, Debian, OpenBSD). FreeBSD is still somewhat of a hack - but it works as well. [1] https://lists.torproject.org/pipermail/tor-relays/2015-February/006472.html [2] https://trac.torproject.org/projects/tor/ticket/14995 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791393 [4] https://github.com/nusenu/ansible-relayor

3 2

Re: [tor-relays] too many circuit creation requests
by starlight.2015q3＠binnacle.cx 25 Oct '15

25 Oct '15

>[warn] Your computer is too slow. . . Raspberries are cute but seriously underpowered for crypto-intensive applications such as Tor. You can (any/all of) 1) ignore the warnings 2) restart the relay to send-off any hidden services that might be causing the overload 3) buy a dirt-cheap used laptop or mini-tower on eBay to run the relay 4) buy a Beagle Board if you enjoy fiddling with miniature computers --much more powerful device The configured limit is reasonable for the device.

5 10

Cheap VPS provider for an exit node
by Riccardo Mori 25 Oct '15

25 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, I have been running an exit Tor relay for 5 months with a PulseServers VPS and everything went fine until some days ago Kyle, the provider's owner, reduced the bandwidth to something above 10 Mbit/s. Adding the fact that he is an OVH reseller I am now searching a new VPS provider. Unfortunately I can't afford a 50$/month VPS so I am looking for something that has more than 5TB of monthly traffic with a reasonable price and preferably that it's not using OVH AS. What are you using? Is there anybody that can give me a hint? Thanks! Riccardo Mori -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWKmXTAAoJEE1LNuolWAxgnMAP/iWqUu0QpftVf8fzWNrs+UuJ bIpXdyYfjHTIcfk6cEZDNsJ+A3eNSYp2wt99QLLawiY95Jb7TNdzKBaiYCHtELHi R9iybldSH5snzpIDZE35SOSi+gleu334Yx0wSguVp4apxXKeaw4KMNC7nKXbWraH ijarl4LVBrkgoqs+l77DA/QtrmrY3zYQv1eRt6hHh3ah+XlW8HUMV1ipDblUtkot NH5sCe6FMg7fS0G33ZJprOq4a76jvmFJ89nfqyhZJjvey7ukuidYQLN+gFM5NWVs Pe3EYzv0tvOWZEnU+rPLEeF5iUQrTLPNlNhGirCQ74Mj9UMrVtKx7b9VoRedSua2 kx131c3VCCqc8CvheH6eztAt7WDE1GyA0JAGRCleTdhDxUdDdHZWgyrHp78aDvN7 6fYS0z4HFUyB/xTY7z3jP6z4IgxkeWv1McQXlyKQhn4ZSTRs9Z5ySpiKSi+L/Uar 145U4x6biuE5ZjkoTwJFNyLUdgduG+LPHfckyGHr0qsTm9TG+9FkEoVx02pijkVV zJRTuPPlOgOwabsFchj5Gzc+B3B1yZbNdjjFYMTyPv+LXP9MoFzC4Ytd2LyzLdCz TfOcvfbiWU2BK8GbzxD6Q5+nayZ20zFPQvvW7y6XKweiUZCkXmIFKWyDtZ0egCr5 fXY92u9AUOYgraHGOhps =7i7O -----END PGP SIGNATURE-----

3 3

too many circuit creation requests
by trshck_tor＠riseup.net 24 Oct '15

24 Oct '15

Hi all, I set up a new tor relay named trshck using a raspberry pi a few days ago. All was going fine until early today, when a lot of warning have started appearing in the log file: "[warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy." I've looked up this message and found some comments but nothing clear about how to solve the issue. I think this can be related with the recent acquisition of the HSDir flag. The relay is not configured to be an exit node. The number of open circuits has greatly increase in the last few hours: "Circuit handshake stats since last time: 4860/4984 TAP, 228464/229242 NTor." MaxAdvertisedBandwidth is not set, only: "RelayBandwidthRate 200 KB RelayBandwidthBurst 300 KB" What do you advice me to do? Regards, Joan Terrassa Hacklab

3 2

ntpd problems explanation
by I 23 Oct '15

23 Oct '15

2 2

Re: [tor-relays] Tor node break-in attempts
by starlight.2015q3＠binnacle.cx 23 Oct '15

23 Oct '15

> > Attack counts are in the 100,000s. > This sort of thing posses no threat and is quite stupid as previously observed. Is mainly annoying for the mess it makes of /var/log/security. If you don't want to change the SSH port (best solution IMO), here's an 'iptables' rule that will fix it (adjust/rearrange as needed/desired). These lines assume they will go in /etc/sysconfig/iptables. You can run them manually by prefixing with the 'ipbables' command. I wrote this without looking at the default 'iptables' file for any distro and if you are using one, revise accordingly or rename the original and start from scratch. -N input_eth0 -A INPUT -i eth0 -j input_eth0 -A input_eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT -A input_eth0 -p tcp --dport 22 -d x.x.x.x -m recent --update --seconds 600 --hitcount 3 --name SSH_ATTACK -j DROP -A input_eth0 -p tcp --dport 22 -d x.x.x.x -m recent --set --name SSH_ATTACK -j ACCEPT ========== Because we all make mistakes, you should *TEST* the rule by KEEPING A LIVE CONNECTION active and logging in a second time or you may lock yourself out of your server. Use iptables -nvL to display the counters and look for the lock-out effect after 'hitcount' attempts. Also look in cat /proc/net/xt_recent/SSH_ATTACK for the login tries and lock-out. You can clear an IP with echo "-x.x.x.x" >>/proc/net/xt_recent/SSH_ATTACK ========== If you want a bigger hash table and more history than the default, you can create /etc/modprobe.d/xt_recent.conf and put something like options xt_recent ip_list_tot=16384 ip_pkt_list_tot=255 in it. ========== Some documentation at http://linux.die.net/man/8/iptables

1 0