[aprssig] IGate Registering for ANSRVR (Messaging failures)

[Pete Loveall AE5PL Lists]

javAPRSSrvr (internal IGate client) has always used only number of hops as the criteria (direct is, of course, zero hops) for gating to RF.  There is no dependency on type of packet.  One caveat to reduce needless gating (QRM) to RF: when the station has been heard directly on APRS-IS (TCPIP* as path), javAPRSSrvr will not try to gate to it on RF.  Both the local and heard-on-APRS-IS lists are timed lists.  Number of hops and length of time the lists hold their information is adjustable for local conditions.

Yes, there is some IGate software out there (I never tried to track which software) that uses "nearby" as a criteria instead of "recently heard within N hops".  Also, remember that some people are running "receive-only" IGates which completely break the messaging functions of APRS-IS IGates.  Receive-only IGates are at best worthless and at worst breaking messaging.

73,

Pete Loveall AE5PL
pete at ae5pl dot net

> -----Original Message-----
> From: Lynn W. Deffenbaugh (Mr) via aprssig
> Sent: Friday, July 15, 2016 10:12 AM
> Subject: Re: [aprssig] IGate Registering for ANSRVR (Messaging failures)
> 
> I can only state with conviction that APRSISCE/32 considers a station
> "recently" "local" based on 30 minutes and at most 2 hops used (although
> the calculation of that is interesting with stations originating WIDE2-1
> in a path, is that one used or was it originally that way?).  Eventually
> these will be configurable, but for now, they're hard-coded.  You can
> 
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> 
> PS.  If anyone can speak authoritatively on what criteria the other
> IGate software uses for gating messages from the APRS-IS to RF, I'd be
> all ears... er eyes and would love to be corrected or confirmed in my
> recollection that one of them can consider distance rather than used hops.