RADIUSdesk

Differences

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

Link to this comparison view

Next revision
Previous revision
user_guide:md_on_lede [2016/11/17 13:57] – created adminuser_guide:md_on_lede [2017/04/09 04:56] (current) – [Preset for a certain model and server] admin
Line 11: Line 11:
  
 ===== Preparing the environment ===== ===== Preparing the environment =====
-  * We assume you have a standard install of the Ubuntu 14.04 operating system.+  * We assume you have a standard install of the Ubuntu 16.04 operating system.
   * You need to install certain required packages which the LEDE build environment needs to function correct.   * You need to install certain required packages which the LEDE build environment needs to function correct.
 <code bash> <code bash>
Line 21: Line 21:
  
 ===== Check out the code ===== ===== Check out the code =====
-  * Since there is not a stable LEDE release yet, we will check out the current development branch+  * We will use the **17.0.1 release** of LEDE which is the first stable release of the LEDE Project. 
 + 
 +<WRAP center round tip 100%> 
 +  * Please note that we use the **release 17.0.1** and not the **lede-17.01 branch**. 
 +  * Refer to this URL for the different releases and branches: https://github.com/lede-project/source/ 
 +</WRAP> 
 <code bash> <code bash>
 cd ~ cd ~
Line 27: Line 33:
 cd lede cd lede
 git clone https://git.lede-project.org/source.git git clone https://git.lede-project.org/source.git
 +#To see the tags (releases)
 +git fetch --tags
 +git tag -l
 +#Checkout the 17.0.1 release
 +git checkout v17.01.0
 </code> </code>
-  * This will create a folder called **source** where the build environemnt resides.+  * This will create a folder called **source** where the build environment resides.
  
-<WRAP center round tip 90%> +<WRAP center round tip 100%> 
-  * Should you wish to update an existing checked out source, use the following command: + <wrap em>Please refrain from using the current development branch or even the **lede-17.01** branch since something in that code breaks the Batman-adv mesh in the MESHdesk firmware making it useless.</wrap>
-<code bash> +
-cd ~ +
-cd lede/source +
-git pull +
-</code>+
 </WRAP> </WRAP>
  
Line 184: Line 190:
   * On these devices the LAN is connected to **eth1** instead of the usual **eth0**.   * On these devices the LAN is connected to **eth1** instead of the usual **eth0**.
   * We know of the **TP-Link WR1043ND** and also the **Archer** models that have this issue.   * We know of the **TP-Link WR1043ND** and also the **Archer** models that have this issue.
 +<code bash>
 + vi ./package/zzz-MESHdesk/files/MESHdesk/meshdesk
 +</code>
   * Edit the following and change:   * Edit the following and change:
 <code bash> <code bash>
Line 192: Line 201:
 option id_if 'eth1' option id_if 'eth1'
 </code> </code>
 +
 +==== Default mode ====
 +  * The MESHdesk firmware currently supports three modes. 
 +  * They are:
 +    * **off** -> The MESHdesk package is not active
 +    * **mesh** -> The device will contact the **MESHdesk** applet and are managed as a mesh node.
 +    * **ap** -> The device will contact the **APdesk** applet and are managed as a member of one of the AP Profiles.
 +<code bash>
 + vi ./package/zzz-MESHdesk/files/MESHdesk/meshdesk
 +</code>
 +    * These are specified as an option under the **settings** section.
 +<code bash>
 +option gw_auto_reboot_time '600'
 +option mode 'mesh'
 +option id_if 'eth0'
 +</code>
 +
 +==== Preset for a certain model and server ====
 +  * Should you wish to already have the firmware setup when you flash it (As needed for Over The Air OTA upgrades) check the following additional items.
 +  * Specify the server it is pointing to
 +<code bash>
 + vi ./package/zzz-MESHdesk/files/MESHdesk/meshdesk
 +</code>
 +  * Under **internet1** the value of **ip**
 +  * Under **settings** the value of **hardware** should specify the correct value of the model you use. Available options are in the same file.
 +  * Then you need to specify a system config file to define the LED we will use to indicate the mesh traffic
 +<code bash>
 + vi ./files/etc/config/system
 +</code>
 +  * Use this as a reference.
 +<code bash>
 +config system
 +        option ttylogin '0'
 +        option log_size '64'
 +        option urandom_seed '0'
 +        option timezone 'SAST-2'
 +        option hostname '505'
 +
 +config timeserver 'ntp'
 +        option enabled '1'
 +        option enable_server '0'
 +        list server '0.lede.pool.ntp.org'
 +        list server '1.lede.pool.ntp.org'
 +        list server '2.lede.pool.ntp.org'
 +        list server '3.lede.pool.ntp.org'
 +
 +config led 'wifi_led'
 +        option name 'wifi'
 +        option trigger 'netdev'
 +        option dev 'bat0'
 +        option mode 'link tx rx'
 +        option sysfs 'zbt-wa05:blue:air'
 +
 +</code>
 +
  
   * Now the tweaks are completed we can select the packages to include.   * Now the tweaks are completed we can select the packages to include.
Line 246: Line 310:
 | **Kernel modules -> USB support -> kmod-usb2** | Required for USB support in device | | **Kernel modules -> USB support -> kmod-usb2** | Required for USB support in device |
 | **Utilities -> usb-modeswitch** | Required to switch the mode of the USB stick from storage to modem  | | **Utilities -> usb-modeswitch** | Required to switch the mode of the USB stick from storage to modem  |
 +
 +
 +
 +==== Atheros based 802.11AC ====
 +
 +  * If you build firmware for hardware that includes the **ATH10K** driver, be sure to also include the binary blob firmware package.
 +  * The following table can be uses as a reference
 +
 +^ Hardware      ^ Firmware Package       
 +| Yuncore XD3200    | ath10k-firmware-qca988x |