[Dxspider-support] Wrong configurations in the links
Kin
ea3cv at cronux.net
Mon Aug 26 17:29:26 BST 2024
Peter, one that seems to be trying to connect to you is TA2NC.
Captured a few seconds ago:
1724681942^(chan) <- I EA3CV-3 PC92^TA2NC^51542^D^^5PI4CC^H95^
1724682002^(chan) <- I EA3CV-3 PC92^TA2NC^51602^D^^5PI4CC^H95^
1724682064^(chan) <- I EA3CV-3 PC92^TA2NC^51664^D^^5PI4CC^H95^
1724682122^(chan) <- I EA3CV-3 PC92^TA2NC^51722^D^^5PI4CC^H95^
1724682186^(chan) <- I EA3CV-3 PC92^TA2NC^51786^D^^5PI4CC^H95^
1724682242^(chan) <- I EA3CV-3 PC92^TA2NC^51842^D^^5PI4CC^H95^
1724682305^(chan) <- I EA3CV-3 PC92^TA2NC^51904^D^^5PI4CC^H95^
1724682366^(chan) <- I EA3CV-3 PC92^TA2NC^51966^D^^5PI4CC^H95^
1724682427^(chan) <- I EA3CV-3 PC92^TA2NC^52027^D^^5PI4CC^H95^
1724682482^(chan) <- I EA3CV-3 PC92^TA2NC^52082^D^^5PI4CC^H95^
1724682543^(chan) <- I EA3CV-3 PC92^TA2NC^52143^D^^5PI4CC^H95^
1724689081^(chan) <- I EA3CV-3 PC92^TA2NC^58681^D^^5PI4CC^H95^
1724689142^(chan) <- I EA3CV-3 PC92^TA2NC^58742^D^^5PI4CC^H95^
1724689202^(chan) <- I EA3CV-3 PC92^TA2NC^58802^D^^5PI4CC^H95^
1724689262^(chan) <- I EA3CV-3 PC92^TA2NC^58862^D^^5PI4CC^H95^
1724689323^(chan) <- I EA3CV-3 PC92^TA2NC^58923^D^^5PI4CC^H95^
1724689381^(chan) <- I EA3CV-3 PC92^TA2NC^58981^D^^5PI4CC^H95^
The list I have posted only shows the pairs involved, not necessarily the
two nodes trying to initiate the link.
Even if you do not define it as a node, if it tries to make a connection
with PI4CC, the result seems to be that.
Here the one who should look at its configuration is TA2NC.
Kin
-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
Peter via Dxspider-support
Enviado el: lunes, 26 de agosto de 2024 16:39
Para: dxspider-support at tobit.co.uk
CC: Peter <pc2a at pi4cc.nl>
Asunto: Re: [Dxspider-support] Wrong configurations in the links
Hi Kin
As sysop of PI4CC I can comment that PI4CC have only in coming connections.
There are no crontab running to make a connection to any dx-node. I am quit
passive :-)
The node TA2NC, is as far as in known, not set as spider node @ PI4CC
So I do not known were to look to solve this case.
Peter
PC2A
Op 26-8-2024 om 15:46 schreef Kin via Dxspider-support:
> 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
>
>
> _______________________________________________
> 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
More information about the Dxspider-support
mailing list