ua1zbe
/
aprsc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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
This commit is contained in:
Kenneth Finnegan 2017-08-09 18:25:37 -07:00
parent 7794d807ec
commit ef2350b467
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/IGATE-HINTS.md
View File

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