<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hello Sysops of RBN and cluster nodes</div>
<div> </div>
<div>there is frustration and disappointment in the DX cluster network all around the world. Meanwhile I did read a lot of complaints and lots of emails reached me also asking about F8DGY and possibilities to mitigate his spamming actions. As we discussed here on the list, the RBN and DXcluster are two separate areas we need to keep divorced. It's self-explanatory that F8DGY's action is regarded as spamming the DXcluster network, irrespective of whether CC, ARc or DXspider is used and whether F8DGY is doing this intended or not. The information is propagated through the network and reach all connected users, that's the bad thing!</div>
<div> </div>
<div>In my opinion there are 3 ways to fight against this spamming action:</div>
<div>method 1)</div>
<div>is intended to all Sysops running DX cluster node (like CCc, ARc, DXspider). It was explained in detail in my previous message. I attached it to this message, just scroll down to the bottom and read. All Sysops of DX cluster nodes are encouraged to add the spamming callsign F8DGY to their node. Not waterproof because EVERY sysop would need to perform this action, how to enforce ?</div>
<div> </div>
<div>method 2)</div>
<div>is intended to the developers (root) of the various DX cluster systems (DXspider, CCC, ARc). They could add a global filtering rule for this BadCall F8DGY into their system and forbid propagating spots under the spotter callsign F8DGY. This method is not easy to fulfill and means a lot of work for the dev of each network. And regarding the ARcluster it's difficult because most of you know that the author and developer of ARc is silent key.</div>
<div> </div>
<div>method 3)</div>
<div>would be the most accurate and easiest in my humble opinion: rejecting/blocking the callsign F8DGY on the root of the RBN and/or on the application "CW SkimSrv". That means the devs of RBN and/or VE3NEA, Alex (=developer of CW SkimSrv) would place this bad callsign F8DGY into a reject rule, so the skimmer server running "CW SkimSrv + RBN Aggregator" with the callsign F8DGY is not allowed to use "CW SkimSrv + RBN Aggregator" under the callsign F8DGY at all.</div>
<div> </div>
<div>I mean: there MUST be a way to fight against such spammers. Just imagine tomorror or next week there are 5 other guys doing the same action with their SDR receiver. They will flood the whole network, that would be a DoS attack.</div>
<div> </div>
<div>What do you think, how to progress? Doing nothing, leaning back and watching the spamming actions ?</div>
<div> </div>
<div>just my 2 cents</div>
<div>73 // Saki, DD5XX</div>
<div> </div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Donnerstag, 17. Oktober 2019 um 12:42 Uhr<br/>
<b>Von:</b> dd5xx@web.de<br/>
<b>An:</b> dxspider-support@tobit.co.uk<br/>
<b>Betreff:</b> Aw: [Dxspider-support] SDR Spot to avoid on "classic" Cluster</div>
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Salut Pat,</div>
<div> </div>
<div>obviously you mean the spots from F8DGY. This operator seems not willing to cooperate and both the cluster developers and the RBN devs are aware about this issue we're currently facing. There are a lot of complaints around the net and there even were a lot of complaints about this user in the past years.</div>
<div> </div>
<div>I already did send a suggestion through the list and showed with basic command how to block/ban spots from this user F8DGY but unless all (!) cluster sysops will add the particular reject filter to their node, it won't happen anything. Me myself, I blocked this spotter callsign from my own node at dd5xx.dxcluster.net:7000 and I am clear of this spammer abusing the cluster. To my knowledge there seems either no technical way or no interest from the DX cluster developers to implement a "global" reject rule into their software (DXspider, ARcluster, CC, ...)</div>
<div> </div>
<div>I have no clue how else we can prevent such spammers abusing the cluster network.</div>
<div> </div>
<div>73 // Saki, DD5XX</div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Mittwoch, 16. Oktober 2019 um 21:52 Uhr<br/>
<b>Von:</b> "f6gcp--- via Dxspider-support" <dxspider-support@tobit.co.uk><br/>
<b>An:</b> Dxspider-support@dxcluster.org<br/>
<b>Cc:</b> f6gcp@free.fr<br/>
<b>Betreff:</b> [Dxspider-support] SDR Spot to avoid on "classic" Cluster</div>
<div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hi</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Some people are now sending automatic spot from SDR while connected as user on « classic DXCluster »</p>
<p class="MsoNormal">I know it is possible to add such station to a black list, but no sense to perform this on one or few clusters.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I don’t know the policy about such stations and if a group already discussed on this.</p>
<p class="MsoNormal">I just know that SDR spots are only passed to specific station, and not spread out to « classic » clusters</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">73</p>
<p class="MsoNormal">P@t – F6GCP</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Dienstag, 15. Oktober 2019 um 11:58 Uhr<br/>
<b>Von:</b> dd5xx@web.de<br/>
<b>An:</b> "Dirk Koopman (G1TLH)" <dxspider-support@tobit.co.uk>, RBN-OPS@groups.io<br/>
<b>Betreff:</b> reject bad spotter callsign F8DGY from all DX cluster networks</div>
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>To all DX cluster SysOps !</div>
<div> </div>
<div>I highly recommend to block the callsign "F8DGY" from your DX cluster node.</div>
<div> </div>
<div>As most of you did read about the issue with F8DGY spots on the list, someone is flooding (self-)spots the DX cluster network and thus abusing the services. Although this guy has been contacted through email it didn't reveal any helpful information to counterfeit against. There are a lot of complaints around the world, see</div>
<div> </div>
<div>"<a href="https://dxheat.com/db/f8dgy" target="_blank">https://dxheat.com/db/f8dgy</a>"</div>
<div> </div>
<div>and also some historic complaints about F8DGY in the past</div>
<div> </div>
<div>"<a href="http://forum.log4om.com/viewtopic.php?t=1390" target="_blank">http://forum.log4om.com/viewtopic.php?t=1390</a>"</div>
<div> </div>
<div>So it seems this guy either is not telling the truth or intensionally abusing the cluster network. As there is no global filter mechanism on the DX cluster network yet implemented and lots of ham operators around the world are annoyed by the spots originatedfrom callsign F8DGY ...</div>
<div> </div>
<div>==> <u>I highly recommend to all DX cluster node SysOps to <strong>REJECT </strong>the callsign <strong>F8DGY </strong>as it is regarded as a bad spotter callsign.</u></div>
<div> </div>
<div>I want to add that this guy added the note on his own QRZ.com page that he never used or uses any cluster network so this blocking action should not affect him at all and cannot give him any reason to complain about.</div>
<div> </div>
<div>On a DXspider node you can add the block filter with this command:</div>
<div><strong>set/badspotter F8DGY</strong></div>
<div>
<div>This command runs fine on my DXspider node. Alternatively on DXspider nodes one could try "reject/spots by F8DGY"</div>
<div> </div>
<div>I don't know about the AR cluster nodes in detail, but after some research I found the manual ("<a href="http://lynxdxg.com/archivos/AR-Cluster%20User%20Manual.pdf" target="_blank">http://lynxdxg.com/archivos/AR-Cluster%20User%20Manual.pdf</a>") and if understood correctly the command for AR cluster nodes should be:</div>
<div><strong>set/filter dxkeyword/reject /f8dgy</strong></div>
<div> </div>
<div>On a CC cluster node according the manual ("<a href="http://bcdxc.org/ve7cc/ccc/CCC_Commands.htm" target="_blank">http://bcdxc.org/ve7cc/ccc/CCC_Commands.htm</a>") the command should be:</div>
<div><strong>set/filter keyword/reject f8dgy</strong><br/>
</div>
<div> </div>
<div> </div>
<div>73</div>
<div>Saki, DD5XX</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>