From ef2350b46792082ae879d6eef737c8f50c46d4cc Mon Sep 17 00:00:00 2001 From: Kenneth Finnegan Date: Wed, 9 Aug 2017 18:25:37 -0700 Subject: [PATCH] Clarify What I-Gates should do with duplicate packets Make it exceedingly clear that I-gates should send *all* heard packets to the APRS-IS except those excluded by NOGATE/RFONLY --- doc/IGATE-HINTS.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/IGATE-HINTS.md b/doc/IGATE-HINTS.md index dd25cfb..bf2ce4b 100644 --- a/doc/IGATE-HINTS.md +++ b/doc/IGATE-HINTS.md @@ -124,9 +124,12 @@ do improved APRS message routing based on this information. ***Solution:*** Do not implement duplicate packet filtering in an RX igate (RF > APRS-IS). -Duplicate filtering only needs to be done when digipeating. When doing TX -igating (APRS-IS > RF) you might prefer to have a rate limit instead to -prevent too many packets being sent overall, even if they are different. +Send all locally received packets to the APRS-IS except when +`NOGATE` or `RFONLY` is found in the packet's path. +Duplicate filtering only needs to be done when preparing to transmit packets +for digipeating. When doing TX igating (APRS-IS > RF) you might prefer +to have a rate limit instead to prevent too many packets being sent overall, +even if they are different. iGates not supporting DNS