<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I assume you're referring to
<a class="moz-txt-link-freetext" href="http://www.aprs-is.net/IGateDetails.aspx">http://www.aprs-is.net/IGateDetails.aspx</a> which allows for<br>
<br>
<blockquote type="cite"><span style="color: rgb(0, 0, 0);
font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">Gate all
packets to RF based on criteria set by the sysop (such as
callsign, object name, etc.).</span></blockquote>
<br>
In my APRSISCE/32, I support an APRS-IS-style filter setting where
the matching packets will be gated from the APRS-IS to local RF.
This is currently only available in my development version, is not
persistent (must be re-established on each restart), and is a
two-step process. The first step is to hit Control-G to specify
the filter into a "FilterTest" window that I support. Once that
is accomplished, a Control-I confirms that the user intends to
gate the filtered packets to local RF.<br>
<br>
My design goal is to keep the filter spec to select the packets to
forward but to allow multiple filters, make them persistent across
restarts, and implement a "Leaky Bucket" to throttle the packets
flowing through each filter and a composite for each RF port.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
PS. My internal filter implementation adds a "+" qualification on
a term. Similar to how "-" eliminates packets from passing a
filter, my "+" requires that the term be matched to pass. This
implements a sort of "AND" similar to the "AND NOT" of the minus.
Of course, as we all know, non-qualified terms are "OR". For
instance:<br>
<br>
b/KJ4ERJ-12 +m/10 would only gate my Android phone's packets to RF
IF I was within 10 km of the IGate. Without the + modifier,
there's no way in the standard filters to accomplish this.<br>
<br>
<br>
On 6/15/2017 10:00 AM, spam8mybrain wrote:<br>
</div>
<blockquote type="cite"
cite="mid:bhqb3un3hoj7x4hq2rj4mprb.1497535258350@email.android.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Greetings, all.
<div><br>
</div>
<div>Some time ago, there was a thread discussing what a Tx I-gate
should and should not forward to RF. The aprs-is.net website
clearly documents the minimum allowed and prohibited traffic,
but does not say anything about optional forwarding.</div>
<div><br>
</div>
<div>What do other I-gating applications do to control extra
I-gate-operator-approved forwarded traffic, and how do you let
the control operator specify what extra is allowed?</div>
<div><br>
</div>
<div>The reason I ask is that I've gotten some questions about my
application YAAC, regarding why it isn't forwarding
geographically local Internet-only stations to RF. YAAC
presently only supports the minimum forwarding (Internet traffic
explicitly addressed to RF-local stations, and one subsequent
position report from those specific Internet stations). I'm
trying to figure out how to sanely and safely allow operators to
specify additional traffic so they can't accidentally specify
dumping the entire APRS-IS feed to RF.</div>
<div><br>
</div>
<div>Any suggestions or descriptions on how other I-gates do it
would be welcome.</div>
<div><br>
</div>
<div>Andrew Pavlin, KA2DDO</div>
<div>author of YAAC</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>