Panic in AHDEMO mode (was: net-mgmt/aircrack-ng on FreeBSD 7+ / call for testing)

PseudoCylon moonlightakkiy at yahoo.ca
Tue Oct 4 23:40:40 UTC 2011


On Tue, Oct 4, 2011 at 6:31 AM, Bernhard Schmidt <bschmidt at freebsd.org> wrote:
> On Tuesday 04 October 2011 09:33:38 Adrian Chadd wrote:
>> Well that just means the BSS isn't correctly setup. Shouldn't we just
>> fail any frames at that point? (and thus the dup'ing of a fake node
>> won't occur) ?
>> Or perhaps find out why the bss isn'et setup right and fix that?
>
> Do we know in which state the VAP was? Afaik I've added a check to
> discard frames while in SCAN state, might as well extend that to !RUN.
>

All I can say in this quick reply is when iv_newstate in RUN state
calls beacon setup function, ni_chan could still be 0xffff. I don't
remember when other 0xffff panic happened. I saw some one was
reporting the same issue with rum(4) in PR or somewhere, but I
couldn't find it.


AK


More information about the freebsd-wireless mailing list