Thanks for screwing me Google

[jhar]

Does not work at SeaTac! I have been trying to connect for an hour
with no success. I fly from SeaTac often and NEVER had a problem
connecting with ATT wifi. So now, I am stuck with a 2 hour delay and
instead of getting work done, I can't access anything because of
Google wifi. Luckily I have my iPhone so I can still post this message.

[Becky]

Your Google WI-fi sucks the worst never works in FT.Laud either the
worst can't wait for them to get read of Google.

[Edward]

In Google's defense, they paid a pre-existing Wi-Fi provider (Boingo,
Wayport, etc) to provide the Wi-Fi service over the holidays. Has
your laptop ever worked in these airports or any other public Wi-Fi
hotspot? It might've also not worked since there were too many people
connecting to the Wi-Fi network. Normally, the $9.95/day charge is
enough of a barrier to entry that only the most serious folks bother
to connect.

[anon]

I was able to get this working at SeaTac by changing the apparently-
incorrect default route handed out.

Was:
# netstat -nr
...
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 198.134.89.88
198.134.91.5 1
...

Works after running this:
route change 0.0.0.0 mask 0.0.0.0 198.134.88.1

...at least, in the subnet I ended up in:
# ipconfig
...
Connection-specific DNS Suffix . : airportwifi.net
IP Address. . . . . . . . . . . . : 198.134.91.51
Subnet Mask . . . . . . . . . . . : 255.255.252.0