[aprssig] IGate Registering for ANSRVR (Messaging failures)

Lee Bengston lee.bengston at gmail.com
Sat Jul 16 07:49:54 CDT 2016


On Sat, Jul 16, 2016 at 6:05 AM, Steve Dimse via aprssig <aprssig at tapr.org>
wrote:

>
> > 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
>

‚ÄčAlso IGate software needs to determine if a station heard on RF in the
last 30 minutes‚Äč was also heard via the Internet.  If yes, then it
shouldn't gate the message to RF because that station already got the
message via the Internet.

Lee - K5DAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20160716/9c8b648e/attachment.html>


More information about the aprssig mailing list