<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to conceptwiki</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/</link><description>Recent changes to conceptwiki</description><atom:link href="https://sourceforge.net/p/radiusdesk/conceptwiki/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 30 Nov 2017 16:56:51 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/radiusdesk/conceptwiki/feed.rss" rel="self" type="application/rss+xml"/><item><title>Discussion for BYOD_MAC page</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_MAC/?limit=25#10a7</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
I can't find the option "Use profile during EAP authentication" in BYOD manager applet.&lt;br/&gt;
Can you help me, please?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Emanuele</dc:creator><pubDate>Thu, 30 Nov 2017 16:56:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2b3a2136dff4597385edb863288103d6d8616e7a</guid></item><item><title>Discussion for Administrator page</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/Administrator/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;thats all what i sea &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joyex</dc:creator><pubDate>Thu, 27 Mar 2014 17:52:30 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcf9a7c9edb1fac9314b432dc7900781884d56f49</guid></item><item><title>WikiPage BYOD_MAC modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_MAC/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -54,7 +54,7 @@
 * With the ability to add tags to devices we can even implement our own logic on the back-end.
 * We can for instance require that all the devices belonging to students has to get an RFI identification before they can connect to the campus network.
 * So all **student** (already tagged) devices will get an additional **rfi_complete** tag. 
-* The RADIUS server can them be modified to check if a student device has both tags before allowing them onto the network.
+* The RADIUS server can then be modified to check if a student device has both tags before allowing them onto the network.
 * This is just a simple example of how to unleash the power of tags.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 12:00:53 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5442215a66b2bcd76edf31dc4689da5591caf2e6</guid></item><item><title>WikiPage BYOD_MAC modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_MAC/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,27 +1,62 @@
 # MAC Authentication #
 * A simple way to configure LAN switches is to do MAC Authentication when a device connects to it.
 * This is by no means secure since the MAC Address of a device can be spoofed. 
-* This should not bee seen as a way to secure a LAN but rather to dynamically segment it based on the reply attributes of the RADIUS server.
-* If you need to implement a secure way to authenticate devices on a LAN you should use 802.1x
+* This should not bee seen as a way to secure a LAN but rather to dynamically segment it based on the reply attributes from the RADIUS server.
+* If you need to implement a secure way to authenticate devices on a LAN, use 802.1x

 # 802.1x Authentication #
 * 802.1x can use various EAP methods to authenticate a device to the back-end.
 * The most widely supported menthod is PEAP
 * Unfortunately devices like printers; security cameras etc does not include an 802.1x supplicant and makes implementation usually more complex. 
-* Each vendor of networking equipment has different ways in dealing with devices that doesn ot include a 802.1x supplicant.
-* You are advises to experiment and explore the equipment you have available to see how 802.1x can be optimally implemented.
+* Each vendor of networking equipment has different ways in dealing with devices that does not include a 802.1x supplicant.
+* You are advised to experiment and explore on the equipment you have available to see how 802.1x can be optimally implemented.

 # BYOD Manager applet in RADIUSdesk #
 * RADIUSdesk has a dedicated applet called **BYOD Manager**
 * This applet will list all the registered devices on the system.
 * Each registered device **must** have:
-    * A Permanent User owner
-    * A MAC address to be identified with
-    * A name to be identified with
-    * A profile associated with it
+    * A Permanent User owner.
+    * A MAC address to be identified with.
+    * A name to be identified with.
+    * A profile associated with it.
 * Each registered device **may** have:
-    * The active check disabled/disabled
-    * The use profile during EAP authentication enabled/disabled
+    * The active check enabled/disabled.
+    * The use profile during EAP authentication enabled/disabled.
+    * One or more tags associated with it.
 * Although the BYOD Manager applet gives an overview of all the registered devices; each Permanent User can be assigned through the Permanent User Manager applet one or more devices which in turn will also be displayed on the BYOD Manager.
-* The BYOD Manager is thus a holistic manager of registered devices where the Permanent User's Devices is only a subset of those displayed in the BYOD Manager owned by the choosen Permanent User.
+* The BYOD Manager is thus a holistic manager of registered devices where the Permanent User's Devices is only a subset of those displayed in the BYOD Manager; owned by the chosen Permanent User.
+
+# Profiles associated to devices #
+* With BYOD devices; you will typically assign a profile which returns the information that the LAN switch requires to dynamically assign the device into a VLAN after authentication.
+* The profiles is not limited to it; you can for instance also implement a Captive Portal which makes use of MAC authentication and limit the connection time of a certain device to the captive portal.
+
+## Implementing an associated profile during EAP ##
+* One point which has to be mentioned here is when you use EAP (includes 802.1x and WPA2 Enterprise) to authenticate a device.
+* This device will be authenticated by a username and password (that of a Permanent User) and the profile of the permanent user will be used.
+* You can however select the "Use profile during EAP authentication" on a device.
+* This will include the return attributes of the profile associated with the device **ddding and overriding** to the attributes returned for the authenticated Permanent User.
+* This will allow for fine grained management of each of a user's devices despite the fact that they are using a single username and password to authenticate all of them through EAP.
+* Imagine Bob has a iPad, iPhone and an Android tablet.
+    * We record all these devices' MACs into the BYOD Manager making Bob the owner.
+    * We then can give each of them a unique profile; e.g. assign the Android to the R&amp;amp;D Lab profile and the Apple devices to the corporate LAN.
+    * We make sure the "Use profile during EAP authentication" is selected. 
+    * Provided the back-end is configured in a way to work with the RADIUS server; depending on which device Bob connects; he will be dynamically assigned to the VLAN associated with the profile associated to the device.
+
+
+# Tags assigned to devices #
+* The BYOD Manager also features the ability to add one or more tags to devices.
+* The tags can come in handy to generate reports based on certain tags.
+* One can for instance tag all the printers with the **Printer** tag.
+* One can then optionally tag all the devices in a certain region with a regional tag e.g. **Pretoria**.
+* So for us to get a CSV list of all the **Printers** in **Pretoria** is literally two ticks away!!
+
+## The tag's the limit ##
+* With the ability to add tags to devices we can even implement our own logic on the back-end.
+* We can for instance require that all the devices belonging to students has to get an RFI identification before they can connect to the campus network.
+* So all **student** (already tagged) devices will get an additional **rfi_complete** tag. 
+* The RADIUS server can them be modified to check if a student device has both tags before allowing them onto the network.
+* This is just a simple example of how to unleash the power of tags.
+
+
+

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 11:59:45 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc0bdf074c1f632efd9e73b338081dda8603b9c58</guid></item><item><title>WikiPage Home modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v16
+++ v17
@@ -20,8 +20,7 @@
 * Vouchers 
 * BYOD
     * [BYOD Background](/p/radiusdesk/conceptwiki/BYOD_Background/)
-    * [MAC Authentication](/p/radiusdesk/conceptwiki/BYOD_MAC/)
-    * [EAP](/p/radiusdesk/conceptwiki/BYOD_EAP/)
+    * [MAC Authentication, 802.1x and BYOD Manager ](/p/radiusdesk/conceptwiki/BYOD_MAC/)
 * Advanced concepts #
     * [i18n]
     * [Rights]
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 11:27:45 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1051007a056c006a834c53d703a6c42eaf28c61a</guid></item><item><title>WikiPage BYOD_MAC modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_MAC/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="mac-authentication"&gt;MAC Authentication&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;A simple way to configure LAN switches is to do MAC Authentication when a device connects to it.&lt;/li&gt;
&lt;li&gt;This is by no means secure since the MAC Address of a device can be spoofed. &lt;/li&gt;
&lt;li&gt;This should not bee seen as a way to secure a LAN but rather to dynamically segment it based on the reply attributes of the RADIUS server.&lt;/li&gt;
&lt;li&gt;If you need to implement a secure way to authenticate devices on a LAN you should use 802.1x&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="8021x-authentication"&gt;802.1x Authentication&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;802.1x can use various EAP methods to authenticate a device to the back-end.&lt;/li&gt;
&lt;li&gt;The most widely supported menthod is PEAP&lt;/li&gt;
&lt;li&gt;Unfortunately devices like printers; security cameras etc does not include an 802.1x supplicant and makes implementation usually more complex. &lt;/li&gt;
&lt;li&gt;Each vendor of networking equipment has different ways in dealing with devices that doesn ot include a 802.1x supplicant.&lt;/li&gt;
&lt;li&gt;You are advises to experiment and explore the equipment you have available to see how 802.1x can be optimally implemented.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="byod-manager-applet-in-radiusdesk"&gt;BYOD Manager applet in RADIUSdesk&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;RADIUSdesk has a dedicated applet called &lt;strong&gt;BYOD Manager&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;This applet will list all the registered devices on the system.&lt;/li&gt;
&lt;li&gt;Each registered device &lt;strong&gt;must&lt;/strong&gt; have:&lt;ul&gt;
&lt;li&gt;A Permanent User owner&lt;/li&gt;
&lt;li&gt;A MAC address to be identified with&lt;/li&gt;
&lt;li&gt;A name to be identified with&lt;/li&gt;
&lt;li&gt;A profile associated with it&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Each registered device &lt;strong&gt;may&lt;/strong&gt; have:&lt;ul&gt;
&lt;li&gt;The active check disabled/disabled&lt;/li&gt;
&lt;li&gt;The use profile during EAP authentication enabled/disabled&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Although the BYOD Manager applet gives an overview of all the registered devices; each Permanent User can be assigned through the Permanent User Manager applet one or more devices which in turn will also be displayed on the BYOD Manager.&lt;/li&gt;
&lt;li&gt;The BYOD Manager is thus a holistic manager of registered devices where the Permanent User's Devices is only a subset of those displayed in the BYOD Manager owned by the choosen Permanent User.&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 11:24:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9a253cc19710baf6d274847220373c81e5ee2abd</guid></item><item><title>WikiPage BYOD_Background modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_Background/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -46,5 +46,8 @@
     * 802.1x
 * With MAC Authentication, the LAN switch will forward a request to the RADIUS server using the connecting device's MAC address as the username
 * With 802.1x, the connecting device requires a small program called a supplicant to interact with the LAN switch and the LAN switch in turn will forward the request to the RADIUS server. The supplicant typically requires the imput of a username and password.
-* Some more advanced Wi-Fi Access Points also includes a feature where the reply of the WPA2 Enterprise authentication can instruct the Access Point assign the newly authenticated user into a specified VLAN. 
+* Some more advanced Wi-Fi Access Points also includes a feature where the reply of the WPA2 Enterprise authentication can instruct the Access Point assign the newly authenticated user into a specified VLAN.
+* The hostapd program responsible for WPA2 Enterprise authentication on the Atheros Chip devices running OpenWRT has such a patch:
+http://patchwork.openwrt.org/patch/2761/
+* I still have to confirm if it works as intended though.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 10:54:02 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd105560ec7dbf5506ce6ec383cc35fd8532657f0</guid></item><item><title>WikiPage BYOD_Background modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_Background/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -44,6 +44,7 @@
 * There are usually two methods (or a mixture of these two methods) available on LAN switches
     * MAC Authentication
     * 802.1x
-* With MAC Authentication, the LAN switch will forward a request to the RADIUS server using the connecting device's MAC address and the username
-* With 802.1x, the connecting device requires a small program called a supplicant to interact with the LAN switch and the LAN switch in turn will forward the request to the RADIUS server. The supplicant typically requires the imput of a username and password. 
+* With MAC Authentication, the LAN switch will forward a request to the RADIUS server using the connecting device's MAC address as the username
+* With 802.1x, the connecting device requires a small program called a supplicant to interact with the LAN switch and the LAN switch in turn will forward the request to the RADIUS server. The supplicant typically requires the imput of a username and password.
+* Some more advanced Wi-Fi Access Points also includes a feature where the reply of the WPA2 Enterprise authentication can instruct the Access Point assign the newly authenticated user into a specified VLAN.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 10:49:56 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net38f809ab7053a8f6b2ca62902aa8523168047b4c</guid></item><item><title>WikiPage BYOD_Background modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_Background/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,5 +1,5 @@
 # Introduction #
-Every few years there's is a new buzzword. As of this writing one of them is BYOD (Bring Your Own Device). The concept it this:
+Every few years there's is a new buzzword. As of this writing one of them is BYOD (Bring Your Own Device). The concept is this:

 * Most users in an enterprise environment today are likely to bring along one of their own devices from home to the workplace.
 * Most of these devices will connect through the wireless network.
@@ -21,4 +21,29 @@
 * Core protection should be implemented no matter who has access to the corporate network.
 * This includes the following:
     * Web pages served through https
-    * Mandatory username and password protection on important systems 
+    * Mandatory username and password protection on important systems
+
+# BYOD Solutions #
+Most big vendors today do have products that let you manage BYOD in a way they see most practiacl and efficient.
+Sometimes however there is a few things to watch out for when evaluating the product:
+
+* **Cost** Some of the BYOD management systems are very expensive and although it may include a lot of features; make sure that you actually have a need for these features before investing into such a product.
+* **Proprietary nature** Some products require that you have a homogenous environment with a single vendor's equipment for the product to work in an optimal way. This can lead to vendor-lock in.
+* **Mandatory Agent installations** As anyone who's been involved with a network with more than 20 users will know, this is not always practical. Reconsider if the product requires a user to install something first on their own device before it can access the corporate network. We all know the familiar *Since this has been installed...* accusations.
+
+# A simple BYOD solution #
+* A simple BYOD solution can be through dynamic VLAN assignment.
+* Most of today's LAN switches (and some Access Points) includes a feature where the VLAN which a device that connects to it can be prescribed by a back-end (RADIUS) server.
+* The Reply attributes which these LAN switches responds to is:
+    * Tunnel-Type := VLAN
+    * Tunnel-Medium-Type := IEEE-802
+    * Tunnel-Private-Group-Id := "100"
+
+## Instructing a NAS to use dynamic VLANS ##
+* This depends on each vendor's implementation and you are advised to consult the vendor's documentation on it.
+* There are usually two methods (or a mixture of these two methods) available on LAN switches
+    * MAC Authentication
+    * 802.1x
+* With MAC Authentication, the LAN switch will forward a request to the RADIUS server using the connecting device's MAC address and the username
+* With 802.1x, the connecting device requires a small program called a supplicant to interact with the LAN switch and the LAN switch in turn will forward the request to the RADIUS server. The supplicant typically requires the imput of a username and password. 
+  
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 10:45:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net32a24f0b526c84b1e3e9f971d302ff94f0aae9a8</guid></item><item><title>WikiPage BYOD_Background modified by Dirk van der Walt</title><link>https://sourceforge.net/p/radiusdesk/conceptwiki/BYOD_Background/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;Every few years there's is a new buzzword. As of this writing one of them is BYOD (Bring Your Own Device). The concept it this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Most users in an enterprise environment today are likely to bring along one of their own devices from home to the workplace.&lt;/li&gt;
&lt;li&gt;Most of these devices will connect through the wireless network.&lt;/li&gt;
&lt;li&gt;Some devices may also connect through the LAN to the corporate network.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="security"&gt;Security&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;In order to limit the unknown devices to a corporate network today one may protect the corporate network at two places:&lt;ul&gt;
&lt;li&gt;The edge&lt;/li&gt;
&lt;li&gt;The core&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There are also deployments which makes (and should actually) make use of both.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="edge-protection"&gt;Edge protection&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Edge protection includes:&lt;ul&gt;
&lt;li&gt;VPN connection on the outside firewall&lt;/li&gt;
&lt;li&gt;802.1x security on the LAN&lt;/li&gt;
&lt;li&gt;WPA2 Enterprise security on the WLAN&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="core-protection"&gt;Core protection&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Core protection should be implemented no matter who has access to the corporate network.&lt;/li&gt;
&lt;li&gt;This includes the following:&lt;ul&gt;
&lt;li&gt;Web pages served through https&lt;/li&gt;
&lt;li&gt;Mandatory username and password protection on important systems &lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk van der Walt</dc:creator><pubDate>Wed, 06 Feb 2013 10:23:04 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5ad0a8c00c3202b2bffad555c7a6d8d43007ee89</guid></item></channel></rss>