[aprssig] Question about APRS-IS and IS->RF igating

[Pete Loveall AE5PL Lists]

Multiple things occur at the server on filtered ports that are configured to handle IGates (most 14580 ports).  I will focus on this as an IGate connected to a user-filter port with no filter set.

After initial verified login, the server will only pass messages and associated posits to the client (IGate).

Each station gated to the server by the client (stations heard on RF) are added to a "recently heard" list which is good for about an hour on most servers but is adjustable.  This recently heard list is a moving window list (in other words, every time a station is "heard" from the client, its position on the list is updated).  That list is used for two things: passing messages and associated posits to the client for possible gating to RF AND passing any packets heard from recently heard list stations that were injected directly on APRS-IS (TCPIP* as the path).  This is so the IGate can determine if there is a station it is hearing on RF is also directly connected to APRS-IS.  If the RF station is heard directly on APRS-IS, the IGate should NOT gate messages for that station to RF.

Sounds like your APRS4R software is buggy and not following the specifications for IGates at www.aprs-is.net if it is gating everything heard on the APRS-IS feed to RF.

73,

Pete Loveall AE5PL
pete at ae5pl dot net



> -----Original Message-----
> From: Lynn W. Deffenbaugh (Mr)
> Sent: Thursday, May 17, 2012 10:53 AM
> 
> On 5/17/2012 11:43 AM, Phil N6TCT wrote:
> 
> 
> 	We have a bidirectional igate, GERLCH, out in the Nevada desert.  It's
> running aprs4r under linux.
> 
> 
> 	My question:  Why would our igate be getting this message from
> APRS-IS?  Is it because we just gated a message to APRS-IS from this station?