Stop every re-advertisement with NO_ADVERTISE
04NO_ADVERTISE has a stricter scope than an export-boundary tag: the received route must not be advertised to any other BGP peer.
The separate combined-set example carries NO_EXPORT as well. NO_ADVERTISE still prevents both advertisements; no route is sent past either stop bar.
Source for this drawing: RFC 1997 · Read RFC source: Well-known Communities · p.3 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
NO_ADVERTISE is 0xFFFFFF02. A route received with it MUST NOT be advertised to other BGP peers, including iBGP peers in the same AS.
- For community-attribute-aware speakers, nO_ADVERTISE is 0xFFFFFF02. A route received with it MUST NOT be advertised to other BGP peers, including iBGP peers in the same AS.
- This is an advertisement restriction, not a command to withdraw the route from the receiving router or a promise that it is installed.
- When the shown tag set contains NO_ADVERTISE and NO_EXPORT, the NO_ADVERTISE prohibition still blocks every peer. An ordinary local community does not override it.
Fictional routes and private AS numbers. These are bounded teaching examples, not a complete BGP implementation. Display a tag as AS:local only to help read its two 16-bit parts; the wire contains four octets.
Read the RFC section ↗