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:md_node_config_utility [2016/10/31 04:44] – [Operating instruction for MESHdesk Node config utility] adminuser_guide:md_node_config_utility [2016/11/05 22:49] (current) – admin
Line 1: Line 1:
 ====== MESHdesk Node Config Utility ====== ====== MESHdesk Node Config Utility ======
-  * As of October 2016 we've released a fresh version of the **MESHdesk Node Config Utility** to include new features not supported yet in the industry.+  * As of October 2016 we have released a fresh version of the **MESHdesk Node Config Utility** to include new features not supported yet in the industry.
   * This page will discuss the new **MESHdesk Node Config Utility**. We will divide the discussion into segments similar to the tabs of the **MESHdesk Node Config Utility**.   * This page will discuss the new **MESHdesk Node Config Utility**. We will divide the discussion into segments similar to the tabs of the **MESHdesk Node Config Utility**.
   * Before we go into the various tabs let us first discover how to use the **MESHdesk Node Config Utility** (here after simply called the utility) in the correct manner.   * Before we go into the various tabs let us first discover how to use the **MESHdesk Node Config Utility** (here after simply called the utility) in the correct manner.
Line 10: Line 10:
   * This is where we use the utility.   * This is where we use the utility.
   * Another purpose for the utility is to 'prime' the hardware for an Internet connection.   * Another purpose for the utility is to 'prime' the hardware for an Internet connection.
-  * We took the lead and added extra functionality to our firmware which does not enforce an Ethernel (LAN) connection for Internet connectivity.+  * We took the lead and added extra functionality to our firmware so that you are not limited to Ethernet (LAN) connection for Internet connectivity anymore.
   * We now support the following types of Internet connections.   * We now support the following types of Internet connections.
-    * Ethernet (LAN) which require a DHCP server and Internet connection on the LAN the hardware connects to. This is the same as other cloud based controlled hardware like OpenMesh, Meraki, or IgniteNet. +    * Ethernet (LAN) which require a DHCP server and Internet connection on the LAN the hardware connects to. Most cloud based controlled hardware like OpenMesh, Meraki, or IgniteNet use only Ethernet. 
-    * **3G/4G dongle** support. For this you simply need hardware with a USB port. You then use the utility to preset the hardware with settings to obtain an Internet connection through the dongle. This is a first when compared to what is available today and will probably be first for a while since not many commercial cloud controlled hardware includes a USB port. +    * **3G/4G dongle** support. For this you simply need a router with a USB port. With the Node Config Utility you preset the hardware with settings to obtain an Internet connection through the dongle. Not many commercial cloud controlled hardware includes a USB port. 
-    * **WiFi Client** support. No need for extra hardware, we can simply use one of the existing radios to connect as a client to a WiFi network and distribute the connection from there. Again a first especially on meshes, since this is done in the firmware the commercial guys might have more success also implementing this.+    * **WiFi Client** support. No need for extra hardware, we can simply use your current WiFi router to connect as a client to a WiFi network and distribute the connection from there. In other words, we can build a mesh network onto your existing WiFi network. Again a first, especially on meshes.
  
 <WRAP center round tip 90%> <WRAP center round tip 90%>
-With **3G/4G dongle ** and **WiFi Client** support we  can really say goodbye LAN cables on our meshes and access points!+  * With **3G/4G dongle ** and **WiFi Client** support we  can really say goodbye to LAN cables on our meshes and access points! 
 +  * [[user_guide:mobile_support|3G / Mobile support for APdesk and MESHdesk]] 
 +  * [[user_guide:wifi_client_support|Support for WiFi Client as an Internet connection]] 
 </WRAP> </WRAP>
  
Line 57: Line 60:
  
 ------------------------ ------------------------
- 
- 
- 
  
 ===== Current Settings ===== ===== Current Settings =====
Line 94: Line 94:
 </WRAP> </WRAP>
  
 +------------
 +
 +===== 3G Option =====
 +
 +{{ :user_guide:node_config:new_node_config_3g_settings.png?nolink |}}
 +
 +  * The **3G Option** offers an alternative way to configure the device for obtaining an Internet connection.
 +  * Be sure the device has either an on-board 3G/4G module or an USB port with the required packages included with the firmware for 3G/4G dongle support.
 +  * The default value of **Action** is not to change any existing setup.
 +  * If you select **Enable** the other fields becomes available to configure.
 +  * Normally there are two things that require setting up. They are the **APN** and **PIN**.
 +  * The value of the **APN** depends on the mobile provider and may also include an optional **Username**.
 +  * The PIN is specific to the SIM card which you use for connecting to the mobile network and may be disabled. Simply leave the field blank if the PIN is disabled.
 +  * If you wish to disable an existing 3G setup, simply change the **Action** to **Disable** and ensure the device re-contacts the utility (power cycle the device) to commit those changes.
 +
 +-------
 +
 +===== WiFi Client =====
 +
 +{{ :user_guide:node_config:new_node_config_wifi_settings.png?nolink |}}
 +
 +  * The **WiFi Client** offers an alternative way to configure the device for obtaining an Internet connection.
 +  * For this option we do not need any additional hardware and make use of the radio in client (station) mode to provide also Internet connectivity.  Be sure though that the firmware includes the **relayd** package for this option to work.
 +  * The default value of **Action** is not to change any existing setup.
 +  * If you select **Enable** the other fields becomes available to configure.
 +  * Normally there are three things that require setting up. They are the **SSID**, **Encryption** and **Key**.
 +  * If you have a dual radio device, you can also opt for selection one of the two radios. For single radio devices, leave the default of **Radio 0**.
 +  * If you wish to disable an existing WiFi Client setup, simply change the **Action** to **Disable** and ensure the device re-contacts the utility (power cycle the device) to commit those changes.
 +
 +<WRAP center round tip 90%>
 +  * The MediaTek and Atheros ath9k WiFi drivers allow the radio to support multiple modes simultaneously.
 +  * This enable us to offer this option while also using the same radio to do Mesh and Access Point at the same time.
 +  * Remember though there will be a performance drop. 
 +  * If speed is an issue consider using dual radio hardware instead or connecting through the LAN port
 +</WRAP>
 +
 +-------
  
 +===== Security =====
  
 +{{ :user_guide:node_config:new_node_config_security_settings.png?nolink |}}
  
 +  * This is an advanced setting. Leave it untouched unless you know what you're doing.
  
  
    
  
Last modified: 2016/10/31 04:44