<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I’m in regular conversation with the author of HamClock. He’s aware of this and is very open to suggestions. <div><br></div><div>He’s already made a number of changes over the last few versions following my feedback to reduce the amount of traffic that HamClock generates, a big one last year was switching from regular keep-alive commands every few minutes down to just sending a ping if there’s no activity for ten minutes.<br><div><br></div><div>I have around twenty HamClocks connected to my node with only an FTTC connection (80Mbps down, 20Mbps up) and it’s not swamping my connection at all. I use HamClock myself and find it a very useful tool so I personally don’t have a problem with people connecting to my node using it.</div><div><br></div><div><div>At the moment, when a HamClock is connected to a DX Spider and receives a spot, it sends a show/heading command so it can plot the received spot on the map. If there’s any alternative to this, I’m happy to pass it on to him.</div><div><br></div><div>If anyone has any suggestions as to how he can reduce this but still provide the same functionality, I’m very happy to pass them on and I’m sure he’ll look into it.</div><div><br></div><div>But describing HamClock as sh*t software and being abusive isn’t the way to go here. </div><div><br></div><div>I’m wondering if he can somehow cache the cty file locally on the HamClock and use that as a lookup.</div><div><br></div><div>I will mention to him that this subject has been raised again.</div><div><br></div><div>73 Keith G6NHU</div><div><br></div><div><br><blockquote type="cite"><div>On 14 Jan 2024, at 22:06, John Spigel via Dxspider-support <dxspider-support@tobit.co.uk> wrote:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>
<font face="monospace">My debug file is chock full of sh/headings.
Each results in a lengthy response that is unlikely used. An
alternative should be agreed upon. Let's not condemn the author of
clock. It's a very useful application and does provide spots for
the users. Let's work with him to see what we can do to make it
work within acceptable limits.<br>
<br>
73, John W1AN<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">On 14-Jan-24 19:00, Peter via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite" cite="mid:fcf7b5b4-78cf-4d84-a475-4748d9d7f70f@pi4cc.nl">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi Steve<br>
<br>
Let us know how to take down this s**t piece of software.<br>
The command sh/head is only traceable in the debug file as I know.<br>
<br>
@Dirk<br>
Is there a way to create/make a log file that contains this type
of commands on a month bases? (like log/01.dat)<br>
Then we can create a fail2ban filter for it (and other cmds).<br>
<br>
Peter<br>
PC2A<br>
<br>
<div class="moz-cite-prefix">Op 14-1-2024 om 18:07 schreef John
Spigel via Dxspider-support:<br>
</div>
<blockquote type="cite" cite="mid:d624fc41-1800-4c30-9f91-3fca0bef3ed4@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Steve, I have a couple of ideas I may try to discourage the
abuse. I'll post results if they work.<br>
And another solution may be to encourage the author of hamclock
to start his own node just for hamclock. He could then add all
the features he wants.<br>
73, John W1AN<br>
<br>
<div class="moz-cite-prefix">On 14-Jan-24 16:53, Stephen Carroll
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAHi5uwY4sh_abYBfxdDPghAUfkUY4tcgZ8ETx1teLS5AhUeyyQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>John,</div>
<div dir="auto"><br>
</div>
<div dir="auto">This issue was discussed about a year ago,
search the listserver archives. A few of us were actually
in contact with the software author at that time, but I
don't have his email address anymore. In the end, not much
changed after numerous emails back and forth. Again, good
luck!</div>
<div dir="auto"><br>
</div>
<div dir="auto">73, Steve - AA4U</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div data-smartmail="gmail_signature">Samsung Galaxy S22+ on
Verizon 5G Network</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jan 14, 2024,
10:29 AM John Spigel via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk" moz-do-not-send="true" class="moz-txt-link-freetext">dxspider-support@tobit.co.uk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> Steve, It depends on what data hamclock is seeking.
Why all the show/heading requests by every hamclock user
every second? It makes little sense. Does someone know
the originator of hamclock who may be able to offer a
solution? For dxspider could there be an automatic
rejection of some or all commands by those hiding behind
set/nohere? Before I start the pain of rejecting
multiple ips, I'll wait patiently to see if another
solution is offered. .<br>
<br>
73, John W1AN<br>
<br>
<div>On 14-Jan-24 16:10, Stephen Carroll wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div>There's no getting around the fact that
Hamclock is a bandwidth/resource hog! The software
makes rigorous data queries in order to populate
the map, etc. Without the queries there would be
no data!</div>
<div dir="auto"><br>
</div>
<div dir="auto">I have banned users from utilizing
this software on my node. They are free to go
elsewhere, but my 100mb internet connection gets
bogged down (especially during contests). In the
beginning I had 10 hamclock users, before I
realized what was going on. I've configured my
router to reject their IP addresses, this prevents
them from even reaching the DXSpider computer.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Perhaps some high bandwidth nodes
can handle this constant barrage of data requests,
but mine can't. Good luck!</div>
<div dir="auto"><br>
</div>
<div dir="auto">73, Steve - AA4U</div>
<div><br>
</div>
<div data-smartmail="gmail_signature">Samsung Galaxy
S22+ on Verizon 5G Network</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jan 14,
2024, 9:53 AM John Spigel via Dxspider-support
<<a href="mailto:dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">dxspider-support@tobit.co.uk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The
number of abusive show/heading commands has
exploded in the last few <br>
months, stealing much bandwidth especially on
contest weekends. The <br>
software causing is probably known to many on this
list. The users are <br>
setting themselves as not/here (call). Can someone
offer a solution <br>
other than banning the abusers? The software could
probably use a change <br>
as it seems the purpose is akin to a ping to see
if the node is still <br>
active. Maybe an alternative could be offered. I
think this was <br>
mentioned in the past. Consider not allowing
sh/headings for those who <br>
have set as not/here? Or ?<br>
<br>
73, John W1AN<br>
<br>
<a href="http://dxc.dxusa.net/" rel="noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true">dxc.dxusa.net</a>
7373<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote>
</div>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Dxspider-support@tobit.co.uk" moz-do-not-send="true">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></div></blockquote></div><br></div></div></body></html>