[Dxspider-support] Partnes with connection problems

[Kin]

Hi,

The following pairs of nodes have some error in the configuration that
causes the links not to be established.
Some have not defined the correct node type, some have defined the wrong
callsign, others have not defined the wrong password, etc.
These are not all the ones that fail, only those that I have been able to
detect because they use PC9x, or their partner uses it.
This is generating constant traffic that could be eliminated if the partners
set up the session correctly.
We may think that the link is established correctly by querying commands
like sh/conn, who or link, but to make sure that it is really working, we
should verify that the connection is stable and that sentences like
PC11/PC61 are received from the neighbouring node.

To verify this you can do for example:
cd /spider/local_data/debug/2024/
Change 2024 to the current year.

tail -f 366.dat | grep "<\- I NODE_NEIGHBOUR PC[16]1"
366.dat is the current day year. The 1st of January will be 001.dat.
replace NODE_NEIGHBOUR with the one we want to monitor.

Pairs with problems:

9A0DXC	DB0SUE-7
9M2PJU-1	WB3FFV-2
CS5SEL-5	CQ0PCV-9
CS5SEL-5	CT1EBQ-9
CT2IWW-2	CS5ARTD-2
CU3HY-2	SV5FRI-1
DB0HGW-6	DB0SUE-7
DB0OVN-6	DB0SUE-7
DH1TW-2	K1TTT
DH1TW-2	PY1TSP-1
DJ4PK-2	WA9PIE-2
DL9GTB-1	EA4RCH-5
DO5SSB-2	HB9DRV-9
DO5SSB-2	EA4URE-2
DO5SSB-2	WB3FFV-2
DO5SSB-2	DB0OVN-6
DO5SSB-2	9A0DXC
DO5SSB-2	WA9PIE-2
DO5SSB-2	KB2SYD-5
EA4URE-2	DO5SSB-2
EA4URE-2	JH1RFM-9
EA4URE-3	ON3URE-2
F1FCA-2	KF8I-3
F1FCA-2	KF8MZ-3
F1FCA-2	WI3W-2
F4BWT-3	I8ZSE-1
F6BVP-3	F6KVP-3
F6KVP-3	F6BVP-3
GB7NHR	EA7URG-5
GB7NHR	EA7URG
GB7VAX	KB3CMT-2
HB9DRV-9	WB3FFV-2
HB9DRV-9	DO5SSB-2
HB9DRV-9	DJ4PK-2
HB9VQQ-2	SV2HRT-1
HG8PRC	KC9AOP-1
HG8PRC	9A0DXC
HI8S-8		NL7S
I8ZSE-1	F4BWT-3
IK2XDE-6	IQ1LA-6
IK7IMO-6	TA2NC
IV3SCP-6	PE1ITR-8
IZ0ORT-8	IZ0FKE
IZ0ORT-8	IZ0ORT-6
JA2YYF-9	SV5FRI-1
JA2YYF-9	BG2RVL-9
JA2YYF-9	7N4TWL-7
JG1VGX-8	IW1QLH-6
K1TTT		IW9FRA-6
K1TTT		VE3EY-7
K1TTT		IW5ECF-6
K1TTT		DH1TW-2
K1TTT		PY1NB-4
KF8MZ-3	F1FCA-2
KM3T-5	KM3T-10
M0KGX-3	SM7IUN-1
M0KGX-3	VE3ZIN-2
M0KGX-3	IK8HJC-6
M0KGX-3	SV1IW-9
M0KGX-3	SM6HOC-6
N0VD		OP0P
N6WS-6	PY1NB-4
N6WS-6	F4EYQ-1
N6WS-6	SK3W-6
OK0DXI	SR4DXC
OK2CQR-1	VE3ZIN-2
OK2CQR-1	SR2PUT
ON4KST	EI7SDX
OP0P		EI7MRE
OP0P		EA2RCF-5
OP0P		SK3W-6
OP0P		PE1ITR-8
PA1RBZ	IW1PSC-6
PA4JJ-3	PA4JJ-2
PY2ZEN-6	KB3CMT-2
PY3NZ-8	PY4OG-4
PY5JO-11	DB0ERF-5
PY5JO-11	PY3NZ-8
PY5JO-11	EA4FIT-2
PY5JO-11	LU3DXG
PY5JO-11	SQ3MZM-3
R2AKT-9	R2DGO-1
R2AKT-9	RA3ATX-9
R2AKT-9	RA3ATX-8
RA3ATX-8	R2AKT-9
SP6MI-2	SP6PWS-2
SP6MI-2	SP6PWS
VA3UG		OK2CQR-1
VE3LNZ-1	VE3TOK-1
VE6CIC-1	SV5FRI-1
VE6CIC-1	WB3FFV-2
VE9SC		GB7DXG-1
WA9PIE-2	DO5SSB-2
WC2L		IW5ECF-6
YO2LOJ-2	N2YO-2

If left unrepaired, and maintained for a year, at the end, a single node
could have sent over 8,000,000 (22000*365) sentences to each of its
neighbouring nodes, and they will have done the same to their partners.
Calculate the useless traffic that would circulate through the network if we
don't maintain it.

Happy New Year.

Kin EA3CV

EA3CV-2 dxcluster.cronux.net 7300
https://clustermap.cronux.net/map.html
https://clustermap.cronux.net/route_finder.html