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
Next revisionBoth sides next revision
toh:mikrotik:rb2011uias [2019/04/23 16:15] – cleanup; moved outdated content to end of page tmomastoh:mikrotik:rb2011uias [2021/02/27 18:05] – cleanup according to the fixme notes danijeltudek
Line 32: Line 32:
 Please refer to [[toh:mikrotik:common|Common Procedures for Mikrotik RouterBoard Products]]. Please refer to [[toh:mikrotik:common|Common Procedures for Mikrotik RouterBoard Products]].
  
- 
-==== How to remove RouterOS and install OpenWrt ==== 
- 
-**1.** What you need ? 
- 
--> (**<color #7092be>Source</color>**) Second OpenWrt router with Extroot for image files, [[http://downloads.openwrt.org/releases/17.01.4/targets/ar71xx/mikrotik/]] 
- 
--> (**<color #7092be>Target</color>**) MikroTik RouterBoard RB2011-UiAS-2HnD-IN router 
- 
-**2.** Images 
- 
-You must check version of your MikroTik device. 
- 
-For 64M version you have to install **lede-XX.XX.X-ar71xx-mikrotik-nand-64m-squashfs-sysupgrade.bin** 
- 
-For more than 64MB version you have to install **lede-XX.XX.X-ar71xx-mikrotik-nand-large-squashfs-sysupgrade.bin** 
- 
-Where ''XX.XX.X'' is the latest release version number. 
- 
-**lede-XX.XX.X-ar71xx-mikrotik-vmlinux-initramfs-lzma.elf** file you need to upload to the source device, this file is used to run in MikroTik memory. 
- 
- 
-**3.** How the installation proceeds (elucidation) 
- 
-OpenWrt installation takes place in two stages - first we write OpenWrt to the device's memory, then install image to the target device NAND. 
- 
-We need to configure the tftp server on the source device, giving the path to the image file that will be sent to the target device memory. 
- 
-Connecting target device (eth1) to the source device (any switch port) image will be sent to the target device's memory. 
- 
-Sound signal informs about the completed procedure of transferring the image to the target device memory. 
- 
-Now it is possible to log into the target device via ssh (user root, no password) 
- 
-If everything went well, you can now start the installation to the NAND memory of the target device. 
- 
-You need to setup basic HTTP web server on your laptop or PC. 
- 
- 
-**4.** Step by step installation 
- 
-Edit source device configuration ''/etc/config/dhcp'' adding 
- 
- 
-''option enable_tftp'1' 
-option tftp_root '/tftpboot' 
-option dhcp_boot 'filename.elf''' 
- 
-at the end of this file add 
- 
-''config 'host' 
-        option 'name' 'mikrotik' 
-        option 'ip'   '192.168.1.230' 
-        option 'mac'  '54:8d:8c:15:df:00''' 
-         
-where '''mac''' is your target device mac address. 
- 
-Save changes and wget **lede-XX.XX.X-ar71xx-mikrotik-vmlinux-initramfs-lzma.elf** into ''/tftpboot'' folder. 
- 
-Reboot your source device. 
- 
-Power on your target device with reset button pushed until ''Ether Boot'' message appears. 
- 
-Ether boot mode try to download image from your network device. 
- 
-Connect target device (eth1) to the source device (any switch port) image will be sent to the target device's memory. 
- 
-One short signal from your target device informs about the completed procedure. 
- 
-On your source device syslog should contain: 
- 
-    Mon Jan  8 19:15:09 2018 daemon.info dnsmasq-dhcp[1073]: BOOTP(br-lan) 192.168.1.230 54:8d:8c:15:df:00  
-    Mon Jan  8 19:15:11 2018 daemon.info dnsmasq-tftp[1073]: sent /tftpboot/lede-17.01.4-ar71xx-mikrotik-vmlinux-initramfs-lzma.elf to 192.168.1.230 
-    Mon Jan  8 19:15:25 2018 daemon.info odhcpd[787]: Using a RA lifetime of 0 seconds on br-lan 
- 
-On your Laptop or PC manualy configure static IP 192.168.1.120 with 255.255.255.0 subnet and 192.168.1.1 gate 
- 
-Disconnect cable from source device. Connect your laptop or PC to the ''ETH10'' port on your target device (from this point target device can not be reset, OpenWrt is running in memory). 
- 
-SSH into target device (user root, no password) 
- 
-You should now see OpenWrt command line. Next step is to download image file *.bin to the /tmp directory of your target device. 
- 
-    # cd /tmp 
-    # wget http://192.168.1.120/image.bin 
-    # sysupgrade -n /tmp/lede-XX.XX.X-ar71xx-mikrotik-nand-XX-squashfs-sysupgrade.bin 
-     
-Where ''192.168.1.120'' is your Laptop or PC basic web server. Yep, you need to download *.bin image to the root folder of your web server. 
- 
-The sysupgrade command flash your nand target device and reboot your MikroTik router automatically. 
  
 ===== Hardware ===== ===== Hardware =====
Line 140: Line 50:
 ^ other               | 2" color touch display                                           | ^ other               | 2" color touch display                                           |
  
-[[http://i.mt.lv/routerboard/files/Block-RB2011UAS-2HnD.pdf|vendor supplied hardware diagram]] +FIXME [[http://i.mt.lv/routerboard/files/Block-RB2011UAS-2HnD.pdf|vendor supplied hardware diagram]]
- +
- +
- +
-===== Historical info ===== +
- +
-FIXME For reference only. Delete after 31/12/2019  --- //[[tmo26@gmx.de|tmomas]] 2019/04/23 16:04// +
- +
-<del>05/2015: Barrier Breaker & Trunk can boot this device, but the built-in 5 * GigE switch does not connect correctly to the CPU. Compiling the OpenWrt kernel with a patch is required (see below).</del> Fixed in [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=e457d22261b2dbf5f75f5c73e6930bcecb8e8772]] +
- +
-<del>05/2015: The SFP port (not populated) periodically claims to go down/up/down. Uncommenting the SFP lines in /etc/config/network avoids this.</del> Fixed in [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=e457d22261b2dbf5f75f5c73e6930bcecb8e8772]] +
- +
-==== Tracking reported experience with suggested patch for the 5 GigE Ports ==== +
- +
-FIXME For reference only. Delete after 31/12/2019  --- //[[tmo26@gmx.de|tmomas]] 2019/04/23 16:04// +
- +
-| user | platform | Unpatched (0x06000000) | 0x3e000000 | [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030217.html| 0x6f000000 ]] | Notes | +
-| [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029833.html| davey ]] | RB951G-2HnD | NOK | OK | not tested | Original [[http://patchwork.ozlabs.org/patch/419857/| patch ]] for mach-rb95x.c | +
-| [[https://lists.openwrt.org/pipermail/openwrt-devel/2015-November/037172.html|baptiste]] | RB951G-2HnD | NOK | NOK | not tested | AR9344 rev 3. Using 0x3e000000 works, but the router crashes every ~10 days. | +
-| [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030230.html| chris ]] | RB2011UiAS-2HnD | NOK | OK | OK | AR9344 rev 2. Davey's patch on mach-rb2011.c. WiFi only tested with unpatched | +
-| [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030216.html| matt ]] | 2011UiAS-2HnD | NOK | NOK | [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030219.html| OK ]] | | +
-| [[https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030300.html| soren ]] | RB2011UiAS-RM | OK | OK | OK | AR9344 rev 2. No WiFi on this model | +
-| toerless | RB2011UiAS-2HnD | NOK | NOK | OK | AR9344 rev 3. WiFi works with all options |  +
-| jbergstroem | RB2011UiAS-2HnD | NOK | NOK | OK | AR9344 rev 3 | +
-| ventYl | RB951G-2HnD | not tested | NOK | OK | Using 0x3e000000 works but reboot crashes each ~10 days or loses ethernet connectivity | +
-| mycoe | RB2011UiAS-2HnD | not tested | NOK | OK | AR9344 rev 3. 74kc |+
  
 [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029838.html|Register layout]] [[https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029838.html|Register layout]]
Line 185: Line 70:
 See [[docs:guide-user:virtualization:metarouter|Metarouter Virtualization on Mikrotik RouterBoard]] See [[docs:guide-user:virtualization:metarouter|Metarouter Virtualization on Mikrotik RouterBoard]]
  
 +===== See also =====
 +
 +* [[:toh:mikrotik:rb2011]]
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>mikrotik}}+{{tag>AR9344 128NAND 128RAM}}
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1