Return-path: Received: from ns2.inescn.pt ([192.35.246.20]:37102 "EHLO trubo.inescn.pt" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751725AbbCKJ4M convert rfc822-to-8bit (ORCPT ); Wed, 11 Mar 2015 05:56:12 -0400 Message-ID: <20150311105604.42081tsuhqw9inn8@horde.inescporto.pt> (sfid-20150311_105616_136861_D12D4020) Date: Wed, 11 Mar 2015 10:56:04 +0100 From: =?iso-8859-1?b?TeFyaW8=?= Lopes To: Ben Greear Cc: "linux-wireless@vger.kernel.org" Subject: Re: Why can we not set the mcast rate for AP/STA interfaces? References: <54FF7095.9010800@candelatech.com> In-Reply-To: <54FF7095.9010800@candelatech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; DelSp=Yes format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On which 802.11 amendment (a/b/g/n/ac) and driver allows you setting mcast rate for mesh and IBSS interfaces? Far as I know, some vendors send multicast traffic as unicast in order to reduce airtime. Quoting Ben Greear : >> From looking at 3.17 code, it appears we are only supposed to set the > mcast rate for mesh and IBSS interfaces? > > What if I want to tell an AP or station to send broadcast/multicast > at a higher than default rate? > > Should this just be controlled by the normal 'iw setbitrates' logic? > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.