GCC 4.6 has added 'unused but set' reports so this change allows builds to proceed without
erroring out for those building from SVN with GCC 4.6.
(AFAIK Wireshark source distributions do not enable -Werror).
This change can be removed (at least globally) once the code as been fixed.
svn path=/trunk/; revision=38311
The previous fixes in r37728 and r37730 did build a wireshark which was
unable to use the native windows file dialog (GetOpenFileName).
svn path=/trunk/; revision=38299
cc1: warnings being treated as errors
../../gtk/sctp_graph_dlg.c: In function ‘draw_tsn_graph’:
../../gtk/sctp_graph_dlg.c:511: error: ‘cr’ may be used uninitialized in this function
../../gtk/sctp_graph_dlg.c: In function ‘draw_sack_graph’:
../../gtk/sctp_graph_dlg.c:163: error: ‘cr’ may be used uninitialized in this function
../../gtk/sctp_graph_dlg.c: In function ‘draw_nr_sack_graph’:
../../gtk/sctp_graph_dlg.c:341: error: ‘cr’ may be used uninitialized in this function
svn path=/trunk/; revision=38296
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 8/9] add support for Root Announcement (RANN) IEs
svn path=/trunk/; revision=38281
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 8/9] add support for Root Announcement (RANN) IEs
svn path=/trunk/; revision=38280
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 7/9] update parsing of mesh control field
During development of the 80211s standard, a "mesh header" was conceived. This mesh header has been renamed the "mesh control field". Further, the conditions under which it is expected to appear have also changed. Specifically, the mesh control field appears in multihop action frames and mesh data frames. In the former case, it appears after the action category and action code, so no special header parsing is required to parse it.
The latter case is a bit more complicated. We know the mesh control field is present if the data frame was transmitted by a mesh STA, AND the new "Mesh Control Present" bit in the QoS control field is set. This second thing is easy enough to check. But the first thing is not. So we continue to rely on heuristics. Specifically, we only expect the mesh control field for valid from-ds/to-ds settings, and if the mesh control field itself is valid.
Other relevant changes in this patch include:
-- rename mesh_header to mesh_control as appropriate
-- consider the mesh control field to be part of the header when accounting for payload padding.
-- parse some of the qos fields earlier so they can be used to determine if the mesh control field is present.
-- use existing mesh control parsing code instead of duplicating it.
svn path=/trunk/; revision=38279
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 6/9] update mesh path discovery (hwmp) IEs to 802.11s v12
This includes adding the new mesh reason codes
From me
Fix checkAPI Errors (the blurb field matches the field name)
svn path=/trunk/; revision=38278
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 5/9] make pre-80211s marvell mesh use its own data structures
The pre-80211s legacy mesh networking developed by marvell has some similarities to the latest 80211s mesh networking. However, there are enough differences in naming and convention that they should have their own data. For clarity, we break up the marvell and 80211s mesh dissection.
Note that as of this patch, 80211s parsing uses the legacy data structures. That will change in subsequent patches in this set.
svn path=/trunk/; revision=38277
Update 802.11s packet dissecting to the ratified standard (v12.0)
Subject: [PATCH 4/9] eliminate obsolete non-standard 80211s peer link action frame code
The peer link action frame no longer exists. Its data now appears in the self-protected action frame and the peering management IE.
Note that this leaves a gap in the internal field codes that is addressed in a subsequent patch.
svn path=/trunk/; revision=38276
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 3/9] add support for 802.11s v12.0 mesh peering management IE
The v12.0 mesh peering management IE replaces the exiting mesh peer link management IE and has a slightly different format.
From me
Fix checkAPI Errors (the blurb field matches the field name)
Remove unused hf_ieee80211_mesh_mgt_pl_reason_code
svn path=/trunk/; revision=38275
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 2/9] add support for 802.11s v12.0 action frame fixed fields
From me
Fix checkAPI Errors (the blurb field matches the field name)
svn path=/trunk/; revision=38274
Update 802.11s packet dissecting to the ratified standard (v12.0)
[PATCH 1/9] update mesh ID and mesh config IEs to latest 80211s draft (v12)
svn path=/trunk/; revision=38273
