N2WQ-1 no longer accepts peers, only humans. It is running CC Cluster. Despite numerous emails to peers many still try connecting to it as nodes :-(

Here's the text of my emails:

I'd like to thank all of my partners that have been feeding N2WQ-1 over the years. The time has come to migrate to what I believe is a solution that serves better end users, while helping reduce malicious spots across the cluster network.

Please change your connection settings to replace N2WQ-1 with N2WQ-73. N2WQ-73 will handle all partner connections for both nodes. N2WQ-73 is at dxs.n2wq.com port 7300. N2WQ-73 runs DXSpider on AWS and is available 24/7. If you'd like to establish partnering password, no problem, let me know what password you want to set.

N2WQ-1 will no longer have partners of its own; it will only serve end users.

Thank you so much for your partnership!

73, Rudy N2WQ

Rudy N2WQ

On Monday, February 2, 2026 at 02:47:40 PM EST, Erik Schott via Dxspider-support <dxspider-support@dxcluster.org> wrote:


Dear Kin,

I saw my clusters callsign in your mail a verified it here locally but I feel to understand what goes wrong.
I have a working connection with N2WQ-1 but it is different version as the others:

set/var $DXProt::pc92_ad_enabled = 1
set/var $DXProt::pc92c_ipaddr_enable = 1
Have been done

Node Call  Sort    Version
9M2PJU-2    Spider  1.57 build: 547
F1FCA-2    Spider  1.57 build: 633
IK5ZUK-6    Spider  1.57 build: 633
N2KI        Spider  1.57 build: 633
N2WQ-1      Spider  4947
PA0ESH-3    Spider  1.57 build: 633
PY2ZEN-6    Spider  1.57 build: 633
VK2AZ-2    Spider  1.57 build: 633

But maybe N2WQ-1  has no script running on his side?
Any help is appreciated.
Erik, PA0ESH

> Op 2 feb 2026, om 20:26 heeft Kin via Dxspider-support <dxspider-support@dxcluster.org> het volgende geschreven:
>
> Hi,
>  * It is advisable to have PC92 enabled, in particular:
> set/var $DXProt::pc92_ad_enabled = 1
> set/var $DXProt::pc92c_ipaddr_enable = 1
> Although it may not always be feasible, it would be beneficial to encourage our CCC neighbor nodes to enable PC92, even in a limited form. This can significantly help when network-related issues arise.
>  * It is also recommended to periodically review the neighboring nodes we currently have configured. Some nodes may change, disappear, or stop responding, yet we may continue sending requests to them indefinitely.
>  * Keeping the node software up to date is essential, as many network-related issues are resolved in newer versions.
>  * Please note that the RBN servers SK0MMR and SK1MMR are not typical DXSpider nodes. They must be explicitly defined as RBN nodes, for example:
> set/rbn SK0MMR
> set/rbn SK1MMR
>
> Finally, some examples of failed connections between nodes include:
> Conn: number of connections
> Disc: number of disconnections
>  Node-1    Node-2    Conn  Disc  ALL 
> ----------------------------------------
> DB0ERF-5  ON0DXC    0      105    105 
> DH1TW-2    AE5E      0      43    43   
> DH1TW-2    N6WS-6    0      900    900
> ED1ZAC-5  CT1EBQ-9  0      88    88   
> EI7SDX    ON4KST    0      38    38   
> F6KVP-3    MB6WV      0      90    90   
> G1FEF-2    G4BFG-9    0      179    179 
> G3FCA-4    G3FCA-8    179    0      179 
> IZ7AUH-6  IZ7AUH-6  0      900    900 
> HB9VQQ-2  N6WS-6    0      900    900
> HI8S-8    M0IPU-4    0      90    90   
> I8ZSE-1    F4BWT-3    0      90    90   
> IQ1LA-6    PA1RBZ    0      90    90   
> IW1QLH-6  IW1QLH-2  252    0      252
> K1AX-11    VE7CC-1    0      28    28   
> KB3CMT-2  GB7VAX    0      89    89 
> KB3CMT-2  PA4JJ-2    0      88    88
> KB3CMT-2  PY2ZEN-6  0      90    90
> KF8I-3    KB8PMY-3  0      90    90   
> M0KGX-3    N2WQ-1    0      33    33 
> ON0DXC    SK1MMR    0      37    37 
> PA0ESH-3  N2WQ-1    0      31    31   
> PY3NZ-8    KC9AOP-1  0      180    180 
> PY4OG-4    GB7DJK    0      90    90   
> R2DGO-1    OP0P      0      39    39   
> SM7IUN-1  HI8S-8    0      90    90   
> SM7IUN-2  DL0PF      0      133    133 
> UA4CC      AE5E      0      30    30   
> UF3K-1    R1BLH-1    0      900    900 
> VE3ZIN-2  HI8S-8    0      90    90
> VE6CIC-1  SV5FRI    45    0      45
> W6RFU      JG1VGX-9  0      90    90 
> W6RFU      VE6DXC    0      90    90 
> WB3FFV-2  AE5E      0      40    40 
> YV5KXE    IK4PKL    0      90    90
>  73 de Kin EA3CV
>  _______________________________________________
> Dxspider-support mailing list -- dxspider-support@dxcluster.org
> To unsubscribe send an email to dxspider-support-leave@dxcluster.org


_______________________________________________
Dxspider-support mailing list -- dxspider-support@dxcluster.org
To unsubscribe send an email to dxspider-support-leave@dxcluster.org