We are also looking at our next-gen wireless solution (we're currently running no-WEP/broadcast SSID, but VPN to leave the wireless cloud). At the same time, we're looking at installing wireless in the campus airport (which also serves the community and has commercial flights).
We can install campus style wireless and limit access to UIUC folks or take an ISP approach, and sell a pipe that we tunnel to beyond our campus firewall (so it looks like any other outside ISP) and let the airport decide who gets to use it. If we did the latter we'd probably block traffic other than the secure and basic ports (ssh, secure pop & imap, and ports 80, 443, 25) to campus unless the traffic is on an ipsec tunnel for consistency with the current campus wireless security model.
If we do that at the airport, we'll then expect the cry of "why can't we do that?" from the rest of campus, especially for our student union (which has guest rooms), and coffee shops that have locations in campus owned buildings.
So we thought it would be useful to hear how other campuses (that aren't running anyone-can-use-it models) have dealt with this issue. If you've done something interesting for these kinds of spaces, or decided to keep them the same as the rest of your campus, I'd be interested in hearing what you're doing, or why you decided not to do any thing different.
thanks!
--
-debbie Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il email: [EMAIL PROTECTED] <http://www.uiuc.edu/ph/www/fligor> "Every keystroke can be monitored. And the computers never forget."
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/cg/.
