On 28 November 2013 16:03, C. Falconer <[email protected]> wrote: > > Honestly? TCL cable is pretty good. When they have an outage, its a > decent one but only once a year at worst. > A/VDSL can be solid or flakey, depending on the age of your wire pair. > And it can change at any time. > Shame cable isn't better-priced.
When we were on cable, the cable stability was the best internet I have ever seen. 6 months of solid uptime was not unusual, and most our internet outages were in fact us overloading the fuses in our house and having the router ( a full linux box ) powered off as a result. Though something I never got my head around was the fact the link-level speed to TCL was amazing fast 100Mb/s, the international speed was abysmal. Literally never saw even 1/4 of our medium speed to anywhere other than TCL's test box. We did a lot of digging, and we eventually concluded the TCP delay-product induced limitation bandwidth-delay-product was the cause ( didn't help that TCL had no idea what this was at the time , and TCL help staff saw the exact same speeds we did and considered it normal and impossible to beat ). For those who don't know what I'm talking about, there's a limit on throughput that is regulated by the ping time multiplied by the buffer size, and TCP Window scaling has something to do with it. Though I don't fully understand what regulates "buffer" size, whether every node in the route needs larger buffers to get better throughput, or if its just end-point controlled. However, now on Snap VDSL, with a lower medium cap ( 55M ), we see better international traffic than we ever saw on Cable!. Though, it comes with a price, notably, the connection is for some reason incredibly flakey, and we've been on snap's support line practically constantly for the last few weeks with a problem nobody can understand: Our router keeps rebooting. When we take the router to their office, it ceases to exhibit the problem. When they give us one of theirs, we still see the problem. But diagnostics don't show there's anything wrong with the signal at all, and the router itself is *NOT* expected to reboot simply on signal noise. However, it does reboot quite regularly, and some of the time it gets the DSL connection lost with a message "No response from DSL, retrying", sort of suggesting the medium itself had been entirely breached temporarily making it get a periodic 100% signal loss. Nobody has any clue what is going wrong. -- Kent perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" http://kent-fredric.fox.geek.nz _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
