So the libpcap main and 1.10 branches include changes to
not clear the CANFD_FDF flag for FD frames;
put the multi-byte fields in the CAN XL header into little-endian byte
order;
and the Wireshark main and 4.2 branches include changes to
treat CAN frames without the CANXL_XLF flag or the CANFD_FDF flag as FD
frames if they're exactly 72 bytes long, to work around the (fixed in the main
and 1.10 branches) libpcap bug where CANFD_FDF is unintentionally cleared;
dissect CAN XL frames;
hand LINKTYPE_LINUX_SLL frames with a protocol type of CAN XL to the
SocketCAN dissector;
so I think this issue will be resolved by the next Wireshark and libpcap
releases.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
