The Aruba ERM Type 1 Dissector inconsistent with Type 0 and Type 3
**This issue was migrated from [bug 11204](https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11204) in our old bug tracker.**
Original bug information:
**Reporter:** Doug Wussler\
**Status:** RESOLVED FIXED\
**Product:** Wireshark\
**Component:** Dissection engine (libwireshark)\
**OS:** All\
**Platform:** All\
**Version:** 1.12.5
Attachments:
[ERM_Dissectors.pdf](/uploads/faf046b527003db9919bcc7df56644ac/ERM_Dissectors.pdf): Screen shots showing FCS for Type 1 and absence of FCS for Type 3
[ERM_Type1.pcapng](/uploads/664a6673b30c17a196e3e7662f48de59/ERM_Type1.pcapng): This is an ERM Type 1 Packet Capture
[ERM_Type0.pcapng](/uploads/e92a4fb0aa6147cbecacb9ad697c38eb/ERM_Type0.pcapng): This is ERM Type 0 packet capture
[ERM_Type3.pcapng](/uploads/362ea620da9063947913883ca44b2844/ERM_Type3.pcapng): This is ERM Type 3 packet capture
See also:
Issue #9880
issue