Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread lists
On 03.05.2020 23:36, ronqtorrel...@risley.net wrote: I got a *bunch* (harassment-level) of telephone calls from my ISP similar to this. They refused to do anything by email, and wouldn't tell me anything more about the supposed port-scanning attacks. They just kept asking me to "make sure Windows

Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread lists
On 03.05.2020 23:31, Roger Dingledine wrote: First of all thank you all. I have already written to masergy that they should send me logs and that the problem comes from them. If necessary, I have to block all masergy IP's on the firewall. But their AS is huge, does a lot of work Whether you

Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread niftybunny
So its a generic attack on an RFC 1918 IP. Thats really helpful. I also love the possible cause and the top-notch log …. People are getting paid real money to send this shit? niftybunny > On 3. May 2020, at 22:15, li...@for-privacy.net wrote: > > Hi, > > got multiple abuse in the last 2 weeks

Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread ronqtorrelays
I got a *bunch* (harassment-level) of telephone calls from my ISP similar to this. They refused to do anything by email, and wouldn't tell me anything more about the supposed port-scanning attacks. They just kept asking me to "make sure Windows and my router firmware were up to date." (No Window

Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread Roger Dingledine
On Sun, May 03, 2020 at 10:15:47PM +0200, li...@for-privacy.net wrote: > Below is the information about the attack. Keep in mind that the source IP > of our client has been sanitized for anonymity. > > Date: 04/30/2020 > Time: 11:05:37 > Time Zone: America/Chicago > Source(s): 37.157.255.118 > Ty

Re: [tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread gerard
That is really unhelpful of them to state Type of Attack/Scan: Generic Hosts: 10.10.10.182 which is non-routable address. Something on their LAN is wrong. You cannot even respond by blocking their actual WAN IP in torrc. Ask for the real WAN IP of their network so you can block the attack

[tor-relays] Again: abuse email for non-exit relay (masergy)

2020-05-03 Thread lists
Hi, got multiple abuse in the last 2 weeks. 2 relays with 2 IP run on the server. Someone is always hammering my OR port on one IP. (37.157.255.118:9002) https://metrics.torproject.org/rs.html#details/BD2A34ADE4E603A272FAAD23AEF389801BB223BB https://metrics.torproject.org/rs.html#details/8EE44

Re: [tor-relays] Recommended router for 200+ Mb/s relay

2020-05-03 Thread lists
On 30.04.2020 14:27, Logforme wrote: On 2020-04-29 17:13:49, "Secure Node" wrote: If you have an old PC with 2 ethernet ports laying around or you can get one cheap I suggest you build your own: https://arstechnica.com/gadgets/2016/04/the-ars-guide-to-building-a-linux-router-from-scratch/