[Dxspider-support] Again

Rudy Bakalov r_bakalov at yahoo.com
Sat Mar 22 17:58:26 GMT 2025


The point is the other way around- you didn’t get any spam when connected to N2WQ-1. I don’t see the spam many DXS sysops are talking about.

Rudy N2WQ

Sent using a tiny keyboard.  Please excuse brevity, typos, or inappropriate autocorrect.


> On Mar 22, 2025, at 12:55 PM, Kin <ea3cv at cronux.net> wrote:
> 
> 
> As soon as I was notified of a suspected attack, I logged into several nodes to try to see how each one responded.
> Unfortunately, I couldn't connect with VE7CC-1; I couldn't get past the login prompt, so I decided to try with N2WQ-1, as you can see in my previous email.
> I'm still logged in in case it happens again.
>  
> You won't receive any spam messages, just the sh/ver and who commands.
>  
> Kin EA3CV
>  
> De: Rudy Bakalov <r_bakalov at yahoo.com>
> Enviado el: sábado, 22 de marzo de 2025 17:39
> Para: rene at rcolsen.dk; 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
> CC: Kin <ea3cv at cronux.net>
> Asunto: Re: [Dxspider-support] Again
>  
> Earlier today I noticed that EA3CV-12 is connected to N2WQ-1 and decided to observe the spots he is getting. I had coffee and breakfast, fed the dogs, talked to my family, etc. all while keeping an eye on the screen.
>  
> I didn't see a single spot like the ones discussed here. Zero. Maybe my timing was off. I don't have an explanation why, but it might be worth connecting to multiple clusters of various types to see how they handle/drop bad spots.
>  
> Rudy N2WQ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250322/33ee55a0/attachment-0001.htm>


More information about the Dxspider-support mailing list