- tor-relays - lists.torproject.org

One of my nodes seems down by its tunnel quite a bit of traffic
by Eran Sandler 02 Nov '15

02 Nov '15

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

6 7

(no subject)
by 海洋 31 Oct '15

31 Oct '15

1 0

HoneyPot?
by Mirimir 30 Oct '15

30 Oct '15

Anyone know what HoneyPot was/is? https://atlas.torproject.org/#details/F77FD005BF74CD0B4C611389C3006452AEC60…

6 11

Re: [tor-relays] HoneyPot?
by Dhalgren Tor 29 Oct '15

29 Oct '15

Is the end of the month. Maybe they ran out of bandwidth and will be back 11/1. LeaseWeb over-limit rates are terrifying. BTW the exit policy includes 443.

2 1

(no subject)
by 海洋 29 Oct '15

29 Oct '15

8e10f0be03478ac378eb8562bd71e3757734fd75

1 0

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