Somebody in the thread at some point said: > Well, for one, the PS code is only relevant if we're ourselves operating > in IBSS or AP mode. If we're operating in AP/IBSS mode we'll also > automatically buffer your injected multicast frames for after the DTIM > beacon. I think we should just buffer injected unicast frames as well, > it won't hurt your use case (multicast destination) and makes things > more consistent. Fine by me. >> For sure things will be much better and more consistent if we can inject >> down unassociated interfaces reliably, so this is a nice move. > > Well, no, that's unrelated, and it's a bug in iwlwifi that it craps out > over that ;) There are other problems hiding somewhere, perhaps iwl3945, as well. Having a secondary network interface like mon0 in Monitor mode is still not quite the same as having the primary network interface in Monitor mode. Externally generated Packetspammer broadcasts are not visible down a monitor mode secondary network interface with current wireless-dev on iwl3945 in the case where it is associated to a network and a secondary network interface is in Monitor mode. Deassociate and stick the wlan0 interface in Monitor mode though (without changing or deleting the mon0 interface) and you suddenly see the packetspammer broadcasts from the other box just fine. -Andy - 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
