...
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.
Routing The routing rule configuration is the same except for the menu location (instead of /ip route rule, now it is /routing rule).
...
OSPF Configuration
OSPFv3 and OSPFv2 is 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.
...
At this point, you are ready to start OSPF on the network interface. In the case of IPv6, you add either interface on which you want to run OSPF (the same as ROSv6) or the IPv6 network. In the second case, OSPF will automatically detect the interface. Here are some interface configuration examples:
...
All route distribution control is now done purely with routing filter select, no more redistribution knobs in the instance (Since the v7.1beta7 redistribution knob is back, but you still need to use routing filters to set route costs and type if necessary). This gives greater flexibility on what routes from which protocols you want to redistribute.
For example, let's say you want to redistribute only static IPv4 routes from the 192.168.0.0/16 network range.
...
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 |
|---|
Starting from v7.1beta4 template parameters are exposed in the "connection" configuration. This means that the template is not mandatory anymore, allowing for an easier basic BGP connection setup, similar as to what it was in ROSv6. |
Most of the parameters are similar to ROSv6 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. If you are familiar with CapsMan then the syntax is the same, for example, to specify the output selection chain you set output.filter-chain=myBgpChain.
...
Very interesting parameters are input.affinity andoutput.affinity, they allow to control in which process input and output of active session will be processed:
- alone - input and output of each session is are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers
- afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters
- main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores)
- input - run output in the same process as input (can be set only for output affinity)
...
Peer role is now a mandatory parameter, for basic setups, you can just use ibgp, ebgp (more information on available roles can be found in the corresponding RFC draft https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-open-policy/?include_text=1), keep in mind that at the moment capabilities, communities, and filtering described in the draft is not implemented.
...
Now input.accept-* allows filter filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix prefixes which means that it will still eat memory and will be visible in /routing route table as "not active, filtered",
...
Lastly, you might notice that the network menu is missing and probably wondering how to advertise your own networks. Now networks are added to the firewall address-list and referenced in the BGP configuration.
Following ROSv6 network configuration:
...
| 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). |
...
| Code Block | ||
|---|---|---|
| ||
/routing/filter/rule
add chain=ospf_in rule="if (dst in 172.16.0.0/16 && dst-len==24 && protocol static) { accept }" |
Another example, to match prefixes from the 172.16.0.0/16 range with prefix length equal to 24 and set BGP med and prepend values
...
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.
[admin@MikroTik] > routing/rip/instance/add name=instance1 originate-default=never redistribute=connected,static
...
[admin@MikroTik] > routing/rip/interface-template/add interfaces=ether1 instance=instance1
Now the basic configuration is completed on one router. RIP neighbor router should be configured in a similar way. In ROS v7 the neighbors will appear only when there are routes to be sent or/and to be received.