said by slyphoxj:
I just went to »192.168.100.1 on my tablet and had no problem getting into all the pages of my DPC2100's web interface... maybe it's just you? I am in Brook Park and am served out of the Blaze Pkwy. location also.
That just makes it more blatant. Not that I would put it past Dan Della-Terza or Mike Doty in Corporate Network Engineering, whose LinkedIn is here:
(All the info shows if you search of course.)
Keeps adding more crap but still hasn't learned that it's a DSLAM - Digital Subscriber Line Access Module - not a "D slam." But hey, claiming a WRT54G as "Cisco," obsolete and irrelevant bottom-end gear and lying to customers and management has clearly served him and Dan both well so far.
And it's clearly worked quite well for Mister Kirk Zerkle; he's been promoted to VP and GM of Huntsville and Knoxville territories. How's his work going there after taking over early last year?
»Review of WOW Internet and Cable by cwcjr
- pretty awful, I think the customers would say. Or rather: have been saying. Fixing the infrastructure out there? Yeah.. doesn't take a year. Hell, converting ALL
the LANcity systems to DOCSIS didn't take a year and that involved ripping out both CPE and from the amps back at the head end.
You know, there sure are a lot of people with regulatory oversight who would like to know about the things WOW has done and continues to do wrong. The lax to non-existent security. Yah, I've reported many
times through appropriate channels that WOW hasn't turned off SNMPv2c on critical devices including on routed IPs, the "stealthed" proxies are neither stealthed nor secure, they have multiple DNS servers fail open resolver checks and have no RRL, they filter ICMP traffic but don't filter correctly at CPE, list goes on. This is all stuff anybody with the most basic understanding of security can find out in 5 minutes and fix. Hell, IIRC Arris even put out an advisory regarding recursive open resolvers and CPE configs.
Here. I'll save them time I shouldn't be saving them yet again. I've offered to help multiple times, I've explained and pointed to fixes and advisories multiple times.
And that's just three /24's checked - out of 63 prefixes (no IPv6 still, not smart enough to do that obviously, so block customers by blocking ICMP) with a total of 49,664 IPs originating.
But it's time for today's bump anyway. Hey look. It's even WORSE than yesterday's. Stars at about 17:20 today, with a nice long 5 HOURS of packet loss that suddenly mysteriously clears up when everyone goes to bed.