Order Tray | Contact Us | Home | SIG Lists

[aprssig] Port 14580 Filter Bug? Or Is It Intentional?

Pete Loveall AE5PL Lists hamlists at ametx.com
Sun Jul 8 17:49:40 UTC 2012


This is correct operation, not a bug.  Port 14580 is an IGATE port.  It maintains a last-heard list of stations you have gated to APRS-IS and will present those stations back to you if they are heard directly on APRS-IS or if there is a message routed to that station and associated posits.

Remember, when you create a filter, you are saying "I want these things in addition to what is normally served up on this port".  Exception filters do not override the port's native functions.  An IGate port always passes to the client all message packets (and associated posits) addressed to that client or addressed to a station that has been recently gated to APRS-IS by the client.  It also passes to the client all packets from a station that was recently gated to APRS-IS by the client where those packets indicate they were directly injected into APRS-IS.  The reason for this last part is so an IGate can determine if as station heard on RF also has a direct APRS-IS connection and, therefore, the IGate does not need to gate to RF messages for that APRS-IS connected station.

73,

Pete Loveall AE5PL
pete at ae5pl dot net

> -----Original Message-----
> From: Stephen H. Smith
> Sent: Sunday, July 08, 2012 11:58 AM
> 
> The only common thread I can see is that stations I once heard on RF and
> igated
> *TO* the APRS-IS later come back *FROM* the IS if:   either their station is
> beaconing on both RF and Internet, or if they beacon with an identical
> callsign/SSID on VHF and enter the APRS-IS from another igate.    This
> happens
> sometimes hours after HF propagation has caused the station to fade out on
> HF.
>     It's not obvious this is happening when you just look at the map, but is
> very obvious when you look at the station details and see "Q" constructs and
> TCPIP components in the path.


More information about the aprssig mailing list