¿ªÔÆÌåÓý

  1. Direwolf
  2. Topics

OM>(callsign)

 

From time?to time I get a pop up on my FT5 from my direwolf igate/DiGi that has?
OM>(callsign)
It won¡¯t log to my station list or message list on the radio.

What is this?
Is there a way to filter this out either server or client side?
 

That is indicating your radio heard a message not addressed to you (other message). There should be an aprs menu option for disabling other message pop-ups on the FT5.

73, Brent WG0A
 

ahh thank you!
I was able to turn off the beep for this.

Can it be filtered out in direwolf?

On Wed, Aug 9, 2023 at 10:03?PM Brent WG0A <bjpetit@...> wrote:
That is indicating your radio heard a message not addressed to you (other message). There should be an aprs menu option for disabling other message pop-ups on the FT5.

73, Brent WG0A

 

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.



--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

 

makes sense, thank you!


On Tue, Aug 15, 2023 at 12:30?AM Geoffrey Merck <f4fxl@...> wrote:

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.



--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

 

¿ªÔÆÌåÓý

Yes, if you want to _see_ a filtered view of your traffic, use an APRS client like APRSIS32 or YAAC to monitor your Direwolf instance (through the AGWPE or KISS interface), and do the filtering in that program's user interface displays, not in the data stream flowing through your digipeater.

Direwolf's log output is really meant for debugging your Direwolf setup; it wasn't intended to be a tactical user interface.

The only good reason you would want to use excluding filters in a digipeater or I-gate is for deliberate blacklisting of an offensive station (such as the pirates getting on APRS-IS to send commercial or otherwise illegal traffic, where a transmit-capable I-gate operator wouldn't want to be liable for forwarding the pirate's packets to RF).

Andrew, KA2DDO
author of YAAC

From: [email protected] <[email protected]> on behalf of Russell, KV4S <russelljthomas@...>
Sent: Tuesday, August 15, 2023 8:57:27 AM

makes sense, thank you!

On Tue, Aug 15, 2023 at 12:30?AM Geoffrey Merck <f4fxl@...> wrote:

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.

--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

_._,_._,
_._,_._,_

1 - 6 of 6