| Table of Contents |
|---|
Routing Tables
By default, all routes are added to the "main" routing table as it was before. From a configuration point of view, the biggest differences are routing table limit increase, routing table monitoring differences, and how routes are added to specific routing tables (see next example)
v7 introduces a new menu /routing route, which shows all address family routes as well as all filtered routes with all possible route attributes. /ip route and /ipv6 route menus are used to add static routes and for simplicity show only basic route attributes.
...
Another new change is that most common route print requests are processed by the routing process which significantly improves the speed compared to v6.
Use of Routing Tables and Policy Routing
The main difference from v6 is that the routing table must be added to the /routing table menu before actually referencing it anywhere in the configuration. And fib parameter should be specified if the routing table is intended to push routes to the FIB.
The routing rule configuration is the same except for the menu location (instead of /ip route rule, now it is /routing rule).
...
Instead of routing rules, you could use mangle to mark packets with routing-mark, the same way as it was in ROSv6.
OSPF Configuration
OSPFv3 and OSPFv2 are now merged into one single menu /routing ospf. At the time of writing this article, there are no default instances and areas.
To start both OSPFv2 and OSPF v3 instances, first, you need to create an instance for each and then add an area to the instance.
...
| Note |
|---|
The default action of the routing filter chain is "drop" |
BGP Configuration
There is a complete redesign of the BGP configuration compared to ROSv6. The first biggest difference is that there is no more instance and peer configuration menus. Instead, we have connection, template and session menus.
The reason for such a structure is to strictly split parameters that are responsible for connection and parameters that are BGP protocol specific.
...
| Note |
|---|
In v7 it is not possible to turn off synchronization with IGP routes (the network will be advertised only if the corresponding IGP route is present in the routing table). |
Routing Filters
Starting from ROSv7.1beta4, the routing filter configuration is changed to a script-like configuration. The rule now can have "if .. then" syntax to set parameters or apply actions based on conditions from the "if" statement.
...
| Code Block | ||
|---|---|---|
| ||
/routing/filter/rule add chain=bgp_in rule="set bgp-ext-communities rt:327824:20 " |
RPKI
RouterOS implements an RTR client. You connect to the server which will send route validity information. This information then can be used to validate routes in route filters against a group with "rpki-validate" and further in filters "match-rpki" can be used to match the exact state.
For more info refer to the RPKI documentation.
RIP Configuration
To start RIP, the instance should be configured. There you should select which routes will be redistributed by RIP and if it will redistribute the default route.
...