Information Systems:Implementing staff and guest WiFi networks - Revision history

Aaront at 18:56, 26 September 2019

2019-09-26T18:56:50Z

Norwinu: /* Configuration */

2017-11-08T17:39:43Z

Configuration

Norwinu: /* Overview */

2017-11-07T00:32:44Z

Overview

Norwinu at 00:31, 7 November 2017

2017-11-07T00:31:49Z

Norwinu: /* Overview */

2017-11-07T00:27:51Z

Overview

Norwinu at 19:17, 2 November 2017

2017-11-02T19:17:10Z

Norwinu at 19:14, 2 November 2017

2017-11-02T19:14:12Z

Norwinu: Created page with " Category: Wireless LAN"

2017-11-02T19:12:04Z

Created page with " Category: Wireless LAN"

New page

[[Category: Wireless LAN]]

← Older revision		Revision as of 18:56, 26 September 2019
Line 1:		Line 1:
−	{{quote\|In ~~progress~~.}}	+	{{quote\|to be archived.}}

	==Overview==		==Overview==

← Older revision		Revision as of 17:39, 8 November 2017
Line 24:		Line 24:

	While MAC authentication + captive portal achieves the requirements above, our specific implementation comes with a few significant limitations/caveats:		While MAC authentication + captive portal achieves the requirements above, our specific implementation comes with a few significant limitations/caveats:
−	* Our wireless infrastructure uses one of the APs as the controller (a.k.a ~~virtual~~ AP ~~controller~~). Since it has limited resources, WiNG cannot run a database server/service.	+	* Our wireless infrastructure uses one of the APs as the controller (a.k.a one AP is in 'Virtual AP' mode). Since it has limited resources, WiNG on a virtual AP cannot run a database server/service. A database is necessary to store information, and thus it is logical that the absence of one means the record-keeping for wireless traffic is minimal and temporary. This imparts the following limitations:
		+	:* For MAC authentication + captive portal fallback (the scheme being proposed for the staff network), self-registration of devices is not possible. That is, MAC entries (for MAC authentication) in the RADIUS database must be manually added.
−	* Captive portal.
		+	:* The 'remembering' of devices by Captive Portal across APs does not seem to work properly. Again, this is likely due to MAC address caching staying local to an AP rather than querying a central database run by a dedicated controller.
		+	:* SMS and email delivery of OTPs (one-time passwords) may not also be possible.
		+
		+

@@ Line 2: / Line 2: @@
 ==Overview==
-This page will document the design/implementation of staff and guest wireless networks. This mini-project builds upon the current, recently upgraded wireless setup, which was acquired and implemented primarily to serve the RF guns in the DC. Wireless hardware is already in place; this documentation relates to software configuration of the networks.
+This page will document the design/implementation of staff and guest wireless networks. This mini-project builds upon the current, recently upgraded wireless setup, which was acquired and implemented primarily to serve the RF guns in the DC. Wireless hardware is already in place; this documentation relates only to software configuration of these new networks.
 It is worth noting that these staff and guest wireless networks were/are not a requirement - rather this is a side project to get more value out of the wireless infrastructure and to provide a perk to staff and guests.

← Older revision		Revision as of 00:31, 7 November 2017
Line 22:		Line 22:

	====Caveats====		====Caveats====
		+
		+	While MAC authentication + captive portal achieves the requirements above, our specific implementation comes with a few significant limitations/caveats:
		+	* Our wireless infrastructure uses one of the APs as the controller (a.k.a virtual AP controller). Since it has limited resources, WiNG cannot run a database server/service.
		+	* Captive portal.

@@ Line 2: / Line 2: @@
 ==Overview==
-This page will document the implementation of staff and guest wireless networks. This project builds upon the current and recently upgraded wireless setup, which was acquired and implemented primarily to serve the RF guns in the DC.
+This page will document the design/implementation of staff and guest wireless networks. This mini-project builds upon the current, recently upgraded wireless setup, which was acquired and implemented primarily to serve the RF guns in the DC. Wireless hardware is already in place; this documentation relates to software configuration of the networks.
 [[Category: Networking]]

← Older revision		Revision as of 19:17, 2 November 2017
Line 1:		Line 1:
		+	{{quote\|In progress.}}
−	{{note\|Currently a placeholder page.}}
		+
		+	==Overview==
		+	This page will document the implementation of staff and guest wireless networks. This project builds upon the current and recently upgraded wireless setup, which was acquired and implemented primarily to serve the RF guns in the DC.

	* Staff: MAC authentication + Captive Portal fallback.		* Staff: MAC authentication + Captive Portal fallback.

← Older revision		Revision as of 19:14, 2 November 2017
Line 1:		Line 1:
		+	{{note\|Currently a placeholder page.}}

		+	* Staff: MAC authentication + Captive Portal fallback.
		+	* Guest: Captive Portal

−	[[Category: ~~Wireless LAN~~]]	+	[[Category: Networking]]