Introduction

Peering Policy

Peering Agreement

Peering Locations

Routing Policy

Route Filtering

Packet Filtering

BGP Communities

Network Utilization

These communities are recognized and used by AS6667

NOTE: These communities will evolve with changes in transit providers and exchange points. If you are having problems with the communities, check here first to see if a community has been changed or removed. We will try to not change the meaning of a community unless the new meaning is a direct replacement.

Local Preference

Community

Effect

6667:80


6667:90


6667:100


6667:110

Set LOCAL_PREF to 80
Set LOCAL_PREF to 90
Set LOCAL_PREF to 100
Set LOCAL_PREF to 110

The communities that set the local preference within our network are usable by all customers and peers. The default local preference for customers is 101 and for peers it is 100. The default local preference for transits is 90. Local preference of 80 is meant for backup provided by a customer or peer to someone else and the local preference of 110 is meant for overriding routing to choose a certain path over others. Peers can't set a preference of 110.
Announce Route ...

Community

Effect

6667:200x

6667:201x



6667:202x




6667:203x




6667:204x




6667:205x



6667:206x




6667:207x



6667:208x




6667:209x

to all peers

to peers in Helsinki Finland and at Ficix

to peers in Stockholm Sweden and at Netnod

to peers in London United Kingdom and as LINX

to peers in Frankfurt Germany and at DECIX

to peers in Hamburg Germany

to peers in Copenhagen Denmark and at DIX

to peers in Oslo Norway and at NIX

to peers in Amsterdam The Netherlands and at AMS-IX

to peers in New York USA and at NYIIX

The communities that control route announcement to peers and transits are only available to customers. The x specifies what the action for the said target is:

0 Announce as is ..
1 Announce with 6667 prepended to as-path ...
2 Announce with 6667 6667 prepended to as-path ...
3 Announce with 6667 6667 6667 prepended to as-path ...
9 Don't announce ... (default and takes precedence if present)

We will also let external communities through from customers. This will enable customers to use similar communities of our peers and transits. Some pages describing these communities have been collected at the end of the page.


Announce Route ...

Community

Effect

6667:90x


6667:100x

6667:101x


6667:102x


6667:103x

to all AS6667 customers

to all transits

to AS3356
Level3

to AS3549
Global Crossing

to AS3320
T-Systems


Route Origins...

Community

Effect

6667:4000


6667:4001


6667:4002


6667:4003


6667:4004


6667:4005


6667:4006


6667:4007


6667:4008


6667:4009


6667:4010

Tampere Finland

Turku
Finland

Helsinki
Finland

Stockholm
Sweden

London United Kingdom

Frankfurt
Germany

Hamburg
Germany

Copenhagen
Denmark

Oslo
Norway

Amsterdam The Netherlands

New York
USA

These communities are tagged on all routes to distinguish their origins. They are sent to everyone but not excepted from outside. They are there to let customers filter routes based on route source.

Route Origins

Community

Effect

6667:3000


6667:3001


6667:3003

6667:3004

internal or customer

public peering


private peering

transit

A normal customer announces all their routes to us with communities 6667:900, 6667:1000 and 6667:2000. When Eunet receives the routes, they are tagged with 6667:300x and the local location community (6667:4xxx.)