From:[email protected] <[email protected]> on behalf of Andrew P. via groups.io <andrewemt@...>
Sent:?November 30, 2024 20:05
To:[email protected] <[email protected]>
Subject:?Re: [yaac-users] YAAC and Direwolf interfacing

Yes. When you try to open one of those ports, YAAC is trying to connect to the software TNC. If the software TNC is not running, there will be nothing for it to connect to. So Direwolf needs to be started _before_ YAAC is started.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...>
Sent: Saturday, November 30, 2024 7:51 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC and Direwolf interfacing

Hi Neil

I tried opening a kiss over tcp port following your example but when I tried to create the port, the attempt fails with a java connection refused message.? Do I have to hae direwolf running at the same time?? I get the same result trying agwpe.? I don't have direwolf running at the moment.

________________________________
From: [email protected] <[email protected]> on behalf of Neil Hanlon <neil@...>
Sent: November 30, 2024 15:51
To: [email protected] <[email protected]>
Subject: Re: [yaac-users] YAAC and Direwolf interfacing

Hi Joe,

There are a couple ways to accomplish this. As you mentioned, AGWPE is one option, KISS is another; Direwolf supports both.

The default direwolf configuration should listen on both ports 8000 (AGWPE) and 8001 for KISS. In YAAC, all you need to do is choose the option you want, and set the hostname and port in the fields

Attached a couple screenshots of my AGWPE and KISS configurations:

KISS:
[Screenshot_20241130_153458.png]

AGWPE:

[Screenshot_20241130_153422.png]

Note that DireWolf will only send to KISS/AGWPE what it hears over RF *only*. If another AGWPE/KISS client connects and sends, OR if DireWolf is configured as an iGate, these messages will not be relayed into YAAC by default. To do so, you would need to add a configuration like this to direwolf.conf:

ICHANNEL 15 # Define an internal direwolf channel 15 which should receive APRS-IS traffic
KISSCOPY # Enable copying traffic to/from KISS ports
KISSPORT 8001 # Default listener on 8001
KISSPORT 8015 15 # Assign port 8015 to ICHANNEL 15

Then, you can configure a KISS port in YAAC on this port to hear IS messages forwarded from YAAC.

I hope this helps, Joe. Please let me know if you need any clarification on anything.

---

One thing I still have not yet figured out, and would appreciate others' expertise here, is a peculiarity I've discovered regardless of if I have DireWolf or YAAC or Both configured as iGates:

When sending some messages to a station not in range of me, the station correctly routes the ACK to my station via IS, however when YAAC receives this reply (and TX is turned off on the IS port), the ACK over RF is sent without the original message's digipeater path, leading to a situation where my station won't acknowledge messages heard via RF. I'm not sure if this is a knob I need to turn (or make) in YAAC or DireWolf or both, but it definitely feels like I'm missing something...

To elaborate further, I primarily want to use RF instead of IS, but if a message ack is heard over IS, either respond via IS to the ack *or* (preferably) use the same digipeater path to acknowledge the message as it was sent with.

73,
Neil N1HAN


On Sat, Nov 30, 2024 at 1:15?PM Joseph LaFerla via ?<joe@...<mailto:[email protected]>> wrote:
HI all

I have been running yaac for a long time with a TNC-Pi2 on my rpi3 and a Kenwood TMD710G.? I have recently had to ditch the tnc and have been looking at replacing it with direwolf.?? I have a working configuration using direwolf 1.7 and a digirig into my Baofeng handheld.? I want to make this work with my kenwood mobile TMd710G.? I am thinking that most of my current configuration will work. I don't think that my digirig would work.? I have read somewhere that I need to setup an AGWPE port.?? Can anyone help please?

Thanks in advance

Joe VA3TV