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
Steps to reproduce:
Send a message from an APRSIS only client to an RF only client. E.g. I used my APRSDroid to send a message to my FT2.
Expected Result:
The message goes onto RF unchanged and with its sequence number
Actual Result
The sequence number is removed from the message when going on air. This will prevent the recipient to send any ack packet because it did not get the sequence number. Additionally it will lead to unnecessary traffic as the sender ill continue sending the message as long as it does not get the ack.
The error was introduced in the dev branch (release 1.7 development) by commit e108147 on February 25, 2022.
Those running release 1.6 or earlier not be impacted. This would affect only those who
are using the "dev" branch from between the two dates mentioned.
Steps to reproduce:
Send a message from an APRSIS only client to an RF only client. E.g. I used my APRSDroid to send a message to my FT2.
Expected Result:
The message goes onto RF unchanged and with its sequence number
Actual Result
The sequence number is removed from the message when going on air. This will prevent the recipient to send any ack packet because it did not get the sequence number. Additionally it will lead to unnecessary traffic as the sender ill continue sending the message as long as it does not get the ack.
See topic here : https://groups.io/g/direwolf/topic/92085159
The text was updated successfully, but these errors were encountered: