You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The APRS igate does not forward packets it can not decode itself. There may be packets out there that are not yet implemented in the decoder of sdrangel, or new/experimental packets. The igate does not need to care whether it can understand the APRS packet contents - the decision whether to forward the packet can be left to the APRS-IS servers, and other decoders on the other side of APRS-IS may well be able to decode them. It's good to obey the "NOGATE", "RFONLY" rules, of course.
Hi,
The APRS igate does not forward packets it can not decode itself. There may be packets out there that are not yet implemented in the decoder of sdrangel, or new/experimental packets. The igate does not need to care whether it can understand the APRS packet contents - the decision whether to forward the packet can be left to the APRS-IS servers, and other decoders on the other side of APRS-IS may well be able to decode them. It's good to obey the "NOGATE", "RFONLY" rules, of course.
sdrangel/plugins/feature/aprs/aprsworker.cpp
Line 108 in cb89392
Just make sure the igate is binary clean, and send bytes up to the first CR or LF character seen in the AX.25 data field.
The text was updated successfully, but these errors were encountered: