BGP EVPN Type-5 Roadmap: IP Route Import/Export, VRF Integration and VPNv4 Interworking

Hi MikroTik team,

I would like to ask about the current development status and future roadmap for BGP EVPN Type-5 (IP Prefix Routes) support in RouterOS v7, particularly regarding route installation, local prefix advertisement, and integration with the existing VPNv4/VRF implementation.

We are evaluating MikroTik routers for integration into an existing multi-vendor ISP network using BGP EVPN/VXLAN for Layer 3 VPN services.

CURRENT BEHAVIOR

We have tested RouterOS 7.25 stable and the latest 7.26 beta releases.

Our observations are:

1. RouterOS successfully receives BGP EVPN Type-5 IP Prefix Routes from remote BGP peers.

2. These routes are visible through:

/routing/route/print where afi=evpn

3. However, the received IP prefixes are not imported into the main IPv4 routing table or into any locally configured VRF routing table.

4. Consequently, these prefixes cannot currently be used for normal IP forwarding through the corresponding routing tables.

This behavior has been consistently reproduced in our tests.

DESIRED FUNCTIONALITY

We are particularly interested in three capabilities:

1. EVPN TYPE-5 ROUTE IMPORT

Allow RouterOS to import received BGP EVPN Type-5 prefixes into the appropriate local IP routing table.

Ideally, the destination could be:

- The main routing table.

- A specific local VRF routing table.

Route Target (RT) matching and VRF configuration should determine which routes are imported.

2. EVPN TYPE-5 ROUTE EXPORT

Allow RouterOS to originate and advertise its own IP prefixes through the BGP EVPN address family as Type-5 routes.

These prefixes could originate from:

- Connected routes.

- Static routes.

- Routes learned through other routing protocols.

- Routes belonging to a specific local VRF.

The objective is to provide bidirectional IP prefix exchange between RouterOS and other EVPN-capable routers.

3. INTEGRATION WITH THE EXISTING VPNv4/VRF IMPLEMENTATION

RouterOS already provides VPNv4 functionality through:

/routing/bgp/vpn

This implementation supports importing and exporting IP prefixes associated with VRFs, using Route Distinguishers and Route Targets.

We would particularly like to know whether the existing VPNv4/VRF route import/export mechanisms could be reused or extended to support EVPN Type-5.

For example:

- Import EVPN Type-5 prefixes into an existing VRF routing table.

- Export prefixes from that VRF as EVPN Type-5 routes.

- Reuse existing RD/RT-based route selection and import/export logic.

- Support interoperability or route redistribution between VPNv4 and EVPN Type-5 where appropriate.

We understand that VPNv4 and EVPN are different BGP address families, with different forwarding and encapsulation requirements.

We are not suggesting that they are directly interchangeable.

Instead, we are interested in whether RouterOS could provide common VRF route management and, potentially, controlled interworking between these address families.

This would allow existing VRF routing functionality to be reused while distributing IP prefixes through BGP EVPN and using VXLAN as the corresponding data-plane encapsulation.

QUESTIONS FOR THE DEVELOPMENT TEAM

1. Is importing received EVPN Type-5 IP prefixes into the main routing table or a local VRF currently planned?

2. Is originating and advertising locally available IP prefixes as EVPN Type-5 routes on the development roadmap?

3. Are there plans to integrate EVPN Type-5 with the existing /routing/bgp/vpn and VRF import/export mechanisms?

4. Could RouterOS eventually support controlled route exchange between VPNv4 and EVPN Type-5, using common VRF routing tables and Route Targets?

5. Will EVPN Type-5 support require a complete L3VNI/VXLAN configuration, or could the control-plane route import/export functionality be implemented independently?

6. Is there any estimated RouterOS release, development milestone, or roadmap information available for these features?

Our primary interest is complete bidirectional Layer 3 route exchange using BGP EVPN Type-5, with proper integration into RouterOS routing tables and VRFs.

This would be especially useful for ISP networks where MikroTik routers need to interoperate with existing EVPN/VXLAN infrastructures from other vendors.

We would appreciate any clarification from the MikroTik development team regarding the intended functionality and development roadmap.

We can provide additional configuration details and testing results if needed.

Thanks in advance.

Hello, im not affiliated in any way, shape or form with Mikrotik, but you can do feature requests via their jira ticketing system (Log into Atlassian - Support).

image

For the questions you have for them, asking them here; while probably being your best bet, theres still a chance you might not get an answer from them, they do read the forums from time to time, but not all the time.

You could however send them a "technical support question" via the ticketing system too, and that would kind-of-sort-of guarantee you an answer (it just might take some time).

image

So take that with a grain of salt, wish you best of luck :slight_smile:

Hi @drotz,

Thanks for the suggestion!

I've followed your advice and submitted an official feature request through the MikroTik support portal.

Ticket: SUP-227175

The request covers bidirectional BGP EVPN Type-5 route import/export, installation into main/VRF routing tables, and potential integration with the existing VPNv4/VRF mechanisms.

Hopefully, the MikroTik development team can provide some insight into their roadmap for these features.

I'll share any relevant updates here so others interested in EVPN Type-5 support can follow the progress.

Thanks again!

Hi everyone,

Just a quick update after contacting MikroTik support through an official feature request (SUP-227175).

MikroTik support has confirmed that:

- EVPN Type-5 routes are currently recognized by RouterOS, but actual route import/export is not yet implemented.

- EVPN Type-5 import/export is on their TODO list.

- Regarding the future implementation, support indicated that reusing the existing BGP VPN functionality would most likely be the approach, although this was explicitly described as an educated guess rather than a confirmed development decision.

- There is currently no estimated release date.

This is encouraging, particularly regarding the possibility of integrating EVPN Type-5 with the existing BGP VPN/VRF infrastructure.

However, the final configuration model, VRF integration details, and forwarding requirements remain to be confirmed.

I'll update this thread if further information becomes available or if future RouterOS releases introduce relevant changes.

Thanks again to @drotz for suggesting the official feature request channel!