[Dxspider-support] Dxspider-support Digest, Vol 241, Issue 140
Brian Bowers
g0vax67 at gmail.com
Tue Feb 21 06:54:54 GMT 2023
I think a centralised bad word list is a good idea.
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.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> on behalf of dxspider-support-request at tobit.co.uk <dxspider-support-request at tobit.co.uk>
Sent: Tuesday, February 21, 2023 2:03:02 AM
To: dxspider-support at tobit.co.uk <dxspider-support at tobit.co.uk>
Subject: Dxspider-support Digest, Vol 241, Issue 140
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: Some network data (Dirk Koopman)
2. Re: Some network data (Dirk Koopman)
3. Re: Some network data (Dirk Koopman)
4. Re: Some network data (IZ5FSA)
5. Re: Some network data (Howard Leadmon)
6. Re: Some network data (John Spigel)
----------------------------------------------------------------------
Message: 1
Date: Mon, 20 Feb 2023 23:17:15 +0000
From: Dirk Koopman <djk at tobit.co.uk>
To: dxspider-support at tobit.co.uk
Subject: Re: [Dxspider-support] Some network data
Message-ID: <03ce698c-007a-d07e-8016-41209f750e81 at tobit.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Even older versions will stop set/badnode, plain badword and some regex
based badword traffic.
Newer nodes will layer on the newer stuff, such as badip, regex badwords
etc. The result of this is that only persons that pop just for contests
and also randomise their IP addresses that seem to be a problem. We had
one this weekend. He managed ~20 spots over a fairly short period of
time on two (very different) IP addresses.
Any of node will drop stuff it knows is bad. The problem is that there
is (now) only the central list of bad ip addresses. Reluctant as I am to
say this but, in order to get better overall coverage,? we probably now
need? central? badword, bad node and maybe baddx lists (although I see
very little usage of set/baddx (maybe I should get out less? :-)
distributed from a central point in the same way as the badip stuff.
Thoughts?
Dirk G1TLH
On 20/02/2023 19:53, Mike McCarthy, W1NR via Dxspider-support wrote:
>
>
> On 2/20/2023 2:16 PM, Kin via Dxspider-support wrote:
>
>> I think that the execution of the lock request is not being so
>> traumatic. It is clear who has not participated in any way.
>>
>> I ask you, what do you think the next step should be?
>>
>> Kin EA3CV
>
> Dirk may clarify this but if an outdated node has one link to an
> updated node, any bad spots originating from that old node should get
> dropped by the updated partner's filtering and not propagate any
> further. Correct?
>
> I still say that blindly disconnecting and locking out older nodes is
> an authoritarian sledgehammer approach and really isn't necessary if
> the majority are up to date.
>
> Also, 3 of my partner nodes who were on your block list whom you claim
> could not be contacted were contacted directly by me and were unaware
> of this whole thing.
>
> Let's now just stop and observe how and if what we have is working.
>
> Mike, W1NR
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
------------------------------
Message: 2
Date: Mon, 20 Feb 2023 23:22:12 +0000
From: Dirk Koopman <djk at tobit.co.uk>
To: dxspider-support at tobit.co.uk
Subject: Re: [Dxspider-support] Some network data
Message-ID: <8c2d6b56-9899-b7d3-dfbf-04831b6e1f07 at tobit.co.uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 20/02/2023 22:17, Howard Leadmon via Dxspider-support wrote:
> ?Also as Mike mentioned, for sure we are shooting total innocents on
> this, as not everyone follows everything going on with this list, so
> people just find out the hard way they have been blocked.?? As easy as
> it is to setup a node, I would not be surprised if some of them are
> little Pi's for personal use by the op,? and maybe a few other hams,
> it's that easy to do.
I would add that many active node sysops are not on this list. Which
makes a lot of this work difficult at best.
Dirk G1TLH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/9a9a3f23/attachment-0001.htm>
------------------------------
Message: 3
Date: Mon, 20 Feb 2023 23:25:26 +0000
From: Dirk Koopman <djk at tobit.co.uk>
To: dxspider-support at tobit.co.uk
Subject: Re: [Dxspider-support] Some network data
Message-ID: <519c5e0a-9155-5461-b29a-743358784ef3 at tobit.co.uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
There have been some odd connections and configurations appearing
lately, which I take to mean that there is some configuration checking
that could usefully be done.
For instance KM3T-10 recently had an issue, which I see has now been fixed.
Dirk G1TLH
On 20/02/2023 22:26, Howard Leadmon via Dxspider-support wrote:
> ?Kin, what is this, from your list:
>
> *WB3FFV ?????? -->???? KY9J-2*
>
> WB3FFV-2 -->
> 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
>
> *WB3FVV-2 ???? -->???? W8BS-2*
>
>
> ?I get the long list of other nodes connected to WB3FFV-2, expected
> and is fine.? I am at a loss as to why my non-SSID call appears,
> that;s my normal user call, not a node.?? Does this mean KY9J-2 is
> connecting to me wrong, or has my user call set?
>
> ?I am also guessing that WB3FVV-2 is an oops, close but no cigar as
> they say, so is this a config error on W8BS-2?
>
> ?Not sure where you gathered this info, but was surprised to see the
> bolded parts above..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230220/ad9da911/attachment-0001.htm>
------------------------------
Message: 4
Date: Tue, 21 Feb 2023 00:30:39 +0100
From: IZ5FSA <iz5fsa at gmail.com>
To: Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>
Subject: Re: [Dxspider-support] Some network data
Message-ID: <88e45e45-72b9-46e3-f5d7-8db8d55a3df9 at gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Il 21/02/2023 00:17, Dirk Koopman via Dxspider-support ha scritto:
> Any of node will drop stuff it knows is bad. The problem is that there
> is (now) only the central list of bad ip addresses. Reluctant as I am
> to say this but, in order to get better overall coverage,? we probably
> now need? central? badword, bad node and maybe baddx lists (although I
> see very little usage of set/baddx (maybe I should get out less? :-)
> distributed from a central point in the same way as the badip stuff.
I agree.
Leo IZ5FSA
------------------------------
Message: 5
Date: Mon, 20 Feb 2023 18:51:38 -0500
From: Howard Leadmon <howard at leadmon.net>
To: dxspider-support at tobit.co.uk
Subject: Re: [Dxspider-support] Some network data
Message-ID: <11f9cd8b-b817-5b5a-7398-e73d9dfee94d at leadmon.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
? Hello Dirk,
?I think your in a similar situation, so maybe not even an issue. That
said, if I can ever support any of the efforts with storage, hosting, or
DNS, it's simple to do..
73's..
---
Howard Leadmon - WB3FFV
PBW Communications, LLC
http://www.pbwcomm.com
On 2/20/2023 6:17 PM, Dirk Koopman via Dxspider-support wrote:
> Even older versions will stop set/badnode, plain badword and some
> regex based badword traffic.
>
> Newer nodes will layer on the newer stuff, such as badip, regex
> badwords etc. The result of this is that only persons that pop just
> for contests and also randomise their IP addresses that seem to be a
> problem. We had one this weekend. He managed ~20 spots over a fairly
> short period of time on two (very different) IP addresses.
>
> Any of node will drop stuff it knows is bad. The problem is that there
> is (now) only the central list of bad ip addresses. Reluctant as I am
> to say this but, in order to get better overall coverage,? we probably
> now need? central? badword, bad node and maybe baddx lists (although I
> see very little usage of set/baddx (maybe I should get out less? :-)
> distributed from a central point in the same way as the badip stuff.
>
> Thoughts?
>
> Dirk G1TLH
>
> On 20/02/2023 19:53, Mike McCarthy, W1NR via Dxspider-support wrote:
>>
>>
>> On 2/20/2023 2:16 PM, Kin via Dxspider-support wrote:
>>
>>> I think that the execution of the lock request is not being so
>>> traumatic. It is clear who has not participated in any way.
>>>
>>> I ask you, what do you think the next step should be?
>>>
>>> Kin EA3CV
>>
>> Dirk may clarify this but if an outdated node has one link to an
>> updated node, any bad spots originating from that old node should get
>> dropped by the updated partner's filtering and not propagate any
>> further. Correct?
>>
>> I still say that blindly disconnecting and locking out older nodes is
>> an authoritarian sledgehammer approach and really isn't necessary if
>> the majority are up to date.
>>
>> Also, 3 of my partner nodes who were on your block list whom you
>> claim could not be contacted were contacted directly by me and were
>> unaware of this whole thing.
>>
>> Let's now just stop and observe how and if what we have is working.
>>
>> Mike, W1NR
>>
>> _______________________________________________
>> 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: Tue, 21 Feb 2023 02:02:52 +0000
From: John Spigel <w1an.dxusa at gmail.com>
To: Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>
Subject: Re: [Dxspider-support] Some network data
Message-ID: <fdc5cfde-4c7d-2203-ae45-eee5149aa94e at gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Howard, The connect "file name" does propagate through the system. So a
missing SSID, or wrong call will show up in show/config and the
connection will still be made with a correct telnet address in the file.
My old node call W1AAA stayed in the system isolated and lonely for
years until I figured that a partner hadn't updated the connect "file
name". Check with KY9J and W8BS and see if they can correct their typos.
On 20-Feb-23 23:25, Dirk Koopman via Dxspider-support wrote:
> There have been some odd connections and configurations appearing
> lately, which I take to mean that there is some configuration checking
> that could usefully be done.
>
> For instance KM3T-10 recently had an issue, which I see has now been
> fixed.
>
> Dirk G1TLH
>
> On 20/02/2023 22:26, Howard Leadmon via Dxspider-support wrote:
>> ?Kin, what is this, from your list:
>>
>> *WB3FFV ?????? -->???? KY9J-2*
>>
>> WB3FFV-2 ???? -->
>> 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
>>
>> *WB3FVV-2 ???? -->???? W8BS-2*
>>
>>
>> ?I get the long list of other nodes connected to WB3FFV-2, expected
>> and is fine.? I am at a loss as to why my non-SSID call appears,
>> that;s my normal user call, not a node.?? Does this mean KY9J-2 is
>> connecting to me wrong, or has my user call set?
>>
>> ?I am also guessing that WB3FVV-2 is an oops, close but no cigar as
>> they say, so is this a config error on W8BS-2?
>>
>> ?Not sure where you gathered this info, but was surprised to see the
>> bolded parts above..
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230221/beaa0f29/attachment.htm>
------------------------------
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 241, Issue 140
**************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230221/28c8f9f7/attachment-0001.htm>
More information about the Dxspider-support
mailing list