[Dxspider-support] Ending ham.cm flooding
Mike G3YPP
mike at g3ypp.uk
Mon Jan 9 22:45:24 GMT 2023
Dirk,
According to their blurb the hamaward.cloud system used by WRTC adds the ham.cm/wrtc23 comment to spots
Anyway, I look forward to any updates. My node is on 1.57 build 351
Regards
Mike
Sent from my iPad
> On 9 Jan 2023, at 22:37, dxspider-support-request at tobit.co.uk wrote:
>
> Send Dxspider-support mailing list submissions to
> dxspider-support at tobit.co.uk
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> or, via email, send a message with subject or body 'help' to
> dxspider-support-request at tobit.co.uk
>
> You can reach the person managing the list at
> dxspider-support-owner at tobit.co.uk
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dxspider-support digest..."
>
>
> Today's Topics:
>
> 1. Re: Ending ham.cm flooding (Dirk Koopman)
> 2. Re: Ending ham.cm flooding (Dirk Koopman)
> 3. Re: Ending ham.cm flooding (Lee Sawkins)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 9 Jan 2023 22:01:15 +0000
> From: Dirk Koopman <djk at tobit.co.uk>
> To: Keith Maton via Dxspider-support <dxspider-support at tobit.co.uk>
> Subject: Re: [Dxspider-support] Ending ham.cm flooding
> Message-ID: <64a4e54c-1faa-34a9-af5b-b09c1cda5b53 at tobit.co.uk>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> I fought hard with myself to avoid it slipping out: but, but it's got me!
>
> BRU HAH HAH HAH
>
>> On 09/01/2023 20:11, Keith Maton via Dxspider-support wrote:
>> Ahh right, I hadn?t realised the spots were actually from spoofed callsigns.
>>
>> In which case, yes, I have no problem with stopping them.
>>
>> "But not for much longer ??
>>
>> I?m all in :-)
>>
>> 73 Keith G6NHU
>>
>>
>>
>>>> On 9 Jan 2023, at 17:49, Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>
>>> Sadly, they are coming from an IP address that is connected to many node using callsigns that are not his. The spots look genuine, but are not being sent by the owners of those callsigns.
>>>
>>> He has some considerable form doing this + more overt mischief, especially in contests. But not for much longer ...
>>>
>>> 73 de Dirk G1TLH
>>>
>>> On 09/01/2023 17:19, Keith Maton via Dxspider-support wrote:
>>>> Perhaps I?m being naive but although there are a lot of spots for these WRTC award stations, they do appear to be genuine. They?re coming from award chasers who all seem to be using the same web site to log their QSOs which then sends out a spot.
>>>>
>>>> Just because stations are being spotted a lot, why should we remove them?
>>>>
>>>> I initially looked at these spots with a view to stopping them but the more I thought about it, I decided I didn?t think it was a good idea.
>>>>
>>>> There are lots of spots posted for dxpeditions, especially busy ones. We wouldn?t consider removing or blocking those, why would we look at blocking these award station spots?
>>>>
>>>> In fact, yesterday, I used the spots to work a dozen or so of the WRTC stations. Some of them have big pileups so it was fun breaking them.
>>>>
>>>> 73 Keith G6NHU
>>>>
>>>>
>>>>
>>>>> On 9 Jan 2023, at 16:42, Jim Reisert AD1C via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>>>
>>>>> I guess that finally explains why all the spots tell me to check out
>>>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>>>> the WRTC page. I did not realize that the URL was being truncated
>>>>> along the way.
>>>>>
>>>>> --
>>>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>>>
>>>>> _______________________________________________
>>>>> Dxspider-support mailing list
>>>>> Dxspider-support at tobit.co.uk
>>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 9 Jan 2023 22:08:28 +0000
> From: Dirk Koopman <djk at tobit.co.uk>
> To: Mike G3YPP via Dxspider-support <dxspider-support at tobit.co.uk>
> Subject: Re: [Dxspider-support] Ending ham.cm flooding
> Message-ID: <df18d870-fa1b-faf9-c963-ae846254d8e6 at tobit.co.uk>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> That is as maybe, but what I was talking about is this:
>
> 21:33:14 (chan) <- I GB7MBC PC61^14022.6^N5W^ 9-Jan-2023^2133Z^WRTC 2023
> Award > ham.cm/wrtc23^K5WA^VE9SC^217.61.58.23^H27^~
> 21:38:47 (chan) <- I GB7MBC PC61^3746.0^CQ7WRTC^ 9-Jan-2023^2138Z^WRTC
> 2023 Award > ham.cm/wrtc23^CT1CJJ^ON4KST-2^217.61.58.23^H27^~
> 21:43:09 (chan) <- I GB7MBC PC61^7173.0^II1WRTC^ 9-Jan-2023^2143Z^WRTC
> 2023 Award > ham.cm/wrtc23^IK1TAZ^IZ6RND-6^217.61.58.23^H27^~
> 21:46:14 (chan) <- I GB7MBC PC61^28026.0^ZL6WRTC^ 9-Jan-2023^2146Z^WRTC
> 2023 Award > ham.cm/wrtc23^ZL3GA^ON4KST-2^217.61.58.23^H27^~
> 21:46:58 (chan) <- I GB7MBC PC61^14205.0^CQ7WRTC^ 9-Jan-2023^2146Z^WRTC
> 2023 Award > ham.cm/wrtc23^CT2IMG^ON4KST-2^217.61.58.23^H27^~
> 21:47:27 (chan) <- I GB7MBC PC61^7005.3^PY5WRTC^ 9-Jan-2023^2147Z^WRTC
> 2023 Award > ham.cm/wrtc23^PY2NY^SR2PUT^217.61.58.23^H28^~
> 21:51:35 (chan) <- I GB7MBC PC61^21030.0^ZL6WRTC^ 9-Jan-2023^2151Z^WRTC
> 2023 Award > ham.cm/wrtc23^ZL3GA^ON4KST-2^217.61.58.23^H27^~
> 21:52:23 (chan) <- I GB7MBC PC61^14258.0^PY5WRTC^ 9-Jan-2023^2152Z^WRTC
> 2023 Award > ham.cm/wrtc23^PY2CP^IZ6RND-6^217.61.58.23^H26^~
>
> Which I believe is nothing (official) to do with WRTC 2023.
>
> A solution to this other nasties perpetrated by some twisted individuals
> is currently in testing which stops nearly all of this dead.
>
> Every DXSpider node upgrading to mojo would stop ALL of this dead (and
> in more than one way). Bru hah hah etc.
>
> 73 de Dirk G1TLH
>
>> On 09/01/2023 21:12, Mike G3YPP via Dxspider-support wrote:
>> The public facing website is hamaward.cloud. This is the paid for service being used by the WRTC 2023 Award activation. One of the services offered is automatic spotting to the DX cluster with customised comments.
>>
>> Someone needs to have words
>> Mike G3YPP
>> Sysop for MX0NCA-2
>>
>> Sent from my iPad
>>
>>>> On 9 Jan 2023, at 18:40, dxspider-support-request at tobit.co.uk wrote:
>>>
>>> ?Send Dxspider-support mailing list submissions to
>>> dxspider-support at tobit.co.uk
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>> or, via email, send a message with subject or body 'help' to
>>> dxspider-support-request at tobit.co.uk
>>>
>>> You can reach the person managing the list at
>>> dxspider-support-owner at tobit.co.uk
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Dxspider-support digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>> 1. Re: Remote sysop password ? (Kin EA3CV)
>>> 2. DXSpider and Web Clusters (Lee Sawkins)
>>> 3. Re: Ending ham.cm flooding (Jim Reisert AD1C)
>>> 4. Re: Ending ham.cm flooding (Keith Maton)
>>> 5. Re: Ending ham.cm flooding (Dirk Koopman)
>>> 6. Re: DXSpider and Web Clusters (Kin)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Mon, 9 Jan 2023 15:26:30 +0100
>>> From: Kin EA3CV <ea3cv at cronux.net>
>>> To: Gabriel - EA6VQ <ea6vq at dxmaps.com>, Tobias Wellnitz via
>>> Dxspider-support <dxspider-support at tobit.co.uk>
>>> Subject: Re: [Dxspider-support] Remote sysop password ?
>>> Message-ID: <81594C2A-B6B6-9045-A5D1-2B6B8D60A552 at hxcore.ol>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> An HTML attachment was scrubbed...
>>> URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230109/bb92b941/attachment-0001.htm>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Mon, 9 Jan 2023 09:43:00 -0700 (MST)
>>> From: Lee Sawkins <ve7cc at shaw.ca>
>>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>>> Subject: [Dxspider-support] DXSpider and Web Clusters
>>> Message-ID:
>>> <1777489283.102792676.1673282580459.JavaMail.zimbra at shaw.ca>
>>> Content-Type: text/plain; charset=utf-8
>>>
>>> Some time ago both DXSpider and CC Cluster node software starting including the IP addresses of spotters along with the DX spots. This was a big step forward in helping to clean up bad spots. The IP addresses helped identified the spotters even when they used bogus call signs. As a minimum, even if the spotter's real call sign could not be determined, at least the spots could be identified and dropped.
>>>
>>> Recent hundreds if not thousands of spam spots advertising a commercial web site were recently seen in the system. These spots all had identical comments and all came from the same IP address of 217.61.58.23. This can be solved by dropping all PC61 spots from this IP address. Some still get through as they are converted to PC11 spots which do not include the bad address. These can be filtered out by the bad comments.
>>>
>>> There are several Web Clusters that are running DXSpider software to interface to the DX Cluster system. One of these is F5LEN-5. Recently I have seen bad spots trashing Bolsonaro from PY calls using this node. These spots included IP addresses of 51.68.11.211. These spots could also be filtered by the IP address. Unfortunately it appears this IP address is the IP address where the web cluster. All spots originating at the F5LEN-3 node end up with the same IP address. Since not all web clusters do this I can only assume that it is caused by badly written web cluster software. Perhaps the F5LEN-3 software could be changed to include the correct addresses of spotters so we could drop just the bad spots. Otherwise we will be blocking all spots from this web cluster.
>>>
>>> Lee VE7CC
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Mon, 9 Jan 2023 09:42:50 -0700
>>> From: Jim Reisert AD1C <jjreisert at alum.mit.edu>
>>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>>> Cc: Mikel Berrocal <mikelberrocal at gmail.com>
>>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>>> Message-ID:
>>> <CAK-n8j7XTkyu26BLS+L1jmTZfUhTC6EmoJHYbjhH3GPcaq5zaA at mail.gmail.com>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> I guess that finally explains why all the spots tell me to check out
>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>> the WRTC page. I did not realize that the URL was being truncated
>>> along the way.
>>>
>>> --
>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 4
>>> Date: Mon, 9 Jan 2023 17:19:11 +0000
>>> From: Keith Maton <g6nhu at me.com>
>>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>>> Message-ID: <B6EB2BF0-B1C5-4F16-9480-2378C3F04767 at me.com>
>>> Content-Type: text/plain; charset=utf-8
>>>
>>> Perhaps I?m being naive but although there are a lot of spots for these WRTC award stations, they do appear to be genuine. They?re coming from award chasers who all seem to be using the same web site to log their QSOs which then sends out a spot.
>>>
>>> Just because stations are being spotted a lot, why should we remove them?
>>>
>>> I initially looked at these spots with a view to stopping them but the more I thought about it, I decided I didn?t think it was a good idea.
>>>
>>> There are lots of spots posted for dxpeditions, especially busy ones. We wouldn?t consider removing or blocking those, why would we look at blocking these award station spots?
>>>
>>> In fact, yesterday, I used the spots to work a dozen or so of the WRTC stations. Some of them have big pileups so it was fun breaking them.
>>>
>>> 73 Keith G6NHU
>>>
>>>
>>>
>>>> On 9 Jan 2023, at 16:42, Jim Reisert AD1C via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>>
>>>> I guess that finally explains why all the spots tell me to check out
>>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>>> the WRTC page. I did not realize that the URL was being truncated
>>>> along the way.
>>>>
>>>> --
>>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>>
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 5
>>> Date: Mon, 9 Jan 2023 17:49:48 +0000
>>> From: Dirk Koopman <djk at tobit.co.uk>
>>> To: dxspider-support at tobit.co.uk
>>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>>> Message-ID: <3d3c2c8a-9990-c950-d539-77377d324692 at tobit.co.uk>
>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>>
>>> Sadly, they are coming from an IP address that is connected to many node
>>> using callsigns that are not his. The spots look genuine, but are not
>>> being sent by the owners of those callsigns.
>>>
>>> He has some considerable form doing this + more overt mischief,
>>> especially in contests. But not for much longer ...
>>>
>>> 73 de Dirk G1TLH
>>>
>>>> On 09/01/2023 17:19, Keith Maton via Dxspider-support wrote:
>>>> Perhaps I?m being naive but although there are a lot of spots for these WRTC award stations, they do appear to be genuine. They?re coming from award chasers who all seem to be using the same web site to log their QSOs which then sends out a spot.
>>>>
>>>> Just because stations are being spotted a lot, why should we remove them?
>>>>
>>>> I initially looked at these spots with a view to stopping them but the more I thought about it, I decided I didn?t think it was a good idea.
>>>>
>>>> There are lots of spots posted for dxpeditions, especially busy ones. We wouldn?t consider removing or blocking those, why would we look at blocking these award station spots?
>>>>
>>>> In fact, yesterday, I used the spots to work a dozen or so of the WRTC stations. Some of them have big pileups so it was fun breaking them.
>>>>
>>>> 73 Keith G6NHU
>>>>
>>>>
>>>>
>>>>>> On 9 Jan 2023, at 16:42, Jim Reisert AD1C via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>>> I guess that finally explains why all the spots tell me to check out
>>>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>>>> the WRTC page. I did not realize that the URL was being truncated
>>>>> along the way.
>>>>>
>>>>> --
>>>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>>>
>>>>> _______________________________________________
>>>>> Dxspider-support mailing list
>>>>> Dxspider-support at tobit.co.uk
>>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 6
>>> Date: Mon, 9 Jan 2023 19:39:16 +0100
>>> From: "Kin" <ea3cv at cronux.net>
>>> To: "'The DXSpider Support list'" <dxspider-support at tobit.co.uk>
>>> Subject: Re: [Dxspider-support] DXSpider and Web Clusters
>>> Message-ID: <004301d92459$adff0180$09fd0480$@cronux.net>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Lee,
>>> DXSpider nodes (not archaic) that have a webcluster associated, have a very
>>> easy way to incorporate the user's IP so that it appears on the PC61.
>>>
>>> Ideally, those nodes would first update to the latest version, and then add
>>> the IP. As the WebCluster URE, DXHEAT or DXFun have done.
>>>
>>> If any sysop needs information to add the user's IP to dxspider, tell me and
>>> I'll be happy to help you.
>>>
>>> Kin EA3CV
>>>
>>> -----Mensaje original-----
>>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Lee
>>> Sawkins via Dxspider-support
>>> Enviado el: lunes, 9 de enero de 2023 17:43
>>> Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
>>> CC: Lee Sawkins <ve7cc at shaw.ca>
>>> Asunto: [Dxspider-support] DXSpider and Web Clusters
>>>
>>> Some time ago both DXSpider and CC Cluster node software starting including
>>> the IP addresses of spotters along with the DX spots. This was a big step
>>> forward in helping to clean up bad spots. The IP addresses helped
>>> identified the spotters even when they used bogus call signs. As a minimum,
>>> even if the spotter's real call sign could not be determined, at least the
>>> spots could be identified and dropped.
>>>
>>> Recent hundreds if not thousands of spam spots advertising a commercial web
>>> site were recently seen in the system. These spots all had identical
>>> comments and all came from the same IP address of 217.61.58.23. This can be
>>> solved by dropping all PC61 spots from this IP address. Some still get
>>> through as they are converted to PC11 spots which do not include the bad
>>> address. These can be filtered out by the bad comments.
>>>
>>> There are several Web Clusters that are running DXSpider software to
>>> interface to the DX Cluster system. One of these is F5LEN-5. Recently I
>>> have seen bad spots trashing Bolsonaro from PY calls using this node. These
>>> spots included IP addresses of 51.68.11.211. These spots could also be
>>> filtered by the IP address. Unfortunately it appears this IP address is the
>>> IP address where the web cluster. All spots originating at the F5LEN-3 node
>>> end up with the same IP address. Since not all web clusters do this I can
>>> only assume that it is caused by badly written web cluster software.
>>> Perhaps the F5LEN-3 software could be changed to include the correct
>>> addresses of spotters so we could drop just the bad spots. Otherwise we
>>> will be blocking all spots from this web cluster.
>>>
>>> Lee VE7CC
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>>
>>> ------------------------------
>>>
>>> End of Dxspider-support Digest, Vol 240, Issue 20
>>> *************************************************
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 9 Jan 2023 15:36:47 -0700 (MST)
> From: Lee Sawkins <ve7cc at shaw.ca>
> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
> Subject: Re: [Dxspider-support] Ending ham.cm flooding
> Message-ID:
> <1347131721.104135299.1673303807735.JavaMail.zimbra at shaw.ca>
> Content-Type: text/plain; charset=utf-8
>
> I believe the WRTC2023 group is paying money for spots containing the comments "ham.cm/wrtc23" to be sent to the DX Cluster.
>
> I posted the following 2 emails to CQ-Contest at contesting.com. The first on 3 Nov 2021. Second 28 Nov 2921.
> There has been a huge amount of time spent by many people looking at activity by IP 217.61.58.23
> Many contest operators were concerned they would be disqualified for self spotting due to these spots.
> The contest committee assured everyone that they would very carefully check all the logs.
> Many node sysops were asked by the contest committee to sent complete logs of every spot for the days in question.
> If you have any questions about why this IP address should be dropped then look at these logs.
>
> To CQ on 3 Nov 2021
>
>> From the VE7CC-1 cluster log.
>
> 30 Oct total spoofed spots 866 out of 50140 non skimmer spots.
> 31 Oct total spoofed spots 1956 out of 51741 non skimmer spots.
> Total 2822 spoofed spots from IP 217.61.58.23 over weekend.
> 439 were self spots.
>
> Handful of spoofed spots on 28 and 29 Oct. Appears spoofer was testing program.
>
> These spoofed spots are only the ones that I identified with IP 217.61.58.23.
> These spots were entered on both DX Spider and CC Cluster nodes. There could
> be more from AR Cluster or Spider nodes running software that doesn't include
> IP addresses.
>
> https://bcdxc.org/ve7cc/SelfSpot-Oct-2021.zip
> http://bcdxc.org/ve7cc/30-Oct-2021.zip
> http://bcdxc.org/ve7cc/31-Oct-2021.zip
>
> Lee VE7CC
>
> To CQ on 28 Nov 2021
>> From the VE7CC-1 cluster log.
>
> 27 Nov total spoofed spots 599 out of 30018 non skimmer spots.
> 28 Nov total spoofed spots 1117 out of 30073 non skimmer spots.
> Total 1716 spoofed spots from IP 217.61.58.23 over weekend.
>
> Includes
> 203 self spots 27 Nov 2021
> 385 self spots 28 Nov 2021
>
> These spoofed spots are only the ones that I identified with IP 217.61.58.23.
> These spots were entered on both DX Spider and CC Cluster nodes. There could
> be more from AR Cluster or Spider nodes running software that doesn't include
> IP addresses.
>
> https://bcdxc.org/ve7cc/SelfSpot-Nov-2021.zip
> http://bcdxc.org/ve7cc/27-Nov-2021.zip
> http://bcdxc.org/ve7cc/28-Nov-2021.zip
>
> Lee VE7CC
> ________________
>
>
> ----- Original Message -----
> From: "The DXSpider Support list" <dxspider-support at tobit.co.uk>
> To: "The DXSpider Support list" <dxspider-support at tobit.co.uk>
> Cc: "G3YPP" <mike at g3ypp.uk>
> Sent: Monday, January 9, 2023 9:12:30 PM
> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>
> The public facing website is hamaward.cloud. This is the paid for service being used by the WRTC 2023 Award activation. One of the services offered is automatic spotting to the DX cluster with customised comments.
>
> Someone needs to have words
> Mike G3YPP
> Sysop for MX0NCA-2
>
> Sent from my iPad
>
>> On 9 Jan 2023, at 18:40, dxspider-support-request at tobit.co.uk wrote:
>>
>> ?Send Dxspider-support mailing list submissions to
>> dxspider-support at tobit.co.uk
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>> or, via email, send a message with subject or body 'help' to
>> dxspider-support-request at tobit.co.uk
>>
>> You can reach the person managing the list at
>> dxspider-support-owner at tobit.co.uk
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Dxspider-support digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: Remote sysop password ? (Kin EA3CV)
>> 2. DXSpider and Web Clusters (Lee Sawkins)
>> 3. Re: Ending ham.cm flooding (Jim Reisert AD1C)
>> 4. Re: Ending ham.cm flooding (Keith Maton)
>> 5. Re: Ending ham.cm flooding (Dirk Koopman)
>> 6. Re: DXSpider and Web Clusters (Kin)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 9 Jan 2023 15:26:30 +0100
>> From: Kin EA3CV <ea3cv at cronux.net>
>> To: Gabriel - EA6VQ <ea6vq at dxmaps.com>, Tobias Wellnitz via
>> Dxspider-support <dxspider-support at tobit.co.uk>
>> Subject: Re: [Dxspider-support] Remote sysop password ?
>> Message-ID: <81594C2A-B6B6-9045-A5D1-2B6B8D60A552 at hxcore.ol>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> An HTML attachment was scrubbed...
>> URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230109/bb92b941/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 9 Jan 2023 09:43:00 -0700 (MST)
>> From: Lee Sawkins <ve7cc at shaw.ca>
>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>> Subject: [Dxspider-support] DXSpider and Web Clusters
>> Message-ID:
>> <1777489283.102792676.1673282580459.JavaMail.zimbra at shaw.ca>
>> Content-Type: text/plain; charset=utf-8
>>
>> Some time ago both DXSpider and CC Cluster node software starting including the IP addresses of spotters along with the DX spots. This was a big step forward in helping to clean up bad spots. The IP addresses helped identified the spotters even when they used bogus call signs. As a minimum, even if the spotter's real call sign could not be determined, at least the spots could be identified and dropped.
>>
>> Recent hundreds if not thousands of spam spots advertising a commercial web site were recently seen in the system. These spots all had identical comments and all came from the same IP address of 217.61.58.23. This can be solved by dropping all PC61 spots from this IP address. Some still get through as they are converted to PC11 spots which do not include the bad address. These can be filtered out by the bad comments.
>>
>> There are several Web Clusters that are running DXSpider software to interface to the DX Cluster system. One of these is F5LEN-5. Recently I have seen bad spots trashing Bolsonaro from PY calls using this node. These spots included IP addresses of 51.68.11.211. These spots could also be filtered by the IP address. Unfortunately it appears this IP address is the IP address where the web cluster. All spots originating at the F5LEN-3 node end up with the same IP address. Since not all web clusters do this I can only assume that it is caused by badly written web cluster software. Perhaps the F5LEN-3 software could be changed to include the correct addresses of spotters so we could drop just the bad spots. Otherwise we will be blocking all spots from this web cluster.
>>
>> Lee VE7CC
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Mon, 9 Jan 2023 09:42:50 -0700
>> From: Jim Reisert AD1C <jjreisert at alum.mit.edu>
>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>> Cc: Mikel Berrocal <mikelberrocal at gmail.com>
>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>> Message-ID:
>> <CAK-n8j7XTkyu26BLS+L1jmTZfUhTC6EmoJHYbjhH3GPcaq5zaA at mail.gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> I guess that finally explains why all the spots tell me to check out
>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>> the WRTC page. I did not realize that the URL was being truncated
>> along the way.
>>
>> --
>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 9 Jan 2023 17:19:11 +0000
>> From: Keith Maton <g6nhu at me.com>
>> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>> Message-ID: <B6EB2BF0-B1C5-4F16-9480-2378C3F04767 at me.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> Perhaps I?m being naive but although there are a lot of spots for these WRTC award stations, they do appear to be genuine. They?re coming from award chasers who all seem to be using the same web site to log their QSOs which then sends out a spot.
>>
>> Just because stations are being spotted a lot, why should we remove them?
>>
>> I initially looked at these spots with a view to stopping them but the more I thought about it, I decided I didn?t think it was a good idea.
>>
>> There are lots of spots posted for dxpeditions, especially busy ones. We wouldn?t consider removing or blocking those, why would we look at blocking these award station spots?
>>
>> In fact, yesterday, I used the spots to work a dozen or so of the WRTC stations. Some of them have big pileups so it was fun breaking them.
>>
>> 73 Keith G6NHU
>>
>>
>>
>>>> On 9 Jan 2023, at 16:42, Jim Reisert AD1C via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>
>>> I guess that finally explains why all the spots tell me to check out
>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>> the WRTC page. I did not realize that the URL was being truncated
>>> along the way.
>>>
>>> --
>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Mon, 9 Jan 2023 17:49:48 +0000
>> From: Dirk Koopman <djk at tobit.co.uk>
>> To: dxspider-support at tobit.co.uk
>> Subject: Re: [Dxspider-support] Ending ham.cm flooding
>> Message-ID: <3d3c2c8a-9990-c950-d539-77377d324692 at tobit.co.uk>
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Sadly, they are coming from an IP address that is connected to many node
>> using callsigns that are not his. The spots look genuine, but are not
>> being sent by the owners of those callsigns.
>>
>> He has some considerable form doing this + more overt mischief,
>> especially in contests. But not for much longer ...
>>
>> 73 de Dirk G1TLH
>>
>>>> On 09/01/2023 17:19, Keith Maton via Dxspider-support wrote:
>>> Perhaps I?m being naive but although there are a lot of spots for these WRTC award stations, they do appear to be genuine. They?re coming from award chasers who all seem to be using the same web site to log their QSOs which then sends out a spot.
>>>
>>> Just because stations are being spotted a lot, why should we remove them?
>>>
>>> I initially looked at these spots with a view to stopping them but the more I thought about it, I decided I didn?t think it was a good idea.
>>>
>>> There are lots of spots posted for dxpeditions, especially busy ones. We wouldn?t consider removing or blocking those, why would we look at blocking these award station spots?
>>>
>>> In fact, yesterday, I used the spots to work a dozen or so of the WRTC stations. Some of them have big pileups so it was fun breaking them.
>>>
>>> 73 Keith G6NHU
>>>
>>>
>>>
>>>>> On 9 Jan 2023, at 16:42, Jim Reisert AD1C via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>>>
>>>> I guess that finally explains why all the spots tell me to check out
>>>> ham.cm/wrtc2, which takes me to the home page of ham.cm, rather than
>>>> the WRTC page. I did not realize that the URL was being truncated
>>>> along the way.
>>>>
>>>> --
>>>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
>>>>
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Mon, 9 Jan 2023 19:39:16 +0100
>> From: "Kin" <ea3cv at cronux.net>
>> To: "'The DXSpider Support list'" <dxspider-support at tobit.co.uk>
>> Subject: Re: [Dxspider-support] DXSpider and Web Clusters
>> Message-ID: <004301d92459$adff0180$09fd0480$@cronux.net>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Lee,
>> DXSpider nodes (not archaic) that have a webcluster associated, have a very
>> easy way to incorporate the user's IP so that it appears on the PC61.
>>
>> Ideally, those nodes would first update to the latest version, and then add
>> the IP. As the WebCluster URE, DXHEAT or DXFun have done.
>>
>> If any sysop needs information to add the user's IP to dxspider, tell me and
>> I'll be happy to help you.
>>
>> Kin EA3CV
>>
>> -----Mensaje original-----
>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Lee
>> Sawkins via Dxspider-support
>> Enviado el: lunes, 9 de enero de 2023 17:43
>> Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
>> CC: Lee Sawkins <ve7cc at shaw.ca>
>> Asunto: [Dxspider-support] DXSpider and Web Clusters
>>
>> Some time ago both DXSpider and CC Cluster node software starting including
>> the IP addresses of spotters along with the DX spots. This was a big step
>> forward in helping to clean up bad spots. The IP addresses helped
>> identified the spotters even when they used bogus call signs. As a minimum,
>> even if the spotter's real call sign could not be determined, at least the
>> spots could be identified and dropped.
>>
>> Recent hundreds if not thousands of spam spots advertising a commercial web
>> site were recently seen in the system. These spots all had identical
>> comments and all came from the same IP address of 217.61.58.23. This can be
>> solved by dropping all PC61 spots from this IP address. Some still get
>> through as they are converted to PC11 spots which do not include the bad
>> address. These can be filtered out by the bad comments.
>>
>> There are several Web Clusters that are running DXSpider software to
>> interface to the DX Cluster system. One of these is F5LEN-5. Recently I
>> have seen bad spots trashing Bolsonaro from PY calls using this node. These
>> spots included IP addresses of 51.68.11.211. These spots could also be
>> filtered by the IP address. Unfortunately it appears this IP address is the
>> IP address where the web cluster. All spots originating at the F5LEN-3 node
>> end up with the same IP address. Since not all web clusters do this I can
>> only assume that it is caused by badly written web cluster software.
>> Perhaps the F5LEN-3 software could be changed to include the correct
>> addresses of spotters so we could drop just the bad spots. Otherwise we
>> will be blocking all spots from this web cluster.
>>
>> Lee VE7CC
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>> ------------------------------
>>
>> End of Dxspider-support Digest, Vol 240, Issue 20
>> *************************************************
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> ------------------------------
>
> End of Dxspider-support Digest, Vol 240, Issue 22
> *************************************************
More information about the Dxspider-support
mailing list