Exchange failed: read wl2k: connection reset by peer

[Robert Cheek]

Pat log shows it connects then fails with error:

2025/04/24 13:48:40 Unable to get frequency from rig 370: dial tcp 127.0.0.1:4532: connect: connection refused.
2025/04/24 13:48:40 Connecting to W4NWG-10 (ax25+linux)...
2025/04/24 13:48:42 Connected to W4NWG-10 (AX.25)
Welcome to the W4NWG Hybrid Gateway
[WL2K-5.0-B2FWIHJM$]
;PQ: 14275247
CMS via W4NWG >
>FF
2025/04/24 13:49:36 Exchange failed: read wl2k: connection reset by peer

It worked yesterday, but fails today on two different gateways.  Does this mean the Winlink is down?  Tried a different computer with and older version of Ubuntu (22.04 vs 24.04) with same results. 

Or is there another problem that the gremlins got into my computer last night?

Regards,

Bob N4RFC

 

[Rich Sahlender]

Hello Robert,

I am unsure it is the root of the error but that first line from the log
indicates an inability to communicate with hamlib for rig control. Was
rigctl(d) running at the time?

73 de Rich WA3WLH

[Robert Cheek]

I had made one change to the PAT config file, to add a couple of alias lines to the configuration.  I had this:

 "connect_aliases": {
    "telnet": "telnet://{mycall}:CMST...@cms.winlink.org:8772/wl2k",
    "kj4uc": "ax25:///w4nwg-15/kj4uc-10",
    "w4nwg": "ax25:///w4nwg-10"

  },

and removed the two ax25 alias lines to this:

 "connect_aliases": {
    "telnet": "telnet://{mycall}:CMST...@cms.winlink.org:8772/wl2k"

  },

and now it is working again.  Anyone see a problem with the added lines.   I forgot a comma, but the that flagged an error that on startup of PAT that I corrected, or at least thought I did....

Regards,

Bob - N4RFC

[Robert Cheek]

I am not using Hamlib on AX25.  There is no rig definition in the config file so I am not sure where that error is coming from.  It has always been there and it worked in the past.  As you can see below it is working today. The radio that is used on AX25 has no CAT control.  On ARDOP I use a IC-7100.  The PTT commands are on the ARDOP startup string and seem to work.  Hamlib used to work but honestly I haven't used it in a while.  I just saw where the Hamlib rig number has changed from 370 to 3070 with the later version of Hamlib so I fixed. that.

On Thursday, April 24, 2025 at 3:00:59 PM UTC-4 rsahl...@gmail.com wrote: