RADIUSdesk

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
user_guide:mikrotik:rb751 [2017/02/01 12:52] – [What next] adminuser_guide:mikrotik:rb751 [2022/05/09 12:22] (current) – [Converting an Unknown client] admin
Line 5: Line 5:
 With this scenario we assume you have: With this scenario we assume you have:
   * A recent installation of RADIUSdesk which includes Dynamic RADIUS Clients support.    * A recent installation of RADIUSdesk which includes Dynamic RADIUS Clients support. 
-    * We will use our **Radiusdesk Hosted** server which has an IP Address of **178.32.59.137** in this document. +    * We will use our **cloud.radiusdesk.com** demo server which has an IP Address of **164.160.89.129** in this document. 
-    * Our **Radiusdesk Hosted** server has a site wide RADIUS shared secret of **RDhostedXYZ2525**.+    * Our  **cloud.radiusdesk.com** demo server has a site wide RADIUS shared secret of **testing123**.
   * A new (or reset to defaults) Mikrotik RouterBOARD 751U which you will set up from scratch.   * A new (or reset to defaults) Mikrotik RouterBOARD 751U which you will set up from scratch.
   * You want to run a Captive portal on the Mikrotik's WiFi interface.   * You want to run a Captive portal on the Mikrotik's WiFi interface.
Line 15: Line 15:
   * If you connect with a machine which has DHCP enabled; you will get a 192.168.88.x IP Address while the RouterBOARD 751U can be reached through 192.168.88.1.   * If you connect with a machine which has DHCP enabled; you will get a 192.168.88.x IP Address while the RouterBOARD 751U can be reached through 192.168.88.1.
   * The default username is **admin** with **no password**.   * The default username is **admin** with **no password**.
 +  * Newer versions of ROS insist you set a password. If you never had password on the device specify the old password as blank text and specify the new value and confirm it to set the password on the device.
  
 ===== Our approach ===== ===== Our approach =====
 We will take the following configuration approach. This approach very common on the 751U. We will take the following configuration approach. This approach very common on the 751U.
-  * Ethernet port 1 (Marked PoE) will be used to connect the 751U to the Internet. (Typically a DSL router's Ethernet port)+  * Ethernet port 1 (Marked PoE) will be used to connect the 751U to the Internet. (Typically a LTE router's Ethernet port)
   * Ethernet port 1 will be configured to be a **DCHP Client**.   * Ethernet port 1 will be configured to be a **DCHP Client**.
   * Ethernet ports 2-5 will be used as a Ethernet switch which runs a DHCP Server and NAT traffic between Ethernet port 1 and Ethernet ports 2-5.   * Ethernet ports 2-5 will be used as a Ethernet switch which runs a DHCP Server and NAT traffic between Ethernet port 1 and Ethernet ports 2-5.
Line 45: Line 46:
  
 ===== Set the Mikrotik's identity ===== ===== Set the Mikrotik's identity =====
-  * We will use a fictional convention and assume that this Mikrotik is the first one deployed in the city of Pretoria, Gauteng province, South Africa. +  * We will use a geographic naming convention and assume that this Mikrotik is the first one deployed in the city of Johannesburg, Gauteng province, South Africa. 
-  * The systems identity will thus be **za-gp-pta-001**.+  * The systems identity will thus be **za-gp-jhb-001**.
   * Connect to the Mikrotik's web interface and select **System** -> **Identity**.   * Connect to the Mikrotik's web interface and select **System** -> **Identity**.
-  * Specify the Identiry as **za-gp-pta-001** and click **Apply** +  * Specify the Identity as **za-gp-jhb-001** and click **Apply** 
  
 ===== Confirm Ethernet-1's status ===== ===== Confirm Ethernet-1's status =====
   * Connect to the Mikrotik's web interface and select **IP** -> **DHCP Client**.   * Connect to the Mikrotik's web interface and select **IP** -> **DHCP Client**.
   * The **ether1-gateway** interface should be listed along with it's DHCP supplied IP Address.   * The **ether1-gateway** interface should be listed along with it's DHCP supplied IP Address.
-{{ :user_guide:mikrotik:ethernet1-dhcp.jpg |}}+{{:user_guide:mikrotik:dhcp_client.png|}}
   * If this is not listed or the interface does not have an IP Address assigned to it; ensure that it is fixed before continuing.   * If this is not listed or the interface does not have an IP Address assigned to it; ensure that it is fixed before continuing.
  
Line 59: Line 60:
   * Connect to the Mikrotik's web interface and select **Bridge**.   * Connect to the Mikrotik's web interface and select **Bridge**.
   * Select the **Ports** sub-tab to see the list of ports and to which bridge they are assigned.   * Select the **Ports** sub-tab to see the list of ports and to which bridge they are assigned.
-  * By default **wlan1** and **ether2-master-local** will be members of the bridge named **bridge**. +  * By default **ether2-master**, **wlan1**, **ether3**, **ether4** and **ether5** will be members of the bridge named **bridge**. 
-  * Remove **wlan1** from the list of ports (thus being a member of the bridge named **bridge**). +  * Remove **wlan1** from the list of ports. 
-{{ :user_guide:mikrotik:bridge-local.jpg |}}+{{:user_guide:mikrotik:bridge.png|}} 
 +  * To remove the interface click on the **-** button. The **D** button will simply disable it. 
 +{{:user_guide:mikrotik:bridge-no-wlan.png|}}
  
 ===== Add a RADIUS server ===== ===== Add a RADIUS server =====
Line 68: Line 71:
   * Click the **Add new** button to add a RADIUS server.   * Click the **Add new** button to add a RADIUS server.
     * Select the **Hotspot** service.     * Select the **Hotspot** service.
-    * Specify the IP Address of the RADIUSdesk server running FreeRADIUS. (We use 178.32.59.137) +    * Specify the IP Address of the RADIUSdesk server running FreeRADIUS. (We use 164.160.89.129) 
-    * Specify the shared secret. (We use RDhostedXYZ2525)+    * Specify the shared secret. (We use testing123)
     * Since our server is somewhere out on the Internet, we increase the timeout to 5000ms.     * Since our server is somewhere out on the Internet, we increase the timeout to 5000ms.
     * Leave **Accounting Backup** unchecked.     * Leave **Accounting Backup** unchecked.
-{{:user_guide:mikrotik:mt-radius.jpg}}+{{:user_guide:mikrotik:radius.png}}
   * Next we will set-up the hotspot   * Next we will set-up the hotspot
  
Line 129: Line 132:
 ===== Our situation ===== ===== Our situation =====
  
-  * With our setup in this document, we make use of a VPS server that runs RADIUSdesk somewhere in the cloud. (We use our **Radiusdesk Hosted** server.) +  * The setup described here makes use of a VPS server that runs RADIUSdesk somewhere in the cloud. (We use cloud.radiusdesk.com) 
-  * Recent versions of RADIUSdesk makes it super easy to add a RADIUS client to the FreeRADIUS server to which RADIUSdesk is a front-end. +  * RADIUSdesk makes it super easy to add a RADIUS client to the FreeRADIUS server. 
-  * One simply have to take care of the following items when you are pointing a RADIUS client to the RADIUSdesk server. +  * Simply take care of the following items when you are pointing a RADIUS client to the RADIUSdesk server: 
-    * Specify the public IP Address of the RADIUSdesk server.+    * Public IP Address of the RADIUSdesk server.
     * Ensure the site wide shared secret is correct. (Check this with the person who configured the RADIUSdesk server)     * Ensure the site wide shared secret is correct. (Check this with the person who configured the RADIUSdesk server)
-    * Ensure there is a unique identifier the RADIUS client can identify itself to the server. (We did this by setting the **Identity** of the Mikrotik router.) +    * Ensure there is a unique identifier the RADIUS client can identify itself with to the server. (We did this by setting the **Identity** of the Mikrotik router.) 
-  * After you took care of that a simply reboot the Mikrotik router while it has an active Internet connection. +  * After you took care of that simply reboot the Mikrotik router while it has an active Internet connection. 
-  * It should then be reported under the **Unknown Clients** list of the **RADIUS -> Dynamic RADIUS Clients** applet.+  * It should then be reported under the **Unknown Clients** list of the **RADIUS -> RADIUS Clients** applet. 
 +  * The **Unknown Clients** tab is closed by default. To launch it, click the **Unknown Clients** button in the **RADIUS Clients**  applet. (Last button on the right of the toolbar)
  
-{{ :user_guide:mikrotik:dynamic_clients_unknown.png?nolink |}} +{{ :user_guide:mikrotik:unknown_clients.png?nolink |}} 
-===== Converting an Unknown client  =====+ 
 +===== Converting An Unknown Client  =====
   * After the Mikrotik appeared under the **Unknown clients** tab we can convert it to a known client.   * After the Mikrotik appeared under the **Unknown clients** tab we can convert it to a known client.
   * Select the unknown client you want to convert and click on the  **Attach** button.   * Select the unknown client you want to convert and click on the  **Attach** button.
Line 151: Line 156:
 {{ :user_guide:mikrotik:dynamic_clients_attach_realms.png?nolink |}} {{ :user_guide:mikrotik:dynamic_clients_attach_realms.png?nolink |}}
   * After you click the **Next** button this item will be moved to the list of known Dynamic Radius Clients. As you can see this item indicates that it never contacted the RADIUSdesk server.   * After you click the **Next** button this item will be moved to the list of known Dynamic Radius Clients. As you can see this item indicates that it never contacted the RADIUSdesk server.
-{{ :user_guide:mikrotik:dynamic_clients_known_never_contact.png?nolink |}}+{{ :user_guide:mikrotik:radius_client.png |}}
   * Simply reboot the Mikrotik to confirm that contact is now established:   * Simply reboot the Mikrotik to confirm that contact is now established:
-{{ :user_guide:mikrotik:dynamic_clients_known_contact.png?nolink |}}+{{ :user_guide:mikrotik:radius_client_online.png |}}
   * This brings us to the end of this section   * This brings us to the end of this section
  
Last modified: 2017/02/01 12:52