¿ªÔÆÌåÓý

Re: Digipeating with a local client connected


 

I have a direwolf configuration on a Raspberry PI 3 with digipeating.? I configure APRSIS32 to connect to the Direwolf kiss port.

Digipeating is not enabled in the APRSIS32.

The system still digipeats?form the direwolf layer.

Connecting a client to the kiss port does not seem to disable digipeating.

On Fri, Sep 24, 2021 at 9:45 AM Andrew P. <andrewemt@...> 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






--

73,
AB1PH
Don Rolph

Join [email protected] to automatically receive all group messages.