--- title: Configuring BGP Community Propagation is Confusing «... description: A comparison of how different network operating systems handle BGP community propagation configuration, exposing the inconsistencies across platforms that... canonical: https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Configuring BGP Community Propagation is Confusing « ipSpace.net blog | daily.dev og:description: A comparison of how different network operating systems handle BGP community propagation configuration, exposing the inconsistencies across platforms that... og:url: https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark og:image: https://api.daily.dev/og/posts/sI9debark.png og:image:alt: Configuring BGP Community Propagation is Confusing « 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. # Configuring BGP Community Propagation is Confusing « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary A comparison of how different network operating systems handle BGP community propagation configuration, exposing the inconsistencies across platforms that claim to follow an "industry-standard" CLI. Arista EOS offers the most flexible approach with add/remove keywords and control over standard, extended, and large communities in a single command. ArubaCX mimics old-school Cisco IOS with a single-argument command. FRRouting treats community types as binary toggles and enables all communities by default in datacenter mode. Cisco Nexus OS has quirky behavior where the 'standard' keyword is silently absorbed. Junos takes a completely different approach, requiring routing policies to suppress community propagation rather than a direct configuration command. The post highlights how the lack of a true CLI standard leads to subtle but painful differences when writing automation templates across 14 platforms. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does FRRouting handle BGP community propagation configuration compared to Cisco IOS? FRRouting treats standard, large, and extended communities as independent binary values, settable or removable one per command. It also accepts 'both' (standard+extended) and 'all' (standard+large+extended) keywords. Notably, in datacenter defaults all community propagation is enabled, so you must explicitly remove unwanted types with 'no neighbor send-community ' rather than adding them. _Network engineers automating multi-vendor BGP configs track these platform quirks on daily.dev._ ### How does Junos configure BGP community propagation differently from other vendors? Junos has no direct command to disable BGP community propagation. Instead, if you want to suppress communities from being sent to a neighbor, you must apply a routing policy that explicitly removes them. This is fundamentally different from all other major platforms, which use a 'neighbor send-community' command to control propagation. _Engineers choosing between routing platforms for BGP automation find vendor-by-vendor breakdowns like this on daily.dev._ ### What changed in Cisco IOS 17.16.01 regarding BGP send-community behavior? Cisco IOS 17.16.01 reverted to a 'last value wins' behavior for the neighbor send-community command. Previously, specifying 'standard' and 'extended' in separate commands would merge them into 'both'. After 17.16.01, only the most recently configured value is retained. Additionally, Cisco IOS still has no way to control propagation of large communities. _Staying current on Cisco IOS breaking changes before upgrading is easier when the relevant posts surface on daily.dev._ ## Similar posts on daily.dev - [The Never-Ending IPv6 Loopback Prefix Saga « ipSpace.net blog](https://daily.dev/posts/the-never-ending-ipv6-loopback-prefix-saga-ipspace-net-blog-4nlhgh10l) · ipSpace.net Blog · 0 upvotes · 0 comments - [Arista cEOS Does Not Apply ACLs to Control-Plane Traffic « ipSpace.net blog](https://daily.dev/posts/arista-ceos-does-not-apply-acls-to-control-plane-traffic-ipspace-net-blog-ieh2uzhm7) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark) ```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":"Configuring BGP Community Propagation is Confusing « ipSpace.net blog","url":"https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark"},"datePublished":"2026-08-11T08:55:59.392Z","dateModified":"2026-08-11T09:08:07.998Z","description":"A comparison of how different network operating systems handle BGP community propagation configuration, exposing the inconsistencies across platforms that...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","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/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","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":"Configuring BGP Community Propagation is Confusing « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/configuring-bgp-community-propagation-is-confusing-ipspace-net-blog-si9debark#faq","mainEntity":[{"@type":"Question","name":"How does FRRouting handle BGP community propagation configuration compared to Cisco IOS?","acceptedAnswer":{"@type":"Answer","text":"FRRouting treats standard, large, and extended communities as independent binary values, settable or removable one per command. It also accepts 'both' (standard+extended) and 'all' (standard+large+extended) keywords. Notably, in datacenter defaults all community propagation is enabled, so you must explicitly remove unwanted types with 'no neighbor send-community ' rather than adding them. Network engineers automating multi-vendor BGP configs track these platform quirks on daily.dev."}},{"@type":"Question","name":"How does Junos configure BGP community propagation differently from other vendors?","acceptedAnswer":{"@type":"Answer","text":"Junos has no direct command to disable BGP community propagation. Instead, if you want to suppress communities from being sent to a neighbor, you must apply a routing policy that explicitly removes them. This is fundamentally different from all other major platforms, which use a 'neighbor send-community' command to control propagation. Engineers choosing between routing platforms for BGP automation find vendor-by-vendor breakdowns like this on daily.dev."}},{"@type":"Question","name":"What changed in Cisco IOS 17.16.01 regarding BGP send-community behavior?","acceptedAnswer":{"@type":"Answer","text":"Cisco IOS 17.16.01 reverted to a 'last value wins' behavior for the neighbor send-community command. Previously, specifying 'standard' and 'extended' in separate commands would merge them into 'both'. After 17.16.01, only the most recently configured value is retained. Additionally, Cisco IOS still has no way to control propagation of large communities. Staying current on Cisco IOS breaking changes before upgrading is easier when the relevant posts surface on daily.dev."}}]} ```