BGP Communities
as210880 supports BGP large communities for traffic engineering. Tag your announcements to control how we propagate your prefixes. The scheme is 210880:<action>:<target> where a target of 0 means "all upstreams / peers" and a specific ASN scopes the action to that neighbour.
Action communities
Upstream actions
For networks we don't connect to ourselves but one of our upstreams does. The format is 210880:<upstream ASN>:<network ASN>: do not announce to that network via that upstream. Other upstreams are not affected.
Blackhole
Informational
We set these ourselves and strip them from anything that arrives already tagged, so on our routes they mean what they say.
Targets
0215296214762See the peering policy for session requirements and contact details, or check how a prefix is actually routed on the looking glass.
Example
Say you want us to prepend twice towards AS215296: tag your routes with 210880:102:215296. Same made-up prefixes and names as the session example on the peering page.
protocol bgp as210880 {
# ...
ipv6 {
export filter {
if net ~ [ 2001:db8:100::/48 ] then {
bgp_large_community.add((210880, 102, 215296));
accept;
}
reject;
};
};
}