BGP Communities
Well-Known Communities
The route servers at LIS-IX will follow these well-known communities. For blackholing please refer to the specific Blackholing section.
| Description | Community |
|---|---|
| Prevent announcement of this prefix to a peer | 0:peer-as |
| Announce a route to a certain peer | 33733:peer-as |
| Prevent announcement of a prefix to ALL peers | 0:33733 |
| Announce a route to all peers (default) | 33733:33733 |
For BGP large communities:
| Description | Community |
|---|---|
| Prevent announcement of this prefix to a peer | 33733:0:peer-as |
| Announce a route to a certain peer | 33733:1:peer-as |
| Prevent announcement of a prefix to ALL peers | 33733:0:0 |
| Announce a route to all peers (default) | 33733:1:0 |
| Prepend to peer AS once | 33733:101:peer-as |
| Prepend to peer AS twice | 33733:102:peer-as |
| Prepend to peer AS thrice | 33733:103:peer-as |
These communities can be used to control which peers receive which routes. By peering with our route servers, you can control who receives your routes, and who doesn't.
For example, to announce route 192.0.2.0/24 to AS64500, this route could be announced to our RS with 33733:0:0 and 33733:1:64500.
In another scenario, you might not want to announce a route to AS64500 but you want everyone else to receive it: 33733:0:64500.
If you have any questions about communities or route server operations, please do not hesitate to contact us.
