--- title: One-Arm Hub-and-Spoke VPN on Arista EOS « ipSpace.net blog description: Arista EOS release 4.34.2F introduced a fix that enables one-arm hub-and-spoke MPLS/VPN topologies, which previously failed because EOS uses per-VRF label... canonical: https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: One-Arm Hub-and-Spoke VPN on Arista EOS « ipSpace.net blog | daily.dev og:description: Arista EOS release 4.34.2F introduced a fix that enables one-arm hub-and-spoke MPLS/VPN topologies, which previously failed because EOS uses per-VRF label... og:url: https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x og:image: https://api.daily.dev/og/posts/wXCMVHI1x.png og:image:alt: One-Arm Hub-and-Spoke VPN on Arista EOS « 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. # One-Arm Hub-and-Spoke VPN on Arista EOS « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary Arista EOS release 4.34.2F introduced a fix that enables one-arm hub-and-spoke MPLS/VPN topologies, which previously failed because EOS uses per-VRF label allocation. The new feature allows assigning a separate MPLS label specifically to the default route via a single BGP VRF configuration command: `route-target export vpn-ipv4 label allocation nexthop default-route`. With this change, spoke-to-spoke traffic correctly traverses the hub CE-router rather than being turned around at the hub PE-router, as confirmed by traceroute output before and after the fix. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I make one-arm hub-and-spoke MPLS VPN work on Arista EOS when per-VRF label allocation causes spoke-to-spoke traffic to not reach the hub CE? Arista EOS 4.34.2F added support for assigning a distinct MPLS label to the default route within a VRF, separate from the per-VRF label. Configure it on the hub PE with: `route-target export vpn-ipv4 label allocation nexthop default-route` under the hub VRF in BGP. This causes spoke PE-routers to receive a different label for the default route, directing traffic through the hub CE-router as intended. _Network engineers implementing hub-and-spoke MPLS designs track EOS-specific workarounds like this on daily.dev._ ### What Arista EOS version fixed the per-VRF label allocation limitation for hub-and-spoke MPLS VPN? Arista EOS 4.34.2F introduced the ability to assign a separate MPLS label to the default route within a VRF, even though EOS still uses per-VRF label allocation overall. This resolves the one-arm hub-and-spoke topology limitation where all VRF routes shared the same label, preventing traffic from being correctly forwarded through the hub CE-router. _Staying current on Arista EOS releases that unblock specific network designs is easier when following 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 - [MPLS/VPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/mpls-vpn-with-sr-mpls-core-ipspace-net-blog-nw3uwiphe) · ipSpace.net Blog · 0 upvotes · 0 comments - [Multivendor SR-MPLS « ipSpace.net blog](https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk) · ipSpace.net Blog · 0 upvotes · 0 comments - [BGP-Free Core with SR-MPLS « ipSpace.net blog](https://daily.dev/posts/bgp-free-core-with-sr-mpls-ipspace-net-blog-h7kronzy3) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#vpn](https://daily.dev/tags/vpn), [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x) ```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":"One-Arm Hub-and-Spoke VPN on Arista EOS « ipSpace.net blog","url":"https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x"},"datePublished":"2026-08-11T08:56:00.459Z","dateModified":"2026-08-24T07:00:57.345Z","description":"Arista EOS release 4.34.2F introduced a fix that enables one-arm hub-and-spoke MPLS/VPN topologies, which previously failed because EOS uses per-VRF label...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","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/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"vpn,bgp","timeRequired":"PT3M"} {"@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":"One-Arm Hub-and-Spoke VPN on Arista EOS « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/one-arm-hub-and-spoke-vpn-on-arista-eos-ipspace-net-blog-wxcmvhi1x#faq","mainEntity":[{"@type":"Question","name":"How do I make one-arm hub-and-spoke MPLS VPN work on Arista EOS when per-VRF label allocation causes spoke-to-spoke traffic to not reach the hub CE?","acceptedAnswer":{"@type":"Answer","text":"Arista EOS 4.34.2F added support for assigning a distinct MPLS label to the default route within a VRF, separate from the per-VRF label. Configure it on the hub PE with: `route-target export vpn-ipv4 label allocation nexthop default-route` under the hub VRF in BGP. This causes spoke PE-routers to receive a different label for the default route, directing traffic through the hub CE-router as intended. Network engineers implementing hub-and-spoke MPLS designs track EOS-specific workarounds like this on daily.dev."}},{"@type":"Question","name":"What Arista EOS version fixed the per-VRF label allocation limitation for hub-and-spoke MPLS VPN?","acceptedAnswer":{"@type":"Answer","text":"Arista EOS 4.34.2F introduced the ability to assign a separate MPLS label to the default route within a VRF, even though EOS still uses per-VRF label allocation overall. This resolves the one-arm hub-and-spoke topology limitation where all VRF routes shared the same label, preventing traffic from being correctly forwarded through the hub CE-router. Staying current on Arista EOS releases that unblock specific network designs is easier when following daily.dev."}}]} ```