RADIUSdesk

logo
Trace:

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
technical:openwrt-meshdesk-file [2022/09/18 20:40]
admin [Exploring our hardware] 		technical:openwrt-meshdesk-file [2022/09/18 21:17] (current)
admin [Review new hardware]
Line 33: Line 33:
  
    * With this info we can create a hardware section in /etc/config/meshdesk    * With this info we can create a hardware section in /etc/config/meshdesk
- 
 <code bash> <code bash>
 config hardware 'xiaomi_4a_100' config hardware 'xiaomi_4a_100'
Line 40: Line 39:
  option wifi_led 'led0'  option wifi_led 'led0'
 </code> </code>
-  * This have to match the value for hardware under the settings section+ 
 +===== Adjust the settings section accordingly ===== 
 +  * There are two important options here to adjust 
 +        * **hardware** - have to match the value of a hardware definition under the settings section. 
 +        * **id_if** - have to match the interface specified in the **wan_network** file.
 <code bash> <code bash>
 config settings 'settings' config settings 'settings'
Line 48: Line 51:
 </code> </code>
 <WRAP center round tip 100%> <WRAP center round tip 100%>
-Don't make the name of the hardware section more than 14characters. Longer names break things during deployment.+  * Don't make the name of the hardware section more than 14characters. Longer names break things during deployment. 
 +  * Devices where the interface used in wan_network is eth0.1 simply use eth0 here.
 </WRAP> </WRAP>
   * Later we will also use the value of **xiaomi_4a_100** to define the hardware on the controller.   * Later we will also use the value of **xiaomi_4a_100** to define the hardware on the controller.
-  * The final tweak for the hardware in the config file is the interface that must be used as the id_if. +===== Alarm On or Alarm Off?  ===== 
-        * It will typically be **eth0**. +  * We use the yellow LED as an alarm which means it has to light up when communication to the controller is down. 
-        * On devices like the MT7621 based boards it will typically be **wan**. +  * Since we want the **yellow LED** to be off when the communication to the controller is fine we need to check what the current setup is.
-  * Since we want the **yellow LED** to be off when the comms to the controller is fine we need to check what the current setup is.+
 <code bash> <code bash>
 vi /etc/MESHdesk/reporting/report_to_server.lua  vi /etc/MESHdesk/reporting/report_to_server.lua 
 #Look for this section #Look for this section
     if(ok_flag)then                                      if(ok_flag)then                                 
-        internetLED('0'); -- NOTE Here we can swap thme around eg make it 0 to turn off a red LED when the internet is OK+        internetLED('0'); -- NOTE Here we can swap them around eg make it 0 to turn off a red LED when the internet is OK
         checkForContollerReboot('1');                            checkForContollerReboot('1');                   
     else                                                                                  else                                                                             
Line 67: Line 70:
 </code> </code>
  
-  * The following table lists some of the important items with comments+==== Review new hardware ==== 
 + 
 + 
 +  * The following table lists the important items with comments
  
 ^ Item        ^ Typical value           ^ Comment    ^ ^ Item        ^ Typical value           ^ Comment    ^
Line 74: Line 80:
 | settings -> skip_radio_0  | 0 | set to 1 when radio0 is a 5G radio and you don't want to use it for config SSID  | | settings -> skip_radio_0  | 0 | set to 1 when radio0 is a 5G radio and you don't want to use it for config SSID  |
  
-=== Tweaks For Our Environment ===+===== Remember Your Environment ===== 
 +  * Finally you need to adjust some items to match up with your controller and its environment.
   *  The following table lists some of the important items with comments    *  The following table lists some of the important items with comments 
  
 ^ Item        ^ Typical value           ^ Comment    ^ ^ Item        ^ Typical value           ^ Comment    ^
 | internet1 -> disabled    | 1  | change it to 0 in order for the device to be centrally controlled   | | internet1 -> disabled    | 1  | change it to 0 in order for the device to be centrally controlled   |
-| internet1 -> dns    | cloud.radiusdesk.com  | Supply Dummy Value If Not Using DNS System |+| internet1 -> dns    | cloud.radiusdesk.com  | <wrap em>Supply Dummy Value If Not Using DNS System e.g. nohost.radiusdesk.com</wrap> |
 | internet1 -> protocol | https | Can be http or https | | internet1 -> protocol | https | Can be http or https |
 | internet1 -> ip | 176.31.15.210 | Fallback when FQDN does not resolve on FQDN not used | | internet1 -> ip | 176.31.15.210 | Fallback when FQDN does not resolve on FQDN not used |
Last modified: 2022/09/18 20:40