May 2018 - Test - lists.nanog.org

DirecTV Now contact
by Michael Crapse 22 May '18

22 May '18

Our eyeball network is consistently having some streaming issues(buffering) with DirecTV now. Our main recourse is to sell them on youtube TV and netflix. fixes the issue, no more complaints from our customers. Issues mainly occur during peak times and even on 300+mbps low latency/jitter customers. However, if someone from DirecTV could contact me off list and we can debug this issue so that we don't have to keep pulling people to other services that would be great. Alternatively, if anyone could suggest with whom to peer to reduce the impact of this issue, that would be great. A solution that would be even better is if someone from Youtube TV would contact us off list and we can set up something commissioned based for all the good things we say about your service, and of course give our tech support people a reason to not be frustrated with the calls we receive for this issue.

5 4

NANOG 73 Agenda is Published
by Ryan Woolley 22 May '18

22 May '18

NANOG Community, The NANOG 73 Agenda is published at http://www.cvent.com/d/ttqv1z/16K and available as an iCal feed at https://pc.nanog.org/static/published/meetings/NANOG73/agenda.ics The Program Committee has worked closely with our speakers to develop a first-rate program, and we encourage all attendees to enjoy the whole conference. As we review submitted content, minor changes to the agenda are possible and will be reflected in the online feed. Thank you to the many members of our community who submitted interesting content for NANOG 73! Close to 500 attendees have registered and the NANOG family looks forward to welcoming all of you to Denver. Useful Information: - NANOG 73 General Information and Registration: http://www.cvent.com/d/ttqv1z - Hotel Room Block(s) Information: http://www.cvent.com/d/ttqv1z/8K - There are a few remaining spots to register for the NANOG 73 Hackathon: http://www.cvent.com/d/ttqv1z/4K - A welcome message that will be sent to registered NANOG 73 attendees shortly will provide more information on scheduled events and applications to help you to make the most of your time in Denver - Register to attend NANOG On The Road Washington, DC, taking place in September at http://www.cvent.com/d/ygqk8s/4W Safe travels and see you in Denver. Sincerely, Ryan Woolley, on behalf of the NANOG Program Committee

1 0

[NANOG-announce] NANOG 73 Agenda is Published
by Ryan Woolley via NANOG-announce 22 May '18

22 May '18

This message has been wrapped due to the DMARC policy setting to prevent NANOG subscribers from being unsubscribed due to bounces. _______________________________________________ NANOG-announce mailing list NANOG-announce(a)nanog.org https://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

Segment Routing
by Matt Geary 22 May '18

22 May '18

Hello maillist anyone had any experience with segment routing and its performance over LDP? We are evaluating the option to move to SR over LDP so we can label switch across our Nexus L3 switching environment. Thanks Packet Plumber

8 30

Re: Telecommunications Outage Report: Northern California Firestorm 2017
by Scott Weeks 22 May '18

22 May '18

--- sean(a)donelan.com wrote: From: Sean Donelan <sean(a)donelan.com> :: During the 2017 wildfires, there were no forms of :: communications or technologies that worked better :: than the rest. I don't have time to read all 80+ pages and don't see it in the contents. Do you know what services restored first? scott

1 0

earthlink email problems
by jimmy keffer 22 May '18

22 May '18

my has problems sending mail to earthlink.net the sever has a ptr abd reverse dns set but i get this To: jimmy(a)horsezipsworld.com Subject: Message undeliverable: MegaBBS Forum horsezip's world : New user alert From: mailer-daemon(a)horsezipsworld.com Date: Sun, 20 May 2018 23:40:41 -0400 Your message did not reach some or all of the intended recipients. Sent: Sun, 20 May 2018 23:40:40 -0400 Subject: MegaBBS Forum horsezip's world : New user alert The following recipient(s) could not be reached: horsezip(a)earthlink.net Error Type: SMTP Remote server (209.86.93.228) issued an error. hMailServer sent: MAIL FROM:<jimmy(a)horsezipsworld.com> Remote server replied: 550 ERROR: No or mismatched reverse DNS (PTR) entries for 23.227.197.10 hMailServer any one here who can help my server sends mail to servers fine gmail etc jimmy

3 2

RE: Segment Routing
by Jakob Heitz (jheitz) 22 May '18

22 May '18

Nexus supports LDP. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/mpls… Regards, Jakob

1 0

is odd number of links in lag group ok
by Aaron Gould 22 May '18

22 May '18

I have (2) 10 gig links bundled in a lag to my upstream internet provider. and we need more internet capacity. Is it cool to add a third 10 gig to my existing 20 gig lag internet connection? I'm asking since I heard in the past something negative about odd numbers of lag members. .but I also have heard that it's not a big deal. Let me know please -Aaron

7 8

Telecommunications Outage Report: Northern California Firestorm 2017
by Sean Donelan 22 May '18

22 May '18

A report on the telecommunications outages that affected Mendocino, Napa and Sonoma Counties in the wake of the devastating fires of 2017. http://www.mendocinobroadband.org/wp-content/uploads/1.-NBNCBC-Telecommunic… [...] Results show that in the 3-county area, 66% of residents lost landline services, 74% of residents lost cellular services, and 66% of residents lost Internet services with Napa County experiencing the most severe impacts. The 3-county average of service loss for these combined technologies is 71%. Many of these outages impacted residents that were geographically far from the actual burn areas. [...] During the 2017 wildfires, there were no forms of communications or technologies that worked better than the rest. Each method used for emergency notification played a crucial role in preparing residents for disaster. Technologies used by residents varied from many conventional methods to many non-conventional forms of communications. Regardless of the ways residents were notified, collectively the different methods played a major role in saving lives. [...] In the entire 2017 Northern California wildfires’ footprint, it is estimated that 160,000 wireline and 85,000 wireless customers lost service, including 11-15 Public Safety Answering points losing service. Over 340 cell sites were completely destroyed or damaged. [...] Internet outages affected (22) internet provider services over the 3-county region; however, not all (22) providers are available within each County. [...] When you evacuated your residence, how did you receive warning/notice to evacuate? did not receive any warning from anyone outside my own home (23.48%) other response (17.15%) received a phone alert of some kind (text alert, amber alert) (15.67%) received a phone call from a neighbor, family, friend (13.52%) received warning from a neighbor physically at my door (12.05%) received warning from public safety official physically at my door (6.88%) received a reverse 9-1-1 call (3.5%) heard sirens/bullhorns/public safety officials outside my home (3.44%) received notice on the radio (2.03%) heard a power outage alarm at my home (1.23%) received notice from a press event (0.86%) received notice from a ham radio operator (0.18%)

1 0

AT&T mobile intercepting TCP sockets?
by Chris Adams 21 May '18

21 May '18

I ran into an odd issue with access to a website I manage from AT&T mobile devices this weekend. The website worked for everybody not on AT&T mobile, and AT&T mobile users could access other sites; the problem was just this combination. Android and iOS phones, as well as a Linux system tethered to an Android phone, all had the same problem. On the Linux system, I disabled IPv6 in Firefox, and it could then connect. Browsers got various "connection reset" type errors; on Linux, I could telnet to port 80 or 443, and it would connect and immediately close. The site does have an IPv6 address, but I had missed getting the webserver to listen on IPv6 (my mistake). Adding that looks to have solved the problem. When I ran tcpdump on the server and had someone try to connect from their AT&T mobile iPhone, I saw three connection attempts a few tenths of a second apart (all refused by the server). My question is this: is AT&T mobile intercepting the TCP socket (and not handling "connection refused" correctly)? Is that a known thing? -- Chris Adams <cma(a)cmadams.net>

5 5