v7.16.2 [stable] is released!

[szalkerous]

tried all ways imaginable - couldn’t get it to work besides downgrading…

revisited the issue - well - before upgrading one has to remove the parameter “vrf-interface” from any static vrf routes that do typically carry routing-table=vrf and vrf-interface=NAME which obviously breaks the routes after v7.16 upgrade.
also dialer-interfaces that enable “add default route” do not add a working default route into its assigned vrf, one has to add a route like:

add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=PPPoE-VRF@vrfO routing-table=vrfO scope=30 suppress-hw-offload=no target-scope=10

it’s a pitty an upgrade breaks the config this way.

I too had my VRF setup break completely moving from 7.15.2 to 7.16.1

Glad these posts were here to give me an idea of where to look.

Sadly not sure where mine is broken since I already had scripts to build the routes for my DHCP “add default route” problems.

I reviewed all the literature at https://help.mikrotik.com/docs/spaces/ROS/pages/328206/Virtual+Routing+and+Forwarding+-+VRF#VirtualRoutingandForwardingVRF-VRFinterfacesinfirewall and compared it to the information at https://wiki.mikrotik.com/Manual:PCC where I originally based my PCC/VRF setup for the two DHCP ISP WANs from. I don’t see where I went wrong in my config.

Looks like this might be the first time I ever downgrade. Very disappointing.