-
Notifications
You must be signed in to change notification settings - Fork 0
WiFi Overview
WiFi is currently available (though, spotty) throughout the Delancey/Middle/Sanctuary buildings. Hopefully, coverage will be improved in these buildings, and will be expanded to the 1710 and Carriage House buildings. Depending on the future uses of 315 or 1716, expansion of WiFi to these buildings should be considered as well.
There are currently three separate WiFi SSIDs: "Tenth", "Tenth Staff", and "Kurtz Tech."
The first WiFi network, named just "Tenth" is intended for members, regular attenders, and conference attendees. Currently, it requires accepting a fairly generic Terms of Use every few hours. This network is completely disabled during school hours, and the early hours of the morning. It is, however, available during most Church events: weekends, and weekday evenings. So far, it has been used by about 600 unique devices.
Soon, this WiFi network will change its authentication method to requiring users to sign in with their ACS credentials, rather than simply accepting terms. Unlike the current method of accepting terms, the new method will, to the user, appear to last much more than a few hours. A handshake will still take place between the user's device and the system every few hours, but the user will not need to log in again. Potentially, the user may not need to log in again ever. When this new login method is implemented, the schedule for this network will expand to include weekdays, and web filtering may be imposed on this network.
This is a secure network intended for Tenth Staff.
Tenth-owned computers connect to this network automatically, and are mapped to the Staff VLAN, affording access to office printers and servers. By using this method, there is no "shared" password. Thus, when a staff member leaves and their account is deactivated, they automatically lose access to the staff network, keeping things appropriately secure.
Most staff members should only connect personal devices to this network if absolutely necessary. That is, if they must connect to the printers, or must access network resources. If staff just wants internet access on a personal device, they should connect to the public network instead.
This SSID should, however, be used by residents for their personal devices. Residents will be authenticated by their user credentials and are mapped to the Resident VLAN, which is separate from the Staff VLAN.