From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-yx0-f192.google.com ([209.85.210.192]:53756 "EHLO mail-yx0-f192.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751997AbZFSR0K convert rfc822-to-8bit (ORCPT ); Fri, 19 Jun 2009 13:26:10 -0400 Received: by yxe30 with SMTP id 30so2663181yxe.4 for ; Fri, 19 Jun 2009 10:26:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <45e8e6c40906191000i2e74e06btee7313c5c30bc6a2@mail.gmail.com> References: <4A3B5B11.7060103@bitnet.be> <45e8e6c40906191000i2e74e06btee7313c5c30bc6a2@mail.gmail.com> Date: Fri, 19 Jun 2009 13:19:54 -0400 Message-ID: Subject: Re: current status of 802.11s mesh in ath5k ? From: Bob Copeland To: Andrey Yurovsky Cc: Hans Maes , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Jun 19, 2009 at 1:00 PM, Andrey Yurovsky wrote: > You'll want wireless-testing (or the latest compat), after commit > 41ba08509.  However ath5k will not beacon until you issue a scan due > to a bug. By the way, I imagine this is a side effect of calling ath5k_beacon_config inside ath5k_reset(). If so, we probably want to call it at the appropriate time when the interface is brought up. I have been working on a patch to rework the beaconing, namely using bss_conf->enable_beacon and calling beacon_config whenever the beacon interval or beacon changes, that might fix it but I'm not too familiar with mesh details to say. -- Bob Copeland %% www.bobcopeland.com