[MUD_Wizard]

Originally Posted by Sephiroth

Your downstream is VM's upstream. It seems to me that any bufferbloat they claim to detect when testing downstream speed (how do they detect it?) is in VM's transmission path.

Yes, the upstream service flows corresponds to queues in the cable modem for out-going traffic and the downstream service flows corresponds to queues at the CMTS for sending traffic to the cable modem(s).

The bufferbloat test is measuring these queues.

Though I notice that DSLReports test on the CM upstream does not match my increase in latency to google, so is not an accurate representation of the bloat. The downstream bloat test seems to work fine though.


---------- Post added at 18:00 ---------- Previous post was at 17:51 ----------

Originally Posted by SnoopZ

It would be nice to know why some people see bufferbloat on VM and others don't though. I was originally Cambridge Cable before NTL/VM took it over if that makes any difference.

For downstream bloat it depends on the situation and configuration at the CMTS, so it would be area specific and possibly CMTS type specific (because different CMTS's are configured differently and have different options).