January 2015 - NZNOG - lists.nznog.org

Re: [nznog] IPv6 support across NZ ISPs [SECURITY=UNCLASSIFIED]
by HENDERSON MIKE, MR 26 Jan '15

26 Jan '15

Unfortunately, "those who have bothered to implement it" appear to be commercially inconsequential in the residential and mobile broadband markets. According to Andrew Cushen's recent blog post (at http://tinyurl.com/nvdxgh2), Spark, Vodafone and Callplus (= Orcon and Slingshot) between them own 94% of the residential broadband market, and of them Orcon says it has a 'trial' IPv6 offering, all the others Just Say No. Vodafone, Spark and two Degrees of course own 100% of the mobile broadband market, and none of them appear to offer IPv6. I'm afraid that v6 traffic is going to continue to be down amongst the noise until either Vodafone or Spark come to the IPv6 party Regards Mike Disclaimer: opinions expressed are mine and may not represent the position of my employer From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Pete Mundy Sent: Monday, 26 January 2015 5:37 p.m. To: nznog Subject: Re: [nznog] IPv6 support across NZ ISPs Agreed! Back-pats to those who have bothered to implement it. I know I base my purchasing decisions on it's availability. FWIW we went through a process of finding co-lo package providers that would provide IP space, bandwidth and physical hosting for our PBX equipment around 12 months ago and one of the pre-requisites was the ability to provision us IPv6 space. I was disappointed to find that only 3 of the 10 NZ providers we approached were able to offer it! Most said "it's on the roadmap, but not yet". Some just said "no". In the end we selected two of the providers that could, and we are very happy with the service from both. Hat tips to both Vibe and Unleash/Solarix; your IPv6 support was a significant part of what got you our custom :) Server colo (or VPS') are a different market than home DSL or UFB, but I think it could be interesting & useful to have some sort of matrix of IPv6 availability in that sector too. And 'business' UFB/HSNS/VSDL etc too for that matter. I do hope my 30% hit rate isn't an accurate indicator... Pete On 26/01/2015, at 10:38 AM, Alastair Johnson <aj(a)sneep.net<mailto:aj(a)sneep.net>> wrote: Nice work by FX. Keep it up. (and good work to the others that are offering IPv6 as compiled by Lindsay's list - also good work) The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately.

1 0

CloudFlare at AKL-IX doing some traffic!
by Michael Fincham 24 Jan '15

24 Jan '15

Hey all, Looks like ClareFlare have started moving some traffic at AKL-IX: <http://monitor.akl-ix.nz/cacti/graph.php?local_graph_id=18&rra_id=all> I look forward to seeing what happens next on this graph :) -- Michael Fincham

2 1

They're adding a "leap second" at Noon, Wednesday, 1 July 2015 NZ Standard Time {SECURITY=UNCLASSIFIED}
by HENDERSON MIKE, MR 15 Jan '15

15 Jan '15

Folks, Some of you may not have noticed this in the post-Christmas doze ... What will happen is that on 30th June [UTC time] the clock will go 23:59:59 > 23:59:60 > 00:00:00, instead of 23:59:59 > 00:00:00, i.e. an extra 'leap' second is inserted. It will cause the odd issue or two, depending on your environment and operating system.. For example, if you should happen to use RHEL you could start here https://access.redhat.com/articles/15145 There were certainly issues in other Linux distributions (including Oracle Linux and SLES) last time this happened on 30th June / 1st July 2012. Regards Mike ________________________________________ Press Coverage: This year will be slightly longer after the Paris Observatory announced that it was adding a "leap second" at midnight [UTC] on June 30 http://www.smh.com.au/technology/sci-tech/extra-second-to-be-added-to-2015-… Note: Midnight [UTC] on June 30 2015 is Noon, Wednesday, 1 July 2015 NZ Standard Time Official Announcement: INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE DE L'IERS OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : 33 (0) 1 40 51 22 26 FAX : 33 (0) 1 40 51 22 91 e-mail : services.iers(a)obspm.fr<mailto:services.iers(a)obspm.fr> http://hpiers.obspm.fr/eop-pc Paris, 5 January 2015 Bulletin C 49 To authorities responsible for the measurement and distribution of time UTC TIME STEP on the 1st of July 2015 A positive leap second will be introduced at the end of June 2015. The sequence of dates of the UTC second markers will be: 2015 June 30, 23h 59m 59s 2015 June 30, 23h 59m 60s 2015 July 1, 0h 0m 0s The difference between UTC and the International Atomic Time TAI is: from 2012 July 1, 0h UTC, to 2015 July 1 0h UTC : UTC-TAI = - 35s from 2015 July 1, 0h UTC, until further notice : UTC-TAI = - 36s Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC or to confirm that there will be no time step at the next possible date. Daniel Gambis Head Earth Orientation Center of IERS Observatoire de Paris, France http://datacenter.iers.org/eop/-/somos/5Rgv/latest/16<http://datacenter.iers..org/eop/-/somos/5Rgv/latest/16> The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately.

2 1

APNIC Consultations at Conference - Wednesday
by Richard Nelson 14 Jan '15

14 Jan '15

Hostmaster consultations ------------------------ APNIC is offering free, individual Hostmaster consultation sessions at the NZNOG Conference. These will be available on Wednesday Jan 28. At these sessions you can ask about: - How to request IPv4, IPv6, and AS numbers from APNIC - How to transfer IPv4 addresses and AS numbers - Current policies for IP and AS number management in the APNIC region - How to maintain and update your resource registration record in the APNIC Whois Database - Any individual issues you might have To register for the Hostmaster consultations, please email: elly(a)apnic.net

1 0

New prefixes on WIX
by Tim Price 13 Jan '15

13 Jan '15

Heads up that ~700 new prefixes just appeared then vanished from WIX route reflector 2. This momentarily pushed the route totals up over 2000 which may have reset a few BGP sessions for anyone limiting their received prefixes to 2000 on that session. Cheers, Tim.

1 0

python network trace analysis tutorial at NZNOG 2014
by Nevil Brownlee 13 Jan '15

13 Jan '15

Hi all: I'm giving a tutorial on "analysing network traces with python" at NZNOG 2015. The tutorial will cover how to use my python-libtrace module, with lots of example python programs. However, the examples I can think up easily are mostly trivial. It would help me a lot to know what kinds of trace analysis ISPs would actually find useful! If/when you collect packet traces, what kinds of information or analysis would you like to get from them? Any suggestions would be much appreciated - please email me off-list, nevil(a)auckland.ac.nz Cheers, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand

1 0

Fwd: Re: [mailop] Wildcarding of AHBL public DNSbl lists on Jan 1st
by Thom Hooker 04 Jan '15

04 Jan '15

(Apologies if you've seen this notification from the mailop list already. ) See the post below re: the AHBL RBL wildcarding certain zones today. There are NZ ASs in the latest CSV lists in the link below (Vodafone NZ, ICONZ, HD & NZ Wireless), this change may affect mail flows. Regards Thom -------- Original Message -------- Subject: Re: [mailop] Wildcarding of AHBL public DNSbl lists on Jan 1st Date: Fri, 26 Dec 2014 16:26:34 -0700 From: Brielle Bruns <bruns(a)2mbit.com> To: mailop(a)mailop.org On 12/26/14 4:00 PM, Frank Bulk (iname.com) wrote: > Thanks, that's helpful. > > I'm not sure how many IPs you have, but Cymru's service might be an option: >https://www.team-cymru.org/Services/ip-to-asn.html > > I found some other options: >http://quaxio.com/bgp/ >http://ipinfo.io/ >http://dev.maxmind.com/geoip/legacy/geolite/ (usage described here: >https://stackoverflow.com/questions/13110386/ip-to-asn-mapping-algorithm) > Thanks. I threw together a shell script that handles the conversion for me based on the geoiplookup tool and the output is going here: http://www.ahbl.org/queries/ I have to generate the lists manually for now, but it should help those looking to figure out who on their network is doing queries. -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org /http://www.ahbl.org _______________________________________________ mailop mailing list mailop(a)mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop _____________________________________________________________________________ This email has been filtered by SMX. For more info visit http://smxemail.com _____________________________________________________________________________

1 0

BCP / Guidance on IPv6 prefix size to provide to customers
by Alexander Neilson 02 Jan '15

02 Jan '15

I wondered if anyone on here had any guidance on any current BCP (or BCOP) or some general guidance on IPv6 allocations to customers (I am speaking here only for casual day to day allocations to customers) Looking through email archives and discussions that have seen around there was fairly vigorous discussions but no real resolutions. I have seen suggestions of /48, /50, /56. I am inclined to allocate /56’s to each customer (providing 256 /64’s). I don’t want to prevent customers from having the flexibility to do what they need / want to do nor stymie future use cases. If there is some good guidance on a need for /48’s then I will look at it and will use those if needed. Also, is current operating practice amongst others for all links to be /64’s even for p2p links? It seems a lot of documentation / reference texts are a few years old now and some providers have told me that this advice is no longer current but I haven’t yet seen this codified. My /32 allocation is provisionally as follows: 16 bits of /56 allocations - 65,535 customer allocations 8 bits for internal (leaves me 255 /64’s for p2p links between routers) Currently using PPPoE for IPv4 authentication for bulk customers and bespoke routed configurations for the rest. I intend to continue the PPPoE at this stage and just provide dual stack to every customer when connecting. I am still open to any input people have or feedback about what contributed to their deployments. I have looked into archives but was unable to find clear guidance that wasn’t discussed at length to be out of date / disputed so I am primarily looking for what the current best practice is so I can take advantage of the best advise for rolling out the deployment (I know we are late to this party but better late than never) Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz 021 329 681 022 456 2326

7 13