For the past few days I've been seeing various network connectivity
issues.

First I was getting lots of name resolution failures, but that finally
cleared up (which usually means my ISP reset the DNS servers I'm using).

Since then there have been ongoing performance problems - most notably
with stream buffering.

Having now looked into it, my TRACERTs all show a timeout on the second
hop - like this:

> tracert www.microsoft.com
>
> Tracing route to lb1.www.ms.akadns.net [207.46.19.254]
> over a maximum of 30 hops:
>
> 1 3 ms <1 ms <1 ms 192.168.1.1
> 2 * * * Request timed out.
> 3 9 ms 9 ms 10 ms ge-2-25-ur02.greenspoint.tx.houston.comcast.net [68.85.251.213]
> 4 10 ms 9 ms 13 ms po-11-ur01.greenspoint.tx.houston.comcast.net [68.85.244.145]
> 5 9 ms 11 ms 12 ms po-13-ar02.greenspoint.tx.houston.comcast.net [68.85.244.149]
> ...etc...


192.168.1.1 is my Linksys WRT54GS router which has worked fine for
several years.

If, however, I issue a TRACERT directly from the router itself I get the
timeout on the first hop - like this:

> traceroute to lb1.www.ms.akadns.net (207.46.192.254), 30 hops max, 40 byte packets
>
> 1 * * * Request timed out.
> 2 ge-2-25-ur02.greenspoint.tx.houston.comcast.net (68.85.251.213) 10.490 ms 10.281 ms 9.380 ms
> 3 po-11-ur01.greenspoint.tx.houston.comcast.net (68.85.244.145) 11.094 ms 9.810 ms 10.428 ms
> 4 po-13-ar02.greenspoint.tx.houston.comcast.net (68.85.244.149) 10.446 ms 9.430 ms 10.684 ms
> ...etc...


And I see the same result (first hop timeout) if I bypass the router and
connect a system directly to my cable modem:

> Tracing route to lb1.www.ms.akadns.net [207.46.193.254]
> over a maximum of 30 hops:
>
> 1 * * * Request timed out.
> 2 7 ms 7 ms 7 ms ge-2-25-ur02.greenspoint.tx.houston.comcast.net [68.85.251.213]
> 3 10 ms 9 ms 10 ms po-11-ur01.greenspoint.tx.houston.comcast.net [68.85.244.145]
> 4 10 ms 9 ms 10 ms po-13-ar02.greenspoint.tx.houston.comcast.net [68.85.244.149]
> ...etc...


This all implies it is not a local router issue - but when I connect to
another (separate) wireless network on the same ISP (Comcast) I see
this:

> Tracing route to lb1.www.ms.akadns.net [207.46.19.190]
> over a maximum of 30 hops:
>
> 1 2 ms 2 ms 1 ms 192.168.1.1
> 2 10 ms 10 ms 14 ms 192.168.1.1
> 3 11 ms 11 ms 12 ms ge-2-25-ur02.greenspoint.tx.houston.comcast.net [68.85.251.213]
> 4 14 ms 12 ms 11 ms po-11-ur01.greenspoint.tx.houston.comcast.net [68.85.244.145]
> 5 10 ms 11 ms 11 ms po-13-ar02.greenspoint.tx.houston.comcast.net [68.85.244.149]
> ...etc...


Since the second hop there was also to the local 192.168.1.1 router, and
the remaining hops all referenced the same external servers, and that
network is using the same gateway server, that would imply my issue is
local - right?

But rebooting and fully resetting / power cycling the router and modem
doesn't help, so that again implies something external - right?

Also, a TRACERT to my private (router assigned) IP address
(192.168.1.100), the router itself (192.168.1.1), and the external
dynamic IP address assigned by my ISP to the router (98.something),
always returns the expected successful (<1 ms) single hop. A TRACERT to
my (ISP assigned) external gateway server (on 98.x) completes in 2
successful hops (one to the local router plus one to the remote 98.x
server). But anything to my DNSs (on 68.x) or anything else external
all get that one timeout. And of course this never happened in the
past.

So what's the deal here? Anyone know what's really going on from these
details?