# EVPN Designs: Multi-Pod with IP-Only WAN Routers

DevFeed: [EVPN Designs: Multi-Pod with IP-Only WAN Routers](<https://devfeed.tech/articles/evpn-designs-multi-pod-with-ip-only-wan-routers-11257.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/10/evpn-designs-inter-as-c/>)

Published: 2025-10-15T06:12:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [Containers](<https://devfeed.tech/topics/containers.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [containers](<https://devfeed.tech/tags/containers.md>), [design](<https://devfeed.tech/tags/design.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [linux](<https://devfeed.tech/tags/linux.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>)

## AI overview

This tutorial presents an EVPN/VXLAN Inter-AS Option C design that uses IP-only WAN edge routers. IPv4 EBGP exchanges underlay VTEP next-hop addresses, while a multihop EBGP session between route reflectors carries only EVPN routes, eliminating the need for EVPN support on the WAN edge.

## Source excerpt

In the multi-pod EVPN design, I described a simple way to merge two EVPN fabrics into a single end-to-end fabric. Here are a few highlights of that design: Each fabric is running OSPF and IBGP, with core (spine) devices being route reflectors There's an EBGP session between the WAN edge routers (sometimes called border leaf switches) Every BGP session carries IPv4 (underlay) and EVPN (overlay) routes. In that design, the WAN edge routers have to support EVPN (at least in the control plane) and carry all EVPN routes for both fabrics. Today, we'll change the design to use simpler WAN edge routers that support only IP forwarding. Read more ...