The upload thing is not an NTL problem - it's inherent in the design of cable modems. The computer connects to the modem at 10Mbps, so sends data to the modem at that speed. However, this means the modem ends up dropping most packets, and the sending slows down to allow for this. Thus stuff takes quite a while to get through, which is most noticeable for things like SSH, and sometimes TCP ACKs, which means the download rate goes way down. So the solution is to use traffic shaping on your end, so data is sent to the modem at below the rate it can send, so the modem does no queueing.
As for NTL itself... we've had very few problems. Our first modem was broken, would only work via USB. However once we figured this out and told them so, it was replaced reasonably quickly. Connectivity in general is fine, and most of the problems have been me screwing up the router config :)
We're using the NTL DNS servers, with a CUDN one as backup, and haven't found any problems. The NNTP server has worked fine whenever I use it... but I still use the cambridge one so I can get ucam.*. Haven't tried the mail server at all...
Re: NTL Cambridge
Date: 2004-09-25 07:38 am (UTC)As for NTL itself... we've had very few problems. Our first modem was broken, would only work via USB. However once we figured this out and told them so, it was replaced reasonably quickly. Connectivity in general is fine, and most of the problems have been me screwing up the router config :)
We're using the NTL DNS servers, with a CUDN one as backup, and haven't found any problems. The NNTP server has worked fine whenever I use it... but I still use the cambridge one so I can get ucam.*. Haven't tried the mail server at all...