[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: AX25 support in `pat` package



Direwolf uses ax25? I don't think I ever went that route.
I did update this howto after upgrading Ubuntu:
https://howtotrainyourrobot.com/pat-winlink-ft70-and-handheld-mobilinkd-tnc/


From: Tyler Schwend <tylerschwend@gmail.com>
Sent: Monday, June 13, 2022 5:40 AM
To: Paul Tagliamonte <paultag@debian.org>
Cc: tony mancill <tmancill@debian.org>; Federico Grau <donfede@casagrau.org>; Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Subject: AX25 support in `pat` package
 
Thank y'all for this. I assume it will come out in testing before too long.

The pat->direwolf route is pretty rough right now. When wl2k-go and Pat support KISS (https://github.com/la5nta/wl2k-go/issues/56) or AGW over TCP (https://github.com/la5nta/wl2k-go/issues/57) it will get easier, but for now we have to use the pretty bad AX25 stack in Linux, which has at least one annoying-enough-to-be-broken issue that I encounter (https://github.com/la5nta/pat/issues/352).

Here's what I run when I do this:

#Launch direwolf with my stripped down configuration to avoid attempts at digipeating
direwolf -p -c direwolf-pat.conf
#Attach an AX25 port to the kiss port that Direwolf exposes. Existing required configuration in /etc/ax25/axports
sudo /usr/sbin/kissattach `ls -l /tmp/kisstnc | awk '{ print $11 }'` direwolf 192.168.90.1
#Set some params on the `direwolf` AX25 port to keep Direwolf happy
sudo kissparms -c 1 -p direwolf

And then I can connect via AX25 in Pat.

Y'all's work on this repackaging will at least keep me and others from having to manage a separate source of packages just for the AX25 support.

Thanks again!

On Sunday, June 12, 2022, Paul Tagliamonte <paultag@debian.org> wrote:
> That looks configured correctly!
>
> The trick is to configure ax25 next - in particular, here, you'll want to set up /etc/ax25/axports - and to kissattach to your TNC / direwolf.
> Regardless, that build looks to have taken the go build flag correctly, in either case!
>
>   Paul K3XEC
> On Sun, Jun 12, 2022 at 12:19 PM tony mancill <tmancill@debian.org> wrote:
>>
>> On Sun, Jun 12, 2022 at 11:10:38AM -0400, Federico Grau wrote:
>> > On Sat, Jun 11, 2022 at 08:06:51PM -0700, tony mancill wrote:
>> > > On Sat, Jun 11, 2022 at 07:53:47PM -0700, tony mancill wrote:
>> > > > However, I don't have good way to test it fully, so feedback on whether
>> > > > it works with AX25 is appreciated.
>> > >
>> > > I see that the CI job for the crossbuild has failed in the past, but my
>> > > upload has also impacted the reproducible build.  I'll have to look into
>> > > that.
>> >
>> > Thanks for the pushes again Tony,
>> >
>> > Adding to this thread some debugging info Tyler had shared OOB.  I've yet to
>> > get to a point where I can dig into this deeper, but am tracking it.
>> >
>> >
>> >     On Wed, Jun 08, 2022 at 10:03:56PM -0400, Tyler Schwend wrote:                                                                                             
>> >     > user@system:~$ dpkg -s pat | grep Version
>> >     > Version: 0.12.1-2+b1
>> >     > user@system:~$ pat-winlink connect ax25:///W4ABC-10
>> >     > 2022/06/08 22:01:30 Connecting to W4ABC-10 (ax25)...
>> >     > 2022/06/08 22:01:30 Unable to establish connection to remote: AX.25 support
>> >     > not included in this build                                                                                                                               
>> Thank you for the test sequence.  After running `pat-winlink configure`
>> to configure my callsign, the new version output is:
>>
>> $  dpkg -s pat | grep Version
>> Version: 0.12.1-3
>>
>> $ pat-winlink connect ax25:///W4ABC-10
>> 2022/06/12 09:15:05 Connecting to W4ABC-10 (ax25)...
>> 2022/06/12 09:15:05 Unable to establish connection to remote: No AX.25 ports configured
>>
>> Since I am completely unfamiliar with winlink, I won't be able to
>> experiment further until I learn more about it (starting here:
>> https://www.winlink.org/user).
>>
>> Cheers,
>> tony
>
>
> --
> :wq

Reply to: