2 ms·
I haven't walked anything back, thank you. There's more than one bad thing Comcast does to their customers, we haven't got close to enumerating the full list.
by tristor 3y ago
I haven't walked anything back, thank you. There's more than one bad thing Comcast does to their customers, we haven't got close to enumerating the full list. The two issues with the CPE are orthogonal to one another. Whether or not they lift the cap, they still perform traffic shaping when using their CPE (they also perform shaping /without/ their CPE, but it's much cruder).
- mindslight 3y agoSorry, I missed that you addressed the request for details in another branch. I was hoping to see a description of what their CPE was actually doing - metadata-based traffic shaping, throttling after a certain amount of usage, too small NAT table like ATT routers were famous for, just underpowered performance, or what. But now I understand you just investigated enough for your own purposes. FWIW I think the DiffServ RFC explicitly acknowledges that the QoS marks are generally ignored across administrative boundaries. It was an extension of the earlier 4-level QoS priority, so by that time it was clear that transit networks weren't paying them much attention. What would be surprising is finding a consumer ISP that actually did something different when a customer set them.