No, it's YAAC doing the Tx I-gating. Notice in the RF header the src>dst is yourcallsign>APJYC1. APJYC1 is the tocall assigned to YAAC. It's a "belt-and-suspenders" thing in YAAC that it specifies the no I-gating aliases when Tx-I-gating, even though Rx I-gates shouldn't forward a packet that already has a third-party header in it (i.e., came from APRS-IS).
Andrew, KA2DDO
author of YAAC
________________________________________
From:
[email protected] <
[email protected]> on behalf of Don via groups.io <donpjr@...>
Sent: Sunday, April 27, 2025 9:51 AM
To:
[email protected]Subject: Re: [yaac-users] RF Only NOGATE
I¡¯m using Direwolf without IG active. I have mycall and the Linux port in the Direwolf.conf only.
So the ¡°rfonly nogate¡± must be Direwolf message not YAAC.
Sent from Proton Mail<> for iOS
On Sun, Apr 27, 2025 at 09:05, Andrew P. via groups.io <andrewemt@...<mailto:On%20Sun,%20Apr%2027,%202025%20at%2009:05,%20Andrew%20P.%20via%20groups.io%20<<a%20href=>> wrote:
Ah, yes, thank you for reminding me to fix that. That says that WB9BLA-7 acknowledged your text message over the APRS-IS backbone, but you are Tx I-gating it on to local RF because it's a text message to a station heard locally (i.e., yourself). Kind of a weird corner case for Tx I-gating.
Now, the really weird thing is if you had received that acknowledgement text message over RF, should it still be Rx I-gated to the APRS-IS?
Andrew, KA2DDO
author of YAAC
________________________________________
From:
[email protected] <
[email protected]> on behalf of Don via groups.io <donpjr@...>
Sent: Sunday, April 27, 2025 8:33 AM
To:
[email protected]Subject: [yaac-users] RF Only NOGATE
Good day
I have IP online but see this:
W9JUN-10>APJYC1,TCPIP,W9JUN-10*,RFONLY,NOGATE:}WB9BLA-7>APN000,TCPIP,W9JUN-10*::W9JUN-10 :ackM0001
