Closed Tyler-2 closed 2 years ago
Thanks for writing.
"WIDE1-2" is highly unusual. Some digipeaters might discard it depending on the configuration. You probably want to change the IGate configuration to use "WIDE1-1,WIDE2-1". Otherwise it looks normal.
An IGate station wraps the original packet in a third party header. That way it has both the RF station transmitting this new packet and it retains the original sending station. When properly functioning APRS implementations see the "}" data type indicator, they process everything after it to obtain a modified version of the original packet.
You might find these references interesting:
APRS-IS (Automatic Packet Reporting System-Internet Service) http://www.aprs-is.net/Default.aspx
APRS iGate properties http://wiki.ham.fi/APRS_iGate_properties (now gone but you can find a copy here:) https://web.archive.org/web/20120503201832/http://wiki.ham.fi/APRS_iGate_properties
Notes to iGate developers https://github.com/hessu/aprsc/blob/master/doc/IGATE-HINTS.md#igates-dropping-duplicate-packets-unnecessarily
Thank you, looks like this format wasn't a mistake, it's just something I'm unfamiliar with. I'll read up on the docs. Two things I've already learned:
Thanks for the careful and informative reply, it was probably more than I deserved!
I noticed that when I send a message from my phone (APRSDroid) via APRS-IS, when my Direwolf digi picks it up and then tries to TX to RF, it seems to mangle the "header":
I think this should look more like:
Shouldn't it? While I'm not sure how IGate paths are supposed to be preserved/represented, it doesn't seem like the
WIDE1-2:}
that is inserted in the current case is correct, nor the changing of the packet to have "originated" from K1MLN-2.The current case doesn't look like it would even be routable...