So, I’ve got 2 hours to wait before my flight leaves for JFK today, so I open up my laptop to change my email to vacation mode and read some news, etc …  Linux connects to the WAP, but fails to get any DNS info from the server, so I reboot into WinXP.  XP detects the WAP with “excellent” connection status, but getting the ‘portal’ server to actually serve any information is almost completely useless.  The server serves up a 30 second commercial before it allows the user to get access to the internet, but I’m guessing from the speed of things (now about 45 minutes since I started trying to get access to the internet, when I decided to whip out my offline BLOG writer application), the server is busy serving up the ad, to so many people that the server is completely unresponsive.  The actual wireless strength of the signal is great, it’s just that whoever they chose as the ISP (http://freefinet.rtr ???) does a completely crappy job at actually doing the connection redirection.  Blech!  Sure, it’s free wireless, that you have to hit “accept” for twice, and watch a 30-second video that never shows up, but come on!!!  Ever heard about caching?  Proxying?  Load-balancing?  Or how about this, if a connection completely fails after about 30 minutes of attempts, how about just lifting the proxying crap and just allowing normal internet in case your stupid server can’t handle the load???  In by book, DIA wireless is completely useless to me.  This is both the fault of the ISP and DIA.  DIA should give the ISP 2 days to fix the problem or drop them like a hot rock.  I'm sure that there are thousands of ISPs in Denver willing to provide the access hardware for one free ad.

Tweet