_____  __    ____ \                                             contact
     |   |  \  |      \  /                                           press
     |   |__/  |---    \/                                              faq
     |   |  \  |       /\                                          sitemap
     |   |   \ |____  /  \                                          search
  -about-  -services-  -members-  -joining-  -research-  -links-  -private

Secondary Service: Multi-Lateral Peering Agreement Route Servers

This service should be considered to be in BETA testing. And as such it is being offered with no implied warranty and free of charge for now.

TREX is running two route servers to facilitate the interconnection of members. The route servers accept all RIPE registered routes from all members that wish to peer with the route servers and announce those routes to all members that wish to receive them. They are eBGP route reflectors in essence.

Both route servers are running BIRD right now. However, we have plans to change one of them to run some other software to protect the service from bugs occuring in either one of the chosen software routing daemons. Further details are as yet unavailable.

The AS number that the servers use is 197032 which is a 32-bit ASN. Members that wish to peer with it, but who cannot configure 32-bit ASNs in their routers should configure 23456 instead. The addresses of the servers are 195.140.192.1, 195.140.192.2, 2001:7f8:1d:4::1 and 2001:7f8:1d:4::2.

Members who have transit-customer relationships with other members on the exchange should be careful about using the route servers in case they might inadvertently damage the functionality of said transit. The communities listed below can be used to limit route visibility in such cases.

BGP Communities Supported

Community	Announce?
0:ASN	not to ASN
0:65534	not to anyone
65534:ASN	yes to ASN

The route servers respect some parametrized BGP communities. To forbid the announcement of a route to a certain peer, use the community 0:peer-AS. For example to forbid announcing the route to AS1234 and AS2345 tag the route with the following communities:

0:1234 0:2345

To change from opt-out style announcement of routes to opt-in style announcement, use the community 0:65534. Routes with that community will not be announced to any peer unless the community 65534:peer-as appears on the route. For example, to announce a route to only autonomous systems 29243 and 51164 use the following set of communities:

0:65534 65534:29243 65534:51164

These communities are untested with 32bit autonomous system numbers. We shall worry about that once we get a member that has one.