[Dxspider-support] Initial cluster to cluster handshake

[Dirk Koopman]

There is no "initial handshake" as such for nodes at this level. You are 
not a node until you have successfully logged in as a known entity to a 
node. Only at that point does PC protocol happen - *_if you are defined 
as a node with that callsign_* - on the node that you are attempting to 
connect to.  Otherwise you will be treated as a user, given the contents 
of any MOTD file and sent a user prompt.

So if one connects to a PC92 capable node; you have successfully logged 
with user (+password if required); that username is a callsign that is 
recognised as a node by the receiving node; you are not locked out there 
(the default for some random node callsign)  -  then this happens 
(GB7TLH-2 connecting to GB7DJK) as shown from the receiving node's 
(GB7DJK) point of view:

11:31:10 (chan) <- A GB7TLH-2 telnet
11:31:10 (chan) -> B GB7TLH-2 0
11:31:10 (chan) -> E GB7TLH-2 0
*11:31:10 (chan) -> D GB7TLH-2 PC18^DXSpider Version: 1.57 Build: 569 
Git: test/83fc0019[r] pc9x^5457^*
11:31:10 (state) GB7TLH-2 channel func  state 0 -> init
*11:31:10 (chan) <- I GB7TLH-2 
PC92^GB7TLH-2^41469^A^^5GB7DJK:2001,bc8,3b8c,200,,2^H99^*
11:31:10 (state) GB7TLH-2 channel func  state init -> init92
11:31:10 (*) DXPROT: Do pc9x set on GB7TLH-2
*11:31:10 (chan) <- I GB7TLH-2 
PC92^GB7TLH-2^41469.01^K^5GB7TLH-2:5457:536^4^1^H99^
11:31:10 (chan) <- I GB7TLH-2 PC20^*
11:31:10 (*) GB7TLH-2 send_local_config: doing pc9x
*11:31:10 (chan) -> D GB7TLH-2 
PC92^GB7DJK^41469^A^^5GB7TLH-2:2a01,4f8,1c1b,c95c,,1^H99^
11:31:10 (chan) -> D GB7TLH-2 
PC92^GB7DJK^41469.01^K^5GB7DJK:5457:569^25^65^163.172.11.79^test/83fc0019[r]^H99^
11:31:10 (chan) -> D GB7TLH-2 PC22^*
11:31:10 (state) GB7TLH-2 channel func  state init92 -> normal

shortly followed by:

*11:31:13 (chan) <- I GB7TLH-2 PC51^GB7DJK^GB7TLH-2^1^*
*11:31:13 (chan) -> D GB7TLH-2 PC51^GB7TLH-2^GB7DJK^0^*

Actual data transfer data *green* = GB7DJK (receiving node)*red *= 
GB7TLH-2 (connecting node).

The stuff in black is normal logging on the receiving node (GB7DJK) - 
and not passed across this connection.

Connecting to an old style PC protocol node is much more verbose but the 
PC18 -> PC20 -> PC22 pattern is the same. It just has a big flurry of 
PC19/PC17 records in between these three markers. The principle is the same.

Dirk G1TLH

On 08/03/2025 22:39, Rudy Bakalov via Dxspider-support wrote:
> I was wondering if anyone can shed some light on what the initial 
> handshake between two cluster partners looks like. Presumably it is 
> something like this:
>
>  1. Cluster A connects to Cluster B.
>  2. Cluster B says "Login:"
>  3. Cluster A says "N2WQ-1"
>  4. What happens next?
>
> I have been trying to see how this works by connecting to my cluster 
> and providing a SSID registered as a partner, but nothing happens 
> after I provide the SSID:
>
> Inline image
>
> Meanwhile, I enabled logging in Winsock to see the chatter between 
> partners and see something like this:
>
>  -> 22:14:10 N2WQ-1 PC61^21339.0^K0WHY^08-Mar-2025^2214Z^OK QSO Party: 
> Kay^K4SBZ^AE5E^135.129.119.21^H98^~
>  -> 22:14:11 ND4X PC61^21339.0^K0WHY^08-Mar-2025^2214Z^OK QSO Party: 
> Kay^K4SBZ^AE5E^135.129.119.21^H98^~
>  -> 22:14:11 EA7JXH PC61^21339.0^K0WHY^08-Mar-2025^2214Z^OK QSO Party: 
> Kay^K4SBZ^AE5E^135.129.119.21^H97^~
>
> So going back to my question on the initial handshake, how do I get 
> traffic going to show PC61 messages?
>
> Rudy N2WQ
>
> _______________________________________________
> 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/20250310/7ca008c1/attachment.htm>