Add support for MikroTik RB5009UG

adron · 2022-02-12T10:43:49.936Z

I haven't checked this yet.

Borromini · 2022-02-12T22:49:23.773Z

@adron Does one need to be on the 7.2 RC1 or is any RouterOS OK? I see you circling the 7.2 RC1 in your video, but the RC's are at RC3 now. MikroTik offers 7.2 RC3 but by modifying the link from RC3 to RC1 I seem to be able to pull in RC1.

Your GitHub README says RC1 as well (just to make clear I didn't skip that).

adron · 2022-02-13T03:22:44.805Z

The device can have any version of bootloader - when the specified commands are executed, it will be replaced with the appropriate one - 7.2RC1.

LightArrow123 · 2022-02-13T04:04:19.211Z

I was following your commands on github to try it out and I get the following error on mine.

/system/routerboard/settings/set boot-device=ethernet
input does not match any value of boot-device

Mind you I am new to mikrotik. Also what port is tftp used on?

Borromini · 2022-02-13T10:09:47.980Z

LightArrow123:

Mind you I am new to mikrotik. Also what port is tftp used on?

TFTP server should listen on port 69, standard port.

noodles · 2022-02-13T10:10:03.690Z

You want set boot-device=try-ethernet-once-then-nand and port 1 should be connected to your TFTP server.

Borromini · 2022-02-13T13:54:27.274Z

Is there a way to load OpenWrt onto the device without needing to solder? I have a CH341a programmer, so I can get by dumping and overwriting the flash. And I'm seeing RX/TX/GND/3.3V pins, two on each side of the board.

Already dumping the flash as we speak.

Also, is there a fixed TFTP server address RouterBOOT expects or should I pre-set that in RouterOS first? Since I haven't got serial I'd be going a bit blind here .

sumo · 2022-02-13T15:31:31.651Z

Borromini:

I haven't got serial I'd be going a bit blind here .

Serial won't really help you through the process as MikroTik completely disabled that on the RB5009UG if I'm not mistaken. The only thing one may do via serial is UART boot should it get completely bricked.

Borromini · 2022-02-13T16:23:23.018Z

OK. How would one get the console then that adron's video is showing? From 0:16 he has Minicom open showing the boot loader. I'm a bit puzzled about that, can't find anything in the thread about that.

adron · 2022-02-13T16:29:18.274Z

In my patched version of RouberBOOT the UART is works. The patch make necessary fixes for this.

#fix the UART
binay_patch 0x0144 "20 00 80 52  20 0c 01 b9  c0 03 5f d6"
binay_patch 0xB348 "1f 20 03 d5"

But you absolutely do not need UART to flash my OpenWrt assembly. Just follow the instructions and you'll be fine.

Borromini · 2022-02-13T16:34:36.702Z

@adron Thanks! Is there a specific IP the TFTP server should be listening on? And should the ramdisk be named specifically? Or will RouterBOOT just take whatever it gets fed from wherever as long as it's in the same range as its own IP default?

Apologies for the questions, but I'm used to using a specific IP and file name when setting up a TFTP server with e.g. TP-Link and the likes...

sumo · 2022-02-13T17:25:59.934Z

Borromini:

Is there a specific IP the TFTP server should be listening on?

Not being much of a router OS guy myself I also had to look that up. By default it is on 192.168.88.1 with user admin no password. Just SSH into it. And yeah, while you need the 2.5 GbE LAN1 for the later BOOTP, initially you need to use any of the other ports being LAN as that port 1 defaults to WAN.

Borromini:

And should the ramdisk be named specifically?

Well, it does BOOTP so you do tell it what to further do.

Borromini:

Or will RouterBOOT just take whatever it gets fed from wherever as long as it's in the same range as its own IP default?

No, it really just does BOOTP which is the ancient predecessor of DHCP. So whatever your BOOTP server configured for it.

Borromini · 2022-02-13T17:33:38.305Z

Thanks - gonna look into BOOTP then.

noodles · 2022-02-13T17:57:50.523Z

In case it helps I ended up with the following, which will send the rb5009-jailbreak.elf file. The machine it runs on is 198.168.100.1 on the local interface. Replace "-u username" with your username, put the file in /tftpboot/.

dnsmasq --bind-interfaces -i eth1 \
        -a 192.168.100.1 --dhcp-range=192.168.100.100,192.168.100.200 \
        --dhcp-authoritative \
        --dhcp-boot=rb5009-jailbreak.elf \
        --enable-tftp --tftp-root=/tftpboot/ \
        -d -u username -p0 -K --log-dhcp --bootp-dynamic

Borromini · 2022-02-13T19:15:38.055Z

I guess it goes to show I'm completely unfamiliar with RouterBOOT/OS Thank you! Will give that a shot. From the look of it just my usual TFTP server won't cut it.

Borromini · 2022-02-13T21:09:41.905Z

OK, so it looks like the ELF image gets uploaded, but after that it goes silent. I have no idea what's going on here.

Set client IP to 192.168.88.10 so I can SSH into 192.168.88.1, and set boot from network. Tell RouterOS to reboot.
Plug cable into the 2,5G port and switch IP to 192.68.1.1
Activate DHCP server: sudo dnsmasq --bind-interfaces -i eth0 -a 192.168.1.1 --dhcp-range=192.168.1.100,192.168.1.200 --dhcp-authoritative --dhcp-boot=openwrt-mvebu-cortexa72-mikrotik_rb5009-initramfs-fit-uImage.elf --enable-tftp --tftp-root=/srv/tftp/ -d -u <user> -p0 -K --log-dhcp --bootp-dynamic

I see the ELF image gets uploaded, but after that the router goes silent.

dnsmasq: started, version 2.85 DNS disabled
dnsmasq: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, IP range 192.168.1.100 -- 192.168.1.200, lease time 1h
dnsmasq-dhcp: DHCP, sockets bound exclusively to interface eth0
dnsmasq-tftp: TFTP root is /srv/tftp/  
dnsmasq-dhcp: 508793544 available DHCP range: 192.168.1.100 -- 192.168.1.200
dnsmasq-dhcp: 508793544 vendor class: ARM64__boot
dnsmasq-dhcp: 508793544 tags: bootp, eth0
dnsmasq-dhcp: 508793544 BOOTP(eth0) 192.168.1.163 xx:xx:xx:xx:xx:xx 
dnsmasq-dhcp: 508793544 bootfile name: openwrt-mvebu-cortexa72-mikrotik_rb5009-initramfs-fit-uImage.elf
dnsmasq-dhcp: 508793544 next server: 192.168.1.1
dnsmasq-dhcp: 508793544 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 508793544 sent size:  4 option: 28 broadcast  192.168.1.255
dnsmasq-dhcp: 508793544 sent size:  4 option:  3 router  192.168.1.1
dnsmasq-tftp: sent /srv/tftp/openwrt-mvebu-cortexa72-mikrotik_rb5009-initramfs-fit-uImage.elf to 192.168.1.163

After that switching to a 'LAN' port (port 2, port 8 e.g.) doesn't do anything, not a DHCP IP, static IP in the default OpenWrt range doesn't connect either.

I'm going to give the jailbreak a shot .

sumo · 2022-02-13T22:57:44.727Z

Borromini:

I see the ELF image gets uploaded, but after that the router goes silent.

For me that actually booted into OpenWrt and even showed boot messages via UART. It then defaults to regular 192.168.1.1 LAN on p2 to p8. But so far WAN did not come up. Will try to continue installation from a USB memory stick. Let's see...

Borromini · 2022-02-13T23:20:46.056Z

Might be my desktop playing up. Will give the laptop a shot tomorrow.

sumo · 2022-02-13T23:23:43.068Z

Yep, that worked:

mount /dev/sda1 /mnt
cat /mnt/rbt-with-aux-for-mtd5.bin | mtd write - RouterBOOT
echo cfg > /sys/firmware/mikrotik/soft_config/boot_device
echo 1 > /sys/firmware/mikrotik/soft_config/commit
cp /mnt/openwrt-mvebu-cortexa72-mikrotik_rb5009-squashfs-sysupgrade.bin /tmp/fw.bin
sysupgrade /tmp/fw.bin

However, still no reaction from WAN. While LAN on p2 works fine WAN on p1 (the 2.5 GbE one) seems dead:

root@OpenWrt:/# ethtool p1
Settings for p1:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                1000baseX/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                1000baseX/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Auto-negotiation: on
        master-slave cfg: preferred slave
        master-slave status: unknown
        Port: MII
        PHYAD: 0
        Transceiver: external
        Supports Wake-on: d
        Wake-on: d
        Link detected: no
root@OpenWrt:/# ethtool p2
Settings for p2:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 7
        Transceiver: external
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

So the 2.5 GbE port does not seem to advertise 2.5 GbE and also does not react on anything being plugged in.

Curious how the SFP+ behaves... There you go:

root@OpenWrt:/# ethtool -m sfp
        Identifier                                : 0x03 (SFP)
        Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)
        Connector                                 : 0x21 (Copper pigtail)
        Transceiver codes                         : 0x10 0x00 0x00 0x00 0x40 0x40 0x04 0x00 0x00
        Transceiver type                          : 10G Ethernet: 10G Base-SR
        Transceiver type                          : FC: short distance (S)
        Transceiver type                          : FC: Shortwave laser w/o OFC (SN)
        Transceiver type                          : FC: Multimode, 50um (M5)
        Encoding                                  : 0x06 (64B/66B)
        BR, Nominal                               : 10300MBd
        Rate identifier                           : 0x00 (unspecified)
        Length (SMF,km)                           : 0km
        Length (SMF)                              : 0m
        Length (50um)                             : 300m
        Length (62.5um)                           : 300m
        Length (Copper)                           : 0m
        Length (OM3)                              : 300m
        Laser wavelength                          : 850nm
        Vendor name                               : OEM
        Vendor OUI                                : 00:1b:21
        Vendor PN                                 : SFP-10G-T
        Vendor rev                                : A0
        Option values                             : 0x00 0x1a
        Option                                    : RX_LOS implemented
        Option                                    : TX_FAULT implemented
        Option                                    : TX_DISABLE implemented
        BR margin, max                            : 0%
        BR margin, min                            : 0%
        Vendor SN                                 : 2104060324
        Date code                                 : 210331
root@OpenWrt:/# ethtool sfp
Settings for sfp:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
                                2500baseX/Full
                                10000baseKR/Full
                                1000baseX/Full
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseLRM/Full
                                10000baseER/Full
                                2500baseT/Full
                                5000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
                                2500baseX/Full
                                10000baseKR/Full
                                1000baseX/Full
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseLRM/Full
                                10000baseER/Full
                                2500baseT/Full
                                5000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Auto-negotiation: on
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

So while it recognizes my 10GBASE-T transceiver, which means I2C is working, no further reaction so far. Okay, after another re-boot with the SFP+ already plugged in it looks slightly different:

root@OpenWrt:/# ethtool sfp
Settings for sfp:
        Supported ports: [  ]
        Supported link modes:   10000baseSR/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10000baseSR/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Auto-negotiation: on
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

However, still no link or anything. But for a first try, quite amazing! Thanks, @adron!

adron · 2022-02-14T03:24:29.270Z

This is strange, because my WAN(p1) works fine on 1 gigabit. I don't have a 2.5 gigabit switch yet.

ethtool port1
Settings for port1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
                                1000baseX/Full 
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
                                1000baseX/Full 
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                             100baseT/Half 100baseT/Full 
                                             1000baseT/Full 
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

In general, its first port is strange, even in RouterOS it does not work with all the switches that I tried! - the link rises and immediately falls, and so on in a circle.