Quote:
|
Originally Posted by badnbusy
did Docsdiag never used to work in ex-cwc regions. I know STB's never liked it, but when i first got the Ambit ntl:home 120 modem that didnt work either (tried everything i could at the time). I've just tried it now out of curiosity and low and behold it works!
|
DocsDiag has always worked in principle with stand-alone cable modems, in all areas. There have been two difficulties in practice with the Ambit modems:
1. getting the user's PC to address the CM correctly for traffic to 192.168.1.100: I posted a Windows registry hack for this some time back when the MRTG issue first raised its head;
2. some Ambit firmware versions incorrectly send their responses to the user's PC via their ISP-side port and the CMTS/UBR then back through the CM, rather than directly via their user-side port: the trombone-route traffic is blocked in ex-C&W regions by security filters in the UBR.
It is possible that later versions of Ambit firmware have fixed these problems. Perhaps those who have this working now should compare firmware version numbers with those who still do not have this working.
DocsDiag will not produce correct -traffic reports in ex-C&W regions, because the only CM it can read will be the user's own. So the only traffic reported will be the user's own, not a meaningful assessment of the load on the system as a whole.