Massassi Forums Logo

This is the static archive of the Massassi Forums. The forums are closed indefinitely. Thanks for all the memories!

You can also download Super Old Archived Message Boards from when Massassi first started.

"View" counts are as of the day the forums were archived, and will no longer increase.

ForumsDiscussion Forum → O, Comcast, Let Me Count the H8
O, Comcast, Let Me Count the H8
2008-07-06, 2:17 AM #1
So the other day, I was working on trying to forward some ports on my gateway to set up a Vent server.

I come to the screens on my modem/gateway, and lo, the options and screens to do so do not actually exist. This is on a Linksys WCG200-CC, which is the cable modem/wifi router dumbed down by Comcast.

I have seen and read documentation on precisely how to do what I need to, but my interface lacks these parts somehow. I think, perhaps, that my firmware is out of date and must be updated. The Linksys site says there are no releases of firmware for the WCG200, but other sources suggest that there may be revisions for the CC rebrand. I pop into Linksys's live chat support and the girl says they don't manage firmware for it.

So I do a few hours of Googling and everything I find says that there is no way to update the firmware myself, and that Comcast has to push the upgrade from their end, which frankly creeps me right out.

So I pop onto Comcast's live support chat, and the girl says, oh, you'll need to call our support center as I don't have that information. I call Comcast, first guy I talk to says as far as he knows, the firmware is just updated automatically and there's no way to do it manually, but he'll double-check. Not three seconds of hold time later he comes back telling me he's checked with his team-mates, his lead, and several techs and that is indeed the case.

I ask to be transferred to home networking support, and after talking for a few minutes with the guy there he says I completely get what you're wanting to do, but we don't support that model, and transfers me to.. Netgear support.. yes, that's right. Netgear. Netgear support of course tells me, dude, why did you call us, you have a Linksys device. I hang up and call Linksys support, and explain my situation, and they kindly tell me that I'll have to contact Comcast, as it is a Comcast-supported model, not a Linksys-supported model.

Having a slightly clearer idea of the slippery slope that I'm treading here, I call Comcast back and ask to be transferred to home networking again. I get a different guy who coughs continuously and deafeningly into his headset while he looks up my model-- and drops the call while he's typing.

I concede defeat and go to sleep.

In the morning, hoping I'll have an entirely fresh batch of employees to talk at, I call back.

This time I get a different guy, thank god and my ears, and we go through the whole spiele, he looks up my model and tells me that he'll have to register this device with my account. Okay, fine. I read off the MAC and SN blah blah, then he tells me how to log in to it. I humor him, as I have it open already and have been poking at it for days, on the off chance that he'll reveal something new.


"Okay, open up Internet Explorer."
"Ok"
"Click on the address bar."
"uhuh."
"Delete everything in it."
"done.."
"Now type.. 1.. 9.. 2.. dot.. 1.. 6.. 8.. dot.. 0.. dot.. 1, exactly like that."
"yeah..."
"now hit enter"
"done."


Prompts for username and password. I already know that it is the Linksys default of <blank>:admin despite him saying comcast:1234 which does not work

Once in, he tells me ok now click on such-and-such link.

"There is no such link."
"Are you sure?"
"Absolutely. Trust me, I've--"
"It should be there. Just click it."
"No, it seriously isn't."
"It should be."
"Maybe you need the Linksys login"
"I have it, I've talked with them and they--"
"You need to talk to Linksys."
"I was just on the phone with--"
"Call Linksys and ask them for the login."
"I already have it--."
"You need to do that, I can't help you more."
"Linksys said they didn't support it and I'd have to call you."
"Contact Linksys, I can't help."
"But.."
"Well at least we got your modem registered, which we needed to do. Thank you for calling Comcast. I'm glad we could help. *click*."



So today after realizing there was probably no way I was going to get the Linksys, or wait is it Comcast, gateway working how I needed it, I reinstalled the old Motorola wired modem and jacked a wireless router into it for great signal.


I power everything back on, and lo and behold every website I visit gets walledgardened into their Welcome to Comcast captive portal saying I need to set up my account. There was a procedure I worked out to bypass this by forcing different DNS addresses a while back at a previous installation but I couldn't convince it to work this time around, so finally I threw my hands up and called Comcast again.

The lady informs me that it's perfectly expected that I'd be getting those screens, as my old modem had been revoked from my account. So we add it back in. Power cycle everything, reboot my computers. Same message. Half an hour of unplugging and replugging and checking lights continues on the phone until something inexplicable happens and lo and behold I can resolve Gmail. Good enough, I thank the lady and hang up so as not to waste more minutes.


But that's when the real madness ensues. Not /everything/ resolves. About 75% of the websites I try still resolve to the Welcome to Comcast internal page, while about 20% resolve and about 5% don't resolve at all. I reboot everything, clear all my local caches, reset all of my adapters and interfaces. Same result. It's now four in the afternoon and I need to leave for work at eight in the evening, so I crash for a few hours and come in, where I am now typing this.


Half rant, half plea for wtfhelpplox. So maddening.



Also I ran into a completely bizarre thing that nobody I've talked to [net gurus among them] has ever seen or knows why I find this, nor any results on the internets that I can find. On the WGC200-CC, any time I netcat requested any filename including '.conf' in it, I would get this, even or obviously bogus requests. Any other bogus requests not including '.conf' would return the expected 404 or forbiddens.

Code:
$  nc 192.168.0.1 80
GET /home/fnord/bar.conf 80

HTTP/1.0 200 Ok
Server: micro_httpd
Date: TUE, 01 JUL 2008 23:44:04 GMT
Content-Type: zip/application
Connection: close
Cache-Control: no-cache

#<<Begin of Configuration File>>
#
#RIP
#
RIP Support(Enable or Disable)=Disable;
RIP Authentication (Enable or Disable)=Enable;
RIP Authentication Key=;
RIP Authentication Key ID=0;
RIP Reporting Interval=30;
RIP Reporting Unicast IP Address=0.0.0.0;
#
#Routed Subnet
#
RIP Routed Subnet Support (Enable or Disable)=Disable;
DHCP Provisioned Routed Subnet (Enable or Disable)=Disable;
NAT Routed Subnet Support(Enable or Disable)=Disable;
NAT Routed Subnet Gateway IP=0.0.0.0;
NAT Routed Subnet DNS(1)=0.0.0.0;
NAT Routed Subnet DNS(2)=0.0.0.0;
NAT Routed Subnet DNS(3)=0.0.0.0;
Routed Subnet Network IP(1)=0.0.0.0;
Routed Subnet Mask(1)=255.255.255.0;
Routed Subnet Gateway(1)=0.0.0.0;
Routed Subnet Network IP(2)=0.0.0.0;
Routed Subnet Mask(2)=255.255.255.0;
Routed Subnet Gateway(2)=0.0.0.0;
Routed Subnet Network IP(3)=0.0.0.0;
Routed Subnet Mask(3)=255.255.255.0;
Routed Subnet Gateway(3)=0.0.0.0;
#<<End of Configuration File>>
HMAC-MD5 checksum=3912E637608E FFF8538A5F93E CB740;



Any ideas? I can't find but a hair of documentation online about micro_httpd.
Also, I can kill you with my brain.
2008-07-06, 3:26 AM #2
wow..

well I would just buy a modem and my own router/switch.. those combos are peices of ****
"Nulla tenaci invia est via"
2008-07-06, 6:22 AM #3
I /am/ using now a modem and router/switch.
Also, I can kill you with my brain.
2008-07-06, 7:07 AM #4
Well, setting my router to use external DNS addresses instead of whatever the modem fed it and it works again. Le closed.
Also, I can kill you with my brain.
2008-07-06, 11:02 AM #5
This is micro_httpd.
I've seen more than a few embedded devices use that server. Sounds like the clueless developers at Linksys used it for your device and butchered it to respond to requests for /*\.conf/ with a copy of its config file. With the hilariously invalid mimetype of 'zip/application', no less.


Laugh, its funny.
And when the moment is right, I'm gonna fly a kite.
2008-07-06, 11:18 AM #6
Oh, BTW, Comcast is not alone.
And when the moment is right, I'm gonna fly a kite.
2008-07-07, 12:19 AM #7
I'm coming from only the experience of setting up my own home network, so ignore this if it's a stupid idea.

Couldn't you take another router and have it between your Comcast gateway and the rest of your network, then forward the ports on that one? So it would go Vent server -> New router that forwards ports -> Comcast BS. Just a thought. Also keep in mind that it very well may be against your service's terms of use to run a server.
2008-07-07, 12:38 AM #8
comcast, the 8th layer of hell
Holy soap opera Batman. - FGR
DARWIN WILL PREVENT THE DOWNFALL OF OUR RACE. - Rob
Free Jin!
2008-07-07, 2:07 AM #9
Originally posted by gbk:
This is micro_httpd.
I've seen more than a few embedded devices use that server. Sounds like the clueless developers at Linksys used it for your device and butchered it to respond to requests for /*\.conf/ with a copy of its config file. With the hilariously invalid mimetype of 'zip/application', no less.


Laugh, its funny.


Yep! That's honestly as much documentation as I could find as well, and it's sparse to the point of balding.
Also, I can kill you with my brain.
2008-07-07, 2:37 AM #10
Originally posted by RingMaster481:
I'm coming from only the experience of setting up my own home network, so ignore this if it's a stupid idea.

Couldn't you take another router and have it between your Comcast gateway and the rest of your network, then forward the ports on that one? So it would go Vent server -> New router that forwards ports -> Comcast BS. Just a thought. Also keep in mind that it very well may be against your service's terms of use to run a server.



This is my current working setup, which is basically that :)
Attachment: 19677/topology_vent.jpg (33,185 bytes)
Also, I can kill you with my brain.
2008-07-07, 9:21 AM #11
If you need a good external DNS, try 4.2.2.1

It seems to be always up :D
gbk is 50 probably

MB IS FAT
2008-07-07, 4:41 PM #12
Originally posted by Dormouse:
Yep! That's honestly as much documentation as I could find as well, and it's sparse to the point of balding.

He posted the source. All 286 lines of it. Kinda documents itself.
And when the moment is right, I'm gonna fly a kite.
2008-07-07, 5:03 PM #13
thats the best diagram ever
[01:52] <~Nikumubeki> Because it's MBEGGAR BEGS LIKE A BEGONI.
2008-07-07, 9:15 PM #14
Originally posted by NoESC:
If you need a good external DNS, try 4.2.2.1

It seems to be always up :D


You can use any DNS you want? I thought you had to use your ISPs.
2008-07-07, 9:29 PM #15
Originally posted by Obi_Kwiet:
You can use any DNS you want? I thought you had to use your ISPs.

You can use any you want, in theory. In practice some DNS servers are configured to only respond to requests from specific IP ranges.
And, in practice, you really want a DNS server that is relatively close (fewer number of hops away) so that domain lookups are faster.
And when the moment is right, I'm gonna fly a kite.

↑ Up to the top!