Compiled (32-bit) with Qt 5.13.0, with libpcap, with POSIX capabilities (Linux), without libnl, with GLib 2.56.1, with zlib 1.2.11, without SMI, with c-ares 1.14.0, without Lua, with GnuTLS 3.5.19 and PKCS #11 support, with Gcrypt 1.5.0, with MIT Kerberos, without MaxMind DB resolver, without nghttp2, without brotli, with LZ4, without Zstandard, without Snappy, with libxml2 2.9.4, with QtMultimedia, without automatic updates, with SpeexDSP (using bundled resampler). There is NO warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. License GPLv2+: GNU GPL version 2 or later This is free software see the source for copying conditions. Wireshark 3.4.0 (Git commit 9733f173ea5e) Copyright 1998-2020 Gerald Combs and contributors. Here the interesting HID Reports are in packets No. Wireshark-logitec-receiver-typed-in-two-interfaces-dev-addr-7.pcapng. The following file was captured using the steps described above:
Also, RightGUI should be present and also shown as UP. What is the expected correct behavior?īits go from least significant to most significant, and 0x03 should be interpreted as LeftControl (0xe0) and LeftShift (0xe1) being DOWN, while RightAlt (0xe6) being UP. The first byte, corresponding to Report Size (1), Report Count (8), Usage Minimum (0xe0), Usage Maximum (0xe7), Input (Data,Var,Abs), is interpreted assuming wrong bit order.
Notice how above not only is one key missing (the LSB is ignored for some reason, although Usage Maximum is specified as 0xe7 in HID Report Descriptor), but also the wrong key shown as DOWN.
0 kommentar(er)
