Direwolf _does_ do IS->RF, but your snooping client connected to DireWolf's AGWPE or KISS port is neither RF nor IS. Only RF-received traffic is sent to those ports, and traffic sent from your client over those ports only goes to RF, not to the Internet. If you want your client to receive (or send) Internet traffic as well as RF traffic, you'll have to connect the client directly to APRS-IS (not via DireWolf).
Andrew, KA2DDO
author of YAAC ("Yet Another APRS Client"), which frequently is used with DireWolf
-------------------------------------------------------------------------
From:
[email protected] <
[email protected]> on behalf of Rob Giuliano via groups.io <kb8rco@...>
Sent: Tuesday, November 30, 2021 10:33 AM
To:
[email protected] <
[email protected]>
Subject: Re: [direwolf] APRS-IS data over KISS TCP port
?
Charlie,
Thanks for the response.
I started out in Python and only getting data from the IS servers, but the group wanted 3 separate sources: VHF, UHF, and IS.
I guess they relied on IS before, and had issues when the payload dropped in a noncoverage area.
I was using Python, then C++ code to receive KISS packets from 2 hardware TNCs and IS when I thought using Direwolf and collecting the data over TCP might be easier.
I thought I had it all working with the RF data, but now that even stopped being received (or maybe just printed) by my app.
The intent is to have several of these Pi receivers around with directional antennas to more directly point at the location to increase the probability of being heard.
Another objective (as stated earlier) is to have a telescope or other visual device point during a night launch.
I am pretty sure I can get the RF side back working, but I don't understand why there is nothing from Direwolf receiving data from APRS-IS out of TCP/IP KISS.?
I would have thought that the IS->RF would have solved that.
Rob KB8RCO
