<div dir="ltr">I wonder what oleg thinks the starlink repairability index is?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 16, 2023 at 12:46 AM David Fernández via Starlink <<a href="mailto:starlink@lists.bufferbloat.net">starlink@lists.bufferbloat.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">ISPs like Orange are into extending the life of the routers they give<br>
for Internet access, which are built for that:<br>
<a href="https://www.orange.com/en/commitments/oranges-commitment/to-the-environment" rel="noreferrer" target="_blank">https://www.orange.com/en/commitments/oranges-commitment/to-the-environment</a><br>
<br>
France has introduced a repairability index for products, so you know<br>
better what are you buying:<br>
<a href="https://www.ecologie.gouv.fr/indice-reparabilite" rel="noreferrer" target="_blank">https://www.ecologie.gouv.fr/indice-reparabilite</a><br>
<br>
Then, there is the one from iFixit:<br>
<a href="https://www.ifixit.com/News/49319/why-ifixits-repair-scores-are-different-than-the-french-repair-index" rel="noreferrer" target="_blank">https://www.ifixit.com/News/49319/why-ifixits-repair-scores-are-different-than-the-french-repair-index</a><br>
<br>
Wondering what repairability index would have the Starlink terminals<br>
all around the world.<br>
<br>
Regards,<br>
<br>
David<br>
<br>
> Date: Wed, 15 Mar 2023 18:08:41 -0400<br>
> From: dan <<a href="mailto:dandenson@gmail.com" target="_blank">dandenson@gmail.com</a>><br>
> To: Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>><br>
> Cc: Rpm <<a href="mailto:rpm@lists.bufferbloat.net" target="_blank">rpm@lists.bufferbloat.net</a>>, libreqos<br>
> <<a href="mailto:libreqos@lists.bufferbloat.net" target="_blank">libreqos@lists.bufferbloat.net</a>>, Bruce Perens <<a href="mailto:bruce@perens.com" target="_blank">bruce@perens.com</a>>,<br>
> Dave Taht via Starlink <<a href="mailto:starlink@lists.bufferbloat.net" target="_blank">starlink@lists.bufferbloat.net</a>>, bloat<br>
> <<a href="mailto:bloat@lists.bufferbloat.net" target="_blank">bloat@lists.bufferbloat.net</a>>, David Lang <<a href="mailto:david@lang.hm" target="_blank">david@lang.hm</a>><br>
> Subject: Re: [Starlink] [Rpm] [Bloat] [LibreQoS] On FiWi<br>
> Message-ID:<br>
> <<a href="mailto:CAA_JP8W4B6ixcYjijJ8FyA%2BPAXpLTLjvvKH5-dGjB-UaanC3dQ@mail.gmail.com" target="_blank">CAA_JP8W4B6ixcYjijJ8FyA+PAXpLTLjvvKH5-dGjB-UaanC3dQ@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> On Mar 15, 2023 at 4:04:27 PM, Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>> wrote:<br>
><br>
>> On Wed, Mar 15, 2023 at 2:52 PM David Lang <<a href="mailto:david@lang.hm" target="_blank">david@lang.hm</a>> wrote:<br>
>><br>
>><br>
>> On Wed, 15 Mar 2023, Dave Taht wrote:<br>
>><br>
>><br>
>> > On Wed, Mar 15, 2023 at 12:33 PM David Lang via Rpm<br>
>><br>
>> > <<a href="mailto:rpm@lists.bufferbloat.net" target="_blank">rpm@lists.bufferbloat.net</a>> wrote:<br>
>><br>
>> >><br>
>><br>
>> >> if you want another example of the failure, look at any conference<br>
>> center, they<br>
>><br>
>> >> have a small number of APs with wide coverage. It works well when the<br>
>> place is<br>
>><br>
>> >> empty and they walk around and test it, but when it fills up with<br>
>> users, the<br>
>><br>
>> >> entire network collapses.<br>
>><br>
>> >><br>
>><br>
>> >> Part of this is that wifi was really designed for sparse environments,<br>
>> so it's<br>
>><br>
>> >> solution to "I didn't get my message through" is to talk slower (and<br>
>> louder if<br>
>><br>
>> >> possible), which just creates more interference for other users and<br>
>> reduces the<br>
>><br>
>> >> available airtime.<br>
>><br>
>> >><br>
>><br>
>> >> I just finished the Scale conference in Pasadena, CA. We deployed over<br>
>> 100 APs<br>
>><br>
>> >> for the conference, up to 7 in a room, on the floor (so that the<br>
>> attendees<br>
>><br>
>> >> bodies attenuate the signal) at low power so that the channels could be<br>
>> re-used<br>
>><br>
>> >> more readily.<br>
>><br>
>> ><br>
>><br>
>> > How did it go? You were deploying fq_codel on the wndr3800s there as<br>
>><br>
>> > of a few years ago, and I remember you got rave reviews... (can you<br>
>><br>
>> > repost the link to that old data/blog/podcast?)<br>
>><br>
>><br>
>> no good stats this year. still using the wndr3800s. Lots of people<br>
>> commenting on<br>
>><br>
>> how well the network did, but we were a bit behind this year and didn't<br>
>> get good<br>
>><br>
>> monitoring in place. No cake yet.<br>
>><br>
>><br>
>> I think this is what you mean<br>
>><br>
>> <a href="https://www.youtube.com/watch?v=UXvGbEYeWp0" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=UXvGbEYeWp0</a><br>
>><br>
>><br>
>><br>
>> A point I would like to make for the africa contingent here is that<br>
>> you do not need the latest<br>
>> technology for africa. We get 300Mbit out of hardware built in the<br>
>> late 00s, like the wndr3800. The ath9k chipset is STILL manufactured,<br>
>> the software mature, and for all I know millions of routers<br>
>> like these are lying in junk bins worldwide, ready to be recycled and<br>
>> reflashed.<br>
>><br>
>> One libreqos customer deployed libreqos, and took a look at the 600+<br>
>> ubnt AGWs (ath9k based), on the shelf that could be fq_codeled,<br>
>> especially on the wifi... built a custom openwrt imagebuilder image<br>
>> for em, reflashed and redistributed them.<br>
>><br>
>> The wndr3800s were especially well built. I would expect them to last<br>
>> decades. I had one failure of one that had been in the field for over<br>
>> 10 years... I thought it was the flash chip... no, it was the power<br>
>> supply!<br>
>><br>
>><br>
>> > Did you get any good stats?<br>
>><br>
>> ><br>
>><br>
>> > Run cake anywhere?<br>
>><br>
>> >><br>
>><br>
>> >> in the cell phone world they discovered 'microcells' years ago, but<br>
>> with wifi<br>
>><br>
>> >> too many people are still trying to cover the max area with the fewest<br>
>> possible<br>
>><br>
>> >> number of radios. As Dan says, it just doesn't work.<br>
>><br>
>> >><br>
>><br>
>> >> and on mesh radios, you need to not just use a different channel for<br>
>> your<br>
>><br>
>> >> uplink, you need a different band to avoid desense on the connection to<br>
>> your<br>
>><br>
>> >> users. And that uplink is going to have the same hidden transmitter and<br>
>> airtime<br>
>><br>
>> >> problems competing with the other nodes also doing the uplink that it's<br>
>><br>
>> >> scalability is very limited (even with directional antennas).<br>
>> Wire/fiber for the<br>
>><br>
>> >> uplink is much better.<br>
>><br>
>> >><br>
>><br>
>> >> David Lang<br>
>><br>
>> >><br>
>><br>
>> >><br>
>><br>
>> >><br>
>><br>
>> >> On Wed, 15 Mar<br>
>><br>
>> >> 2023, dan via Bloat wrote:<br>
>><br>
>> >><br>
>><br>
>> >>> Trying to do all of what is currently wanted with 1 AP in a house is a<br>
>> huge<br>
>><br>
>> >>> part of the current problems with WiFi networks. MOAR power to try to<br>
>><br>
>> >>> overcome attenuation and reflections from walls so more power bleeds<br>
>> into<br>
>><br>
>> >>> the next home/suite/apartment etc.<br>
>><br>
>> >>><br>
>><br>
>> >>> In the MSP space it's been rapidly moving to an AP per room with<br>
>> >>> output<br>
>><br>
>> >>> turned down to minimum. Doing this we can reused 5Ghz channels 50ft<br>
>> away<br>
>><br>
>> >>> (through 2 walls etc...) without interference.<br>
>><br>
>> >>><br>
>><br>
>> >>> One issue with the RRH model is that to accomplish this 'light bulb'<br>
>> model,<br>
>><br>
>> >>> ie you put a light bulb in the room you want light, is that it<br>
>> >>> requires<br>
>><br>
>> >>> infrastructure cabling. 1 RRH AP in a house is already a failure<br>
>> today and<br>
>><br>
>> >>> accounts for most access complaints.<br>
>><br>
>> >>><br>
>><br>
>> >>> Mesh radios have provided a bit of a gap fill, getting the access SSID<br>
>><br>
>> >>> closer to the device and backhauling on a separate channel with better<br>
>> (and<br>
>><br>
>> >>> likely fixed position ) antennas.<br>
>><br>
>> >>><br>
>><br>
>> >>> regardless of my opinion on the full on failure of moving firewall off<br>
>> prem<br>
>><br>
>> >>> and the associated security risks and liabilities, single AP in a home<br>
>> is<br>
>><br>
>> >>> already a proven failure that has given rise to the mesh systems that<br>
>> are<br>
>><br>
>> >>> top sellers and top performers today.<br>
>><br>
>> >>><br>
>><br>
>> >>> IMO, there was a scheme that gained a moment of fame and then died out<br>
>> of<br>
>><br>
>> >>> powerline networking and an AP per room off that powerline network. I<br>
>> have<br>
>><br>
>> >>> some of these deployed with mikrotik PLA adapters and the model works<br>
>><br>
>> >>> fantastically, but the powerline networking has evolved slowly so I'm<br>
>><br>
>> >>> seeing ~200Mbps practical speeds, and the mikrotik units have 802.11n<br>
>><br>
>> >>> radios in them so also a bit of a struggle for modern speeds. This<br>
>> model,<br>
>><br>
>> >>> with some development to get ~2.5Gbps practical speeds, and WiFi6 or<br>
>> WiFi7<br>
>><br>
>> >>> per room at very low output power, is a very practical and deployable<br>
>> by<br>
>><br>
>> >>> consumers setup.<br>
>><br>
>> >>><br>
>><br>
>> >>> WiFi7 also solves some pieces of this with AP coordination and<br>
>><br>
>> >>> co-transmission, sort of like a MUMIMO with multiple APs, and that's<br>
>> >>> in<br>
>><br>
>> >>> early devices already (TPLINK just launched an AP).<br>
>><br>
>> >>><br>
>><br>
>> >>> IMO, too many hurdles for RRH models from massive amounts of<br>
>> unfrastructure<br>
>><br>
>> >>> to build, homes and appartment buildings that need re-wired, security<br>
>> and<br>
>><br>
>> >>> liability concerns of homes and business not being firewall isolated<br>
>> >>> by<br>
>><br>
>> >>> stakeholders of those networks.<br>
>><br>
>> >>><br>
>><br>
>> >>> On Wed, Mar 15, 2023 at 11:32 AM rjmcmahon <<a href="mailto:rjmcmahon@rjmcmahon.com" target="_blank">rjmcmahon@rjmcmahon.com</a>><br>
>> wrote:<br>
>><br>
>> >>><br>
>><br>
>> >>>> The 6G is a contiguous 1200MhZ. It has low power indoor (LPI) and<br>
>> >>>> very<br>
>><br>
>> >>>> low power (VLP) modes. The pluggable transceiver could be color coded<br>
>> to<br>
>><br>
>> >>>> a chanspec, then the four color map problem can be used by installers<br>
>><br>
>> >>>> per those chanspecs. <a href="https://en.wikipedia.org/wiki/Four_color_theorem" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Four_color_theorem</a><br>
>><br>
>> >>>><br>
>><br>
>> >>>> There is no CTS with microwave "interference" The high-speed PHY<br>
>> >>>> rates<br>
>><br>
>> >>>> combined with low-density AP/STA ratios, ideally 1/1, decrease the<br>
>><br>
>> >>>> probability of time signal superpositions. The goal with wireless<br>
>> isn't<br>
>><br>
>> >>>> high densities but to unleash humans. A bunch of humans stuck in a<br>
>> >>>> dog<br>
>><br>
>> >>>> park isn't really being unleashed. It's the ability to move from<br>
>> >>>> block<br>
>><br>
>> >>>> to block so-to-speak. FiWi is cheaper than sidewalks, sanitation<br>
>><br>
>> >>>> systems, etc.<br>
>><br>
>> >>>><br>
>><br>
>> >>>> The goal now is very low latency. Higher phy rates can achieve that<br>
>> and<br>
>><br>
>> >>>> leave the medium free the vast most of the time and shut down the RRH<br>
>><br>
>> >>>> too. Engineering extra capacity by orders of magnitude is better than<br>
>><br>
>> >>>> AQM. This has been the case in data centers for decades. Congestion?<br>
>> Add<br>
>><br>
>> >>>> a zero (or multiple by 10)<br>
>><br>
>> >>>><br>
>><br>
>> >>>> Note: None of this is done. This is a 5-10 year project with zero<br>
>><br>
>> >>>> engineering resources assigned.<br>
>><br>
>> >>>><br>
>><br>
>> >>>> Bob<br>
>><br>
>> >>>>> On Tue, Mar 14, 2023 at 5:11 PM Robert McMahon<br>
>><br>
>> >>>>> <<a href="mailto:rjmcmahon@rjmcmahon.com" target="_blank">rjmcmahon@rjmcmahon.com</a>> wrote:<br>
>><br>
>> >>>>><br>
>><br>
>> >>>>>> the AP needs to blast a CTS so every other possible conversation<br>
>> >>>>>> has<br>
>><br>
>> >>>>>> to halt.<br>
>><br>
>> >>>>><br>
>><br>
>> >>>>> The wireless network is not a bus. This still ignores the hidden<br>
>><br>
>> >>>>> transmitter problem because there is a similar network in the next<br>
>><br>
>> >>>>> room.<br>
>><br>
>> >>>><br>
>><br>
>> >>> _______________________________________________<br>
>><br>
>> >> Bloat mailing list<br>
>><br>
>> >> <a href="mailto:Bloat@lists.bufferbloat.net" target="_blank">Bloat@lists.bufferbloat.net</a><br>
>><br>
>> >> <a href="https://lists.bufferbloat.net/listinfo/bloat" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/bloat</a><br>
>><br>
>> >> _______________________________________________<br>
>><br>
>> >> Rpm mailing list<br>
>><br>
>> >> <a href="mailto:Rpm@lists.bufferbloat.net" target="_blank">Rpm@lists.bufferbloat.net</a><br>
>><br>
>> >> <a href="https://lists.bufferbloat.net/listinfo/rpm" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/rpm</a><br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Come Heckle Mar 6-9 at: <a href="https://www.understandinglatency.com/" rel="noreferrer" target="_blank">https://www.understandinglatency.com/</a><br>
>> Dave Täht CEO, TekLibre, LLC<br>
>><br>
><br>
> Much of the hardware dumped on the US market in particular is especially<br>
> poorly made. Ie, engineered for our disposable market. Lots of netgear<br>
> products for example have a typical usable life of just 2-3 years if that,<br>
> and then the caps have busted or some patina on the boards has killed them.<br>
><br>
><br>
> I know Europe has some standards on this as well as South Korea to give<br>
> them longer life. To the point, it’s not realistic to recycle these items<br>
> from the US to other place because they were ‘built to fail’.<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="https://lists.bufferbloat.net/pipermail/starlink/attachments/20230315/5ca4404e/attachment.html" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/pipermail/starlink/attachments/20230315/5ca4404e/attachment.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> Starlink mailing list<br>
> <a href="mailto:Starlink@lists.bufferbloat.net" target="_blank">Starlink@lists.bufferbloat.net</a><br>
> <a href="https://lists.bufferbloat.net/listinfo/starlink" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/starlink</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of Starlink Digest, Vol 24, Issue 37<br>
> ****************************************<br>
><br>
_______________________________________________<br>
Starlink mailing list<br>
<a href="mailto:Starlink@lists.bufferbloat.net" target="_blank">Starlink@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/starlink" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/starlink</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Oct 30: <a href="https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html" target="_blank">https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html</a></div><div>Dave Täht CSO, LibreQos<br></div></div></div>