Add identifiable packets through a counter

[hrfarmer]

Summary

Adds a 1 byte number to the header of packets that identifies the message it came from. Receive will bounce any packets that don't match the identifier it's looking for. Should be a good start for adding retry logic in the future.

How was this tested

• Added new unit tests
• Ran code on hardware (screenshots are helpful)
• Other (Please describe)

[Mikefly123]

Hey @hrfarmer I was wondering, since the unique identifier is only 1 Byte (256 possible options) is the idea here that it is statistically unlikely that two packets sent at a random time will have the same unique identifier?

My thought here is mainly like, what if we are sending a packet stream of more than 256 unique packets (i.e. if we are transferring a file or something) wouldn't we run the risk of rolling over the counter and having replication? I suppose the 2 byte sequence number when sending a stream of packets could also alleviate that

[hrfarmer]

The number is incremented on each unique message sent, so unless we have a situation where there's over 255 things pending to be sent at a time, it shouldn't be an issue.

Also yes for things like file transfer the sequence number should be able to handle that.

[nateinaction]

Looks like we need a test for if we get another message while receiving a message.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud