Wireshark mailing list archives
Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ??
From: Guy Harris <guy () alum mit edu>
Date: Wed, 4 Mar 2015 20:03:51 -0800
On Mar 4, 2015, at 9:32 AM, Dave Stephenson <daves () ruckuswireless com> wrote:
Thanks, Guy!
By the way, radiotap has provisions for vendor extensions: http://www.radiotap.org/defined-fields/Vendor%20Namespace and the organization responsible for registering vendors is the Institute of Electrical and Electronic Engineers: The Vendor Namespace Field contains three sub-fields. The first sub-field is 3 bytes long. It contains the vendor's IEEE 802 Organizationally Unique Identifier (OUI). The fourth byte is a vendor-specific "namespace selector." with whom you've already registered several OUIs, so you don't even need anybody's permission to add extensions to radiotap using the vendor namespace (other than possibly permission within your organization to use a particular OUI for that purpose). ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Dave Stephenson (Mar 03)
- Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Guy Harris (Mar 03)
- Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Dave Stephenson (Mar 04)
- Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Guy Harris (Mar 04)
- Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Dave Stephenson (Mar 04)
- Re: Does Wireshark maintain the Per-Packet Information (PPI) Header Specification ?? Guy Harris (Mar 03)