Cannot disable preboot-etherboot after updating to ROS 7.18

RouterOS General
1

Hi,

I updated an ATL from 7.16 to 7.18. In general, everything seems to work as expected except this - (see failure messages below):

[	admin@MikroTik] /system/routerboard/settings> print
              auto-upgrade: no
               boot-device: nand-if-fail-then-ethernet
         preboot-etherboot: 60s
  preboot-etherboot-server: <hidden>
             boot-protocol: bootp
       force-backup-booter: no
               silent-boot: no
      protected-routerboot: disabled
      reformat-hold-button: 20s
  reformat-hold-button-max: 10m
[admin@MikroTik] /system/routerboard/settings> set preboot-etherboot=disabled
failure: not allowed by device-mode
[admin@MikroTik] /system/routerboard/settings> set preboot-etherboot-server=any
failure: not allowed by device-mode
[admin@MikroTik] /system/routerboard/settings> /system/device-mode/print
                 mode: advanced
     allowed-versions: 7.13+,6.49.8+
              flagged: no
     flagging-enabled: yes
            scheduler: yes
                socks: yes
                fetch: yes
                 pptp: yes
                 l2tp: yes
       bandwidth-test: yes
          traffic-gen: no
              sniffer: yes
                ipsec: yes
                romon: yes
                proxy: yes
              hotspot: yes
                  smb: yes
                email: yes
             zerotier: yes
            container: no
  install-any-version: no
           partitions: no
          routerboard: no
        attempt-count: 0
[admin@MikroTik] /system/routerboard/settings>

This has never happened before and I have always been able to change these settings. (FWIW, I have not touched anything in device-mode, just showing that in relation to the message)

Why is this happening and what is the fix?

v7.18.2 [stable] is released!
ATL suddenly says "sim not present"
2

Maybe you have to enable routerboard mode… this is not documented here https://help.mikrotik.com/docs/spaces/ROS/pages/93749258/Device-mode

For me this device mode, is the worst thing in ros, i’have more than 70 devices located accross the country and have to spend time/kilometers to reconfigure them because now i can’t switch easily with parts, or set cpu speed without pressing a fucking button

3

As part of the “we will make your devices secure no matter whether you like it or not” campaign, certain features now have to be explicitly allowed using exactly the “device mode” setting you haven’t touched. So read the manual, check what device mode has to be set to permit the capabilities you need, set that, and then power-cycle the device within some minutes. You are more lucky than a lot of other people as you can do that without flying.

4

Thanks everyone for the quick feedback.

I found that new info in the linked doc right after posting this. You are right - I had to enable routerboard mode and power cycle the device.

Thank you!

5

Change CPU speed sounds not like a recurring task. According to docs you can switch partitions even when device mode feature partitions is enabled.