From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 27 09:33:51 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 84B40106566B for ; Mon, 27 Jun 2011 09:33:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 463CF8FC15 for ; Mon, 27 Jun 2011 09:33:50 +0000 (UTC) Received: by gyf3 with SMTP id 3so2378692gyf.13 for ; Mon, 27 Jun 2011 02:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=iJ90PcdajY4CNj8JWqryLOvuomf6WBCmAkfGlEbj5NI=; b=FzSYBaypCnj/3rPQbZTj7D68IWr3VTJnV75vEFKG+U3X8hsi+HKXV2U9X//MyHcmxq S2ZxrKkjiqlCD31+OccscVI1tfi9t+DTCTN4LvSPa2fA6MJqdc8QzaVmvjdBRJk5avb5 zWlav18yXxz9U0E9gsd2ERw0IhNKYHs+XoFGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=feZxwp2EvS6bgNbvEAElJaTKwiCx1MOS9ZYhcCqlfNrrZFnAveKveW4srSp8agKuJc 2E3WMuwo5vW6TMwkGfWLZpFbynB0A9YZvtGLg1IuE5IgK31VAbllSjy5l1D++BPNSn7j +fcYmGnJ0q+A2s+uKo33YN86R7EnsQ1CobzZw= MIME-Version: 1.0 Received: by 10.150.165.14 with SMTP id n14mr6154940ybe.408.1309167230304; Mon, 27 Jun 2011 02:33:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.146.13 with HTTP; Mon, 27 Jun 2011 02:33:50 -0700 (PDT) Date: Mon, 27 Jun 2011 17:33:50 +0800 X-Google-Sender-Auth: IQt8r2ZasFNe3O3iiOqwfeMKosE Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: DFS STA/Hostap behaviour; issues! 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: Mon, 27 Jun 2011 09:33:51 -0000 After bernhard and I discussed this a bit, we came to the conclusion this is papering over bug/bugs. So what I've discovered thus far: * If a radar event occurs in CAC, another CSA doesn't go out - the AP just changes channel * If a STA receives a CSA for a DFS channel and the hostap enters CAC, it doesn't immediately send beacon frames, so bmiss is never triggered. However, because of this, if the hostap shuffles away to another channel within the CAC time, the STA doesn't ever get an initial beacon to configure the beacon config from, and thus the STA never generates a bmiss; which means it never initiates another channel scan. Getting back to the original bug: The hostap is actually sending the correct channel in the new beacon frames but there's currently no code in sta_recv_mgmt() to update the bss channel. That should occur (and similarly occur for ibss/mesh modes as well.) Adrian