<div dir="ltr">I can't say with confidence what APRX does off the top of my head, but I agree that it *should* be RF-gating based on seeing any type of packet from a station come in on an interface. I'll need to ensure that that is the default behavior.<div><br></div><div>That being said, APRX supports geographical filtering so it's possible for users to configure APRX to be more restrictive with its RF-gating based on distance, inside a rectangle, etc. Seeing an instance of APRX in the wild which doesn't behave like we're discussing may be a deliberate configuration choice by the operator.<br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">--<br>Kenneth Finnegan<br><a href="http://blog.thelifeofkenneth.com/" target="_blank">http://blog.thelifeofkenneth.com/</a></div></div>
<br><div class="gmail_quote">On Fri, Jul 15, 2016 at 8:12 AM, Lynn W. Deffenbaugh (Mr) via aprssig <span dir="ltr"><<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm going on memory which is known at times to be faulty, but I believe there is at least one IGate implementation that can be configured to consider "local" to be based on distance. But I also believe it to be true that some IGates require hearing a position packet, not just any packet, in order to consider a station available for gating messages from APRS-IS to RF for that station. I could be worng (sic) on both counts.<br>
<br>
I can only state with conviction that APRSISCE/32 considers a station "recently" "local" based on 30 minutes and at most 2 hops used (although the calculation of that is interesting with stations originating WIDE2-1 in a path, is that one used or was it originally that way?). Eventually these will be configurable, but for now, they're hard-coded. You can see the settings in an APRSISCE/32 instance by double-clicking the narrow vertical bar immediately to the right of the map. it will show the following information:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Close Stations<br>
<snip><br>
30 via RF (9 Direct 18 Local)<br>
IStoRF: 2 hops in 30 minutes<br>
</blockquote>
<br>
If you want to see just the stations considered "Local", use View / None followed by View / RF / Local. Or you can send a ?APRSL query to an APRSISCE/32 IGate and it will respond with a list of all currently "Local" stations as defined for gating messages from the APRS-IS to RF. Note that this query is best done via the APRS-IS as the list can be fairly long. A ?IGATE query will return the count of local, direct, and RF stations. This information is also periodically transmitted in an IGate status packet.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
PS. If anyone can speak authoritatively on what criteria the other IGate software uses for gating messages from the APRS-IS to RF, I'd be all ears... er eyes and would love to be corrected or confirmed in my recollection that one of them can consider distance rather than used hops.<div class="HOEnZb"><div class="h5"><br>
<br>
On 7/15/2016 10:50 AM, Robert Bruninga via aprssig wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In any case, most IGates must have received a position packet<br>
from a station "recently" and consider it "close" enough<br>
before messages will be gated from the APRS-IS for it.<br>
</blockquote>
WHAT!!??? This totally breaks APRS as a messaging system. Where did this<br>
come about. It also breaks vicinity tracking, another very powerful APRS<br>
capability.<br>
<br>
There are MANY times and certainly in times of stress and emergency and<br>
backup comms when a position is not possible or easy. How did this creep<br>
into the APRS system?<br>
<br>
How do we fix it?<br>
<br>
The criteria for IGateing back to RF is "LOCAL" meaning only that the<br>
station was heard DIRECT or on the first hop. (though this can be a<br>
variable in remote areas)..<br>
<br>
Bob<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" rel="noreferrer" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" rel="noreferrer" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br></div></div></div>