AS250.net community documentation
The communities at AS250 allways follow this scheme: 250:XLLLO
X is the action to take place
X can be 0 for marking routes and will not be stripped when leaving our AS
or 1 up to 5 to be used by downstreams for asking us to prepend (1 to 5 times)
or 6 for the route not be advertised to the specified destination.
For values 1 to 6 the community will be stripped from the advertisment once
it is processed at our border routers.
LLL specifys the location
168 nbg1 (Nuremberg-I - Deutschherrnstr.) 169 nbg2 (Nuremberg-II - Deutschherrnstr.) 170 dus1 (Dusseldorf - Interxion) 171 ber1 (Berlin-I - Alt Moabit) 172 ffm1 (Frankfurt - Newcolo Mainzer Landstr.) 173 ams1 (Amsterdam) 174 zur1 (Zurich - LayerONE Letzigraben) 175 bru1 (Brussel - Versatel Nossegem) 176 lon1 (London - Telehouse East) 177 par1 (Paris - Verizon Saint-Denis/Aubervilliers) 178 ber2 (Berlin-II - Mitte) 179 mil1 (Milano - Newmedialabs Via Caldera)
O tells the kind of origin of the route
This digit can tell you if the route is received via peering or transit.
O has the value of 1 to 5 to indicate via which Internet Exchange the
route has been received. Thus they only unique per city or PoP.
The digits 6 through 9 as well as 0 have a global unique meaning:
0 customer route 9 paid upstream 8 peering partner of one of our upstream providers 7 paid private peering 6 unpaid private peering
List of Internet Exchanges with corresponding O value:
1 N-IX (location nbg1, nbg2) 1 ECIX (location ber1, dus1) 2 BCIX (location ber1) 1 freeBIX (location bru1) 1 kleyrex (location ffm1) 1 SwissIX (location zur1) 1 panap (location par1) 2 Sfinx (location par1) 3 pouix (location par1) 4 parix (location par1) 1 minap (location mil1) 2 MIX (location mil2)
Examples:
250:61771 - do not advertise route to panap in paris 250:1711 - this route comes from ECIX in Berlin-I 250:31689 - prepend three times to paid upstream in Nuremberg-I 250:1780 - this route came from a customer in Berlin-II If you want to filter out a certain upstream of ours we suggest matching the community for it e.g. 250:1689 and then apply an as-path filter to match the desired upstreams as (e.g. _250_31333_)
Our NOC Helpdesk will be pleased to help you making use of our communities.
