- tor-relays - lists.torproject.org

Making use of new bandwidth
by Logforme 11 Apr '19

11 Apr '19

I run the non-exit relay: https://metrics.torproject.org/rs.html#details/855BC2DABE24C861CD887DB9B2E9… The relay run on a debian stretch machine with an i5-4670 at 3.8GHz with 4GB memory. CPU usage at 250Mbps traffic is around 40% of 1 core out of 4. On April 1st my ISP doubled my bandwidth, from 250Mbps to 500Mbps. So far the Tor bandwidth authorities seems to not have picked up on all the new bandwidth. The observed bandwidth number has changed twice, increasing with small amounts. How long does it take for the BW authorities to eventually observe a BW closer to 500Mbps. Weeks? Months? The reason I ask is that I wonder if I should run a second Tor instance or if the current one will be able to make use a a reasonable part of the 500Mps.

5 8

Dirauth running new bandwidth scanner version
by juga 10 Apr '19

10 Apr '19

Hi!, >From this moment longclaw is using a new bandwidth scanner version [0]. If you detect any issues with longclaw's voted bandwidth, please email me or open a ticket in Tor project trac [1]. Thanks, juga. [0] sbws.rtfd.io [1] trac.torproject.org

1 0

Advertised Bandwidth/Consensus Weight Dropping: Is Verizon FiOS throttling Tor Relays?
by Neel Chauhan 10 Apr '19

10 Apr '19

Hi tor-relays@ mailing list, I run the following Tor middle relay on a 300 Mbps symmetrical Verizon FiOS connection: https://metrics.torproject.org/rs.html#details/2A65713649C1FD68764DBF43C463… My setup is as follows: * HPE MicroServer Gen10 (AMD X3421) running FreeBSD 12.0 * Tor relay in FreeBSD 12.0 jail, with "RelayBandwidthRate 0" * Linksys WRT1900AC running OpenWrt The Linksys is connected directly to Verizon's ONT (which converts fiber/GPON to Ethernet) and no Verizon-branded router is used in my setup. The problem is that after setting up my relay, I had my Tor Advertised Bandwidth and Consensus Weight values trend downwards for the past week. Sometimes, I have occasional spikes in consensus weight. This relay has a new fingerprint, but used this server with another fingerprint as well. On the previous fingerprint, I reached a peak of 19.5 MB/s (~160 Mbps) for the Advertised Bandwidth but has dropped to ~10 MB/s (~80 Mbps). The previous fingerprint also had the same server and router. I am thinking the issue is one of the two: 1. Tor bandwidth authority nodes are overloaded or have bad connectivity to Verizon 2. Verizon is intentionally throttling Tor on FiOS 3. The relay ramp-up phase is still in action for my relay and I need to wait I am suspecting reason 2, as I had seen my bandwidth values drop, and unable to reach higher values. For some reason, other relays on AS701 (Verizon's AS Number) have higher Advertised Bandwidth/Consensus Weight values than me (around ~18.7MB/s on the fastest relay): https://metrics.torproject.org/rs.html#search/as:AS701 Sometimes, the other FiOS relays can go up to ~23 MB/s (~184 Mbps). Is Verizon throttling Tor or are Tor bandwidth authority nodes just overloaded (or have bad peering with Verizon)? Or is it just the relay ramp-up phase in action? Thank You, Neel Chauhan

1 0

Another Slow Relay
by Ben Riley 09 Apr '19

09 Apr '19

Hi everyone, I've read over a couple of other threads regarding relays being slow, however, I can't figure out why mine is running as slow as it is. I used to have a FAST flag and was getting a throughput of several hundred KB/sec on my relay. Now I can't remember if I upgraded TOR or just updated the OS, but I lost the flag. I figured that I'd changed something and would have to 'earn' it again after a few days, week and now months? According to NYX, my average is 6.4KB/sec. I did have the limit set to 1MB and 2MB burst for the last few months thinking that would be more than enough. This morning I changed those (via NYX) to 0 (default) 1GB/s and it looks like it's starting to climb. My internet connection is on a home set up with a connection speed of about 97Mb, so plenty of speed available. If you look at my previous reports on: https://metrics.torproject.org/rs.html#details/9F19251CEE17B1E05084898D164F… there appears to be a massive drop off in speed during Feb 2019. I'm open to suggestion. Additionally, I'm considering opening an exit port, but everyone seems to say that is a REALLY bad idea on a home set up. Plus I don't really know what I'm doing :)

3 5

Please help, my relay is unresponsive
by digitalist00 08 Apr '19

08 Apr '19

Dear helpers! Nyx says that my relay is unresponsive and that it was resumed. As I write this mail I have already 334 duplicates hidden. What's my problem and how can I solve this? The relay runs on a Raspberry Pi and is connected via LAN. Yours Digitalist [Unbenannt.JPG] Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 16

IPv6 not provided, guard relay
by digitalist00 08 Apr '19

08 Apr '19

Hello! I have read that it's recommended to enable IPv6 for a tor middle relay. But my provider doesn't offer IPv6. Is IPv6 required to become a guard middle relay? Yours Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

Relay C19B33758B3A5144894233EC4C95D7985B9FD101
by ylms 08 Apr '19

08 Apr '19

Hello, I just setup a new exit, I know it takes time to "train", but I would be interested in tips on how to tweak it. I just replaces a old exit that used the same IP, but unfortunately we lost that config/key. So any tips are welcome in general. I also have some questions. Atlas does not show any IPv6 address, is this normal? WHat loglevel can I set to see if there is any problems, to find possible improvements? I know the logging should not be changed, but I want tot make sure tor works fine, so I would like to see some more information for now. Thanks for your help. yl

6 14

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101
by ylms 08 Apr '19

08 Apr '19

On 4/5/19 12:36 PM, torgate(a)linux-hus.dk wrote: > hi, the adress is in use check what is running on your system and check > also the ports sudo lsof -i -P -n | grep LISTEN does not show any ports used twice for the same address. yl

1 0

is a good idea to run a ssh honeypot?
by caioau 07 Apr '19

07 Apr '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I been running a relay for almost 1,5 year, and in the beginning I didn't change the default 22 ssh port but a lot of people were trying to login , no worries I only allow public key authentication. So I was wondering if I could record the attacks, so I find this https://haas.nic.cz/ service and I'm running on my relay, is it a good idea? Thanks Sent with ProtonMail Secure Email. -----BEGIN PGP SIGNATURE----- Version: ProtonMail Comment: https://protonmail.com wsBcBAEBCAAGBQJcqlUBAAoJEO6drAP5JZWbZ30H/i5UlyLceKIKB1osoA16 W0x2YZWoLw8Lvifxt0ijwQSLdzU5H1CTXxHoQJLpygESdGJMbBYiOGirRnWR nnlHqnbHHwUbZDUsxUBZTBrutwVaXXmswYyfrgZvJo17ocSaT2goaPJ0F9oK JHpzDegTOIE6hbwUI3BnDLI6u7/gCE1ZvgrzSbIvXebZ8XKC67j0AwhKMX0Q zUjLpXQ2eq5XLKPlOnXUc/i6xYCIoNjoBRSHX95hd2N4zy7xuZ3UhrVn0ZBi 7ZRjo77h7BeRsB3F9bA61DfgN9pM+J+R9sPU3qYClXPB/cOJmyVqVFtcT7NK 0Tz+mfbFNI8KfhN9ZHMS16Q= =FsLz -----END PGP SIGNATURE-----

2 1

Re: [tor-relays] is a good idea to run a ssh honeypot?
by caioau 07 Apr '19

07 Apr '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I use ufw as my firewall and it's set to limit ssh so if there's someone brute forcing the ssh it will get blocked for a time Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, April 7, 2019 7:54 PM, Elmar Otter <mailer(a)elmarotter.eu> wrote: > Hello, > > Why don't you use Fail2Ban? > > Greatings, Elmar > > Op 07-04-19 om 21:52 schreef caioau: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > Hi, I been running a relay for almost 1,5 year, and in the beginning I didn't change the default 22 ssh port but a lot of people were trying to login , no worries I only allow public key authentication. > > > > So I was wondering if I could record the attacks, so I find this https://haas.nic.cz/ service and I'm running on my relay, is it a good idea? > > > > Thanks > > > > Sent with ProtonMail Secure Email. > > -----BEGIN PGP SIGNATURE----- > > Version: ProtonMail > > Comment: https://protonmail.com > > > > wsBcBAEBCAAGBQJcqlUBAAoJEO6drAP5JZWbZ30H/i5UlyLceKIKB1osoA16 > > W0x2YZWoLw8Lvifxt0ijwQSLdzU5H1CTXxHoQJLpygESdGJMbBYiOGirRnWR > > nnlHqnbHHwUbZDUsxUBZTBrutwVaXXmswYyfrgZvJo17ocSaT2goaPJ0F9oK > > JHpzDegTOIE6hbwUI3BnDLI6u7/gCE1ZvgrzSbIvXebZ8XKC67j0AwhKMX0Q > > zUjLpXQ2eq5XLKPlOnXUc/i6xYCIoNjoBRSHX95hd2N4zy7xuZ3UhrVn0ZBi > > 7ZRjo77h7BeRsB3F9bA61DfgN9pM+J+R9sPU3qYClXPB/cOJmyVqVFtcT7NK > > 0Tz+mfbFNI8KfhN9ZHMS16Q= > > =FsLz > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -----BEGIN PGP SIGNATURE----- Version: ProtonMail Comment: https://protonmail.com wsBcBAEBCAAGBQJcqlaMAAoJEO6drAP5JZWbQWIH/ilOz3NVPG5J+GpiNDv5 ju59FlI0TaxdS30sR1AwPhEnROGfso0vELw9EXVgmUrZbYYK05pa95FnHEps bHQSTJhkD7bMHzMYs/5O/mWTLA3CNHBGOuJW42pC/5l8EG8/+/vxNMKpfDJD zmft+QketkX/0n0vznmrO4kwn8pKVagqcBvkIMFSA2KvYRW/ldFA2xkNk6oR NbKGUAcCCU29erzwpDPfK4XOf+Qeqmrr1QOCPtX1OYLJSYZJgArPtUrG7Wy9 gcEyHsUO4GfEbhGWMqUiRHR3nlZnzRlFaVyYAJ5h292dZU1hh/Zb11DoCRzS FJXH901okncTHTqzs9PVdx0= =itms -----END PGP SIGNATURE-----

1 0