Something like that. The guesswork may be automated for the initial install, but that's not the real problem. Ongoing operation is the problem. Keeping it running after adding new hardware or additional computers or devices or installing software or junior tinkering with settings and not telling anyone or whatever else. I don't think it's likely that ongoing operational troubleshooting of network problems can be automated via software very well. Too many permutations. It's also a moving target so it would be perpetually upgraded.
I know of 3 people that over the past year have installed wireless networks in their homes. 2 are engineers, but not network engineers. All raved how easy it was to install. Within 3-6 months, all 3 had ripped it out and called it a piece of $#!+. What happened? No idea. Could have been any of a zillion combinations of little things that caused some flakeyness that led to attempts to adjust or change things, which only ended up making it totally inoperable. It probably was not related at all to the wireless net hardware, which was only doing what the software told it, but that is what will get the blame.
3 isn't a huge sample by any means, but I think it will be representative. Seeing how trained professionals have trouble keeping networks running smoothly for long periods of time, I think we could guess this will be the outcome of home networks, even without these 3 data points.
I still say this ubiquitous home networking concept may get a little early traction with consunmers, because it *seems* attractive, but will fall on its face. Some sort of outsourced IT function is needed because the average joe won't have any idea where to start, or any desire to learn. Even the outsourced IT service won't get much traction unless you agree to use their standardized recommended hardware and software in your network, in order to at least make the number of troubleshooting possibilities a smaller set.
MSO's want to own your home network (though they don't necessarily want to pay for it for you<gg>), and want administrative rights to all machines on the network. Some people will accept this. Not me. They are mostly inept at remote troubleshooting of their own network, and TOTALLY inconsistent in their methods; no possible way I'd let some random hack have administrative rights to my machines. Wonder if they have thought of the liability ramifications of taking this IT-like function on? Probably you waive all your rights when you sign them on.
As for firewalls, same types of issues. No set of firewall rules is right for everybody; they may even need to be different for different users of the home network. They also evolve with time. A generic rule set will prevent you from accessing certain sites that you want access to; you have to have some understanding of the rules and risks to do site-specific relaxed rules.
This all seems to point to AOL-like walled gardens ruling the world, as far as mainstream users that want no involvement in the underlying technologies (which is about 95% of the users). Such a shame. |
