Introduction
The device-mode is a feature in ROS that sets specific limitations to a device for accessing specific configurations. By default, all devices have a mode: enterprise
...
| Note |
|---|
It is possible that in the future there will be a number of devices that will be set to mode = home at the factory, which means that they will reach users with limited functionality, and then if you want advanced features, you will have to change it yourself. |
Properties
Following properties are available in the system/device-mode/update console path.
...
| Property | Description |
|---|---|
do scheduler without-paging | |
| activation-timeout | |
| flaging-enabled | |
| mode: (home, enterprise; default: enterprise); | Allows choosing from available modes that will limit device functionality. In the future, various modes can be added. By default, enterprise mode allows all options except container. So to use the container feature, you will need to turn it on by performing a device-mode update. By default, home mode excludes the following tags: scheduler, socks, fetch, bandwidth-test, traffic-gen, sniffer, romon, proxy, hotspot, email, zerotier, container. |
Configuration
More specific control over the available features is possible. Each of the features controlled by device-mode can be specifically turned on or off, for example:
...
| Code Block | ||
|---|---|---|
| ||
[admin@MikroTik] > ip hotspot/add interface=ether1 [admin@MikroTik] > ip hotspot/print Flags: X, S - HTTPS Columns: NAME, INTERFACE, PROFILE, IDLE-TIMEOUT # NAME INTERFACE PROFILE IDLE-TIMEOUT ;;; inactivated, not allowed by device-mode 0 X hotspot1 ether1 default 5m |
Flagged notice
The Flag is another important "option". Along with the device-mode feature, ROS has implemented code that analyzes the whole configuration at system startup to determine if there are any signs of unauthorized access. If the following features are detected, the flagged flag is set at device-mode (and the corresponding configuration is disabled):
...