How to Go Insane Using Comcast
It's simple to go insane when using Comcast as your cable modem provider.
Apparently when my new cable modem is put on the network, it was given 68.87.96.204 (CPSDNS.selfprov.pa.comcast.net) as its DNS server. This is a really amazing system. Check it out.
The first 1.1.1.1 IP address is reserved. The second 68.87.96.200 belongs to act02.selfprov.pa.comcast.net, which goes to a www.comcast.net Web server. Apparently I was supposed to not use a site like Google as my home page, but something else that would bring me to the Comcast site so I could "self-provision" my new cable modem.
So why could I update time with NTP? Check out the wonders of 68.87.96.204:
That's not correct.
But guess what -- 68.87.96.200 is running a time server.
Hence, my insanity. Some applications worked (NTP), others (TCP to certain Web sites) did not. Good grief. By the way, my equipment came with zero setup instructions. I should have just called tech support earlier and said "the Internet is broken," rather than network troubleshoot!
- Watch as Comcast-provided cable modem goes dead. (Not insane yet).
- Swap out cable modem at store. (Not insane yet).
- Plug in cable modem and watch router receive IP address. (Not insane yet. Happy, actually.)
- Notice machines begin trying to reach 1.1.1.1 when using TCP. (Slight insanity.)
- Observe that UDP traffic like NTP updates work properly. (Higher insanity level.)
- Notice that your cannot ping your default gateway. (Insane. Period.)
Apparently when my new cable modem is put on the network, it was given 68.87.96.204 (CPSDNS.selfprov.pa.comcast.net) as its DNS server. This is a really amazing system. Check it out.
orr:/home/richard$ nslookup www.google.com 68.87.96.204
Server: 68.87.96.204
Address: 68.87.96.204#53
Name: www.google.com
Address: 1.1.1.1
orr:/home/richard$ nslookup www.taosecurity.com 68.87.96.204
Server: 68.87.96.204
Address: 68.87.96.204#53
Name: www.taosecurity.com
Address: 68.87.96.200
The first 1.1.1.1 IP address is reserved. The second 68.87.96.200 belongs to act02.selfprov.pa.comcast.net, which goes to a www.comcast.net Web server. Apparently I was supposed to not use a site like Google as my home page, but something else that would bring me to the Comcast site so I could "self-provision" my new cable modem.
So why could I update time with NTP? Check out the wonders of 68.87.96.204:
orr:/home/richard$ nslookup clock.isc.org 68.87.96.204
Server: 68.87.96.204
Address: 68.87.96.204#53
Name: clock.isc.org
Address: 68.87.96.200
That's not correct.
orr:/home/richard$ nslookup clock.isc.org 209.98.98.98
Server: 209.98.98.98
Address: 209.98.98.98#53
Non-authoritative answer:
Name: clock.isc.org
Address: 204.152.184.72
But guess what -- 68.87.96.200 is running a time server.
orr:/home/richard$ sudo ntpdate 68.87.96.200
Looking for host 68.87.96.200 and service ntp
host found : act02.selfprov.pa.comcast.net
5 May 20:56:17 ntpdate[874]: adjust time server 68.87.96.200 offset 0.016223 sec
Hence, my insanity. Some applications worked (NTP), others (TCP to certain Web sites) did not. Good grief. By the way, my equipment came with zero setup instructions. I should have just called tech support earlier and said "the Internet is broken," rather than network troubleshoot!
Comments
Gotta love Comcast - NOT! I'm connected to the Dale City 02 node, but in 1 week only 3 folks connected to my OpenBSD firewall running spamd.
I actually went out and bought a cable modem - I picked up the cheapest (biggest rebate) at BestBuy. I don't remember what the ROI was, but I think it paid for itself if it lasted a couple of months longer than the warranty period.
I see Comcast the way I saw Deutsche Telekom while in Germany, anything I can do to avoid paying them money, I'll do. Feel the same way about Verizon!
Anyways, long story short, the tech could not provision the linksys cable modem I bought, (being lazy, who knows), he said we need to call their support line. 8 calls later, and Sunday evening (all I could do is hit comcast sites during that period), 7 different answers why they could not provision the modem, 5 of those excuses stated that 1 or another system was hosed and is down, 1 stating that it was maint period (yes, all ISP's do their maint on weekends during peak usage [sarcasm]), and 1 totally clueless tech who I think I made cry. Eventually, I got a hold of someone who stated there is nothing wrong with the system, except a tie in, he would have to do the provisioning manually, and run up two floors, puts me on hold, comes back 5 min later, its working... Only reason I use them, I am too far out for DSL.