On Fri, Aug 03, 2007 at 11:54:54AM +0200, Johannes Berg wrote: > On Fri, 2007-08-03 at 08:59 +0100, Andy Green wrote: > > > There seems to be some agreement that in the future the number of > > virtual interfaces that happen to be lying around shouldn't determine > > the functionality of Monitor mode like that. > > I think that only happens if you don't have monitor_during_oper set; > otherwise it's a bug. > > I am, however, not entirely sure we should be forwarding packets with > failed CRC on hard monitor interfaces. Because if you have both a hard > monitor and a regular interface (monitor_during_oper allowed) then we > will never check the CRC on frames that enter the networking path and > can get corrupted TCP packets in etc. Having that as a configurable option that defaults to off (no invalid frames) would be the ideal solution :-) Ciao Joerg -- Joerg Mayer <jmayer@xxxxxxxxx> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - 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