https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14492

            Bug ID: 14492
           Summary: tshark -T ek, all 802.11 management  packets "wlan"
                    critical data missed
           Product: Wireshark
           Version: 2.4.4
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: TShark
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: display...@gmail.com
  Target Milestone: ---

Created attachment 16206
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16206&action=edit
tshark -T ek compare between version 2.2.6 to 2.4.4

Build Information:
TShark (Wireshark) 2.4.4 (Git v2.4.4 packaged as 2.4.4-1~16.04.0)

Copyright 1998-2018 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.48.2, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.2.4, with GnuTLS 3.4.10, with Gcrypt 1.6.5, with MIT Kerberos, with GeoIP,
with nghttp2 1.7.1, with LZ4, with Snappy, with libxml2 2.9.3.

Running on Linux 4.4.0-97-generic, with Intel(R) Core(TM) i7-4930MX CPU @
3.00GHz (with SSE4.2), with 31788 MB of physical memory, with locale
LC_CTYPE=en_US.UTF-8, LC_NUMERIC=he_IL.UTF-8, LC_TIME=he_IL.UTF-8,
LC_COLLATE=en_US.UTF-8, LC_MONETARY=he_IL.UTF-8, LC_MESSAGES=en_US.UTF-8,
LC_PAPER=he_IL.UTF-8, LC_NAME=he_IL.UTF-8, LC_ADDRESS=he_IL.UTF-8,
LC_TELEPHONE=he_IL.UTF-8, LC_MEASUREMENT=he_IL.UTF-8,
LC_IDENTIFICATION=he_IL.UTF-8, with libpcap version 1.7.4, with GnuTLS 3.4.10,
with Gcrypt 1.6.5, with zlib 1.2.8.

Built using gcc 5.4.0 20160609.

--
in tshark -T ek when 802.11 management packet, all data from old "wlan" display
filter disappeared, 
The version 2.4.4 changed the "wlan_mgt" to "wlan" but the old data was in wlan
missed.

        "wlan": {
            "wlan_fc_wlan_fc_subtype": "4",
            "wlan_fc_wlan_fc_type": "0",
            "wlan_fc_wlan_fc_version": "0",
            "wlan_fc_wlan_flags": "0x00000000",
            "wlan_flags_wlan_fc_ds": "0x00000000",
            "wlan_flags_wlan_fc_frag": "0",
            "wlan_flags_wlan_fc_fromds": "0",
            "wlan_flags_wlan_fc_moredata": "0",
            "wlan_flags_wlan_fc_order": "0",
            "wlan_flags_wlan_fc_protected": "0",
            "wlan_flags_wlan_fc_pwrmgt": "0",
            "wlan_flags_wlan_fc_retry": "0",
            "wlan_flags_wlan_fc_tods": "0",
            "wlan_wlan_addr": "ff:ff:ff:ff:ff:ff",
            "wlan_wlan_addr_resolved": "Broadcast",
            "wlan_wlan_bssid": "ff:ff:ff:ff:ff:ff",
            "wlan_wlan_bssid_resolved": "Broadcast",
            "wlan_wlan_da": "ff:ff:ff:ff:ff:ff",
            "wlan_wlan_da_resolved": "Broadcast",
            "wlan_wlan_duration": "0",
            "wlan_wlan_fc": "0x00004000",
            "wlan_wlan_fc_type_subtype": "4",
            "wlan_wlan_fcs": "0x15bf95b1",
            "wlan_wlan_fcs_status": "1",
            "wlan_wlan_frag": "0",
            "wlan_wlan_ra": "ff:ff:ff:ff:ff:ff",
            "wlan_wlan_ra_resolved": "Broadcast",
            "wlan_wlan_sa": "e8:ab:fa:74:dd:ff",
            "wlan_wlan_sa_resolved": "Shenzhen_74:dd:ff",
            "wlan_wlan_seq": "1994",
            "wlan_wlan_ta": "e8:ab:fa:74:dd:ff",
            "wlan_wlan_ta_resolved": "Shenzhen_74:dd:ff"
        },
        "wlan_mgt": {

-- 
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

Reply via email to