From owner-freebsd-wireless@FreeBSD.ORG Wed May 8 02:53:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D7E1C74A; Wed, 8 May 2013 02:53:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by mx1.freebsd.org (Postfix) with ESMTP id 3C604EFE; Wed, 8 May 2013 02:53:23 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id m15so1389946wgh.5 for ; Tue, 07 May 2013 19:53:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VnV+LuyiXbb2yL9NhPVM1Or7AZWgOJD9lFY7/Hf03lA=; b=eHmwF6sTAmWO9Y5QS/nnSfBjfS9wzth69pwoTSqfRPP5xYI7MBPH6cp+USdQSJPlbn +Nv6Vpqjiv/7ZCKIs5vKXoJwYf+zU0Fl8HJE8hnyG7pV8QyiFtgbL5c51BvtUmukFaiy 9P+npJTM8IzF9gbXbJdyk+Xz+Yz/CVsPmx/sZlertxsDKVVkQ7TaToqMOE2AiZgxf3k1 /ID7MlxpB8sEvOoSi5LPxS8M58bDyQu8KnmLAPsHEJ2TMBNZkh5R9G6QqaeUu8jDmxYF 165ymZqnsmkgqldSPhivVzbHda9O7416/nkE05PaDQF0sNQ/PdzW+6J3bYpaHapD4quh Umzg== MIME-Version: 1.0 X-Received: by 10.180.89.140 with SMTP id bo12mr4076617wib.22.1367981602390; Tue, 07 May 2013 19:53:22 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 7 May 2013 19:53:22 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> <94971208.20130503122811@serebryakov.spb.ru> Date: Tue, 7 May 2013 19:53:22 -0700 X-Google-Sender-Auth: 3kDpMMfkd0kYQRYv8hD3T_NjeY4 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 08 May 2013 02:53:23 -0000 Hi Lev (and others); I've fixed the UDP TX + rekey session drop bug. Please re-test your testcase on the latest -HEAD and let me know how it goes. I'd really like to sneak in these power save and reassociate changes of mine, but first I want to make sure that your issue is correctly resolved. Thanks! Adrian On 3 May 2013 22:09, Adrian Chadd wrote: > Hi, > > So doing this testing as a station doing the UDP transmitting (to a > FreeBSD AP) is showing some interesting behaviour. No, i don't think > it's your bug. > > The key re-negotiation seems to be failing somewhere; I bet it's out > of sequence or out of order crypto frames. I've seen this happen > before but I only fixed it for the AP case (by overriding the QOS for > said frames so it appeared in a different TID, thus different sequence > number space.) Since it's reauthing, it's transitioning the node > through disassociate / re-auth / re-associate, but the current code in > -HEAD isn't resetting the local state (aggregation, BAR state, > filtered frames state, etc.) So things can and do go weird. > > I'll do some further digging into this and see if I can resolve it. I > thought I had fixed it but .. well, obviously not. Once I have > resolved this rekey / disconnect issue I'll keep testing things out > and see if I've fixed your issue. > > (And I'll do some testing in parallel in open mode, so I don't bite this bug.) > > > > adrian