[OZAPRS] Do RX only igates break APRS messaging?

[Damien Gardner]

Hey Dave,

The 'APRS Servers' don't route anything, unless something's changed in one
of the newer daemons.  They're just relaying a simple text based string to
all connected stations (with some caveats around filters based on the TCP
port stations are connected to), for each packet on the network.  They're
not really even aware that they're handling an AX-25 payload (As evidenced
by all the malformatted D-star crap being relayed with invalid SSID's).
It's the i-gates and digipeaters that are actually doing the routing.

If you send a message from one station to another, and it ends up on the
internet stream, it will only end up back out on RF, if it hits an i-gate
that has HEARD the destination call, and that i-gate has TX capability.  If
the destination station has been heard by multiple TX-capable i-gates, then
the message will be relayed by multiple i-gates. Just like it might travel
multiple paths from the i-gate to the destination, so duplicate handling
kicks in on the receiver anyway :) (DUP! on my D7 :) )

Cheers,

DG

On Thu, 1 Nov 2018 at 19:39, David Murphy <david.k.murphy at gmail.com> wrote:

> Hi Team,
>
> I am new to APRS and trying to get my head around it for SAR and WICEN
> use. Messaging seems like a great function, but obviously needs
> bi-directional simplex radio coverage between stations on APRS or
> access to an i-gate that has TX and RX functions. So my questions is
> do RX only i-gates kill messaging? From what I have read the APRS
> servers will route a message back to the i-gate that heard the station
> first, is that right? Therefore the message doesn't get sent?
>
> Thanks,
> Dave
>
> VK2XDA
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.aprs.net.au/pipermail/ozaprs/attachments/20181102/5b06bdcc/attachment.html>