For all those interested, Kansas State's wireless network was highlighted in the latest Syllabus e-newsletter.
http://www.kstatecollegian.com/article.php?a=2395
Frank
**
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http:/
On Wed, 1 Sep 2004, Frank Bulk - iNAME.com wrote:
: For all those interested, Kansas State's wireless network was
: highlighted in the latest Syllabus e-newsletter.
: http://www.kstatecollegian.com/article.php?a=2395
The article says:
Because WEP keys do not guarantee an entirely secure a
Haven't talked to Harv since Anaheim to know what specifically he's up to
(Harv -- you on the list?)
I do know that we are being sloppy in our terminology and interchanging
session authentication (and authorization) with session encryption.
Most schools really just want to AuthN/AuthZ their wirel
Since the issue of authentication has come up, I'm wondering how other
organizations are dealing with the guest access issue. Here at Syracuse,
we have an authentication system in place for wireless, web-based for
people who aren't concerned about session encryption and don't want to
deal with clie
> security system. Is anyone doing this? The exposure is that anyone in
That's what we are designing and testing today at UT
5 SSID each mapping to a specific VLAN:
-802.1x VLAN (no gateway, rules are on the VLAN)
-non-802.1x VLAN (with a Gateway liek BlueSocket)
-Quarantine VLAN (with access to d
On Wed, 1 Sep 2004, Dave Molta wrote:
> Most infrastructure vendors allow you to define multiple SSID's and map
> them to different VLANs or provide other capabilities for guest access.
> This allows you to have a secure wireless network that terminates inside
> the network and an open network tha
Notre Dame is about a week away from installing the Roving Planet solution
at our WLAN core and we're targeting Fall Break for complete cut over.
I won't go into great detail here as to why we selected Roving Planet, but
it did the best job of meeting our requirements -- some of which were 802.1x