pat ax25 prehook status

Nick Vanderest

unread,

Nov 12, 2024, 5:41:21 PM11/12/24

to pat-users

Just wondering what the current status of the prehook stuff was? Is it something that is working in 0.16.0 or to be officially enabled in a future version?

Thanks, Nick - VA7NIC

Martin Hebnes Pedersen

unread,

Nov 13, 2024, 2:15:20 AM11/13/24

to Nick Vanderest, pat-users

Hi Nick,

Low level support for added in v0.16.0. There is an example in the PR discussion: https://github.com/la5nta/pat/pull/432

A higher-level scripting language will probably be added in a future release, but we need feedback and real-world working scripts to work with :)

--
73 de LA5NTA / Martin

tir. 12. nov. 2024, 23:41 skrev Nick Vanderest <back...@gmail.com>:

Just wondering what the current status of the prehook stuff was? Is it something that is working in 0.16.0 or to be officially enabled in a future version?

Thanks, Nick - VA7NIC

--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/pat-users/e77e37f1-d03b-4cc0-8c08-23fbeae4b47cn%40googlegroups.com.

Nick Vanderest

unread,

Nov 13, 2024, 3:48:12 PM11/13/24

to pat-users

Great! Looking forward to giving it a spin once I figure out a couple simple things.

Based on the my-prehook.sh and command line pat connect string example in the pull thread you listed, what nodes are what? What node is in the connect string, and what node or nodes would go in the script?

In my current environment, I have access to a mountain top kantronics node digi which can provide me with paths to several gateways and even hop to another mountain top before I go down to gateways.

Thanks , Nick - VA7NIC

Nick Vanderest

unread,

Dec 9, 2024, 4:54:38 PM12/9/24

to pat-users

So the attemps to use the prehook to connect via a mountain node hasn't worked for me yet.

My setup: VA7NIC - I want to call VE7KU-8 (mountain top node) to connect to VA7BCE-10 (RMS gateway). There are also a few other gateways within RF ear shot of KU-8 so once the basic connection works, I can test to them as well.

Using the command line : pat connect 'ax25:///VE7KU-8?prehook=prehook.sh' will connect to VE7KU-8 which is our mountain top node, but doesn't seem to get any response back from the TNC that a connection was made.

I'm expecting a CONNECTED string like I can see if I manually connect to VE7KU-8. The script just loops through, waiting for the expected text, not receiving it, then waiting some more in the preset delay.

Trying the connection using an AGWPE interface in a windows VM (trying to see if perhaps the linux ax.25 stack is causing part of the problem) with the command line of

pat connect 'ax25+agwpe:///VE7KU-8?prehook=prehook.sh' comes back with a date/time string and AGWPE TNC initialization failed: callsign in use

A normal ax25+agwpe connection in the GUI to the gateway works flawlessly 10 times out of 10.

Here is my prehook.sh

#!/bin/bash
set -x
function wait {
local timeout=$1 keyword=$2 line=""
while [[ $line != $keyword ]]; do read -t $timeout -r line; done
}
function print {
shift
echo "${@}\r"
}
wait 10 CONNECTED
print 'c VA7BCE-10'
wait 10 VA7BCE-10

I've also tried a few attempts to add single quotes around various strings to make sure they get sent properly. If I have print c VA7BCE-10 as the first line, the output of the script on screen doesn't include the c

The current TNC in use in a AEA/Timewave PK-96 in KISS mode. The tnc in a windows enviroment with RMS Express doing the digi connection works going through VE7KU-8 to VA7BCE-10. I don't think its the problem.

I currently have pat running on the latest raspbian enviroment on a Pi4, could that be part of the problem? I haven't had a chance to create a test enviroment on my server machine yet. Perhaps that is this afternoons adventure, but would really like it all on the RPi, then its a bit more portable in a grab 'n go setup.

Nick

Nick Vanderest

unread,

Dec 23, 2024, 6:01:49 PM12/23/24

to pat-users

Just a quick update, the issue with the AGWPE and callsign in use I reported earilier could be a AGWPE issue. If you exit and restart AGWPE you can access it with whatever client and not get that callsign issue until you try from another client again. I tried working with the prehook stuff again, and get the same sort of results, where whatever communication from the TNC/PE are not making it back to the prehook script.

Looking forward to some direction on things to try or test.

Thanks,

Nick

Martin Hebnes Pedersen

unread,

Dec 26, 2024, 5:39:08 AM12/26/24

to Nick Vanderest, pat-users

Hi Nick,

Can you please share the log output from Pat? A full dump of the packet conversation from direwolf would also be handy in order to debug this.

Thank you!

--

73 de LA5NTA / Martin

To view this discussion, visit https://groups.google.com/d/msgid/pat-users/0669fe2c-3047-4b65-ae00-7715943d569en%40googlegroups.com.

Nick Vanderest

unread,

Jan 1, 2025, 4:44:32 PMJan 1

to pat-users

I'll have to give you a raincheck on that debug info. Seems our mountaintop site has some snow and it is affecting our packet digi a touch.

Once we get a good shot of sunshine up there I will pickup where I left off.

Nick

Incredible Budget

unread,

Jan 8, 2025, 12:28:56 AMJan 8

to pat-users

Incredible Budget

unread,

Jan 8, 2025, 12:29:36 AMJan 8

to pat-users

Reply all

Reply to author

Forward