The idea is this: I operate an AP on one channel that talks to some set of devices. On another "channel" (maybe just different BW) I use packet injection to send data to and from a separate device. The bitrate to the 2nd device (on the 2nd channel) is much lower than that of the AP, and I'd like to get longer range out of it. The idea is that I use narrower bandwidth and fixed, low bitrates with control over the retries to get really tight control over that link. Thats the idea, anyway... On Wed, Aug 19, 2015 at 11:09 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2015-08-19 at 09:37 -0700, Allan Matthew wrote: > >> It seems like the functionality for this (maybe not the monitor mode) >> must be available in order to support the multiple 802.11p channels >> in the 5.8ghz band. > > Not sure - I haven't looked at WAVE/11p in a long time, but the code we > have certainly assumes that the channel configuration is fixed, i.e. > only done once when "joining" the network. > >> It sounds like what you are proposing is to create a non-monitor vif, >> select its channel, bitrate, bandwidth and then use the MAC address >> to >> select it as the transmitting interface. Is that correct? I'm >> guessing I could do this with raw sockets and prepend the ieee80211 >> header (but not the radiotap header)? >> > > No - radiotap injection has code to select the interfaces. So if you > have hardware that's capable of, say, having two AP interfaces on > different channels, then injection would select the channel by > selecting the interface. However, this isn't really a good way of > handling this either. > > If you can be more specific what this would be used for, perhaps kernel > modifications would be appropriate to support it more correctly (rather > than relying on injection.) > > johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
