On Thu, 2008-06-12 at 09:26 +0200, Johannes Berg wrote: > All your description makes a lot of sense, but I don't see why altering > the bridge code is necessary. In mac80211, we decided that the "promisc" > bit only means to capture all frames in the current BSS (remember that > in ethernet there is no way to capture frames from different LAN > segments) and hence an AP would not behave differently in promisc mode > at all since, by definition, it sees all BSS traffic. You are right, within the BSS every frame is going to be addressed to the AP anyway, so we should not receive more or less frames when activating promiscuous mode. When activating promiscuous mode in this device, it stops acknowledging frames, and this impairs the association process. The other solution would be to ignore the promiscuous mode commands (i.e. never send the command to the device) for interfaces in AP mode. If this is the only device showing this behavior, maybe that would be the best solution. -- Luis Carlos Cobo Rus GnuPG ID: 44019B60 cozybit Inc. -- 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
