Wireshark-bugs: [Wireshark-bugs] [Bug 4226] New: WiFi Media Type Frame for Network Monitor 3

Date: Mon, 9 Nov 2009 11:50:41 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4226

           Summary: WiFi Media Type Frame for Network Monitor 3
           Product: Wireshark
           Version: 1.2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: paullo@xxxxxxxxxxxxx


Created an attachment (id=3937)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3937)
Capture file with  wifi traffic

Build Information:
Version 1.2.0 (SVN Rev 28753)

Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 with GTK+ 2.14.7, with GLib 2.18.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI,
without c-ares, without ADNS, with Lua 5.1, without GnuTLS, without Gcrypt,
without Kerberos, without GeoIP, with PortAudio V19-devel (built Jun 15 2009),
without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.

Running on Windows Vista, build 7600, without WinPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Starting with Network Monitor 3.1, we've added a new Wifi Media type to
describe the meta data we are able to capture using Wireless Adapater
Management mode.

The Media type is 6, and is only store as per frame media type (See bug 4223).

As the parser definitions are included with the product, you can reference
wireless.npl as the source for the wireless header.  This file has also been
attached.  Starting with "Protocol WiFi" you should be able to determine the
structure of the packet.

You can ignore anything in square brackets [], in the parser code.

Tables are often used to describe the mapping of values to human readble text.

I've also attached a sample wireless capture.


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