On Tue, 2007-09-25 at 15:18 +0000, Matthew Garrett wrote:
> and n-m never sees the association. I suspect that this is due to the
> event coming from wifi0 rather than wlan2. I'll take a quick look at
> this, but right now I lean towards blaming the kernel.
Does it behave any differently for you if you remove the udev iface
renaming rule so that it's wifi0 and wlan0? The hostap utils have
problems when those numbers don't match. Internally the driver seems to
keep track of just the number and assumes that wifi and wlan will match.
On Tue, 2007-09-25 at 15:18 +0000, Matthew Garrett wrote:
> and n-m never sees the association. I suspect that this is due to the
> event coming from wifi0 rather than wlan2. I'll take a quick look at
> this, but right now I lean towards blaming the kernel.
Does it behave any differently for you if you remove the udev iface
renaming rule so that it's wifi0 and wlan0? The hostap utils have
problems when those numbers don't match. Internally the driver seems to
keep track of just the number and assumes that wifi and wlan will match.