4 ms·

I have quite a bit of networking knowledge and also used to work at an ISP for several years. Back then I wouldn't have used any router that didn't run my custo

by gst 11y ago

I have quite a bit of networking knowledge and also used to work at an ISP for several years. Back then I wouldn't have used any router that didn't run my custom OpenWRT built with QoS settings, etc. But times have changed: On my old ADSL line QoS made a huge difference due to congestion (and the large buffer sizes). SSH was nearly unusable while uploading a file. My current Comcast line is so fast that I don't experience any issues due to congestion - so how would I benefit from QoS? Another difference is that in the past consumer-level hardware was just unreliable: I remember an old Netgear router that just crashed if there were too many concurrent TCP connections, as its NAT table would overflow. I haven't seen those issues in a long time now.

wtallis 11y ago
> "My current Comcast line is so fast that I don't experience any issues due to congestion - so how would I benefit from QoS?" Are you sure you don't have a few hundred milliseconds of bufferbloat in your cable modem, as is the case for almost all modems out there?
- gst 11y ago
  No - I'm not. But my connection works well enough and I don't notice any delays on either SSH or VoIP connections. So why should I invest time/energy into changing something that doesn't affect me?
  - deleted 11y ago
    [deleted]
  - indlebe 11y ago
    > So why should I invest time/energy into changing something that doesn't affect me? This argument has a place here, but it has a cringe effect each time I see it. I find it a dangerous one if applied to other circumstances.