Internet Access From Vrf--Mikrotik

Packages required: routing-test, mpls-test, RouterOS version 3.23+

There are multiple ways how Internet access could last provided to VRF clients. They are outlined inward RFC 4364 department 11, for example.
Here nosotros demonstrate the agency how to configure access using global routing table.

Example 

Default routes

Add default routes to VRF routing tables on PE:

 /ip road add together routing-mark=cust-one gateway=10.0.0.1@main  /ip road add together routing-mark=cust-two gateway=10.0.0.1@main 

Note that nosotros must explicitly specify that the gateway should last resolved inward the @main routing table, otherwise the routes volition non larn active.

Routes to client's networks

Routes to client's networks should last added inward the principal routing table, acre their nexthops should last reachable via client's VRF interfaces, as well as every 2nd such belong to the VRF tables.
On the other hand, at that topographic point is no agency how to explicitly specify that gateway must last resolved inward whatever other table, except the principal table. So instead nosotros specify the interface (which is inward a VRF) as well as nexthop gateway address (which must last straight reachable on that interface). For point-to-point interfaces fifty-fifty the gateway address is non required.
Add these routes to PE's road tabular array as well as redistribute them via OSPF:

 /ip road add together dst-address=10.7.7.0/24 gateway=10.3.3.4%ether2  /ip road add together dst-address=10.8.8.0/24 gateway=10.4.4.5%ether3 

And this is how should await inward print:

 [admin@PE2] > /ip road impress exceptional where !routing-mark   ...   five Influenza A virus subtype H5N1 south  dst-address=10.7.7.0/24 gateway=10.3.3.4 on cust-one reachable ether2       distance=1 scope=30 target-scope=10       six Influenza A virus subtype H5N1 south  dst-address=10.8.8.0/24 gateway=10.4.4.5 on cust-two reachable ether3        distance=1 scope=30 target-scope=10