- 2.4.17 - if_arp.h - Add the Prism2 ARP type

(Please CC: me responses; I'm not subscribed)

Hey, this one-line patch (I diffed it against 2.4.17-rc2) defines the ARPHRD_IEEE80211_PRISM arp type.

A little background. The prism2 series of wireless ethernet cards are capable of operating in true promiscious mode, capturing raw 802.11 frames. When it's doing this, the driver prepends a special monitoring header onto the packet with useful information.

Since the v0.1.6 release of the driver, this was handled via NETLINK broadcasts.. but that's Bad(tm). Instead, the next version (0.1.14) of the driver will support raw capture using the PF_PACKET interface, which means that it'll need its own arp type for libpcap to recognize and handle the special headers. (without the header, it sends standard ARPHRD_IEEE80211 frames)

libpcap/ethereal/etc already have dissectors for this special header, so all that's left is to define a fixed arp type.

So, I humbly submit this patch for inclusion.

Thanks!

Solomon Peachy                                    pizzaATfucktheusers.org
I ain't broke, but I'm badly bent.                           ICQ# 1318344
Patience comes to those who wait.
    ...It's not "Beanbag Love", it's a "Transanimate Relationship"...

@@ -82,6 +82,7 @@
 	/* 787->799 reserved for fibrechannel media types */
 #define ARPHRD_IEEE802_TR 800		/* Magic type ident for TR	*/
 #define ARPHRD_IEEE80211 801		/* IEEE 802.11			*/
+#define ARPHRD_IEEE80211_PRISM 802	/* IEEE 802.11 + Prism2 header  */
 
 #define ARPHRD_VOID	  0xFFFF	/* Void type, nothing is known */
 

From: Stuffed Crust <[email protected]>
Date: Sat, 22 Dec 2001 00:01:05 -0500

Hey, this one-line patch (I diffed it against 2.4.17-rc2) defines the ARPHRD_IEEE80211_PRISM arp type.

Is the allocation of this number standardized somewhere?

Yes and no. There are a handful of standard hardware ARP types defined
in RFC826, I believe. [checks.] No, I guess not. But those are
definately standardized, probably by the IEEE or somesuch.

Meanwhile, the "Dummy types for non ARP hardware" list in if_arp.h seems to be the authoratitive non-standard standard, as it starts at 256 and seems to pretty much sequentially count up with the occasional large gap.

Linux's PF_SOCKET code uses this to identify the packet type coming off the wire.

The ARPHRD_IEEE80211 type was defined in 2.4.6 by incrementing the number by one and appending it to the end of the list. I just incremented the protocol number by one for the _PRISM type.

I have no idea if there was some master list somewhere; google didn't seem to return any hits other than the linux source.

- Pizza

Solomon Peachy                                    pizzaATfucktheusers.org
I ain't broke, but I'm badly bent.                           ICQ# 1318344
Patience comes to those who wait.
    ...It's not "Beanbag Love", it's a "Transanimate Relationship"...

From: Stuffed Crust <[email protected]>
Date: Sat, 22 Dec 2001 00:01:05 -0500

So, I humbly submit this patch for inclusion.

I've applied this patch.