November 2015 - NANOG - lists.nanog.org

Traceroute troubleshooting
by Joe Maimon 03 Nov '15

03 Nov '15

So we all know that its much more difficult to diagnose using that tool than just reading its output more often than not. Whats usually more important is correlation, over time and at any specific time. While tools such as mtr provide over time viewpoints, what can be run, user style, that will show packet loss/jitter over successive hops or in some sort of diagnosable pattern, as snapshots of data, when running the tool for some period of time where the long term averages/cumulative numbers will render such events mere statistical noise? Thanks! Joe

2 1

New ISPs getting of the ground without IPv4?
by nanog-isp＠mail.com 03 Nov '15

03 Nov '15

Surprisingly enough demand for Internet services did not end when we ran out of IPv4. I'd like to hear from the guys and gals starting new ISPs how they are facing this brave new world. Is it NATs all the way down? Is IPv6 the knight in shining armor? Are you getting enough IPs? If not, how are you coping? Buying/renting some, tunneling to somebody who has some, what? It's all good and well hearing about how you should dual stack and reading about how established players handle IPv6 and IPv4 exhaustion, but what do you do when dual stacking isn't an option and IPv6 only takes you so far? Now is your chance to shine and bring us some tales from the trenches :) Jared

5 4

Routing between TATA COMMUNICATIONS and Level 3 Communications, Inc.
by Joe Klein 02 Nov '15

02 Nov '15

Found a routing problem between TATA COMMUNICATIONS and Level 3 Communications, Inc. Attempted traceroute from Digital Ocean to FrontRange Internet : traceroute to www.asx.com (2607:fa88:1000:5::a744:a050) from 2604:a880:800:10::1ba:5001, 30 hops max, 24 byte packets 1 2604:a880:800:10:ffff:ffff:ffff:fff2 (2604:a880:800:10:ffff:ffff:ffff:fff2) 2.638 ms 1.354 ms 1.101 ms 2 2604:a880:800::701 (2604:a880:800::701) 0.418 ms 0.338 ms 0.289 ms 3 decix-nyc.he.net (2001:504:36::1b1b:0:1) 11.43 ms 9.492 ms 1.132 ms 4 10ge16-1.core1.nyc4.he.net (2001:470:0:259::1) 10.062 ms 9.559 ms 1.177 ms 5 level3.gige-g3-5.core1.nyc4.he.net (2001:470:0:202::2) 2.989 ms 2.773 ms 1.515 ms 6 2001:1900:19:5::8 (2001:1900:19:5::8) 1.427 ms 1.402 ms 1.344 ms 7 vl-4060.car2.NewYork2.Level3.net (2001:1900:4:1::fe) 1.349 ms 1.332 ms 1.967 ms 8 vl-4061.car1.Chicago1.Level3.net (2001:1900:4:1::21) 22.435 ms 71.92 ms 57.907 ms 9 vl-4040.edge1.Chicago2.Level3.net (2001:1900:4:1::1e) 23.516 ms 23.427 ms 23.414 ms 10 vl-4042.edge6.Denver1.Level3.net (2001:1900:4:1::35) 46.468 ms 46.58 ms 46.779 ms 11 vl-51.ear1.Denver1.Level3.net (2001:1900:13:1::8) 47.678 ms 47.647 ms 47.861 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * Traceroute from the FrontRange Internet to Digital Ocean: traceroute6 2604:a880:800:10::1ba:5001 traceroute to 2604:a880:800:10::1ba:5001 (2604:a880:800:10::1ba:5001), 30 hops max, 80 byte packets 1 2607:fa88:1000:5::fffd (2607:fa88:1000:5::fffd) 0.554 ms 0.471 ms 0.375 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 2001:5a0:3900::3e (2001:5a0:3900::3e) 75.679 ms 78.276 ms 77.441 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Please contact off-line. Joe Klein "Inveniam viam aut faciam"

2 1

CIDR Utilization
by John Steve Nash 02 Nov '15

02 Nov '15

Hi, I'm looking for any tool or a way I could specify a CIDR and the prefixes that are being used within this CIDR and the tool show me all free supernets. Example: 192.168.0.0/24 - CIDR Used subnet's: 192.168.0.1/32 192.168.0.8/27 192.168.0.64/26 192.168.0.68/32 192.168.0.96/29 Tool Result => Free Subnet's: 192.168.0.2/31 192.168.0.4/30 192.168.0.32/27 192.168.0.128/25 Regards, John

7 7

APRICOT 2016
by Philip Smith 01 Nov '15

01 Nov '15

Hi everyone, Many of the NANOG community have over the years participated in the annual APRICOT conference. This is to let you know about the opening of the Call for Papers for APRICOT 2016, being held in Auckland, New Zealand. If you are considering attending APRICOT, why not do so as a presenter too. I've forwarded the CfP on behalf of the PC Chairs. Many thanks! philip -- Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 15th - 26th February 2016, Auckland, New Zealand https://2016.apricot.net CALL FOR PAPERS =============== The APRICOT 2016 Programme Committee is now seeking contributions for Presentations and Tutorials for APRICOT 2016. We are looking for presenters who would: - Offer a technical tutorial on an appropriate topic; - Participate in the technical conference sessions as a speaker; - Convene and chair panel sessions of relevant topics. Please submit on-line at: http://papers.apricot.net/user/login.php?event=34 CONFERENCE MILESTONES --------------------- Call for Papers Opens: 2 November 2015 Draft Program Published: As Papers Confirmed Final Deadline for Submissions: 25 January 2016 Final Program Published: 1 February 2016 Final Slides Received: 8 February 2016 **NOTE THAT REGARDLESS OF DEADLINES SLOTS ARE FILLED ON A FIRST COME, FIRST SERVED BASIS*** PROGRAMME MATERIAL ------------------ The APRICOT Programme is organised in three parts, including workshops, tutorials and the conference. Topics for tutorials and the conference must be relevant to Internet Operations and Technologies: - IPv4 / IPv6 Routing and operations - IPv6 deployment and transition technologies - Internet backbone operations - ISP and Carrier services - IXPs and Peering - Research on Internet Operations and Deployment - Pacific/Oceania Internet - Software Defined Networking / Network Function Virtualisaton - Network security issues (NSP-SEC, DDoS, Anti-Spam, Anti-Malware) - DNS / DNSSEC - Internet policy (Security, Regulation, Content Management, Addressing, etc) - Access and Transport Technologies, including Cable/DSL, 3G/LTE, wireless, metro ethernet, fibre, MPLS - Content & Service Delivery (Multicast, Voice, Video, "telepresence", Gaming) and Cloud Computing CfP SUBMISSION -------------- Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the Programme Committee will be unable to review the submission. For avoidance of doubt this means that submissions which do not include slides will be rejected immediately. For work in progress, the most current information available at time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Final slides are to be provided by the specified deadline for publication on the APRICOT website. Prospective presenters should note that the majority of speaking slots will be filled well before the final submission deadline. The PC may, at their discretion, retain a limited number of slots up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Every year we turn away submissions, due to filling up all available program slots before the deadline. Presenters should endeavour to get material into the PC sooner rather than later Please submit on-line at: http://papers.apricot.net/user/login.php?event=34 Any questions or concerns should be addressed to the Programme Committee by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mike Jager & Dean Pemberton Co-Chairs, APRICOT 2016 Programme Committee

1 0