- tor-relays - lists.torproject.org

DDoS attack on relay
by Green Dream 26 Jan '16

26 Jan '16

My hosting provider alerted me of a DDoS attack on one of my relays. It started around 2016-01-26 12:42 UTC. They claim they tried "filtering, routing, and network configuration changes" to mitigate the attack, but as a last resort they temporarily disconnected the host from the network for 3 hours. I know such attacks are not uncommon, but I'm curious if any other operators experienced a DDoS around the same time? I'm also curious to know more about the nature of such attacks -- what type of attack was it, what is the general end goal of attacking a random Tor (non-exit) relay, etc. My hosting provider is unable or unwilling to share additional information.

3 2

EventDNS error
by TorOp AnonymizedDotIo1 25 Jan '16

25 Jan '16

Hi, Over the weekend I started having those kind of error popping on my log at a very high rate (a few per seconds): Jan 25 09:00:00.000 [warn] eventdns: Address mismatch on received DNS packet. Apparent source was xxx.237.192.xxx:61083 Apparent source is not my IP and is different at every error message. I restarted my relay and I have stopped happening. I am running my own local unbound DNS server. Is it some kind of attack or simply an error that happened over the weekend? I have never seen it before. For what it's worth, my relay is an exit relay at about 150mbps.

2 1

Fw: new message
by michael＠deepol.de 24 Jan '16

24 Jan '16

Hey! Open message <http://ks.mpt.ru/opinion.php?wdgm> michael(a)deepol.de

1 0

Tor Bridges
by Roots Babilonia 23 Jan '16

23 Jan '16

Please send me bridges

4 3

Re: [tor-relays] Tor Bridges
by jason 23 Jan '16

23 Jan '16

No -------- Original message -------- From: Roots Babilonia <f1re_f1ngers(a)hotmail.com> Date:23/01/2016 02:59 (GMT+00:00) To: tor-relays(a)lists.torproject.org Cc: Subject: [tor-relays] Tor Bridges Please send me bridges

1 0

Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
by AJ NOURI 22 Jan '16

22 Jan '16

*sudo service tor reload* * Reloading tor daemon configuration... [fail] */var/log/tor/log* > > Jan 08 08:01:25.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) > opening new log file. > Jan 08 10:19:40.000 [notice] Heartbeat: Tor's uptime is 3 days 0:00 > hours, with 0 circuits open. I've sent 1.17 MB and received 28.04 MB. > Jan 08 12:31:58.000 [notice] Received reload signal (hup). Reloading > config and resetting internal state. > Jan 08 12:31:58.000 [notice] Read configuration file > "/usr/share/tor/tor-service-defaults-torrc". > Jan 08 12:31:58.000 [notice] Read configuration file "/etc/tor/torrc". > Jan 08 12:31:58.000 [notice] Based on detected system memory, > MaxMemInQueues is set to 5988 MB. You can override this by setting > MaxMemInQueues by hand. > Jan 08 12:31:58.000 [notice] Opening OR listener on 0.0.0.0:443 > Jan 08 12:31:58.000 [warn] **Could not bind to 0.0.0.0:443: > Permission denied** > Jan 08 12:31:58.000 [warn] Failed to parse/validate config: Failed to > bind one of the listener ports. > Jan 08 12:31:58.000 [err] Reading config failed--see warnings above. > For usage, try -h. > Jan 08 12:31:58.000 [warn] Restart failed (config error?). Exiting. *Configuration /etc/tor/torrc* ORPort 443 > Nickname ididnteditheconfig > RelayBandwidthRate 1000 KBytes # Throttle traffic to 100KB/s (800Kbps) > RelayBandwidthBurst 2000 KBytes # But allow bursts up to 200KB (1600Kb) > ExitPolicy reject *:* Opened 443 port on the Internet box: http://i.stack.imgur.com/oVwzO.jpg [image: Inline image 1] Port 443 locally opened: *ss -tunlp | grep 443* tcp LISTEN 0 128 *:443 > *:* > tcp LISTEN 0 128 :::443 > :::*

4 4

[warn] Bad password or authentication cookie on controller.
by pa011 21 Jan '16

21 Jan '16

Hello, yesterday I got within a minute three times the above warning in my log file on Tor 0.2.7.6. Could somebody please explain to me what it means and how to solve? Is there a source where I can possibly find answers on this and other warnings? Thanks in advance Paul

2 1

Re: [tor-relays] what's up(down) with gablemoo?
by starlight.2016q1＠binnacle.cx 21 Jan '16

21 Jan '16

At 18:55 1/21/2016 +0100, you wrote: >Gabelmoo is running 0.2.7.6. . . Thank you for replying. I saw earlier that moria1 ran into this and decided to wait on 0.2.7 for my relay, though I suppose the issue is specific to authorities and does not apply to normal relays.

2 1

what's up(down) with gablemoo?
by starlight.2016q1＠binnacle.cx 21 Jan '16

21 Jan '16

Lately 'gabelmoo' had been bouncing down and up like a ping-pong ball. Because gabelmoo is a BWauth (of which only five exist) as well as a normal authority, the impact is greater than if it did not participate in bandwidth measurement. Disrupts the consensus median. Does anyone know anything about it? Thanks

2 1

Location of private key on Android?
by Christian Andersen 21 Jan '16

21 Jan '16

Hey guys, I'm running Orbot as a relay on my otherwise unused mobile. It works great! https://atlas.torproject.org/#details/B47A49120A51D28A6191BE9A67F102AA96F5F… But in case I ever need to move the relay to a real computer, or start using the mobile, I'll need the private key, but I can't seem to find it. My phone is Sony Xperia ZR, unrooted, running Android 5.1.1, 10.7.A.0.228 (possibly a Sony version number). Orbot is version 15.1.0-RC-2 (Tor 0.2.7.5-020120160125) I just updated from Google Play Store - I realize the version above (from the About-menu) doesn't reflect the Atlas-info. I don't know why. Root\Android\data shows no folders related to Orbot, I have unchecked "Hide system files" in the file managers I downloaded from Google Play store. - File Manager from ZenUI - File Manager from SAND STUDIO and - File Commander - File Manager from MobiSystems - - Which requires Premium to view hidden files(!). Any help is appreciated. Maybe i just need a non-sucky file manager? C A

1 0