- NZNOG - lists.nznog.org

A vs AAAA
by Mark Foster 12 May '14

12 May '14

Hello learned NZNOG-folks, Many of you have been working hands-on with IPv6 a lot more than I have, so i'll ask this here. In two cases, on two discrete systems, both Windows clients (one a Windows 7 workstation, the other a Windows 2008R2 server) a 'ping'[1] is run against a hostname. In both cases a ping against a v6 IP address is tried (and failed, as the host has no v6 connectivity - and in at least one case, v6 is actually disabled in the network interface settings). A simple 'nslookup' check without specifying the query type returns both IPv6 and IPv4 responses for the hostname. So why is the client trying to ping a v6 address when it has no v6 connectivity? (and for the record, an answer of 'make v6 work' doesn't solve my problem, as much as it might be a simple resolution.) Cheers Mark. [1] as you can probably guess, ping isn't actually the end-use of this connectivity, but it was the first troubleshooting measure used. This is impacting on application-layer connectivity, so 'use-v4-only' ping syntax also doesn't help me. :-)

4 5

TICSA "Guidance for Network Operators" released
by Michael Fincham 11 May '14

11 May '14

Hi all, Just a heads up to anyone who hasn't spotted it, it seems the "Guidance for Network Operators" document has been released by the NCSC. More info at: <http://ncsc.govt.nz/ticsa/> -- Michael

1 0

Average Usage Per Service
by Skeeve Stevens 11 May '14

11 May '14

Hey all, Just doing some math and capacity planning and I am wondering what others use for numbers for the average usage of a service per user? I am working with NBN-like speeds of 12mb, 25, 50 and 100. Back in the day I used to factor it in at around 30% when we were doing dialup and low-speed DSL... and on ADSL2 I normally factored it at around 15%. But I am wondering what people use for NBN-like speeds. I am thinking that a percentage is probably not a realistic measurement anymore as there is no particular reason a 25, 50 or 100mb user would do more or less on average... they just have the capacity to do more. Does anyone else have any thoughts they are willing to share, or even real observations across a significant number (thousands) of customers that they use for bandwidth (agvc and/or transit) planning? Feel free to off-list if you want to keep the information anonymous... I am happy to publish some findings and a spreadsheet for the use of others. Thanks all. ...Skeeve *Skeeve Stevens - *eintellego Networks Pty Ltd skeeve(a)eintellegonetworks.co.nz ; www.eintellegonetworks.co.nz Phone: +612 8014 7398; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellegonetworks ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/theispguy ; blog: www.theispguy.com The Experts Who The Experts Call Juniper - Cisco - Cloud - Consulting - IPv4 Brokering

2 2

Transit in Skytower
by Ben Cornish 11 May '14

11 May '14

Hey All, Looking for some Transit Capacity in Sky Tower for out of Band Management and possibly some Failover capacity. We are on Level 47 of Sky Tower and looking for the Cross connect.. Can anyone help me out ? Cheers.

1 0

Location and venue confirmed for NZNOG 2015
by Krystal Waine 09 May '14

09 May '14

Dear List, The location and venue are all locked in and I can officially announce that next years NZNOG conference will be held in Rotorua at the Distinction Hotel, which is conveniently located between the airport and the town centre. The dates for NZNOG 2015 are 29 - 30th January. Look forward to seeing a lot of you there! Cheers Krystal -- Krystal Waine Events Lead, InternetNZ DDI: 04 472 1601 Mobile:027 6555 450 *To promote the Internet's benefits and uses, and protect its potential.*

3 3

Best Practice - prefix advertisement
by Alexander Neilson 06 May '14

06 May '14

Hi All At $Dayjob I have been working around an aggregation bug in our routers and manually specifying prefix’s at the three levels we operate (/22, /23, /24) and using prefix filters to advertise /24’s to APE / WIX, /23’s to our domestic transit, and only the /22’s to international transit as a method of Traffic Management / Traffic Engineering to utilise cheapest links available. I have been exploring the looking glass services of a number of entities to see what propagates to them (that they enter into the forwarding database) and I am seeing some entities (who announce peering at APE for example) having the /22 and /23 routes in the LG outputs and following the /23 path in trace route. I am asking for two fold information. Can someone / everyone point me at their best guide to BGP “Best Practice” regarding advertising prefixes? and also can I get people’s specific advice about what they accept / do to announcements before entering them into their routers as accepted routes and what they would expect to see advertised to ensure my goals are reached. I made these changes to help reduce my contribution to the ballooning of the global routing table but I also don’t want to go to extremes on polluting the APE routing table by advertising the 12 /24’s plus the 6 /23’s and the 3 /22’s. Also can I get consensus information (or peoples opinions) about am I abusing / dis respecting APE with my announcements and how I should structure my announcements to be a respectable citizen here while providing the best hints to my preferred handling of traffic? (and feel free to let me know if I should just announce the /22’s and accept that some people choose to prioritise other paths) Thank you in advance for any input, feel free to reply off list. Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz 021 329 681 022 456 2326

4 3

APNIC 38 Call for Papers
by Dean Pemberton 06 May '14

06 May '14

___________________________________________________________________ APNIC 38 Conference - Call for Papers ___________________________________________________________________ The APNIC 38 Program Committee is now seeking presentations for the APNIC 38 Conference to be held in Brisbane, Australia, from 15 - 19 September 2014. We are looking for content that would suit the APOPS Plenary, technical conference sessions, and tutorials. Key dates --------- The timeline for submissions is: Call for Papers Opens Now First Round Paper Acceptance 1 August Final Deadline for Submissions 29 August Final Round Paper Acceptance 5 September Final Slides Received 12 September Submitting Proposals -------------------- Please submit your proposal for a presentation, technical session, or tutorial at: http://submission.apnic.net/user/login.php?event=14 Program material ---------------- The technical sessions at APNIC 38 will include presentations relevant to Internet operations and technologies. Possible areas of interest include: - IPv6 deployment and operations - IPv6 transition / IPv4 prolongation technologies - ISP and Carrier Services - IXPs and Peering - Network and Infrastructure security - Access and Transport Technologies - Content and Service Delivery - Software Defined Networking and Network Function Virtualization If you have any other ideas or proposals for panel or Birds of a Feather sessions, please feel free to submit your ideas via the submission system. If you have any questions, please email the Program Committee chairs at: pc-chairs(a)apricot.net For more information about APNIC 38, please visit: http://conference.apnic.net/38 On behalf of: APNIC 38 Program Committee Co-chairs: Dean Pemberton, Mark Tinka, and Raphael Ho

1 0

AusNOG 2014 Call for Presentations
by Mark Prior 05 May '14

05 May '14

Call for presentations for AusNOG 2014 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Swissotel Sydney 4 & 5 September 2014 Topics =-=-=- Internet operations can be a broad topic and the programme committee will be short-listing presentations in the following focus areas: * Improving the redundancy/resiliency/sustainability of your network * Making leaps in service or network availability * Taking the network operations BCP to the next level * Using 'offline' communications tools to keep the network working * How technology is changing network architectures * Evolution in network architectures and scaling issues * Analysis of relevant major operational events of the year This year we will be reintroducing a "Peering Forum". In this part of the programme we hope to include: * Peering related talks * Peering personals from various networks * IX updates Additional topics that are of interest to the network operator community are also welcome at AusNOG 2014. Naturally, presentations of a marketing nature are not welcome at this technical event. Notes to presenters =-=-=-=-=-=-=-=-=-= Preference will be given to presentations that result in actual operational outcomes. Session speakers should be prepared to present for 30 minutes. Keynote speakers will be expected to present for 45 minutes to 1 hour. Short presentations of strong operational content are also acceptable. Once the final slides are submitted, changes will only be permitted where the presentation requires the most up to date information or data. By submitting a presentation for consideration in the AusNOG 2014 programme, and if selected the presenter will allow AusNOG to: * Take photographs of the presentation and presenter * Record and rebroadcast video and audio of the presentation and presenter * Redistribute the presentation slides, audio, video, and photographs electronically, on the AusNOG website, or otherwise but leaving all intellectual property in the hands of presenter or rightful property holder[1]. Deadlines =-=-=-=-= 09 June: Submission of presentation title, presentation description (300 words), and presenter biography (200-400 words) 04 July: Presenters notified of their acceptance status as an AusNOG 2014 presentation. 27 August: Submission of final presentation slides as Portable Document Format (pdf), PowerPoint, or Keynote. Provision of a recent digital photograph (<500k) of the presenter. All submissions must be sent to organisers at ausnog.net. A separate call for lightning talks will be made closer to the AusNOG 2014 event. As in previous years you must be registered to attend AusNOG 2014 in order to be considered for a lightning talk. [1]: AusNOG accepts that some speakers are unable to allow us to archive their presentation due to company or corporate policy, and if the situation arises AusNOG will delete all copies in its possession after the presentation. Mark. For the AusNOG Board

1 0

clear.net.nz maintainers
by Al Twohill 04 May '14

04 May '14

Hi, Does anyone from Vodafone who looks after the Clear email servers lurk about here? I've had an issue going no-where with L1 support for the past 6 months.. Would greatly appreciate a contact off list. Cheers, Al

1 0

2 of 3 IPv6 DNS servers broken?
by Pete Mundy 27 Apr '14

27 Apr '14

Dear list Is anyone from Snap network ops watching who is involved in IPv6 or DNS? I'm not officially a Snap customer yet (1 week to go) so I guess trying to put this through the helpdesk might not be the best approach. Just wanted to give you guys a heads up really that only 1 of the 3 published NS appear to be responding to DNS queries via IPv6 (but they do all respond to ping6). See transcripts below. They were taken from a Snap UFB link. It all works fine via v4. I guess maybe others on the list with native v6 could test to confirm that this is also the case as seen from elsewhere? Eg perhaps from a non-Snap link? My v6 visibility is still a bit limited. Just a Raspberry Pi stuck behind a Fritzbox on Snap UFB for testing. Maybe something is 'on the fritz'?! Pete root(a)fpl-rpi16:~# ping6 -c 1 ns1.snap.net.nz PING ns1.snap.net.nz(2406:e000::100) 56 data bytes 64 bytes from 2406:e000::100: icmp_seq=1 ttl=251 time=10.0 ms --- ns1.snap.net.nz ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 10.048/10.048/10.048/0.000 ms root(a)fpl-rpi16:~# dig -6 SOA snap.net.nz @ns1.snap.net.nz ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> -6 SOA snap.net.nz @ns1.snap.net.nz ;; global options: +cmd ;; connection timed out; no servers could be reached root(a)fpl-rpi16:~# ping6 -c 1 ns2.snap.net.nz 64 bytes from 2406:e000::200: icmp_seq=1 ttl=251 time=9.98 ms --- ns2.snap.net.nz. ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 9.985/9.985/9.985/0.000 ms root(a)fpl-rpi16:~# dig -6 SOA snap.net.nz @ns2.snap.net.nz ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> -6 SOA snap.net.nz @ns2.snap.net.nz ;; global options: +cmd ;; connection timed out; no servers could be reached root(a)fpl-rpi16:/home/ladmin# ping6 -c 1 ns3.snap.net.nz PING ns3.snap.net.nz(2406:e000::300) 56 data bytes 64 bytes from 2406:e000::300: icmp_seq=1 ttl=251 time=11.4 ms --- ns3.snap.net.nz ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 11.433/11.433/11.433/0.000 ms root(a)fpl-rpi16:~# dig -6 SOA snap.net.nz @ns3.snap.net.nz ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> -6 SOA snap.net.nz @ns3.snap.net.nz ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57245 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 6 ;; QUESTION SECTION: ;snap.net.nz. IN SOA ;; ANSWER SECTION: snap.net.nz. 86400 IN SOA ns1.snap.net.nz. soa.snap.net.nz. 2014040202 10800 3600 604800 86400 ;; AUTHORITY SECTION: snap.net.nz. 86400 IN NS ns2.snap.net.nz. snap.net.nz. 86400 IN NS ns1.snap.net.nz. snap.net.nz. 86400 IN NS ns3.snap.net.nz. ;; ADDITIONAL SECTION: ns1.snap.net.nz. 86400 IN A 202.37.101.1 ns1.snap.net.nz. 86400 IN AAAA 2406:e000::100 ns2.snap.net.nz. 86400 IN A 202.37.101.2 ns2.snap.net.nz. 300 IN AAAA 2406:e000::200 ns3.snap.net.nz. 86400 IN A 202.37.101.3 ns3.snap.net.nz. 300 IN AAAA 2406:e000::300 ;; Query time: 35 msec ;; SERVER: 2406:e000::300#53(2406:e000::300) ;; WHEN: Sun Apr 27 19:34:48 2014 ;; MSG SIZE rcvd: 255

2 1