Documentation updates - October 1, 2026
Summary of documentation changes made on October 1, 2026.
Storage
- Tmpfs: Rewritten and tested on RouterOS 7.26. Corrected: tmpfs is part of the base RouterOS package and needs no Storage package (not on SMIPS devices). New sections:
- Create a RAM folder, and what the sizes mean: decimal units, a maximum rather than reserved RAM, about half of the RAM when
tmpfs-max-sizeis not set, and the total size check. - Check what the folder shares: on routers whose default configuration turns on automatic disk sharing (for example the hAP ax²), a new folder is shared through SMB to the
guestuser, who needs no password, and through DLNA. How to check it, and how to create the folder unshared or stop the sharing. - Keep packet captures in RAM and download them, check how full the folder is (a full folder makes writes fail), resize it and delete it.
- Technical details: after a reboot the folder is mounted again empty, and a tmpfs cannot be formatted (use a Ramdisk for a block device).
- The "RAM-backed folder" section of Disks now links here.
- Create a RAM folder, and what the sizes mean: decimal units, a maximum rather than reserved RAM, about half of the RAM when
Firewall & QoS
- Address lists: Rewritten from a single v6-era example into tasks, each imported as written and tested on RouterOS 7.26:
- Block traffic from a list of addresses with a raw rule, for IPv4 and IPv6.
- Allow SSH and WinBox from a dynamic address by its DNS name, with the rule placed before the default drop rule and a warning on what it opens.
- Block hosts that probe a closed port for a day, with a
trustedlist the rule skips, because a single packet with a forged source address is enough to list it. - View, remove, export and import entries.
file=must come beforewhere, or the export prints to the terminal and writes no file. - How entries behave: static and dynamic entries and what a reboot keeps, timeouts (up to
35w3d13h13m56s, reset by each new match), how prefixes and ranges are stored, and how DNS names resolve. - Corrected: a range written in short form such as
203.0.113.1-254is stored as a DNS name and matches nothing, and IPv6 lists take no ranges.
Diagnostics & Monitoring
- Speed Test: Rewritten with tests between two routers and against the router's own bandwidth server.
- Prerequisites: the remote router's bandwidth test server, a user whose group has the
testandwinboxpolicies, device mode, and firewall rules on both routers. Without a rule on the testing router, its firewall drops the UDP download traffic. - New section with tested firewall rules for a test over the internet. To limit who can run tests, use the server's
allowed-addresses4andallowed-addresses6: a user'saddresssetting does not limit bandwidth test logins. - A table explaining the result lines, and the CPU warning explained.
- Troubleshooting for
authentication failed, missing throughput or UDP lines, and device mode. - Technical details: five parts of
test-durationeach (10 seconds by default, at least 5), 20 pings per second, 20 TCP connections, and the ports used. - Corrected the old parameter notes, and removed an unverified rule about routers with more than 20 cores.
- Prerequisites: the remote router's bandwidth test server, a user whose group has the
- Bandwidth test: Now links to Speed Test.
CLI Reference
- /disk, /disk/settings:
tmpfs-max-sizedescribes the units, the default size, the total size check and live resizing. The automatic sharing rows note that the hAP ax² default configuration turns them on. - /ip/firewall/address-list, /ipv6/firewall/address-list: New intros and corrected rows. Only a range that is exactly one prefix is stored as a prefix, an entry with a timeout is dynamic and not saved, and
dynamic=yesand DNS names are explained. - /ip/firewall/raw and the other filter, mangle, raw and NAT tables (IPv4 and IPv6):
address-list-timeoutnow covers a time (reset by each new match),none-dynamic(the same as0s) andnone-static. - /tool/speed-test: All 14 rows described: the ranges and defaults of
connection-countandtest-duration, the policies the test user needs, the status values and the result lines.