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 4793] New: 802.11s support

Date: Tue, 25 May 2010 15:11:45 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4793

           Summary: 802.11s support
           Product: Wireshark
           Version: SVN
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: gerald@xxxxxxxxxxxxx


Created an attachment (id=4690)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4690)
802.11s patch

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Patch to add 802.11s mesh support from Sam Leffler and Javier Cardona. Per
Sam's email:

Hi Gerald, attached is a version of Javier's patch to add 802.11s mesh support
to the latest wireshark in svn (or at least close, svn up'd yesterday).  I've
made some changes to his original work but it's his so please give credit to
him and blame to me  :)   Changes from Javiers's original patch (mostly for
Javier) are:

1. Update from 1.02 code base by resolving conflicts.  11s tags are not yet
assigned and conflict w/ items already present in packet-ieee802_11.c including
the draft 11p support (that was similarly committed w/o IEEE-assigned numbers).
 I hacked this by adding a MESH_OVERRIDES #define and sticking the 11p stuff
under WAVE_SUPPORT.  I don't know how you handle this stuff; if you want I can
add a button the gui to try and allow everything to co-exist.

2. Fix the handling of radiotap DATAPAD.

3. Fix the handling of mesh data frames with AE != 0.

Note that parsing mesh data frames is problematic as the mesh control header
that's placed after the 802.11 header cannot be reliably identified.  Javier
came up with a heuristic that I've kept and there's still a debug g_warning
(#if 1) to help diagnose problems.  I can add a radiotap flag to reliably mark
mesh frames but would prefer to stay out of the radiotap politics so it'd
likely be freebsd-specific.

Attached is a sample radiotap capture of mesh data that includes data frames. 
I can provide a longer one w/ more variety later if interested (I recall Guy
saying you keep test data for doing regressions).

Note this work is based on 802.11s D3.0 but some of the assigned numbers are
back-rev'd to 1.08 to be compatible with Javier's linux implementation. 
FreeBSD 8.0 will ship with mesh support and I've also got tcpdump changes I'll
forward separately.

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