--- title: BGP Route Server in an Internet Exchange Point « BGP Labs description: A hands-on BGP lab exercise covering how to configure a BGP route server at an Internet Exchange Point (IXP). The lab demonstrates the problem of IXP AS... canonical: https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: BGP Route Server in an Internet Exchange Point « BGP Labs | daily.dev og:description: A hands-on BGP lab exercise covering how to configure a BGP route server at an Internet Exchange Point (IXP). The lab demonstrates the problem of IXP AS... og:url: https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp og:image: https://api.daily.dev/og/posts/HnoaCznrP.png og:image:alt: BGP Route Server in an Internet Exchange Point « BGP Labs 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. # BGP Route Server in an Internet Exchange Point « BGP Labs **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 6 min read · 0 upvotes · 0 comments ## Summary A hands-on BGP lab exercise covering how to configure a BGP route server at an Internet Exchange Point (IXP). The lab demonstrates the problem of IXP AS numbers appearing in AS paths when ISPs peer through a shared BGP daemon, then walks through the solution: configuring neighbors as route-server-clients on the RS router and disabling the enforce-first-as check on ISP routers. Includes topology details, configuration commands, and verification steps using netlab validate with Arista EOS or FRRouting. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does the AS path include the IXP AS number when peering through an internet exchange point route server? Without route server configuration, a standard BGP daemon at an IXP prepends its own AS number to all updates it forwards, so ISP peers see the IXP AS in the path even though traffic never traverses it. Configuring neighbors as route-server-clients (per RFC 7947) makes the BGP daemon forward updates with the original AS path unmodified, hiding the IXP AS entirely. _Engineers building IXP peering setups track BGP edge cases like this on daily.dev._ ### How do I fix 'first AS check' failures when peering with a BGP route server? A BGP route server omits its own AS from the AS path, so the first AS in received updates is the originating peer's AS, not the route server's AS. Most BGP implementations reject this by default. Disable the check with a command like 'no neighbor enforce-first-as' on each ISP router's session toward the route server to accept these updates. _Networking engineers troubleshooting BGP session issues find relevant discussions on daily.dev._ ## Similar posts on daily.dev - [How far can you go with IX Route Servers only?](https://daily.dev/posts/how-far-can-you-go-with-ix-route-servers-only--pzqn4hqop) · Benjojo's 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: [#networking](https://daily.dev/tags/networking), [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp) ```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":"BGP Route Server in an Internet Exchange Point « BGP Labs","url":"https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp"},"datePublished":"2026-08-11T08:51:46.561Z","dateModified":"2026-08-11T08:52:53.633Z","description":"A hands-on BGP lab exercise covering how to configure a BGP route server at an Internet Exchange Point (IXP). The lab demonstrates the problem of IXP AS...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","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/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking,bgp","timeRequired":"PT6M"} {"@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":"BGP Route Server in an Internet Exchange Point « BGP Labs"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/bgp-route-server-in-an-internet-exchange-point-bgp-labs-hnoacznrp#faq","mainEntity":[{"@type":"Question","name":"Why does the AS path include the IXP AS number when peering through an internet exchange point route server?","acceptedAnswer":{"@type":"Answer","text":"Without route server configuration, a standard BGP daemon at an IXP prepends its own AS number to all updates it forwards, so ISP peers see the IXP AS in the path even though traffic never traverses it. Configuring neighbors as route-server-clients (per RFC 7947) makes the BGP daemon forward updates with the original AS path unmodified, hiding the IXP AS entirely. Engineers building IXP peering setups track BGP edge cases like this on daily.dev."}},{"@type":"Question","name":"How do I fix 'first AS check' failures when peering with a BGP route server?","acceptedAnswer":{"@type":"Answer","text":"A BGP route server omits its own AS from the AS path, so the first AS in received updates is the originating peer's AS, not the route server's AS. Most BGP implementations reject this by default. Disable the check with a command like 'no neighbor enforce-first-as' on each ISP router's session toward the route server to accept these updates. Networking engineers troubleshooting BGP session issues find relevant discussions on daily.dev."}}]} ```