[Dxspider-support] Skimmer feeds?

Danilo Brelih s50u at s50e.si
Wed Feb 19 10:01:59 GMT 2025


The RBN guys have solved the problem and the RBN feeds are up again.

CU Dan S50U



>
> I get "Invalid callsign" even if I connect manually from the console. Most 
> likely a mistake with them I didn't make any changes on that myself. I'll have 
> to check with them or if someone drops the connection and tries a new telnet 
> rbn session to be sure?
>
> Thanks, Dan
>
>
> 1739950140^(connect) CONNECT 281 sort: telnet command: telnet.reversebeacon.net 7001
> 1739950140^(connll) ExtMsg connecting 281 to telnet.reversebeacon.net:7001
> 1739950140^(connect) Connected 281 to telnet.reversebeacon.net 7001
> 1739950140^(progress) CMD: 'connect SK1MMR' by S50CLX ip: localhost 4mS
> 1739950140^(cron) DXCron::cmd out: connection to SK1MMR started
> 1739950140^(conn) ExtMsg connected 281:10.1.1.1 to 44.52.120.51:7001
> 1739950140^(conn) ExtMsg connected 280:10.1.1.1 to 44.10.10.51:7000
> 1739950140^(connect) connect 281: Please enter your call:
> 1739950140^(connect) connect 281: expecting: "call:" received: "Please enter your call: "
> 1739950140^(connect) connect 281: got: "call:" sending: "s50clx"
> 1739950140^(connect) connect 280: Please enter your call:
> 1739950140^(connect) connect 280: expecting: "call:" received: "Please enter your call: "
> 1739950140^(connect) connect 280: got: "call:" sending: "s50clx"
> 1739950140^(connect) connect 281: Invalid callsign. Disconnecting...%0D
> 1739950140^(connll) ExtMsg Connection 281 SK1MMR stored
> 1739950140^(connll) Timer deleted (notimers: 2)
> 1739950140^(connll) timer destroyed (2)
> 1739950140^(connll) ExtMsg Connection 281 SK1MMR stored
> 1739950140^(chan) DXChannel SK1MMR created (38)
> 1739950140^(state) SK1MMR channel func  state 0 -> prompt
> 1739950140^(*) SK1MMR connected from 44.52.120.51
> 1739950140^(*) RBN: noinrush: 1, setting inrushpreventor on SK1MMR to 0
> 1739950140^(connll) ExtMsg::disconnect on call SK1MMR attempt 1 called from Msg::/spider/perl/Msg.pm line 169
> 1739950140^(*) ExtMsg socket missing on SK1MMR
> 1739950140^(connll) ExtMsg::_close_it on call SK1MMR attempt 1 called from Msg::/spider/perl/Msg.pm line 317
> 1739950140^(connll) ExtMsg Connection 281 SK1MMR starting to close
> 1739950140^(connll) ExtMsg::disconnect on call SK1MMR attempt 2 called from DXChannel::/spider/perl/DXChannel.pm line 527
> 1739950140^(chan) DXChannel SK1MMR destroyed (38)
> 1739950140^(trace) ExtMsg::DESTROY on call SK1MMR called from Mojo::IOLoop::Stream::/usr/share/perl5/Mojo/IOLoop/Stream.pm line 107
> 1739950140^(connll) ExtMsg Connection 281 SK1MMR [44.52.120.51 7001] being destroyed (total 41)
> 1739950141^(chan) <- I N6WS-6 PC92^9M2PJU-2^26941^K^59M2PJU-2:5457:568^17^9^H98^
> 1739950141^(connect) connect 280: Invalid callsign. Disconnecting...%0D
>
>
>
>
>> Are skimmer feeds unreachable only by me this morning?
>>
>> Sorry QRM, we are all under the impression of the latest attack on the 
>> dxcluster network. 😕
>>
>> Dan
>>
>>
>> DXSpider v1.57 (build 568 git: mojo/0920a333[r]) using perl v5.34.0 on Linux
>> Copyright (c) 1998-2025 Dirk Koopman G1TLH
>> S50U de S50CLX 19-Feb-2025 0651Z 2.4481  dxspider >
>>
>> 19Feb2025 at 06:29:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:30:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:31:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:32:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:33:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:34:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:35:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:36:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:37:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:38:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:39:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:40:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:41:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:42:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:43:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:44:01 SK0MMR connected from 44.10.10.51
>> 19Feb2025 at 06:45:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:46:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:47:00 SK0MMR connected from 44.52.120.51
>> 19Feb2025 at 06:48:01 SK0MMR connected from 44.10.10.51
>> -- 
>> S50CLX DX Cluster <https://s50clx.infrax.si>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> -- 
> S50CLX DX Cluster <https://s50clx.infrax.si>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support


-- 
S50CLX DX Cluster <https://s50clx.infrax.si>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250219/c854d09d/attachment-0001.htm>


More information about the Dxspider-support mailing list