From: David Lang <david@lang.hm>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] sigcomm wifi
Date: Fri, 22 Aug 2014 16:30:29 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1408221629530.19968@nftneq.ynat.uz> (raw)
In-Reply-To: <20140821093048.GA26169@sesse.net>
On Thu, 21 Aug 2014, Steinar H. Gunderson wrote:
> On Thu, Aug 21, 2014 at 11:23:01AM +0200, Mikael Abrahamsson wrote:
>> I also remember a problem that was solved by turning down the
>> transmit power of the APs, as they were causing problems due to too
>> much interference between them. Sometimes the solutions aren't all
>> intuitive, and +1 on the experience of running these kinds of
>> networks being important.
>
> This is very common on 2.4 GHz (and will happen by itself in a
> controller-based setup). Anything that reduces the cell size is good
> (assuming you have enough APs for all the resulting cells); if you go to big
> stadiums etc., you will also see lots of directional antennas to reduce the
> cell size further.
>
> Note that the AP also can ask _clients_ to reduce their power level
> accordingly.
can you give a pointer to this? I'd like to check if openwrt does this and how
to configure it (and if not, what would it take to get it added)
David Lang
next prev parent reply other threads:[~2014-08-22 23:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:45 Dave Taht
2014-08-20 7:12 ` Eggert, Lars
2014-08-20 14:01 ` Dave Taht
2014-08-20 22:05 ` Jim Gettys
2014-08-21 6:52 ` Eggert, Lars
2014-08-21 7:11 ` Michael Welzl
2014-08-21 8:30 ` David Lang
2014-08-22 23:07 ` Michael Welzl
2014-08-22 23:50 ` David Lang
2014-08-23 19:26 ` Michael Welzl
2014-08-23 23:29 ` Jonathan Morton
2014-08-23 23:40 ` Steinar H. Gunderson
2014-08-23 23:49 ` Jonathan Morton
2014-08-24 1:33 ` David Lang
2014-08-24 2:29 ` Jonathan Morton
2014-08-24 5:12 ` David Lang
2014-08-24 6:26 ` Jonathan Morton
2014-08-24 8:24 ` David Lang
2014-08-24 9:20 ` Jonathan Morton
2014-08-25 7:25 ` Michael Welzl
2014-08-30 7:20 ` Jonathan Morton
2014-08-31 20:46 ` Simon Barber
2014-08-25 7:35 ` Michael Welzl
2014-08-24 1:09 ` David Lang
2014-08-25 8:01 ` Michael Welzl
2014-08-25 8:19 ` Sebastian Moeller
2014-08-25 8:33 ` Michael Welzl
2014-08-25 9:18 ` Alex Burr
2014-08-31 22:37 ` David Lang
2014-08-31 23:09 ` Simon Barber
2014-09-01 0:25 ` David Lang
2014-09-01 2:14 ` Simon Barber
2014-08-31 22:35 ` David Lang
2014-08-21 6:56 ` David Lang
2014-08-21 7:04 ` David Lang
2014-08-21 9:46 ` Jesper Dangaard Brouer
2014-08-21 19:49 ` David Lang
2014-08-21 19:57 ` Steinar H. Gunderson
2014-08-22 17:07 ` Jan Ceuleers
2014-08-22 18:27 ` Steinar H. Gunderson
2014-08-21 8:58 ` Steinar H. Gunderson
2014-08-22 23:34 ` David Lang
2014-08-22 23:41 ` Steinar H. Gunderson
2014-08-22 23:52 ` David Lang
2014-08-22 23:56 ` Steinar H. Gunderson
2014-08-23 0:03 ` Steinar H. Gunderson
2014-08-21 9:23 ` Mikael Abrahamsson
2014-08-21 9:30 ` Steinar H. Gunderson
2014-08-22 23:30 ` David Lang [this message]
2014-08-22 23:40 ` Steinar H. Gunderson
2014-08-20 8:30 ` Steinar H. Gunderson
2014-08-21 6:58 ` David Lang
2014-08-24 3:49 Hal Murray
2014-08-24 3:52 ` Jonathan Morton
2014-08-24 5:14 ` David Lang
2014-08-25 7:43 ` Michael Welzl
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1408221629530.19968@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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