Closed mxwendler closed 2 years ago
Could you attache the frame as a pcap file, that makes it much simpler for me to debug?
sure! only one pcap, the capture is 200MB fault-discovery-1.zip
So disecting that frame, it looks ok to me. Ignoring the UDP/IP header:
Thank you - i also think the check for SACN_DATA_PACKET_MIN_SIZE makes no sense here, since the check for a general packet size is done before (ETC Library code):
bool parse_sacn_data_packet(const uint8_t* buf, size_t buflen, SacnRemoteSource* source_info, uint8_t* seq,
bool* terminated, SacnRecvUniverseData* universe_data)
{
// Check the input parameters including buffer size
if (!buf || !source_info || !seq || !terminated || !universe_data || buflen < SACN_DATA_PACKET_MIN_SIZE)
return false;
[...]
}
I will point the ETC developers to this issue. Thank you again for your prompt support!
Hello there,
thank you for writing this awesome tool!
On my windows laptop i have sacnview and my own application using the etc sacn library. i get warnings in the log,
00:56:16: Debug: sacn: [WARN] sACN: Ignoring malformed sACN universe discovery packet from component 7b646566-3632-6538-652d-613863652d34
and looking deeper into the issue, this check in the ETC library fails:
because buflen is 10, which is lower than SACN_DATA_PACKET_MIN_SIZE (88).
These are much more than 10 bytes .. can someone give me a hint if the issue is either in sacnview or in the etc library?