photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

269
active users

#bufferbloat

0 posts0 participants0 posts today

In a new #podcast episode we talk to team members of @LibreQoS. The software helps ISPs fight #bufferbloat & distribute traffic fairly. In a lively conversation they talk about the vital importance of stable internet connections and their reasons for open sourcing LibreQoS: they hoped it would help a few small ISPs that bring internet access to under-served communities. But to their surprise LibreQoS has become very popular with deployments in 58 countries.
podcast.nlnet.nl/@NGIZero/epis
#FOSS #NGI0

I hadn't heard of #bufferbloat until a few days ago, but we'd been having terrible Internet issues since we dropped my #Netgear CM500 DOCSIS 3.0 cable modem in favor of a newer DOCSIS 3.1 #Spectrum one.

My router didn't have very sophisticated #QOS, so I switched to a #GL.iNet one that has substantially improved traffic shaping.
Initial test look good.

I wonder if there was some kind of QOS at the modem level on the cm500 that's not on the Spectrum one.

I've been using #OPNsense for years (and before that, #pfsense) but its #IPv6 support is so buggy I think I'll have to switch. Suggestions for what to switch to? #OpenWRT is my leading contender due to its #CAKE anti- #bufferbloat support.

#OPNsense bugs: IPv6 NAT uses the wrong IP address after WAN gets a new one github.com/opnsense/core/issue , same with NPTv6 github.com/opnsense/core/issue . Not IPv6, but it uses the wrong MAC sometimes github.com/opnsense/core/issue though I was able to work around that.

GitHubOutgoing IPv6 NAT uses wrong address after WAN gets new address from DHCPv6 · Issue #6530 · opnsense/coreBy jgoerzen
Replied in thread

@timbray #bufferbloat was an issue discovered and documented years ago in consumer routers, but it hasn't gone anywhere. It CAN be mitigated in downstream devices but the real fix is making sure the border router doesn't cause it.