Midwest Internet Exchange

Category Archives: Support

Why you need an IX, even if you have your own cache boxes

We’ve had networks on our IXes that have had a gigabit/s or more of traffic going to our cache boxes when they had their own on-net cache boxes that were working as designed. Many Content Delivery Networks (CDNs) have programs where you can get a node of theirs in your network to maximize performance, minimize […]

What do route servers do?

Transparency Route Servers, unlike regular BGP routers, provide transparency features to facilitate optimal path selection in Internet Exchange infrastructure. FD-IX Route Servers provide the following: 1) AS path transparency by hiding its own ASN. This shortens AS path by one hop and avoids the need for direct peering with other customers on our fabric. There may […]

IOS-XR Example Config

; ; REPLACE X with your appropriate FD-IX IP Address ; ; REPLACE Y with your appropriate IP blocks ; ; REPLACE 1234 with your ASN ; ; Route Server addresses are specific for Indy. Other locatins will need to be modified interface TenGigE0/1/0/7.300 description “Midwest IX Peering” ipv4 address 206.53.139.X ipv6 nd suppress-ra […]

Route Server Communities

We have started to implement communities in the route servers.  The most useful one we’ve found so far is that you can advertise a community of 0:{insert AS here} and it will not advertise that prefix to that AS via the route servers. It is useful if you have some specific prefixes you don’t want […]

Stopping DDOS attacks with BCP38

How do we stop DDoS attacks? Everyone implementing BCP38.  

General Policies

1. This document contains a set of common rules that all networks wishing to connect to the M-IX fabric must adhere to. Failure to comply with any provision of this agreement can result in immediate disconnection from the M-IX peering fabric without notice. By connecting to the M-IX peering fabric you acknowledge that you have […]

M-IX peering Requirements

Midwest Internet Exchange Peering Requirements: 1. The peering candidate must be a registered entity in its local jurisdiction. 2. The peering candidate must provide M-IX with a 24 hour contact point. 3. Only BGPv4 and BGPv6 are allowed as routing protocols. 4. The Peering candidate must have a registered, Public ASN (Autonomous System Number) issued […]

Example Cisco 3550 Config for M-IX

vtp mode transparent ! no spanning-tree vlan 777 ! If you don’t need LLDP, disable globally no lldp run ! If you don’t need CDP, disable globally no cdp run ! vlan 777 name M-IX ! interface /IfIdent/ description Interface to MIDWEST-IX switchport access vlan 777 switchport mode access switchport nonegotiate no keepalive speed nonegotiate […]

%d bloggers like this: