From: Bob McMahon <bob.mcmahon@broadcom.com>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] more well funded attempts showing market demand for better wifi
Date: Thu, 23 Jun 2016 20:28:30 -0000 [thread overview]
Message-ID: <CAHb6Lvq+oh7N1PbG-cHk5nH4mC-DOri1wPDreKsihEUhXsW+WQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1606231308190.2044@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 4137 bytes --]
An AP per room/area, reducing the tx power (beacon range) has been my
approach and has scaled very well. It does require some wires to each AP
but I find that paying an electrician to run some quality wiring to things
that are to remain stationary has been well worth the cost.
just my $0.02,
Bob
On Thu, Jun 23, 2016 at 1:10 PM, David Lang <david@lang.hm> wrote:
> Well, just using the 5GHz DFS channels in 80MHz or 160 MHz wide chunks
> would be a huge improvement, not many people are using them (yet), and the
> wide channels let you get a lot of data out at once. If everything is
> within a good range of the AP, this would work pretty well. If you end up
> needing multiple APs, or you have many stations, I expect that you will be
> better off with more APs at lower power, each using different channels.
>
> David Lang
>
>
>
>
> On Thu, 23 Jun 2016, Bob McMahon wrote:
>
> Date: Thu, 23 Jun 2016 12:55:19 -0700
>> From: Bob McMahon <bob.mcmahon@broadcom.com>
>> To: Dave Taht <dave.taht@gmail.com>
>> Cc: make-wifi-fast@lists.bufferbloat.net,
>> "cerowrt-devel@lists.bufferbloat.net"
>> <cerowrt-devel@lists.bufferbloat.net>
>> Subject: Re: [Make-wifi-fast] more well funded attempts showing market
>> demand
>> for better wifi
>>
>>
>> hmm, I'm skeptical. To use multiple carriers simultaneously is difficult
>> per RF issues. Even if that is somehow resolved, to increase throughput
>> usually requires some form of channel bonding, i.e. needed on both sides,
>> and brings in issues with preserving frame ordering. If this is just
>> channel hopping, that needs coordination between both sides (and isn't
>> simultaneous, possibly costing more than any potential gain.) An AP only
>> solution can use channel switch announcements (CSA) but there is a cost to
>> those as well.
>>
>> I guess don't see any break though here and the marketing on the site
>> seems
>> to indicate something beyond physics, at least the physics that I
>> understand. Always willing to learn and be corrected if I'm
>> misunderstanding things.
>>
>> Bob
>>
>> On Wed, Jun 22, 2016 at 10:18 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> On Wed, Jun 22, 2016 at 10:03 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>>>
>>>>
>>> https://www.kickstarter.com/projects/portalwifi/portal-turbocharged-wifi?ref=backerkit
>>>
>>>>
>>>> "Portal is the first and only router specifically engineered to cut
>>>> through and avoid congestion, delivering consistent, high-performance
>>>> WiFi with greater coverage throughout your home.
>>>>
>>>> Its proprietary spectrum turbocharger technology provides access to
>>>> 300% more of the radio airwaves than any other router, improving
>>>> performance by as much as 300x, and range and coverage by as much as
>>>> 2x in crowded settings, such as city homes and multi-unit apartments"
>>>>
>>>> It sounds like they are promising working DFS support.
>>>>
>>>
>>> It's not clear what chipset they are using (they are claiming wave2) -
>>> but they are at least publicly claiming to be using openwrt. So I
>>> threw in enough to order one for september, just so I could comment on
>>> their kickstarter page. :)
>>>
>>> I'd have loved to have got in earlier (early shipments are this month
>>> apparently), but those were sold out.
>>>
>>>
>>>
>>> https://www.kickstarter.com/projects/portalwifi/portal-turbocharged-wifi/comments
>>>
>>>
>>>
>>>> --
>>>> Dave Täht
>>>> Let's go make home routers and wifi faster! With better software!
>>>> http://blog.cerowrt.org
>>>>
>>>
>>>
>>>
>>> --
>>> Dave Täht
>>> Let's go make home routers and wifi faster! With better software!
>>> http://blog.cerowrt.org
>>> _______________________________________________
>>> Make-wifi-fast mailing list
>>> Make-wifi-fast@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>>>
>>>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
>
[-- Attachment #2: Type: text/html, Size: 6375 bytes --]
next prev parent reply other threads:[~2016-06-23 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 17:03 [Cerowrt-devel] " Dave Taht
2016-06-22 17:18 ` Dave Taht
2016-06-22 18:08 ` Dave Taht
2016-06-23 19:55 ` [Cerowrt-devel] [Make-wifi-fast] " Bob McMahon
2016-06-23 20:10 ` David Lang
2016-06-23 20:28 ` Bob McMahon [this message]
2016-06-23 20:35 ` David Lang
2016-06-23 20:48 ` dpreed
2016-06-23 20:52 ` David Lang
2016-06-23 21:08 ` dpreed
2016-06-23 21:41 ` Bob McMahon
2016-06-24 2:14 ` David Lang
2016-06-24 3:01 ` Bob McMahon
2016-06-24 5:19 ` David Lang
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=CAHb6Lvq+oh7N1PbG-cHk5nH4mC-DOri1wPDreKsihEUhXsW+WQ@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--cc=make-wifi-fast@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