Understanding BGP communities and their practical use in network operations

Question

I've been working on optimizing our network's outbound traffic flows and keep hearing about BGP communities. I understand they're a way to tag routes, but I'm not entirely clear on what they actually are or why network operators rely on them so heavily. I've looked at some provider documentation and see communities like 12345:100 but the practical use case isn't clicking for me. What are BGP communities in simple terms, and what are the main reasons an operator would use them instead of just relying on standard path attributes?

admin · Accepted Answer

BGP communities are tags attached to routes that convey routing policy information between autonomous systems without altering the path attributes. They function as simple, standardized labels that allow network operators to signal desired traffic handling to upstream providers or internal network segments, enabling granular control over route propagation, path selection, and traffic engineering. Operators heavily rely on communities because they provide a more scalable and flexible method than manipulating AS paths or MEDs, allowing specific actions like regional prepending, blackholing, or influencing peering preferences through agreed-upon values with transit partners.

For example, to mitigate a DDoS attack, you might tag a route with your provider's blackhole community:

route-map SET_COMMUNITY permit 10
  set community 65530:666

This signals the provider to drop traffic to that prefix. Another common use is influencing outbound path selection by prepending your AS only to specific neighbors:

route-map OUTBOUND permit 10
  match community 123
  set as-path prepend 64512 64512 64512

The underlying concept is that communities act as a policy language between BGP speakers, making them indispensable for large-scale traffic optimization and automated incident response.

Understanding BGP communities and their practical use in network operations

Who Is Online