[aprssig] IGate Registering for ANSRVR (Messaging failures)

Steve Dimse steve at dimse.com
Sat Jul 16 06:05:26 EDT 2016

> On Jul 16, 2016, at 3:16 AM, SARTrack Admin via aprssig <aprssig at tapr.org> wrote:
> Hmm,
> I have not looked at my SARTrack code in this area for years, but SARTrack will simply send all incoming data from RF to the APRS-IS network, after checking for duplicate packets.
> Once a station is heard on RF in the last 30 minutes, regardless of what is send, SARTRack will accept any Messages directed to that station (after checking for Duplicates) and transmit it on RF.
> SARTrack can also be used as a fill-in Digipeater but it will display a big warning to the end-user on the consequences of this.
> I hope this is the right behaviour...

Pretty close, ideally you should be checking for how the station was heard: direct, one hop, two hops, etc, and only IGate traffic to those within however many hops your output is configured to send outgoing packets. You might also raise the timeout from 30 minutes. If a station only beacons every 30 minutes there will be a loss of coverage for those 30 minutes every time a packet is not heard by you. Two hours is probably better. Stations that leave your network still time out pretty quickly and there is less risk of not IGating something you should have.

Steve K4HG

More information about the aprssig mailing list