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 197032IPv4 routes
bgp.he.net 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 23456IPv4 routes
bgp.he.net instead. All ASNs visible via the route-servers have been collected into the AS macro AS197032:AS-ALL. The addresses of the servers are 220.127.116.11, 18.104.22.168, 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
|197032:0:ASN||not to ASN|
|197032:0:65534||not to anyone|
|197032:65534:ASN||yes to ASN|
0:1234 0:2345The Large Community equivalents are:
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:51164The Large Community equivalents are:
197032:0:65534 197032:65534:29243 197032:65534:51164
Only the Large Communities will work with 32bit autonomous system numbers.