Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Tue, 17 Dec 2013 13:51:54 -0500	[thread overview]
Message-ID: <CAGhGL2Cd-g2j7f==3cpUFTRHyTQCkhmkyha20wZSw0aRWJTn4A@mail.gmail.com> (raw)
In-Reply-To: <18972.1387302855@sandelman.ca>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

On Tue, Dec 17, 2013 at 12:54 PM, Michael Richardson <mcr@sandelman.ca>wrote:

>
> Fred Stratton <fredstratton@imap.cc> wrote:
>     > For best 5GHz results, get rid of your walls and doors...
>
>     >
> http://www.theregister.co.uk/2011/09/14/virgin_media_superhub_update_modem_mode/
>
> Yeah, in my house, my experience with 5Ghz is that it means the network
> doesn't work.
>

I sometimes have a similar situation in my house.  And I live in a radio
quiet area, so I don't face the usual tradeoff of polluted 2.4ghz.


But it does make it very hard to simply recommend 5 over 2.4ghz; there is
no single "right answer"; the answer is "it depends" for the simple one
router case.

And the right solution is more routers, and using 5ghz once you have them.

Sigh...
                          - Jim



>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2630 bytes --]

  reply	other threads:[~2013-12-17 18:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 19:46 Dave Taht
2013-12-16 20:19 ` Sebastian Moeller
2013-12-16 20:25 ` Toke Høiland-Jørgensen
2013-12-16 20:48 ` Kelvin Edmison
2013-12-16 21:28 ` David Lang
2013-12-16 22:06   ` Fred Stratton
2013-12-17 17:54     ` Michael Richardson
2013-12-17 18:51       ` Jim Gettys [this message]
2013-12-17 22:25         ` dpreed
2013-12-17 22:32           ` Jim Gettys
2013-12-17 23:43             ` Stephen Hemminger
2013-12-18  1:33               ` Theodore Ts'o
2013-12-18  3:04                 ` David Lang
2013-12-18  5:05                   ` Theodore Ts'o
2013-12-18  5:49                     ` David Lang
2013-12-18 14:17                 ` Chuck Anderson
2013-12-18 15:19               ` dpreed
2013-12-18 16:54                 ` Michael Richardson
2013-12-18 18:18                   ` Toke Høiland-Jørgensen
2013-12-18 19:24                     ` David Lang
2013-12-18 20:07                       ` Michael Richardson
2013-12-18 20:14                         ` David Lang
2013-12-19  9:31                           ` Toke Høiland-Jørgensen
2013-12-19 14:32                             ` Michael Richardson
2013-12-19 20:05                             ` David Lang
2013-12-19 21:01                               ` Chuck Anderson
2013-12-20  0:50                 ` Theodore Ts'o
2013-12-20  5:18                   ` dpreed
2013-12-18 14:06           ` Michael Richardson
2013-12-27 23:56 ` Maciej Soltysiak

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='CAGhGL2Cd-g2j7f==3cpUFTRHyTQCkhmkyha20wZSw0aRWJTn4A@mail.gmail.com' \
    --to=jg@freedesktop.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    /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