June 2023 - mice-discuss - lists.micemn.net

Please welcome Qwilt Inc. to MICE!
by Jeremy Lumby Oct. 7, 2025

Oct. 7, 2025

Name: Qwilt Inc. Switch: MICE Main Ports: 6/29/1 ASN: 20253 IPv4: 206.108.255.202/24 IPv6: 2001:504:27:0:0:4F1D::1/64 Peering Contact: peering(a)qwilt.com Route Servers: YES BFD: NO Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

4 51

Please welcome T-Mobile USA, Inc to MICE!
by Jeremy Lumby Sept. 30, 2025

Sept. 30, 2025

Name: T-Mobile USA, Inc Switch: MICE Main Port: Ethernet 6/15/1 ASN: 21928 IPv4: This is a port addition to an existing LAG, all IP info remains the same. The new connection will be 3x100G IPv6: Peering Contact: peering(a)t-mobile.com Route Servers: Yes BFD: No Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

2 8

Please welcome Hiawatha Broadband Communications to MICE!
by Jeremy Lumby May 9, 2025

May 9, 2025

Name: Hiawatha Broadband Communications Switch: MICE Core Port: E5/41 ASN: 14828 IPv4: IPs remain the same. This is a port addition bringing capacity to 40G on portchannel 32 IPv6: Peering Contact: noc(a)hbci.com Route Servers: YES BFD: YES Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

3 21

Please welcome Express Data Solutions LLC to MICE!
by Jeremy Lumby Dec. 13, 2024

Dec. 13, 2024

Name: Express Data Solutions LLC Switch: MICE MAIN Port: Ethernet4/2 ASN: 31834 IPv4: 206.108.255.183/24 IPv6: 2001:504:27:0:0:7C5A::1/64 Peering Contact: peering(a)express-ds.com Route Servers- Yes BFD: Yes Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

3 10

IRR Mandatory at MICE / New Route Servers
by Richard Laager Feb. 27, 2024

Feb. 27, 2024

[I plan to send this to MICE-ANNOUNCE too, but I want to see if anyone has corrections.] MICE will soon be deploying new route servers which will require IRR (Internet Routing Registry) records, as is a best practice at IXPs. *What* * You MUST have an as-set object listing your AS and your downstream ASes (if any). o You MUST either list that as-set in PeeringDB or email the name of your as-set to me (off-list to rlaager(a)wiktel.com please). * A route/route6 object MUST exist for each prefix you announce to the route servers (whether originated by you or transited through you) and it must list an Origin AS that is in your as-set. *When* * *If you are a transit AS (i.e. have ASes behind you) and don't have an /as-set/ object, fix this **/now/**.* Without an as-set object, your downstream ASes announcements will be blocked (filtered) immediately when the /first/ new route server is cut in. (Granted, they will still work through the second route server until it is upgraded.) Figure you have 1-2 weeks at most. * Enforcement of the route/route6 objects (for both transit and non-transit ASes) will come later, but not a lot later. So please, start on this now. ** *Where* If you are not sure /where/ to create IRR records, use ARIN (assuming you are in the ARIN region). *How (with ARIN)* 1. Login to ARIN Online. (Go to arin.net and click Login in the top right.) 2. On the left side, expand "Routing Security" and click "IRR". 3. Click "as-set" at the top. 4. Click "Create an Object". 5. Fill in the fields: The "AS Set Name" is what you will list in PeeringDB (or email to me). "Description" is unparsed, but they suggest the location and have a button to "Copy the Address from My Org ID". "Members" is where you list your ASN and downstream ASes (if any). 6. Click "Review". Once ready, click "Submit". 7. Click "route/route6" at the top. 8. Click "Create an Object". 9. Fill in the fields: "Prefix" is the prefix, e.g. 192.0.2.0/24. "Origin" is your ASN. 10. Click "Review". Once ready, click "Submit". 11. Repeat to create additional route objects until all of your announcements are covered. Don't forget IPv6! *Examples* Here is my as-set: https://www.radb.net/query?keywords=AS-WIKTEL Here is one example route: https://www.radb.net/query?keywords=69.89.192.0%2F20 (I created the AS33362 one. The AS19905 one is because another AS can originate this route for DDoS scrubbing reasons.) -- Richard

10 34

Please welcome G-Core Labs S.A. to MICE!
by Jeremy Lumby Sept. 7, 2023

Sept. 7, 2023

Name: G-Core Labs S.A. Switch: MICE Core Port: E 4/7 ASN: 199524 IPv4: 206.108.255.191/24 IPv6: 2001:504:27:0:3:0B64::1/64 Peering Contact: noc(a)gcore.lu Route Servers: YES BFD: No Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

2 3

Re: FW: [EXTERNAL] - [MICE-DISCUSS] MICE Participants List
by Richard Laager June 28, 2023

June 28, 2023

It turns out that I had the route server links wrong. There is a database ID that gets put into the BIRD protocol. I thought it was the customer (participant) ID. But it turns out it is the VLAN Interface ID. I corrected this, and now the links work correctly. On 2023-06-28 06:26, Miles McCredie wrote: > > FWIW, the looking glass links generate the following message > -- Richard

1 0

MICE Participants List
by Richard Laager June 28, 2023

June 28, 2023

The MICE participants list is now built from IXP Manager: https://micemn.net/participants.html If there is something wrong about your entry, please let me or Jeremy know. See below about port discrepancies, first. I want to specifically thank Dustin Frandle of South Front Networks. He started this effort with JavaScript code to convert a standard IX-F JSON export into a participants table. While I ended up going a different direction (for reasons discussed below), he got the ball rolling. Jeremy and I wanted to retain the contact addresses, which IXP Manager only outputs in the IX-F export if you are logged in. (And, despite my request, they remain firm in that position and refuse to allow customization.) Additionally, I wanted to retain the ports, since our current process has Cologix using the website as the LOA/CFA. (We may want to move to a more standard approach on that, but I didn't want to put that change into the critical path of getting the participants list automated.) Unfortunately, despite a previous request and my re-request for it, the IXP Manager maintainer has taken a firm position that the IX-F JSON export should not be customizable. So I cannot easily tweak the template to output emails when unauthenticated or add additional information for ports. IXP Manager does support the idea of a custom member export, and INEX (the exchange primarily behind IXP Manager development) does use that for a custom JSON output. However, that requires building the desired output from scratch. I figured if I was going to do that, I might as well just output HTML directly. That way, I only have one thing in one language (PHP) to worry about, rather than two things (PHP + JavaScript). Granted, there are some cons too. I'm not 100% happy about any of this. But, ultimately I had to make some decision to get it done, and that's where I landed. I did the best I could with the responsive design. There are a couple of pre-existing bugs on edge cases (e.g. when your size falls at 991.xx so it's not <= 991 but also not >= 992, which is maybe only possible on HiDPI displays) that affect the whole site. This page in particular is not ideal on mobile, but I did what I could. If you've got better ideas, please let me know. ---- There are a couple port discrepancies that I've asked Jeremy to review: 702 Communications * Bluepeak Broadband Visions * G-Core Labs * HBC * LTD Broadband Omnitel * Paul Bunyan South Front Truestream * US Internet * I'm pretty sure these were wrong/outdated on the old list and correct in IXP Manager / on the new list. -- Richard

3 2

WiscNet router maintenance Thursday, June 29, 4pm
by Chris Wopat June 27, 2023

June 27, 2023

WiscNet will be replacing a router this coming Thursday at 4pm local time. Our MICE connection will be down during this transition. Expect it down for 15mins or so, maintenance should be complete by 7pm. Cheers, -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

1 0

Three BGP peers
by Frank Bulk June 24, 2023

June 24, 2023

Anyone else seeing both Yahoo peers and one Google peer down since early am? I didn't see any log messages about exceeding prefix counts or the like. Frank SiouxCity-Fibernet-Arista(s2)#sh ip bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.58 4 10310 2035987 4886675 0 0 12:23:38 Active 206.108.255.59 4 10310 2029469 4886360 0 0 12:23:41 Active 206.108.255.167 4 15169 2050148 4888984 0 0 12:23:40 Active SiouxCity-Fibernet-Arista(s2)#sh ipv6 bgp sum | ex Estab BGP summary information for VRF default Router identifier 207.32.15.21, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 2001:504:27::2846:0:1 4 10310 2209610 1893247 0 0 12:23:40 Active 2001:504:27::2846:0:2 4 10310 2202613 1892818 0 0 12:23:47 Active 2001:504:27::3b41:0:2 4 15169 2043589 1894022 0 0 12:23:48 Active SiouxCity-Fibernet-Arista(s2)#

6 8