- mice-discuss - lists.micemn.net

Re: IRR Filtering

by Larry Larsen

Good Afternoon; I am also using ARIN IRR and have setup an AUT-NUM object. I was told that I had to set it up to get updates to appear properly. The problem I have is not with my IP Addresses, but with my customers that have their own blocks and ASNs. HE is still rejecting them. I am not sure how to get the AUT-NUM or Route-Set to work for my customers. Thank you! Larry L. Larsen Director of Information Technology O: 712-271-5920 | F: 712-271-2727 llarsen(a)longlines.biz Connect | Empower | Erich 504 4th Street | Sergeant Bluff, IA 51054 www.longlines.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Tuesday, June 23, 2020 1:44 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] IRR Filtering WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. I've looked at some other networks and this approach (list an as-set in PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. -- Richard

June 23, 2020

IRR Filtering

by Richard Laager

Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. I've looked at some other networks and this approach (list an as-set in PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. -- Richard

June 23, 2020

Re: Please Welcome SaskTel (AS803) to MICE!

by Doug McIntyre

On Fri, Jun 19, 2020 at 12:30:58PM -0500, Jay Hanke wrote: >Name: Saskatchewan Telecommunications >Port: Main Switch Ethernet 3/24/1 >ASN: 803 >IPv4: 206.108.255.166/24 >IPv6: 2001:504:27:0:0:0323::1/64 >Peering Contact: carrier.quotes(a)sasktel.com >Route Servers- YES >BFD: No Added into the route-servers and ready to go. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

June 19, 2020

Please Welcome SaskTel (AS803) to MICE!

by Jay Hanke

Name: Saskatchewan Telecommunications Port: Main Switch Ethernet 3/24/1 ASN: 803 IPv4: 206.108.255.166/24 IPv6: 2001:504:27:0:0:0323::1/64 Peering Contact: carrier.quotes(a)sasktel.com Route Servers- YES BFD: No Please note this is a reclaimed IPv4 Address. Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 19, 2020

Premier Disconnect AS53347

by Jay Hanke

Premier Communications has disconnected from MICE. Please remove the route server sessions and port assignments. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 19, 2020

Fwd: [arin-announce] New Internet Routing Registry Release

by Jay Hanke

FYI ---------- Forwarded message --------- From: ARIN <info(a)arin.net> Date: Wed, Jun 10, 2020 at 1:38 PM Subject: [arin-announce] New Internet Routing Registry Release To: <arin-announce(a)arin.net> ARIN is pleased to announce the release of new and updated Internet Routing Registry (IRR) features. Full release notes are included below this message. ARIN systems are operating normally. If you have questions, comments, or issues, please submit an Ask ARIN ticket using your ARIN Online account, or contact the Registration Services Help Desk by phone Monday through Friday, 7:00 AM to 7:00 PM ET at +1.703.227.0660. Regards, Mark Kosters Chief Technology Officer American Registry for Internet Numbers (ARIN) Release Notes This release consists of IRR additions and improvements. The following information is provided to assist you in using ARIN’s IRR. Obtaining Routing Information from ARIN’s IRR Using FTP ARIN’s IRR information can be obtained from ftp://ftp.arin.net/pub/rr/. The FTP site provides two sources that have been migrated from ARIN’s IRR: one for authorized objects and one for nonauthorized objects. Authorized objects have been verified that the organization is authorized to create the record and that the registration associated with the object is under an (L)RSA. What do I need to change after this IRR deployment to use FTP? * If you are obtaining IRR information via FTP, to get all ARIN objects, you’ll need to access two separate sources: ARIN (arin.db.gz) and ARIN-NONAUTH (arin-nonauth.db.gz). Note that the source files are in a new, zipped format (.gz). Using Near Real-Time Monitoring (NRTM) ARIN provides two NRTM streams: ARIN (which contains authorized objects, as previously described) and ARIN-NONAUTH (which contains nonauthorized objects). What do I need to change after this IRR deployment to use NRTM? * Add the new NONAUTH stream to your monitoring. The serial number for this stream is found at https://ftp.arin.net/pub/rr/ARIN-NONAUTH.CURRENTSERIAL * Update the current ARIN (authorized) stream serial number; this number is found at https://ftp.arin.net/pub/rr/ARIN.CURRENTSERIAL Whois Port 43: You can access ARIN’s IRR database for both ARIN and ARIN-NONAUTH sources (which is running IRR Daemon, or IRRd) by entering commands from a terminal window. There are no changes to this functionality after the deployment. Managing Routing Information in ARIN’s IRR ARIN now provides a new method to manage IRR data directly in ARIN Online by selecting IRR Object Records from the main navigation menu. Organizations who currently use ARIN’s email-template based system (IRR-email) can continue to use that system, but no new organizations will be added to the IRR-email system. Your data from the IRR-email system has been migrated and is available for viewing in ARIN Online, but migrated IRR objects cannot be modified in ARIN Online. (Only IRR objects created in ARIN Online can be modified in ARIN Online.) What do I need to do as a result of these changes? - If you are currently using IRR-email and you want to continue to use that system, no action is needed. (You cannot use both IRR-email and ARIN Online to manage your IRR data.) - If you are currently using IRR-email and you want to start using ARIN Online to manage your IRR data, upon your first use of IRR in ARIN Online, you’ll be asked to confirm that you want to switch to ARIN Online to manage your IRR data. You’ll have to agree to this change before proceeding. If you start using IRR-online, you will no longer have access to IRR-email. _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net) Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 10, 2020

Re: Route issues using University of Minnesota

by Frank Bulk

Interesting, both those sites are on ICN’s network (AS 6122), and trcaceroutes show a hop going through UMN. root@nagios:/home/fbulk# traceroute 205.221.124.133 traceroute to 205.221.124.133 (205.221.124.133), 30 hops max, 60 byte packets 1 router-core-inside.mtcnet.net (96.31.0.254) 0.311 ms 0.362 ms 0.478 ms 2 premier.sxct-south.fbnt.netins.net (207.32.15.26) 0.177 ms 0.223 ms 0.224 ms 3 sxct-south-2.sxcy.fbnt.netins.net (207.32.15.6) 1.622 ms sxct-south-1.sxcy.fbnt.netins.net (207.32.15.4) 1.720 ms sxct-south-2.sxcy.fbnt.netins.net (207.32.15.6) 1.663 ms 4 AS57-1.micemn.net (206.108.255.51) 11.012 ms 11.113 ms 11.129 ms 5 iastate-umn-v895.northernlights.gigapop.net (146.57.253.9) 15.663 ms 15.733 ms 15.763 ms 6 205.221.255.5 (205.221.255.5) 13.693 ms 13.588 ms 13.555 ms 7 207.28.254.50 (207.28.254.50) 15.366 ms 15.378 ms 15.375 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 *^C root@nagios:/home/fbulk# traceroute 165.206.200.5 traceroute to 165.206.200.5 (165.206.200.5), 30 hops max, 60 byte packets 1 router-core-inside.mtcnet.net (96.31.0.254) 0.307 ms 0.412 ms 0.471 ms 2 premier.sxct-south.fbnt.netins.net (207.32.15.26) 0.151 ms 0.163 ms 0.168 ms 3 sxct-south-1.sxcy.fbnt.netins.net (207.32.15.4) 1.593 ms sxct-south-2.sxcy.fbnt.netins.net (207.32.15.6) 1.618 ms sxct-south-1.sxcy.fbnt.netins.net (207.32.15.4) 1.603 ms 4 AS57-1.micemn.net (206.108.255.51) 11.250 ms 11.419 ms 11.423 ms 5 iastate-umn-v895.northernlights.gigapop.net (146.57.253.9) 15.645 ms 15.827 ms 15.893 ms 6 205.221.255.5 (205.221.255.5) 16.350 ms 13.646 ms 16.240 ms 7 207.28.254.1 (207.28.254.1) 13.693 ms 13.680 ms 13.680 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 *^C From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Steve Savoy Sent: Monday, June 8, 2020 2:05 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Route issues using University of Minnesota Hi Colin, Early this am we were seeing flapping of the circuits (pings were going up and down, etc) and then the circuits just went dark. Two of the circuits our customers were complaining about were: view.wrightmed.com 205.221.124.133 countyvrt.iowadot.us / 165.206.200.5 Thank you, Steve From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Colin Murphy Sent: Monday, June 8, 2020 1:58 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Route issues using University of Minnesota Hi Steve, Thank you for the email. We are trying to bring up a new peering with MICE, but it seems to be causing issues. Would you be able to provide any more detail on what you were seeing? I've shutdown the peering from this router to the MICE route servers and you should be able to bring yours back up. Thanks, Colin Murphy Sr. Network Engineer Office of Information Technology University of Minnesota Northern Lights Gigapop Desk: 612-626-0870 On Mon, Jun 8, 2020 at 1:53 PM Steve Savoy <stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com>> wrote: Hello, I was wondering if anyone else is having any route issues through the University of Minnesota today (206.108.255.162). We’ve taken multiple complaints so we had to shutdown the peering to the route servers. Thank you, Steve Savoy Network Administrator Winnebago Cooperative Telecom Assn. 704 E Main St | Lake Mills, IA 50450 [cid:image001.png@01D63E91.1087E5D0] 641.592.6105 - Phone 800.592.6105 - Toll Free 641.592.6067 - Fax stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com> - Email Visit www.wctatel.net<http://www.wctatel.net/> Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 10, 2020

Re: Route issues using University of Minnesota

by Steve Savoy

Hi Colin, Early this am we were seeing flapping of the circuits (pings were going up and down, etc) and then the circuits just went dark. Two of the circuits our customers were complaining about were: view.wrightmed.com 205.221.124.133 countyvrt.iowadot.us / 165.206.200.5 Thank you, Steve From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Colin Murphy Sent: Monday, June 8, 2020 1:58 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Route issues using University of Minnesota Hi Steve, Thank you for the email. We are trying to bring up a new peering with MICE, but it seems to be causing issues. Would you be able to provide any more detail on what you were seeing? I've shutdown the peering from this router to the MICE route servers and you should be able to bring yours back up. Thanks, Colin Murphy Sr. Network Engineer Office of Information Technology University of Minnesota Northern Lights Gigapop Desk: 612-626-0870 On Mon, Jun 8, 2020 at 1:53 PM Steve Savoy <stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com>> wrote: Hello, I was wondering if anyone else is having any route issues through the University of Minnesota today (206.108.255.162). We’ve taken multiple complaints so we had to shutdown the peering to the route servers. Thank you, Steve Savoy Network Administrator Winnebago Cooperative Telecom Assn. 704 E Main St | Lake Mills, IA 50450 [cid:image001.png@01D63D9D.6732F180] 641.592.6105 - Phone 800.592.6105 - Toll Free 641.592.6067 - Fax stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com> - Email Visit www.wctatel.net<http://www.wctatel.net/> Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

June 8, 2020

Re: Route issues using University of Minnesota

by Colin Murphy

Hi Steve, Thank you for the email. We are trying to bring up a new peering with MICE, but it seems to be causing issues. Would you be able to provide any more detail on what you were seeing? I've shutdown the peering from this router to the MICE route servers and you should be able to bring yours back up. Thanks, Colin Murphy Sr. Network Engineer Office of Information Technology University of Minnesota Northern Lights Gigapop Desk: 612-626-0870 On Mon, Jun 8, 2020 at 1:53 PM Steve Savoy <stevesavoy(a)wctatel.com> wrote: > Hello, > > > > I was wondering if anyone else is having any route issues through the > University of Minnesota today (206.108.255.162). > > > > We’ve taken multiple complaints so we had to shutdown the peering to the > route servers. > > > > > > Thank you, > > > > > > *Steve Savoy* > > *Network Administrator* > > *Winnebago Cooperative Telecom Assn.* > > 704 E Main St | Lake Mills, IA 50450 > > > > 641.592.6105 - Phone > > 800.592.6105 - Toll Free > > 641.592.6067 - Fax > > * stevesavoy(a)wctatel.com <stevesavoy(a)wctatel.com> *- Email > > > > *Visit www.wctatel.net* <http://www.wctatel.net/> > > > > > > > > Confidentiality Notice: This correspondence is the property of Winnebago > Cooperative Telecom Association and is for the sole use of the intended > recipient(s) and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. If you > are not the intended recipient, please contact the sender by reply email > and destroy all copies of the original message. > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

June 8, 2020

Route issues using University of Minnesota

by Steve Savoy

Hello, I was wondering if anyone else is having any route issues through the University of Minnesota today (206.108.255.162). We've taken multiple complaints so we had to shutdown the peering to the route servers. Thank you, Steve Savoy Network Administrator Winnebago Cooperative Telecom Assn. 704 E Main St | Lake Mills, IA 50450 [cid:image001.png@01D63D9C.37A4D470] 641.592.6105 - Phone 800.592.6105 - Toll Free 641.592.6067 - Fax stevesavoy(a)wctatel.com<mailto:stevesavoy@wctatel.com> - Email Visit www.wctatel.net<http://www.wctatel.net/> Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

June 8, 2020