[Dxspider-support] Wrong configurations in the links

[Kin]

Hi all,

Yesterday I was analyzing the Network traffic for a few hours and I found
what appears to be erroneous configurations in the crontabs or in the
configuration of the nodes to establish connections with other neighboring
nodes.
As you can see in the table, all of the ones that appear are reporting that
their neighboring/adjacent node is inaccessible or the session is not
established.
When you analyze the sentences in more detail, you can see the cadence in
the crontabs.
All this traffic stops being significant when we don't look at it, and it
becomes useless and unwanted traffic.
It would be good if we could reduce this list, by making those links work or
eliminating the automatic connections.

Node Pairs             PC92   UP(A)  DOWN(D)
--------------------------------------------
CS5ARTD-2 <--> CT2IWW-2          0  83 ***
CU3HY-2 <--> SV5FRI              0  85 ***
DL9GTB-1 <--> EA4RCH-5           0  43 ***
DL9GTB-1 <--> SM7GVF-6           0  31 ***
EA4URE-3 <--> EA6VQ-1            0  57 ***
EA4URE-3 <--> ON3URE-2           0  76 ***
EI7SDX <--> ON4KST               0  40 ***
F4EYQ-1 <--> N6WS-6              0 121 ***
F6BVP-3 <--> M0KGX-3             0  71 ***
GB7VAX <--> KB3CMT-2             0  85 ***
GB7VAX <--> LA7Q-6               0  38 ***
HB9DRV-9 <--> WB3FFV-2           0 123 ***
HB9VQQ-2 <--> SV2HRT-1           0 412 ***
IK2XDE-6 <--> IQ1LA-6            0  34 ***
IK2XDE-6 <--> IW1PSC-6           0  47 ***
IK5ZUK-6 <--> IQ8DO-6            0 416 ***
IQ1IM-6 <--> K7EK                0  44 ***
IQ1LA-6 <--> PA1RBZ              0  88 ***
IZ0FKE-6 <--> VE7CC              0  31 ***
K0PIR-2 <--> M0KGX-2             0  83 ***
K1TTT <--> KD4WLE-4              0  31 ***
KA2PBT-1 <--> VE2HEW-5           0  16 ***
KM3T-10 <--> KM3T-5              0  44 ***
LA3WAA-6 <--> SV5FRI-1           0  89 ***
M0KGX-3 <--> SM7IUN-1            0  58 ***
N6WS-6 <--> PY1NB-4              0 402 ***
N6WS-6 <--> SK3W-6               0  29 ***
ON0DXK <--> SR4DXC               0  29 ***
OP0P <--> R2DGO-1                0  25 ***
PA2SQ-1 <--> PI1LAP              0 416 ***
PI4CC <--> TA2NC                 0 416 ***
RW3XA-9 <--> US4MFB-15           0  44 ***

Also, I have found two nodes that have SK0MMR and SK1MMR defined as spider
nodes and not RBN, so the rest of the network identifies them as nodes, but
their IP is UNKNOWN.
SK0MMR and SK1MMR are usually used to connect to RBNs. I don't know if these
pseudonodes are defined on purpose as spider or if it is an error. In any
case, I think it is not advisable to publish them beyond the node that
generates the PC92.

IW9EDP-6 <--> SK0MMR             0  42 ***
IW9EDP-6 <--> SK1MMR             0  31 ***
PY2ZEN-6 <--> SK0MMR             0  37 ***
PY2ZEN-6 <--> SK1MMR             0  25 ***

Regards,

Kin EA3CV

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 6510 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240826/48a35a17/attachment.bin>