-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not parsing Profinet Real-Time Protocol directly on ethernet frame #61
Comments
Thanks for logging the issue. You're correct: at the moment, both traffic parsing engines in Malcolm (Arkime and Zeek) only parse traffic IP traffic, not anything directly on the ethernet frame. Zeek v4.1 has just recently been released, which has a new packet framework which should allow for stuff like this. The next release of Malcolm will use Zeek v4.1, but that in and of itself won't automagically fix parsers like this. A colleague of mine is working on a new PROFINET parser to replace the Amazon one we're using right now. I'll reach out to him and see if this fits into what he's doing. Is there a possibility you could attach a sample or obfuscated PCAP to this issue? |
Thank you for the quick reply. unfortunately i am not allowed to post such data. it is good to know that there could be such a function in the future. |
No problem. For now I'll keep this issue open so we can track it, though it may not be resolved in the short term. |
Kamino closed and cloned this issue to cisagov/Malcolm |
Hello, i have PCAP files from tapping Profinet-Communication with wireshark/tshark. After Uploading it to Malcolm i mainly see S7Comm and cotp. The Documentation mentions zeek is able to parse Profinet but it doesn't work. see attached file.
In wireshark it says Profinet Real-Time Protocol thats directly on the Ethernet-Frame. see second file.
I havent found Data in the Elasticsearch database containing any ethernet information. Does zeek not parse ethernet information or am i doing something wrong?
The text was updated successfully, but these errors were encountered: