[Bloat] Best approach for debloating Airbnb host?

I stayed in an Airbnb rental last week. It was nicely appointed with a very gracious host who lived in the other half of the home. They had decent internet from xfinity - I was getting 20mbps/5mpbs. But.. they have bad bufferbloat. I was on a Zoom call and occasionally people would sound like

Re: [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news

Thank you Jonathan for this clear description of the issues and their history. I wonder if there's a fourth one - privacy. Rosenworcel's talk https://docs.fcc.gov/public/attachments/DOC-397257A1.pdf also points out that ISPs might want to monetize our traffic patterns and location data. (This

Re: [Bloat] [Rpm] [Make-wifi-fast] Traffic analogies (was: Wonderful video)

> On Oct 19, 2022, at 7:36 PM, Stephen Hemminger via Rpm > wrote: > > Grocery store analogies also breakdown because packets are not "precious" > it is okay to drop packets. A lot of AQM works by doing "drop early and often" > instead of "drop late and collapse". Another problem is that

Re: [Bloat] [Rpm] [Make-wifi-fast] [Cake] The most wonderful video ever about bufferbloat

> On Oct 10, 2022, at 8:05 PM, Bob McMahon via Rpm > wrote: > > > I think conflating bufferbloat with latency misses the subtle point in that > > bufferbloat is a measurement in memory units more than a measurement in > > time units. Yes, but... I am going to praise this video, even as I

Re: [Bloat] [Rpm] [Make-wifi-fast] [Cake] The most wonderful video ever about bufferbloat

> On Oct 11, 2022, at 1:05 PM, Bob McMahon wrote: > > I agree that bufferbloat awareness is a good thing. The issue I have is the > approach - ask consumers to "detect it" and replace a device with a new one, > that may or may not, meet all the needs of the users. > > Better is that

Re: [Bloat] really lovely live plots of bandwidth, queue depth, marks and drops in libreqos

> On Jan 6, 2023, at 11:14 PM, bloat-requ...@lists.bufferbloat.net wrote: > > Wearing my theorist hat... and looking at all the ISP plans > https://payne.taht.net is now emulating (click > on bandwidth test, > then a plan) This is really cool! I see the

Re: [Bloat] Dave's wonderful rant (was: grinch...)

Thanks Dave for summarizing the current state of speedtests at https://blog.cerowrt.org/post/speedtests/. (Perhaps this post should be linked from the Bufferbloat.net home page?) I really enjoyed Jim Roskind's presentation when I watched it on Youtube: https://youtu.be/_uaaCiyJCFA?t=499 I

[Bloat] FCC requires broadband "Nutritional Label"

Forwarded from NANOG list: > The effective date will be determined later, after publication in the > Federal Register and OMB review under PRA. > > November 17, 2022?The Federal Communications Commission today > unveiled new rules that will for the first time require broadband > providers to

Re: [Bloat] On metrics

> On Mar 19, 2023, at 11:03 PM, bloat-requ...@lists.bufferbloat.net wrote: > >> Consumers really need things like published performance specs so they can >> assemble their needs like an a la carte menu. What do you do, what’s >> important to you, what details support that need, and they need

Re: [Bloat] Annoyed at 5/1 Mbps...

> On Mar 21, 2023, at 1:21 AM, Frantisek Borsik via Rpm > wrote: > > Now, I hope to really piss You off with the following statement :-P but: > > even sub 5/1 Mbps “broadband” in Africa with bufferbloat fixed on as many > hops along the internet journey from a data center to the customers

Re: [Bloat] [Starlink] Annoyed at 5/1 Mbps...

> On Mar 21, 2023, at 8:31 AM, Sebastian Moeller wrote: > > I have to push back gently on this... > ... > So I am not su sure I would prefer the 5/1 (A)DSL over a PON... > > That however is orthogonal to me preferring a competent ISP that takes care > of keeping latency under load at bay.

Re: [Bloat] [Starlink] [LibreQoS] Enabling a production model

> On Mar 29, 2023, at 1:13 PM, David Lang via Starlink > wrote: > > The problem is that laying cable (or provisioning wifi access to cover the > area) is expensive, and if you try to have multiple different companies doing > it, they each need a minimum density of users to make it worth

[Bloat] Review of Delta's in-flight wifi mentions latency!

In this ZDnet article, they showed a screenshot of speedtest.net while using Delta's in-flight wifi. It showed pretty big latency. https://www.zdnet.com/home-and-office/networking/i-tried-deltas-new-free-inflight-wi-fi-heres-how-fast-it-was/ BUT... the good news is that the reviewer commented

Re: [Bloat] Open Source Needs You to Act - Help Fight Proposed Patent Rules

> On May 31, 2023, at 9:08 AM, bloat-requ...@lists.bufferbloat.net wrote: > > just when I thought it was safe to stop worrying about patents Hi Dave, The letter you forwarded has really long URLs that made it hard to see the essentials of the argument. Do you have a link to the heart of the

[Bloat] Disappointment on "Best Newcomer Router" front

For the last several years, I have responded on various boards to complaints about bad latency with a happy-go-lucky "Or just try OpenWrt!". [recent example: https://www.reddit.com/r/HomeNetworking/comments/1ay509v/comment/krx120h/?context=3] I used to mention IQrouter, but that's no longer a

Re: [Bloat] Disappointment on "Best Newcomer Router" front

> On Feb 25, 2024, at 5:28 PM, Sebastian Moeller wrote: > > the coming OpenWrt One, which I am quite excited about, way mote excited that > I should). Me too. > Is that what you asked for, hell no. But it might do as a replacement in a > pinch... I suspect that's what I'll have to wait

Re: [Bloat] Disappointment on "Best Newcomer Router" front

> the problem is the 'easy to install' requirement. Too many vendors (including > ones that used to be easy to install) are adding extra hoops to jump through > on the newer models. Yes. My fantasy (I can still have fantasies, right? :-) is that people buy one of our recommended routers for a

Re: [Bloat] mDNS

> Avoid the WAN port's DHCP assigned subnet (what if the ISP uses > 192.168.1.0/24?) > > ... > > Exactly! There are no rules about what subnet range an ISP's gear will assign > to DHCP devices. @Mark Andrews and @Kenneth Porter... I apologize for any confusion caused by my slightly

Re: [Bloat] mDNS

> On Feb 27, 2024, at 12:00 PM, bloat-requ...@lists.bufferbloat.net wrote: > > On 2/26/2024 6:28 AM, Rich Brown via Bloat wrote: >> - Avoid the WAN port's DHCP assigned subnet (what if the ISP uses >> 192.168.1.0/24?) > > I recently got ATT fiber and its mod

Re: [Bloat] mDNS

I'm not advocating that we change the default OpenWrt address from 192.168.1.1 That's welded too deeply into our synapses (and documentation). But this proposal will benefit newcomers for the reasons described below. > On Feb 28, 2024, at 7:17 AM, David Lang wrote: > > remember, you don't

Re: [Bloat] mDNS (was Disappointment on "Best Newcomer Router" front)

Thanks for the observations re: "zero configuration OpenWrt install" > On Feb 26, 2024, at 4:47 AM, Sebastian Moeller wrote: > >> >> How about "openwrt.local" to conform to mDNS (RFC 6762) and IANA's >> [special-use domain names][1]? Or perhaps "openwrt.internal" in the >> future? > > Or

[Bloat] Need help with netperf.bufferbloat.net server

Hi folks, This note was prompted by a question from the crusader github repo [1] where I wrote the following: >> It seems to me that the server netperf.bufferbloat.net (also called >> netperf-east.bufferbloat.net) has been down for quite a while. > > Yes. I have been stymied by heavy abuse of

Re: [Bloat] [Starlink] The "reasons" that bufferbloat isn't a problem

Thanks! I just posted to: https://randomneuronsfiring.com/all-the-reasons-that-bufferbloat-isnt-a-problem/ It has mild edits from the original to address a broader audience. Also posted to the bloat list. Rich > On May 6, 2024, at 3:05 PM, Frantisek Borsik > wrote: > > Hey Rich, > >

Re: [Bloat] [Starlink] L4S

Let's split this thread and use this message to continue the discussion of L4S. Thanks > On May 8, 2024, at 5:31 AM, David Fernández via Starlink > wrote: > > I see that L4S is not really solving everything (I read about issues with > Wi-Fi), although it seems to be a step in the right

[Bloat] fq_codel Day - it's twelve years old!

My calendar reminds me that fq_codel is TWELVE YEARS OLD today! Dave Täht announced a testable version on the CeroWrt list at: https://lists.bufferbloat.net/pipermail/cerowrt-devel/2012-May/000233.html Since then, fq_codel, CAKE, TX Queues, AQL, ATF, and cake-autorate have all made their way