- tor-relays - lists.torproject.org

New router, new IP address
by Rick 08 Aug '14

08 Aug '14

So I saw the Craigslist post in tor-talk and checked to find that I'm at full speed with them. Since I'm an exit relay (residential, US, 15 months) and have been experiencing the CL Dial-Up Retro for a few months, I was surprised. It turns out that I have a new IP address so for the moment I'm a shiny new exit. Two days ago I installed a new router. Nothing special: $45 Linksys but selected specifically for use with DD-WRT. ROM burn and set-up was done completely offline. It took maybe a minute to do the router hot swap and all went well. IP address change never crossed my mind. After all, I was down for four days back in the winter (ice storm) and hoping for a new address when we came back up. No luck. Is this normal? Or at least not unusual? It seems a bit spooky to me. I thought the address was tied to the cable modem (ISP's equipment) and they couldn't care less about my LAN. :-\ Thanks Rick

2 1

tor bridges
by Patrick Kelley 06 Aug '14

06 Aug '14

2 1

Exit Nodes under DDoS attacks
by Tyler Durden 04 Aug '14

04 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi I just wanted to know from others how often your nodes are being DDoSed? Because this month one of our nodes has been targeted twice. Because DDoS sucks and most providers aren't very happen when this happens often. Greetings virii - enn.lu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlPfgjcACgkQzowS8yos8Rt1LQD/Rj2zZJpdmCyQhCmG3enWL6Z5 J0tbnnG2FS1GelACY74BAKIYRK8EVUt/pYfuuRzlBWWI84kuzcOmOiehqm6iyVjS =/ay4 -----END PGP SIGNATURE-----

6 6

Re: [tor-relays] Exit Nodes under DDOS attacks
by tor＠t-3.net 04 Aug '14

04 Aug '14

We never had our exit nodes become the targets of DDOS attacks HOWEVER, we occasionally see abuse complaints due to someone abusing Tor to DDOS attack other targets. Perhaps that's what you're seeing?

3 2

Running an AWS bridge on eu-west-1?
by tor-question＠puti.de 04 Aug '14

04 Aug '14

2 2

Learn Linux free for beginners
by I 02 Aug '14

02 Aug '14

A free online course from The Linux Foundation for beginners begins today. https://www.edx.org/

3 2

'relay early' attack detection at the infrastructure level
by Nusenu 02 Aug '14

02 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 [moved to tor-relays] Hi relay ops, please consider having a regular look at your logs after upgrading to the latest tor releases to spot relay_early attacks (even if the attack origin is not directly attributable from a relays point of view). searching your logs for 'Received an inbound RELAY_EARLY cell' should do it. https://gitweb.torproject.org/tor.git/commitdiff/68a2e4ca4baa595cc4595a511d… >>> It doesn't have to decrypt the stream to see it, because >>> whether a cell is relay or relay_early is a property of the >>> (per hop) link, not a property of the (end-to-end) stream. >> >> Does a patched relay also create a log entry as soon as it >> "kills" the circuit or is logging only happening on tor instances >> acting as clients? > > The patched relay also does a log message, yes. > > But the relay can only see its immediate neighbor in the circuit, > so it will only log that. Whether the attacking relay is that > (adjacent) one, or one farther on the circuit, isn't something your > relay can learn. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT3Bt6AAoJEDcK3SCCSvoensYQAJnuXhPNbhdJF7C6P9L8elG7 elPinCK6vmTbRXCoQam5j1VeL9C3FCBv415s811hfZxA37K17VdiKoS1NXB2kzkW 7WvL5/lH8culr83GTxrca0m7i2x6n0gCPOVPUWI3Go5bzwlsEidZsj7V14h2lfXH Ew8ZavvL0SLnRYJTvcjzqrWf3L8LsfYou6R2Y7yn085rGaGtUyVkQM44G9Zy3TVY 3lS4XqkZekXmmKjP06JjWdFMFdkaQhItbcdn3fF131ptlZlM5hFUaEpZHbpLLcjz fgJOt36jlkfILKRvxGyzcI118wmgrFVJFz9d7fuLVOdekK49aWxKh9Yh2aAekQEn Z3uF/eskL+Txptrc7iEKuWQZVlEkA8WVaQ70F1ADD/irln6ShJ17zrKqJ0qtaYlU V+CNfj/v2R6AgRhbVsNRdq8SWhDz4Nk4WgdYoUvxzgM1jmkAhQamlkC4f6JCqVQE /O0qeuXr/Z02pBwshcZlqKnBmPtuilSZwmlstIEfPAX9Tg6S1a0B/ycp3ByyJHJP QUNKwJ/cHtLpdPmIh2XUOT/5Kf10qmrLP5amYdRtBh304GoeHir3N/zfPmxdLfy7 Spb8W4p2C1HITzRlb9J97OGdKOR/2OOziZHOWZimF5O3fsrzsXQZe3Wlwbt5AxtY LJ5aXCUjNJ/TXe93nSQH =3FwX -----END PGP SIGNATURE-----

4 5

More attack traffic against Tor detected on exit relay
by tor＠t-3.net 01 Aug '14

01 Aug '14

IPTables rule involved: -A INPUT -p tcp -m string --hex-string "|00002800390038008800870035008400160013000a00330032009a009900450044002f00960041000500ff020100000400230000|" --algo kmp -j LOG --log-prefix "IPTables-GFC-new " -A INPUT -p tcp -m string --hex-string "|00002800390038008800870035008400160013000a00330032009a009900450044002f00960041000500ff020100000400230000|" --algo kmp -j DROP Logs generated Wednesday from hits against these rules: Jul 30 13:44:38 Libero2-vserver kernel: IPTables-GFC-new IN=eth0 OUT= MAC=00:16:3e:21:6d:34:00:21:d8:25:c0:20:08:00 SRC=1.50.250.198 DST=64.113.44.206 LEN=147 TOS=0x08 PREC=0x20 TTL=44 ID=21838 DF PROTO=TCP SPT=13717 DPT=9001 WINDOW=46 RES=0x00 ACK PSH FIN URGP=0 Jul 30 13:44:59 Libero2-vserver kernel: IPTables-GFC-new IN=eth0 OUT= MAC=00:16:3e:21:6d:34:00:21:d8:25:c0:20:08:00 SRC=175.152.3.46 DST=64.113.44.206 LEN=147 TOS=0x00 PREC=0x00 TTL=50 ID=21839 DF PROTO=TCP SPT=49229 DPT=9001 WINDOW=46 RES=0x00 ACK PSH FIN URGP=0 Jul 30 13:45:41 Libero2-vserver kernel: IPTables-GFC-new IN=eth0 OUT= MAC=00:16:3e:21:6d:34:00:21:d8:25:c0:20:08:00 SRC=124.90.49.99 DST=64.113.44.206 LEN=147 TOS=0x00 PREC=0x00 TTL=49 ID=21840 DF PROTO=TCP SPT=10200 DPT=9001 WINDOW=46 RES=0x00 ACK PSH FIN URGP=0

2 1

don't worry (to much) if your relay is loosing the guard flag
by Nusenu 31 Jul '14

31 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I guess it makes sense to make this change a bit more visible on the tor-relays mailing list since relay ops will notice the change eventually and not everyone is reading changelogs closely. A lot of relays will loose their guard flag (and probably see less traffic?) once enough dir auths [1] upgraded to 0.2.5.6-alpha. For the background see the changelog [2]: >> o Minor features: - Authorities now assign the Guard flag to the >> fastest 25% of the network (it used to be the fastest 50%). Also >> raise the consensus weight that guarantees the Guard flag from >> 250 to 2000. For the current network, this results in about 1100 >> guards, down from 2500. This step paves the way for moving the >> number of entry guards down to 1 (proposal 236) while still >> providing reasonable expected performance for most users. >> Implements ticket 12690. It will be interesting to follow the metrics graphs during that transition. I.e. will the guard bw history go down or will the remaining relays handle the same amount of traffic without any difference? (and similar questions) https://metrics.torproject.org/bandwidth.html#bandwidth-flags [1] https://consensus-health.torproject.org/#authorityversions [2] https://lists.torproject.org/pipermail/tor-talk/2014-July/034180.html -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT2rO6AAoJEDcK3SCCSvoeh4sP/iH6DKlOLtCo1ZoBYKsZx+EJ jir+Lk4urwU+3MeM5Ikbb/XTCXY9Y3RCX8tTG65tn+NoLKNJP/fUGuz8A87Vrc48 ismcoSPrjpgX358VMLy7gO9i1tZGLGDd6qNuh0hLws1Z1JVMBACQKv6ZJrSuaoy6 gM/+htBawyRy8KC9Lsw4C6RZsu8b5Kintn9D6MmcWwVIDY8voB3wyypeZZLWaFzI N9sfyT9M4GC+i2CyWsYNdXB/x6z+IEsq0FE0XMdaLr0W17vh8pef0X3XH06h+MUf GsqK86MkjiYfQ0KfMkA/XfYCA3AWTdMSn63L40cDtLqBEHILlvpY/awWX0G78cnU D6cyhRs/R9rUlzvxMxtEF2mMrhvMAkWhz3JrqoEh0o6eOOF9QsOB700rovNsNufw tCYw/PfDD8PVj/J38jcidxo4VBtLcIrdnSInFuLezyZtvKvlCgzMomu8fOdSLxgf gXmKLY6MzduQFAqgYOg5eu33zMSqiTckC2mWPJXWiJ8m5uRbgw57I+7DjTalB4lD KTBTbtjLf+jbZOYn+E8bmoi8hQFPfhjkMMaqSIXeooqDa2xTbYlmEgPy4VmW5rLf cJd1rM2irw9yMKIYMMcI/aLG5uWZJ5pYAw0zWNA1aBzp33mgJ1yFbdhk9BMA+3/G rqNAV1pSC4brVzn4nF++ =02Sf -----END PGP SIGNATURE-----

1 0

tor daemon problem with obfsproxy
by Fereydoon Sepehri 31 Jul '14

31 Jul '14

Hi All, I install and configure tor to set up a obfs3 bridge. If I use command "tor", everything is fine and clients could connect to server buf if I use "service tor start", the connection will be refused. I checked the log file. the problem is: [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is > 'closed'. Most probably the managed proxy stopped running. This might be a > bug of the managed proxy, a bug of Tor, or a misconfiguration. Please > enable logging on your managed proxy and check the logs for errors. > Jul 31 20:55:56.000 [notice] Failed to terminate process with PID '28836' > ('No such process'). the question is why "tor" command could run the obfsproxy but "service tor start"could not. I change the permission of "obfsproxy" from "root" to "debian-tor" but it did not solve the problem. Best Regards Fereydoon

1 0