Date: Tue, 4 Oct 2011 17:27:44 -0600 From: PseudoCylon <moonlightakkiy@yahoo.ca> To: Bernhard Schmidt <bschmidt@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Panic in AHDEMO mode (was: net-mgmt/aircrack-ng on FreeBSD 7+ / call for testing) Message-ID: <CAFZ_MYKFf8_9Td-JuisxmaSfDT1ECe3qDYH8cTGc81P523h9rQ@mail.gmail.com> In-Reply-To: <201110041431.39599.bschmidt@freebsd.org> References: <CAFZ_MYJEV24QLD%2BhOE%2Bzh331xWp2_cnLu7GwV8rT-roi1qYv5Q@mail.gmail.com> <CAJ-Vmo=M7NN=k4K=t-PK0hUQ7mjQkdvSN3etK3_MNjuCReXErA@mail.gmail.com> <201110041431.39599.bschmidt@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 4, 2011 at 6:31 AM, Bernhard Schmidt <bschmidt@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFZ_MYKFf8_9Td-JuisxmaSfDT1ECe3qDYH8cTGc81P523h9rQ>