<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z" -->

---
title: Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics «...
description: A deep dive into Layer-3 WAN handoff (L3Out) options for VXLAN/EVPN fabrics across multiple locations, based on input from Cisco's Lukas Krattiger. Three main...
canonical: https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics « ipSpace.net blog | daily.dev
og:description: A deep dive into Layer-3 WAN handoff (L3Out) options for VXLAN/EVPN fabrics across multiple locations, based on input from Cisco's Lukas Krattiger. Three main...
og:url: https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z
og:image: https://api.daily.dev/og/posts/CuYNRc09z.png
og:image:alt: Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics « ipSpace.net blog
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics « ipSpace.net blog

**[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments

## Summary

A deep dive into Layer-3 WAN handoff (L3Out) options for VXLAN/EVPN fabrics across multiple locations, based on input from Cisco's Lukas Krattiger. Three main approaches are covered: VXLAN-to-IP (Inter-AS Option A with per-VRF eBGP), VXLAN-to-VXLAN using a Multi-Site Border Gateway (BGW) that handles EVPN re-origination and RMAC community rewriting, and VXLAN-to-MPLS/SR/SRv6 using L3VPN (VPNv4/VPNv6). The post explains why simply changing the BGP next hop is insufficient for VXLAN-to-VXLAN — the RMAC extended community must also be updated. A follow-up covering Arista's approach is referenced.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.ipspace.net/2023/09/evpn-wan-handoff-l3out>

## Questions this post answers

### Why is changing the BGP next hop not enough for VXLAN-to-VXLAN routing between EVPN sites?

EVPN routes carry an RMAC extended community that encodes the inner destination MAC address used for VXLAN encapsulation. When a border node re-originates a route toward a remote domain, it must update both the BGP next hop and the RMAC to point to itself — not just the next hop. A Multi-Site Border Gateway (BGW) performs this EVPN re-origination correctly; plain VXLAN RIOT on the data plane alone is insufficient.

_Engineers stitching EVPN domains together track exactly these re-origination details on daily.dev._

### What are the three options for L3 WAN handoff in a VXLAN/EVPN fabric?

The three options are: (1) VXLAN-to-IP using Inter-AS Option A, where IP prefixes are imported into per-VRF sub-interfaces with eBGP peering toward the WAN; (2) VXLAN-to-VXLAN using a Multi-Site Border Gateway that performs EVPN re-origination including RMAC rewriting; and (3) VXLAN-to-MPLS/SR/SRv6 using L3VPN (VPNv4/VPNv6) with LDP, SR, or BGP-LU as the underlay.

_Network architects choosing between these handoff models find peer discussions and vendor updates on daily.dev._

## Similar posts on daily.dev

- [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments

---

Tags: [#bgp](https://daily.dev/tags/bgp), [#evpn](https://daily.dev/tags/evpn), [#networking](https://daily.dev/tags/networking)

[View this post on daily.dev](https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics « ipSpace.net blog","url":"https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z"},"datePublished":"2026-08-11T08:54:49.648Z","dateModified":"2026-10-14T02:29:46.306Z","description":"A deep dive into Layer-3 WAN handoff (L3Out) options for VXLAN/EVPN fabrics across multiple locations, based on input from Cisco's Lukas Krattiger. Three main...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp,evpn,networking","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Layer-3 WAN Handoff (L3Out) in VXLAN/EVPN Fabrics « ipSpace.net blog"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/layer-3-wan-handoff-l3out-in-vxlan-evpn-fabrics-ipspace-net-blog-cuynrc09z#faq","mainEntity":[{"@type":"Question","name":"Why is changing the BGP next hop not enough for VXLAN-to-VXLAN routing between EVPN sites?","acceptedAnswer":{"@type":"Answer","text":"EVPN routes carry an RMAC extended community that encodes the inner destination MAC address used for VXLAN encapsulation. When a border node re-originates a route toward a remote domain, it must update both the BGP next hop and the RMAC to point to itself — not just the next hop. A Multi-Site Border Gateway (BGW) performs this EVPN re-origination correctly; plain VXLAN RIOT on the data plane alone is insufficient. Engineers stitching EVPN domains together track exactly these re-origination details on daily.dev."}},{"@type":"Question","name":"What are the three options for L3 WAN handoff in a VXLAN/EVPN fabric?","acceptedAnswer":{"@type":"Answer","text":"The three options are: (1) VXLAN-to-IP using Inter-AS Option A, where IP prefixes are imported into per-VRF sub-interfaces with eBGP peering toward the WAN; (2) VXLAN-to-VXLAN using a Multi-Site Border Gateway that performs EVPN re-origination including RMAC rewriting; and (3) VXLAN-to-MPLS/SR/SRv6 using L3VPN (VPNv4/VPNv6) with LDP, SR, or BGP-LU as the underlay. Network architects choosing between these handoff models find peer discussions and vendor updates on daily.dev."}}]}
```

