(Newbie) Getting "Exchange failed: Unexpected response: 'Login [481]:'" When connecting on AX25

Jeremiah Puhek

unread,

Feb 20, 2018, 9:57:38 PM2/20/18

to pat-users

Hi all,

So I'm a newbie to PAT and to Winlink, But I'm a long time ham and Linux user.

I'm running into an odd issue when connecting to our local ARES Winlink Gateway on Packet, when I connect with Pat the gateway will request a login and Pat will fail with "Exchange failed: Unexpected response: 'Login [481]:'". But if I pull out my Windows Laptop and connect with RMS Express with the same TNC/Radio the same gateway will let me connect and get messages with out ever sending the Login promt.

So I'm not sure if I built pat wrong, or configured it wrong or what. Below is the exchange(as seen my ax25spy) when I try to connect with pat:

vhf: AX25: AD7DD-10->KD7DMP Text
[WL2K-5.0-B2FWIHJM$]
vhf: AX25: KD7DMP->AD7DD-10 <RR R R1>
vhf: AX25: AD7DD-10->KD7DMP <RR C+ R0>
vhf: AX25: KD7DMP->AD7DD-10 <RR R- R1>
vhf: AX25: AD7DD-10->KD7DMP Text
;PQ: 40358702
vhf: AX25: AD7DD-10->KD7DMP Text
CMS via AD7DD >
vhf: AX25: KD7DMP->AD7DD-10 Text
;FW: KD7DMP
[Pat-0.6.0-B2FHMG$]
;PR: 34764204
; AD7DD-10 DE KD7DMP (DN17)
vhf: AX25: KD7DMP->AD7DD-10 Text
FF
vhf: AX25: AD7DD-10->KD7DMP <RR R- R2>
vhf: AX25: AD7DD-10->KD7DMP Text
Login [481]:
vhf: AX25: KD7DMP->AD7DD-10 Text
*** Unexpected response: 'Login [481]:'

I'm running OpenSuse Linux LEAP 42.3 and Built Pat via go with the most recent version from Github.

Below is my current config:

{
"mycall": "KD7DMP",
"secure_login_password": "-------------",
"auxiliary_addresses": [],
"locator": "DN17",
"http_addr": "192.168.2.192:8080",
"motd": [
   "Open source Winlink client - getpat.io"
],
"connect_aliases": {
   "telnet": "telnet://{mycall}:CMST...@cms.winlink.org:8772/wl2k"
},
"listen": [],
"hamlib_rigs": {},
"ax25": {
   "port": "vhf",
   "beacon": {
     "every": 3600,
     "message": "Winlink P2P",
     "destination": "IDENT"
   },
   "rig": ""
},
"serial-tnc": {
   "path": "/dev/ttyUSB0",
   "baudrate": 9600,
   "type": "Kenwood"
},
"winmor": {
   "addr": "localhost:8500",
   "inbound_bandwidth": 1600,
   "drive_level": 0,
   "rig": "",
   "ptt_ctrl": false
},
"ardop": {
   "addr": "localhost:8515",
   "arq_bandwidth": {
     "Forced": false,
     "Max": 500
   },
   "rig": "",
   "ptt_ctrl": false,
   "beacon_interval": 0,
   "cwid_enabled": true
},
"telnet": {
   "listen_addr": ":8774",
   "password": ""
},
"gpsd_addr": "localhost:2947",
"schedule": {},
"version_reporting_disabled": false
}

Any help you can offer would very much appreciated. I really like PAT's interface and would prefer to stick with it for Winlink.

Thanks and 73's

Jeremiah

LA5NTA

unread,

Feb 25, 2018, 9:24:51 AM2/25/18

to pat-users

onsdag 21. februar 2018 03.57.38 UTC+1 skrev Jeremiah Puhek følgende:

I'm running into an odd issue when connecting to our local ARES Winlink Gateway on Packet, when I connect with Pat the gateway will request a login and Pat will fail with "Exchange failed: Unexpected response: 'Login [481]:'". But if I pull out my Windows Laptop and connect with RMS Express with the same TNC/Radio the same gateway will let me connect and get messages with out ever sending the Login promt.

Hi Jeremiah, welcome to the community!

Thanks for the detailed report. I've experienced this error myself lately, but very intermittent. My guess is that there is a bug in Winlink CMS or gateway software that is causing this. The "Login [xxx]" prompt is sent by the Winlink CMS software for raw keyboard connections, it should never be seen in a normal WL2K session.

Are you experiencing this error continuously or intermittent? Also, do you know which software the AD7DD-10 is running? Could it be running BPQ32 or linBPQ?

--

73 de LA5NTA/Martin

Jeremiah Puhek

unread,

Feb 25, 2018, 8:13:22 PM2/25/18

to LA5NTA, pat-users

The issues is very constant, every time I connect with PAT it will give me the same error, the numbers following the login prompt will some times change, but as I understand it that is just part of the WinLink systems.

I also tried it with another local Gateway and got the same thing.

I will need to ask and see what version they are running.

Jeremiah
Puhek

I have just three things to teach: simplicity, patience, compassion. These three are your greatest treasures. – Lao Tzu

--
You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/NQaKSv3aGv0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+unsubscribe@googlegroups.com.
To post to this group, send email to pat-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/3e52dbcf-07c9-4e78-8cc8-7c2e54d206d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

LA5NTA

unread,

Feb 26, 2018, 5:13:08 PM2/26/18

to pat-users

Jeremiah,

I am in contact with the Winlink Development Team regarding this issue. In the mean time, could you please tell me which kernel version (output of "uname -a") and TNC you are using?

Also, it would be very helpful to know a bit more about the setup on AD7DD-10 if you have their contact information. Details on software, TNC and operating system (including kernel version if they are running Linux) would be very valuable.

Thanks!

--

Martin

Jeremiah Puhek

unread,

Feb 26, 2018, 5:59:06 PM2/26/18

to LA5NTA, pat-users

Martin,

Thanks very much for digging into this. I sent an email off today to AD7DD to get info on how his gateway is setup and I'll send that your way as soon as I have it.

On my side of things I'm using a MFJ-1270C in KISS Mode connected via a USB to RS-232 Serial Adapter( ID 050d:0109 Belkin Components F5U109/F5U409 PDA Adapter According to lsusb).

Here is the Uname out put for that box. " Linux KD7DMP-Packet 4.4.114-42-default #1 SMP Tue Feb 6 10:58:10 UTC 2018 (b6ee9ae) x86_64 x86_64 x86_64 GNU/Linux"

Please let me know if you need any more info.

Thanks,

Jeremiah
Puhek

I have just three things to teach: simplicity, patience, compassion. These three are your greatest treasures. – Lao Tzu

--

You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/NQaKSv3aGv0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+unsubscribe@googlegroups.com.
To post to this group, send email to pat-...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/936c9164-4343-45c9-95d3-28e76bcea336%40googlegroups.com.

Jeremiah Puhek

unread,

Feb 27, 2018, 11:43:53 PM2/27/18

to LA5NTA, pat-users

Martin,

I just spoke with AD7DD about his gateway and he said it is running the latest RMS Packet and RMS Relay software on an up to date Windows 10 System.

Let me know if you need any more details and thanks again for the help.

Jeremiah
Puhek

I have just three things to teach: simplicity, patience, compassion. These three are your greatest treasures. – Lao Tzu

LA5NTA

unread,

Mar 7, 2018, 3:19:23 PM3/7/18

to pat-users

Hi Jeremiah,

with some great support for WDT I was able to see all CMS logs with this error. It looks like you are the only one experiencing this problem currently.

According to the CMS logs, the data sent from your node is not received correctly. The data packets is received out of order, and the stream is corrupt on the receiving end.

For instance, you sent: ";FW: KD7DMP"

But CMS received: ";FW(DN17)"

Since your axlisten log looks correct, my best guess is that your TNC's outbound buffer is corrupted somehow or you have a bad USB serial converter (or driver). It could also be a bad kernel branch. If I recall correctly, I've seen a similar situation with a TNC-X with a bad memory chip.

I would suggest that you try with another kernel version (>4.7) or try with another TNC to help diagnose the problem.

What is clear is that the connection stream gets corrupted somewhere between your kernel and the CMS.

Please keep us posted on your progress!

--

73 de LA5NTA/Martin

Jeremiah Puhek

unread,

Mar 8, 2018, 12:18:04 AM3/8/18

to LA5NTA, pat-users

Hi Martin,

So I swapped out the USB to RS232 converter and that did the trick.

I was able to send and receive and send an email via a gateway with out issue, I was using the same Computer, and TNC.(I used W7GBU-10 as AD7DD-10 seems to be having issues.)

So I'm going to test the old USB to RS232 converter a bit more to see what if I can figure out what the issues was with that unit.

Thank you for Checking with the WDT folks on this for me.

I have been using PAT with WINMOR on HF with great results thus far.

I've really been enjoying the the PAT interface as it is very simple to use, and the PAT config file has been easy to setup.

I'll let you know what I find on testing the old RS232 converter.

Thanks for your help and the great bit of software.

Jeremiah
Puhek

I have just three things to teach: simplicity, patience, compassion. These three are your greatest treasures. – Lao Tzu

--
You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/NQaKSv3aGv0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+unsubscribe@googlegroups.com.
To post to this group, send email to pat-...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/b0af6851-a83a-4740-b1b6-0b7904c553da%40googlegroups.com.

Reply all

Reply to author

Forward