aboutsummaryrefslogtreecommitdiffstats
path: root/wiretap/airopeek9.c
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2008-09-11 03:37:16 +0000
committerGuy Harris <guy@alum.mit.edu>2008-09-11 03:37:16 +0000
commitba292329e05703e5bdbc7fdcc8346a11dc1d8133 (patch)
tree176abee2a8e9c025b678df707606bff13336cc8d /wiretap/airopeek9.c
parent6dba0c117bb8fa7100fa36e60725139aa2747e2f (diff)
Suggest why we might have at least 3 different network subtypes for 802.11.
svn path=/trunk/; revision=26175
Diffstat (limited to 'wiretap/airopeek9.c')
-rw-r--r--wiretap/airopeek9.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/wiretap/airopeek9.c b/wiretap/airopeek9.c
index bbd036158e..c96ec5cb4f 100644
--- a/wiretap/airopeek9.c
+++ b/wiretap/airopeek9.c
@@ -52,7 +52,13 @@ typedef struct airopeek_section_header {
guint32 section_const;
} airopeek_section_header_t;
-/* network subtype values */
+/*
+ * Network subtype values.
+ *
+ * XXX - do different network subtype values for 802.11 indicate different
+ * network adapter types, with some adapters supplying the FCS and others
+ * not supplying the FCS?
+ */
#define AIROPEEK_V9_NST_ETHERNET 0
#define AIROPEEK_V9_NST_802_11 1 /* 802.11 with 0's at the end */
#define AIROPEEK_V9_NST_802_11_2 2 /* 802.11 with 0's at the end */