September 2020 - NANOG - lists.nanog.org

iOS 14 (Apple) DNS bits
by vom513 24 Sep '20

24 Sep '20

*** Hopefully this is on-topic enough for the list… Since iOS 14 has been released recently, folks have observed the changes to the network and DNS mechanics. I wanted to get some feedback from folks here on this. I have a small observation, and a slightly larger question: Observation: iOS 14 now seems to send 3 queries (up from 2) for every “socket” connection to a name. Whereas we’ve had A + AAAA for quite some time in many OS’es - on iOS 14 we now have A + AAAA + HTTPS (type 65). I doubt this will be any burden on anyone, but I just wanted to point out that now many Apple devices will have 1.5x the previous query traffic coming from them. I also wonder who is actually using HTTPS RR’s in their zones - I would assume Apple would be (soon at least) for their cloud and infra. services. Alas, I don’t see anything in Wireshark, nor do I have a command line utility that understands the RRtype to test by hand... Question: iOS 14 now flags networks that it believes are blocking encrypted DNS. It puts a warning in Settings for the wifi. For my home network this is expected. I redirect 53 to my own firewall - as well as use some RPZ feeds - one of which aims to block/poison DOH/DOT attempts. My question is how is it making this determination ? I log the iptables redirects, and I also log RPZ hits out of bind. I don’t see anything in my logs where my phone has tripped these. I don’t currently block 853/tcp (but I likely will) - so it shouldn’t be making it’s determination off of that… Does anyone *really* know how iOS 14 is testing this ?

3 3

Connecting networks across borders, and the world: A conversation with Alejandra Moreno + Joel Pacheco
by NANOG News 23 Sep '20

23 Sep '20

*“Here you can find mentors, friends, and colleagues who are willing to help you and share their knowledge.”* Everything Alejandra Moreno and Joel Pacheco do is centered on community, collaboration, and connectivity — from routing traffic to and from the MEX-IX, to peering relations and education with networks around the world. The two, who work together at MDC Data Centers in McAllen, Texas, first met while attending NANOG 70. We spoke with them recently about the role of empathy and a shared sense of purpose in staying connected during a pandemic; translating passion into action through one's professional work; and the importance of teamwork and mentorship in growing and evolving a career. Read the Feature <https://nanog.org/stories/connecting-across-borders/>

1 0

AS45102(Alibaba) Contact
by Pascal Masha 23 Sep '20

23 Sep '20

Hello, We are experiencing a routing issue towards AS45102, any engineer available on this list to help resolve. Please contact me offline. Emails to their noc have gone unanswered.

1 0

Cogent emails
by Dovid Bender 23 Sep '20

23 Sep '20

Is anyone starting to get the "cogent emails" again?

15 17

SRv6
by aaron1＠gvtc.com 22 Sep '20

22 Sep '20

I have what seems to be a good SRv6 test in my lab running XRv9k 7.0.2 But I'm wondering why the sniffer doesn't show the much-spoken-of SRH (Segment Routing Header).. But rather, shows my L3VPN v4 traffic riding v6 and that's it. Let me know if I'm seeing an SRH and just don't know it, LOL. Ethernet - Type 0x86dd Ipv6 - Next Header IPIP (4) Ipv4 - icmp echo (my tests ce to ce end to end) Those layers is all it shows. I've read a lot about SRv6 with SID's inside extension headers or segment routing header, but I'm not seeing it. Any idea what this is that I'm seeing ? I've configured the PE's IAW https://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k-r6-6/se gment-routing/configuration/guide/b-segment-routing-cg-asr9000-66x/b-segment -routing-cg-asr9000-66x_chapter_011.html#id_95420 I can give you more info if you wish. Aaron aaron1(a)gvtc.com

19 61

Just got this apparently fake NANOG invoice - Looks phishy
by Chris Boyd 22 Sep '20

22 Sep '20

Apparent MS-Word doc attached. Be careful out there. Return-Path: <cb2004097(a)bristol.lu> Received: from cross6.lu-visp.net (cross6.lu-visp.net [62.182.179.184]) by lenny.gizmopartners.com (8.14.7/8.14.7) with ESMTP id 08LJIMld018071 for <cboyd(a)gizmopartners.com>; Mon, 21 Sep 2020 19:18:25 GMT Message-Id: <202009211918.08LJIMld018071(a)lenny.gizmopartners.com> Received: from [161.132.101.74] (unknown [161.132.101.74]) by cross4.lu-visp.net (Postfix) with ESMTPSA id 54FDC8808 for <cboyd(a)gizmopartners.com>; Mon, 21 Sep 2020 21:13:53 +0200 (CEST) Date: Mon, 21 Sep 2020 14:15:49 -0500 From: "NANOG" <cb2004097(a)bristol.lu> To: "Chris Boyd" <cboyd(a)gizmopartners.com> Subject: Chris Boyd MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--308522813199332622918802174927344" X-unconfigured-debian-site-MailScanner-ID: 54FDC8808.AF049 X-unconfigured-debian-site-MailScanner: Found to be clean X-unconfigured-debian-site-MailScanner-From: cb2004097(a)bristol.lu X-Spam-Status: No ----308522813199332622918802174927344 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =0DPlease let me know WHAT ADDRESS TO SEND TO. NANOG =0D----Original Message-----=0DOn Mon, Sep 21, 2020 at 15:17 Chris Boyd <cb= oyd(a)gizmopartners.com> wrote:=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ----308522813199332622918802174927344 Content-Type: application/msword; name="INV #7565831.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="INV #7565831.doc" 0M8R4KGxGuEAAAAAAAAA

4 3

ARIN 46 Registration Now Open
by John Curran 22 Sep '20

22 Sep '20

NANOGers - ARIN 46 Registration is now open! Note that we will have the Public Policy consultations on 14-15 October (before NANOG) and the ARIN Member Meeting afterwards on 23 October. Please register asap for the ARIN meeting if you will be participating! Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] ARIN 46 Registration Now Open Date: 9 September 2020 at 4:10:25 PM EDT To: <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> Registration is now open for the ARIN 46 Public Policy and Members Meeting, which will be held entirely online this October. ARIN is holding this Public Policy and Members Meeting so that attendees may gather virtually to discuss draft Internet number resource policies and learn more about ARIN services and operations. Register today by visiting: https://www.arin.net/ARIN46 The ARIN 46 Public Policy and Members Meeting will be spread out over two sets of dates: 14-15 October and 23 October. Note that you only have to register once to attend any and all meeting dates! On 14-15 October, we will be conducting policy discussions and providing ARIN operational reports during the meeting sessions. Attendees will have the opportunity to join topic-based breakout sessions on a range of topics for informal conversation and networking. These breakout sessions will take place immediately following the conclusion of the meeting on 14 October. On 23 October, we will reconvene for the Members Meeting, which is open to all interested individuals. In addition to updates from the Board and Advisory Council, this session will focus on the 2020 ARIN Elections. Attendees will hear from the candidates as they answer community-sourced questions in our moderated candidate forums. Don’t forget to save the date for the ARIN 46 Newcomer Orientation and Policy Preview! All registrants will be invited to participate in an optional Newcomer Orientation and Policy Preview on 7 October. We welcome all first-time ARIN meeting attendees to come learn about ARIN and find out how to make the most of your meeting experience. Just like our last virtual meeting, ARIN 46 will be held via Zoom. We will provide the same remote participation options for ARIN 46 that we usually do for our in-person Public Policy and Members Meetings, utilizing features inside the Zoom webinar platform. The meeting will also be webcast with a live transcript for unregistered viewing. Registration is free, and all remote registrants will be listed as registered participants on the meeting website and in the archive of the meeting on the ARIN website. You must register for the meeting in order to submit comments and questions and vote in straw polls. The ARIN 46 chat in the Zoom webinar will be monitored to ensure that all participants adhere to the ARIN Participants Expected Standards of Behavior: https://www.arin.net/about/corporate/standards/ Register today at: https://www.arin.net/ARIN46 A link to access the virtual meeting will be emailed to all registered attendees in the days leading up to 14 October. For more details about remote participation and everything you’ll need to know to get ready for ARIN 46, visit: https://www.arin.net/ARIN46_remote If you have any questions, please email us at meetings(a)arin.net. Regards, American Registry for Internet Numbers (ARIN) _______________________________________________ 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.

1 0

BFD for routes learned trough Route-servers in IXPs
by Douglas Fischer 22 Sep '20

22 Sep '20

Time-to-time, in some IXP in the world some issue on the forwarding plane occurs. When it occurs, this topic comes back. The failures are not big enough to drop the BGP sessions between IXP participants and route-servers. But are enough to prejudice traffic between participants. And then the problem comes: "How can I check if my communication against the NextHop of the routes that I learn from the route-servers are OK? If it is not OK, how can I remove it from my FIB?" Some other possible causes of this feeling are: - ARP Resolution issues (CPU protection and lunatic Mikrotiks with 30 seconds ARP timeout is a bombastic recipe) - MAC-Address Learning limitations on the transport link of the participants can be a pain in the a..rm. So, I was searching on how to solve that and I found a draft (8th release) with the intention to solve that... https://tools.ietf.org/html/draft-ietf-idr-rs-bfd-08 If understood correctly, the effective implementation of it will depend on new code on any BGP engine that will want to do that check. It is kind of frustrating... At least 10 years after the release of RFC until the refresh os every router involved in IXPs in the world. Some questions come: A) There is anything that we can do to rush this? B) There is any other alternative to that? P.S.1: I gave up of inventing crazy BGP filter polices to test reachability of NextHop. The effectiveness of it can't even be compared to BFD, and almost kill de processing capacity of my router. P.S.2: IMHO, the biggest downside of those problems is the evasion of route-servers from some participants when issues described above occurs.

14 20

SPAM for nanog@ senders
by Łukasz Bromirski 21 Sep '20

21 Sep '20

NANOGers, Have you got email from 'dating.support(a)csvwebsupport.xn--com-to0a immediately after you post to nanog@? First time I thought it’s coincidence, but today when I got it, it’s hardly one ;) Topic is '[#WHB-257-41491]: Re: XXXXXX’ where XXXX is subject taken from last e-mail. I understand there’s need to connect people in hard, COVID times, but I doubt automated spam sender has good intentions with that regard ;) So.. somebody is scrapping this list to feed their spamming lists :/ — ./

5 6

See what's in store for NANOG 80 Virtual
by NANOG News 21 Sep '20

21 Sep '20

The NANOG Program Committee is preparing a solid program for NANOG 80, which will take place online October 19-21. Sessions will be held each day of the conference, from 12pm to 5pm EDT Monday through Wednesday, and will feature a variety of presentations, networking sessions, and BoFs on the latest technologies and industry innovation, plus a Virtual Expo, daily games + prizes, and numerous opportunities to connect with our community in real time. Explore the NANOG 80 Highlights page to learn more! View Highlights <https://www.nanog.org/meetings/nanog-80/highlights/>

1 0