[Dxspider-support] For all sysops
Kin
ea3cv at cronux.net
Fri Feb 17 15:42:44 GMT 2023
Hi Stephen,
You are right, it is always best to DISCONNECT and then LOCK. Sometimes it works the other way round, I can testify to that.
On my first attempt I have managed to get the node count to almost 50% of nodes on the Mojo branch. On the second attempt the goal was to collect contact information from the sysops and inform them of the need to keep their node up to date. In the last stage, all nodes that are not interested in participating in the upgrading of the other nodes should be isolated.
I have a list of sysops that have assured me that they will upgrade, and others that are considering it. In a reasonable time, I will publish those that simply have not done anything.
I know there are sysops that are having difficulties, but they have asked for help and are doing their best to upgrade, which is to be welcomed.
I have also come across nodes that had a *life of their own*, no one was managing them and when I managed to reach someone related to the node, they shut it down. These should disappear because without active administration it makes no sense to have a node that interacts with the rest and can compromise the overall state of the network.
As you can see from the list, I've only put up spider nodes, but that's just the beginning. I hope that other sysops in other clusters will do something similar to what we are doing here. If in the end we don't all go in the same direction, decisions will have to be made.
I don't see a problem with the number of nodes, but I do see a problem with the quality of the nodes.
As for what you say about experimentation, I agree with you that we can't do certain tests that could affect the rest. There are mechanisms for experimenting locally.
The sysops must be aware of the great effort Dirk and others are making to secure the network and make it more reliable. But developers are not God and need all of us to make an effective improvement.
And an important step to take is to migrate from the current Master branch to the Mojo branch, regardless of the number of users that the node involved usually has.
Sorry for my bad English, I hope I was able to get the message across.
73 de Kin EA3CV
De: Stephen Carroll <aa4u.steve at gmail.com>
Enviado el: viernes, 17 de febrero de 2023 15:25
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] For all sysops
Kin,
In my experience, a partner node or user needs to be DISCONNECTED before you can issue a LOCKOUT.
In the case of a node that hasn't, won't or promised to upgrade in the future --- that node could be put in ISOLATED status, right? The objective should be for them to upgrade, not be cutoff from getting spots, etc. I have 2 older nodes (AK1A, AR Cluster) that are isolated from the main network. The way I understand it, any spots they originate get filtered through my up-to-date mojo cluster node. In fact, do those spots even get forwarded to the main network or just stay within the isolated network?
My opinion, I'm all for weeding out the network of outdated node software or nodes with no active sysop. I've held my tongue on this topic for many years, but the bottom line is there are TOO MANY cluster nodes. Back in the day, it was necessary because of the RF component of each of these area networks. But, very few nodes even have any radio/tnc users anymore. The internet makes ANY node accessible from anywhere now. As an example, there are almost as many nodes listed in Italy as the entire United States --- that seems rather excessive to me. Do we need a network architect? I normally average between 30-40 connected users, but would QRT my node after 20+ years if it meant improving the network.
Aside from the "appliance operators" that abound, ham radio is still an experimenters hobby --- whether that's equipment, antennas or software related. However, my opinion is that the cluster network isn't a place where you want the casual experimenter. Today, we're seeing the outcome of having folks setup a node and in some cases then forget about it --- some of those folks may likely not even be around anymore.
The current actions are a good first step to get every node updated and utilizing the advancements that Dirk and others have been working on to improve the overall network. Thank you.
73, Steve - AA4U
On Fri, Feb 17, 2023, 4:57 AM Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> > wrote:
Hi all,
I think it is time to get involved and play as a team.
After having tried to contact all the spider nodes by email, the following list (except for error, sri) have not replied or have not been located. I therefore ask you to block them.
It may seem very drastic, but we need the involvement of most of the sysops if we want to solve the problems we have.
The blocking should be done so that we can inform those sysops of the changes that have occurred and the need to update their nodes. They can then be unblocked.
For those of you who think this doesn't affect you because you're on your own, I think you're making a big mistake, and you'll realise it when you find yourself excluded from the *team*. This is a request for help to get a necessary change for our Community.
This list is not just for us to ask for help and advice, it is for us to answer those requests for help. There are sysops who only show up here when they have problems, and when you ask for their help they don't even answer you, this behaviour is not part of the ideals of our hobby. We count on you?
If you can, update your details at: <https://www.dxcluster.info/telnet/submit.php%20> https://www.dxcluster.info/telnet/submit.php which will appear at <https://www.dxcluster.info/telnet/index.php> https://www.dxcluster.info/telnet/index.php
Execute command
set/lockout <node>
disc <node>
and verify with:
sh/lockout <node>
Unlockout is done like this:
unset/lockout <node>
And the list of those affected:
Column1 Column2 Column3
9M2PJU-1 5455 196
A61BK-1 5455 198
AB2VY-12 5455 200
AB2VY-2 5455 203
AB2VY-3 5455 215
AB2VY-6 5455 199
AB2VY-7 5455 210
AB2VY-9 5455 249
AI3I-15 5455 203
CS5ARLC-1 5455 197
CT1EBQ-9 5455 204
DB0HGW-6 5455 216
DB0IUZ-6 5455 249
DB0OVN-6 5455 249
DB0PRA-9 5455 115
DB0RBS-11 5455 249
DB0TUD-6 5455 100
DB0UHI-9 5455 166
DD5XX-10 5455 196
DG2KBC-1 5455 82
DK7ET-4 5455 248
DK7ET-5 5455
DL1FLW-1 5455 249
DQ8Z 5455 204
EA2RKS-2 5455 249
EA5URM-5 5455 216
EA7URG 5455
EA7URG-5 5455 196
ED3ZAK-5 5455 249
EW8AX-1 5455 115
F4ERG-3 5455 199
F4GVE-2 5455 175
F4IAA-3 5455 249
F5MZN-3 5455 33
F6KVP-3 5455 141
F8KHI-3 5455 198
G7VJR-5 5455 115
GB7BEX-9 5455 204
GB7DXX 5455 115
GB7IPF 5455 198
GB7KUX-4 5455 249
GB7NHR 5455 166
HA5KDR-3 5455 249
HA6DX 5455 32
HB9IAC-8 5455 115
HG6DXC 5455
I0INU-6 5455 216
I0OJJ-6 5455 250
IK2DUW-6 5455 166
IK4PKL-6 5455 115
IQ1GP-6 5455 249
IQ1LA-6 5455 196
IQ5KG-6 5455 52
IQ8PQ-6 5455 166
IQ8RB-6 5455 166
IQ8XF 5455 249
IR2UGI-5 5455 250
IR2UGI-6 5455 249
IR4FOC-6 5455 216
IR4U-6 5455 216
IT9FTP-6 5455 236
IT9OBK-6 5455 200
IV3BVK-5 5455 216
IW1QLH-6 5455 163
IW2EVH-6 5455 171
IW8PGT-9 5455 115
IW9FDD-6 5455 82
IW9HHF-8 5455 216
IZ0AWG-6 5455 115
IZ0ORT-6 5455 216
IZ5IIN-6 5455 190
IZ5ILU-6 5455 198
IZ6RND-6 5455
IZ8DMZ-6 5455 171
JH1RFM-9 5455 216
K0PIR-2 5455 181
K2LS 5455 82
K4JW 5455 65
K4KYD 5455 249
K4KYD-2 5455 249
K8QIK-3 5455 80
KB2FAF-12 5455 249
KB8UVN-2 5455 73
KC5PQX-9 5455 249
KC9AOP-1 5455 229
KG4OOL-2 5455 249
KY9J-2 5455 216
LZ0DXC 5455 249
M0KGX-3 5455 217
MX0ONL 5455 115
N4DW-9 5455 166
N8NM 5455 249
N9KT-2 5455 229
NA7KR-3 5455 250
NL7S 5455 250
NP3N 5455 203
NR0Q-2 5455 217
NR1X-3 5455 166
OH1RCF 5455 250
OK0DXI 5455 52
OK2CQR-1 5455 250
ON0LLV-5 5455 249
ON3URE-2 5455 216
ON4KST-2 5455 216
PD0SIM-2 5455
PY1TSP-1 5455 197
PY2ZEN-6 5455 250
PY4OG-2 5455 229
SK6AW-2 5455 166
SM4ONW-14 5455 218
SM6EAT-6 5455 249
SM6HOC-14 5455 218
SM6HOC-2 5455 218
SM6HOC-6 5455 218
SM6YOU-2 5455 82
SM6YOU-4 5455 166
SM6YOU-7 5455 82
SR2PUT 5455 197
SR4DXC 5455 198
SR9DDF-12 5455 200
SV2HRT-1 5455 115
SV5BYR-7 5455 217
UA4CC 5455 115
VA3MW-7 5455 249
VE1CFB 5455 38
VE2PKT-9 5455 166
VE3MIS-2 5455 210
VE3XPG-3 5455
VE6DXC 5455 100
VK3HRA-2 5455 185
W1DX-2 5455 82
W1NR 5455 250
W1NR-9 5455 250
W6RFU 5455 216
W6RGG-2 5455 89
W9AEK 5455 158
WT3Q 5455 136
WW1R-9 5455 82
YO2LOJ-2 5455
73 de Kin EA3CV
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto: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/20230217/53fe2c07/attachment-0001.htm>
More information about the Dxspider-support
mailing list