I hate to bump an old topic, but a solution was never posted. I was looking for an answer to the same question, but only to avoid using kissattach as part of the pat startup process.
The answer is to run direwolf with the -p flag:
$ direwolf -p
....
The answer is to run direwolf with Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/4
Created symlink /tmp/kisstnc -> /dev/pts/4
....
The you must run kissattach:
kissattach /dev/pts/4 wl2k
Assuming the relevant alias and config in config.json:
kissattach /dev/pts/5 wl2k
"connect_aliases": {
...
"ax25test": "ax25:///{mycall}"
},
...
"ax25": {
"port": "wl2k",
"beacon": {
"every": 3600,
"message": "Winlink P2P",
"destination": "IDENT"
},
"rig": ""
},
~$ pat connect ax25test
2021/04/29 16:40:22 Connecting to KF6IIU (ax25)...
~$ pat connect ax25:///K6SOL-5
2021/04/29 16:42:17 Connecting to K6SOL-5 (ax25)...
etc