On Tuesday 31 July 2007 23:00:43 Jiri Benc wrote: > On Tue, 31 Jul 2007 00:52:05 +0200, Ulrich Kunitz wrote: > > What about add_interface/remove_interfaces and monitor interfaces? > > It depends on the IEEE80211_HW_MONITOR_DURING_OPER flag in hw.flags. If you > set the flag in the driver, then monitor interfaces work in the exactly > same way as STA or IBSS interfaces - the add_interface callback is called > (with conf.type equal to IEEE80211_IF_TYPE_MNTR) whenever user brings up a > monitor interface. You are responsible for switching the card to a monitor > mode (e.g. turning off hardware packet filtering). I think you don't want to completely turn off packet filtering (promisc) if a monitor interface is present. The promisc bit is to be honoured seperately. The only thing we do in bcm43xx is enable passing of ctl frames (ACKs, etc), if we have a monitor interface. > > There seems to > > be also calls to add_interface/remote_interface with if_id -1. I > > guess that means something like all interfaces. The expected > > behaviour is not documented for that case. > > As Michael correctly said, don't care about the value, just store it and > hand it back to the stack when the stack wants it. That might raise the question, if it's required to store if_ids of monitor interfaces. I think it's not, as you don't need any mac80211 callback, that requires an if_id, for a monitor interface. So in bcm43xx we only store the if_id of the "operating" interface. -- Greetings Michael. - 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
