Greetings.

I've been getting some strange problem reports from users of my YAAC software when connected to DireWolf, so I wanted to find out if this was a feature or a misconfiguration on their part, or whether they were just mistaken because there was no traffic to digipeat at the time.

They tell me that when DireWolf is configured to be a digipeater, but they then connect YAAC to DireWolf (they didn't say whether it was by the KISS port or the AGWPE port), then DireWolf stops digipeating. It still sends and receives packets just fine, but it doesn't automatically forward packets as it did when YAAC was not connected to it.

Is this actually a design feature of any recent version of DireWolf? Or are they just confused?

Andrew, KA2DDO
author of YAAC

开云体育

Hello Andrew,

This is the first time I've heard of this issue and without some additional details, logs, etc... people here on this list won't be able to help you.? Few questions that stick out in my mind:

?? - What hardware, OS, and OS version are they running this on
?? - What version of Direwolf?? Should be on v1.6 or maybe v1.7-Beta
?? - What version of YACC
?? - What version of the Java JVM
?? - How is YACC communicating to Direwolf?? serial emulation, TCP-KISS, AGW?

It's worth mentioning that you can ONLY communicate with Direwolf's internal AX.25 stack via AGW or TCP-KISS.? It's this internal stack that supports the UI-frame and I-frame digipeating function which are configured independantly.

--David
KI6ZHD

That's why I was asking if this was a known feature (of DireWolf assuming the attached client application is going to take over the digipeat logic). I haven't had a chance to actually test this myself, but I suspect the users were confused, per your statement of them not seeing the outgoing (digipeated) packet in YAAC, but only the original (incoming) packet. But I didn't want to make any blanket statements to them without checking with an authority such as the DireWolf author.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Rob Giuliano via groups.io <kb8rco@...>
Sent: Friday, September 24, 2021 11:31 AM
To: [email protected]
Subject: Re: [direwolf] Digipeating with a local client connected

I have used Direwolf (1.6 for sure) with other APRS clients, and Direwolf's DIGI function has not been affected as viewed on the computer terminal screen. I just confirmed this again.

So my question: How do they know that Direwolf is not DIGI'ing?
Many look at places like aprs.fi and don't see the digi'ed packet any more.
Of course if they are connected to the APRS-IS through YAAC,
then the DIGI'ed packet would never be saved.



Robert Giuliano
KB8RCO



On Friday, September 24, 2021, 11:22:36 AM EDT, David Ranch <direwolf-groupsio@...> wrote:



Hello Andrew,

This is the first time I've heard of this issue and without some additional details, logs, etc... people here on this list won't be able to help you. Few questions that stick out in my mind:

- What hardware, OS, and OS version are they running this on
- What version of Direwolf? Should be on v1.6 or maybe v1.7-Beta
- What version of YACC
- What version of the Java JVM
- How is YACC communicating to Direwolf? serial emulation, TCP-KISS, AGW?

It's worth mentioning that you can ONLY communicate with Direwolf's internal AX.25 stack via AGW or TCP-KISS. It's this internal stack that supports the UI-frame and I-frame digipeating function which are configured independantly.

--David
KI6ZHD



On 09/24/2021 06:35 AM, Andrew P. wrote:

Greetings.

I've been getting some strange problem reports from users of my YAAC software when connected to DireWolf, so I wanted to find out if this was a feature or a misconfiguration on their part, or whether they were just mistaken because there was no traffic to digipeat at the time.

They tell me that when DireWolf is configured to be a digipeater, but they then connect YAAC to DireWolf (they didn't say whether it was by the KISS port or the AGWPE port), then DireWolf stops digipeating. It still sends and receives packets just fine, but it doesn't automatically forward packets as it did when YAAC was not connected to it.

Is this actually a design feature of any recent version of DireWolf? Or are they just confused?

Andrew, KA2DDO
author of YAAC

--