We have two across campus:
eduroam
General use, access by group:
Some temporary ITS exceptions to special VLANs
Current faculty/staff/students to general access VLANs
Other local (alumni, applicants) and roaming users to guest network VLAN
Bethel-Guest
Open, Captive portal or MAC registration
Portal offers self-service guest or login
Self-service guest option asks for legal-requested info and drops to
guest network VLAN
Login pushes eduroam setup or registration, but then drops to guest
network VLAN (logout in a day)
Registration allows anyone with an account to set up devices to
automatically go to guest network VLAN
The guest network has similar access to campus resources as one would have
coming from the general Internet (no access to things that assume a trusted
network), and also has speed caps. Those are enough for a HD video call or
FHD video streaming. We did not want to pretend a widely shared PSK
reasonably protected data, and just encourage non-802.1x-capable devices to
use the open network.
We also have another PSK AV SSID in few locations which drops to the local
closet's L2 AV network for those staff to manage their equipment (not
known/used by presenters/general public).
On Tue, Feb 21, 2017 at 2:36 PM, Jim Stasik <jsta...@mc3.edu> 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 <(215)%20641-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.
>
>
--
Jeremy Mooney
ITS - Bethel University
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/discuss.
