Update some comments.

There's all sorts of interesting stuff out there on the Intertubes if
you happen to be searching for the right thing.

Change-Id: Ib5e18ece5dfaa284ece8cfda23887a9408c8318e
Reviewed-on: https://code.wireshark.org/review/8503
Reviewed-by: Guy Harris <guy@alum.mit.edu>

epan/dissectors/packet-aruba-erm.c

@@ -25,6 +25,16 @@
  * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
  */
 
+/*
+ * See
+ *
+ *    http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/Bug-in-ArubaOS-Packet-Capture/td-p/237984
+ *
+ *    http://kjspgd.net/?p=30
+ *
+ * for more information.
+ */
+
 /*
  * Formats:
  *
@@ -43,7 +53,7 @@
  *
  * Peek (type 1):
  *
- * Payload contains a "peek remote" packet, as supported by
+ * Payload contains a "Peek remote" packet, as supported by
  * EtherPeek/AiroPeek/OmniPeek.
  *
  * Airmagnet (type 2):
@@ -67,6 +77,14 @@
  *
  * Payload contains a PPI header followed by the packet data, starting
  * with an 802.11 header.
+ *
+ * Peek 11n/11ac (type 5):
+ *
+ * This is probably the "new" "Peek remote" format.  The "Peek remote"
+ * dissector should probably be able to distinguish this from type 1,
+ * as the "new" format has a magic number in it.  Given that there's
+ * a heuristic "Peek remote new" dissector, those packets might
+ * automatically be recognized without setting any preference whatsoever.
  */
 
 #include "config.h"

epan/dissectors/packet-peekremote.c

@@ -15,6 +15,9 @@
  * discovery and setup, or whether they use different protocols
  * for streaming packets.
  *
+ * Apparently Aruba supports several protocols, including Peek remote.
+ * See the packet-aruba-erm dissector.
+ *
  * Tested with frames captured from a Cisco WCS.
  *
  * Copyright 2007 Joerg Mayer (see AUTHORS file)