Hi, > > Ivo, > > Don't forget that there was no response to the request for someone to test > > if broadcast packets were received in monitor mode on the older hardware > > so if the filter flags don't select multicast traffic we could be losing > > broadcast traffic too. I'm not sure if the stack will be reporting any > > active multicast groups in AP mode. (For the benefit of others the only > > reason normal broadcast traffic was working was because there was always a > > multicast group present, Ivo's request is linked below.) > > > > http://sourceforge.net/mailarchive/forum.php?thread_name=200803031921.41634.IvDoorn%40gmail.com&forum_name=rt2400-devel > > > I would like to test for this, but I'm not quite sure how, I've read > Ivo's original message, but I can't find the monitoring bug discussion > Ivo is referring to. Would the frame captures on debugfs, again with the > above mentioned tools test for this bug as well? Or is there something > else I have to do? So far I have received 1 result for the above test request which indicated rt2500pci wasn't harmed with this bug. However, latest rt2x00 has Adam's patch active for all rt2x00 drivers (since the code is now handled in rt2x00mac.c). So this means that that multicast bug should have no influence for this bug. Ivo -- 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
