From owner-freebsd-wireless@freebsd.org Sat Oct 22 19:46:32 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 14234C1DED1 for ; Sat, 22 Oct 2016 19:46:32 +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 03B78A55 for ; Sat, 22 Oct 2016 19:46:32 +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 u9MJkVts006894 for ; Sat, 22 Oct 2016 19:46:31 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 19:46:32 +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 19:46:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213621 --- Comment #7 from Adrian Chadd --- God damnit, okay. So it /looks/ like a single bit corruption of the RSC, wh= ich causes the AES-CCM code to consider everything afterwards to be a replay attack. ie: Adrians-MacBook-Pro:~ adrian$ perl -e 'printf "%x\n", 3407656;' 33ff28 Adrians-MacBook-Pro:~ adrian$ perl -e 'printf "%x\n", 2150891303;' 8033ff27 Those are from your AES-CCM replay logs. I would've thought that a single bit error would've been caught by the MAC CRC/FCS. -adrian --=20 You are receiving this mail because: You are the assignee for the bug.=