Why wireshark is not identifying my mongo packets? [closed]
Asked Answered
H

0

7

I'm using Wireshark 3.0.0 (Git) to sniff Mongo packets. I can see the packets in port 27017 but the protocol identifies them as TCP and not as Mongo. After checking protocol preferences, Mongo port is set to 27017.

Why doesn't wireshark detect the packages as Mongo?

Thanks in advance,

Handiwork answered 4/4, 2019 at 21:31 Comment(5)
Presumably because it goes over a regular TCP/IP socket per docs.mongodb.com/manual/reference/mongodb-wire-protocolRamillies
Can you post a capture file somewhere for analysis?Egwan
Check that the dissector is enabled in Analyze --> Enabled Protocols....Pork
@MikaS Mongo appers as enabledHandiwork
Using Analyze --> Decode As... and changing TCP port 27017 and field Current to MONGO makes the capture display them but it is not a permanent solution.Handiwork

© 2022 - 2024 — McMap. All rights reserved.