* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi
@ 2023-03-16 7:46 David Fernández
2023-09-05 16:15 ` Dave Taht
0 siblings, 1 reply; 9+ messages in thread
From: David Fernández @ 2023-03-16 7:46 UTC (permalink / raw)
To: starlink
ISPs like Orange are into extending the life of the routers they give
for Internet access, which are built for that:
https://www.orange.com/en/commitments/oranges-commitment/to-the-environment
France has introduced a repairability index for products, so you know
better what are you buying:
https://www.ecologie.gouv.fr/indice-reparabilite
Then, there is the one from iFixit:
https://www.ifixit.com/News/49319/why-ifixits-repair-scores-are-different-than-the-french-repair-index
Wondering what repairability index would have the Starlink terminals
all around the world.
Regards,
David
> Date: Wed, 15 Mar 2023 18:08:41 -0400
> From: dan <dandenson@gmail.com>
> To: Dave Taht <dave.taht@gmail.com>
> Cc: 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>, David Lang <david@lang.hm>
> Subject: Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi
> Message-ID:
> <CAA_JP8W4B6ixcYjijJ8FyA+PAXpLTLjvvKH5-dGjB-UaanC3dQ@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Mar 15, 2023 at 4:04:27 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> On Wed, Mar 15, 2023 at 2:52 PM David Lang <david@lang.hm> wrote:
>>
>>
>> On Wed, 15 Mar 2023, Dave Taht wrote:
>>
>>
>> > 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?)
>>
>>
>> no good stats this year. still using the wndr3800s. Lots of people
>> commenting on
>>
>> how well the network did, but we were a bit behind this year and didn't
>> get good
>>
>> monitoring in place. No cake yet.
>>
>>
>> I think this is what you mean
>>
>> https://www.youtube.com/watch?v=UXvGbEYeWp0
>>
>>
>>
>> A point I would like to make for the africa contingent here is that
>> you do not need the latest
>> technology for africa. We get 300Mbit out of hardware built in the
>> late 00s, like the wndr3800. The ath9k chipset is STILL manufactured,
>> the software mature, and for all I know millions of routers
>> like these are lying in junk bins worldwide, ready to be recycled and
>> reflashed.
>>
>> One libreqos customer deployed libreqos, and took a look at the 600+
>> ubnt AGWs (ath9k based), on the shelf that could be fq_codeled,
>> especially on the wifi... built a custom openwrt imagebuilder image
>> for em, reflashed and redistributed them.
>>
>> The wndr3800s were especially well built. I would expect them to last
>> decades. I had one failure of one that had been in the field for over
>> 10 years... I thought it was the flash chip... no, it was the power
>> supply!
>>
>>
>> > 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
>>
>
> Much of the hardware dumped on the US market in particular is especially
> poorly made. Ie, engineered for our disposable market. Lots of netgear
> products for example have a typical usable life of just 2-3 years if that,
> and then the caps have busted or some patina on the boards has killed them.
>
>
> I know Europe has some standards on this as well as South Korea to give
> them longer life. To the point, it’s not realistic to recycle these items
> from the US to other place because they were ‘built to fail’.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://lists.bufferbloat.net/pipermail/starlink/attachments/20230315/5ca4404e/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> ------------------------------
>
> End of Starlink Digest, Vol 24, Issue 37
> ****************************************
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-16 7:46 [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi David Fernández @ 2023-09-05 16:15 ` Dave Taht 0 siblings, 0 replies; 9+ messages in thread From: Dave Taht @ 2023-09-05 16:15 UTC (permalink / raw) To: David Fernández; +Cc: starlink [-- Attachment #1: Type: text/plain, Size: 12775 bytes --] I wonder what oleg thinks the starlink repairability index is? On Thu, Mar 16, 2023 at 12:46 AM David Fernández via Starlink < starlink@lists.bufferbloat.net> wrote: > ISPs like Orange are into extending the life of the routers they give > for Internet access, which are built for that: > https://www.orange.com/en/commitments/oranges-commitment/to-the-environment > > France has introduced a repairability index for products, so you know > better what are you buying: > https://www.ecologie.gouv.fr/indice-reparabilite > > Then, there is the one from iFixit: > > https://www.ifixit.com/News/49319/why-ifixits-repair-scores-are-different-than-the-french-repair-index > > Wondering what repairability index would have the Starlink terminals > all around the world. > > Regards, > > David > > > Date: Wed, 15 Mar 2023 18:08:41 -0400 > > From: dan <dandenson@gmail.com> > > To: Dave Taht <dave.taht@gmail.com> > > Cc: 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>, David Lang <david@lang.hm> > > Subject: Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi > > Message-ID: > > < > CAA_JP8W4B6ixcYjijJ8FyA+PAXpLTLjvvKH5-dGjB-UaanC3dQ@mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > On Mar 15, 2023 at 4:04:27 PM, Dave Taht <dave.taht@gmail.com> wrote: > > > >> On Wed, Mar 15, 2023 at 2:52 PM David Lang <david@lang.hm> wrote: > >> > >> > >> On Wed, 15 Mar 2023, Dave Taht wrote: > >> > >> > >> > 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?) > >> > >> > >> no good stats this year. still using the wndr3800s. Lots of people > >> commenting on > >> > >> how well the network did, but we were a bit behind this year and didn't > >> get good > >> > >> monitoring in place. No cake yet. > >> > >> > >> I think this is what you mean > >> > >> https://www.youtube.com/watch?v=UXvGbEYeWp0 > >> > >> > >> > >> A point I would like to make for the africa contingent here is that > >> you do not need the latest > >> technology for africa. We get 300Mbit out of hardware built in the > >> late 00s, like the wndr3800. The ath9k chipset is STILL manufactured, > >> the software mature, and for all I know millions of routers > >> like these are lying in junk bins worldwide, ready to be recycled and > >> reflashed. > >> > >> One libreqos customer deployed libreqos, and took a look at the 600+ > >> ubnt AGWs (ath9k based), on the shelf that could be fq_codeled, > >> especially on the wifi... built a custom openwrt imagebuilder image > >> for em, reflashed and redistributed them. > >> > >> The wndr3800s were especially well built. I would expect them to last > >> decades. I had one failure of one that had been in the field for over > >> 10 years... I thought it was the flash chip... no, it was the power > >> supply! > >> > >> > >> > 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 > >> > > > > Much of the hardware dumped on the US market in particular is especially > > poorly made. Ie, engineered for our disposable market. Lots of netgear > > products for example have a typical usable life of just 2-3 years if > that, > > and then the caps have busted or some patina on the boards has killed > them. > > > > > > I know Europe has some standards on this as well as South Korea to give > > them longer life. To the point, it’s not realistic to recycle these > items > > from the US to other place because they were ‘built to fail’. > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > < > https://lists.bufferbloat.net/pipermail/starlink/attachments/20230315/5ca4404e/attachment.html > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Starlink mailing list > > Starlink@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/starlink > > > > > > ------------------------------ > > > > End of Starlink Digest, Vol 24, Issue 37 > > **************************************** > > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > -- Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html Dave Täht CSO, LibreQos [-- Attachment #2: Type: text/html, Size: 20062 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>]
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA @ 2023-03-13 18:14 ` Sebastian Moeller 2023-03-13 18:42 ` rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: Sebastian Moeller @ 2023-03-13 18:14 UTC (permalink / raw) To: dan Cc: Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, rjmcmahon, bloat Hi Dan, > On Mar 13, 2023, at 18:26, dan <dandenson@gmail.com> wrote: > > On Mon, Mar 13, 2023 at 10:36 AM Sebastian Moeller <moeller0@gmx.de> wrote: >> >> Hi Dan, >> >> >>> On Mar 13, 2023, at 17:12, dan <dandenson@gmail.com> wrote: >>> ... >>> >>> High water mark on their router. >> >> [SM] Nope, my router is connected to my (bridged) modem via gigabit ethernet, with out a traffic shaper there is never going to be any noticeable water mark on the router side... sure the modem will built up a queue, but alas it does not expose the length of that DSL queue to me... A high water mark on my traffic shaped router informs me about my shaper setting (which I already know, after al I set it) but little about the capacity over the bottleneck link. And we are still talking about the easy egress direction, in the download direction Jeremy's question aplied is the achieved thoughput I measure limited by the link's capacity of are there simply not enoiugh packet available/sent to fill the pipe. >> > > And yet it can still see the flow of data on it's ports. The queue is > irelevant to the measurement of data across a port. I respectfully disagree, if say, my modem had a 4 GB queue I could theoretically burst ~4GB worth of data at line rate into that buffer without learning anything about the the modem-link capacity. > turn off the > shaper and run anything. run your speed test. don't look at the > speed test results, just use it to generate some traffic. you'll find > your peak and where you hit the buffers on the DSL modem by measuring > on the interface and measuring latency. Peak of what? Exactly? The peak sending rate of my router is well known, its 1 Gbps gross ethernet rate... > That speed test isn't giving > you this data and more than Disney+, other than you get to pick when > it runs. Hrm, no we sre back at actually saturating the link, > >>> Highwater mark on our CPE, on our >>> shaper, etc. Modern services are very happy to burst traffic. >> >> [SM] Yes, this is also one of the readons, why too-little-buffering is problematic, I like the Nichols/Jacobsen analogy of buffers as shiock (burst) absorbers. >> >>> Nearly >>> every customer we have will hit the top of their service place each >>> day, even if only briefly and even if their average usage is quite >>> low. Customers on 600Mbps mmwave services have a usage charge that is >>> flat lines and ~600Mbps blips. >> >> [SM] Fully agree. most links are essentially idle most of the time, but that does not answer what instantaneous capacity is actually available, no? > > yes, because most services burst. That Roku Ultra or Apple TV is > going to running a 'speed test' every time it goes to fill it's > buffer. [SM] not really, given enough capacity, typical streaming protocols will actually not hit the ceiling, at least the one's I look at every now and then tend to stay well below actual capacity of the link. > Windows and Apple updates are asking for everything. Again, > I'm measuring even the lowly grandma's house as consuming the entire > connection for a few seconds before it sits idle for a minute. That > instantaneous capacity is getting used up so long as there is a > device/connection on the network capable of using it up. [SM] But my problem is that on variable rate links I want to measure the instantaneous capacity such that I can do adaptive admission control and avpid over filling my modem's DSL buffers (I wish they would do something like BQL, but alas they don't). > >> >>> >>> " [SM] No ISP I know of publishes which periods are low, mid, high >>> congestion so end-users will need to make some assumptions here (e.g. >>> by looking at per day load graphs of big traffic exchanges like DE-CIX >>> here https://www.de-cix.net/en/locations/frankfurt/statistics )" >>> >>> You read this wrong. Consumer routers run their daily speeds tests in >>> the middle of the night. >> >> [SM] So on my turris omnia I run a speedtest roughly every 2 hours exactly so I get coverage through low and high demand epochs. The only consumer router I know that does repeated tests is the IQrouter, which as far as I know schedules them regularly so it can adjust the traffic shaper to still deliver acceptale responsiveness even during peak hour. > > Consider this. Customer under load, using their plan to the maximum, > speed test fires up adding more constraint. Speed test is a stress > test, not a capacity test. [SM] With competent AQM (like cake on ingress and egress configured for per-internal-IP isolation) I do not even notice whether a speedtes runs or not, and from the reported capacity I can estimate the concurrent load from other endhosts in my network. > Speed test cannot return actual capacity > because it's being used by other services AND the rest of the internet > is in the way of accuracy as well, unless of course you prioritize the > speed test and then you cause an effective outage or you're running a > speed test on-net which isn't an 'internet' test, it's a network test. [SM] Conventional capcaity tests give a decent enough estimate of current capacity to be useful, I could not care less that they are potential not perfect, sorry. The question still is how to estimate capacity without loading the link... > Guess what the only way to get an actual measure of the capacity is? > my way. measure what's passing the interface and measure what happens > to a reliable latency test during that time. [SM] This is, respectfully, what we do in cake-autorate, but that requires an actual load and only accidentally detects the capacity, if a high enough load is sustained long enough to evoke a latency increase. But I knew that already, what you initially wrote sounded to me like you had a method to detect instantaneous capacity without needing to generate load. (BTW, in cake-autorate we do not generate an artificial load (only artificial/active latency probes) but use the organic user generated traffic as load generator*). *) If all endhosts are idle we do not care much about the capacity, only if there is traffic, however the quicker we can estimate the capacity the tigher our controller can operate. > >> >> >>> Eero at 3am for example. Netgear 230-430am. >> >> [SM] That sounds"specisl" not a useless daa point per se, but of limited utility during normal usage times. > > In practical terms, useless. Like measuring how freeway congestion > affects commutes at 3am. [SM] That is not "useless" sorry, it gives my a lower bound for my compute (or allows to estimate a lower duration of a transfer of a given size). But I agree it does little to inform me what to expect during peak hour. > >> >>> THAT is a bad measurement of the experience the consumer will have. >> >> [SM] Sure, but it still gives a usable reference for "what is the best my ISP actually delivers" if if the odds are stacked in his direction. > > ehh...... what the ISP could deliver if all other considerations are > removed. [SM] No, this is still a test of the real existing network... > I mean, it'd be a synthetic test in any other scenario and > the only reason it's not is because it's on real hardware. I don't > have a single subscriber on network that can't get 2-3x their plan > speed at 3am if I opened up their shaper. Very narrow use case here > from a consumer point of view. Eero runs speed tests at 3am every > single day on a few hundred subs on my network and they look AMAZING > every time. no surprise. [SM] While I defend some utility for such a test on pronciple, I agree that if eero only runs a single test 3 AM is not the best time to do that, except for night owls. > >> >>> It's essentially useless data for ... >> >> [SM] There is no single "service latency" it really depends on he specific network paths to the remote end and back. Unless you are talking about the latency over the access link only tere we have a single number but one of limited utility. > > The intermediate hops are still useless to the consumer. Only the > latency to their door so to speak. again, hop 2 to hop 3 on my > network gives them absolutely nothing. [SM] I agree if these are mandatory hops I need to traverse every time, but if these are host I can potentially avoid then this changes, even though I am now trying to gsame my ISP to some degree which in the long run is a loosing proposition. > >> >> >>> My (ISP) latency from hop 2 to 3 on the network has >> ...> > hops are which because they'll hidden in a tunnel/MPLS/etc. >> >> [SM] Yes, end-users can do little, but not nothing, e.g. one can often work-around shitty peering by using a VPN to route one's packets into an AS that is both well connected with one's ISP as well as with one's remote ASs. And I accept your point of one-way testing, getting a remote site at the ight location to do e.g. reverse tracerputes mtrs is tricky (sometimes RIPE ATLAS can help) to impossible (like my ISP that does not offer even simple lookingglas servers at all)). > > This is a REALLY narrow use case. Also, irrelevant. [SM] You would think, would you ;). However over here the T1 incumbent telco plays "peering games" and purposefully runs its transit links too hot so in primetime traffic coming from content providers via transit suffers. The telco's idea here is to incentivize these content providers to buy "transit" from that telco that happens to cost integer multiples of transit and hence will only ever be used to access this telco's customers if a content provider actually buys in. As an end-user of that telco, I have three options: a) switch content providers b) switch ISP c) route around my ISPs unfriendly peering (Personally even though not directly affected by this I opted for b) and found a better connected yet still cheaper ISP). I am not alone in this, actually a lot of gamers do something similar using gaming oriented VPN services. But then gamers are a bit like audiophiles to me, some of the things they do look like cargo-cult to me, but I digress/ > Consumer can test > to their target, to the datacenter, and datacenter to target and > compare, and do that in reverse to get bi-directional latency. [SM] I have been tought thst does not actually work as the true return path is essentially invisible without a probe for a reverse traceroute at the site of the remote server, no? > per > hop latency is still of zero benefit to them because they can't use > that in any practical way. [SM] And again I disagree, I can within reason diagnose congested path elements from an mtr... say if on a path across three AS that at best takes 10 milliseconds, I see at primetime that from the link between AS1 and AS2 all hops including the endpoint show an RTT of say 100ms, I can form the hypothsis that somewhere between AS1 and AS2 there is a undue queue build-up. Pratically this can mean I need to rpute my own traffic differentky, either by VPN, or by switching the used application content provider hoping to avoid the apparently congested link. What I can not do is fix the problem, that is true ;) > Like 1 in maybe a few thousand consumers > might be able to use this data to identify the slow hop and find a > datacenter before that hop to route around it and they get about 75% > of the way with a traditional trace router. and then of course they've > added VPN overheads so are they really getting an improvement? [SM] In the german telco case peak rate to some datacenters/VPS (single-homed at cogent) dropped into the low Kbps range, while a VPN route-around returned that into the high double digit Mbps, so yes the improvement can be tangible. Again, my soluton to that possibility was to "vote with my feet" and change ISPs (a pity, because outside of that unpleasant peering/transit behaviour that telco is a pretty competent ISP; case in point the transit links run too hot, but are are competently managed to actually stay at the selected "temperature" and do not progress into to total overload territory.) > I'm not saying that testing is bad in any way, I'm saying that 'speed > tests' as they are generally understood in this industry are a bad > method. [SM] +1, with that I can agree. But I see some mild improvements, with e.g. Ookla reporting latency numbers from during the load phases. Sure the chosen measure inter-quartil mean, is sub-optimal, but infinitely better than hat they had before, no latecny under load numbers. > Run 10 speed tests, get 10 results. Run a speed test while > netflix buffers, get a bad result. Run a speed test from a weak wifi > connection, get a bad result. A tool that is inherently flawed > because it's methodology is flawed is of no use to find the truth. [SM] For most end users speedtests are the one convenient way of generating saturating loads. BUt saturating loads by them selves are not that useful. > > If you troubleshoot your ISP based on speed tests you will be chasing > your tail. My most recent attempt was with mtr traces to document packetloss only when "packed" into one specific IP range, and that packetloss happens even without load at night, so no speedtest required (I did run a few speed.cloudflare.com tests, but mainly because they contain a very simple and short packet loss test, that finishes a tad earlier than my go to 'mtr -ezbw -c 1000 IP_HERE' packet loss test ;) ) > Meanwhile, that internet facing interface can see the true > numbers the entire time. [SM] Only averaged over time... > The consumer is pulling their full capacity > on almost all links routinely even if briefly and can be nudged into > pushing more a dozen ways (including a speed test). The only thing > lacking is a latency measurement of some sort. Preseem and Libreqos's > TCP measurements on the head end are awesome, but that's not available > on the subscriber's side but if it were, there's the full testing > suite. how much peak data, what happened to latency. If you could > get data from the ISP's head end to diff you'd have internet vs isp > latencies. 'speed test' is a stress test or a burn in test in > effect. [SM] I still agree "speedtests" are misnames capacity tests and do have their value (e.g. over here the main determinant of internet access price is the headline capacity number) we even have an "official" capacity test blessed by the national regulatory agency that can be used to defend consumer rights against those ISP that over-promise but under-deliver (few people d though, as it happens if your ISP generally delivers acceptable throughput and generally is not a d*ck, people are fine with not caring all too much). On the last point I believe the more responsiveness an ISP link maintains under load the fewer people will get unhappy about their internet experience and without unhappyness most users I presime have better things to do than fight with their ISP. ;) Regards Sebastian ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 2023-03-13 18:14 ` [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA Sebastian Moeller @ 2023-03-13 18:42 ` rjmcmahon 2023-03-13 18:51 ` Sebastian Moeller 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-13 18:42 UTC (permalink / raw) To: Sebastian Moeller Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat > [SM] not really, given enough capacity, typical streaming protocols > will actually not hit the ceiling, at least the one's I look at every > now and then tend to stay well below actual capacity of the link. > I think DASH type protocol will hit link peaks. An example with iperf 2's burst option a controlled WiFi test rig, server side first. [root@ctrl1fc35 ~]# iperf -s -i 1 -e --histograms ------------------------------------------------------------ Server listening on TCP port 5001 with pid 23764 Read buffer size: 128 KByte (Dist bin width=16.0 KByte) Enabled receive histograms bin-width=0.100 ms, bins=10000 (clients should use --trip-times) TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 1] local 192.168.1.15%enp2s0 port 5001 connected with 192.168.1.234 port 34894 (burst-period=1.00s) (trip-times) (sock=4) (peer 2.1.9-rc2) (icwnd/mss/irtt=14/1448/5170) on 2023-03-13 11:37:24.500 (PDT) [ ID] Burst (start-end) Transfer Bandwidth XferTime (DC%) Reads=Dist NetPwr [ 1] 0.00-0.13 sec 10.0 MBytes 633 Mbits/sec 132.541 ms (13%) 209=29:31:31:88:11:2:1:16 597 [ 1] 1.00-1.11 sec 10.0 MBytes 755 Mbits/sec 111.109 ms (11%) 205=34:30:22:83:11:2:6:17 849 [ 1] 2.00-2.12 sec 10.0 MBytes 716 Mbits/sec 117.196 ms (12%) 208=33:39:20:81:13:1:5:16 763 [ 1] 3.00-3.11 sec 10.0 MBytes 745 Mbits/sec 112.564 ms (11%) 203=27:36:30:76:6:3:6:19 828 [ 1] 4.00-4.11 sec 10.0 MBytes 787 Mbits/sec 106.621 ms (11%) 193=29:26:19:80:10:4:6:19 922 [ 1] 5.00-5.11 sec 10.0 MBytes 769 Mbits/sec 109.148 ms (11%) 208=36:25:32:86:6:1:5:17 880 [ 1] 6.00-6.11 sec 10.0 MBytes 760 Mbits/sec 110.403 ms (11%) 206=42:30:22:73:8:3:5:23 860 [ 1] 7.00-7.11 sec 10.0 MBytes 775 Mbits/sec 108.261 ms (11%) 171=20:21:21:58:12:1:11:27 895 [ 1] 8.00-8.11 sec 10.0 MBytes 746 Mbits/sec 112.405 ms (11%) 203=36:31:28:70:9:3:2:24 830 [ 1] 9.00-9.11 sec 10.0 MBytes 748 Mbits/sec 112.133 ms (11%) 228=41:56:27:73:7:2:3:19 834 [ 1] 0.00-10.00 sec 100 MBytes 83.9 Mbits/sec 113.238/106.621/132.541/7.367 ms 2034=327:325:252:768:93:22:50:197 [ 1] 0.00-10.00 sec F8(f)-PDF: bin(w=100us):cnt(10)=1067:1,1083:1,1092:1,1105:1,1112:1,1122:1,1125:1,1126:1,1172:1,1326:1 (5.00/95.00/99.7%=1067/1326/1326,Outliers=0,obl/obu=0/0) (132.541 ms/1678732644.500333) [root@fedora ~]# iperf -c 192.168.1.15 -i 1 -t 10 --burst-size 10M --burst-period 1 --trip-times ------------------------------------------------------------ Client connecting to 192.168.1.15, TCP port 5001 with pid 132332 (1 flows) Write buffer size: 131072 Byte Bursting: 10.0 MByte every 1.00 second(s) TOS set to 0x0 (Nagle on) TCP window size: 16.0 KByte (default) Event based writes (pending queue watermark at 16384 bytes) ------------------------------------------------------------ [ 1] local 192.168.1.234%eth1 port 34894 connected with 192.168.1.15 port 5001 (prefetch=16384) (trip-times) (sock=3) (icwnd/mss/irtt=14/1448/5489) (ct=5.58 ms) on 2023-03-13 11:37:24.494 (PDT) [ ID] Interval Transfer Bandwidth Write/Err Rtry Cwnd/RTT(var) NetPwr [ 1] 0.00-1.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5517K/18027(1151) us 582 [ 1] 1.00-2.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5584K/13003(2383) us 806 [ 1] 2.00-3.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5613K/16462(962) us 637 [ 1] 3.00-4.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5635K/19523(671) us 537 [ 1] 4.00-5.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5594K/10013(1685) us 1047 [ 1] 5.00-6.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5479K/14008(654) us 749 [ 1] 6.00-7.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5613K/17752(283) us 591 [ 1] 7.00-8.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5599K/17743(436) us 591 [ 1] 8.00-9.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5577K/11214(2538) us 935 [ 1] 9.00-10.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 4178K/7251(993) us 1446 [ 1] 0.00-10.01 sec 100 MBytes 83.8 Mbits/sec 800/0 0 4178K/7725(1694) us 1356 [root@fedora ~]# Note: Client side output is being updated to support outputs based upon the bursts. This allows one to see that a DASH type protocol can drive the bw bottleneck queue. Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 2023-03-13 18:42 ` rjmcmahon @ 2023-03-13 18:51 ` Sebastian Moeller 2023-03-13 19:32 ` rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: Sebastian Moeller @ 2023-03-13 18:51 UTC (permalink / raw) To: rjmcmahon Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat Hi Bob, > On Mar 13, 2023, at 19:42, rjmcmahon <rjmcmahon@rjmcmahon.com> wrote: > >> [SM] not really, given enough capacity, typical streaming protocols >> will actually not hit the ceiling, at least the one's I look at every >> now and then tend to stay well below actual capacity of the link. > I think DASH type protocol will hit link peaks. An example with iperf 2's burst option a controlled WiFi test rig, server side first. [SM] I think that depends, each segment has only a finite length and if this can delivered before slow start ends that burst might never hit the capacity? Regards Sebastian > > > [root@ctrl1fc35 ~]# iperf -s -i 1 -e --histograms > ------------------------------------------------------------ > Server listening on TCP port 5001 with pid 23764 > Read buffer size: 128 KByte (Dist bin width=16.0 KByte) > Enabled receive histograms bin-width=0.100 ms, bins=10000 (clients should use --trip-times) > TCP window size: 128 KByte (default) > ------------------------------------------------------------ > [ 1] local 192.168.1.15%enp2s0 port 5001 connected with 192.168.1.234 port 34894 (burst-period=1.00s) (trip-times) (sock=4) (peer 2.1.9-rc2) (icwnd/mss/irtt=14/1448/5170) on 2023-03-13 11:37:24.500 (PDT) > [ ID] Burst (start-end) Transfer Bandwidth XferTime (DC%) Reads=Dist NetPwr > [ 1] 0.00-0.13 sec 10.0 MBytes 633 Mbits/sec 132.541 ms (13%) 209=29:31:31:88:11:2:1:16 597 > [ 1] 1.00-1.11 sec 10.0 MBytes 755 Mbits/sec 111.109 ms (11%) 205=34:30:22:83:11:2:6:17 849 > [ 1] 2.00-2.12 sec 10.0 MBytes 716 Mbits/sec 117.196 ms (12%) 208=33:39:20:81:13:1:5:16 763 > [ 1] 3.00-3.11 sec 10.0 MBytes 745 Mbits/sec 112.564 ms (11%) 203=27:36:30:76:6:3:6:19 828 > [ 1] 4.00-4.11 sec 10.0 MBytes 787 Mbits/sec 106.621 ms (11%) 193=29:26:19:80:10:4:6:19 922 > [ 1] 5.00-5.11 sec 10.0 MBytes 769 Mbits/sec 109.148 ms (11%) 208=36:25:32:86:6:1:5:17 880 > [ 1] 6.00-6.11 sec 10.0 MBytes 760 Mbits/sec 110.403 ms (11%) 206=42:30:22:73:8:3:5:23 860 > [ 1] 7.00-7.11 sec 10.0 MBytes 775 Mbits/sec 108.261 ms (11%) 171=20:21:21:58:12:1:11:27 895 > [ 1] 8.00-8.11 sec 10.0 MBytes 746 Mbits/sec 112.405 ms (11%) 203=36:31:28:70:9:3:2:24 830 > [ 1] 9.00-9.11 sec 10.0 MBytes 748 Mbits/sec 112.133 ms (11%) 228=41:56:27:73:7:2:3:19 834 > [ 1] 0.00-10.00 sec 100 MBytes 83.9 Mbits/sec 113.238/106.621/132.541/7.367 ms 2034=327:325:252:768:93:22:50:197 > [ 1] 0.00-10.00 sec F8(f)-PDF: bin(w=100us):cnt(10)=1067:1,1083:1,1092:1,1105:1,1112:1,1122:1,1125:1,1126:1,1172:1,1326:1 (5.00/95.00/99.7%=1067/1326/1326,Outliers=0,obl/obu=0/0) (132.541 ms/1678732644.500333) > > > [root@fedora ~]# iperf -c 192.168.1.15 -i 1 -t 10 --burst-size 10M --burst-period 1 --trip-times > ------------------------------------------------------------ > Client connecting to 192.168.1.15, TCP port 5001 with pid 132332 (1 flows) > Write buffer size: 131072 Byte > Bursting: 10.0 MByte every 1.00 second(s) > TOS set to 0x0 (Nagle on) > TCP window size: 16.0 KByte (default) > Event based writes (pending queue watermark at 16384 bytes) > ------------------------------------------------------------ > [ 1] local 192.168.1.234%eth1 port 34894 connected with 192.168.1.15 port 5001 (prefetch=16384) (trip-times) (sock=3) (icwnd/mss/irtt=14/1448/5489) (ct=5.58 ms) on 2023-03-13 11:37:24.494 (PDT) > [ ID] Interval Transfer Bandwidth Write/Err Rtry Cwnd/RTT(var) NetPwr > [ 1] 0.00-1.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5517K/18027(1151) us 582 > [ 1] 1.00-2.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5584K/13003(2383) us 806 > [ 1] 2.00-3.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5613K/16462(962) us 637 > [ 1] 3.00-4.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5635K/19523(671) us 537 > [ 1] 4.00-5.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5594K/10013(1685) us 1047 > [ 1] 5.00-6.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5479K/14008(654) us 749 > [ 1] 6.00-7.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5613K/17752(283) us 591 > [ 1] 7.00-8.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5599K/17743(436) us 591 > [ 1] 8.00-9.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 5577K/11214(2538) us 935 > [ 1] 9.00-10.00 sec 10.0 MBytes 83.9 Mbits/sec 80/0 0 4178K/7251(993) us 1446 > [ 1] 0.00-10.01 sec 100 MBytes 83.8 Mbits/sec 800/0 0 4178K/7725(1694) us 1356 > [root@fedora ~]# > > Note: Client side output is being updated to support outputs based upon the bursts. This allows one to see that a DASH type protocol can drive the bw bottleneck queue. > > Bob > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 2023-03-13 18:51 ` Sebastian Moeller @ 2023-03-13 19:32 ` rjmcmahon 2023-03-13 20:00 ` Sebastian Moeller 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-13 19:32 UTC (permalink / raw) To: Sebastian Moeller Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat On 2023-03-13 11:51, Sebastian Moeller wrote: > Hi Bob, > > >> On Mar 13, 2023, at 19:42, rjmcmahon <rjmcmahon@rjmcmahon.com> wrote: >> >>> [SM] not really, given enough capacity, typical streaming protocols >>> will actually not hit the ceiling, at least the one's I look at every >>> now and then tend to stay well below actual capacity of the link. >> I think DASH type protocol will hit link peaks. An example with iperf >> 2's burst option a controlled WiFi test rig, server side first. > > [SM] I think that depends, each segment has only a finite length and > if this can delivered before slow start ends that burst might never > hit the capacity? > > Regards I believe most CDNs are setting the initial CWND so TCP can bypass slow start. Slow start seems an engineering flaw from the perspective of low latency. It's done for "fairness" whatever that means. Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 2023-03-13 19:32 ` rjmcmahon @ 2023-03-13 20:00 ` Sebastian Moeller 2023-03-13 20:28 ` rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: Sebastian Moeller @ 2023-03-13 20:00 UTC (permalink / raw) To: rjmcmahon Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat Hi Bob, > On Mar 13, 2023, at 20:32, rjmcmahon <rjmcmahon@rjmcmahon.com> wrote: > > On 2023-03-13 11:51, Sebastian Moeller wrote: >> Hi Bob, >>> On Mar 13, 2023, at 19:42, rjmcmahon <rjmcmahon@rjmcmahon.com> wrote: >>>> [SM] not really, given enough capacity, typical streaming protocols >>>> will actually not hit the ceiling, at least the one's I look at every >>>> now and then tend to stay well below actual capacity of the link. >>> I think DASH type protocol will hit link peaks. An example with iperf 2's burst option a controlled WiFi test rig, server side first. >> [SM] I think that depends, each segment has only a finite length and >> if this can delivered before slow start ends that burst might never >> hit the capacity? >> Regards > > I believe most CDNs are setting the initial CWND so TCP can bypass slow start. [SM] My take is not necessarily to bypass slow start, but to kick it off with a higher starting point... which is the conservative way to expedite slow-start. Real man actually increase the multiplication factor instead, but there are few real men around (luckily)... s I see both the desire to finish many smaller transfers within the initial window (so the first RTT after the handshake IIUC). > Slow start seems an engineering flaw from the perspective of low latency. [SM] Yes, exponential search, doubling every RTT is pretty aggressive. > It's done for "fairness" whatever that means. [SM] It is doe because: a) TCP needs some capacity estimate b) preferably quickly c) in a way gentler than what was used before the congestion collapse. we are calling it slow-start not because it is slow in absolute terms (it is pretty aggressive already) but IIUC because before slow start people where even more aggressive (immediately sending at line rate?) I think we need immediate queue build-up feedback so each flow can look at its own growth projection and the queue space shrinkage projection and then determine where these two will meet. Essentially we need a gently way of ending slow-start instead of the old chestnut, dump twice as much data in flight into the network before we notice... it is this part that is at odds with low latency. L4s, true to form with its essential bit-banging of queue filling status over all flows in the LL queue is essentially givvin too little information too late. If I had a better proposal for a slow-start altenative I would make it, but for me slow-start is similar to what Churchill is supposed to have said about democracy "democracy is the worst form of government – except for all the others that have been tried."... > > Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 2023-03-13 20:00 ` Sebastian Moeller @ 2023-03-13 20:28 ` rjmcmahon 2023-03-14 4:27 ` [Starlink] On FiWi rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-13 20:28 UTC (permalink / raw) To: Sebastian Moeller Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat > [SM] It is doe because: > a) TCP needs some capacity estimate > b) preferably quickly > c) in a way gentler than what was used before the congestion collapse. Right, but we're moving away from capacity shortages to a focus on better latencies. The speed of distributed compute (or speed of causality) is now mostly latency constrained. Also, it's impossible per Jaffe & others for a TCP link to figure out the on-demand capacity so trying to get one via a "broken control loop" seems futile. I believe control theory states control loops need to be an order greater than what they're trying to control. I don't think an app or transport layer can do more than make educated guesses at for its control loop. Using a rating might help with that but for sure it's not accurate in space-time samples. (Note: many APs are rated 60+ Watts. What's the actual? Has to be sampled and that's only a sample. This leads to poor PoE designs - but I digress.) Let's assume the transport layer should be designed to optimize the speed of causality. This also seems impossible because the e2e jitter is worse with respect to end host discovery so there seems no way to adapt from end host only. If it's true that the end can only guess, maybe the solution domain comes from incorporating network measurements via telemetry with the ECN or equivalent? And an app can signal to the network elements to capture the e2e telemetry. I think this all has to happen within a few RTTs if the transport or host app is going to adjust. Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Starlink] On FiWi 2023-03-13 20:28 ` rjmcmahon @ 2023-03-14 4:27 ` rjmcmahon 2023-03-14 11:10 ` Mike Puchol 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-14 4:27 UTC (permalink / raw) To: Sebastian Moeller Cc: dan, Jeremy Austin, Rpm, libreqos, Dave Taht via Starlink, bloat To change the topic - curious to thoughts on FiWi. Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS Radios, Antennas) and which is point to point inside a building connected to virtualized APs fiber hops away. Each remote radio head (RRH) would consume 5W or less and only when active. No need for things like zigbee, or meshes, or threads as each radio has a fiber connection via Corning's actifi or equivalent. Eliminate the AP/Client power imbalance. Plastics also can house smoke or other sensors. Some reminders from Paul Baran in 1994 (and from David Reed) o) Shorter range rf transceivers connected to fiber could produce a significant improvement - - tremendous improvement, really. o) a mixture of terrestrial links plus shorter range radio links has the effect of increasing by orders and orders of magnitude the amount of frequency spectrum that can be made available. o) By authorizing high power to support a few users to reach slightly longer distances we deprive ourselves of the opportunity to serve the many. o) Communications systems can be built with 10dB ratio o) Digital transmission when properly done allows a small signal to noise ratio to be used successfully to retrieve an error free signal. o) And, never forget, any transmission capacity not used is wasted forever, like water over the dam. Not using such techniques represent lost opportunity. And on waveguides: o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, independent of modulation" o) “Copper cables and PCB traces are very frequency dependent. At 100Gb/s, the loss is in dB/inch." o) "Free space: the power density of the radio waves decreases with the square of distance from the transmitting antenna due to spreading of the electromagnetic energy in space according to the inverse square law" The sunk costs & long-lived parts of FiWi are the fiber and the CPE plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could be pluggable, allowing for field upgrades. Just like swapping out SFP in a data center. This approach basically drives out WiFi latency by eliminating shared queues and increases capacity by orders of magnitude by leveraging 10dB in the spatial dimension, all of which is achieved by a physical design. Just place enough RRHs as needed (similar to a pop up sprinkler in an irrigation system.) Start and build this for an MDU and the value of the building improves. Sadly, there seems no way to capture that value other than over long term use. It doesn't matter whether the leader of the HOA tries to capture the value or if a last mile provider tries. The value remains sunk or hidden with nothing on the asset side of the balance sheet. We've got a CAPEX spend that has to be made up via "OPEX returns" over years. But the asset is there. How do we do this? Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] On FiWi 2023-03-14 4:27 ` [Starlink] On FiWi rjmcmahon @ 2023-03-14 11:10 ` Mike Puchol 2023-03-14 16:54 ` [Starlink] [Rpm] " Robert McMahon 0 siblings, 1 reply; 9+ messages in thread From: Mike Puchol @ 2023-03-14 11:10 UTC (permalink / raw) To: Dave Taht via Starlink; +Cc: libreqos, Rpm, bloat [-- Attachment #1: Type: text/plain, Size: 7399 bytes --] Hi Bob, You hit on a set of very valid points, which I'll complement with my views on where the industry (the bit of it that affects WISPs) is heading, and what I saw at the MWC in Barcelona. Love the FiWi term :-) I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, and Mimosa, but also newer entrants such as Tarana, increase the performance and on-paper specs of their equipment. My examples below are centered on the African market, if you operate in Europe or the US, where you can charge customers a higher install fee, or even charge them a break-up fee if they don't return equipment, the economics work. Where currently a ~$500 sector radio could serve ~60 endpoints, at a cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the antenna that you mount on the roof), and supply ~2.5 Mbps CIR per endpoint, the evolution is now a ~$2,000+ sector radio, a $200 endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR per endpoint. If every customer a WISP installs represents, say, $100 CAPEX at install time ($50 for the antenna + cabling, router, etc), and you charge a $30 install fee, you have $70 to recover, and you recover from the monthly contribution the customer makes. If the contribution after OPEX is, say, $10, it takes you 7 months to recover the full install cost. Not bad, doable even in low-income markets. Fast-forward to the next-generation version. Now, the CAPEX at install is $250, you need to recover $220, and it will take you 22 months, which is above the usual 18 months that investors look for. The focus, thereby, has to be the lever that has the largest effect on the unit economics - which is the per-customer cost. I have drawn what my ideal FiWi network would look like: Taking you through this - we start with a 1-port, low-cost EPON OLT (or you could go for 2, 4, 8 ports as you add capacity). This OLT has capacity for 64 ONUs on its single port. Instead of connecting the typical fiber infrastructure with kilometers of cables which break, require maintenance, etc. we insert an EPON to Ethernet converter (I added "magic" because these don't exist AFAIK). This converter allows us to connect our $2k sector radio, and serve the $200 endpoints (ODUs) over wireless point-to-multipoint up to 10km away. Each ODU then has a reverse converter, which gives us EPON again. Once we are back on EPON, we can insert splitters, for example, pre-connectorized outdoor 1:16 boxes. Every customer install now involves a 100 meter roll of pre-connectorized 2-core drop cable, and a $20 EPON ONU. Using this deployment method, we could connect up to 16 customers to a single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 (assuming the same $50 of extras we had before), and an even shorter break-even. In addition, as the endpoints support higher capacity, we can provision at least the same, if not more, capacity per customer. Other advantages: the $200 ODU is no longer customer equipment and CAPEX, but network equipment, and as such, can operate under a longer break-even timeline, and be financed by infrastructure PE funds, for example. As a result, churn has a much lower financial impact on the operator. The main reason why this wouldn't work today is that EPON, as we know, is synchronous, and requires the OLT to orchestrate the amount of time each ONU can transmit, and when. Having wireless hops and media conversions will introduce latencies which can break down the communications (e.g. one ONU may transmit, get delayed on the radio link, and end up overlapping another ONU that transmitted on the next slot). Thus, either the "magic" box needs to account for this, or an new hybrid EPON-wireless protocol developed. My main point here: the industry is moving away from the unconnected. All the claims I heard and saw at MWC about "connecting the unconnected" had zero resonance with the financial drivers that the unconnected really operate under, on top of IT literacy, digital skills, devices, power... Best, Mike On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink <starlink@lists.bufferbloat.net>, wrote: > To change the topic - curious to thoughts on FiWi. > > Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS > Radios, Antennas) and which is point to point inside a building > connected to virtualized APs fiber hops away. Each remote radio head > (RRH) would consume 5W or less and only when active. No need for things > like zigbee, or meshes, or threads as each radio has a fiber connection > via Corning's actifi or equivalent. Eliminate the AP/Client power > imbalance. Plastics also can house smoke or other sensors. > > Some reminders from Paul Baran in 1994 (and from David Reed) > > o) Shorter range rf transceivers connected to fiber could produce a > significant improvement - - tremendous improvement, really. > o) a mixture of terrestrial links plus shorter range radio links has the > effect of increasing by orders and orders of magnitude the amount of > frequency spectrum that can be made available. > o) By authorizing high power to support a few users to reach slightly > longer distances we deprive ourselves of the opportunity to serve the > many. > o) Communications systems can be built with 10dB ratio > o) Digital transmission when properly done allows a small signal to > noise ratio to be used successfully to retrieve an error free signal. > o) And, never forget, any transmission capacity not used is wasted > forever, like water over the dam. Not using such techniques represent > lost opportunity. > > And on waveguides: > > o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, > independent of modulation" > o) “Copper cables and PCB traces are very frequency dependent. At > 100Gb/s, the loss is in dB/inch." > o) "Free space: the power density of the radio waves decreases with the > square of distance from the transmitting antenna due to spreading of the > electromagnetic energy in space according to the inverse square law" > > The sunk costs & long-lived parts of FiWi are the fiber and the CPE > plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could be > pluggable, allowing for field upgrades. Just like swapping out SFP in a > data center. > > This approach basically drives out WiFi latency by eliminating shared > queues and increases capacity by orders of magnitude by leveraging 10dB > in the spatial dimension, all of which is achieved by a physical design. > Just place enough RRHs as needed (similar to a pop up sprinkler in an > irrigation system.) > > Start and build this for an MDU and the value of the building improves. > Sadly, there seems no way to capture that value other than over long > term use. It doesn't matter whether the leader of the HOA tries to > capture the value or if a last mile provider tries. The value remains > sunk or hidden with nothing on the asset side of the balance sheet. > We've got a CAPEX spend that has to be made up via "OPEX returns" over > years. > > But the asset is there. > > How do we do this? > > Bob > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink [-- Attachment #2.1: Type: text/html, Size: 8415 bytes --] [-- Attachment #2.2: Hybrid EPON-Wireless network.png --] [-- Type: image/png, Size: 149871 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] On FiWi 2023-03-14 11:10 ` Mike Puchol @ 2023-03-14 16:54 ` Robert McMahon 2023-03-14 17:06 ` Robert McMahon 0 siblings, 1 reply; 9+ messages in thread From: Robert McMahon @ 2023-03-14 16:54 UTC (permalink / raw) To: Mike Puchol; +Cc: Dave Taht via Starlink, Rpm, libreqos, bloat [-- Attachment #1: Type: text/plain, Size: 8913 bytes --] Hi Mike, I'm thinking more of fiber to the room. The last few meters are wifi everything else is fiber.. Those radios would be a max of 20' from the associated STA. Then at phy rates of 2.8Gb/s per spatial stream. The common MIMO is 2x2 so each radio head or wifi transceiver supports 5.6G, no queueing delay. Wholesale is $5 and retail $19.95 per pluggable transceiver. Sold at Home Depot next to the irrigation aisle. 10 per house is $199 and each room gets a dedicated 5.8G phy rate. Need more devices in a space? Pick an RRH with more cmos radios. Also, the antennas would be patch antenna and fill the room properly. Then plug in an optional sensor for fire alerting. A digression. A lot of signal processing engineers have been working on TX beam forming. The best beam is fiber. Just do that. It even can turn corners and goes exactly to where it's needed at very low energies. This is similar to pvc pipes in irrigation systems. They're designed to take water to spray heads. The cost is the cable plant. That's labor more than materials. Similar for irrigation, pvc is inexpensive and lasts decades. A return labor means use future proof materials, e.g. fiber. Bob On Mar 14, 2023, 4:10 AM, at 4:10 AM, Mike Puchol via Rpm <rpm@lists.bufferbloat.net> wrote: >Hi Bob, > >You hit on a set of very valid points, which I'll complement with my >views on where the industry (the bit of it that affects WISPs) is >heading, and what I saw at the MWC in Barcelona. Love the FiWi term :-) > >I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, >and Mimosa, but also newer entrants such as Tarana, increase the >performance and on-paper specs of their equipment. My examples below >are centered on the African market, if you operate in Europe or the US, >where you can charge customers a higher install fee, or even charge >them a break-up fee if they don't return equipment, the economics work. > >Where currently a ~$500 sector radio could serve ~60 endpoints, at a >cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the >antenna that you mount on the roof), and supply ~2.5 Mbps CIR per >endpoint, the evolution is now a ~$2,000+ sector radio, a $200 >endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR >per endpoint. > >If every customer a WISP installs represents, say, $100 CAPEX at >install time ($50 for the antenna + cabling, router, etc), and you >charge a $30 install fee, you have $70 to recover, and you recover from >the monthly contribution the customer makes. If the contribution after >OPEX is, say, $10, it takes you 7 months to recover the full install >cost. Not bad, doable even in low-income markets. > >Fast-forward to the next-generation version. Now, the CAPEX at install >is $250, you need to recover $220, and it will take you 22 months, >which is above the usual 18 months that investors look for. > >The focus, thereby, has to be the lever that has the largest effect on >the unit economics - which is the per-customer cost. I have drawn what >my ideal FiWi network would look like: > > > >Taking you through this - we start with a 1-port, low-cost EPON OLT (or >you could go for 2, 4, 8 ports as you add capacity). This OLT has >capacity for 64 ONUs on its single port. Instead of connecting the >typical fiber infrastructure with kilometers of cables which break, >require maintenance, etc. we insert an EPON to Ethernet converter (I >added "magic" because these don't exist AFAIK). > >This converter allows us to connect our $2k sector radio, and serve the >$200 endpoints (ODUs) over wireless point-to-multipoint up to 10km >away. Each ODU then has a reverse converter, which gives us EPON again. > >Once we are back on EPON, we can insert splitters, for example, >pre-connectorized outdoor 1:16 boxes. Every customer install now >involves a 100 meter roll of pre-connectorized 2-core drop cable, and a >$20 EPON ONU. > >Using this deployment method, we could connect up to 16 customers to a >single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. >Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 >(assuming the same $50 of extras we had before), and an even shorter >break-even. In addition, as the endpoints support higher capacity, we >can provision at least the same, if not more, capacity per customer. > >Other advantages: the $200 ODU is no longer customer equipment and >CAPEX, but network equipment, and as such, can operate under a longer >break-even timeline, and be financed by infrastructure PE funds, for >example. As a result, churn has a much lower financial impact on the >operator. > >The main reason why this wouldn't work today is that EPON, as we know, >is synchronous, and requires the OLT to orchestrate the amount of time >each ONU can transmit, and when. Having wireless hops and media >conversions will introduce latencies which can break down the >communications (e.g. one ONU may transmit, get delayed on the radio >link, and end up overlapping another ONU that transmitted on the next >slot). Thus, either the "magic" box needs to account for this, or an >new hybrid EPON-wireless protocol developed. > >My main point here: the industry is moving away from the unconnected. >All the claims I heard and saw at MWC about "connecting the >unconnected" had zero resonance with the financial drivers that the >unconnected really operate under, on top of IT literacy, digital >skills, devices, power... > >Best, > >Mike >On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink ><starlink@lists.bufferbloat.net>, wrote: >> To change the topic - curious to thoughts on FiWi. >> >> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS >> Radios, Antennas) and which is point to point inside a building >> connected to virtualized APs fiber hops away. Each remote radio head >> (RRH) would consume 5W or less and only when active. No need for >things >> like zigbee, or meshes, or threads as each radio has a fiber >connection >> via Corning's actifi or equivalent. Eliminate the AP/Client power >> imbalance. Plastics also can house smoke or other sensors. >> >> Some reminders from Paul Baran in 1994 (and from David Reed) >> >> o) Shorter range rf transceivers connected to fiber could produce a >> significant improvement - - tremendous improvement, really. >> o) a mixture of terrestrial links plus shorter range radio links has >the >> effect of increasing by orders and orders of magnitude the amount of >> frequency spectrum that can be made available. >> o) By authorizing high power to support a few users to reach slightly >> longer distances we deprive ourselves of the opportunity to serve the >> many. >> o) Communications systems can be built with 10dB ratio >> o) Digital transmission when properly done allows a small signal to >> noise ratio to be used successfully to retrieve an error free signal. >> o) And, never forget, any transmission capacity not used is wasted >> forever, like water over the dam. Not using such techniques represent >> lost opportunity. >> >> And on waveguides: >> >> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, >> independent of modulation" >> o) “Copper cables and PCB traces are very frequency dependent. At >> 100Gb/s, the loss is in dB/inch." >> o) "Free space: the power density of the radio waves decreases with >the >> square of distance from the transmitting antenna due to spreading of >the >> electromagnetic energy in space according to the inverse square law" >> >> The sunk costs & long-lived parts of FiWi are the fiber and the CPE >> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could >be >> pluggable, allowing for field upgrades. Just like swapping out SFP in >a >> data center. >> >> This approach basically drives out WiFi latency by eliminating shared >> queues and increases capacity by orders of magnitude by leveraging >10dB >> in the spatial dimension, all of which is achieved by a physical >design. >> Just place enough RRHs as needed (similar to a pop up sprinkler in an >> irrigation system.) >> >> Start and build this for an MDU and the value of the building >improves. >> Sadly, there seems no way to capture that value other than over long >> term use. It doesn't matter whether the leader of the HOA tries to >> capture the value or if a last mile provider tries. The value remains >> sunk or hidden with nothing on the asset side of the balance sheet. >> We've got a CAPEX spend that has to be made up via "OPEX returns" >over >> years. >> >> But the asset is there. >> >> How do we do this? >> >> Bob >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink [-- Attachment #2: Type: text/html, Size: 10121 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] On FiWi 2023-03-14 16:54 ` [Starlink] [Rpm] " Robert McMahon @ 2023-03-14 17:06 ` Robert McMahon 2023-03-14 17:11 ` [Starlink] [Bloat] " Sebastian Moeller 0 siblings, 1 reply; 9+ messages in thread From: Robert McMahon @ 2023-03-14 17:06 UTC (permalink / raw) To: Mike Puchol; +Cc: Dave Taht via Starlink, Rpm, libreqos, bloat [-- Attachment #1: Type: text/plain, Size: 9523 bytes --] The ISP could charge per radio head and manage the system from a FiWi head end which they own. Virtualize the APs. Get rid of SoC complexity and costly O&M via simplicity. Eliminate all the incremental engineering that has gone astray, e.g. bloat and over powered APs. Bob On Mar 14, 2023, 9:49 AM, at 9:49 AM, Robert McMahon <rjmcmahon@rjmcmahon.com> wrote: >Hi Mike, > >I'm thinking more of fiber to the room. The last few meters are wifi >everything else is fiber.. Those radios would be a max of 20' from the >associated STA. Then at phy rates of 2.8Gb/s per spatial stream. The >common MIMO is 2x2 so each radio head or wifi transceiver supports >5.6G, no queueing delay. Wholesale is $5 and retail $19.95 per >pluggable transceiver. Sold at Home Depot next to the irrigation aisle. >10 per house is $199 and each room gets a dedicated 5.8G phy rate. Need >more devices in a space? Pick an RRH with more cmos radios. Also, the >antennas would be patch antenna and fill the room properly. Then plug >in an optional sensor for fire alerting. > > >A digression. A lot of signal processing engineers have been working on >TX beam forming. The best beam is fiber. Just do that. It even can turn >corners and goes exactly to where it's needed at very low energies. >This is similar to pvc pipes in irrigation systems. They're designed to >take water to spray heads. > >The cost is the cable plant. That's labor more than materials. Similar >for irrigation, pvc is inexpensive and lasts decades. A return labor >means use future proof materials, e.g. fiber. > >Bob > > > >On Mar 14, 2023, 4:10 AM, at 4:10 AM, Mike Puchol via Rpm ><rpm@lists.bufferbloat.net> wrote: >>Hi Bob, >> >>You hit on a set of very valid points, which I'll complement with my >>views on where the industry (the bit of it that affects WISPs) is >>heading, and what I saw at the MWC in Barcelona. Love the FiWi term >:-) >> >>I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, >>and Mimosa, but also newer entrants such as Tarana, increase the >>performance and on-paper specs of their equipment. My examples below >>are centered on the African market, if you operate in Europe or the >US, >>where you can charge customers a higher install fee, or even charge >>them a break-up fee if they don't return equipment, the economics >work. >> >>Where currently a ~$500 sector radio could serve ~60 endpoints, at a >>cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the >>antenna that you mount on the roof), and supply ~2.5 Mbps CIR per >>endpoint, the evolution is now a ~$2,000+ sector radio, a $200 >>endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR >>per endpoint. >> >>If every customer a WISP installs represents, say, $100 CAPEX at >>install time ($50 for the antenna + cabling, router, etc), and you >>charge a $30 install fee, you have $70 to recover, and you recover >from >>the monthly contribution the customer makes. If the contribution after >>OPEX is, say, $10, it takes you 7 months to recover the full install >>cost. Not bad, doable even in low-income markets. >> >>Fast-forward to the next-generation version. Now, the CAPEX at install >>is $250, you need to recover $220, and it will take you 22 months, >>which is above the usual 18 months that investors look for. >> >>The focus, thereby, has to be the lever that has the largest effect on >>the unit economics - which is the per-customer cost. I have drawn what >>my ideal FiWi network would look like: >> >> >> >>Taking you through this - we start with a 1-port, low-cost EPON OLT >(or >>you could go for 2, 4, 8 ports as you add capacity). This OLT has >>capacity for 64 ONUs on its single port. Instead of connecting the >>typical fiber infrastructure with kilometers of cables which break, >>require maintenance, etc. we insert an EPON to Ethernet converter (I >>added "magic" because these don't exist AFAIK). >> >>This converter allows us to connect our $2k sector radio, and serve >the >>$200 endpoints (ODUs) over wireless point-to-multipoint up to 10km >>away. Each ODU then has a reverse converter, which gives us EPON >again. >> >>Once we are back on EPON, we can insert splitters, for example, >>pre-connectorized outdoor 1:16 boxes. Every customer install now >>involves a 100 meter roll of pre-connectorized 2-core drop cable, and >a >>$20 EPON ONU. >> >>Using this deployment method, we could connect up to 16 customers to a >>single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. >>Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 >>(assuming the same $50 of extras we had before), and an even shorter >>break-even. In addition, as the endpoints support higher capacity, we >>can provision at least the same, if not more, capacity per customer. >> >>Other advantages: the $200 ODU is no longer customer equipment and >>CAPEX, but network equipment, and as such, can operate under a longer >>break-even timeline, and be financed by infrastructure PE funds, for >>example. As a result, churn has a much lower financial impact on the >>operator. >> >>The main reason why this wouldn't work today is that EPON, as we know, >>is synchronous, and requires the OLT to orchestrate the amount of time >>each ONU can transmit, and when. Having wireless hops and media >>conversions will introduce latencies which can break down the >>communications (e.g. one ONU may transmit, get delayed on the radio >>link, and end up overlapping another ONU that transmitted on the next >>slot). Thus, either the "magic" box needs to account for this, or an >>new hybrid EPON-wireless protocol developed. >> >>My main point here: the industry is moving away from the unconnected. >>All the claims I heard and saw at MWC about "connecting the >>unconnected" had zero resonance with the financial drivers that the >>unconnected really operate under, on top of IT literacy, digital >>skills, devices, power... >> >>Best, >> >>Mike >>On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink >><starlink@lists.bufferbloat.net>, wrote: >>> To change the topic - curious to thoughts on FiWi. >>> >>> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS >>> Radios, Antennas) and which is point to point inside a building >>> connected to virtualized APs fiber hops away. Each remote radio head >>> (RRH) would consume 5W or less and only when active. No need for >>things >>> like zigbee, or meshes, or threads as each radio has a fiber >>connection >>> via Corning's actifi or equivalent. Eliminate the AP/Client power >>> imbalance. Plastics also can house smoke or other sensors. >>> >>> Some reminders from Paul Baran in 1994 (and from David Reed) >>> >>> o) Shorter range rf transceivers connected to fiber could produce a >>> significant improvement - - tremendous improvement, really. >>> o) a mixture of terrestrial links plus shorter range radio links has >>the >>> effect of increasing by orders and orders of magnitude the amount of >>> frequency spectrum that can be made available. >>> o) By authorizing high power to support a few users to reach >slightly >>> longer distances we deprive ourselves of the opportunity to serve >the >>> many. >>> o) Communications systems can be built with 10dB ratio >>> o) Digital transmission when properly done allows a small signal to >>> noise ratio to be used successfully to retrieve an error free >signal. >>> o) And, never forget, any transmission capacity not used is wasted >>> forever, like water over the dam. Not using such techniques >represent >>> lost opportunity. >>> >>> And on waveguides: >>> >>> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, >>> independent of modulation" >>> o) “Copper cables and PCB traces are very frequency dependent. At >>> 100Gb/s, the loss is in dB/inch." >>> o) "Free space: the power density of the radio waves decreases with >>the >>> square of distance from the transmitting antenna due to spreading of >>the >>> electromagnetic energy in space according to the inverse square law" >>> >>> The sunk costs & long-lived parts of FiWi are the fiber and the CPE >>> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could >>be >>> pluggable, allowing for field upgrades. Just like swapping out SFP >in >>a >>> data center. >>> >>> This approach basically drives out WiFi latency by eliminating >shared >>> queues and increases capacity by orders of magnitude by leveraging >>10dB >>> in the spatial dimension, all of which is achieved by a physical >>design. >>> Just place enough RRHs as needed (similar to a pop up sprinkler in >an >>> irrigation system.) >>> >>> Start and build this for an MDU and the value of the building >>improves. >>> Sadly, there seems no way to capture that value other than over long >>> term use. It doesn't matter whether the leader of the HOA tries to >>> capture the value or if a last mile provider tries. The value >remains >>> sunk or hidden with nothing on the asset side of the balance sheet. >>> We've got a CAPEX spend that has to be made up via "OPEX returns" >>over >>> years. >>> >>> But the asset is there. >>> >>> How do we do this? >>> >>> Bob >>> _______________________________________________ >>> Starlink mailing list >>> Starlink@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/starlink [-- Attachment #2: Type: text/html, Size: 10771 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Bloat] [Rpm] On FiWi 2023-03-14 17:06 ` Robert McMahon @ 2023-03-14 17:11 ` Sebastian Moeller 2023-03-14 17:35 ` Robert McMahon 0 siblings, 1 reply; 9+ messages in thread From: Sebastian Moeller @ 2023-03-14 17:11 UTC (permalink / raw) To: Robert McMahon; +Cc: Mike Puchol, Dave Taht via Starlink, Rpm, libreqos, bloat Hi Bob, technically attractive, but the "charge per radio head" and :virtualize the AP" are show stoppers for me... I like my ISP, but I have a clear understanding that my ISPs goals and my goals are not perfectly aligned so I would never give them control of my in house network and even less if they start moving things into the clown^W cloud. That means running important functions on some one else's computers, giving that some one else effectively too much power. Regards Sebastian P.S.: The technical side you propose will also work just as well with me in control, even though that lacks a business to make it attractive for ISPs ;) > On Mar 14, 2023, at 18:06, Robert McMahon via Bloat <bloat@lists.bufferbloat.net> wrote: > > The ISP could charge per radio head and manage the system from a FiWi head end which they own. Virtualize the APs. Get rid of SoC complexity and costly O&M via simplicity. Eliminate all the incremental engineering that has gone astray, e.g. bloat and over powered APs. > > Bob > On Mar 14, 2023, at 9:49 AM, Robert McMahon <rjmcmahon@rjmcmahon.com> wrote: > Hi Mike, > > I'm thinking more of fiber to the room. The last few meters are wifi everything else is fiber.. Those radios would be a max of 20' from the associated STA. Then at phy rates of 2.8Gb/s per spatial stream. The common MIMO is 2x2 so each radio head or wifi transceiver supports 5.6G, no queueing delay. Wholesale is $5 and retail $19.95 per pluggable transceiver. Sold at Home Depot next to the irrigation aisle. 10 per house is $199 and each room gets a dedicated 5.8G phy rate. Need more devices in a space? Pick an RRH with more cmos radios. Also, the antennas would be patch antenna and fill the room properly. Then plug in an optional sensor for fire alerting. > > > A digression. A lot of signal processing engineers have been working on TX beam forming. The best beam is fiber. Just do that. It even can turn corners and goes exactly to where it's needed at very low energies. This is similar to pvc pipes in irrigation systems. They're designed to take water to spray heads. > > The cost is the cable plant. That's labor more than materials. Similar for irrigation, pvc is inexpensive and lasts decades. A return labor means use future proof materials, e.g. fiber. > > Bob > On Mar 14, 2023, at 4:10 AM, Mike Puchol via Rpm <rpm@lists.bufferbloat.net> wrote: > Hi Bob, > > You hit on a set of very valid points, which I'll complement with my views on where the industry (the bit of it that affects WISPs) is heading, and what I saw at the MWC in Barcelona. Love the FiWi term :-) > > I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, and Mimosa, but also newer entrants such as Tarana, increase the performance and on-paper specs of their equipment. My examples below are centered on the African market, if you operate in Europe or the US, where you can charge customers a higher install fee, or even charge them a break-up fee if they don't return equipment, the economics work. > > Where currently a ~$500 sector radio could serve ~60 endpoints, at a cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the antenna that you mount on the roof), and supply ~2.5 Mbps CIR per endpoint, the evolution is now a ~$2,000+ sector radio, a $200 endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR per endpoint. > > If every customer a WISP installs represents, say, $100 CAPEX at install time ($50 for the antenna + cabling, router, etc), and you charge a $30 install fee, you have $70 to recover, and you recover from the monthly contribution the customer makes. If the contribution after OPEX is, say, $10, it takes you 7 months to recover the full install cost. Not bad, doable even in low-income markets. > > Fast-forward to the next-generation version. Now, the CAPEX at install is $250, you need to recover $220, and it will take you 22 months, which is above the usual 18 months that investors look for. > > The focus, thereby, has to be the lever that has the largest effect on the unit economics - which is the per-customer cost. I have drawn what my ideal FiWi network would look like: > > > > Taking you through this - we start with a 1-port, low-cost EPON OLT (or you could go for 2, 4, 8 ports as you add capacity). This OLT has capacity for 64 ONUs on its single port. Instead of connecting the typical fiber infrastructure with kilometers of cables which break, require maintenance, etc. we insert an EPON to Ethernet converter (I added "magic" because these don't exist AFAIK). > > This converter allows us to connect our $2k sector radio, and serve the $200 endpoints (ODUs) over wireless point-to-multipoint up to 10km away. Each ODU then has a reverse converter, which gives us EPON again. > > Once we are back on EPON, we can insert splitters, for example, pre-connectorized outdoor 1:16 boxes. Every customer install now involves a 100 meter roll of pre-connectorized 2-core drop cable, and a $20 EPON ONU. > > Using this deployment method, we could connect up to 16 customers to a single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 (assuming the same $50 of extras we had before), and an even shorter break-even. In addition, as the endpoints support higher capacity, we can provision at least the same, if not more, capacity per customer. > > Other advantages: the $200 ODU is no longer customer equipment and CAPEX, but network equipment, and as such, can operate under a longer break-even timeline, and be financed by infrastructure PE funds, for example. As a result, churn has a much lower financial impact on the operator. > > The main reason why this wouldn't work today is that EPON, as we know, is synchronous, and requires the OLT to orchestrate the amount of time each ONU can transmit, and when. Having wireless hops and media conversions will introduce latencies which can break down the communications (e.g. one ONU may transmit, get delayed on the radio link, and end up overlapping another ONU that transmitted on the next slot). Thus, either the "magic" box needs to account for this, or an new hybrid EPON-wireless protocol developed. > > My main point here: the industry is moving away from the unconnected. All the claims I heard and saw at MWC about "connecting the unconnected" had zero resonance with the financial drivers that the unconnected really operate under, on top of IT literacy, digital skills, devices, power... > > Best, > > Mike > On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink <starlink@lists.bufferbloat.net>, wrote: >> To change the topic - curious to thoughts on FiWi. >> >> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS >> Radios, Antennas) and which is point to point inside a building >> connected to virtualized APs fiber hops away. Each remote radio head >> (RRH) would consume 5W or less and only when active. No need for things >> like zigbee, or meshes, or threads as each radio has a fiber connection >> via Corning's actifi or equivalent. Eliminate the AP/Client power >> imbalance. Plastics also can house smoke or other sensors. >> >> Some reminders from Paul Baran in 1994 (and from David Reed) >> >> o) Shorter range rf transceivers connected to fiber could produce a >> significant improvement - - tremendous improvement, really. >> o) a mixture of terrestrial links plus shorter range radio links has the >> effect of increasing by orders and orders of magnitude the amount of >> frequency spectrum that can be made available. >> o) By authorizing high power to support a few users to reach slightly >> longer distances we deprive ourselves of the opportunity to serve the >> many. >> o) Communications systems can be built with 10dB ratio >> o) Digital transmission when properly done allows a small signal to >> noise ratio to be used successfully to retrieve an error free signal. >> o) And, never forget, any transmission capacity not used is wasted >> forever, like water over the dam. Not using such techniques represent >> lost opportunity. >> >> And on waveguides: >> >> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, >> independent of modulation" >> o) “Copper cables and PCB traces are very frequency dependent. At >> 100Gb/s, the loss is in dB/inch." >> o) "Free space: the power density of the radio waves decreases with the >> square of distance from the transmitting antenna due to spreading of the >> electromagnetic energy in space according to the inverse square law" >> >> The sunk costs & long-lived parts of FiWi are the fiber and the CPE >> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could be >> pluggable, allowing for field upgrades. Just like swapping out SFP in a >> data center. >> >> This approach basically drives out WiFi latency by eliminating shared >> queues and increases capacity by orders of magnitude by leveraging 10dB >> in the spatial dimension, all of which is achieved by a physical design. >> Just place enough RRHs as needed (similar to a pop up sprinkler in an >> irrigation system.) >> >> Start and build this for an MDU and the value of the building improves. >> Sadly, there seems no way to capture that value other than over long >> term use. It doesn't matter whether the leader of the HOA tries to >> capture the value or if a last mile provider tries. The value remains >> sunk or hidden with nothing on the asset side of the balance sheet. >> We've got a CAPEX spend that has to be made up via "OPEX returns" over >> years. >> >> But the asset is there. >> >> How do we do this? >> >> Bob >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Bloat] [Rpm] On FiWi 2023-03-14 17:11 ` [Starlink] [Bloat] " Sebastian Moeller @ 2023-03-14 17:35 ` Robert McMahon 2023-03-14 17:54 ` [Starlink] [LibreQoS] " dan 0 siblings, 1 reply; 9+ messages in thread From: Robert McMahon @ 2023-03-14 17:35 UTC (permalink / raw) To: Sebastian Moeller Cc: Mike Puchol, Dave Taht via Starlink, Rpm, libreqos, bloat [-- Attachment #1: Type: text/plain, Size: 11046 bytes --] You could always do it yourself. Most people need high skilled network engineers to provide them IT services. This need is only going to grow and grow. We can help by producing better and simpler offerings, be they DIY or by service providers. Steve Job's almost didn't support the iPhone development because he hated "the orifices." Probably time for many of us to revisit our belief set. Does it move the needle, even if imperfectly? FiWi blows the needle off the gauge by my judgment. Who does it is secondary. Bob On Mar 14, 2023, 10:11 AM, at 10:11 AM, Sebastian Moeller <moeller0@gmx.de> wrote: >Hi Bob, > >technically attractive, but the "charge per radio head" and :virtualize >the AP" are show stoppers for me... I like my ISP, but I have a clear >understanding that my ISPs goals and my goals are not perfectly aligned >so I would never give them control of my in house network and even less >if they start moving things into the clown^W cloud. That means running >important functions on some one else's computers, giving that some one >else effectively too much power. > >Regards > Sebastian > >P.S.: The technical side you propose will also work just as well with >me in control, even though that lacks a business to make it attractive >for ISPs ;) > > >> On Mar 14, 2023, at 18:06, Robert McMahon via Bloat ><bloat@lists.bufferbloat.net> wrote: >> >> The ISP could charge per radio head and manage the system from a FiWi >head end which they own. Virtualize the APs. Get rid of SoC complexity >and costly O&M via simplicity. Eliminate all the incremental >engineering that has gone astray, e.g. bloat and over powered APs. >> >> Bob >> On Mar 14, 2023, at 9:49 AM, Robert McMahon <rjmcmahon@rjmcmahon.com> >wrote: >> Hi Mike, >> >> I'm thinking more of fiber to the room. The last few meters are wifi >everything else is fiber.. Those radios would be a max of 20' from the >associated STA. Then at phy rates of 2.8Gb/s per spatial stream. The >common MIMO is 2x2 so each radio head or wifi transceiver supports >5.6G, no queueing delay. Wholesale is $5 and retail $19.95 per >pluggable transceiver. Sold at Home Depot next to the irrigation aisle. >10 per house is $199 and each room gets a dedicated 5.8G phy rate. Need >more devices in a space? Pick an RRH with more cmos radios. Also, the >antennas would be patch antenna and fill the room properly. Then plug >in an optional sensor for fire alerting. >> >> >> A digression. A lot of signal processing engineers have been working >on TX beam forming. The best beam is fiber. Just do that. It even can >turn corners and goes exactly to where it's needed at very low >energies. This is similar to pvc pipes in irrigation systems. They're >designed to take water to spray heads. >> >> The cost is the cable plant. That's labor more than materials. >Similar for irrigation, pvc is inexpensive and lasts decades. A return >labor means use future proof materials, e.g. fiber. >> >> Bob >> On Mar 14, 2023, at 4:10 AM, Mike Puchol via Rpm ><rpm@lists.bufferbloat.net> wrote: >> Hi Bob, >> >> You hit on a set of very valid points, which I'll complement with my >views on where the industry (the bit of it that affects WISPs) is >heading, and what I saw at the MWC in Barcelona. Love the FiWi term :-) > >> >> I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium, >and Mimosa, but also newer entrants such as Tarana, increase the >performance and on-paper specs of their equipment. My examples below >are centered on the African market, if you operate in Europe or the US, >where you can charge customers a higher install fee, or even charge >them a break-up fee if they don't return equipment, the economics work. > >> >> Where currently a ~$500 sector radio could serve ~60 endpoints, at a >cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the >antenna that you mount on the roof), and supply ~2.5 Mbps CIR per >endpoint, the evolution is now a ~$2,000+ sector radio, a $200 >endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR >per endpoint. >> >> If every customer a WISP installs represents, say, $100 CAPEX at >install time ($50 for the antenna + cabling, router, etc), and you >charge a $30 install fee, you have $70 to recover, and you recover from >the monthly contribution the customer makes. If the contribution after >OPEX is, say, $10, it takes you 7 months to recover the full install >cost. Not bad, doable even in low-income markets. >> >> Fast-forward to the next-generation version. Now, the CAPEX at >install is $250, you need to recover $220, and it will take you 22 >months, which is above the usual 18 months that investors look for. >> >> The focus, thereby, has to be the lever that has the largest effect >on the unit economics - which is the per-customer cost. I have drawn >what my ideal FiWi network would look like: >> >> >> >> Taking you through this - we start with a 1-port, low-cost EPON OLT >(or you could go for 2, 4, 8 ports as you add capacity). This OLT has >capacity for 64 ONUs on its single port. Instead of connecting the >typical fiber infrastructure with kilometers of cables which break, >require maintenance, etc. we insert an EPON to Ethernet converter (I >added "magic" because these don't exist AFAIK). >> >> This converter allows us to connect our $2k sector radio, and serve >the $200 endpoints (ODUs) over wireless point-to-multipoint up to 10km >away. Each ODU then has a reverse converter, which gives us EPON again. > >> >> Once we are back on EPON, we can insert splitters, for example, >pre-connectorized outdoor 1:16 boxes. Every customer install now >involves a 100 meter roll of pre-connectorized 2-core drop cable, and a >$20 EPON ONU. >> >> Using this deployment method, we could connect up to 16 customers to >a single $200 endpoint, so the enpoint CAPEX per customer is now $12.5. >Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5 >(assuming the same $50 of extras we had before), and an even shorter >break-even. In addition, as the endpoints support higher capacity, we >can provision at least the same, if not more, capacity per customer. >> >> Other advantages: the $200 ODU is no longer customer equipment and >CAPEX, but network equipment, and as such, can operate under a longer >break-even timeline, and be financed by infrastructure PE funds, for >example. As a result, churn has a much lower financial impact on the >operator. >> >> The main reason why this wouldn't work today is that EPON, as we >know, is synchronous, and requires the OLT to orchestrate the amount of >time each ONU can transmit, and when. Having wireless hops and media >conversions will introduce latencies which can break down the >communications (e.g. one ONU may transmit, get delayed on the radio >link, and end up overlapping another ONU that transmitted on the next >slot). Thus, either the "magic" box needs to account for this, or an >new hybrid EPON-wireless protocol developed. >> >> My main point here: the industry is moving away from the unconnected. >All the claims I heard and saw at MWC about "connecting the >unconnected" had zero resonance with the financial drivers that the >unconnected really operate under, on top of IT literacy, digital >skills, devices, power... >> >> Best, >> >> Mike >> On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink ><starlink@lists.bufferbloat.net>, wrote: >>> To change the topic - curious to thoughts on FiWi. >>> >>> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS >>> Radios, Antennas) and which is point to point inside a building >>> connected to virtualized APs fiber hops away. Each remote radio head > >>> (RRH) would consume 5W or less and only when active. No need for >things >>> like zigbee, or meshes, or threads as each radio has a fiber >connection >>> via Corning's actifi or equivalent. Eliminate the AP/Client power >>> imbalance. Plastics also can house smoke or other sensors. >>> >>> Some reminders from Paul Baran in 1994 (and from David Reed) >>> >>> o) Shorter range rf transceivers connected to fiber could produce a >>> significant improvement - - tremendous improvement, really. >>> o) a mixture of terrestrial links plus shorter range radio links has >the >>> effect of increasing by orders and orders of magnitude the amount of > >>> frequency spectrum that can be made available. >>> o) By authorizing high power to support a few users to reach >slightly >>> longer distances we deprive ourselves of the opportunity to serve >the >>> many. >>> o) Communications systems can be built with 10dB ratio >>> o) Digital transmission when properly done allows a small signal to >>> noise ratio to be used successfully to retrieve an error free >signal. >>> o) And, never forget, any transmission capacity not used is wasted >>> forever, like water over the dam. Not using such techniques >represent >>> lost opportunity. >>> >>> And on waveguides: >>> >>> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber, >>> independent of modulation" >>> o) “Copper cables and PCB traces are very frequency dependent. At >>> 100Gb/s, the loss is in dB/inch." >>> o) "Free space: the power density of the radio waves decreases with >the >>> square of distance from the transmitting antenna due to spreading of >the >>> electromagnetic energy in space according to the inverse square law" > >>> >>> The sunk costs & long-lived parts of FiWi are the fiber and the CPE >>> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could >be >>> pluggable, allowing for field upgrades. Just like swapping out SFP >in a >>> data center. >>> >>> This approach basically drives out WiFi latency by eliminating >shared >>> queues and increases capacity by orders of magnitude by leveraging >10dB >>> in the spatial dimension, all of which is achieved by a physical >design. >>> Just place enough RRHs as needed (similar to a pop up sprinkler in >an >>> irrigation system.) >>> >>> Start and build this for an MDU and the value of the building >improves. >>> Sadly, there seems no way to capture that value other than over long > >>> term use. It doesn't matter whether the leader of the HOA tries to >>> capture the value or if a last mile provider tries. The value >remains >>> sunk or hidden with nothing on the asset side of the balance sheet. >>> We've got a CAPEX spend that has to be made up via "OPEX returns" >over >>> years. >>> >>> But the asset is there. >>> >>> How do we do this? >>> >>> Bob >>> _______________________________________________ >>> Starlink mailing list >>> Starlink@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/starlink >> _______________________________________________ >> Bloat mailing list >> Bloat@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat [-- Attachment #2: Type: text/html, Size: 11652 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 17:35 ` Robert McMahon @ 2023-03-14 17:54 ` dan 2023-03-14 18:14 ` Robert McMahon 0 siblings, 1 reply; 9+ messages in thread From: dan @ 2023-03-14 17:54 UTC (permalink / raw) To: Robert McMahon Cc: Sebastian Moeller, Dave Taht via Starlink, Mike Puchol, bloat, Rpm, libreqos > You could always do it yourself. > > Most people need high skilled network engineers to provide them IT services. This need is only going to grow and grow. We can help by producing better and simpler offerings, be they DIY or by service providers. > > Steve Job's almost didn't support the iPhone development because he hated "the orifices." Probably time for many of us to revisit our belief set. Does it move the needle, even if imperfectly? > > FiWi blows the needle off the gauge by my judgment. Who does it is secondary. > > Bob most people are unwilling to pay for those services also lol. I don't see the paradigm of discreet routers/nat per prem anytime soon. If you subtract that piece of it then we're basically just talking XGSPON or similar. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 17:54 ` [Starlink] [LibreQoS] " dan @ 2023-03-14 18:14 ` Robert McMahon 2023-03-14 19:18 ` dan 0 siblings, 1 reply; 9+ messages in thread From: Robert McMahon @ 2023-03-14 18:14 UTC (permalink / raw) To: dan Cc: Sebastian Moeller, Dave Taht via Starlink, Mike Puchol, bloat, Rpm, libreqos [-- Attachment #1: Type: text/plain, Size: 1352 bytes --] It's not discrete routers. It's more like a transceiver. WiFi is already splitting at the MAC for MLO. I perceive two choices for the split, one at the PHY DAC or, two, a minimalist 802.3 tunneling of 802.11 back to the FiWi head end. Use 802.3 to leverage merchant silicon supporting up to 200 or so RRHs or even move the baseband DSP there. I think a split PHY may not work well but a thorough eng analysis is still warranted. Bob Get BlueMail for Android On Mar 14, 2023, 10:54 AM, at 10:54 AM, dan <dandenson@gmail.com> wrote: >> You could always do it yourself. >> >> Most people need high skilled network engineers to provide them IT >services. This need is only going to grow and grow. We can help by >producing better and simpler offerings, be they DIY or by service >providers. >> >> Steve Job's almost didn't support the iPhone development because he >hated "the orifices." Probably time for many of us to revisit our >belief set. Does it move the needle, even if imperfectly? >> >> FiWi blows the needle off the gauge by my judgment. Who does it is >secondary. >> >> Bob > >most people are unwilling to pay for those services also lol. > >I don't see the paradigm of discreet routers/nat per prem anytime >soon. If you subtract that piece of it then we're basically just >talking XGSPON or similar. [-- Attachment #2: Type: text/html, Size: 1899 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 18:14 ` Robert McMahon @ 2023-03-14 19:18 ` dan 2023-03-14 19:30 ` rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: dan @ 2023-03-14 19:18 UTC (permalink / raw) To: Robert McMahon Cc: Sebastian Moeller, Dave Taht via Starlink, Mike Puchol, bloat, Rpm, libreqos end users are still going to want their own router/firewall. That's my point, I don't see how you can have that on-prem firewall while having a remote radio that's useful. I would adamantly oppose anyone I know passing their firewall off to the upstream vendor. I run an MSP and I would offer a customer to drop my services if they were to buy into something like this on the business side. So I really only see this sort of concept for campus networks where the end users are 'part' of the entity. On Tue, Mar 14, 2023 at 12:14 PM Robert McMahon <rjmcmahon@rjmcmahon.com> wrote: > > It's not discrete routers. It's more like a transceiver. WiFi is already splitting at the MAC for MLO. I perceive two choices for the split, one at the PHY DAC or, two, a minimalist 802.3 tunneling of 802.11 back to the FiWi head end. Use 802.3 to leverage merchant silicon supporting up to 200 or so RRHs or even move the baseband DSP there. I think a split PHY may not work well but a thorough eng analysis is still warranted. > > Bob > > > > Get BlueMail for Android > On Mar 14, 2023, at 10:54 AM, dan <dandenson@gmail.com> wrote: >>> >>> You could always do it yourself. >>> >>> Most people need high skilled network engineers to provide them IT services. This need is only going to grow and grow. We can help by producing better and simpler offerings, be they DIY or by service providers. >>> >>> Steve Job's almost didn't support the iPhone development because he hated "the orifices." Probably time for many of us to revisit our belief set. Does it move the needle, even if imperfectly? >>> >>> FiWi blows the needle off the gauge by my judgment. Who does it is secondary. >>> >>> Bob >> >> >> most people are unwilling to pay for those services also lol. >> >> I don't see the paradigm of discreet routers/nat per prem anytime >> soon. If you subtract that piece of it then we're basically just >> talking XGSPON or similar. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 19:18 ` dan @ 2023-03-14 19:30 ` rjmcmahon 2023-03-14 23:30 ` Bruce Perens 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-14 19:30 UTC (permalink / raw) To: dan Cc: Sebastian Moeller, Dave Taht via Starlink, Mike Puchol, bloat, Rpm, libreqos The design has to be flexible so DIY w/local firewall is fine. I'll disagree though that early & late majority care about firewalls. They want high-quality access that is secure & private. Both of these require high skill network engineers on staff. DIY is hard here. Intrusion detection systems, etc. are non-trivial. The days of broadcast NFL networks are over. I disagree to with nobody wanting to pay for quality access to knowledge based networks. Not that many years ago, nobody wanted to pay to teach women to read either. Then, nobody wanted to pay for university. I grew up in the latter and figured out that I needed come up with payment somehow to develop my brain. Otherwise, I was screwed. So, if it's a chatGPT, advertising system - sure wrong market. Free shit, even provided by Google, is mostly shit. Connect to something real without the privacy invasions, no queueing, etc. I think it's worth it in spades despite the idea that we shouldn't invest so people, regardless of gender, etc. can learn to read. Bob > end users are still going to want their own router/firewall. That's > my point, I don't see how you can have that on-prem firewall while > having a remote radio that's useful. > > I would adamantly oppose anyone I know passing their firewall off to > the upstream vendor. I run an MSP and I would offer a customer to > drop my services if they were to buy into something like this on the > business side. > > So I really only see this sort of concept for campus networks where > the end users are 'part' of the entity. > > On Tue, Mar 14, 2023 at 12:14 PM Robert McMahon > <rjmcmahon@rjmcmahon.com> wrote: >> >> It's not discrete routers. It's more like a transceiver. WiFi is >> already splitting at the MAC for MLO. I perceive two choices for the >> split, one at the PHY DAC or, two, a minimalist 802.3 tunneling of >> 802.11 back to the FiWi head end. Use 802.3 to leverage merchant >> silicon supporting up to 200 or so RRHs or even move the baseband DSP >> there. I think a split PHY may not work well but a thorough eng >> analysis is still warranted. >> >> Bob >> >> >> >> Get BlueMail for Android >> On Mar 14, 2023, at 10:54 AM, dan <dandenson@gmail.com> wrote: >>>> >>>> You could always do it yourself. >>>> >>>> Most people need high skilled network engineers to provide them IT >>>> services. This need is only going to grow and grow. We can help by >>>> producing better and simpler offerings, be they DIY or by service >>>> providers. >>>> >>>> Steve Job's almost didn't support the iPhone development because he >>>> hated "the orifices." Probably time for many of us to revisit our >>>> belief set. Does it move the needle, even if imperfectly? >>>> >>>> FiWi blows the needle off the gauge by my judgment. Who does it is >>>> secondary. >>>> >>>> Bob >>> >>> >>> most people are unwilling to pay for those services also lol. >>> >>> I don't see the paradigm of discreet routers/nat per prem anytime >>> soon. If you subtract that piece of it then we're basically just >>> talking XGSPON or similar. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 19:30 ` rjmcmahon @ 2023-03-14 23:30 ` Bruce Perens 2023-03-15 0:11 ` Robert McMahon 0 siblings, 1 reply; 9+ messages in thread From: Bruce Perens @ 2023-03-14 23:30 UTC (permalink / raw) To: rjmcmahon; +Cc: dan, libreqos, Dave Taht via Starlink, Rpm, bloat [-- Attachment #1: Type: text/plain, Size: 4526 bytes --] Let's remember some of the reasons why a lot of wireless-last-mile and mesh networking plans have failed to date. Most people who hand-wave about wireless _still_ don't understand Fresnel zones. Most don't account for the possibility of multipath. Or the hidden transmitter problem. Or absorption. Or noise. Spread spectrum does not cure all ills. You are *trading* bandwidth for processing gain. You also trade digital modulations that reach incredibly low s/n for bandwidth. You can only extract so much of your link budget from processing or efficient modulation. Many modern systems already operate at that point. All usable spectrum has been allocated at any particular time. At least 50% is spent on supporting legacy systems. Your greatest spectrum availability will be at the highest possible frequency, just because of 1/f. There your largest consideration will be absorption. Thanks Bruce On Tue, Mar 14, 2023 at 12:30 PM rjmcmahon via Starlink < starlink@lists.bufferbloat.net> wrote: > The design has to be flexible so DIY w/local firewall is fine. > > I'll disagree though that early & late majority care about firewalls. > They want high-quality access that is secure & private. Both of these > require high skill network engineers on staff. DIY is hard here. > Intrusion detection systems, etc. are non-trivial. The days of broadcast > NFL networks are over. > > I disagree to with nobody wanting to pay for quality access to knowledge > based networks. Not that many years ago, nobody wanted to pay to teach > women to read either. Then, nobody wanted to pay for university. I grew > up in the latter and figured out that I needed come up with payment > somehow to develop my brain. Otherwise, I was screwed. > > So, if it's a chatGPT, advertising system - sure wrong market. Free > shit, even provided by Google, is mostly shit. > > Connect to something real without the privacy invasions, no queueing, > etc. I think it's worth it in spades despite the idea that we shouldn't > invest so people, regardless of gender, etc. can learn to read. > > Bob > > > end users are still going to want their own router/firewall. That's > > my point, I don't see how you can have that on-prem firewall while > > having a remote radio that's useful. > > > > I would adamantly oppose anyone I know passing their firewall off to > > the upstream vendor. I run an MSP and I would offer a customer to > > drop my services if they were to buy into something like this on the > > business side. > > > > So I really only see this sort of concept for campus networks where > > the end users are 'part' of the entity. > > > > On Tue, Mar 14, 2023 at 12:14 PM Robert McMahon > > <rjmcmahon@rjmcmahon.com> wrote: > >> > >> It's not discrete routers. It's more like a transceiver. WiFi is > >> already splitting at the MAC for MLO. I perceive two choices for the > >> split, one at the PHY DAC or, two, a minimalist 802.3 tunneling of > >> 802.11 back to the FiWi head end. Use 802.3 to leverage merchant > >> silicon supporting up to 200 or so RRHs or even move the baseband DSP > >> there. I think a split PHY may not work well but a thorough eng > >> analysis is still warranted. > >> > >> Bob > >> > >> > >> > >> Get BlueMail for Android > >> On Mar 14, 2023, at 10:54 AM, dan <dandenson@gmail.com> wrote: > >>>> > >>>> You could always do it yourself. > >>>> > >>>> Most people need high skilled network engineers to provide them IT > >>>> services. This need is only going to grow and grow. We can help by > >>>> producing better and simpler offerings, be they DIY or by service > >>>> providers. > >>>> > >>>> Steve Job's almost didn't support the iPhone development because he > >>>> hated "the orifices." Probably time for many of us to revisit our > >>>> belief set. Does it move the needle, even if imperfectly? > >>>> > >>>> FiWi blows the needle off the gauge by my judgment. Who does it is > >>>> secondary. > >>>> > >>>> Bob > >>> > >>> > >>> most people are unwilling to pay for those services also lol. > >>> > >>> I don't see the paradigm of discreet routers/nat per prem anytime > >>> soon. If you subtract that piece of it then we're basically just > >>> talking XGSPON or similar. > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > -- Bruce Perens K6BP [-- Attachment #2: Type: text/html, Size: 6185 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-14 23:30 ` Bruce Perens @ 2023-03-15 0:11 ` Robert McMahon 2023-03-15 5:20 ` Bruce Perens 0 siblings, 1 reply; 9+ messages in thread From: Robert McMahon @ 2023-03-15 0:11 UTC (permalink / raw) To: Bruce Perens; +Cc: dan, libreqos, Dave Taht via Starlink, Rpm, bloat [-- Attachment #1: Type: text/plain, Size: 5825 bytes --] This isn't last mile nor mesh. It's last meters. The AP/STA power asymmetry shows that a low power STA can reach an AP, but the AP needs to blast a CTS so every other possible conversation has to halt. It's like a person in a large conference room where one person with a megaphone is yelling to someone distant (and that person doesn't have a megaphone to respond.) Better if everyone reduced their energy to just enough and get rid of all megaphone. Reduce AP/STA density which is what drives excessive queuing delays. The free space loss works in the advantage in this model. The trick is structured fiber. But to what exactly? The problem with structured wiring before was that nobody wanted to plug into a wall jack or nobody wants to be on a leash. Look up. How many led lights are over our heads in every space? Electric to photon conversion is happening. We don't blast illumination anymore, either. Semiconductor mfg is changing everything. Best to embrace it vs adding another part to Frankenstein. Bob Get BlueMail for Android On Mar 14, 2023, 4:30 PM, at 4:30 PM, Bruce Perens <bruce@perens.com> wrote: >Let's remember some of the reasons why a lot of wireless-last-mile and >mesh >networking plans have failed to date. > >Most people who hand-wave about wireless _still_ don't understand >Fresnel >zones. >Most don't account for the possibility of multipath. >Or the hidden transmitter problem. >Or absorption. >Or noise. > >Spread spectrum does not cure all ills. You are *trading* bandwidth for >processing gain. >You also trade digital modulations that reach incredibly low s/n for >bandwidth. >You can only extract so much of your link budget from processing or >efficient modulation. Many modern systems already operate at that >point. > >All usable spectrum has been allocated at any particular time. At least >50% >is spent on supporting legacy systems. > >Your greatest spectrum availability will be at the highest possible >frequency, just because of 1/f. There your largest consideration will >be >absorption. > > Thanks > > Bruce > > > >On Tue, Mar 14, 2023 at 12:30 PM rjmcmahon via Starlink < >starlink@lists.bufferbloat.net> wrote: > >> The design has to be flexible so DIY w/local firewall is fine. >> >> I'll disagree though that early & late majority care about firewalls. >> They want high-quality access that is secure & private. Both of these >> require high skill network engineers on staff. DIY is hard here. >> Intrusion detection systems, etc. are non-trivial. The days of >broadcast >> NFL networks are over. >> >> I disagree to with nobody wanting to pay for quality access to >knowledge >> based networks. Not that many years ago, nobody wanted to pay to >teach >> women to read either. Then, nobody wanted to pay for university. I >grew >> up in the latter and figured out that I needed come up with payment >> somehow to develop my brain. Otherwise, I was screwed. >> >> So, if it's a chatGPT, advertising system - sure wrong market. Free >> shit, even provided by Google, is mostly shit. >> >> Connect to something real without the privacy invasions, no queueing, >> etc. I think it's worth it in spades despite the idea that we >shouldn't >> invest so people, regardless of gender, etc. can learn to read. >> >> Bob >> >> > end users are still going to want their own router/firewall. >That's >> > my point, I don't see how you can have that on-prem firewall while >> > having a remote radio that's useful. >> > >> > I would adamantly oppose anyone I know passing their firewall off >to >> > the upstream vendor. I run an MSP and I would offer a customer to >> > drop my services if they were to buy into something like this on >the >> > business side. >> > >> > So I really only see this sort of concept for campus networks where >> > the end users are 'part' of the entity. >> > >> > On Tue, Mar 14, 2023 at 12:14 PM Robert McMahon >> > <rjmcmahon@rjmcmahon.com> wrote: >> >> >> >> It's not discrete routers. It's more like a transceiver. WiFi is >> >> already splitting at the MAC for MLO. I perceive two choices for >the >> >> split, one at the PHY DAC or, two, a minimalist 802.3 tunneling of >> >> 802.11 back to the FiWi head end. Use 802.3 to leverage merchant >> >> silicon supporting up to 200 or so RRHs or even move the baseband >DSP >> >> there. I think a split PHY may not work well but a thorough eng >> >> analysis is still warranted. >> >> >> >> Bob >> >> >> >> >> >> >> >> Get BlueMail for Android >> >> On Mar 14, 2023, at 10:54 AM, dan <dandenson@gmail.com> wrote: >> >>>> >> >>>> You could always do it yourself. >> >>>> >> >>>> Most people need high skilled network engineers to provide them >IT >> >>>> services. This need is only going to grow and grow. We can help >by >> >>>> producing better and simpler offerings, be they DIY or by >service >> >>>> providers. >> >>>> >> >>>> Steve Job's almost didn't support the iPhone development >because he >> >>>> hated "the orifices." Probably time for many of us to revisit >our >> >>>> belief set. Does it move the needle, even if imperfectly? >> >>>> >> >>>> FiWi blows the needle off the gauge by my judgment. Who does it >is >> >>>> secondary. >> >>>> >> >>>> Bob >> >>> >> >>> >> >>> most people are unwilling to pay for those services also lol. >> >>> >> >>> I don't see the paradigm of discreet routers/nat per prem anytime >> >>> soon. If you subtract that piece of it then we're basically just >> >>> talking XGSPON or similar. >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink >> > > >-- >Bruce Perens K6BP [-- Attachment #2: Type: text/html, Size: 8283 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-15 0:11 ` Robert McMahon @ 2023-03-15 5:20 ` Bruce Perens 2023-03-15 17:32 ` rjmcmahon 0 siblings, 1 reply; 9+ messages in thread From: Bruce Perens @ 2023-03-15 5:20 UTC (permalink / raw) To: Robert McMahon; +Cc: dan, libreqos, Dave Taht via Starlink, Rpm, bloat [-- Attachment #1: Type: text/plain, Size: 313 bytes --] 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. [-- Attachment #2: Type: text/html, Size: 672 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-15 5:20 ` Bruce Perens @ 2023-03-15 17:32 ` rjmcmahon 2023-03-15 17:42 ` dan 2023-03-15 17:43 ` [Starlink] [Bloat] [LibreQoS] [Rpm] " Sebastian Moeller 0 siblings, 2 replies; 9+ messages in thread From: rjmcmahon @ 2023-03-15 17:32 UTC (permalink / raw) To: Bruce Perens; +Cc: dan, libreqos, Dave Taht via Starlink, Rpm, bloat 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. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [LibreQoS] [Bloat] [Rpm] On FiWi 2023-03-15 17:32 ` rjmcmahon @ 2023-03-15 17:42 ` dan 2023-03-15 19:33 ` [Starlink] [Bloat] [LibreQoS] " David Lang 2023-03-15 17:43 ` [Starlink] [Bloat] [LibreQoS] [Rpm] " Sebastian Moeller 1 sibling, 1 reply; 9+ messages in thread From: dan @ 2023-03-15 17:42 UTC (permalink / raw) To: rjmcmahon; +Cc: Bruce Perens, libreqos, Dave Taht via Starlink, Rpm, bloat [-- Attachment #1: Type: text/plain, Size: 3874 bytes --] 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. > [-- Attachment #2: Type: text/html, Size: 4737 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Bloat] [LibreQoS] [Rpm] On FiWi 2023-03-15 17:42 ` dan @ 2023-03-15 19:33 ` David Lang 2023-03-15 19:39 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht 0 siblings, 1 reply; 9+ messages in thread From: David Lang @ 2023-03-15 19:33 UTC (permalink / raw) To: dan; +Cc: rjmcmahon, Dave Taht via Starlink, Rpm, bloat, Bruce Perens, libreqos [-- Attachment #1: Type: text/plain, Size: 5367 bytes --] 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. 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. >> > [-- Attachment #2: Type: text/plain, Size: 140 bytes --] _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 19:33 ` [Starlink] [Bloat] [LibreQoS] " David Lang @ 2023-03-15 19:39 ` Dave Taht 2023-03-15 21:52 ` David Lang 0 siblings, 1 reply; 9+ messages in thread From: Dave Taht @ 2023-03-15 19:39 UTC (permalink / raw) To: David Lang Cc: dan, Rpm, libreqos, Bruce Perens, Dave Taht via Starlink, bloat 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 19:39 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht @ 2023-03-15 21:52 ` David Lang 2023-03-15 22:04 ` Dave Taht 0 siblings, 1 reply; 9+ messages in thread From: David Lang @ 2023-03-15 21:52 UTC (permalink / raw) To: Dave Taht Cc: David Lang, dan, Rpm, libreqos, Bruce Perens, Dave Taht via Starlink, bloat [-- Attachment #1: Type: text/plain, Size: 6555 bytes --] On Wed, 15 Mar 2023, Dave Taht wrote: > 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?) no good stats this year. still using the wndr3800s. Lots of people commenting on how well the network did, but we were a bit behind this year and didn't get good monitoring in place. No cake yet. I think this is what you mean https://www.youtube.com/watch?v=UXvGbEYeWp0 > 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 > > > > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 21:52 ` David Lang @ 2023-03-15 22:04 ` Dave Taht 2023-03-15 22:08 ` dan 0 siblings, 1 reply; 9+ messages in thread From: Dave Taht @ 2023-03-15 22:04 UTC (permalink / raw) To: David Lang Cc: dan, Rpm, libreqos, Bruce Perens, Dave Taht via Starlink, bloat On Wed, Mar 15, 2023 at 2:52 PM David Lang <david@lang.hm> wrote: > > On Wed, 15 Mar 2023, Dave Taht wrote: > > > 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?) > > no good stats this year. still using the wndr3800s. Lots of people commenting on > how well the network did, but we were a bit behind this year and didn't get good > monitoring in place. No cake yet. > > I think this is what you mean > https://www.youtube.com/watch?v=UXvGbEYeWp0 A point I would like to make for the africa contingent here is that you do not need the latest technology for africa. We get 300Mbit out of hardware built in the late 00s, like the wndr3800. The ath9k chipset is STILL manufactured, the software mature, and for all I know millions of routers like these are lying in junk bins worldwide, ready to be recycled and reflashed. One libreqos customer deployed libreqos, and took a look at the 600+ ubnt AGWs (ath9k based), on the shelf that could be fq_codeled, especially on the wifi... built a custom openwrt imagebuilder image for em, reflashed and redistributed them. The wndr3800s were especially well built. I would expect them to last decades. I had one failure of one that had been in the field for over 10 years... I thought it was the flash chip... no, it was the power supply! > > 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 22:04 ` Dave Taht @ 2023-03-15 22:08 ` dan 0 siblings, 0 replies; 9+ messages in thread From: dan @ 2023-03-15 22:08 UTC (permalink / raw) To: Dave Taht Cc: Rpm, libreqos, Bruce Perens, Dave Taht via Starlink, bloat, David Lang [-- Attachment #1: Type: text/plain, Size: 9187 bytes --] On Mar 15, 2023 at 4:04:27 PM, Dave Taht <dave.taht@gmail.com> wrote: > On Wed, Mar 15, 2023 at 2:52 PM David Lang <david@lang.hm> wrote: > > > On Wed, 15 Mar 2023, Dave Taht wrote: > > > > 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?) > > > no good stats this year. still using the wndr3800s. Lots of people > commenting on > > how well the network did, but we were a bit behind this year and didn't > get good > > monitoring in place. No cake yet. > > > I think this is what you mean > > https://www.youtube.com/watch?v=UXvGbEYeWp0 > > > > A point I would like to make for the africa contingent here is that > you do not need the latest > technology for africa. We get 300Mbit out of hardware built in the > late 00s, like the wndr3800. The ath9k chipset is STILL manufactured, > the software mature, and for all I know millions of routers > like these are lying in junk bins worldwide, ready to be recycled and > reflashed. > > One libreqos customer deployed libreqos, and took a look at the 600+ > ubnt AGWs (ath9k based), on the shelf that could be fq_codeled, > especially on the wifi... built a custom openwrt imagebuilder image > for em, reflashed and redistributed them. > > The wndr3800s were especially well built. I would expect them to last > decades. I had one failure of one that had been in the field for over > 10 years... I thought it was the flash chip... no, it was the power > supply! > > > > 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 > Much of the hardware dumped on the US market in particular is especially poorly made. Ie, engineered for our disposable market. Lots of netgear products for example have a typical usable life of just 2-3 years if that, and then the caps have busted or some patina on the boards has killed them. I know Europe has some standards on this as well as South Korea to give them longer life. To the point, it’s not realistic to recycle these items from the US to other place because they were ‘built to fail’. [-- Attachment #2: Type: text/html, Size: 16375 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Bloat] [LibreQoS] [Rpm] On FiWi 2023-03-15 17:32 ` rjmcmahon 2023-03-15 17:42 ` dan @ 2023-03-15 17:43 ` Sebastian Moeller 2023-03-15 17:49 ` rjmcmahon 1 sibling, 1 reply; 9+ messages in thread From: Sebastian Moeller @ 2023-03-15 17:43 UTC (permalink / raw) To: rjmcmahon; +Cc: Bruce Perens, Dave Taht via Starlink, Rpm, dan, libreqos, bloat Hi Bob, I like your design sketch and the ideas behind it. > On Mar 15, 2023, at 18:32, rjmcmahon via Bloat <bloat@lists.bufferbloat.net> 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 Maybe design this to be dual band from the start to avoid the up/down "tdm" approach we currently use? Better yet go full duplex, which might be an option if we get enough radios that not much beamforming/MIMO is necessary? I obviously lack deep enough understanf=dingwhether this makes any sense or is just buzzword bingo from my side :) > > 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) I am weary of this kind of trust in continuous exponential growth... at one point we reach a limit and will need to figure out how to deal with congestion again, so why drop this capability on the way? The nice thing about AQMs is if there is no queue build up these basically do nothing... (might need some design changes to optimize an AQM to be as cheap as possible for the uncontended case)... > 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Bloat] [LibreQoS] [Rpm] On FiWi 2023-03-15 17:43 ` [Starlink] [Bloat] [LibreQoS] [Rpm] " Sebastian Moeller @ 2023-03-15 17:49 ` rjmcmahon 2023-03-15 17:53 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht 0 siblings, 1 reply; 9+ messages in thread From: rjmcmahon @ 2023-03-15 17:49 UTC (permalink / raw) To: Sebastian Moeller Cc: Bruce Perens, Dave Taht via Starlink, Rpm, dan, libreqos, bloat Agreed, AQM is like an emergency brake. Go ahead and keep it but hope to never need to use it. Bob > Hi Bob, > > I like your design sketch and the ideas behind it. > > >> On Mar 15, 2023, at 18:32, rjmcmahon via Bloat >> <bloat@lists.bufferbloat.net> 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 > > Maybe design this to be dual band from the start to avoid the up/down > "tdm" approach we currently use? Better yet go full duplex, which > might be an option if we get enough radios that not much > beamforming/MIMO is necessary? I obviously lack deep enough > understanf=dingwhether this makes any sense or is just buzzword bingo > from my side :) > > >> >> 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) > > I am weary of this kind of trust in continuous exponential growth... > at one point we reach a limit and will need to figure out how to deal > with congestion again, so why drop this capability on the way? The > nice thing about AQMs is if there is no queue build up these basically > do nothing... (might need some design changes to optimize an AQM to be > as cheap as possible for the uncontended case)... > >> 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 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 0 siblings, 2 replies; 9+ messages in thread From: Dave Taht @ 2023-03-15 17:53 UTC (permalink / raw) To: rjmcmahon Cc: Sebastian Moeller, Rpm, dan, Bruce Perens, libreqos, Dave Taht via Starlink, bloat On Wed, Mar 15, 2023 at 10:49 AM rjmcmahon via Rpm <rpm@lists.bufferbloat.net> wrote: > > Agreed, AQM is like an emergency brake. Go ahead and keep it but hope to > never need to use it. Tee-hee, flow queuing is like having a 1024 lanes that can be used for everything from pedestrians, to bicycles, to trucks and trains. I would settle for FQ everywhere over AQM. This has been a very fun conversation and I am struggling to keep up. I have sometimes thought that LiFi (https://lifi.co/) would suddenly come out of the woodwork, and we would be networking over that through the household. > > Bob > > Hi Bob, > > > > I like your design sketch and the ideas behind it. > > > > > >> On Mar 15, 2023, at 18:32, rjmcmahon via Bloat > >> <bloat@lists.bufferbloat.net> 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 > > > > Maybe design this to be dual band from the start to avoid the up/down > > "tdm" approach we currently use? Better yet go full duplex, which > > might be an option if we get enough radios that not much > > beamforming/MIMO is necessary? I obviously lack deep enough > > understanf=dingwhether this makes any sense or is just buzzword bingo > > from my side :) > > > > > >> > >> 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) > > > > I am weary of this kind of trust in continuous exponential growth... > > at one point we reach a limit and will need to figure out how to deal > > with congestion again, so why drop this capability on the way? The > > nice thing about AQMs is if there is no queue build up these basically > > do nothing... (might need some design changes to optimize an AQM to be > > as cheap as possible for the uncontended case)... > > > >> 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 17:53 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht @ 2023-03-15 17:59 ` dan 2023-03-15 19:39 ` rjmcmahon 1 sibling, 0 replies; 9+ messages in thread From: dan @ 2023-03-15 17:59 UTC (permalink / raw) To: Dave Taht Cc: rjmcmahon, Sebastian Moeller, Rpm, Bruce Perens, libreqos, Dave Taht via Starlink, bloat [-- Attachment #1: Type: text/plain, Size: 1596 bytes --] On Wed, Mar 15, 2023 at 11:53 AM Dave Taht <dave.taht@gmail.com> wrote: > On Wed, Mar 15, 2023 at 10:49 AM rjmcmahon via Rpm > <rpm@lists.bufferbloat.net> wrote: > > > > Agreed, AQM is like an emergency brake. Go ahead and keep it but hope to > > never need to use it. > > Tee-hee, flow queuing is like having a 1024 lanes that can be used for > everything from pedestrians, to bicycles, to trucks and trains. I > would settle for FQ everywhere over AQM. > > This has been a very fun conversation and I am struggling to keep up. > > I have sometimes thought that LiFi (https://lifi.co/) would suddenly > come out of the woodwork, > and we would be networking over that through the household. > > I'd rather say it's a traffic cop and has value in essentially any network. Keeping the costs down on end user hardware is fundamental, and those devices will behave however they want (ie badly). AQM is the 'roundabout' that keeps things flowing but each thing at an appropriate rate so it works well. There will *never be infinite bandwidth or even enough that no services saturate it. Even a very small town with everyone on a 1G turns into 20Tb of necessary capacity to avoid the usefulness of AQM. When likely 20Gb is sufficient. There has to be something that addresses the car going 180MPH on the freeway. That car requires everyone else to pull off the road to avoid disaster in the same way that data chews up a fifo buffer and wrecks the rest. AQM is the solution now, and more evolved AQM is most likely the answer for many many years to come. [-- Attachment #2: Type: text/html, Size: 2104 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi 2023-03-15 17:53 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht 2023-03-15 17:59 ` dan @ 2023-03-15 19:39 ` rjmcmahon 1 sibling, 0 replies; 9+ messages in thread From: rjmcmahon @ 2023-03-15 19:39 UTC (permalink / raw) To: Dave Taht Cc: Sebastian Moeller, Rpm, dan, Bruce Perens, libreqos, Dave Taht via Starlink, bloat > I have sometimes thought that LiFi (https://lifi.co/) would suddenly > come out of the woodwork, > and we would be networking over that through the household. I think the wishful thinking is "coming from woodwork" vs coming from the current and near future state of engineering. Engineering comes from humans solving problems who typically get paid to do so. FiWi would leverage SFP tech. The Fi side of FiWi comes from mass NRE investments into the data center networks. The Wi side from mass investment into billions of mobile phones. Leveraging WiFi & SFP parts is critical to success as semiconductors are a by-the-pound business. I think a 1X25G VCSEL SFP, which is tolerant to dust over MMF, has a retail price of $40 today. The sweet spot for DC SFP today is driven by 1x100Gb/s serdes and I suspect angel investors are trying to improve the power significantly of the attached lasers. It's been said that one order of improvement in lowering laser power gives multiple orders of laser MTBF improvements. So lasers, SERDES & CMOS radios are not static and will constantly improve year to year per thousands of engineers working on them today, tomorrow & on. The important parts of FiWi have to be pluggable - just like a light bulb is. The socket and wiring last (a la the fiber and antennas) - we just swap a bulb if it burns out, if we want a different color, if we want a higher foot candle rating, etc. This allows engineering cadences to match market cadences and pays staffs. Most engineers don't like to wait decades between releases so-to-speak and don't like feast & famine lifestyles. Moore's law was and is about human cadences too. I don't see any engineering NRE that LiFi could leverage. Sounds cool though. Bob ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-09-05 16:15 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-03-16 7:46 [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi David Fernández 2023-09-05 16:15 ` Dave Taht [not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net> 2023-03-13 18:14 ` [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA 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 ` [Starlink] On FiWi rjmcmahon 2023-03-14 11:10 ` Mike Puchol 2023-03-14 16:54 ` [Starlink] [Rpm] " Robert McMahon 2023-03-14 17:06 ` Robert McMahon 2023-03-14 17:11 ` [Starlink] [Bloat] " Sebastian Moeller 2023-03-14 17:35 ` Robert McMahon 2023-03-14 17:54 ` [Starlink] [LibreQoS] " dan 2023-03-14 18:14 ` Robert McMahon 2023-03-14 19:18 ` dan 2023-03-14 19:30 ` rjmcmahon 2023-03-14 23:30 ` Bruce Perens 2023-03-15 0:11 ` Robert McMahon 2023-03-15 5:20 ` Bruce Perens 2023-03-15 17:32 ` rjmcmahon 2023-03-15 17:42 ` dan 2023-03-15 19:33 ` [Starlink] [Bloat] [LibreQoS] " David Lang 2023-03-15 19:39 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht 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 ` [Starlink] [Bloat] [LibreQoS] [Rpm] " Sebastian Moeller 2023-03-15 17:49 ` rjmcmahon 2023-03-15 17:53 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Dave Taht 2023-03-15 17:59 ` dan 2023-03-15 19:39 ` rjmcmahon
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox