I plead guilty. When I was at University of Tennessee, we turned eduroam on (back in 2005-06) and did very little to inform the community. Classic Technologists believing that the service was so awesome that users would look into this formidable extra SSID with this beautiful self explanatory name. Yeah right! Many years later we informed the community (news, email etc,,,), and very few people joined it anyway. Most of them were confused between UT-WPA2 and eduroam.
This summer UTK reduced their SSIDs to just two (big Bravo to the IT group): UT-Open (MAC address Auth and Guests) and eduroam. There is little need to advertise eduroam or explain why there are two secure SSIDs. It just works, users are enabled for millions of Access-Points in one setup. Most of the filtering for local users VS visitors is done via domains and VLANs. As Jonathan pointed out: ask you users. Philippe Philippe Hanset, CEO www.anyroam.net www.eduroam.us +1 (865) 236-0770 GPG key id: 0xF2636F9C > On Feb 21, 2017, at 5:23 PM, Jonathan Waldrep <wald...@vt.edu> wrote: > > 1. eduroam: primary wireless network > 2. VirginiaTech: captive portal / mac auth for everything else: > - Guest (sponsored and self sponsored) > - web auth for affiliates > - registered devices that don't do .1x > - onboarding to eduroam > > We decided that a 2 SSIDs setup was the clearest approach. You can > communicate far more in a web page (captive portal) than in an SSID. Also, if > all choices are a correct one, then users are more likely to choose a correct > choice. > > Because of the many roles of the secondary network, it was better to > communicate who was providing the network rather than the role of the network. > > Regardless of what you or your governance bodies think is a good SSID, ask > your users. Send out a survey with a list of possible networks and ask them > which one they would be most likely to choose, which one they most easily > associate with the institution, and which one they trust the most. We did > this, and the answer was clear. > > -- > Jonathan Waldrep > Network Engineer > Network Infrastructure and Services > Virginia Tech > > On Tue, Feb 21, 2017 at 4:06 PM, Adam T Ferrero <a...@temple.edu > <mailto: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 > <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 > <mailto: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 <tel:413-545-9639> > michael.dick...@umass.edu <mailto: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 <mailto:jsta...@mc3.edu> > > > > 215.641.6678 <tel: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 <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 > <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 > <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 <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.
