RADIUSdesk

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:openwrt_rb750gr3 [2021/02/10 08:11] – [Load a RAM based version of OpenWRT] adminuser_guide:mikrotik:openwrt_rb750gr3 [2022/04/26 09:26] (current) – [Introduction] admin
Line 8: Line 8:
   * Some of their models are also able to run OpenWRT as an alternative to RouterOS.   * Some of their models are also able to run OpenWRT as an alternative to RouterOS.
   * OpenWRT is OpenSource and there is no paid for licensing involved on OpenWRT.   * OpenWRT is OpenSource and there is no paid for licensing involved on OpenWRT.
-  * This page will just cover the flash from RouterOS to OpenWRT on the Mikrotik RB750Gr3.+  * This page will **only** cover the flash from RouterOS to OpenWRT on the Mikrotik RB750Gr3.
   * We will cover the configuration of the device once OpenWRT is running on it on a separate page.   * We will cover the configuration of the device once OpenWRT is running on it on a separate page.
  
Line 59: Line 59:
 Now that we have the license key taken care of we can go to the next step which is to load the RAM based OpenWRT onto the device Now that we have the license key taken care of we can go to the next step which is to load the RAM based OpenWRT onto the device
  
-==== Load a RAM based version of OpenWRT ====+===== Load a RAM based version of OpenWRT =====
   * In order for us to get the RAM based version of OpenWRT onto the Mikrotik two things are involved.   * In order for us to get the RAM based version of OpenWRT onto the Mikrotik two things are involved.
      - There has to be a BOOTP environment set up to serve the RAM based image      - There has to be a BOOTP environment set up to serve the RAM based image
      - The Mikrotik has to be set in such a mode as to use the BOOTP environment to fetch the RAM based image using BOOTP      - The Mikrotik has to be set in such a mode as to use the BOOTP environment to fetch the RAM based image using BOOTP
  
-=== Set up a BOOTP Environment ===+==== Set up a BOOTP Environment ====
  
    * On Ubuntu it is very simple and we just create a small shell script to take care of it    * On Ubuntu it is very simple and we just create a small shell script to take care of it
Line 70: Line 70:
 <file bash  loader.sh> <file bash  loader.sh>
 #!/bin/bash #!/bin/bash
 +#HEADS UP substitute with the logged in user's name that you use to create this file e.g. whoami output
 USER=system USER=system
 #HEADS UP THIS MUST MATCH YOUR MACHINE'S LAN INTERFACE #HEADS UP THIS MUST MATCH YOUR MACHINE'S LAN INTERFACE
Line 109: Line 110:
  
 === Force Mikrotik to use BOOTP === === Force Mikrotik to use BOOTP ===
 +== We add a note on setting the Mikrotik up to do BOOTP ==
 +  * Not all Mikrotiks we worked with had BOOTP enabled after a reset.
 +  * For those there is a manual procedure you have to follow to enable this startup functionality.
 +  * https://wiki.mikrotik.com/wiki/Manual:Etherboot
 +  * https://wiki.mikrotik.com/wiki/Manual:RouterBOARD_settings
 +
 +== Kicking off BOOTP ==
   * To force the Mikrotik to use the BOOTP environment you need to connect the Internet Port of the Mikrotik to your Linux machine. (Internet Port is Port 1 on the Mikrotik)   * To force the Mikrotik to use the BOOTP environment you need to connect the Internet Port of the Mikrotik to your Linux machine. (Internet Port is Port 1 on the Mikrotik)
   * Press the RESET button while powering up the board.   * Press the RESET button while powering up the board.
Line 149: Line 157:
      * Alternatively you can use ssh to connect to 192.168.1.1      * Alternatively you can use ssh to connect to 192.168.1.1
  
-=== Optional - Backup the original RouterOS Partition === +  * We are all set now to flash the final version of OpenWRT onto the device. 
-  * This step is optional in case you want to make a backup of the flash partition that has the RouterOS on it+  * At this stage you can still return the device back to the original RouterOS by simply rebooting it since the OpenWRT running is all in RAM. 
-  * You have to do this BEFORE flashing the final version of OpenWRT onto the device+  * We are however not going to do that since we want to move over to OpenWRT permanently :-) 
 + 
 +===== Flash the permanent version of OpenWRT ===== 
 +  * Download the **sysupgrade** version of the firmware. 
 +  * Ours is called **openwrt-19.07.6-ramips-mt7621-mikrotik_rb750gr3-squashfs-sysupgrade.bin** at the time of this writing. 
 +  * We will show the shell commands to do the flash but the Luci GUI should work just as well 
 +<code bash> 
 +#Copy the *sysupgrade* file to the /tmp dir on the Mikrotik 
 +scp openwrt-19.07.6-ramips-mt7621-mikrotik_rb750gr3-squashfs-sysupgrade.bin root@192.168.1.1:/tmp 
 +#SSH into the Mikrotik 
 +ssh root@192.168.1.1 
 +#Change directory to /tmp 
 +cd /tmp 
 +#Do a sysupgrade  
 +sysupgrade openwrt-19.07.6-ramips-mt7621-mikrotik_rb750gr3-squashfs-sysupgrade.bin 
 +#USR LED will flash while it is writing to flash 
 +#After ~2min it will stop and reboot (beeper will beep)  
 +</code> 
 +  * Congratulations you have now successfully migrated from RouterOS to OpenWRT 
 +  * If it might happen so that in future you mess up the current version of OpenWRT so bad that it will not let you in, you can just repeat the BOOTP RAM image boot and repeat this step again. 
 +  * This makes the RouterBoard pretty robust