[aprssig] IGATE message routing bug?

[Jim Alles]

"​
Is it the failure of some local IGates or is it some kind of filtering
issue in the APRS-IS.

Where do we fix this?"

Bob,
I wish I didn't have to do this:

It is in the IGate design document http://www.aprs-is.net/IGateDetails.aspx
<Gating Criteria>

The following is the basic criteria for what an IGate gates to/from RF.

Gate message packets and associated posits to RF if all of the following
are true:

   1. the receiving station has been heard within range within a predefined
   time period (range defined as digi hops, *distance*, or both).

</Gating Criteria>
but don't throw the baby out with the bath water!

Folks, I am seeing a real issue ({on this list} and {in the documents we
depend on}) with ambiguous language adding confusion to discussions about
an already complicated system.

This is not hit-and-run criticism, I intend to make some suggestions under
a different topic. I do intend to disrupt the "but we've always done it
this way" thinking, however.

Also, please be patient.

73,

Jim Alles
KB3TBX
Penn State Amateur Radio Club (K3CR)

On Fri, Jul 15, 2016 at 10:27 AM, Robert Bruninga via aprssig <
aprssig at tapr.org> wrote:

> In preparation for the Golden Packet event, a few of us noticed that we
> were not getting ANY messages into or out of the ANSRVR or CQSRVR.
>
>
>
> Turns out, the local IGates or APRS-IS were not recognizing our stations
> (as being local) until/unless the message station first sent a position
> report.
>
>
>
> Please  confirm that this is not a huge bug in APRS-IS behavior that does
> not recognize an APRS station (in the IGate/APRS-IS system) unless and ONLY
> IF it sends a valid position report.  This is not how APRS messaging is
> supposed to work.  There should not be any dependence on a position report
> for 2-way messageing to work.
>
>
>
> ​​
> Is it the failure of some local IGates or is it some kind of filtering
> issue in the APRS-IS.
>
>
>
> Where do we fix this?
>
>
>
> Thanks
>
> Bob
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161116/5f7608d1/attachment.html>