Up until this past summer, we had three SSIDs: a guest SSID, an open SSID for college users and a 1x protected SSID for college users. There was considerable overlap between the open and guest SSIDs, so we collapsed them into one. We now have: eduroam and 'St. Olaf Guest'. We decided we were OK with 1x-incapable devices using the guest network and removed the captive portal we had on the old guest SSID.
On Tue, Feb 21, 2017 at 3:06 PM, Adam T Ferrero <a...@temple.edu> wrote: > > These have served us pretty well. We only have a mac auth SSID in our > residence halls. Occasionally it would be useful to have it everywhere but > we don't currently. > > TUsecurewireless WPA2 enterprise which gives different access > levels (staff, student, guest) > TUguestwireless Open for onboarding (SMS text credentials) > eduroam Guest like access for anyone > > Adam > > -----Original Message----- > From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto: > WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Michael Dickson > Sent: Tuesday, February 21, 2017 4:02 PM > To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > Subject: Re: [WIRELESS-LAN] SSID names > > eduroam (our only 802.1x offering) > UMASS (open, CP, primarily for guests) > UMASS-DEVICES (MAC auth'd device support for non-802.1x capable devices, > as allowed by policy) > > Mike > > Michael Dickson > Network Analyst > Information Technology > University of Massachusetts Amherst > 413-545-9639 > michael.dick...@umass.edu > PGP: 0x16777D39 > > > On 2017-02-21 15:36, Jim Stasik wrote: > > Hello, I have been encouraged by one of our governance bodies to > > consider renaming our wireless SSIDs to better match the network names > > to the function of the networks behind them. I don’t get it, but > > maybe I am a little too close to it. We don’t have any residential on > > our campuses so have just two primary SSIDs in use on our campus (as > > well as eduRoam). One is named Public and is our onboarding/guest > > network. The other is our authenticated/secure network which we call > > MC3Waves and is for all students, staff, faculty and administrators, > > with 802.1x on the back end to steer the end user to the appropriate > > role. We have had these network around for as long as I can remember > > (15 years maybe). I am curious how others are naming and separating > > the SSIDs in their environment? > > > > Thanks in advance, > > > > Jim Stasik > > > > Director of Enterprise Infrastructure Services > > > > Montgomery County Community College > > > > jsta...@mc3.edu > > > > 215.641.6678 > > > > ------------------------- > > > > Montgomery County Community College is proud to be designated as an > > Achieving the Dream Leader College for its commitment to student > > access and success. > > ********** Participation and subscription information for this > > EDUCAUSE Constituent Group discussion list can be found at > > http://www.educause.edu/discuss. > > ********** > Participation and subscription information for this EDUCAUSE Constituent > Group discussion list can be found at http://www.educause.edu/discuss. > > ********** > Participation and subscription information for this EDUCAUSE Constituent > Group discussion list can be found at http://www.educause.edu/discuss. > > -- Tony Skalski Systems Administrator a...@stolaf.edu 507-786-3227 St. Olaf College Information Technology 1510 St. Olaf Avenue Northfield, MN 55057-1097 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.
