- NZNOG - lists.nznog.org

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 12 Jan '15

12 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

Re: [nznog] Whole of Domain Web Harvest 2015
by emma h 23 Dec '14

23 Dec '14

for those wishing to block, the apache rewrite rule is; RewriteEngine on RewriteRule ^(.*)$ http:/your.domain.co.nz [R=301,L] RewriteCond %{HTTP_USER_AGENT} ^(.*)NLNZ_IAHarvester2015(.*)$ RewriteRule ^(.*)$ http://tinyurl.com/NLNZ-IAHarvester2015 merry festivus. -- em

2 1

AUI 10BaseT transceiver
by Gareth Fletcher 23 Dec '14

23 Dec '14

Hi team Is anyone near Auckland CBD/Ponsonby and have one of these they'd be willing to part with this afternoon/next week? We seem to have trashed all ours years ago... Please reply off-list, with beer of choice of course :) Cheers! Gareth

1 0

Whole of Domain Web Harvest 2015
by Jay Gattuso 23 Dec '14

23 Dec '14

Hi NZNoggers, I write to let you know of our intent to commence the next NZ Whole of Domain web harvest on the 12th of Jan 2015. The crawl will take approximately 3 weeks to complete. We will be following the same model as previous years, with the Internet Archive acting on our behalf to undertake the crawl. We will be adhering to robots.txt in the main, however when content blocked by robots.txt is embedded in a page that’s not blocked by robots.txt we will attempt to capture that content. The metadata the crawler will be using is:- metadata.userAgentTemplate=Mozilla/5.0 (compatible; NLNZ_IAHarvester2015 +(a)OPERATOR_CONTACT_URL@) metadata.operatorContactUrl=https://natlib.govt.nz/publishers-and-authors/web-harvesting/domain-harvest The contact URL gives some information that describes why we are doing this, and what we’re doing. If you have any questions or concerns, please drop me a line – I’ll be monitoring this email address over the Xmas period. Many thanks, Jay Jay Gattuso | Digital Preservation Analyst | Preservation, Research and Consultancy National Library of New Zealand | Te Puna Mātauranga o Aotearoa PO Box 1467 Wellington 6140 New Zealand | +64 (0)4 474 3064 jay.gattuso(a)dia.govt.nz<mailto:jay.gattuso(a)natlib.govt.nz>

1 0

Fwd: Estonian IPv6 deployment report
by Brian E Carpenter 22 Dec '14

22 Dec '14

An example from far away... -------- Original Message -------- Subject: Estonian IPv6 deployment report Date: Mon, 22 Dec 2014 17:27:23 +0200 From: Tarko Tikan <tarko(a)lanparty.ee> To: IPv6 Ops list <ipv6-ops(a)lists.cluenet.de> hey, Some time ago, many people noticed rapid IPv6 deployment growth in Estonia (from 0% to 5% in 4 weeks). We at 3249/Elion/Estonian Telecom were behind this, other operators don't have any serious IPv6 deployments at the moment. We rolled out v6 to everyone (both business and residential customers) with last-gen CPE, there was no hop-in our hop-out program - aim was to do it perfectly and without customers even noticing. I'm happy to say that we achieved this goal :) To satisfy general interest, I promised small (somehow it turned out longer than I expected) technical writeup how we enabled v6 for our subscribers. If you have any other questions, feel free to ask and I do my best to answer them. You can also skip the technical content and there are some statistics below. Our access network is mix of DSL/GPON/wimax/p2p-ETH and broadband service is deployed in shared service vlans. IPv6 traffic shares vlan with IPv4. Service vlans are transported over MPLS metro network using pseudowires and terminated in geo-clustered Alcatel 7750 BNG routers. Each subscriber is allocated up to 4 mixed v4 and v6 IP hosts. For v4 we are using the usual DHCP, for IPv6 we are using DHCPv6 with IA_PD only, no IA_NA is provided. Unfortunately DHCPv6 provides no way to signal IPv6 default-route thus we have to fall back to RA for default-route. RA does not include any on-link prefixes or DNS information. RAs are L2 unicasted to CPE MAC so no other CPE in service vlan picks up those RAs. To ensure rapid switchover between BNG routers, we are signalling virtual link-local address as default-route. We are using ALU internal DHCP/DHCPv6 servers to allocate leases but we also signal IP information from radius (in such case BNG "fakes" DHCP server) for static IP customers. Provided IPv6 prefix is always /56 and we keep the old lease for 24h even if the CPE is turned off (actual lease time is 30min). Unfortunately, IPv6 LDRA is not available on most of our access platforms so we have to rely on IPv4 session information for authentication. This linking is done in the radius server during subscriber authentication (excellent radiator + quite awful SQL queries :) - if subscriber has IPv4 session (that has been authenticated using DHCP opt82), same MAC address is allowed to have IPv6 session on exactly the same virtual BNG port. IPv4 and v6 session are both tied to same subscriber and share shapers, QOS etc. We were able to enable IPv6 only on our last-gen Inteno CPEs. They run modified OpenWrt and because it's linux - everything is possible :) In CPE, /56 is divided up to /64s, first one is currently reserved but we will configure it on loopback interface and use it for CPE management. Second /64 is configured on LAN and third is configured on public wifi SSID (if you choose to enable this option). In the LAN, IPv6 config is provided by RAs, we also support RDNSS and stateless DHCPv6 for DNS. There is also ingress IPv6 firewall in the CPE and configuration is modifiable by user. To make deployment as smooth as possible, we rolled out IPv6 capable CPE software first. Then, during the BNG platform refresh, we deployed L2 ACLs that dropped all IPv6 traffic based on 0x86dd ethertype. We then deployed IPv6 config to all BNGs and could verify everything before single v6 lease was handed out to the subscribers. Then, interface by interface, we replaced L2 ACL with one that only allowed 0x86dd for certain, supported, OUIs. This is the current situation and we are investigating ways to support 3rd party CPEs - main problem is unreliable IPv6 config in CPEs. Many don't enable DHCPv6 (or enable NA but no PD) but still pick up default-route from RA and happily signal it to LAN. Some others hammer our BNGs with NA request every 0.1 seconds etc. As statistics go, there are 30000+ active IPv6 subscribers (almost 15% of our customer base, based on our public numbers), 81% of them have have at least one IPv6 enabled device in the LAN, 70% have more than one. Most IPv6 traffic is generated by Google+Youtube, Facebook and Akamai. Not bad for a country with 1.3M people. Next up: mobile network :) -- tarko

2 1