Manual:RouterBOARD settings: Difference between revisions
Jump to navigation
Jump to search
→Settings: Added auto-upgrade |
|||
| Line 76: | Line 76: | ||
|prop=Property | |prop=Property | ||
|desc=Description | |desc=Description | ||
}} | |||
{{Mr-arg-table | |||
|arg=auto-upgrade | |||
|type= yes {{!}} no | |||
|default=no | |||
|desc=Whether to upgrade firmware automatically after RouterOS upgrade. The latest firmware will be applied after an additional reboot | |||
}} | }} | ||
Revision as of 14:40, 6 June 2019
General
Sub-menu level: /system resource
On RouterBOARD devices, the following menu exists which gives you some basic information about your device:
[admin@demo.mt.lv] /system routerboard> print
routerboard: yes
model: 433
serial-number: 185C01FCA958
current-firmware: 3.25
upgrade-firmware: 3.25
Properties
All properties are read-only
| Property | Description |
|---|---|
| model (string) | If this device is a MikroTik RouterBOARD, this describes the model name |
| serial-number (string) | Serial number of this particular device |
| current-firmware (string) | The version of the RouterBOOT loader that is currently in use. Not to be confused with RouterOS operating system version |
| upgrade-firmware (string) | RouterOS upgrades also include new RouterBOOT version files, but they have to be applied manually. This line shows if a new RouterBOOT file has been found in the device. The file can either be included via a recent RouterOS upgrade, or a FWF file which has been manually uploaded to the router. In either case, the newest found version will be shown here |
Upgrading RouterBOOT
RouterBOOT upgrades usually include minor improvements to overall RouterBOARD operation. It is recommended to keep this version upgraded. If you see that upgrade-firmware value is bigger than current-firmware, you simply need to perform the upgrade command, accept it with y and then reboot with /system reboot
[admin@mikrotik] /system routerboard> upgrade Do you really want to upgrade firmware? [y/n] y echo: system,info,critical Firmware upgraded successfully, please reboot for changes to take effect!
After rebooting, the current-firmware value should become identical with upgrade-firmware
Settings
Sub-menu level: /system routerboard settings
[admin@demo.mt.lv] /system routerboard settings> print
baud-rate: 115200
boot-delay: 2s
enter-setup-on: any-key
boot-device: nand-if-fail-then-ethernet
cpu-frequency: 1200MHz
memory-frequency: 1066DDR
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: no
silent-boot: no
| Property | Description |
|---|---|
| auto-upgrade (yes | no; Default: no) | Whether to upgrade firmware automatically after RouterOS upgrade. The latest firmware will be applied after an additional reboot |
| baud-rate (integer; Default: 115200) | Choose the onboard RS232 speed in bits per second (if installed) |
| boot-delay (time; Default: 1s) | How much time to wait for a key stroke while booting |
| boot-device (nand-if-fail-then-ethernet ...; Default: nand-if-fail-then-ethernet) | Choose the way RouterBOOT loads the operating system:
|
| boot-protocol (bootp |dhcp ...; Default: bootp) | Boot protocol to use:
|
| cpu-frequency (depends on model; Default: depends on model) | This option allows for changing the CPU frequency of the device. Values depend on model, to see available options, hit [?] button on the keyboard at this prompt |
| cpu-mode (power-save | regular; Default: power-save) | Whether to enter CPU suspend mode in HTL instruction. Most OSs use HLT instruction during CPU idle cycle. When CPU is in suspend mode, it consumes less power, but in low-temperature conditions it is recommended to choose regular mode, so that overall system temperature would be higher |
| enable-jumper-reset (yes | no; Default: yes) | Disable this to avoid accidental setting reset via the onboard jumper |
| enter-setup-on (any-key | delete-key; Default: any-key) | Which key will cause the BIOS to enter configuration mode during boot delay. Useful when serial console prints out symbols during boot process and goes into RouterBOOT menu by itself. Note that in some serial terminal programs, it is impossible to use Delete key to enter the setup - in this case it might be possible to do this with the Backspace key |
| force-backup-booter (yes | no; Default: no) | If to use the backup RouterBOOT. This is only useful if the main loader has become corrupted somehow and cannot be fixed. So that you don't have to boot the device with a pushed reset button (which loads backup loader), you can use this setting to load it every time
|
| memory-frequency (depends on model; Default: depends on model) | This option allows to change the memory frequency of the device. Values depend on model, to see available options, hit [?] button on the keyboard at this prompt |
| memory-data-rate (depends on model; Default: depends on model) | This option allows to change the memory data rate of the device. Values depend on model, to see available options, hit [?] button on the keyboard at this prompt |
| regulatory-domain-ce (yes | no; Default: no) | Enables extra low TX power for high antenna gain devices (requires reboot) |
| silent-boot (yes | no; Default: no) | This option disables output on the serial console and beeping sounds during booting, to avoid the text output interrupting a connected device. Useful if you have some temperature monitor or modem connected to the serial port
|
Warning: If CPU or memory is overclocked and that is the reason why router is not performing as suspected, then this is not considered as a warranty case and you should return both frequencies to nominal value..
Protected bootloader
This is a new feature which allows the protection of RouterOS configuration and files from a physical attacker by disabling etherboot. It is called "Protected RouterBOOT". This feature can be enabled and disabled only from within RouterOS after login, i.e., there is no RouterBOOT setting to enable/disable this feature. These extra options appear only under certain conditions. When this setting is enabled - both the reset button and the reset pin-hole is disabled. Console access is also disabled. The only ability to change boot mode or RouterBOOT settings is through RouterOS. If you do not know the RouterOS password - only a complete format is possible.
- The backup RouterBOOT version can not be older than v3.24 version. A special package is provided to upgrade the backup RouterBOOT (DANGEROUS). Newer devices will have this new backup loader already installed at the factory. If your RouterOS is v6.40, use these packages: MIPSBE, SMIPS, MMIPS, TILE. If your RouterOS is v6.43 or higher, use the universal package for all architectures: Universal
- RouterOS version 6.33 or later is required to enable this feature. Also make sure, that you have the latest firmware installed.
| Property | Description |
|---|---|
| protected-routerboot (enabled | disabled; Default: disabled) | This setting disables any access to the RouterBOOT configuration settings over a console cable and disables operation of the reset button to change the boot mode (Netinstall will be disabled). Access to RouterOS will only be possible with a known RouterOS admin password. Unsetting of this option is only possible from RouterOS. If you forget the RouterOS password, the only option is to perform a complete reformat of both NAND and RAM with the following method, but you have to know the reset button hold time in seconds.
|
| reformat-hold-button (5s .. 300s; Default: 20s) | As an emergency recovery option, it is possible to reset everything by pressing the button at power-on for longer than reformat-hold-button time, but less than reformat-hold-button-max (new in RouterBOOT 3.38.3).
When you use the button for a complete reset, following actions are taken: EXTREMELY DANGEROUS. Use this only if you have lost all access to the device.
|
| reformat-hold-button-max (5s .. 600s; Default: 10m) | Increase the security even further by setting the max hold time, this means that you must release the reset button within a specified time interval. If you set t he "reformat-hold-button" to 60s and "reformat-hold-button-max" to 65s, it will mean that you must hold the button 60 to 65 seconds, not less and not more, making guesses impossible. Introduced in RouterBOOT 3.38.3 |
Note: RouterBOARD that has the protected RouterBOOT setting enabled will blink the LED every second, to make counting easier. The LED will turn off for one second, and turn on for the next second.
Mode button
Some RouterBOARD devices have a mode button that allows you to run any script when the button it pushed.
The list of supported devices:
- RBcAPGi-5acD2nD (cAP ac)
- RBwsAP5Hac2nD (wsAP ac lite)
- RB750Gr3 (hEX)
- RB760iGS (hEX S)
- RB912R-2nD (LtAP mini, LtAP mini LTE/4G kit)
- RBD52G-5HacD2HnD (hAP ac^2)
- RBLHGR (LHG LTE/4G kit)
- RBSXTR (SXT LTE/4G kit)
- CRS328-4C-20S-4S+RM
- CRS328-24P-4S+RM
Example
/system script add name=test-script source={:log info message=("1234567890");}
/system routerboard mode-button set on-event=test-script
/system routerboard mode-button set enabled=yes
Upon pressing the button, the message 1234567890 will be logged in the system log.
| Property | Description |
|---|---|
| enabled (no | yes; Default: no) | Disable or enable the operation of the button |
| on-event (string; Default: ) | Name of the script that will be run upon pressing the button. The script must be defined and named in the "/system scripts" menu |