From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Wed, 18 Dec 2013 11:54:41 -0500 [thread overview]
Message-ID: <18235.1387385681@sandelman.ca> (raw)
In-Reply-To: <1387379970.401720581@apps.rackspace.com>
dpreed@reed.com wrote:
> The other problem is antenna directionality for the transmit and receive
> antennas. Indeed almost all AP antennas have flattened doughnut radiation
> patterns in free-space. Worse, however, is that indoors, the antenna patterns
> are shaped by reflectors and absorbers so that the energy is highly
> variable,
Is the donut aligned with the flat direction of the 3800, or another
direction?
My 3800 is mounted on a (concrete) wall, just below ground level in my
basement. I have good 2.4Ghz coverage in my bedroom, two stories up.
(This is constrast to the 54gl I used to use, which was above my TV in the
den, but it was just an AP-router. My 3800 is next to the 24-port switch,
and the DSL modem, since it does everything. Another 3800 is going into the
attic, as soon as I dig through the insulation to run cables)
As for having identical ESSID on the same layer-2... I think that perhaps
cerowrt/openwrt/homenet should consider a wireless AP discovery attribute in
the routing protocol, and given that, run GRE over IPv6 ULA between APs.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2013-12-18 16:54 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
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 [this message]
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=18235.1387385681@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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