It requires knowledge of the match and action statements as well as how to write an expression to correctly parse them. Network CLI – The single biggest resistance to the new style of filtering is the string format is hard to work with. # MikroTik RouterOS 6.48.10 (long-term) #Īdd action=accept chain=dead.beef.101 prefix=200:dead:beef:101::/64Īdd action=accept chain=dead.beef.102 prefix=200:dead:beef:102::/64Īdd action=accept chain= prefix=200:dead:beef::/48Īdd action=accept chain=bgp-out-v6 match-chain=dead.beef.101 set-bgp-local-pref=300Īdd action=accept chain=bgp-out-v6 match-chain=dead.beef.102Īdd action=accept chain=bgp-out-v6 match-chain= prefix-length=48-128 set-bgp-local-pref=150 Here is an example of the latest syntax in ROSv7.1rc1Īdd chain=dead.beef.101 rule="if (dst=200:dead:beef:101::/64) "Īnd the corresponding routes received (for the v7 filter rules)Ĭomparable syntax in ROSv6 (note: recursive routing is not supported in IPv6 so the iBGP routes used to test v7rc1 would not be possible) I did a lot of work and testing using ROS 7.1beta7 which never made it to public release and was close to publishing the results when 7.1rc1 came out so this post will use that version. MikroTik then made some changes and opened up discussion to get feedback. MikroTik RouterOS – v7.0.3 stable (chateau) and status of general release MikroTik – RouterOSv7 first look – Dynamic routing with IPv6 and OSPFv3/BGP The first implementation of routing filters in ROSv7 was difficult to work with and documented in the two articles below: Routing filters have been a hot topic lately in the world of RouterOSv7.
0 kommentar(er)
