- NZNOG - lists.nznog.org

Fwd: [apnic-talk] [Apnic-announce] APNIC receives total of a /11 from IANA
by Dean Pemberton 22 May '14

22 May '14

---------- Forwarded message ---------- From: Secretariat <Secretariat(a)apnic.net> Date: Fri, May 23, 2014 at 11:21 AM Subject: [apnic-talk] [Apnic-announce] APNIC receives total of a /11 from IANA To: apnic-announce(a)lists.apnic.net ________________________________________________________________________ APNIC receives total of a /11 from IANA ________________________________________________________________________ Dear Colleagues The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following recovered IPv4 address blocks (total of a /11) from IANA in May 2014. 43.224.0.0/13 43.236.0.0/14 43.240.0.0/14 43.245.0.0/16 43.246.0.0/15 43.248.0.0/14 43.252.0.0/16 43.254.0.0/15 45.64.0.0/16 45.65.0.0/20 150.107.0.0/16 150.129.0.0/16 150.242.0.0/16 163.47.4.0/22 163.47.8.0/21 163.47.16.0/23 163.47.18.0/24 163.47.20.0/23 163.47.32.0/21 163.47.40.0/22 163.47.44.0/23 163.47.47.0/24 163.47.48.0/20 163.47.64.0/18 163.47.128.0/17 163.53.0.0/16 APNIC will soon implement policy proposal prop-105, and will create a new IPv4 address pool, in addition to the 103/8 pool (final /8). APNIC Members will be eligible to receive up to a maximum of a /22 from this new pool, in addition to the /22 they can receive under the final /8 policy. For more information about prop-105, please see: https://www.apnic.net/policy/proposals/prop-105 If you have any questions, please contact helpdesk(a)apnic.net. Kind regards, ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net ________________________________________________________________________ _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce _______________________________________________ apnic-talk mailing list apnic-talk(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-talk

1 0

APNIC allocated new space - all members eligible to receive an additional /22
by Skeeve Stevens 20 May '14

20 May '14

Hi everyone! This is indeed awesome news for small players out there who need address space. APNIC has been allocated a /11 from IANA (see the reasons below). This means that all current account holders will be eligible to receive an additional /22 under this allocation, in addition to the /22 you were already able to receive under the final /8 policy. This is a huge plus for small providers who need just a little bit on extra space. Just a note. This new allocation should not be seen as a handout for those who will request it and try to immediately sell it. It will follow the same /8 allocation where you will be required to hold on to it (and pay your membership at the new level) for at least a year. Those not prepared to pay the new membership level, shouldn't request it. These new ranges should be available for request sometime next week. Expect an announcement from APNIC. Good times! ...Skeeve =====START OF ANNOUNCEMENT===== ________________________________________________________________________ APNIC to receive additional IPv4 allocation from IANA as 'Recovered Space' to be distributed ________________________________________________________________________ LACNIC's announcement that its inventory of IPv4 addresses has reached less than a /9 (or 8,388,608 addresses) today triggered the activation of IANA's Recovered Pool of addresses. This means IANA will make a distribution to each RIR, including APNIC, every six months until the pool is exhausted. APNIC has received a /11 of IPv4 address space (2,097,152 addresses) from IANA under the Recovered Pool Policy. https://www.icann.org/resources/pages/allocation- ipv4-post-exhaustion-2012-05-08-en APNIC will implement procedures for distribution of space from this new allocation of addresses. APNIC Members will be eligible to receive up to a /22 from this pool, in addition to the /22 that they can receive under the last /8 rationing policy. This gives new or existing APNIC Members up to 2,048 IPv4 addresses from these address blocks, while the space is available. APNIC's Director General, Paul Wilson, said reaching this important milestone had two major implications for organizations in the Asia Pacific. ''Firstly, APNIC's receipt of the /11 from IANA will mean that organizations in our region can get a few more addresses, which they sorely need in many cases. Also, newcomers to the Internet will be able to receive these small allocations for some years to come, which is really critical for healthy Internet competition and growth into the future,'' Wilson said. ''The second, and more important message this milestone highlights, is that the journey towards exhaustion of IPv4 address space globally is continuing as expected, and the need for organizations to deploy IPv6 is increasingly urgent,'' he said. ''I again urge the Asia Pacific Internet community to turn its investments toward the transition to IPv6. If you depend on the Internet, then you will depend on IPv6 as a critical part of your business. Now is the time to be asking those who provide you with Internet services and expertise - whether they are ISPs, vendors, data centres, developers, staff, or consultants - how they will support IPv6 services for your in future.'' ''The good news is that costs can be minimized by planning ahead - for instance, by ensuring IPv6 capabilities are gained within the normal hardware and software upgrade cycles.'' APNIC will advise the community when applications for the new IPv4 addresses can be submitted. APNIC account holders who wish to apply for IPv4 addresses from the Recovered IPv4 Pool allocation will be able to do so via MyAPNIC using the standard application process. http://www.myapnic.net All policies for management of IP address space in the Asia Pacific region are determined by the Internet community through an open, consensus-based policy development process that is hosted by APNIC. The policy for allocation of Recovered IPv4 Pool addresses was approved during the 36th APNIC Conference, held in Xi'an, China, in August 2013. For more information on IPv4 and IPv6, visit the IPv6 Resources page. http://www.apnic.net/ipv6 =====END OF ANNOUNCEMENT===== ...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

1 0

Fwd: [apnic-talk] [Apnic-announce] APNIC to receive additional IPv4 allocation from IANA as 'Recovered Space' to be distributed
by Dean Pemberton 20 May '14

20 May '14

An ability to get some more IPv4 addresses for those who still need them. ---------- Forwarded message ---------- From: APNIC Secretariat <secretariat(a)apnic.net> Date: Wed, May 21, 2014 at 12:31 PM Subject: [apnic-talk] [Apnic-announce] APNIC to receive additional IPv4 allocation from IANA as 'Recovered Space' to be distributed To: apnic-announce(a)lists.apnic.net ________________________________________________________________________ APNIC to receive additional IPv4 allocation from IANA as 'Recovered Space' to be distributed ________________________________________________________________________ LACNIC's announcement that its inventory of IPv4 addresses has reached less than a /9 (or 8,388,608 addresses) today triggered the activation of IANA's Recovered Pool of addresses. This means IANA will make a distribution to each RIR, including APNIC, every six months until the pool is exhausted. APNIC has received a /11 of IPv4 address space (2,097,152 addresses) from IANA under the Recovered Pool Policy. https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-… APNIC will implement procedures for distribution of space from this new allocation of addresses. APNIC Members will be eligible to receive up to a /22 from this pool, in addition to the /22 that they can receive under the last /8 rationing policy. This gives new or existing APNIC Members up to 2,048 IPv4 addresses from these address blocks, while the space is available. APNIC's Director General, Paul Wilson, said reaching this important milestone had two major implications for organizations in the Asia Pacific. ''Firstly, APNIC's receipt of the /11 from IANA will mean that organizations in our region can get a few more addresses, which they sorely need in many cases. Also, newcomers to the Internet will be able to receive these small allocations for some years to come, which is really critical for healthy Internet competition and growth into the future,'' Wilson said. ''The second, and more important message this milestone highlights, is that the journey towards exhaustion of IPv4 address space globally is continuing as expected, and the need for organizations to deploy IPv6 is increasingly urgent,'' he said. ''I again urge the Asia Pacific Internet community to turn its investments toward the transition to IPv6. If you depend on the Internet, then you will depend on IPv6 as a critical part of your business. Now is the time to be asking those who provide you with Internet services and expertise - whether they are ISPs, vendors, data centres, developers, staff, or consultants - how they will support IPv6 services for your in future.'' ''The good news is that costs can be minimized by planning ahead - for instance, by ensuring IPv6 capabilities are gained within the normal hardware and software upgrade cycles.'' APNIC will advise the community when applications for the new IPv4 addresses can be submitted. APNIC account holders who wish to apply for IPv4 addresses from the Recovered IPv4 Pool allocation will be able to do so via MyAPNIC using the standard application process. http://www.myapnic.net All policies for management of IP address space in the Asia Pacific region are determined by the Internet community through an open, consensus-based policy development process that is hosted by APNIC. The policy for allocation of Recovered IPv4 Pool addresses was approved during the 36th APNIC Conference, held in Xi'an, China, in August 2013. For more information on IPv4 and IPv6, visit the IPv6 Resources page. http://www.apnic.net/ipv6 ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net ________________________________________________________________________ * Sent by email to save paper. Print only if necessary. _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce _______________________________________________ apnic-talk mailing list apnic-talk(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-talk

1 0

IANA IPv4 Recovered Address Space registry updated
by Leo Vegoda 20 May '14

20 May '14

Hi, ICANN has updated the IANA IPv4 Recovered Address Space registry after LACNIC notified it that it has less than a total of a /9 in its inventory of IPv4 address space. This triggered the activation the Recovered IPv4 pool, which was created in the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. The address space selection is made using software that tries to allocate blocks based on the RIR managing the DNS for that /8. The software, along with a worked example, is published at: https://github.com/icann/ The list of allocations can be found at: https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered -address-space.xhtml#ipv4-recovered-address-space-2 Kind regards, Leo Vegoda

1 0

Real world experiences with Chorus ATA Voice service sought
by Alexander Neilson 19 May '14

19 May '14

Hi All I am looking for anyone who is using Chorus ATA Voice as part of their UFB offerings who would be willing to share experiences / advice / etc with me. I am trying to firm up exactly how we want to deploy things and the choices we will make and while the Chorus documents are fine some real world experiences / pitfalls / tips and tricks that could help shape how I do it or come back to the “lovely in theory, horrible in practice” that can be a common outcome. At the same time if anyone wants to share any similar information on the UFB Data plans / circuits then I would be most interested in anything people could share with me. Thank you all for your time. Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz 021 329 681 022 456 2326

1 0

NZNOG 2015 Programme Commitee
by Jamie Baddeley 12 May '14

12 May '14

Afternoon everyone, The NZNOG 2015 Programme Committee is responsible for the solicitation and selection of suitable presentation and tutorial content for the NZNOG 2015 conference (www.nznog.org) NZNOG 2015 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. The NZNOG Trustees selects a new Programme Committee each year and is now seeking nominations from the community. Eligible PC candidates are those who have attended NZNOG conferences in the recent past, have broad technical knowledge of Internet operations, and have reasonable familiarity with the format of NZNOG conferences. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work actively to solicit content for the event and review submissions for technical merit. The PC will meet by regular conference calls, during the months prior to the event. If you are interested in joining the PC send a brief note to "trustees at nznog.org". The note should include affiliation (if any) and contact details (including e-mail address), and a brief description of why you would make a good addition to the PC. PC members receive complimentary registration for the event. The NZNOG Trustees will accept nominations received by the end of Friday 30th June, 2014, and will announce the new PC shortly thereafter. Many thanks! NZNOG Trustees

1 0

A vs AAAA
by Mark Foster 11 May '14

11 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 08 May '14

08 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 05 May '14

05 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

SPF and mail forwarding, best practice?
by Richard Hector 25 Apr '14

25 Apr '14

Hi all, I'm in an organisation that uses a forwarding mailserver to give (some) members user(a)organisation email addresses, which get forwarded to their regular address. The trouble is, I have SPF on my domain, and one at least of the receiving MTAs checks it, and my mail gets rejected as a consequence. What's the best solution? Do I (and anybody else who might mail us) need to turn off SPF, or make it less strict? Does the forwarding server need to remail rather than forward? Do we need to persuade the receiving mail admins to whitelist our forwarder (there could be many others)? Should the organisation mailserver just operate an IMAP/POP/Webmail service rather than forwarding, so that this never arises (my favourite)? Any tips? Thanks, Richard

4 5

New RIPE NCC contribution to the IANA IPv4 Recovered Address Space registry
by Leo Vegoda 23 Apr '14

23 Apr '14

Hi, In April 2014, ICANN updated the IANA IPv4 Recovered Address Space registry to reflect the return of 14 /24 prefixes (5,376 IPv4 addresses) by the RIPE NCC. The updated registry can be found at: https://www.iana.org/assignments/ipv4-recovered-address-space Kind regards, Leo Vegoda ICANN IANA

3 4

InTAC 2014
by Dean Pemberton 23 Apr '14

23 Apr '14

Morning all. InTAC conference to be held again on the 9th of July in Auckland. The participants at last years conference gave plenty of feedback as to the directions that they wanted to see the Internet within New Zealand take. Feedback was that there needed to be more focus on the following areas: . Technical issues relating to the security of the infrastructure of the New Zealand Internet . Technical mechanisms to assist in the development of more appropriate Authentication, Identity and Trust systems relating to the use of the Internet . Technical ways to ensure the Future-proofing the infrastructure of the New Zealand Internet. What I'm suggesting for InTAC this year is the following structure... Welcome 45 Min - On DNSSEC 45 Min - On RPKI Morning Tea 45 Min - On Identity and trust online 45 Min - On Authentication (federated signon, 2fa, lockers) Lunch 45 Min - On SDN 45 Min - On UFB Afternoon Tea Open discussion Networking Drinks Does anyone have any feedback before I look to secure topic speakers and make it a real thing? -- Dean Pemberton Technical Policy Advisor InternetNZ +64 21 920 363 (mob) dean(a)internetnz.net.nz <javascript:;> To promote the Internet's benefits and uses, and protect its potential. -- -- Dean Pemberton Technical Policy Advisor InternetNZ +64 21 920 363 (mob) dean(a)internetnz.net.nz To promote the Internet's benefits and uses, and protect its potential.

2 2

Re: [nznog] CARDIGAN implements RPKI - Cleanliness of prefixes onWIX
by Andrew Niteesh 21 Apr '14

21 Apr '14

Hi, I have few clarifications, the table you shown have matric, local preference, path and next hop. 1. So how you are setting up these attributes in SDN? (Or) you have an application developed for BGP? (Or) you are running SDN on top of traditional networks? 2. What is Route flow - according to my understanding it's like getting connecting a set of open flow capable switches to single controller. Please correct me if am wrong. Thanks & Regards, Andrew Niteesh University of Houston

2 1

[OT] 3g on mikrotik
by Rob McDonald 21 Apr '14

21 Apr '14

Hey all, Sorry for the OT post... Does anyone have experience with USB 3g sticks on Mikrotik routerboards? I've had quite a long look around, and without resorting to trial and error I thought someone here might be able to share their winning numbers with me. Cheers Rob *Rob McDonald | *Director Level 2 Systems Ltd *M:* +64 21 902 929 *eFax:* +64 9 974 4734 *W:* http://www.L2.co.nz <http://www.l2.co.nz/>

3 3

Message concerning Certs
by Michael Sutton 19 Apr '14

19 Apr '14

NZNOG members: My apologies but all attempts to send the text content of this PDF this morning have been blackholed until I managed to send the contents to InternetNZ PAG as a PDF which made it through filters which been stopping this content. I have had no problem send other messages etc. Your comments would be appreciated as I see this as a major issue which may require all certificates to be regenerated and then only used on patched systems whose memory and priv keys cannot read copied by external parties. Sincerely Michael S Sutton Director - Awacs Communications (NZ) Limited Transit Room The Dominion Observatory 34 Salamanca Road Kelburn Wellington +64 21 305500 Twitter & Skype: Mikiwis http://www.awacs.co.nz https://www.google.co.nz/#q=michael+sutton+nokia+patent http://www.linkedin.com/profile/view?id=16587996&trk=tab_pro

9 13

Heartleech tool
by Juha Saarinen 15 Apr '14

15 Apr '14

https://github.com/robertdavidgraham/heartleech >From the read me: A typical "heartbleed" tool. What makes this different is: autopwn most (-a) that does all the steps needed to get private key post-handshake (encrypted) heartbeats instead of during handshake evades Snort IDS rules loops making repeated requests (-l <loopcount>) dumps binary data to file (-f <filename>) IPv4 or IPv6 (-v <IPver>) full 64k heartbleeds -- Juha Saarinen twitter: juhasaarinen

4 3

Fake domain renewal invoices
by Richard Hulse 14 Apr '14

14 Apr '14

I got one of these just now from Domain Renewal Group, so beware. It was sent to someone else in our organisation, who fortunately brought it to me instead of approving and paying it.

3 2

Heartbleed - clients at risk too
by Juha Saarinen 11 Apr '14

11 Apr '14

Morning. Just saw this: http://vrt-blog.snort.org/2014/04/heartbleed-continued-openssl-client.html Which I thought might be useful to know. -- Juha Saarinen twitter: juhasaarinen

3 2