https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14321
Bug ID: 14321
Summary: confuse transactions at u3v dissector on mixed cmd and
event transactions
Product: Wireshark
Version: 2.4.3
Hardware: x86
OS: Windows 10
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: rwe...@baumer.com
Target Milestone: ---
Build Information:
Version 2.4.3 (v2.4.3-0-g368ba1ee37)
--
- in u3v protocol are commands (rd/wr mem) send from host to device identified
by request-ident
- parallel are (if activated) events send by device (u3v-camera) to host as
well identified by request-ident
- host and device start independently their idents by 0 to 65535 and than
starts again by 1 to 65536 and so on
- if after a cmd with f.e. req-id 42 comes a event from cam also with req-id
1234 and after this the ack for the cmd with req-id 42 - than is the last ack
with the event 'connected' because the using of cl_conv_info->trans_info which
is now set to the event!
to see in packet-cameralink.c at line 1370 f.
=> both directions need there own cl_conv_info->trans_info
f.e. cl_conv_info->trans_info_host and cl_conv_info->trans_info_dev ...
this happens very seldom, we found this, because we adapted the u3v dissector
for cameralink and there happens this with our cams
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
