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?