On Thu, 2007-06-21 at 13:49 -0700, Sam Leffler wrote: > This is the control state available on FreeBSD for doing raw 802.11 > frame xmit (packets need not include all this; I've just provided the > most complete set of knobs): > > uint8_t ibp_flags; > #define IEEE80211_BPF_SHORTPRE 0x01 /* tx with short preamble */ > #define IEEE80211_BPF_NOACK 0x02 /* tx with no ack */ > #define IEEE80211_BPF_CRYPTO 0x04 /* tx with h/w encryption */ > #define IEEE80211_BPF_FCS 0x10 /* frame incldues FCS */ > #define IEEE80211_BPF_DATAPAD 0x20 /* frame includes data padding */ > #define IEEE80211_BPF_RTS 0x40 /* tx with RTS/CTS */ > #define IEEE80211_BPF_CTS 0x80 /* tx with CTS only */ > uint8_t ibp_pri; /* WME/WMM AC+tx antenna */ > uint8_t ibp_try0; /* series 1 try count */ > uint8_t ibp_rate0; /* series 1 IEEE tx rate */ > uint8_t ibp_power; /* tx power (device units) */ > uint8_t ibp_ctsrate; /* IEEE tx rate for CTS */ > uint8_t ibp_try1; /* series 2 try count */ > uint8_t ibp_rate1; /* series 2 IEEE tx rate */ > uint8_t ibp_try2; /* series 3 try count */ > uint8_t ibp_rate2; /* series 3 IEEE tx rate */ > uint8_t ibp_try3; /* series 4 try count */ > uint8_t ibp_rate3; /* series 4 IEEE tx rate */ Sounds simillar to what we're trying here though Dave had some good comments that equally well apply here. I expect I'll be posting a radiotap patch, maybe you can comment on that then? Even wrt. how well you could implement this, possibly even on top of those fields you have. > Note that using a monitor mode interface for transmit is a bad idea. It > is likely you will encounter devices that disallow any packet transmit > when operating in monitor mode. In practice this can be worked around > by using a non-monitor operating mode for the device (e.g. adhoc mode > w/o setting up beacons) but exporting this notion to user mode is bad > IMO. In net80211 there is an adhoc-demo mode which is essentially adhoc > mode which was originally added for functionality found in old lucent > cards but more recently has been used for building applications that > want a "raw 802.11 device". There's a tradeoff here; the actual notion to userspace ought to be a monitor interface because that is what tools need to have opened anyway. It is also natural to use from userspace via libpcap. Also, most modern hardware doesn't actually care what you send. If we ever end up being able to support such cards that do care, then I expect we'll either be able to work around the problem in the driver or need some special instructions for users of such hardware. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
