Trusting firmware logs, it uses both active and passive scans. As to why, I don't know, though I suppose it'd make sense to let the wireless card handle scanning unless some condition arised which led NM to think it would have to roam soon. On Fri, Nov 25, 2011 at 7:00 AM, Kalle Valo <kvalo@xxxxxxxxxx> wrote: > Pedro Francisco <pedrogfrancisco@xxxxxxxxx> writes: > >> >> I was able to trigger the firmware error by doing "iw dev wlan0 scan >> passive". By comparison, "iw dev wlan0 scan" does NOT trigger the >> firmware error. > > So NM uses passive scan? Now I'm curious, why is that? > -- 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
