Jim, I already have a filter on what goes to APRS-IS, and that works well. ? Note to everyone, 50 km is a decent range, but definitely anything beyond 300 km is completely bogus. ?Just about everyone receives something from thousands of miles away from defective trackers, so a filter on the To IS is good. Arnold KQ6DI From: "Jim Alles kb3tbx@... [direwolf_packet]" To: "direwolf packet" Sent: Thursday, November 17, 2016 12:16:24 PM Subject: Re: [direwolf_packet] Rx only iGate - stop Tx data Yes, there are two issues here. I have recently been testing Direwolf for this. you can limit what you send to the APRS-IS, by putting in a filter like this in the config file: "FILTER 0 IG ? r/40.8/-77.8/50 ?| t/m " APRS-IS will only receive position packets within 50 km of some point near me, and messsages that might come from anywhere. This will trap the stray packets that you might get by ducting, for example. That will minimize what is sent to direwolf to decide what to do with messages. In my experience, you can also reduce the incoming data flow but logging into an APRS-IS server that uses aprsc software - it seems to be more conservative. YMMV. 73,? Jim A. On Thu, Nov 17, 2016 at 2:33 PM, kq6di@... [direwolf_packet] <direwolf_packet@...> wrote:
|