Digipeated messages contains NUL character

[F4FXL]

Steps to reproduce
Send a message from RF to RF using a direwolf digipeater configured as digipeater only

Expected result
Message is digipeated unchanged and reaches its recipient

Actual Result
The message is corrupted. The { character marking the beginning of the message is replaced by a NUL charachter. Generally speaking it seems like message digipeating/igating is quite broken in Direwolf 1.7 see also #405

[F4FXL]

It seems like the issue only occurs when igating is enabled... When igating is disabled everything seems to be ok.... Not sure though, needs confirmation. v1.6 also has the issue

[wb2osz]

Thank you for providing a clear complete description including an example to demonstrate the problem.
This has been fixed in the dev branch.

[wb2osz]

commit 30869c7
Date: Mon Jul 4 02:11:55 2022 +0100

Issues 405 & 406 and other improvements in message interpretation.

This is in the "dev" branch which will become release 1.7.

[wb2osz]

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.