If I put in a digi path of FAR (according to this blog post), only FAR should pick up my packet. However, what seems to happen is that NEAR picks up the packet, gates it, and keeps the path I gave. So on APRS-IS it looks like FAR digipeated the packet back to NEAR.
This can't be happening, though. If I pick a station in the next state (VERYFAR) and put that in the digi path as VERYFAR, I get the same behavior in the path on APRS-IS.
Am I right in expecting APRSdroid to work this way?
If APRSdroid is working properly, is this likely an issue with the NEAR iGate, in that it is not filtering packets based on path but instead accepting everything?
I am trying to determine whether this is an APRSdroid issue or with the local iGate. Thanks for any help.
I am experimenting with paths on RF. Let's say i have two iGates, NEAR (close by) and FAR (far away).
If I put in a digi path of
WIDE1-1,WIDE2-1
, my packet is picked up and gated to APRS-IS by NEAR.If I put in a digi path of
FAR
(according to this blog post), only FAR should pick up my packet. However, what seems to happen is that NEAR picks up the packet, gates it, and keeps the path I gave. So on APRS-IS it looks like FAR digipeated the packet back to NEAR.This can't be happening, though. If I pick a station in the next state (VERYFAR) and put that in the digi path as
VERYFAR
, I get the same behavior in the path on APRS-IS.So my questions are:
APRSdroid version 1.6.0d2020-10-02