-
Notifications
You must be signed in to change notification settings - Fork 245
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
Parsing a decrypted PDU-L7 Pcap with multiple sessions does not work #313
Comments
I think exported PDUs don't have proper source/dst information, so all streams get mangled together into one big soup. We should check if there's any info in the exported PDUs that could make it possible to distinguish |
Good point @alxbl! I'll check but if what we need to distinguish isn't available, we will simply update our instructions to differentiate streams before exporting and document the limitation. |
I think there's a clever way to do this by using the EXPORTEDPDU's |
I managed to get something working by parsing the Exported PDUs and creating sessions with the information available in the tags... it's messy right now but I'll clean up the code and open a PR tomorrow.
|
Rebased on master by @obilodeau. Some problems likely remain.
Rebased on master by @obilodeau. Some problems likely remain.
Rebased on master by @obilodeau. Some problems likely remain.
feat(#313): Add support for conversion of multiple exported sessions.
Rebased on master by @obilodeau. Some problems likely remain.
I am able to reliably reproduce a bug where a Pcap with exported PDUs containing more than one session of the same source and destination IPs is getting mixed up and doesn't convert to the correct replay file or mp4.
We should probably cleanly separate streams in the PDU parsing code. Not sure how to do that with PDU level packets (is the information available in the wireshark trace?).
Workaround: walking the pcap with filters like
tcp.stream eq <1, 2, .. N>
and exporting one PDU-L7 pcap per TCP streams works.The text was updated successfully, but these errors were encountered: