Info on Google’s proposal to the City of Mountain View to put in a WiFi network is publically available (490K PDF).
There are some interesting things:
- It will be using mesh technology. There will be about 400 mesh nodes, and 3 uplinks to the Internet (which Google says will use fiber, as though the media really matters).
- The system will use a captive portal, requiring you to log in. The username and password will be a Google account (i.e. the same one as Gtalk, Gmail, customized homepage, etc.) The tinfoil-hat crowd will point out that this will allow Google to snoop all your packets and associate them will all of your e-mail and your chat logs.
- The installs will be on city-owned light poles. Parts of Mountain View will not get service immediately because their light poles are owned by PGE and Google and the city have to negotiate with PGE more. Don’t hold your breath on this, folks. PGE’s probably got some powerline Internet thing it wants to do instead.
- The equipment taps power to the light poles, and as such is unmetered. Google will pay $36 per pole per year for power. That’s $0.0041 per hour. If electricity costs the city 4 cents per kilowatt hour, that means the devices use 100 watts of power. Seems like a fair price.
- There is no mention of solar power or battery backup, which means that this system will be useless for disaster response. Also, because the equipment taps the utility power for the lights, it will not be possible to use generator power to fix some portion of the mesh. Finally, if street light circuits were de-prioritized for repair by the power company during an emergency (as seems likely), the Google wifi mesh would come back slower than other networking technologies.
- There is talk of running a VLAN over the network in the future for city services use. It is not going to be in 1.0. The security aspects of having city services data running over a wireless mesh would need to be thought about. I’m not saying it’s a bad idea, but it’s a sizable liability for Google to take on.
- There are grainy, useless pictures of the proposed hardware. No surprise, it looks like commodity stuff. Google’s value-add will be in software.
- There is no discussion of how the boxes will get installed. I suspect Google will contract that job out to someone with a fleet of boom trucks. Perhaps they will have Peek do it, who you see around town fixing traffic lights.
This project is significant for more than the normal “Telcos Battle Municipal Wifi” reason. This is going to be a real mesh network. Mesh networking is one of those urban legends among networking people. Everyone says that they are nifty, but no one has ever seen one work. Perhaps Google will nail this like they have so many other things.
On a related note, there’s a site called wifi.google.com. It redirects you to the Google personalized homepage. But by searching for all the links Google knows about to wifi.google.com I found more info. In particular, I found this FAQ about something called Google Secure Access (BETA). When you try to download it, you get a page saying they have turned off downloads. But you can still download it via one of the links the web search above turned up. After I installed it, I took a look at the about box. It says, “Tunc tua res agitur, Paries cum proximus ardet.” Which is Greek (well, ok, Latin) to me. (Someone on the net translated: “It is your problem when your neighbor’s wall is burning.”)
Now, Google says clearly that this won’t work for me on my home Internet connection. I need to go to one of their hotspots to see it working. But that doesn’t stop me from playing, does it?
When you tell it to connect, it tries to open a PPTP connection to 220.127.116.11. But who owns that IP address? The reverse DNS says “plsf2internet.putnamlovellnbf.com”. Is that a mistake? What the heck is Putnam Lovell NBF, an investment bank, doing running a PPTP server for Google to connect to?
Update: As of Jan 2007, vpn.google.com points at addresses in the NET-64-9-224-0-1 block, which is named GOOGLE-WIFI-MV. Hmm, no more Putnam Lovell NBF.
Later, after timing out or something, it popped up a normal Windows VPN signin box. I typed my Google username and password, and it started to try to connect to vpn.google.com. I did a name lookup, and got these back: 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52. Those are from the same IP address range, so they are also owned by Putnam Lovell NBF. Why is a Google DNS name pointing at addresses owned by someone else? (And why did no one else notice this but me? This story broke back in September, and 1000 people posted ways to make Mac and Linux PPTP implementations work with the same servers.)
My guess is this is Google’s answer to the criticism that them hosting a VPN server makes it possible for them to snoop all your data. They set up some kind of escrow agreement with Putnam Lovell so that they can provide this service, but have a trusted intermediary in the loop. But the interesting thing is that it cuts Google off from doing anything clever in their network to implement PPTP.