¿ªÔÆÌåÓý

Direwolf as receive only APRS-IS "client"


 

It is possible to configure Direwolf as a receive only client for data from an APRS-IS server? For example, APRSIS32 or AGWTracker can receive data from an APRS-IS server without connecting to a radio / tnc, etc. I'd like to use Direwolf in a non-RF mode for some development and testing.

Thanks,

Matt - N8SHA


 

I am not sure what your expectations are?
Receive only IGates are usually RF to IS.
It sounds like you want to go the other way - which really doesn't make a lot of sense.

With one of the 1.7 (C I think) updates, you can pass APRS traffic to an attached KISS or AGW device, if that is your question.

Rob KB8RCO


On Mon, May 30, 2022 at 8:59, Matthew Adair
<mladair@...> wrote:
It is possible to configure Direwolf as a receive only client for data from an APRS-IS server? For example, APRSIS32 or AGWTracker can receive data from an APRS-IS server without connecting to a radio / tnc, etc. I'd like to use Direwolf in a non-RF mode for some development and testing.

Thanks,

Matt - N8SHA


 

¿ªÔÆÌåÓý


Hello Matt,

It is possible to configure Direwolf as a receive only client for data from an APRS-IS server? For example, APRSIS32 or AGWTracker can receive data from an APRS-IS server without connecting to a radio / tnc, etc. I'd like to use Direwolf in a non-RF mode for some development and testing.

Sure, there are lots of ways to do that.? You can configure Direwolf to use use STDIN as it's input soundcard yet not sent it any data.? Depending on your chosen operating system, you can also configure it to use PulseAudio's "default" soundcard yet never assign a PA "sink" so Direwolf will never receive any audio bits.? There are other possibilities here but it depends on the OS you're running it on.

--David
KI6ZHD


 

Thanks David -
Turns out the main issues is that I forgot to set the filter for the server. doh! Set the filter and all that glorious traffic started appearing.

Unfortunately, I also discovered that the logging functionality of Direwolf apparently doesn't parse & log the incoming IS traffic like it does the pure RF traffic, which was I was ultimately hoping to achieve.
ah well...

Matt
N8SHA


 

I believe Direwolf V1.7C includes the ability to stream the APRS-IS channel througheither the KISSPORT.
If you are using that level, add this line to your direwolf.conf:
#############################################################
#?????????????? VIRTUAL TNC SERVER PROPERTIES?????????????? #
#############################################################
?? ?AGWPORT 8000
?? ?KISSPORT 8001
?? ?IChannel 15

NOTE: IChannel 15 will port any APRS-IS traffic that meets your criteria (filters) to KISSPORT 15.
You can then use the attached KISS client to log the information.

I used this with a friend filter to track some high altitude balloons (and activity around them).

Robert Giuliano
KB8RCO



On Tuesday, May 31, 2022, 09:52:19 PM EDT, Matthew Adair <mladair@...> wrote:


Thanks David -
Turns out the main issues is that I forgot to set the filter for the server. doh! Set the filter and all that glorious traffic started appearing.

Unfortunately, I also discovered that the logging functionality of Direwolf apparently doesn't parse & log the incoming IS traffic like it does the pure RF traffic, which was I was ultimately hoping to achieve.
ah well...

Matt
N8SHA


 

¿ªÔÆÌåÓý

But, since it is open source, you *could* provide your own modifications and re compile....

On 01/06/2022 11:52, Matthew Adair wrote:

Thanks David -
Turns out the main issues is that I forgot to set the filter for the server. doh! Set the filter and all that glorious traffic started appearing.

Unfortunately, I also discovered that the logging functionality of Direwolf apparently doesn't parse & log the incoming IS traffic like it does the pure RF traffic, which was I was ultimately hoping to achieve.
ah well...

Matt
N8SHA