From owner-freebsd-wireless@freebsd.org Sat Oct 22 20:30:16 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91DBEC1D0FD for ; Sat, 22 Oct 2016 20:30:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8159E922 for ; Sat, 22 Oct 2016 20:30:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9MKUGal036171 for ; Sat, 22 Oct 2016 20:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213621] WIFI connection is lost periodically on ath0 Date: Sat, 22 Oct 2016 20:30:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 22 Oct 2016 20:30:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213621 --- Comment #12 from Adrian Chadd --- Hiya, So the beacon miss / TSFOOR is the driver side. I can go take another look = at fixing that up. The CCMP replay attack thing - that we need another NIC to sniff the air in monitor mode and try to capture the invalid PN showing up in the air. If it= 's coming over the air then sure, we can nail it down. If it's not coming over= the air, and instead it's corrupted by the AR9380 NIC, we're in trouble. I need to go double / triple-check to see if we pass frames that fail CRC/FCS/decrypt up to the stack for incorrect processing. I'm kinda worried that we're processing invalid frames a little too far along the input / decryption path. --=20 You are receiving this mail because: You are the assignee for the bug.=