MikroTik RouterBoard RB2011 series

The RB2011 series consists of different models. The base model has 5 * 1000M + 5 * 100/10M ethernet ports and supports passive PoE input on port 1. Some models then add an SFP port, 802.11b/g/n wireless, USB port and passive PoE on port 10.

Features are encoded in the model name. The format is RB2011x-y-z.

First part describes shared across all releases:

  • A - touchscreen LCD
  • i - passive PoE output on ethernert port 10
  • L - no touchscreen LCD
  • S - SFP port
  • U - USB port

Any combination of these (except A+L) is possible.

The second part, if present, indicates the presence of wireless and contains 2HnD (2.4 GHz dual chain).

The last part, if present, indicates the case type. If not present, the model is a bare PCB (without the metal case):

  • RM - rack mount case
  • IN - indoor (desktop) case

Every model identifies itself to the OpenWrt linux kernel with a different model name (eg: 2011r5 for RB2011-UiAS-2HnD-IN). The OpenWrt kernel only boots when it recognizes the model name.


In general, non-PoE-out models are discontinued by Mikrotik, and some of them (UAS) even removed from the website. However, some sellers might have the stock of those old devices.

See Metarouter Virtualization on Mikrotik RouterBoard

Note: Metarouter requires some patches which seems to be unmaintained for versions past 15.05.

General information

Architecture MIPS 24kc
Vendor MikroTik
Bootloader RouterBOOT
System-On-Chip AR9344 SoC
CPU Speed 600 MHz - can be overclocked in the bootloader menu
Flash size 128 MiB NAND Flash
RAM 128 MiB DDR2
Ethernet AR8327 - 5x 10/100/1000MBit/s BASE-T* + 1x SFP (separate chip)
AR8227 - 5x 10/100MBit/s BASE-T (on SoC)
Wireless none or AR9344 - 802.11b/g/n (depending on the model)
USB none or 1x 2.0 microUSB/USB A (depending on the model)
Serial Cisco pinout RJ45 console port
JTAG yes
LCD none or 2“ color touch display (unsupported, depending on the model)

Per-model details

FIXME This link is dead because of the mailing list failure --- danijeltudek 2021-02-27 19:00 Register layout

AR9344 - Atheros Datasheet

AR8327 - Atheros Datasheet

RGMII registers configuration misc info (SFP port)

FIXME Do we need this? ← Yes, we do, I think.

31 TX_INVERT - Decides whether to select the inversion of the GTX clock after the delay line
30 GIGE_QUAD - Decides whether to allow a 2 ns shift (clock in the middle of a data transfer) to the GTX clock. This bit is only effective when bit 25 is set
29:28 RX_DELAY - The delay buffers in the Rx clock path to adjust against the edge/middle- aligned RGMII inputs
27:26 TX_DELAY - Delay line for the GTX clock that goes along with the data
25 GIGE - Set only after a 1000 Mbps connection has been negotiated
24 OFFSET_PHASE - Used to select if the start is from the positive or negative phase (or whether to have a 180 degree change in addition to the phase-delay in [11:8].
0x6f: 30 29    27 26 25 24
0x3e:    29 28 27 26 25

Network ports & switch configuration

WARNING: Do not use the Luci web configuration page for the switches to alter their configuration! It will misconfigure your switches!

See for reference: https://github.com/openwrt/luci/issues/4325

This bug is present in all 19.07 releases at least since August 1st, 2020 up to at least 19.07.10.

You can use the page to determine which ports have an active link. Be aware that the Luci display differs from the case labels of the box.

Display in Luci and corresponding ports:

Please note that I leave out the default VLAN configuration here, because the Luci VLAN display is incorrect.

switch0 All network ports to the left of the 10 LEDs in the middle
Label in Luci CPU (eth0) LAN 1 LAN 2 LAN 3 LAN 4 SFP WAN
Port number in uci 0 2 3 4 5 6 1
Printed on the box (internal) ETH2 ETH3 ETH4 ETH5 SFP ETH1
switch1 All network ports to the right of the 10 LEDs in the middle
Label in Luci CPU (eth1) LAN 1 LAN 2 LAN 3 LAN 4 LAN 5
Port number in uci 0 5 4 3 2 1
Printed on the box (internal) ETH10 ETH9 ETH8 ETH7 ETH6

Port order as seen physically from left to right on the box and corresponding switch ports:

Box labels 2 LEDs SFP ETH1 ETH2 ETH3  ETH4 ETH5 10 LEDs ETH6  ETH7 ETH8  ETH9  ETH10
switch 0 0  0 0  0 0 upper row: 0 1  1 1  1  1
lower row: 1
Port number in uci 6 1 2 3 4 5 1…5 left 5 4 3 2 1
5…1 right
Label in Luci —  SFP WAN LAN 1 LAN 2 LAN 3 LAN 4 WANLAN 5 left LAN 5 LAN 4 LAN 3 LAN 2 LAN 1
LAN 5 … LAN 1 right
Default configuration USR LED unconfigured (off) switch0: LEDs “automatic”
Power LED always on, unprogrammable switch1: programmed explicitly
VLAN 1 = LAN (proto = static) CPU: 0 tagged on both switches off off untagged untagged untagged untagged br-lan = eth0.1 + eth1.1 untagged untagged untagged untagged untagged
VLAN 2 = WAN & WAN6 (proto = dhcp/v6) CPU: 0 tagged on switch 0 off untagged off off off off eth0.2 off off off off off
VLAN 3 = SFP (proto = none) CPU: 0 tagged on switch 0 untagged off off off off off eth0.3 “standalone” off off off off off

FIXME Make sure yYou can use “openwrt-19.07.10-ar71xx-mikrotik-vmlinux-initramfs.elf” for netboot and not instead of the LZMA file linked above. It wont work. It works at least for 19.07.10 on the RB2011iLS, which I've successfully tested before reading this.

FIXME This should be updated for ath79 once the support is merged.

1. Setup DHCP Server with TFTP Boot (set your PC to static IP of range). Note that the initramfs file should be in the directory indicated by the command.

   sudo dnsmasq -i eth0 --dhcp-range=, \
   --dhcp-boot=openwrt-ar71xx-mikrotik-vmlinux-initramfs.elf \
   --enable-tftp --tftp-root=~/directory/where/file/is/ \
   -d -u $USER -p0 -K --log-dhcp --bootp-dynamic

2. Connect PC to ethernet port 1.

3. Power off router, and hold reset while powering on. Wait 20 seconds until you see PC send file. Release reset, and remain connected to ethernet port until you see Router report Openwrt hostname.

4. Connect PC to a different ethernet port.

5. Logon to OpenWrt netboot

6. Sysupgrade the proper Mikrotik sysupgrade.bin. (it's either 64M or huge. You can get the right one by opening up and reading the part # on the tsop48 ic. But, it shouldn't matter if you flash the wrong one, here.)

If you make a mistake, repeat netboot and try again. There is a UART on the PCB near the power cable, if the netboot works, but the sysupgrade fails for some reason. It's possible you may need the 64M image, but the bootloader will remain so the device is not bricked if the wrong sysupgrade is used.

It can be quicker and easier to load ethernet (tftp) from the bootloader, rather than holding down the reset button upon boot.

If you see ECC errors on the UART (rel. 18 and earlier. Has been fixed in 19.07), refer to this forum post: https://forum.openwrt.org/t/ecc-errors-in-ubi-rb2011uias-2hnd-in-and-solution/16424/15

Users have reported seeing multiple devices corrupt their flash upon the 2nd sysupgrade. When this occurs, the device is only usable in netboot mode. See: https://forum.openwrt.org/t/rb433-bad-sector-cannot-start-openwrt/71519/12

For more details see:

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/05/15 18:29
  • by chf