AS9136 BGP Communities
At AS9136 we support communities for informational and control purposes. Which communites are available to you depends on your type of connection (transit, customer or peer) with us. If you find that you are missing certain information or features, please contact us as a peer by mail at firstname.lastname@example.org - Transit customers are welcome to open a ticket the usual way.
Informational communities propagate information about the prefixes and enable you to get insights or filter on the basis of this information. These communities are available to all connected networks, whether transit customer or peer.
|9136:200||From Internal||Prefix comes from a different internal router|
|9136:201||From Upstream||Prefix comes from a transit provider|
|9136:202||From Customer||Prefix comes from a downstream|
|9136:203||From Peer||Prefix comes from a peering session|
Regional origin communities will be supported shortly.
City origin communities will be supported shortly.
Transit origin communities will be supported shortly.
IXP origin communities will be supported shortly.
Control communities allow you to specify where and how a prefix is distributed by us.
|no-export||No Export / 65535:65281||Do not announce the prefix to any eBGP peer||Any|
|no-advertise||No Advertise / 65535:65282||Do not announce the prefix to any other router||Any|
|65535:666||Blackhole||Discard any traffic destined to this prefix
Customer prefixes with this community will be redistributed to Upstreams/Peerings for remote blackholing.
Advanced export control
! This community is not supported for all ASNs. We're working on automatic rollout for every directly connected ASN. More features are to come.
|64512:\<asn>||Do not export to \<asn>||Do not announce the prefix to eBGP peers with the given \<asn>||Any|
|64513:\<asn>||Prepend once to \<asn>||Prepend once on eBGP sessions to the given \<asn>||Any|
|64514:\<asn>||Prepend twice to \<asn>||Prepend once on eBGP sessions to the given \<asn>||Any|