<div dir="auto"><div>It really depends on how is the DDoS protection algorithm. It could be that after a certain threshold many connection are disconnected.</div><div dir="auto"><br></div><div dir="auto">Would you send to me the output of this Linux command</div><div dir="auto">netstat -an</div><div dir="auto"><br></div><div dir="auto">Andrea</div><div dir="auto"><br></div><div><br></div><div data-smartmail="gmail_signature">/// sent from my mobile device \\\</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il sab 21 set 2024, 13:24 Keith Maton via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk">dxspider-support@tobit.co.uk</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space">No change on the router, this started exactly when I updated the node software on Thursday. <div><br></div><div>As soon as I saw what was happening, I disabled the firewall and the DDOS protection on the router (It’s a Draytek 2865) and I’ve since enabled them again. If the connections were being blocked by the router, I wouldn’t expect to see a connection attempt in the debug log on the Pi.</div><div><br></div><div>73 Keith</div><div><br></div><div><br><div><div><br><blockquote type="cite"><div>On 21 Sep 2024, at 12:10, IZ2LSC <<a href="mailto:iz2lsc.andrea@gmail.com" target="_blank" rel="noreferrer">iz2lsc.andrea@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div>Hi,<br></div><div>Any change on the router that is doing the port forward?</div><div>Maybe there is ddos protection on it that kick in.</div><div> <br></div><div>Are we sure that the disconnect is coming from dxspider and not from the router?</div><div><br></div><div>I think we have to take a tcpdump to look at the tcp flow to understand from where the TCP RST or FIN is coming from.</div><div><br></div><div>If you need help taking the tcpdump we can setup a call with screen sharing and I can guide you.</div><div><br></div><div>73</div><div>Andrea, iz2lsc</div><div><br></div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno sab 21 set 2024 alle ore 13:01 Kin via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">dxspider-support@tobit.co.uk</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I have been trying to help Keith with his problem, and after analysing<br>
everything I can think of, I can't see the reason for the disconnection with<br>
the traces we have.<br>
<br>
This is basically what is happening to him:<br>
<br>
1726911492^(connect) ExtMsg accept 165:192.168.1.208 from<br>
<a href="http://68.117.200.55:58828/" rel="noreferrer noreferrer" target="_blank">68.117.200.55:58828</a><br>
1726911492^(connect) ExtMsg connect 165: login: <br>
1726911492^(connect) connect 165: timeout set to 60<br>
1726911492^(connect) connect 165: AE5DW<br>
1726911492^(state) AE5DW channel func state 0 -> prompt<br>
1726911492^(DXCommand) AE5DW connected from 68.117.200.55 cols 80<br>
1726911492^(progress) CMD: 'unset/beep ' by AE5DW ip: 68.117.200.55 0mS<br>
1726911492^(progress) CMD: 'show/cluster ' by AE5DW ip: 68.117.200.55 0mS<br>
1726911492^(DXCommand) AE5DW disconnected<br>
<br>
But with the rest of the users it is not failing.<br>
<br>
Kin EA3CV<br>
<br>
<br>
-----Mensaje original-----<br>
De: Dxspider-support <<a href="mailto:dxspider-support-bounces@tobit.co.uk" target="_blank" rel="noreferrer">dxspider-support-bounces@tobit.co.uk</a>> En nombre de<br>
Keith Maton via Dxspider-support<br>
Enviado el: sábado, 21 de septiembre de 2024 12:30<br>
Para: The DXSpider Support list <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">dxspider-support@tobit.co.uk</a>><br>
CC: Keith Maton <<a href="mailto:g6nhu@me.com" target="_blank" rel="noreferrer">g6nhu@me.com</a>><br>
Asunto: Re: [Dxspider-support] New mojo version<br>
<br>
This morning I took a fresh Pi, a new SSD and built a new node from scratch.<br>
I copied over the user file and imported it. I also copied the spots<br>
directory so no history would be lost and the filters directory so my users<br>
would still have their filters.<br>
<br>
I also copied my startup file, my connect scripts and my crontab.<br>
<br>
I hashed out pretty much everything in the crontab. I started the node,<br>
disconnected some links from the old one and manually started them on the<br>
new one to confirm I could connect and get data in.<br>
<br>
Then I stopped the old node and changed the port forwarding in my router to<br>
the new one.<br>
<br>
It’s no different. I’m still getting exactly the same thing. Some (but not<br>
all) HamClocks are connecting and then immediately being disconnected before<br>
they can send any commands. I’m 99.9% sure the disconnect is coming from<br>
the dxspider and not the HamClock because HamClock tracks whether the<br>
disconnect is coming from local or remote.<br>
<br>
There’s no pattern to this, it doesn’t seem to be HamClock version specific<br>
as I sent a sample to the developer who checked and saw multiple different<br>
versions.<br>
<br>
The HamClock connects<br>
I see the connection in the debug log and then immediately, after two<br>
commands are forced by the node (unset/beep and show/cluster), the node<br>
disconnects.<br>
This repeats ten times then the HamClock stops connecting for one hour<br>
because it’s reached its hard limit of ten disconnects/hour. It only tracks<br>
remote disconnections towards this limit.<br>
<br>
But the crazy and unexplained thing is that when I reverted back to build<br>
536 by restoring a backup, the same thing is still happening. Nothing has<br>
changed on my network as the connections are still making it to the node.<br>
<br>
I’m really lost here. I feel bad because there are well over 200 people who<br>
won’t have been able to connect since Thursday afternoon. They’ve probably<br>
gone over to other nodes, which is fine but it doesn’t resolve the problem<br>
I’ve got here and what could happen to me could happen to anyone. I’ve<br>
gone out of my way recently to push my node as the best for HamClocks<br>
(because I know a lot of sysops weren’t happy with it) and now it’s utterly<br>
rubbish for them.<br>
<br>
I owe it to my users to try and resolve this but at the moment, I feel as<br>
though after eight years of running a node (which I appreciate is a lot less<br>
than many), I just want to switch the damn thing off. I’m not going to,<br>
because I don’t like things to beat me but it’s very, very frustrating.<br>
<br>
73 Keith<br>
<br>
<br>
<br>
<br>
> On 21 Sep 2024, at 04:25, Rene Olsen via Dxspider-support<br>
<<a href="mailto:dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">dxspider-support@tobit.co.uk</a>> wrote:<br>
> <br>
> Hi.<br>
> <br>
> Still waiting for a replay as to why G6NHU-2 lost like 75% of his <br>
> users before I do anything with the new version.<br>
> <br>
> So, will at least wait until next week. Like W1NR, I never update just <br>
> before or during a weekend.<br>
> <br>
> Vy 73 de René / OZ1LQH<br>
> <br>
> On 20 Sep 2024 at 17:44, Kin via Dxspider-support wrote:<br>
> <br>
>> Hi,<br>
>> <br>
>> The new build is working very well for me.<br>
>> Only 60 out of 318 dxspider have been updated.<br>
>> Cheer up, it's been in testing for a while and it's stable.<br>
>> <br>
>> 73 de Kin EA3CV<br>
>> <br>
>> <br>
>> De: Dxspider-support <<a href="mailto:dxspider-support-bounces@tobit.co.uk" target="_blank" rel="noreferrer">dxspider-support-bounces@tobit.co.uk</a>> En nombre <br>
>> de Dirk Koopman via Dxspider-support Enviado el: jueves, 19 de <br>
>> septiembre de 2024 15:24<br>
>> Para: Dxspider-Support <<a href="mailto:dxspider-support@dxcluster.org" target="_blank" rel="noreferrer">dxspider-support@dxcluster.org</a>><br>
>> CC: Dirk Koopman <<a href="mailto:djk@tobit.co.uk" target="_blank" rel="noreferrer">djk@tobit.co.uk</a>><br>
>> Asunto: [Dxspider-support] New mojo version<br>
>> <br>
>> There is a new mojo version which has been under test by a few brave<br>
sysops and they have determined that it is stable. Please look at the<br>
Changes file for the list of issues dealt with.<br>
>> <br>
>> One of the issues that has become apparent is the random lock status<br>
(historically) granted to new nodes that appear on the network. For some<br>
reason they defaulting to "unlocked". I don't understand why this has<br>
suddenly become a problem AGAIN, but it does seem to affect longer running<br>
nodes more than newer ones. <br>
>> <br>
>> This release is an attempt to fix this. It will lock all nodes that are<br>
not specifically unlocked via explicit unset/lock or set/spider type<br>
commands. Unfortunately, previous attempts to deal with this may have got<br>
this all confused and it *MAY* (and I stress this) mean that a (very) few of<br>
your older node partners *MIGHT* get locked out. If this happens then simply<br>
unset/lock or set/spider any of these nodes manually.<br>
>> <br>
>> There is new spot deduping code which seems to reduce the number of<br>
dupes, but since I have not been able to reproduce this further than making<br>
sure that nodes that issue multiple dupe spots with the same sequence number<br>
don't cause dupes.<br>
>> <br>
>> 73 Dirk G1TLH<br>
>> <br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> <a href="mailto:Dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">Dxspider-support@tobit.co.uk</a><br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote></div>
</div></blockquote></div><br></div></div></div>_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank" rel="noreferrer">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote></div>