Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] going back to the default multicast rate on wifi
Date: Mon, 10 Feb 2014 19:39:40 +0100	[thread overview]
Message-ID: <5F676BC3-1164-42EF-A2A9-612CD53EAC04@gmx.de> (raw)
In-Reply-To: <CAA93jw5efyb3csOSLPyZSxzGo8MmKb_oOcq0in3EoDVp-734Cw@mail.gmail.com>

Hi Dave,

On Feb 10, 2014, at 18:48 , Dave Taht <dave.taht@gmail.com> wrote:

> Despite success with a variety of devices in increasing cerowrt's
> multicast rate from 1mbit to 9, I have found two that can't handle it,
> notably an older android tablet (the original nexus 7), and an iwl
> wifi card.
> 
> The value I used for this option in /etc/config/wireless was derived
> from what freifunct uses for their mesh network. It makes sense to run
> the mesh at this rate, but apparently not APs.
> 
> So if you have been experiencing problems getting boxes to connect to
> the last couple comcast versions of cero, go into that file and
> comment out these entries.
> 
> #       option mcast_rate '9000'
> 
> Those of you with success stories on this setting please share them.

	So, here I go: cerowrt 3.10.28-1, 16GB nexus7 wifi only (first generation, but not first batch, from just after the entry model was upgraded to 16GB) works fine on the 2.4GHz network with the following in config wifi-iface
        option mcast_rate '9000'
Since I also have no problems using ht40+ on channel 44, maybe it is related to my choice of "option country 'DE'" ?

Also working are a macbook and a macbook pro and two nexus 4s, no issues so far.

best regards
	Sebastian



> 
> I don't think this has anything to do with the the ht40+ MCS15 problem at 5ghz.
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  parent reply	other threads:[~2014-02-10 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 17:48 Dave Taht
2014-02-10 17:57 ` Daniel Ezell
2014-02-10 18:39 ` Sebastian Moeller [this message]
2014-02-10 20:18   ` Aaron Wood
2014-02-11 13:34     ` Aaron Wood
2014-02-11 13:54       ` Aaron Wood
2014-02-11 14:23         ` Fred Stratton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5F676BC3-1164-42EF-A2A9-612CD53EAC04@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox