# EVPN Route Attribute Bug Affected FRRouting-Based Tests with Overlapping Leaf AS Numbers

DevFeed: [EVPN Route Attribute Bug Affected FRRouting-Based Tests with Overlapping Leaf AS Numbers](<https://devfeed.tech/articles/dear-vendors-evpn-route-attributes-matter-11197.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/06/evpn-route-attributes-matter/>)

Published: 2025-06-18T05:50:00Z

Content type: article

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>), [bug](<https://devfeed.tech/topics/bug.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [networking](<https://devfeed.tech/topics/networking.md>)

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

## AI overview

The article investigates EVPN routes that were visible in BGP tables but unusable in a lab using overlapping leaf AS numbers. Testing showed that a changed FRRouting release caused the failures across multiple platforms; later FRRouting releases 10.3.2 and 10.4.1 included a fix.

## Source excerpt

Another scary tale from the Archives of Sloppy Code: we can't decide whether some attributes are mandatory or optional. When I was fixing the errors in netlab SR-OS configuration templates, I couldn't get the EBGP-based EVPN with overlapping leaf AS numbers to work. I could see the EVPN routes in the SR-OS BGP table, but the device refused to use them. I concluded (incorrectly) that there must be a quirk in the SR-OS EVPN code and moved on. Read more ...