Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3288] Wireshark is not filtering wireless packets based on

Date Prev · Date Next · Thread Prev · Thread Next
Date: Sat, 28 Feb 2009 23:35:52 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3288


Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         OS/Version|Debian                      |All
           Platform|PC                          |All
         Resolution|                            |INVALID




--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx>  2009-02-28 23:35:50 PDT ---
IEEE Std 802.11e-2005 says, in section 7.1.3.5 "QoS Control field", that frames
sent by non-AP QSTAs don't *have* an EOSP bit; instead, bit 4 of the QoS
Control field indicates whether bits 8-15 of the QoS Control field are the TXOP
Duration Requested or Queue Size.

Unless I'm missing something, frames sent by an AP would have From DS set; the
frames you're not seeing when you filter on wlan.qos.eosp don't have From DS
set, which means they don't have an EOSP bit, and therefore neither
wlan.qos.eosp == 0 nor wlan.qos.eosp == 1 are true (wlan.qos.eosp doesn't exist
in those frames, so it is neither 0 nor 1 nor any other value in that frame),
so neither of those filters should, and neither of those filters will, match
those frames.

I've checked in changes to add a "wlan.qos.bit4" field, to give the value of
bit 4 for non-AP frames, and also cleaned up the display of bits 8-15 of the
QoS field.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.