[tor-relays] Re: Running a middle relay on home network

2024-11-11 Thread Marco Predicatori
Keifer Bly wrote on 11/9/24 22:03: Hi, So wondering for running a middle relay on a raspberry pi esque micro computer, what are the recommed maximum bandwidth for running a middle relay on a hole network (by a stock isp router, etc?)? Thanks. Be aware that some sites use idiotic blacklisting ser

[tor-relays] Re: Running a middle relay on home network

2024-11-11 Thread Toomore Chiang
Hi Keifer, Based on my experience, I am using a Raspberry Pi 5 to run a middle relay, and the average bandwidth is around 4.32 ~ 5.40 MiB/s, even though my home network in Taiwan has a ≅37.5MiB/s (300 Mb/s) connection. I think a ≅12.5MiB/s (100 Mb/s) upload/download speed is sufficient for t

[tor-relays] Running a middle relay on home network

2024-11-11 Thread Keifer Bly
Hi, So wondering for running a middle relay on a raspberry pi esque micro computer, what are the recommed maximum bandwidth for running a middle relay on a hole network (by a stock isp router, etc?)? Thanks. --Keifer ___ tor-relays mailing list -- tor-r

[tor-relays] Re: Raspberry Pi 4

2024-11-11 Thread Keifer Bly
Thinking of using a libre computer instead. --Keifer On Sat, Nov 9, 2024, 1:38 PM Keifer Bly wrote: > Ok thanks all. > > --Keifer > > On Thu, Nov 7, 2024, 6:43 AM Michael Wächter via tor-relays < > tor-relays@lists.torproject.org> wrote: > >> Hi all, >> I’m running a relay on a Pi 4 now for alm

[tor-relays] Re: Raspberry Pi 4

2024-11-11 Thread Keifer Bly
Ok thanks all. --Keifer On Thu, Nov 7, 2024, 6:43 AM Michael Wächter via tor-relays < tor-relays@lists.torproject.org> wrote: > Hi all, > I’m running a relay on a Pi 4 now for almost 2 years, almost no issues at > all. Average CPU load 40 %, average bandwidth 5 MB. > Updating to a newer version

[tor-relays] Metrics issue with my relay?

2024-11-11 Thread Carlo P. via tor-relays
Dear experts, my relay https://metrics.torproject.org/rs.html#details/0FBABB8C7B22CEDDFC849331E8E9E29C18081235 is shown as "down since more than three days" in Metrics. The logs on the server however seem to show normal activity: Nov 10 06:45:35 odin Tor[87753]: Heartbeat: It seems like we are

[tor-relays] Re: Tor relays source IPs spoofed to mass-scan port 22?

2024-11-11 Thread George Hartley via tor-relays
Hi, the node is back online. Everything works normally, and I don't get any bogus SSH packets when using iptraf-ng. Also, we noticed reverse path filtering was off on the VM.. we enabled it. but don't know why it was off.. I configured the ArchLinux VM's /etc/sysctl.d entries on my own, and i

[tor-relays] Re: Update: Tor relays source IPs spoofed to mass-scan port 22

2024-11-11 Thread a tor op via tor-relays
Hi, A few notes. I don't know if I have missed it but I don't recall seeing bridges mentioned in this discussion. I too have gotten an abuse message/info/alert from my hosting provider (Nov 8, 03:20 hrs) and I have an OBFS4 BRIDGE, no middle or exit node. And it has always been a bridge, from

[tor-relays] Re: Tor relays source IPs spoofed to mass-scan port 22?

2024-11-11 Thread George Hartley via tor-relays
Hello, add me to the list too. Started receiving packets 3 days ago and Tor Weather sent me an e-mail regarding it. Sad that I could not respond further.. I try to maintain an extremely high uptime. So far, the node has only been been offline for 6 hours in 6 months.. now it's been 72 hours :(

[tor-relays] Re: Raspberry Pi 4

2024-11-11 Thread George Hartley via tor-relays
Hey, I took a look at their boards and the AML-A311D-CC SBC looked like a great choice. 6 cores total, 4x ARM-73, 2x ARM-53 which also feature the crypto extensions. Said crypto roviding up to 40x more speed decoding / encoding AES which is great for openssl (and by extension, thus also Tor).

[tor-relays] Re: Update: Tor relays source IPs spoofed to mass-scan port 22

2024-11-11 Thread tor-operator
Roger Dingledine : > Hi! Can you send me (off-list) the details of what you are seeing? Done. The last observation was made Nov. 9 at 11:49 UTC, that is after it was announced the attacker was shut down. We no longer see the packets, but we continue to receive reports from the same mentioned am