![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
hrafn.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
davis_squareIs anyone else suddenly seeing many periods of zero connectivity from Comcast, starting immediately after the renumbering that took place Thursday the 26th between 0430 and 0600? I'd like to pursue this but need data before contacting them. Technical details below the cut.
Comcast renumbered me from one class-A to another (from net 24 to net 76); this was the fourth unannounced renumbering in less than 9 months, after years of stability. -Immediately- after this latest renumbering, I started experiencing over a dozen instances -a day- in which packets would stop (hung ssh conns, all pings fail, total DNS outage, traceroute fails at the first hop---apparently complete PHY failure), lasting for several minutes. Then, the cable modem (one of the 3Com sharkfins) would do its little bingBINGbingbong song, flash its lights, make little grumbling noises, and eventually bring the connection back up.
Nothing at all has changed in the interior wiring in years. Power-cycling the modem hasn't changed anything (of course, but I had to rule out screwed-up internal state). When I'm not getting zero connectivity, I'm getting excellent connectivity (few or no packet drops on the cablemodem part of the route). I get video from Comcast as well and it is also completely unaffected, making me extremely dubious that this could be any sort of physical cabling issue.
Instead, I think Comcast changed hardware somewhere at their cable headend simultaneously with the renumbering, and the new hardware sucks rocks. But I despair of convincing any of their first- or second-line script-reading drones (who will no doubt -insist- that I reboot my computer before anything else---riiiight), and would like some data before I waste a lot of time trying to escalate this to anyone in their NOC who has the first clue about how a network really works.
Thanks!
Comcast renumbered me from one class-A to another (from net 24 to net 76); this was the fourth unannounced renumbering in less than 9 months, after years of stability. -Immediately- after this latest renumbering, I started experiencing over a dozen instances -a day- in which packets would stop (hung ssh conns, all pings fail, total DNS outage, traceroute fails at the first hop---apparently complete PHY failure), lasting for several minutes. Then, the cable modem (one of the 3Com sharkfins) would do its little bingBINGbingbong song, flash its lights, make little grumbling noises, and eventually bring the connection back up.
Nothing at all has changed in the interior wiring in years. Power-cycling the modem hasn't changed anything (of course, but I had to rule out screwed-up internal state). When I'm not getting zero connectivity, I'm getting excellent connectivity (few or no packet drops on the cablemodem part of the route). I get video from Comcast as well and it is also completely unaffected, making me extremely dubious that this could be any sort of physical cabling issue.
Instead, I think Comcast changed hardware somewhere at their cable headend simultaneously with the renumbering, and the new hardware sucks rocks. But I despair of convincing any of their first- or second-line script-reading drones (who will no doubt -insist- that I reboot my computer before anything else---riiiight), and would like some data before I waste a lot of time trying to escalate this to anyone in their NOC who has the first clue about how a network really works.
Thanks!
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}