We offer two SSIDs for our Faculty. One is for non-academic, BYOD
devices and is the standard for use by Faculty families, and IoT devices
like Xbox's and the like. This network is unsecured and open to guests.
There are three methods of authenticating to the network, all are MAC
The first is by logging in and registering the MAC address using
University credentials. This will permanently register the device to
the user, until the user account is deleted, or the device isn't seen
for 7 months.
The second is by registering the device MAC address in a self-service
portal. This is for devices that don't have a web browser to register.
The MAC address is again tied to the user account and will have the same
expiration policy as the first.
The last method is a guest 2 week registration. After the two weeks is
up, the user is forced to register again. This is the only method that
isn't tied to a user account. This type of registration is also not
supported at the same level as the first two.
The second SSID (eduroam) is for academic use and is 802.1x
authenticated (much like AUB). It has access to our library electronic
resources and printers, but is otherwise treated as non-trusted, BYOD space.
We supply wireless access points for our on campus apartments and
townhouses and take responsibility for ample coverage. For off campus
housing, the Faculty is responsible for their own network setup
(however, we make ourselves available to help them out).
On 07/26/2017 04:01 AM, Walid El Khazen wrote:
> Hello Everyone
> We are currently checking our options to improving the internet services
> and coverage to our Faculty Residences. To be specific this includes
> providing internet services to those staff/faculty who are living in
> Housing apartments inside our Campus and this excludes the Student
> dorms. Currently the internet provided to the faculty residences
> includes wired and wireless coverage as part of the overall University
> network and we use dot1x authentication. The current setup brings with
> it some challenges like securing the network while keeping the
> flexibility of residents connecting to their applications and another
> big one is allowing them to connect their peripherals such as TV’s and
> PlayStation knowing that these do not support dot1x authentication. Some
> of the options that we discussed is to completely outsource this and
> remove it from our network and another is to provide them with network
> to the socket in the wall and have each resident get his own router for
> It would be great if you can share what strategies you use for internet
> connection at the faculty residences and some of the pros and cons you see.
> *Walid El-Khazen*
> * *
> *Assistant CIO*
> Description: Description: Description: Description: aub-logo
> *American University of Beirut*
> P.O.Box 11-0236
> Riad El-Solh, Beirut 1107 2020, Lebanon
> *T*: +961 (1) 350000 *x *2254 *|* *M*: +961 (3) 963111
> *E*: [log in to unmask] <mailto:[log in to unmask]>
> ********** Participation and subscription information for this EDUCAUSE
> Constituent Group discussion list can be found at
Brian Epstein <[log in to unmask]> +1 609-734-8179
Manager, Network and Security Institute for Advanced Study
Key fingerprint = A6F3 9F5A 26C5 5847 79ED C34C C0E5 244A 55CA 2B78
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.