From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 5 11:10:12 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 948761065670; Wed, 5 Oct 2011 11:10:12 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 4519B8FC1A; Wed, 5 Oct 2011 11:10:11 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mail.0x20.net (Postfix) with ESMTP id A34B96A61CC; Wed, 5 Oct 2011 12:52:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.0x20.net Received: from mail.0x20.net ([217.69.76.211]) by mail.0x20.net (mail.0x20.net [217.69.76.211]) (amavisd-new, port 10024) with ESMTP id HXWbfiddyjWN; Wed, 5 Oct 2011 12:52:16 +0200 (CEST) Received: from e-new.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 63CA66A6004; Wed, 5 Oct 2011 12:52:16 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.4/8.14.4) with ESMTP id p95AqGh0077969; Wed, 5 Oct 2011 12:52:16 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.4/8.14.4/Submit) id p95AqFae077338; Wed, 5 Oct 2011 12:52:15 +0200 (CEST) (envelope-from lars) Date: Wed, 5 Oct 2011 12:52:15 +0200 From: Lars Engels To: PseudoCylon Message-ID: <20111005105215.GH76761@e-new.0x20.net> References: <201110041431.39599.bschmidt@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3VRmKSg17yJg2MZg" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.2-RELEASE-p3 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Panic in AHDEMO mode (was: net-mgmt/aircrack-ng on FreeBSD 7+ / call for testing) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 11:10:12 -0000 --3VRmKSg17yJg2MZg Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 04, 2011 at 05:27:44PM -0600, PseudoCylon wrote: > On Tue, Oct 4, 2011 at 6:31 AM, Bernhard Schmidt w= rote: > > 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. > > >=20 > 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. Can I assist somehow? Do you need more details how my machine crashed? --3VRmKSg17yJg2MZg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk6MNt8ACgkQKc512sD3afgT8QCfQHFMmB6j1WHJvYfnD4b7sPfz Ve4An1RQcBK5ViQx5ih69osqgpyW+lOg =ImXo -----END PGP SIGNATURE----- --3VRmKSg17yJg2MZg--