MIXP Announcement May 2016

mixp-announcement@lists.mixp.org

1 participants
5 discussions

by MIXP announcements

Dear all, The last announcement for now, and possibly the most exciting: The MIXP is pleased to welcome Atlas Communications (AS328019). They are already connected and ready to peer. Please contact Jerome Louis <jlouis(a)atlascommunication.mu> to arrange for direct peering. Have a great evening

7 years, 11 months

[MIXP Announcement] Looking glass and route collection

by MIXP announcements

One *more* new service now live at the MIXP is a route collector and looking glass. This only becomes useful though if all members set up peering to the route-collector. The route collector is a BGP speaker (or rather listener) that is similar to the route servers in that it doesn’t forward any traffic. However, it also does not advertise or share any routes or prefixes either. In other words, it’s entirely one way. It accepts and learns your prefixes, but does nothing else with them. So why have it, and why peer with it. Quite simply, attached to it is a web based looking glass service: https://lg.mixp.org/ This is a very important diagnostic and metric tool for you, the members and future members. It allows only BGP queries and is a very quick and easy way to troubleshoot and see what prefixes and ASNs are at the IXP. It’s also very useful for statistics and other research. All members are highly highly highly encouraged to peer with the route collection service. And it may in future become a compulsory requirement to connect the IXP, although that will need internal discussion. Note that as the route-collector never shares or advertises, nor passes any traffic, it is completely safe to set up a session to. Please add your BGP session for: ASN: AS 327821 IPv4: 196.223.0.199 IPV6: 2001:43f8:270:d0d0::199 Looking forward to seeing the sessions live in the looking glass!

7 years, 11 months

[MIXP Announcement] Reminder: Yes you can do IPv6 (at the MIXP)

by MIXP announcements

Dear all, A quick note to remind you that as a layer-2 exchange, the MIXP in no way restricts what version of IP traffic flows across it. It’s a switching fabric, and IPv6 works just as well as IPv4! Of course, both peers need to already be supporting IPv6, but when that is the case there is no reason not to configure an IPv6 BGP session in parallel to IPv4 and exchange IPv6 traffic too. Note that the IPv6 range for the peering LAN at the MIXP is: 2001:43f8:270:d0d0::/64 And the assignment of specific peering addresses simply matches the last hextet to last octet of the IPv4 address. For example, if your IPv4 peering address is 196.223.0.1, then your IPv6 address is 2001:43f8:270:d0d0::1. Likewise, 196.223.0.15, becomes 2001:43f8:270:d0d0::15. And so on. I am sure that there are members already peering with IPv4 that do both already run IPv6 on their own networks... If so, there is no reason not to peer with IPv6 also! Just do it!

7 years, 11 months

[MIXP Announcement] route server(s) now available!

by MIXP announcements

Dear MIXP and others, We are very pleased to let you know that the MIXP has two route servers now available. What is a “route server” and why would you want it? Without a route server, as the MIXP was until now, you need to maintain separate BGP sessions to each of your peers' routers. With a route server you can replace all, or some, of these sessions with one session towards each route server. Once you connect to the route servers you will start exchanging routes with other peers immediately. The route servers are an excellent way to get started on the exchange. And to gain more prefixes and exchange more traffic quickly and easily. Note that the route servers do not pass on any traffic themselves. The route servers do not partake in the forwarding path, so they do not forward any traffic. They simply exchange routing information, so your router learns about routes to your peers from the route-server and can then forward traffic directly to the peer. If you already have direct peering sessions, the route servers are still useful as a backup. If for any reason your direct session becomes inactive, chances are good you can still receive your peers announcements from the route servers, and thus can still exchange traffic. We are hopeful that the majority of members will peer with the route servers very soon. If you are not yet, you should set up your sessions as follows: route-server1.mixp.org: ASN: 37324 IPv4: 196.223.0.201 IPv6: 2001:43f8:270:d0d0::201 route-server2.mixp.org: ASN: 37324 IPv4: 196.223.0.202 IPv6: 2001:43f8:270:d0d0::202 When you are ready, please contact noc(a)mixp.org to confirm your session is up, your own details, or for any other queries.

7 years, 11 months

[MIXP Announcement] MIXP Announcements - welcome

by A "broadcast" mailing list for MIXP announcements.

Dear all, On additional list as also been created to share announcements pertinent to the MIXP and it’s operations. As with any other lists, you are receiving this initial posting as it was felt that you would be interested to receive these postings. Should that not be the case, and you wish to opt out. Or should you want to subscribe additional addresses, please visit: https://lists.mixp.org/mailman/listinfo/mixp-discussion This list is for the time being open for subscriptions, but is intended as a very low traffic “broadcast” list, and not as a discussion list. As such it is closed for posting to. That is, it’s in essence a read-only list. We will do the utmost to keep traffic low, and only send out important and relevant announcements. So generally this list should be non-intrusive. If you represent and existing MIXP participant ASN, it’s highly recommended that you remain subscribed to this list, else you may miss important information about new services, new members or planned maintenance in future. Note that the archives of announcements will for the time being also be publicly available to browse. Watch this space!

7 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

MIXP Announcement May 2016