Just out of curiosity was there any change to the (level of) service being provided by TWC/RR? I have actually SEEN a tech sent out to just replace a faulty router (cable modem) call in and by mistake have the service changed/re-provisioned. This is of course is not supposed to happen but mistakes often happen when they have to "call in & close out" the order. <div>
<br></div><div><br><div><br></div><div><br></div><div><br><div class="gmail_quote">On Mon, Jun 18, 2012 at 9:43 PM, Rick Troth <span dir="ltr"><<a href="mailto:rmt@casita.net" target="_blank">rmt@casita.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can someone lend me a clue stick? (Or perhaps just slap me with it.)<br>
<br>
I got a new cable modem. Since that time, I've had degrading internet access.<br>
To be specific, service went from intermittent extremes (all there, or<br>
nothing there) to slower and slower.<br>
IMPORTANT COINCIDENCE: The new hardware was installed (by a TWC tech)<br>
on June 7, one day after "World IPv6 Launch". So I cannot tell for<br>
sure if the problem is with the new hardware or is because of a change<br>
in the network.<br>
<br>
The most obvious symptom is slow loading web pages. Most other<br>
services (XMPP, IMAP, SSH, PING, so on) seem to be working fine.<br>
Google has it worst, but other sites too. Direct 'wget' of some files<br>
has been immediate, once the hostname resolved.<br>
<br>
Two experiments suggest that it is #1 related to IPv6 and #2 related<br>
to DNS. Of note, I disabled the IPv6 address on my daughter's machine<br>
and it immediately got better. (No details, just her report.) Since<br>
Google was/is a big hurt, I collected the IPv4 addresses for a number<br>
of its hosts and hard-coded them in /etc/hosts and here too got<br>
immediate relief.<br>
<br>
I cannot find news or articles or reports of similar experience.<br>
(Certainly possible that it's just me.) My home network has an IPv6<br>
/48 routed over a SixXS tunnel which has worked well for more than a<br>
year.<br>
<br>
I run my own 'named', forwarding to the servers provided by the ISP<br>
(TWC/RR). I don't see delays with 'nslookup'. But when a given web<br>
page is "slow", the behavior is as if it were resolving fetchable<br>
objects in the page.<br>
<br>
-- R; <><<br>
'::1, not-so-sweet ::1'<br>
<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div><br></div></div>