[Dxspider-support] Partnes with connection problems
Rudy Bakalov
r_bakalov at yahoo.com
Mon Jan 6 21:10:48 GMT 2025
He is at 20.117.16.151 port 7300. I have no problem connecting.
Rudy N2WQ
On Monday, January 6, 2025 at 03:27:36 PM EST, Björn Ekelund via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
Thanks Kin,
I removed the crontab item for the seemingly unreachable M0KGX-3.
Björn SM7IUN
On Mon, Jan 6, 2025 at 8:59 PM Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
Hi Jean,
As I cannot determine from here which of the two nodes has a wrong configuration, I suggest you check your connection file with KY9J-2.
The first thing is to check that the connection file is called KY9J-2 and will be in this path:
/spider/connect/KY9J-2 (it can be in upper or lower case).
If you look at its contents, there is a line that should read ‘login:’. The callsign that should appear there is the one of your node, not the one of the sysop (it is a common mistake).
If everything is correct, you just need to make sure the node definition of your partner is correct:
set/spider KY9J-2
If the file name was not KY9J-2, you must make sure that in your crontab, it appears correctly.
It is likely that the problem is in KY9J-2. You may have set it to VE2PKT instead of VE2PKT-9. If so, you will have to do the same as I have told you.
In case it helps, you can consult the following pdf I made to clarify how to define a connection:
https://github.com/EA3CV/dxspider_info/blob/f2ed6e3bc467cd8abeadd691e18f8dcbe7fc212b/Docs/HOW%20TO%20SET%20UP%20A%20PARTNER%20NODE%20IN%20DXSPIDER.pdf
HNY de Kin EA3CV
-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Jean VE2PKT via Dxspider-support
Enviado el: lunes, 6 de enero de 2025 20:43
Para: dxspider-support at tobit.co.uk
CC: Jean VE2PKT <ve2pkt at gmail.com>
Asunto: Re: [Dxspider-support] Partnes with connection problems
Hi Kin,
What I am supposed to do?
KY9J-2 VE2PKT 105 53 158
VE2PKT-9 KY9J-2 53 53 106
73 de Jean
VA2OM / VE2PKT
On 2025-01-06 13:07, Kin via Dxspider-support wrote:
> Hi,
>
> Seeing that there is almost no involvement of the sysops in solving
> the sending of useless packets in order to keep the network as good as
> possible, here is the last list taken a few minutes ago. I hope it
> helps you at least to see how the network is doing.
>
>
> Pairs of nodes with erroneous callsign:
>
> Node-1 Node-2 Conn Disc ALL
> ----------------------------------------
> 9M2PJU-2 WB3FFV-2 53 53 106
> WB3FFV-2 9M2PJU-1 106 54 160
>
> CU3HY-2 SV5FRI 108 53 161
> SV5FRI-1 CU3HY-2 54 53 107
>
> G1FEF-2 G6NHU 32 15 47
> G6NHU-2 G1FEF-2 17 23 40
>
> KY9J-2 VE2PKT 105 53 158
> VE2PKT-9 KY9J-2 53 53 106
>
> KY9J-2 VK5GR 106 53 159
> VK5GR-2 KY9J-2 53 109 162
>
> PY3NZ-8 PY4OG-2 108 54 162
> PY4OG-4 PY3NZ-8 54 54 108
>
> SV5FRI-1 VE6CIC-1 54 54 108
> VE6CIC-1 SV5FRI 52 0 52
>
>
> Pairs with non-existent node. Guess:
>
> DJ4PK-2 HB9DRV-9 134 67 201
> WA9PIE-2 DJ4PK-2 67 67 134
>
> Rest with connection problems:
>
> Node-1 Node-2 Conn Disc ALL
> ----------------------------------------
> 7N4TWL-7 JA2YYF-9 54 53 107
> 9A0DXC HG8PRC 18 9 27
> BG2RVL-9 JA2YYF-9 53 54 107
> CS5SEL-5 CQ0PCV-9 54 53 107
> CT1EBQ-9 CS5SEL-5 54 53 107
> DB0ALG-9 DB0PER 11 71 82
> DB0HGW-6 DB0SUE-7 120 60 180 DB0SUE-7 does not exist
> DH1TW-2 NC7J 67 67 134
> DO5SSB-2 DB0HGW-6 62 60 122
> EA2RCF-5 OP0P 51 50 101 OP0P is not a partner of EA2RCF-5
> EA4RCH-5 DL9GTB-1 0 51 51
> EA6VQ-1 EA4URE-3 0 49 49 Bad password in EA6VQ-1
> EA7URG-5 GB7NHR 61 54 115
> ED1ZAC-5 OP0P 0 36 36
> EI7MRE OP0P 51 50 101
> EI7MRE UT1U 54 53 107
> EI7SDX ON4KST 0 46 46 is ON4KST-2 and is spider not AK1A
> F4EYQ-1 N6WS-6 0 447 447
> F4IAA-3 CT1EBQ-9 0 109 109
> F6BVP-3 F6KVP-3 194 96 290
> F6KVP-3 F6BVP-3 151 96 247
> GB7NHR EA7URG 108 54 162 There is no EA7URG, it is EA7URG-5
> HI8S-8 NL7S 16 15 31
> I8ZSE-1 SV1IW-9 0 107 107
> IK2DUW-6 IW2OHX-6 0 108 108
> IK8HJC-6 M0KGX-3 0 126 126
> IW1PSC-6 IK2XDE-6 0 93 93
> IW1PSC-6 PA1RBZ 0 107 107
> IW1QLH-6 IW1QLH-2 153 0 153
> IW1QLH-6 JG1VGX-8 66 66 132
> IW1QLH-6 OP0P 35 0 35
> IW1QLH-6 PY5JO-11 0 31 31
> IW5ECF-6 K1TTT 39 38 77
> IW5ECF-6 WC2L 39 38 77
> IW9FRA-6 K1TTT 52 51 103
> IZ0FKE IZ0ORT-8 0 52 52
> IZ0FKE SV1IW-9 0 106 106
> IZ0FKE-6 VE7CC 0 36 36
> IZ0ORT-6 IW0ERQ-6 0 108 108
> IZ0ORT-6 IZ0ORT-8 67 67 134
> JG1VGX-9 JA2YYF-9 54 53 107
> JH1RFM-9 EA4URE-2 0 215 215
> KB3CMT-2 GB7VAX 0 105 105
> KB3CMT-2 PY2ZEN-6 0 105 105
> KD4WLE-4 K1TTT 0 51 51 K1TTT is not an AK1A, it is an
> ARC.
> KM3T-10 KM3T-5 0 51 51
> N2YO-2 YO2LOJ-2 54 54 108
> OK0DXI SR4DXC 18 9 27
> OK2CQR-1 VA3UG 102 48 150
> ON3URE-2 EA4URE-3 0 108 108 Bad password in ON3URE-2
> PE1ITR-8 IV3SCP-6 0 108 108
> PE1ITR-8 OP0P 51 51 102
> PY1NB-4 K1TTT 67 67 134
> R2AKT-9 R2DGO-1 0 1033 1033
> R2DGO-1 R2AKT-9 64 0 64
> R2AKT-9 RA3ATX-8 66 66 132
> R2DGO-1 OP0P 0 36 36
> R2DGO-1 SV1IW-9 0 108 108
> RA3ATX-9 R2AKT-9 122 64 186
> SK3W-6 N6WS-6 0 89 89
> SK3W-6 OP0P 51 50 101
> SM6HOC-6 M0KGX-3 0 126 126
> SM7IUN-1 M0KGX-3 0 233 233
> SP6MI-2 MX0NCA 0 1072 1072
> SV1IW-9 M0KGX-3 0 126 126
> SV5FRI-1 JA2YYF-9 53 54 107
> SV5FRI-1 LA3WAA-6 0 123 123
> TA2NC IK7IMO-6 0 1074 1074
> VE3EY-7 K1TTT 53 53 106
> VE3TOK-1 VA3BAL-1 19 19 38
> VE3TOK-1 VE3CLG-1 19 19 38
> VE3TOK-1 VE3LNZ-1 20 20 40
> VE3ZIN-2 M0KGX-3 0 126 126
> VE3ZIN-2 OK2CQR-1 103 55 158
> VE6CIC-1 WB3FFV 53 1 54
> W9TY-1 WA0O-9 0 1074 1074
> WA9PIE-2 DB0SUE-7 0 68 68 DB0SUE-7 does not exist
> WB3FFV-2 DB0SUE-7 0 215 215 DB0SUE-7 does not exist
> WB3FFV-2 HB9DRV-9 0 214 214 HB9DRV-9 does not exist
> WB3FFV-2 VE6CIC-1 53 54 107
> YO2LOJ-2 N2YO-4 54 54 108 There is no N2YO-4, it's N2YO-2
>
> If anyone needs to locate an email from a sysop, here is a link to
> Jim's excellent website:
> https://www.dxcluster.info/telnet/index.php
>
> For those who don't want to complicate things, there is a Solomonic
> solution: set/lock <node>.
>
> Many thanks to those of you who have contributed.
>
> 73 de Kin EA3CV
>
>
> -----Mensaje original-----
> De: Kin <ea3cv at cronux.net>
> Enviado el: sábado, 4 de enero de 2025 14:21
> Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
> Asunto: RE: Partnes with connection problems
>
> Hi,
>
> Continuing the thread, I have added some comments on some couples. I
> hope it will help to sort it out.
>
> I have also attached a link to a pdf of how to correctly configure a
> link between nodes. I know there is different documentation, but it
> seems to be clear.
> https://github.com/EA3CV/dxspider_info/blob/f2ed6e3bc467cd8abeadd691e1
> 8f8dcb
> e7fc212b/Docs/HOW%20TO%20SET%20UP%20A%20PARTNER%20NODE%20IN%20DXSPIDER
> .pdf
>
> If there is someone who can't or won't solve the problem, I would ask
> them to comment out the connection line in their crontab. No matter
> how hard you try to connect, you won't succeed if you don't fix the
> problem, and at the very least, it will help to maintain the network better.
>
> I have noticed that a few sysops have taken my comments into account
> and taken action. Thanks to all who make our hobby better.
>
>
> Node-1 Node-2 Conn Disc ALL
> ----------------------------------------
> 7N4TWL-7 JA2YYF-9 72 72 144
> 9A0DXC DB0SUE-7 144 72 216 DB0SUE-7 does not exist
> 9A0DXC HG8PRC 28 14 42
> 9M2PJU-2 WB3FFV-2 72 72 144
> BG2RVL-9 JA2YYF-9 72 72 144
> CS5SEL-5 CQ0PCV-9 72 72 144
> CT1EBQ-9 CS5SEL-5 72 72 144
> CU3HY-2 SV5FRI 144 69 213 It is not SV5FRI, the correct
> callsign is SV5FRI-1
> DB0ALG-9 DB0PER 16 85 101
> DB0HGW-6 DB0SUE-7 160 80 240 DB0SUE-7 does not exist
> DB0OVN-6 DB0SUE-7 144 71 215 DB0SUE-7 does not exist
> DB0PER DB0PER-1 13 14 27
> DH1TW-2 NC7J 90 90 180
> DJ4PK-2 HB9DRV-9 180 90 270 HB9DRV-9 does not exist
> DO5SSB-2 9A0DXC 72 72 144
> DO5SSB-2 DB0HGW-6 80 80 160
> DO5SSB-2 DB0OVN-6 73 71 144
> DO5SSB-2 EA4URE-2 0 288 288 DO5SSB-2 is not a partner of
> EA4URE-2
> DO5SSB-2 HB9DRV-9 180 90 270 HB9DRV-9 does not exist
> DO5SSB-2 KB2SYD-5 180 90 270
> DO5SSB-2 WA9PIE-2 72 72 144
> DO5SSB-2 WB3FFV-2 72 72 144
> EA2RCF-5 OP0P 71 71 142
> EA4RCH-5 DL9GTB-1 0 68 68
> EA6VQ-1 EA4URE-3 0 78 78 Wrong configuration in EA6VQ-1
> EA7URG-5 GB7NHR 72 72 144
> ED1ZAC-5 OP0P 0 48 48
> EI7MRE OP0P 71 71 142
> EI7MRE UT1U 72 72 144
> EI7SDX ON4KST 0 62 62 It is not ON4KST, the correct
> callsign is ON4KST-2
> F1FCA-2 KF8MZ-3 136 72 208
> F4EYQ-1 N6WS-6 0 599 599
> F4IAA-3 CT1EBQ-9 0 141 141
> F6BVP-3 F6KVP-3 256 129 385
> F6KVP-3 F6BVP-3 194 129 323
> GB7NHR EA7URG 144 72 216 It is not EA7URG, the correct
> callsign is EA7URG-2
> GB7VAX LA7Q-6 0 29 29
> HG8PRC 9A0DXC 20 14 34
> HG8PRC F6GCP-3 15 14 29
> HG8PRC KC9AOP-1 14 14 28
> HI8S-8 NL7S 71 71 142
> IK2DUW-6 IW2OHX-6 0 143 143
> IK7NXU-6 IZ3LSV-6 25 12 37
> IK8HJC-6 M0KGX-3 0 167 167
> IQ1LA-6 IK2XDE-6 0 135 135
> IV3SCP-6 IZ3LSV-6 24 12 36
> IW1PSC-6 PA1RBZ 0 140 140
> IW1QLH-6 IW1QLH-2 175 0 175 IW1QLH-2 is not a node
> IW1QLH-6 JG1VGX-8 90 90 180
> IW1QLH-6 PY5JO-11 0 34 34
> IW5ECF-6 K1TTT 47 47 94
> IW5ECF-6 WC2L 47 47 94
> IW9FRA-6 K1TTT 71 72 143
> IZ0FKE IZ0ORT-8 0 37 37
> IZ0ORT-6 IW0ERQ-6 0 144 144
> IZ0ORT-6 IZ0ORT-8 51 50 101
> IZ3LSV-6 IK7NXU-6 16 13 29
> JE3YEK JA2YYF-9 71 71 142
> JG1VGX-9 JA2YYF-9 72 72 144
> JH1RFM-9 EA4URE-2 0 288 288 Wrong configuration in JH1RFM-9
> KB3CMT-2 GB7VAX 0 138 138
> KB3CMT-2 PY2ZEN-6 0 140 140
> KC9AOP-1 HG8PRC 28 14 42
> KD4WLE-4 K1TTT 0 68 68
> KE2L-5 DO5SSB-2 171 90 261
> KF8I-3 F1FCA-2 126 72 198
> KM3T-10 KM3T-5 0 69 69
> KY9J-2 VE2PKT 142 71 213 It is not VE2PKT, the correct
> callsign is VE2PKT-9
> KY9J-2 VK5GR 141 71 212 It is not VK5GR, the correct
> callsign is VK5GR-2
> N2YO-2 YO2LOJ-2 72 72 144
> NL7S HI8S 71 0 71 It is not HI8S, the correct
> callsign is HI8S-8
> OK0DXI SR4DXC 25 14 39
> OK2CQR-1 VA3UG 177 90 267
> ON3URE-2 EA3CV-3 0 144 144 Wrong configuration in ON3URE-2
> ON3URE-2 EA4URE-3 0 144 144 Wrong configuration in ON3URE-2
> PE1ITR-8 IV3SCP-6 0 144 144
> PE1ITR-8 OP0P 71 71 142 OP0P is not AK1A, it is a CCC
> (set/spider)
> PY1NB-4 K1TTT 90 90 180
> PY3NZ-8 PY4OG-2 144 72 216
> PY4OG-4 PY3NZ-8 72 72 144
> R2AKT-9 R2DGO-1 0 1411 1411
> R2AKT-9 RA3ATX-8 88 88 176
> R2DGO-1 OP0P 0 48 48
> R2DGO-1 R2AKT-9 80 0 80
> RA3ATX-9 R2AKT-9 150 88 238
> SK3W-6 N6WS-6 0 120 120
> SK3W-6 OP0P 70 71 141
> SM6HOC-6 M0KGX-3 0 167 167
> SM7IUN-1 M0KGX-3 0 311 311
> SP6MI-2 MX0NCA 0 1421 1421
> SR4DXC OK0DXI 27 14 41
> SV1IW-9 M0KGX-3 0 166 166
> SV5FRI-1 CU3HY-2 73 72 145
> SV5FRI-1 JA2YYF-9 72 72 144
> SV5FRI-1 LA3WAA-6 0 153 153
> SV5FRI-1 VE6CIC-1 72 72 144
> TA2NC IK7IMO-6 0 1417 1417
> VA3BAL-1 VE3TOK-1 26 0 26
> VE2PKT-9 KY9J-2 71 71 142
> VE3CLG-1 VE3TOK-1 26 0 26
> VE3EY-7 K1TTT 72 72 144
> VE3LNZ-1 VE3TOK-1 25 0 25
> VE3TOK-1 VA3BAL-1 26 26 52
> VE3TOK-1 VE3CLG-1 26 26 52
> VE3TOK-1 VE3LNZ-1 25 25 50
> VE3ZIN-2 M0KGX-3 0 167 167
> VE3ZIN-2 OK2CQR-1 177 90 267
> VE6CIC-1 SV5FRI 72 0 72
> VE6CIC-1 WB3FFV 72 0 72
> VK5GR-2 KY9J-2 71 145 216
> W9TY-1 WA0O-9 0 1359 1359
> WA9PIE-2 DB0SUE-7 144 72 216 DB0SUE-7 does not exist
> WA9PIE-2 DJ4PK-2 90 90 180
> WA9PIE-2 DO5SSB-2 107 90 197
> WB3FFV-2 9M2PJU-1 141 72 213 It is not 9M2PJU-1, the correct
> callsign is 9M2PJU-2
> WB3FFV-2 DB0SUE-7 144 72 216 DB0SUE-7 does not exist
> WB3FFV-2 HB9DRV-9 0 287 287 HB9DRV-9 does not exist
> WB3FFV-2 VE6CIC-1 72 72 144
> YO2LOJ-2 N2YO-4 72 72 144 It is not N2YO-4, the correct
> callsign is N2YO-2
>
> Regards,
>
> Kin EA3CV
>
>
>
> -----Mensaje original-----
> De: Kin <ea3cv at cronux.net>
> Enviado el: jueves, 2 de enero de 2025 9:54
> Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
> Asunto: RE: Partnes with connection problems
>
> Hi and Happy New Year,
>
> Updating the list.
>
> List updated as of 1 January for values > 24
>
> Node-1 Node-2 Conn Disc ALL
> ----------------------------------------
> 7N4TWL-7 JA2YYF-9 72 72 144
> 9A0DXC DB0SUE-7 144 72 216
> 9A0DXC HG8PRC 24 13 37
> 9M2PJU-2 WB3FFV-2 72 72 144
> BG2RVL-9 JA2YYF-9 72 71 143
> CS5SEL-5 CQ0PCV-9 73 72 145
> CT1EBQ-9 CS5SEL-5 71 71 142
> CU3HY-2 SV5FRI 141 73 214
> DB0ALG-9 DB0PER 23 75 98
> DB0HGW-6 DB0SUE-7 160 80 240
> DB0OVN-6 DB0SUE-7 143 71 214
> DB0PER DB0PER-1 16 14 30
> DH1TW-2 K1TTT 44 50 94
> DH1TW-2 NC7J 50 48 98
> DH1TW-2 PY1TSB-1 60 39 99
> DJ4PK-2 HB9DRV-9 180 90 270 Node HB9DRV-9 does not exist.
> Remove from the crontab
> DO5SSB-2 9A0DXC 72 72 144
> DO5SSB-2 DB0HGW-6 80 80 160
> DO5SSB-2 DB0OVN-6 72 72 144
> DO5SSB-2 EA4URE-2 0 287 287
> DO5SSB-2 HB9DRV-9 180 90 270 Node HB9DRV-9 does not exist.
> Remove from the crontab
> DO5SSB-2 KB2SYD-5 180 90 270
> DO5SSB-2 WA9PIE-2 72 72 144
> DO5SSB-2 WB3FFV-2 139 72 211
> EA2RCF-5 OP0P 72 72 144
> EA4RCH-5 DL9GTB-1 0 69 69
> EA6VQ-1 EA4URE-3 0 28 28
> EA7URG-5 DB0SUE-7 0 119 119
> EA7URG-5 GB7NHR 72 72 144
> ED1ZAC-5 OP0P 0 51 51
> EI7MRE OP0P 72 72 144
> EI7MRE UT1U 72 72 144
> EI7SDX ON4KST 0 62 62
> F1FCA-2 KF8MZ-3 143 72 215
> F4EYQ-1 N6WS-6 0 600 600
> F4IAA-3 CT1EBQ-9 0 147 147
> F6BVP-3 F6KVP-3 280 141 421
> F6KVP-3 F6BVP-3 193 141 334
> GB7DXG-1 VE9SC 0 120 120
> GB7NHR EA7URG 136 72 208 Node EA7URG does not exist, it is
> EA7URG-5
> GB7VAX LA7Q-6 0 49 49
> HG8PRC 9A0DXC 20 13 33
> HG8PRC F6GCP-3 13 14 27
> HG8PRC KC9AOP-1 20 20 40
> HG8PRC ON0LLV-5 15 17 32
> HI8S-8 NL7S 71 71 142
> IK2DUW-6 IW2OHX-6 0 144 144
> IK7NXU-6 IZ3LSV-6 43 22 65
> IK8HJC-6 M0KGX-3 0 168 168
> IQ1LA-6 IK2XDE-6 0 140 140
> IV3SCP-6 IZ3LSV-6 40 20 60
> IW1PSC-6 PA1RBZ 0 105 105
> IW1QLH-6 IW1QLH-2 197 0 197
> IW1QLH-6 JG1VGX-8 89 89 178
> IW1QLH-6 PY5JO-11 0 38 38
> IW5ECF-6 K1TTT 54 54 108
> IW5ECF-6 WC2L 54 54 108
> IW9FRA-6 K1TTT 70 69 139
> IZ0FKE IZ0ORT-8 0 30 30
> IZ0ORT-6 IW0ERQ-6 0 141 141
> IZ0ORT-6 IZ0ORT-8 39 39 78
> IZ3LSV-6 IK7NXU-6 32 20 52
> IZ3LSV-6 IV3SCP-6 25 19 44
> JE3YEK JA2YYF-9 71 71 142
> JG1VGX-9 JA2YYF-9 71 72 143
> JH1RFM-9 EA4URE-2 0 287 287
> KB3CMT-2 GB7VAX 0 141 141
> KB3CMT-2 PY2ZEN-6 0 143 143
> KC9AOP-1 HG8PRC 39 19 58
> KD4WLE-4 K1TTT 0 69 69
> KE2L-5 DO5SSB-2 141 90 231
> KF8I-3 F1FCA-2 142 72 214
> KM3T-10 KM3T-5 0 53 53
> KY9J-2 VE2PKT 144 73 217
> KY9J-2 VK5GR 142 73 215
> N2YO-2 YO2LOJ-2 72 72 144
> NL7S HI8S 71 0 71
> OK0DXI SR4DXC 26 13 39
> OK2CQR-1 IK2XDE-6 26 0 26
> OK2CQR-1 VA3UG 180 90 270
> ON0LLV-5 HG8PRC 25 17 42
> ON3URE-2 EA3CV-3 0 144 144
> ON3URE-2 EA4URE-3 0 143 143
> PE1ITR-8 IV3SCP-6 0 144 144
> PE1ITR-8 OP0P 72 72 144
> PY1NB-4 K1TTT 90 90 180
> PY1TSP-1 DH1TW-2 85 44 129
> PY3NZ-8 PY4OG-2 144 72 216
> PY4OG-4 PY3NZ-8 72 72 144
> R2AKT-9 R2DGO-1 0 1404 1404
> R2AKT-9 RA3ATX-8 88 88 176
> R2DGO-1 OP0P 0 48 48
> R2DGO-1 R2AKT-9 84 0 84
> RA3ATX-9 R2AKT-9 147 88 235
> SK3W-6 N6WS-6 0 120 120
> SK3W-6 OP0P 72 70 142
> SM6HOC-6 M0KGX-3 0 168 168
> SM7IUN-1 M0KGX-3 0 311 311
> SP6MI-2 MX0NCA 0 783 783
> SP6MI-2 SP6PWS 40 0 40
> SP6PWS-2 SP6MI-2 41 41 82
> SR4DXC OK0DXI 26 13 39
> SV1IW-9 M0KGX-3 0 168 168
> SV2HRT-1 CT1EBQ-9 0 137 137
> SV2HRT-1 HB9VQQ-2 0 1367 1367
> SV5FRI-1 CU3HY-2 71 72 143
> SV5FRI-1 JA2YYF-9 72 72 144
> SV5FRI-1 LA3WAA-6 0 167 167
> SV5FRI-1 VE6CIC-1 72 72 144
> TA2NC IK7IMO-6 0 1439 1439
> VA3BAL-1 VE3TOK-1 27 0 27
> VE2PKT-9 KY9J-2 72 72 144
> VE2PKT-9 OP0P 30 0 30
> VE3CLG-1 VE3TOK-1 27 0 27
> VE3EY-7 K1TTT 72 72 144
> VE3LNZ-1 VE3TOK-1 27 0 27
> VE3TOK-1 VA3BAL-1 27 27 54
> VE3TOK-1 VE3CLG-1 27 27 54
> VE3TOK-1 VE3LNZ-1 27 27 54
> VE3ZIN-2 M0KGX-3 0 168 168
> VE3ZIN-2 OK2CQR-1 135 90 225
> VE6CIC-1 SV5FRI 72 0 72
> VE6CIC-1 WB3FFV 72 0 72
> VK5GR-2 KY9J-2 72 142 214
> W9TY-1 WA0O-9 0 1433 1433
> WA9PIE-2 DB0SUE-7 144 72 216
> WA9PIE-2 DJ4PK-2 90 90 180
> WA9PIE-2 DO5SSB-2 90 90 180
> WB3FFV-2 9M2PJU-1 144 72 216
> WB3FFV-2 DB0SUE-7 144 72 216
> WB3FFV-2 HB9DRV-9 0 286 286 Node HB9DRV-9 does not exist.
> Remove from the crontab
> WB3FFV-2 VE6CIC-1 72 72 144
> YO2LOJ-2 N2YO-4 72 72 144
> ----------------------------------------
> Total 7731 16712 24443
>
>
> Kin EA3CV
>
> EA3CV-2 dxcluster.cronux.net 7300
> https://clustermap.cronux.net/map.html
> https://clustermap.cronux.net/route_finder.html
>
>
> -----Mensaje original-----
> De: Kin <ea3cv at cronux.net>
> Enviado el: martes, 31 de diciembre de 2024 12:08
> Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
> Asunto: Partnes with connection problems
>
> 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
>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
--
73 de Jean,
VA2OM / VE2PKT
Sysop de: VE2PKT (BBS), VE2PKT-2 (BPQNode), VE2PKT-4 (XRPI)
: VE2PKT-5 (Jnos), VE2PKT-9 (DXCluster)
RF: 145.05 Mhz (1.2K Bps) Packet, 147.435 Mhz, VARA
Internet:
Telnet: ve2pkt.dyndns.org port 2323 (Xrpi Node) - VE2PKT-4
Telnet: ve2pkt.dyndns.org port 9000 (DXCluster) - VE2PKT-9
AMPR Network:
Telnet xrouter.ve2pkt.ampr.org (XRPI Node) = VE2PKT-4 Telnet dxc.ve2pkt.dyndns.org (DXCluster) = V2PKT-9 Telnet bpq.ve2pkt.ampr.org (BPQ BBS) = VE2PKT-2 Telnet jnos.ve2pkt.ampr.org (Jnos) = VE2PKT-5
E-Mail:
packet: va2om at ve2pkt.#qbc.qc.can.noam
ampr net: va2om at bpq.ve2pkt.ampr.org
Inet: ve2pkt at gmail.com
Membre Createur du groupe PacketQuebec at groups.io
https://groups.io/g/PacketQuebec
Carte des Station RF au Quebec
https://www.google.com/maps/d/u/0/viewer?invite=CIero5gJ&mid=12uFqoa9Kw7jM-kkFOEPOiO03DVSd1efb&ll=47.12459570312563%2C-70.50095495000002&z=7
_______________________________________________
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
_______________________________________________
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/20250106/fc0ec22a/attachment-0001.htm>
More information about the Dxspider-support
mailing list