From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: dan <dandenson@gmail.com>, Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
Bruce Perens <bruce@perens.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] [Bloat] [Starlink] [LibreQoS] On FiWi
Date: Wed, 15 Mar 2023 12:39:39 -0700 [thread overview]
Message-ID: <CAA93jw677LrJODdW+bGYG8b3_jcOMYNX0D77k_H508WronT=Xg@mail.gmail.com> (raw)
In-Reply-To: <48q03o08-ro20-2p59-1644-sp73526024q3@ynat.uz>
On Wed, Mar 15, 2023 at 12:33 PM David Lang via Rpm
<rpm@lists.bufferbloat.net> wrote:
>
> if you want another example of the failure, look at any conference center, they
> have a small number of APs with wide coverage. It works well when the place is
> empty and they walk around and test it, but when it fills up with users, the
> entire network collapses.
>
> Part of this is that wifi was really designed for sparse environments, so it's
> solution to "I didn't get my message through" is to talk slower (and louder if
> possible), which just creates more interference for other users and reduces the
> available airtime.
>
> I just finished the Scale conference in Pasadena, CA. We deployed over 100 APs
> for the conference, up to 7 in a room, on the floor (so that the attendees
> bodies attenuate the signal) at low power so that the channels could be re-used
> more readily.
How did it go? You were deploying fq_codel on the wndr3800s there as
of a few years ago, and I remember you got rave reviews... (can you
repost the link to that old data/blog/podcast?)
Did you get any good stats?
Run cake anywhere?
>
> in the cell phone world they discovered 'microcells' years ago, but with wifi
> too many people are still trying to cover the max area with the fewest possible
> number of radios. As Dan says, it just doesn't work.
>
> and on mesh radios, you need to not just use a different channel for your
> uplink, you need a different band to avoid desense on the connection to your
> users. And that uplink is going to have the same hidden transmitter and airtime
> problems competing with the other nodes also doing the uplink that it's
> scalability is very limited (even with directional antennas). Wire/fiber for the
> uplink is much better.
>
> David Lang
>
>
>
> On Wed, 15 Mar
> 2023, dan via Bloat wrote:
>
> > Trying to do all of what is currently wanted with 1 AP in a house is a huge
> > part of the current problems with WiFi networks. MOAR power to try to
> > overcome attenuation and reflections from walls so more power bleeds into
> > the next home/suite/apartment etc.
> >
> > In the MSP space it's been rapidly moving to an AP per room with output
> > turned down to minimum. Doing this we can reused 5Ghz channels 50ft away
> > (through 2 walls etc...) without interference.
> >
> > One issue with the RRH model is that to accomplish this 'light bulb' model,
> > ie you put a light bulb in the room you want light, is that it requires
> > infrastructure cabling. 1 RRH AP in a house is already a failure today and
> > accounts for most access complaints.
> >
> > Mesh radios have provided a bit of a gap fill, getting the access SSID
> > closer to the device and backhauling on a separate channel with better (and
> > likely fixed position ) antennas.
> >
> > regardless of my opinion on the full on failure of moving firewall off prem
> > and the associated security risks and liabilities, single AP in a home is
> > already a proven failure that has given rise to the mesh systems that are
> > top sellers and top performers today.
> >
> > IMO, there was a scheme that gained a moment of fame and then died out of
> > powerline networking and an AP per room off that powerline network. I have
> > some of these deployed with mikrotik PLA adapters and the model works
> > fantastically, but the powerline networking has evolved slowly so I'm
> > seeing ~200Mbps practical speeds, and the mikrotik units have 802.11n
> > radios in them so also a bit of a struggle for modern speeds. This model,
> > with some development to get ~2.5Gbps practical speeds, and WiFi6 or WiFi7
> > per room at very low output power, is a very practical and deployable by
> > consumers setup.
> >
> > WiFi7 also solves some pieces of this with AP coordination and
> > co-transmission, sort of like a MUMIMO with multiple APs, and that's in
> > early devices already (TPLINK just launched an AP).
> >
> > IMO, too many hurdles for RRH models from massive amounts of unfrastructure
> > to build, homes and appartment buildings that need re-wired, security and
> > liability concerns of homes and business not being firewall isolated by
> > stakeholders of those networks.
> >
> > On Wed, Mar 15, 2023 at 11:32 AM rjmcmahon <rjmcmahon@rjmcmahon.com> wrote:
> >
> >> The 6G is a contiguous 1200MhZ. It has low power indoor (LPI) and very
> >> low power (VLP) modes. The pluggable transceiver could be color coded to
> >> a chanspec, then the four color map problem can be used by installers
> >> per those chanspecs. https://en.wikipedia.org/wiki/Four_color_theorem
> >>
> >> There is no CTS with microwave "interference" The high-speed PHY rates
> >> combined with low-density AP/STA ratios, ideally 1/1, decrease the
> >> probability of time signal superpositions. The goal with wireless isn't
> >> high densities but to unleash humans. A bunch of humans stuck in a dog
> >> park isn't really being unleashed. It's the ability to move from block
> >> to block so-to-speak. FiWi is cheaper than sidewalks, sanitation
> >> systems, etc.
> >>
> >> The goal now is very low latency. Higher phy rates can achieve that and
> >> leave the medium free the vast most of the time and shut down the RRH
> >> too. Engineering extra capacity by orders of magnitude is better than
> >> AQM. This has been the case in data centers for decades. Congestion? Add
> >> a zero (or multiple by 10)
> >>
> >> Note: None of this is done. This is a 5-10 year project with zero
> >> engineering resources assigned.
> >>
> >> Bob
> >>> On Tue, Mar 14, 2023 at 5:11 PM Robert McMahon
> >>> <rjmcmahon@rjmcmahon.com> wrote:
> >>>
> >>>> the AP needs to blast a CTS so every other possible conversation has
> >>>> to halt.
> >>>
> >>> The wireless network is not a bus. This still ignores the hidden
> >>> transmitter problem because there is a similar network in the next
> >>> room.
> >>
> >_______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
--
Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2023-03-15 19:39 UTC|newest]
Thread overview: 148+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>
[not found] ` <1672786712.106922180@apps.rackspace.com>
[not found] ` <F4CA66DA-516C-438A-8D8A-5F172E5DFA75@cable.comcast.com>
2023-01-09 15:26 ` [Rpm] [Starlink] Researchers Seeking Probe Volunteers in USA Dave Taht
2023-01-09 17:00 ` Sebastian Moeller
2023-01-09 17:04 ` [Rpm] [LibreQoS] " Jeremy Austin
2023-01-09 18:33 ` Dave Taht
2023-01-09 18:54 ` [Rpm] [EXTERNAL] " Livingood, Jason
2023-01-09 19:19 ` rjmcmahon
2023-01-09 19:56 ` [Rpm] [LibreQoS] " dan
2023-01-09 21:00 ` rjmcmahon
2023-03-13 10:02 ` Sebastian Moeller
2023-03-13 15:08 ` [Rpm] [Starlink] [LibreQoS] [EXTERNAL] " Jeremy Austin
2023-03-13 15:50 ` Sebastian Moeller
2023-03-13 16:06 ` [Rpm] [Bloat] " Dave Taht
2023-03-13 16:19 ` Sebastian Moeller
2023-03-13 16:12 ` [Rpm] " dan
2023-03-13 16:36 ` Sebastian Moeller
2023-03-13 17:26 ` dan
2023-03-13 17:37 ` Jeremy Austin
2023-03-13 18:34 ` Sebastian Moeller
2023-03-13 18:14 ` Sebastian Moeller
2023-03-13 18:42 ` rjmcmahon
2023-03-13 18:51 ` Sebastian Moeller
2023-03-13 19:32 ` rjmcmahon
2023-03-13 20:00 ` Sebastian Moeller
2023-03-13 20:28 ` rjmcmahon
2023-03-14 4:27 ` [Rpm] On FiWi rjmcmahon
2023-03-14 11:10 ` [Rpm] [Starlink] " Mike Puchol
2023-03-14 16:54 ` Robert McMahon
2023-03-14 17:06 ` Robert McMahon
2023-03-14 17:11 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-14 17:35 ` Robert McMahon
2023-03-14 17:54 ` [Rpm] [LibreQoS] " dan
2023-03-14 18:14 ` Robert McMahon
2023-03-14 19:18 ` dan
2023-03-14 19:30 ` [Rpm] [Bloat] [LibreQoS] " Dave Taht
2023-03-14 20:06 ` rjmcmahon
2023-03-14 19:30 ` [Rpm] [LibreQoS] [Bloat] " rjmcmahon
2023-03-14 23:30 ` [Rpm] [Starlink] [LibreQoS] [Bloat] " Bruce Perens
2023-03-15 0:11 ` Robert McMahon
2023-03-15 5:20 ` Bruce Perens
2023-03-15 16:17 ` Aaron Wood
2023-03-15 17:05 ` Bruce Perens
2023-03-15 17:44 ` rjmcmahon
2023-03-15 19:22 ` [Rpm] [Bloat] [Starlink] [LibreQoS] " David Lang
2023-03-15 17:32 ` [Rpm] [Starlink] [LibreQoS] [Bloat] " rjmcmahon
2023-03-15 17:42 ` dan
2023-03-15 19:33 ` [Rpm] [Bloat] [Starlink] [LibreQoS] " David Lang
2023-03-15 19:39 ` Dave Taht [this message]
2023-03-15 21:52 ` David Lang
2023-03-15 22:04 ` Dave Taht
2023-03-15 22:08 ` dan
2023-03-15 17:43 ` Sebastian Moeller
2023-03-15 17:49 ` rjmcmahon
2023-03-15 17:53 ` Dave Taht
2023-03-15 17:59 ` dan
2023-03-15 19:39 ` rjmcmahon
2023-03-17 16:38 ` [Rpm] [Starlink] " Dave Taht
2023-03-17 18:21 ` Mike Puchol
2023-03-17 19:01 ` Sebastian Moeller
2023-03-17 19:19 ` rjmcmahon
2023-03-17 20:37 ` Bruce Perens
2023-03-17 20:57 ` rjmcmahon
2023-03-17 22:50 ` Bruce Perens
2023-03-18 18:18 ` rjmcmahon
2023-03-18 19:57 ` [Rpm] [LibreQoS] " dan
2023-03-18 20:40 ` rjmcmahon
2023-03-19 10:26 ` [Rpm] [Starlink] [LibreQoS] " Michael Richardson
2023-03-19 21:00 ` [Rpm] On metrics rjmcmahon
2023-03-20 0:26 ` dan
2023-03-20 3:03 ` [Rpm] [Starlink] " David Lang
2023-03-20 20:46 ` [Rpm] [Starlink] [LibreQoS] On FiWi Frantisek Borsik
2023-03-20 21:28 ` dan
2023-03-20 21:38 ` Frantisek Borsik
2023-03-20 22:02 ` [Rpm] On FiWi power envelope rjmcmahon
2023-03-20 23:47 ` [Rpm] [Starlink] " Bruce Perens
2023-03-21 0:10 ` [Rpm] [Starlink] [LibreQoS] On FiWi Brandon Butterworth
2023-03-21 5:21 ` Frantisek Borsik
2023-03-21 11:26 ` [Rpm] Annoyed at 5/1 Mbps Rich Brown
2023-03-21 12:29 ` [Rpm] [Starlink] [LibreQoS] On FiWi Brandon Butterworth
2023-03-21 12:30 ` Sebastian Moeller
2023-03-21 17:42 ` rjmcmahon
2023-03-21 18:08 ` rjmcmahon
2023-03-21 18:51 ` Frantisek Borsik
2023-03-21 19:58 ` rjmcmahon
2023-03-21 20:06 ` [Rpm] [Bloat] " David Lang
2023-03-25 19:39 ` [Rpm] On fiber as critical infrastructure w/Comcast chat rjmcmahon
2023-03-25 20:09 ` [Rpm] [Starlink] " Bruce Perens
2023-03-25 20:47 ` rjmcmahon
2023-03-25 20:15 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-25 20:43 ` rjmcmahon
2023-03-25 21:08 ` [Rpm] [Starlink] " Bruce Perens
2023-03-25 22:04 ` Robert McMahon
2023-03-25 22:50 ` dan
2023-03-25 23:21 ` Robert McMahon
2023-03-25 23:35 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-26 0:04 ` Robert McMahon
2023-03-26 0:07 ` Nathan Owens
2023-03-26 0:50 ` Robert McMahon
2023-03-26 8:45 ` Livingood, Jason
2023-03-26 18:54 ` rjmcmahon
2023-03-26 0:28 ` David Lang
2023-03-26 0:57 ` Robert McMahon
2023-03-25 22:57 ` [Rpm] [Starlink] [Bloat] " Bruce Perens
2023-03-25 23:33 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-25 23:38 ` [Rpm] [Starlink] [Bloat] " Robert McMahon
2023-03-25 23:20 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-26 18:29 ` rjmcmahon
2023-03-26 10:34 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-26 18:12 ` rjmcmahon
2023-03-26 20:57 ` David Lang
2023-03-25 20:27 ` [Rpm] " rjmcmahon
2023-03-17 23:15 ` [Rpm] [Bloat] [Starlink] On FiWi David Lang
2023-03-13 19:33 ` [Rpm] [Starlink] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA dan
2023-03-13 19:52 ` Jeremy Austin
2023-03-13 21:00 ` Sebastian Moeller
2023-03-13 21:27 ` dan
2023-03-14 9:11 ` Sebastian Moeller
2023-03-13 20:45 ` Sebastian Moeller
2023-03-13 21:02 ` [Rpm] When do you drop? Always! Dave Taht
2023-03-13 16:04 ` [Rpm] UnderBloat on fiber and wisps Dave Taht
2023-03-13 16:09 ` Sebastian Moeller
2023-01-09 20:49 ` [Rpm] [EXTERNAL] Re: [Starlink] Researchers Seeking Probe Volunteers in USA Dave Taht
2023-01-09 19:13 ` [Rpm] " rjmcmahon
2023-01-09 19:47 ` Sebastian Moeller
2023-01-11 18:32 ` Rodney W. Grimes
2023-01-11 20:01 ` Sebastian Moeller
2023-01-11 21:46 ` Dick Roy
2023-01-12 8:22 ` Sebastian Moeller
2023-01-12 18:02 ` rjmcmahon
2023-01-12 21:34 ` Dick Roy
2023-01-12 20:39 ` Dick Roy
2023-01-13 7:33 ` Sebastian Moeller
2023-01-13 8:26 ` Dick Roy
2023-01-13 7:40 ` rjmcmahon
2023-01-13 8:10 ` Dick Roy
2023-01-15 23:09 ` rjmcmahon
2023-01-11 20:09 ` rjmcmahon
2023-01-12 8:14 ` Sebastian Moeller
2023-01-12 17:49 ` Robert McMahon
2023-01-12 21:57 ` Dick Roy
2023-01-13 7:44 ` Sebastian Moeller
2023-01-13 8:01 ` Dick Roy
2023-01-09 20:20 ` Dave Taht
2023-01-09 20:46 ` rjmcmahon
2023-01-09 20:59 ` Dave Taht
2023-01-09 21:06 ` rjmcmahon
2023-01-09 21:18 ` rjmcmahon
2023-01-09 21:02 ` Dick Roy
2023-01-10 17:36 ` David P. Reed
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw677LrJODdW+bGYG8b3_jcOMYNX0D77k_H508WronT=Xg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=bruce@perens.com \
--cc=dandenson@gmail.com \
--cc=david@lang.hm \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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