Return-path: Received: from mail-yx0-f174.google.com ([209.85.213.174]:48274 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582Ab1ALKnp (ORCPT ); Wed, 12 Jan 2011 05:43:45 -0500 Received: by yxt3 with SMTP id 3so158742yxt.19 for ; Wed, 12 Jan 2011 02:43:44 -0800 (PST) Subject: Re: Mesh join/leave From: Steve Brown Reply-To: sbrown@cortland.com To: Johannes Berg Cc: "linux-wireless@vger.kernel.org" In-Reply-To: <1294823034.3639.15.camel@jlt3.sipsolutions.net> References: <1294780828.2383.0.camel@mythtv.ewol.com> <1294823034.3639.15.camel@jlt3.sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Date: Wed, 12 Jan 2011 05:43:37 -0500 Message-ID: <1294829017.2347.2.camel@mythtv.ewol.com> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2011-01-12 at 10:03 +0100, Johannes Berg wrote: > On Tue, 2011-01-11 at 16:20 -0500, Steve Brown wrote: > > In testing this, the command "iw mesh0 mesh leave" doesn't stop > > beaconing. Beaconing continues with a null mesh id. > > > > Is this the intended behavior? > > No, it's not -- what driver are you using? > > johannes > The ath5k driver behaves differently. On "leave" it stops beaconing and on "join", starts back up. Steve