<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div>
<div>
<div dir="ltr">
<div dir="ltr">I think a centralised bad word list is a good idea.</div>
<div dir="ltr">I would however, suggest that the ability to add to the list is left in, as localised words from different regions can be added as and when.</div>
</div>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
Sent from <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of dxspider-support-request@tobit.co.uk <dxspider-support-request@tobit.co.uk><br>
<b>Sent:</b> Tuesday, February 21, 2023 2:03:02 AM<br>
<b>To:</b> dxspider-support@tobit.co.uk <dxspider-support@tobit.co.uk><br>
<b>Subject:</b> Dxspider-support Digest, Vol 241, Issue 140</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send Dxspider-support mailing list submissions to<br>
dxspider-support@tobit.co.uk<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
or, via email, send a message with subject or body 'help' to<br>
dxspider-support-request@tobit.co.uk<br>
<br>
You can reach the person managing the list at<br>
dxspider-support-owner@tobit.co.uk<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Dxspider-support digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Some network data (Dirk Koopman)<br>
2. Re: Some network data (Dirk Koopman)<br>
3. Re: Some network data (Dirk Koopman)<br>
4. Re: Some network data (IZ5FSA)<br>
5. Re: Some network data (Howard Leadmon)<br>
6. Re: Some network data (John Spigel)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 20 Feb 2023 23:17:15 +0000<br>
From: Dirk Koopman <djk@tobit.co.uk><br>
To: dxspider-support@tobit.co.uk<br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <03ce698c-007a-d07e-8016-41209f750e81@tobit.co.uk><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Even older versions will stop set/badnode, plain badword and some regex <br>
based badword traffic.<br>
<br>
Newer nodes will layer on the newer stuff, such as badip, regex badwords <br>
etc. The result of this is that only persons that pop just for contests <br>
and also randomise their IP addresses that seem to be a problem. We had <br>
one this weekend. He managed ~20 spots over a fairly short period of <br>
time on two (very different) IP addresses.<br>
<br>
Any of node will drop stuff it knows is bad. The problem is that there <br>
is (now) only the central list of bad ip addresses. Reluctant as I am to <br>
say this but, in order to get better overall coverage,? we probably now <br>
need? central? badword, bad node and maybe baddx lists (although I see <br>
very little usage of set/baddx (maybe I should get out less? :-) <br>
distributed from a central point in the same way as the badip stuff.<br>
<br>
Thoughts?<br>
<br>
Dirk G1TLH<br>
<br>
On 20/02/2023 19:53, Mike McCarthy, W1NR via Dxspider-support wrote:<br>
><br>
><br>
> On 2/20/2023 2:16 PM, Kin via Dxspider-support wrote:<br>
><br>
>> I think that the execution of the lock request is not being so <br>
>> traumatic. It is clear who has not participated in any way.<br>
>><br>
>> I ask you, what do you think the next step should be?<br>
>><br>
>> Kin EA3CV<br>
><br>
> Dirk may clarify this but if an outdated node has one link to an <br>
> updated node, any bad spots originating from that old node should get <br>
> dropped by the updated partner's filtering and not propagate any <br>
> further. Correct?<br>
><br>
> I still say that blindly disconnecting and locking out older nodes is <br>
> an authoritarian sledgehammer approach and really isn't necessary if <br>
> the majority are up to date.<br>
><br>
> Also, 3 of my partner nodes who were on your block list whom you claim <br>
> could not be contacted were contacted directly by me and were unaware <br>
> of this whole thing.<br>
><br>
> Let's now just stop and observe how and if what we have is working.<br>
><br>
> Mike, W1NR<br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 20 Feb 2023 23:22:12 +0000<br>
From: Dirk Koopman <djk@tobit.co.uk><br>
To: dxspider-support@tobit.co.uk<br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <8c2d6b56-9899-b7d3-dfbf-04831b6e1f07@tobit.co.uk><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
On 20/02/2023 22:17, Howard Leadmon via Dxspider-support wrote:<br>
> ?Also as Mike mentioned, for sure we are shooting total innocents on <br>
> this, as not everyone follows everything going on with this list, so <br>
> people just find out the hard way they have been blocked.?? As easy as <br>
> it is to setup a node, I would not be surprised if some of them are <br>
> little Pi's for personal use by the op,? and maybe a few other hams, <br>
> it's that easy to do.<br>
<br>
I would add that many active node sysops are not on this list. Which <br>
makes a lot of this work difficult at best.<br>
<br>
Dirk G1TLH<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/9a9a3f23/attachment-0001.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/9a9a3f23/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 20 Feb 2023 23:25:26 +0000<br>
From: Dirk Koopman <djk@tobit.co.uk><br>
To: dxspider-support@tobit.co.uk<br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <519c5e0a-9155-5461-b29a-743358784ef3@tobit.co.uk><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
There have been some odd connections and configurations appearing <br>
lately, which I take to mean that there is some configuration checking <br>
that could usefully be done.<br>
<br>
For instance KM3T-10 recently had an issue, which I see has now been fixed.<br>
<br>
Dirk G1TLH<br>
<br>
On 20/02/2023 22:26, Howard Leadmon via Dxspider-support wrote:<br>
> ?Kin, what is this, from your list:<br>
><br>
> *WB3FFV ?????? -->???? KY9J-2*<br>
><br>
> WB3FFV-2 --> <br>
> 9M2PJU-1,AB2VY-9,AI3I-15,CS5ARTD-2,CU3HY-2,DB0SUE-7,DL8FCL-7,EA3CV-2,EA4FIT-2,EA4RCH-5,F4GVE-2,F5UGQ-2,G3LRS-2,G6NHU-2,GB7KUX-4,GB7UJS,GB7VAX,HB9ON-9,IK5PWJ-6,IK7IMO-6,IQ8DO-6,IW0HLG-3,IW5ECF-6,IZ0UIN-6,K0PIR-2,K2LS,K4ZR,KB2FAF-12,KB2S-2,KB3CMT-2,KB8PMY-3,KC9GWK-2,N2WLS-5,N7OD,N9JR-2,PA0ESH-3,PE1ITR-8,PY2ZEN-6,PY4OG-4,R5ACQ-1,S50DXS,SK3W-6,SM6HOC-6,SR9DDF-12,VA3MW-7,VE3TOK-1,W1DX,W1WRA-2,W5CMM-1,WR3D,WT3Q,ZL2AQY-10,ZL2ARN-10<br>
><br>
> *WB3FVV-2 ???? -->???? W8BS-2*<br>
><br>
><br>
> ?I get the long list of other nodes connected to WB3FFV-2, expected <br>
> and is fine.? I am at a loss as to why my non-SSID call appears, <br>
> that;s my normal user call, not a node.?? Does this mean KY9J-2 is <br>
> connecting to me wrong, or has my user call set?<br>
><br>
> ?I am also guessing that WB3FVV-2 is an oops, close but no cigar as <br>
> they say, so is this a config error on W8BS-2?<br>
><br>
> ?Not sure where you gathered this info, but was surprised to see the <br>
> bolded parts above..<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/ad9da911/attachment-0001.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/ad9da911/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 21 Feb 2023 00:30:39 +0100<br>
From: IZ5FSA <iz5fsa@gmail.com><br>
To: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <88e45e45-72b9-46e3-f5d7-8db8d55a3df9@gmail.com><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Il 21/02/2023 00:17, Dirk Koopman via Dxspider-support ha scritto:<br>
> Any of node will drop stuff it knows is bad. The problem is that there <br>
> is (now) only the central list of bad ip addresses. Reluctant as I am <br>
> to say this but, in order to get better overall coverage,? we probably <br>
> now need? central? badword, bad node and maybe baddx lists (although I <br>
> see very little usage of set/baddx (maybe I should get out less? :-) <br>
> distributed from a central point in the same way as the badip stuff.<br>
<br>
I agree.<br>
<br>
Leo IZ5FSA<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 20 Feb 2023 18:51:38 -0500<br>
From: Howard Leadmon <howard@leadmon.net><br>
To: dxspider-support@tobit.co.uk<br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <11f9cd8b-b817-5b5a-7398-e73d9dfee94d@leadmon.net><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
? Hello Dirk,<br>
<br>
?I think your in a similar situation, so maybe not even an issue. That <br>
said, if I can ever support any of the efforts with storage, hosting, or <br>
DNS, it's simple to do..<br>
<br>
<br>
73's..<br>
<br>
---<br>
Howard Leadmon - WB3FFV<br>
PBW Communications, LLC<br>
<a href="http://www.pbwcomm.com">http://www.pbwcomm.com</a><br>
<br>
On 2/20/2023 6:17 PM, Dirk Koopman via Dxspider-support wrote:<br>
> Even older versions will stop set/badnode, plain badword and some <br>
> regex based badword traffic.<br>
><br>
> Newer nodes will layer on the newer stuff, such as badip, regex <br>
> badwords etc. The result of this is that only persons that pop just <br>
> for contests and also randomise their IP addresses that seem to be a <br>
> problem. We had one this weekend. He managed ~20 spots over a fairly <br>
> short period of time on two (very different) IP addresses.<br>
><br>
> Any of node will drop stuff it knows is bad. The problem is that there <br>
> is (now) only the central list of bad ip addresses. Reluctant as I am <br>
> to say this but, in order to get better overall coverage,? we probably <br>
> now need? central? badword, bad node and maybe baddx lists (although I <br>
> see very little usage of set/baddx (maybe I should get out less? :-) <br>
> distributed from a central point in the same way as the badip stuff.<br>
><br>
> Thoughts?<br>
><br>
> Dirk G1TLH<br>
><br>
> On 20/02/2023 19:53, Mike McCarthy, W1NR via Dxspider-support wrote:<br>
>><br>
>><br>
>> On 2/20/2023 2:16 PM, Kin via Dxspider-support wrote:<br>
>><br>
>>> I think that the execution of the lock request is not being so <br>
>>> traumatic. It is clear who has not participated in any way.<br>
>>><br>
>>> I ask you, what do you think the next step should be?<br>
>>><br>
>>> Kin EA3CV<br>
>><br>
>> Dirk may clarify this but if an outdated node has one link to an <br>
>> updated node, any bad spots originating from that old node should get <br>
>> dropped by the updated partner's filtering and not propagate any <br>
>> further. Correct?<br>
>><br>
>> I still say that blindly disconnecting and locking out older nodes is <br>
>> an authoritarian sledgehammer approach and really isn't necessary if <br>
>> the majority are up to date.<br>
>><br>
>> Also, 3 of my partner nodes who were on your block list whom you <br>
>> claim could not be contacted were contacted directly by me and were <br>
>> unaware of this whole thing.<br>
>><br>
>> Let's now just stop and observe how and if what we have is working.<br>
>><br>
>> Mike, W1NR<br>
>><br>
>> _______________________________________________<br>
>> Dxspider-support mailing list<br>
>> Dxspider-support@tobit.co.uk<br>
>> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
><br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 21 Feb 2023 02:02:52 +0000<br>
From: John Spigel <w1an.dxusa@gmail.com><br>
To: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] Some network data<br>
Message-ID: <fdc5cfde-4c7d-2203-ae45-eee5149aa94e@gmail.com><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Howard, The connect "file name" does propagate through the system. So a <br>
missing SSID, or wrong call will show up in show/config and the <br>
connection will still be made with a correct telnet address in the file. <br>
My old node call W1AAA stayed in the system isolated and lonely for <br>
years until I figured that a partner hadn't updated the connect "file <br>
name". Check with KY9J and W8BS and see if they can correct their typos.<br>
<br>
On 20-Feb-23 23:25, Dirk Koopman via Dxspider-support wrote:<br>
> There have been some odd connections and configurations appearing <br>
> lately, which I take to mean that there is some configuration checking <br>
> that could usefully be done.<br>
><br>
> For instance KM3T-10 recently had an issue, which I see has now been <br>
> fixed.<br>
><br>
> Dirk G1TLH<br>
><br>
> On 20/02/2023 22:26, Howard Leadmon via Dxspider-support wrote:<br>
>> ?Kin, what is this, from your list:<br>
>><br>
>> *WB3FFV ?????? -->???? KY9J-2*<br>
>><br>
>> WB3FFV-2 ???? --> <br>
>> 9M2PJU-1,AB2VY-9,AI3I-15,CS5ARTD-2,CU3HY-2,DB0SUE-7,DL8FCL-7,EA3CV-2,EA4FIT-2,EA4RCH-5,F4GVE-2,F5UGQ-2,G3LRS-2,G6NHU-2,GB7KUX-4,GB7UJS,GB7VAX,HB9ON-9,IK5PWJ-6,IK7IMO-6,IQ8DO-6,IW0HLG-3,IW5ECF-6,IZ0UIN-6,K0PIR-2,K2LS,K4ZR,KB2FAF-12,KB2S-2,KB3CMT-2,KB8PMY-3,KC9GWK-2,N2WLS-5,N7OD,N9JR-2,PA0ESH-3,PE1ITR-8,PY2ZEN-6,PY4OG-4,R5ACQ-1,S50DXS,SK3W-6,SM6HOC-6,SR9DDF-12,VA3MW-7,VE3TOK-1,W1DX,W1WRA-2,W5CMM-1,WR3D,WT3Q,ZL2AQY-10,ZL2ARN-10<br>
>><br>
>> *WB3FVV-2 ???? -->???? W8BS-2*<br>
>><br>
>><br>
>> ?I get the long list of other nodes connected to WB3FFV-2, expected <br>
>> and is fine.? I am at a loss as to why my non-SSID call appears, <br>
>> that;s my normal user call, not a node.?? Does this mean KY9J-2 is <br>
>> connecting to me wrong, or has my user call set?<br>
>><br>
>> ?I am also guessing that WB3FVV-2 is an oops, close but no cigar as <br>
>> they say, so is this a config error on W8BS-2?<br>
>><br>
>> ?Not sure where you gathered this info, but was surprised to see the <br>
>> bolded parts above..<br>
><br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230221/beaa0f29/attachment.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230221/beaa0f29/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Dxspider-support Digest, Vol 241, Issue 140<br>
**************************************************<br>
</div>
</span></font></div>
</body>
</html>