[aprssig] APRS-IS: frames bypassing server filter

Pete Loveall AE5PL Lists hamlists at ametx.com
Wed Jul 15 12:10:22 EDT 2020

Stephen, I gave you 3 methods to do not receive packets from APRS-IS for gated stations today: use UDP or HTTP send-only ports, or use port 14580 on the Firenet servers.  Since you "have to" receive a packet to a rx-only IGate (satellite object), #3 is your solution.


Pete Loveall AE5PL
pete at ae5pl dot net

-----Original Message-----
From: aprssig <aprssig-bounces at lists.tapr.org> On Behalf Of Stephen H. Smith via aprssig
Sent: Wednesday, July 15, 2020 10:57 AM
To: TAPR APRS Mailing List <aprssig at lists.tapr.org>
Subject: Re: [aprssig] APRS-IS: frames bypassing server filter

On 7/15/2020 10:50 AM, Pete Loveall AE5PL Lists via aprssig wrote:

> If you don't want to see packets originated by stations heard on RF by your IGate (i.e. don't want to support messaging), you may be able to disable the gate capability in your client, change to using a send-only port (UDP or HTTP), or connect to a FIRENET port 14580 which do not support bidirectional IGates.  In all cases, we will know if your IGate is messaging to RF and other IGates will know your station has APRS-IS connectivity (so therefore will not gate to RF messages for your client).

But this still doesn't solve the problem of the original poster, which was to 
stop APRS-IS-to-IGATE traffic.   Even if he chooses to not transmit this data 
back to RF, it's still burning up his limited cellular data quota getting from the APRS-IS to his shack.

Is there ANY way to do this?

More information about the aprssig mailing list