turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Hi 
, CCC works even without an internet connection. If you will log on to the router without internet access, it will not ask your for your CCC account login, instead it would ask you for the router password and if you type the password correctly it enables you to do changes on the router settings offline.
Ok, I downloaded the cloud firmware for E4200 v2 and this was my experience:
1. I doubt if the cloud firmware really needs to be zipped to add an extra step but maybe it does....no big deal.
2. The firmware upgraded manually without a hitch from a wired connection.
3. I gave it my dsl username and password (my modem/router is in bridge mode) and then did the rest from a wireless connection. No problems.
4. I set it up (registered) and explored where all of the settings were at. There's a couple intuitive things that I would have done differently, but they are so minor, it's not even worth mentioning.
5. I noticed that the cloud software automatically detected that I have a wrt54g2 connected to the e4200 and it identified it as such when clicking on "connected devices".
6. I then realized that I hadn't done factory reset to defaults after the upgrade and decided to do so. I used the GUI method to reset. I reconfigured and noticed that the wrt54g2 was now seen as a "network device" when clicking on "connected devices". So I did hard reset with button. Same thing. Finally, I did another button reset and then proceded to disable the UPnP on E4200. I disabled upnp exception in windows firewall and rebooted computer. I enabled upnp on e4200 and the enabled exception on windows firewall and it's back to detecting the wrt54g2 just fine. A minor bug? Possibly. User error? I can never rule that out
6. I actually like the cloud setiup thing and didn't think I would. I don't really follow the "can't configure it with no Internet" logic. I was without power for 12 days from an ice storm a couple years ago, and I had a lot more to worry about than whether or not I could configure or change a setting on my non Internet wireless network. It seems like bathing and hot water, food spoilage were more of a concern. Even if I had a generator, I doubt if I would have had time to monkey around with the home grade router. If I needed a file, I've got everything on seagate USB drive and a laptop and car charger/inverter....and smart phone. The verizon cell towers were back on line in less than 72 hours with emergency generators.
1. I doubt if the cloud firmware really needs to be zipped to add an extra step but maybe it does....no big deal.
2. The firmware upgraded manually without a hitch from a wired connection.
3. I gave it my dsl username and password (my modem/router is in bridge mode) and then did the rest from a wireless connection. No problems.
4. I set it up (registered) and explored where all of the settings were at. There's a couple intuitive things that I would have done differently, but they are so minor, it's not even worth mentioning.
5. I noticed that the cloud software automatically detected that I have a wrt54g2 connected to the e4200 and it identified it as such when clicking on "connected devices".
6. I then realized that I hadn't done factory reset to defaults after the upgrade and decided to do so. I used the GUI method to reset. I reconfigured and noticed that the wrt54g2 was now seen as a "network device" when clicking on "connected devices". So I did hard reset with button. Same thing. Finally, I did another button reset and then proceded to disable the UPnP on E4200. I disabled upnp exception in windows firewall and rebooted computer. I enabled upnp on e4200 and the enabled exception on windows firewall and it's back to detecting the wrt54g2 just fine. A minor bug? Possibly. User error? I can never rule that out
6. I actually like the cloud setiup thing and didn't think I would. I don't really follow the "can't configure it with no Internet" logic. I was without power for 12 days from an ice storm a couple years ago, and I had a lot more to worry about than whether or not I could configure or change a setting on my non Internet wireless network. It seems like bathing and hot water, food spoilage were more of a concern. Even if I had a generator, I doubt if I would have had time to monkey around with the home grade router. If I needed a file, I've got everything on seagate USB drive and a laptop and car charger/inverter....and smart phone. The verizon cell towers were back on line in less than 72 hours with emergency generators.
I wouldn't have downloaded the firmware had they not modified the terms and made public statements about it. I hate that you ea users had to be the guinea pigs, but I'm satisfied with what I've read. Cisco has too much to lose financially to do something "evil".
I think the bean counters were calling the shots and trying to do some ladder climbing. It back fired on them. Instead of increasing corporate profits and putting that on their resume, they did some PR damage to Cisco. I doubt if they'll put that on their resume though.
Greed is amazing thing. But that's how the bean counters got hired in the first place. They're always thinking about how they can make the company more money. They just are clueless about sensitive issues like privacy. The folks making those decisions are out of touch at Cisco, and probably don't use home grade routers. They have Cisco employees come to their house and fix them up with top notch business/corporate grade Cisco VPN stuff. They wouldn't have a clue on how to adjust a setting on a router.
I think the bean counters were calling the shots and trying to do some ladder climbing. It back fired on them. Instead of increasing corporate profits and putting that on their resume, they did some PR damage to Cisco. I doubt if they'll put that on their resume though.
Greed is amazing thing. But that's how the bean counters got hired in the first place. They're always thinking about how they can make the company more money. They just are clueless about sensitive issues like privacy. The folks making those decisions are out of touch at Cisco, and probably don't use home grade routers. They have Cisco employees come to their house and fix them up with top notch business/corporate grade Cisco VPN stuff. They wouldn't have a clue on how to adjust a setting on a router.
