<div dir="ltr">What would it take to change this behavior so that RX-only iGates with metered data connections can avoid consuming this unwanted & expensive data?<div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Kind Regards,<br><br>Rob Riggs WX9O<br>Mobilinkd LLC<br></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 14, 2020 at 6:35 PM spam8mybrain via aprssig <<a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>The purpose of the minimal data stream is so your Internet-connected station can function as a transmit-capable I-gate, not just a receive-only I-gate. The minimum packets you receive from the Internet are those intended for stations that your I-gate has delivered to the backbone, under the assumption that your I-gate is one of the nearest stations to send responses back to the RF station. The assumption is, if you can hear them on RF, you can send back to them on RF (and the backbone doesn't understand the concept of I-gates that can't, so you can't turn off such IS->RF traffic).<div>
<div dir="auto"><br></div><div dir="auto">The backbone sends such packets to all such I-gates that report receiving the RF stations, to ensure a redundant path to get to the RF station. After all, not all I-gates may be capable of transmitting at the time of packet receipt and getting all the way to the RF station (especially if the RF station is mobile and has moved since the last RF->IS-forwarded packet from it).</div><div dir="auto"><br></div><div dir="auto">Hope this helps explain this design decision of the backbone servers.</div><div dir="auto"><br></div><div dir="auto">Andrew, KA2DDO</div></div><br><br>-------- Original message --------<br>From: Wojtek SP9WPN <<a href="mailto:sp9wpn@gmail.com" target="_blank">sp9wpn@gmail.com</a>> <br>Date: 7/14/20 18:14 (GMT-05:00) <br>To: <a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a> <br>Subject: Re: [aprssig] APRS-IS: frames bypassing server filter <br><br>W dniu 2020-07-14 o 00:12, Lynn W Deffenbaugh (Mr) wrote:<br>> You will receive packets generated by any station that you have gated <br>> from RF to the APRS-IS for some period of time after you've last gated <br>> one of their packets. Try matching up the stations you're receiving <br>> with the packets being subsequently received back from the APRS-IS.<br><br>I'm not sure about this. Most of the stations in question are not heard <br>directly, but only digipeated to me. This shouldn't count, should it?<br><br><br>> This is done for several reasons. One is to give you the opportunity <br>> to gate a "courtesy" posit for the source of any message you may have <br>> gated, but it is also so that your IGate can know if a staiton is <br>> injecting packets directly to the APRS-IS so you don't gate messages <br>> from the -IS to RF for addressed to a station that would have received <br>> them directly on the APRS-IS.<br><br>Is this true for non-message packets, too? Because I hardly ever see <br>APRS messages in the logs, just beacons and telemetry all the time. If <br>APRS-IS server sends packets downstream only to stop me from uploading <br>the same packets back, it sounds like a weird protocol design...<br><br><br>I'd agree with Andrew KA2DDO: it seems there's some "minimal data <br>stream" offered to each Igate (and all IS-connected clients are <br>considered Igates). It probably serves some good purpose, but is not <br>well advertised.<br><br><br>Regards,<br><br>Wojciech<br><br>-- <br>73!<br>Wojtek SP9WPN<br><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a><br><a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br></div>_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote></div>