# How to fix SURICATA Ethertype unknown

**URL:** <https://forum.suricata.io/t/how-to-fix-suricata-ethertype-unknown/5927>\
**Category:** Uncategorized\
**Created:** [August 14, 2025, 11:57am UTC](https://forum.suricata.io/t/how-to-fix-suricata-ethertype-unknown/5927 "2025-08-14T11:57:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrn](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/mrn/32/3675_2.png) [@mrn](https://forum.suricata.io/u/mrn)\
**Post date:** [August 14, 2025, 11:57am UTC](https://forum.suricata.io/t/how-to-fix-suricata-ethertype-unknown/5927/1 "2025-08-14T11:57:43Z")

</div>

Hello, guys, from month ago I installed suricata for my network, and got this alert:  
08/14/2025-14:55:44.377170 [**] [1:2200121:1] SURICATA Ethertype unknown [**] [Classification: Generic Protocol Command Decode] [Priority: 3] [\*\*] [Raw pkt: 01 80 C2 00 00 0E D8 EC E5 C1 CC 6E 88 CC 02 07 04 D8 EC E5 C1 CC 58 04 03 07 32 32 06 02 00 78]

And sometime get this alert:  
08/14/2025-14:52:25.018098 [**] [1:2027397:1] ET INFO Spotify P2P Client [**] [Classification: Not Suspicious Traffic] [Priority: 3] {UDP} 10.2.10.134:57621 → 10.2.11.255:57621

How to get correct info for first one.  
Thank you for your time

---

<div class="post-metadata">

**Author:** ![Jeff\_Lucovsky](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/jeff_lucovsky/32/11_2.png) [@Jeff\_Lucovsky](https://forum.suricata.io/u/Jeff_Lucovsky)\
**Post date:** [August 17, 2025, 12:59pm UTC](https://forum.suricata.io/t/how-to-fix-suricata-ethertype-unknown/5927/2 "2025-08-17T12:59:47Z")

</div>

“Ethertype unknown” means that Suricata doesn’t recognize the layer 2 protocol. Suricata knows about most layer 2 protocols – see the full list in the source code file `decode.h and/or `decode-ethernet.h`

According to chatgpt — I cannot vouch for its response, but it looks reasonable.  
It’s an LLDP advertisement from a device with chassis MAC D8:EC:E5:C1:CC:58, sent out of a locally labeled port “22”, with a 120-second TTL, using the standard LLDP multicast destination. (Typically there’s an End-of-LLDPDU TLV 00 00, which just isn’t shown here.)
