[aprssig] IGate FIlter for AMSATS?

[Jess Haas]

Looks like Direwolf igates immediately for digipeated packets but holds
direct packets(10 sends by default) before igating when in satgate mode.
The manual also has an example of how to simply drop direct packets heading
to a satelitte.

>From the manual(https://github.com/wb2osz/direwolf/blob/master/
doc/User-Guide.pdf):

9.9.5 SATgate mode
If we hear a packet directly and the same one digipeated, we only send the
first to the APRS IS due to
duplicate removal. It may be desirable to favor the digipeated packet over
the original. For example,
you might be more interested in packets that have been forwarded by
satellites rather than heard
directly. For this situation, we have an option which delays a packet if we
hear it directly and the via
path is not empty.
When using this option, the digipeated packets will go to the server
immediately. The original, heard
directly, is sent after a delay, typically 10 seconds. Duplicate removal
will drop the original if there is a
corresponding digipeated version.
The configuration option for this feature is:
SATGATE
You can optionally add a delay time in seconds. The default is 10.
You can find more discussion here: http://www.tapr.org/pipermail/
aprssig/2016-January/045283.html

On Feb 24, 2017 6:35 PM, "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
wrote:

> Actually, I think the discussion was to implement an IGate mode whereby it
> would never gate a directly received packet, one with no used path
> components.  Time delaying before gating is a disaster waiting to happen
> IMHO.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 2/24/2017 3:08 PM, Jess Haas wrote:
>
> I havent used it but Direwolf has a mode to attempt to solve this problem.
> If I remember correctly it has a satgate mode that instead of immediately
> gating packets holds on to them to give the satelitte a chance to digipeat
> and then prioritizes the digipeated packet. If none is heard i believe it
> will still igate the original.
>
> -Jess
> KM6GVW
>
> On Feb 24, 2017 10:19 AM, "Robert Bruninga" <bruninga at usna.edu> wrote:
>
>> I should know this…
>>
>>
>>
>> Basics:   Igates pass all packets heard to APRS-IS, but all after the
>> first are filtered out as DUPES
>>
>>
>>
>> Problem:  Satellite operators in simplex range of an IGate will almost
>> always show the first packet (uplink) and not the DESIRED successful
>> downlink digipeated Satellite copy.
>>
>>
>>
>> Question (sorry I forgot the answer last time):  Where do we fix this.
>>
>>
>>
>> I want to finally build us an IGATE here at the Academy in Maryland, but
>> I don’t want it to then filter out all of our satellite packets that get
>> digipeated!  I am totally dependent on FINDU.COM and the APRS-IS to
>> capture and log all APRS Satellite Telelmetry and user packets including
>> ours and nearby locals.
>>
>>
>>
>> Bob
>>
>>
>>
>>
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
>>
>>
>
> _______________________________________________
> aprssig mailing listaprssig at tapr.orghttp://www.tapr.org/mailman/listinfo/aprssig
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170224/61b5174c/attachment.html>