...
Upgrading from v6 to v7 happens exactly the same way, as upgrading within v6 releases. Please follow the the Upgrade manual for more detailed steps. If you are currently running RouterOS version 6 or older, we first suggest upgrading to the latest stable or long-term release in v6 (currently 6.48.6 Long-term or 6.49.5 Stable).
| Info |
|---|
In most RouterOS setups that run fine with the aforementioned v6 versions, no extra steps are required. Upgrading to v7 will automatically convert the configuration and your device will function right away. |
| Info |
|---|
Note: We do not recommend running v7 on hardware that does not have at least 64 MB of RAM. |
Feature list compatibility
...
| Feature | Status |
|---|---|
| CAPsMAN | OK |
| Interfaces | OK |
Wireless | OK |
| Bridge/Switching | OK |
| Tunnels/PPP | OK |
| IPv6 | OK |
BGP | OK, but attention is required * |
| OSPF | OK, but attention is required ** |
| MPLS | OK, but attention is required *** |
Routing filters | OK, but attention required is required **** |
PIM-SM | See notes |
IGMP Proxy | OK |
| Tools | OK |
Queues | OK |
| Firewall | OK |
| HotSpot | OK |
| Static Routing | OK |
| User Manager | See notes |
Notes
| Warning |
|---|
The routing protocol configuration upgrade is triggered only once. This means that if a router was downgraded to ROSv6, the configuration was modified and the router got upgraded back to ROSv7, then the resulting configuration is the one that was present before the downgrade. To re-trigger v6 configuration conversion, load ROSv6 backup with the option |
BGP
Anchor bgp bgp
All known configurations will upgrade from 6.x to 7.x sucessfullysuccessfully. But keep in mind that there is a complete redesign of the configuration. v7 BGP implementation provides with connection, template and session menus.
Template contains all BGP protocol-related configuration options. It can be used as a template for dynamic peers and apply a similar config to a group of peers. Most of the parameters are similar to the previous implementation except that some are grouped in the output and input section making the config more readable and easier to understand whether the option is applied on input or output.
...
All known configurations will upgrade from 6.x to 7.x sucessfullysuccessfully.
OSPFv2 and OSPFv3 are now merged into one single menu /routing ospf. At the moment there ano are no default instances and areaareas. To start OSPF you need to create an instance and then add are area to the instance.
RouterOSv7 uses templates to match the interface against the template and apply configuration from the matched template. OSPF menus interface and neighbor contains read-only entries for status monitoring.
...
Upgrade MPLS setups with caution, and make sure to backup configuration before the upgrade.
Routing filters
Anchor routingfilters routingfilters
All supported options are upgraded without any issue, in the case of an unsupported option - an empty entry is created. The routing filter configuration is changed to a script-like configuration.
...
Multiple rules without action are stacked in a single rule and executed in order like a firewall, the reason is that the "set" parameter order is important, and writing one "set"s per line, allows for an easier understanding from top to bottom on what actions were applied.
More RouterOSv7 routing filter examples are here.
PIM-SM
Anchor pimsm pimsm
Upgrading RouterOS to v7 will not preserve PIM-related configuration. After the upgrade, multicast routing configuration will be available under the /routing/pimsm menu and an additional "multicast" package is not required anymore. More information is available here.
User Manager
Anchor user manager user manager
RouterOSv7 provides with the new and redesigned implementation of User Manager, configuration is now is integrated into RouterOS WinBox and console (WEB admin configuration interface is not available), more information is available here. Direct migration from older User Manager is not possible, it is possible to migrate older database from /user-manager/database/migrate-legacy-db However, it might be a good idea to start configuration for from the scratch.
New features
A New Kernel is implemented in RouterOSv7, that lead which leads to performance changes due to route cache, as well some tasks might require higher CPU and RAM usage for different processes.
- completely new NTP client and server implementation
- merged individual packages, only bundle and a few extra packages remain (dropped support for LCD and KVM packages)
- new Command Line Interface (CLI) style (RouterOS v6 commands are still supported)
- support for Let's Encrypt certificate generation
- support for REST API
- support for UEFI boot mode on x86
- CHR FastPath support for "vmxnet3" and "virtio-net" drivers
- support for "Cake" and "FQ_Codel" type queues
- support for IPv6 NAT
- support for Layer 3 hardware acceleration on all CRS3xx devices
- support for MBIM driver with basic functionality support for all modems with MBIM mode
- support for MLAG on CRS3xx devices
- support for VRRP grouping and connection tracking data synchronization between nodes
- support for Virtual eXtensible Local Area Network (VXLAN)
- support for L2TPv3
- support for OpenVPN UDP transport protocol
- support for WireGuard
- support for hardware offloaded VLAN filtering on RTL8367 (RB4011, RB100AHx4) and MT7621 (hEX, hEX S, RBM33G) switches
- support for ZeroTier on ARM and ARM64 devices
- completely new alternative wireless package "wifiwave2" with 802.11ac Wave2, WPA3, and 802.11w management frame protection support (requires ARM CPU and 256MB RAM)
- support for hardware offloaded VLAN filtering on RTL8367 (RB4011, RB100AHx4) and MT7621 (hEX, hEX S, RBM33G) switches
- support CPU frequency scaling for x86 devices
Dropped support
In RouterOS v7 has been dropped support for:
- LCD package
- KVM package