The BGP Fundamentals We All Mastered
Anyone who has studied for a networking certification or managed a multi-homed environment knows the BGP basics. It’s the path-vector protocol that makes the internet work, allowing tens of thousands of independent Autonomous Systems (AS)—like those run
by ISPs, cloud providers, and large enterprises—to exchange routing information. We all learned the hierarchy of attributes: how a router prioritizes a path with a higher LOCAL_PREF, a shorter AS_PATH, a lower MED (Multi-Exit Discriminator), and so on. The entire point of these deep dives is almost always the same: to understand how BGP makes its core decision of selecting the single best path to a destination from potentially many options. This algorithm is the heart of BGP, and mastering it is crucial for ensuring traffic flows efficiently out of your network.
Where the Typical Deep Dive Stops
This intense focus on path selection is where most deep dives, and many careers, plateau. We become experts at influencing outbound traffic and understanding inbound preferences. We learn to prepend our AS path to make a route less attractive or tweak MEDs to signal a preference to our direct neighbors. These are powerful tools, but they are all fundamentally reactive, designed to manipulate an existing decision-making process. The problem is, this view treats BGP as a one-way conversation where you can only shout suggestions into the void. You are telling other networks which path you think is best, but you have limited tools to tell them what to do with that information once they receive it. This is where a seemingly simple, optional attribute changes the entire game.
The Hidden Detail: BGP Communities
The detail most engineers skip or underutilize is the BGP community attribute. A BGP community is simply a tag, or a label, that you can attach to a route. Unlike attributes that affect the path-selection algorithm, communities don't inherently change a route's ranking. Instead, they act as policy signals. Think of it like putting a special sticker on a shipping package. A sticker that says "This Side Up" doesn't change the package's destination, but it instructs every handler on how to treat it along the way. BGP communities are those stickers for your routes. This optional, transitive attribute is a 32-bit number, often written in the format of `ASN:Value`, which allows networks to group prefixes that should be treated the same way. They are passed along from one BGP peer to another unless explicitly removed.
Why This 'Tag' Is a Game-Changer
The power of communities lies in pre-negotiated agreements. An ISP might publish a policy stating, "If you send us a route with community 64512:70, we will set the LOCAL_PREF to 70 for that route." Suddenly, you have direct, policy-driven control over how your peer handles your traffic. Beyond custom agreements, there are several well-known communities defined by standards. The NO_EXPORT community is one of the most powerful and commonly used. When a router receives a prefix tagged with NO_EXPORT, it knows it must not advertise that route to any of its external BGP (eBGP) peers. This is incredibly useful for limiting the scope of a route, for example, if you want a prefix to be known only within your provider's network for traffic engineering purposes but not leaked to the entire internet. Another well-known community is NO_ADVERTISE, which is even stricter: a router receiving this tag will not advertise the route to any other peer, internal or external. These simple tags prevent the kind of misconfigurations and route leaks that have historically caused major internet outages. By tagging a route, you are no longer just suggesting a path; you are issuing a clear instruction.
