Slashdot Mirror
Google Router Rumors
An anonymous reader writes "There's a new rumor that Google is developing its own router. The company won't comment on the story, but it's been in the hardware business for a while and expanded its presence with Android. If Larry Ellison can go halvsies with HP on a server, then Eric Schmidt should certainly be able to make Cisco nervous."
...to procrastinate on the CCNA test.
THL phish sticks
All I need now is google underwear that twitters for me with real time gps tracking so I know where I've been.
I seem to remember rumors of them building their own insane (10 GbE) hardware switches. And I don't think that's hard to imagine as nothing on the market at the time could possibly meet their needs.
... like many claims they could not be operating on TCP/IP stacks on the inside. Because it's such a resource hog in some respects but that's irrelevant--I'm certain they can apply some of their ideas universally. I would put my money on them being the leader in research on networks and network theory ... probably past Cisco even (although behind the NSA as no one's ever sure about those guys). I feel that networking is so closely tied to their bread and butter search application that they should be dumping huge R&D into that field. I can't offer proof but it certainly makes sense to me.
Of course, there's a lot of questions that remain to be answered
And all I can say is that it's about time someone put pressure on the home & enterprise networking hardware companies. What a stagnant squabbling market that has become.
My work here is dung.
I hope they include sensible and up-to-date standards and protocols. I'm thinking about the possibilities of the interface of the tomato firmware and importantly, inclusion of ipv6 support. If we want this to happen in this generation we need to get software support on at least basic networking devices(thinking of routers and OSes).
Knowledge is power. Knowledge shared is power lost.
It seems likely to me that since Google is full of really smart people who seem to have a touch of the NIH syndrome, it probably isn't surprising that they wanted to develop their own routers from scratch instead of paying through the nose for Cisco or Juniper devices, especially since they needed hundreds or thousands of them and really don't want to have to pay for support contracts. I'd see a Google router announcement as just a productization of something they already use internally, just like Protocol Buffers.
The problem is that Google develops tech internally that is extremely good at solving their problems, but they don't always apply well outside of Google. Protocol Buffers aren't exactly obsoleting XML and from all indications they probably never will. The Google router will probably be super fast and simple, but lack a whole bunch of the more obscure features. The problem is that there's someone out there for each one of those obscure features, and if you don't support it your product won't even make it in the door. This is a problem Juniper runs into a lot, they have good and fast hardware, but the only thing it does is route.
In fact the article points out that Google's router is most likely to compete directly with Juniper instead of Cisco.
I read the internet for the articles.
Forgive my spelling from time to time. I'm often posting during short breaks.
TFA says that Juniper is doomed because Google is getting ready to switch to their own in-house brand of routers. I find this difficult to believe for several reasons. One is that even if Google is Juniper's biggest customer, one customer does not a demise make -- Juniper has many other customers, including the entire UUnet (MCI, WorldCom, Verizon Business, whatever they're calling themselves this year) backbone. But there are far more practical reasons. Routers contain a lot of specialized hardware designed for rapid switching of packets. Google may have a lot of smart people working for them, but they certainly don't have the resources on board to design and build all of those ASIC's and other custom hardware, and it doesn't really make sense for them to get into that business during a recession just for an in-house project. (And no, don't give me that line about how a fast enough server with multiple Ethernet cards can substitute for even a mid-grade Cisco or Juniper. I manage a data center network and know the numbers. It can't even come close, no matter how good the software is, because a general purpose computer has to forward every packet using software, while a real router only makes a routing decision once and then all the rest of the packets for that destination are switched in hardware at wire speed.)
Nothing to see here. Move along.
Tired of FB/Google censorship? Visit UNCENSORED!
My router works fine, and I don't have Google stealing all of my LAN packets and serving me ads.
A fucking grouter had better make me warm delicious waffles if they want me to buy it. Even then, I'd only use it to make waffles.
And now I'm off to amazon to look for a waffle maker.
Of course Google would not waste time developing their own ASICs. Companies like Marvell, Broadcom, and Dune offer plenty to choose from, and companies such as FDRY and JNPR already use these to build their own offerings.
It only makes sense for Google to use the building blocks to make a device that meets their specific needs.
The Apple Airport Express and Airport Extreme routers support IPv6, although there's a bug in the latest firmware for doing configured tunnels.
This
Everybody seems to be assuming that these new routers will be for sale. That's obviously not going to happen — there just isn't room in the marketplace for a new player, even if that player is Google. Breaking into a new hardware marketplace is hard. You have to develop sales channels, create a hardware support organization, set up an operations organization to manage production, etc. etc.
I know about these things because for the last couple of years my job has been to document some of Sun's hardware products. Before that I mostly documented software, and the shear complexity of designing, building, distributing, selling and supporting actual physical products still boggles my mind. At product team meetings I sometimes feel at sea, even though the technical concepts I have to deal with are actually much simpler than those I faced when I was on software product teams. The logistics are just mind boggling.
Google isn't set up to be "in the hardware business". They make their own servers because there are no manufacturers that are able to meet their specialized needs. Now they seem to have decided that their routers also require specialized in-house designs. They haven't tried to sell these servers to other companies, and they won't try to sell their routers. Even if they could hope to compete, it would mean building up the kind of technical bureaucracy that Google's top echelon has no interest in managing.
Hell, they don't really have a proper bureaucracy for the much simpler job of creating and distributing their software products. If they actually charged money for most of them, they'd be trouble.
And Android? How does Android count as being "in the hardware business"? Is Google selling a cell phone I haven't heard about?
Am I the only one who read this and thought, "Hmmm, it must be time for Google to renew their support contracts with Juniper.".
"leak" a rumor about no longer needing Juniper, and watch juniper lower their support rates.
I've often heard this referred to as the Wal-Mart effect. Once Wal-Mart distributes your product nationally, they basically own you. Because once you ramp up production to meet Wal-Mart needs, you can't just scale back down if they drop you... and they can and will drop you if you do not behave.
Check out my lame java blog at www.javachopshop.com