Hi all,

I recently tried to make ROS work with two VRFs, which by itself worked fine.
However, I have a problem with the router accessing services within the VRFs.

I have two VRFs, RED and BLUE.
Both RED and BLUE are using the 10.0.0.0/24 subnet.
RED is on interface ether4, BLUE on interface ether5.
Both interfaces are given the IP 10.0.0.1/24.

Now I need to connect to 10.0.0.254 in both VRFs using PPTP.
The only problem being - PPTP client is not VRF-aware. It's not possible to enter the remote address in "10.0.0.254@RED" or "10.0.0.254%ether5" format.
While trying to figure stuff out, I noticed that pretty much nothing (EoIP, IPIP, ...) is VRF-aware in ROS, except for the ping tool.
This is true for both ROS 5.0rc11 and 4.17
Please note that for operational reasons, it is not possible to change the IP 10.0.0.254 in either VRF. That would in theory
allow me to inject /32 routes into the main routing table, pointing to the respective VRF, but still is a kludge.

To get this working, I now had to build a massive kludge involving two metarouters on the Routerboard I am going to use.
Is there another way, or is that simply a feature request to make all services in ROS VRF aware?

Hi all,

I recently tried to make ROS work with two VRFs, which by itself worked fine.
However, I have a problem with the router accessing services within the VRFs.

I have two VRFs, RED and BLUE.
Both RED and BLUE are using the 10.0.0.0/24 subnet.
RED is on interface ether4, BLUE on interface ether5.
Both interfaces are given the IP 10.0.0.1/24.

Now I need to connect to 10.0.0.254 in both VRFs using PPTP.
The only problem being - PPTP client is not VRF-aware. It's not possible to enter the remote address in "10.0.0.254@RED" or "10.0.0.254%ether5" format.
While trying to figure stuff out, I noticed that pretty much nothing (EoIP, IPIP, ...) is VRF-aware in ROS, except for the ping tool.
This is true for both ROS 5.0rc11 and 4.17
Please note that for operational reasons, it is not possible to change the IP 10.0.0.254 in either VRF. That would in theory
allow me to inject /32 routes into the main routing table, pointing to the respective VRF, but still is a kludge.

To get this working, I now had to build a massive kludge involving two metarouters on the Routerboard I am going to use.
Is there another way, or is that simply a feature request to make all services in ROS VRF aware?

Very interesting... Is it possible to run metarouter on x86 platform? Does it consume addition license?

It does not consume an additional license, and i think virtualization is implemented in x86 using KVM. I never tried it though

If you add this to the feature request wiki I will vote for it.

x86 uses KVM to provide virtualization. Metarouter will not be ported to x86. It has very similar configuration options if compared to Metarouter.

Differences are - no hardware can be assigned to guest, guest resides in image, that can be moved to other RouterOS x86 router, with tweaking and license it can be brought to KVM in any linux distribution, RouterOS version can be different from host system (for best results, same version should be used)

and DHCP-server is VRF aware..

and DHCP-server is VRF aware..

Well thanks for pointing that out
Are there any plans of bringing VRF awareness at least the other key services like PPP?

and DHCP-server is VRF aware..

Well thanks for pointing that out
Are there any plans of bringing VRF awareness at least the other key services like PPP?

Yes, we also need vrf-aware for pptp/pppoe!

and DHCP-server is VRF aware..

But not btest...

and DHCP-server is VRF aware..

But not btest...

Do anybody know, how to put pppoe\ppptp dynamic interfaces to vrf, and not to main routing table? Is it possible?