Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Pat Menu - Telnet - "Invalid or missing target callsign" and "Grid square not set in Pat configure"
#pat-mail
Using BAP on Buster (last version available) and Pat v 0.12.0.
When I try to use the Telnet protocol to connect to Winlink, I get the error message "Invalid or missing target callsign".? I've made no changes to the Pat configuration file prior to getting this error. It used to work. If I run pat from the terminal window, this is what I get: ?
pi@buildapi3:~ $ pat connect telnet
2021/12/12 15:27:56 Unable to get frequency from rig my-rig: dial tcp?: connect: connection refused. 2021/12/12 15:27:56 Connecting to WL2K (telnet)... 2021/12/12 15:27:56 Connected to??(tcp) [WL2K-5.0-B2FWIHJM$] ;PQ: 77213018 CMS> >FF FQ 2021/12/12 15:27:57 Disconnected. So Pat itself is working. ?
?
But when in Pat Menu and trying to connect via telnet, it gives me this:
2021/12/12 15:29:41 Invalid or missing target callsign
?
Running pat configure shows:
{
? "telnet": {? "mycall": "N3JF", ? "secure_login_password": "mypassword", ? "auxiliary_addresses": [], ? "locator": "DM13DN", ? "service_codes": [ ? ? "PUBLIC" ? ], ? "http_addr": "127.0.0.1:5000",
? "motd": [
? ? "Open source Winlink client - getpat.io"
? ],
? "connect_aliases": {
? ? "telnet": "telnet://{mycall}:CMSTelnet@...:8772/wl2k",
? ? "AJ7C-20M-14106.5": "ardop:///AJ7C?freq=14106.5",
...snip...
? ? "listen_addr": ":8774", ? ? "password": "" ? }, ...snip...
?
I also have Conky running and it started showing the following error:
Grid square not set in Pat configure
?
As you can see, my grid square is defined in pat configure!
Any ideas on what's happening? Thanks, Julian |
Let's take Pat Menu out of the equation for the moment. Open a web browser and navigate to 127.0.0.1:5000 which will open the Pat mailbox. Try a telnet connection and let's see if it is successful.
The only thing that jumps out at me is there is a difference between our telnet statements in the Pat Config file. Yours is "telnet": "telnet://{mycall}:CMSTelnet@...:8772/wl2k", and mine looks like this. "telnet": "telnet://{mycall}:CMSTelnet@...:8772/wl2k" Here's a screenshot of my connect window after choosing telnet: Is "wl2k" populating into the target box? -- 73, de KM4ACK
|
|
|
Sorry... don't know how that line got messed up in the copy/paste process. It isn't like that in the config file, it actually says this:
??? "telnet": "telnet://{mycall}:CMSTelnet@...:8772/wl2k", ...so it's identical to yours.. OK, I see what is happening here... groups.io is protecting email addresses in the forum posts. It blanks out the domain after the @ symbol! Anyway, our lines are identical in the config file! Here it is with spaces added after the @ sign and the org: ??? "telnet": "telnet://{mycall}:CMSTelnet@ cms.winlink.org :8772/wl2k", When I select telnet, it does not populate the fields like in your example. It used to, but no longer does. I have not manually changed anything in the configuration file since telnet connections were last working. Julian |
Good catch on groups.io protecting the email.? I was wrong in the post on the Pat Forum. This isn't a Pat Menu issue but is something between the pat config file and the browser. We took Pat Menu out of the equation. Let's try to move your config file out of the way and grab a known good one to eliminate that possibility. Pay attention to the "." in some of the following commands. Run the following:
cd /home/pi/.config/pat/ mv config.json config.json.bkup wget https://raw.githubusercontent.com/km4ack/pi-scripts/master/config.json sudo systemctl restart pat@pi You will have to edit the call, passwd, and grid in the config file. In addition, look for this line: "http_addr": "127.0.0.1:8080" and change the 8080 to 5000. Then test from the browser again. If this works ok, it will just be a matter of adding your aliases to the new config file. If it doesn't work, we can undo this with cd /home/pi/.config/pat/ mv config.json.bkup config.json sudo systemctl restart pat@pi -- 73, de KM4ACK
|
|
|
On Wed, Dec 15, 2021 at 05:03 AM, km4ack wrote:
This isn't a Pat Menu issue but is something between the pat config file and the browser. We took Pat Menu out of the equation. Let's try to move your config file out of the way and grab a known good one to eliminate that possibility. Pay attention to the "." in some of the following commands. Run the following:I did the above and edited the config file (using pat configure) to update my call sign, Winlink password, grid square and change the port. I restarted pat (sudo systemctl restart pat@pi) againso that pat would use the modified port, and tried a telnet connection. The fields still did not populated correctly: My RMS list is set to update at 0800 hrs every day. Since this telnet issue began, I've seen the message "Grid square not set in Pat configure" displayed in Conky. I'm assuming the two problems are related. If I update the RMS list from the menu item, it updates correctly and no error message is displayed. The only things that have changed recently, were standard OS updates (sudo apt-update? and? sudo apt upgrade) BAP updates (updating those apps which were listed as having an update available). Julian |
The very tip drop down where it says select alias. As I recall you have to select telnet there and it will fill everything else out. From your picture, it looks like you did not do that. On Wed, Dec 15, 2021, 11:36 N3JF <n3jf@...> wrote:
|
On Wed, Dec 15, 2021 at 08:48 AM, Brian Dale wrote:
The very tip drop down where it says select alias. As I recall you have to select telnet there and it will fill everything else out. From your picture, it looks like you did not do that.Yikes!!! You know Jason's recent video about spending hours going round-and-round in circles, looking for something complicated, while ignoring the simple mistake? Yep... I was selecting telnet under "Transport" instead of under "Alias"! Selecting the correct telnet option got it working properly! Thank you Brian and Jason for your help! I still have the error coming up in Conky when Pat tries to update the RMS list, where it says "Grid square not set in Pat Configure". Not sure what could be causing that, as my grid square certainly is defined in pat configure. *** I've moved this question to a new post:?/g/KM4ACK-Pi/message/6647 Julian |
I'm glad I could fix your Telnet issue! Not sure about your other one. I'm on the way to the hospital again now and I think Jason is going to be out of commission for a few days so it might be a bit for some more help. To me it sounds like something might have gotten messed up in your PAT config file but I'll leave that one in Jason's good hands. 73 de AD4XJ (Brian) On Wed, Dec 15, 2021, 13:29 N3JF <n3jf@...> wrote:
|
On Wed, Dec 15, 2021 at 10:53 AM, Brian Dale wrote:
it sounds like something might have gotten messed up in your PAT configIn Jason's previous message, we reset the config file to defaults, then updated the call sign, password and grid square, so I don't think it's a problem with the config file. Hope everything is ok with you. Take care. Julian |
to navigate to use esc to dismiss