- NZNOG - lists.nznog.org

Lightening Talks
by Richard Nelson 23 Jan '13

23 Jan '13

We are now looking for lightening talks for tomorrows session at the conference. If anyone would like to present a talk lasting 5 min or so could you please send an email to either me or talks(a)nznog.org. Thanks, Richard Nelson

1 1

Barracuda product warning.
by Alex White-Robinson 23 Jan '13

23 Jan '13

https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/2013… Vulnerability overview/description: ----------------------------------- 1) Backdoor accounts Several undocumented operating system user accounts exist on the appliance. They can be used to gain access to the appliance via the terminal but also via SSH. (see 2) These accounts are undocumented and can _not_ be disabled! 2) Remote access via SSH An SSH daemon runs on the appliance, but network filtering (iptables) is used to only allow access from whitelisted IP ranges (private and public). The public ranges include servers run by Barracuda Networks Inc. but also servers from other, unaffiliated entities - all of whom can access SSH on all affected Barracuda Networks appliances exposed to the Internet. The backdoor accounts from 1) can be used to gain shell access. This functionality is entirely undocumented and can only be disabled via a hidden 'expert options' dialog (see Workaround).

1 0

IPv6 Security
by Andrew Ruthven 23 Jan '13

23 Jan '13

Hey, These emails that just came through on the ipv6hackers seem relevant given Karl's talk on IPv6 Security. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: andrew(a)etc.gen.nz | linux.conf.au 2013 | Come join the party... | http://linux.conf.au

1 0

networking is hard - tshirts
by Sam Russell 23 Jan '13

23 Jan '13

I hope you're all enjoying the conference, and the awesome tshirts that some of us are wearing. I've had a few requests for them, so I thought I'd ask on list to see who wants them - they're $35 each, sizes are a bit larger than kiwi (my size M is like a normal kiwi size L), black with white text on them saying "networking is hard" I need to get about 10 requests all up to make it worthwhile, and I've had 5 already, so if I can get another 5 by the end of the day I might be able to get them printed in time for tomorrow - if not, you'll have to find some way to get your shirt, I'm in wellington, but given how much many of us travel I'm sure you could find someone to courier yours to you -- Sam Russell Network Engineer Research & Education Advanced Network NZ Ltd ddi: +64 4 913 6365 mob: +64 21 750 819 fax: +64 4 916 0064 http://www.reannz.co.nz

1 0

NZIX OpenFlow adventures phase 3
by Dean Pemberton 22 Jan '13

22 Jan '13

Morning everyone, You all remember the NZIX OpenFlow project I've been posting about of late. Well we've just ticked off Phase 3, and as far as we can tell it's another world first. Phase 3 was to implement a distributed SDN controlled fabric and pass production traffic over it. Today, with considerable support from Citylink, REANNZ and others in the SDN community. We have managed to extend our existing fabric across the city, provision our first customer link and pass their production traffic across the fabric and onto the WIX. I'll be giving some of the technical details at the NZNOG conference this week, but suffice to say that we're not about to stop here. We've got a distributed fabric now, and we're looking to extend this even further. 1) More locations. I still want Auckland and we're very close to having this be a reality 2) Look at further services this enables at Layer3 (going to working closely with Citylink on developing this) 3) Look at the auto-provisioning options this can provide at Layer2 So a couple of things to take away from this. . Remember that if you have a WIX peering session currently, I've already configured you a test session on my route server for you. Turn up a test session and convince yourself that it works router bgp 9483 bgp router-id 202.7.0.119 . If you have any suggestions of things we can be working on in the future then now's the time to get in touch and let us know your thoughts. What are the things that you always wished you could do on the exchange but couldn't? We can build those tools. . Thank you to all the people who made this success possible. If you've been a supporter since the beginning then we know who you are and thanks. See you that the conference! Regards, Dean

1 0

Re: [nznog] Will the conference wireless have IPv6?
by Pete Mundy 22 Jan '13

22 Jan '13

Yep, it'll work just fine, I was using it today to get to Google hosted email via IMAP/SSL/IPv6 & KAREN. Pete On 23/01/2013, at 6:16 PM, Lloyd Parkes <lloyd(a)must-have-coffee.gen.nz> wrote: A game server that I've just built here at home is only on IPv6 and I'd like to be able to connect to it. Cheers, Lloyd

1 0

Will the conference wireless have IPv6?
by Lloyd Parkes 22 Jan '13

22 Jan '13

A game server that I've just built here at home is only on IPv6 and I'd like to be able to connect to it. Cheers, Lloyd

1 0

National Library of New Zealand Web Harvest 2013
by Jay Gattuso 18 Jan '13

18 Jan '13

Hi All, This email is to inform you of the NLNZ intent to undertake its 3rd Whole of Domain Web Harvest. The planned dates for this exercise are the 4th to the 22nd of February 2013. The harvest will be undertaken by the Internet Archive<http://archive.org/index.php> on our behalf, More details can be found on the web harvest website: http://natlib.govt.nz/publishers-and-authors/web-harvesting/2013-nz-web-har… If anyone has any specific concerns, requests or questions, please do not hesitate to contact me directly: jay.gattuso(a)dia.govt.nz<mailto:jay.gattuso(a)dia.govt.nz> or via the project email address: Web.Archive(a)dia.govt.nz<mailto:Web.Archive(a)dia.govt.nz?Subject=About%20the%202013%20Web%20Harvest> If anyone wants to discuss this further on the mailing list I am happy to do so. King regards, 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>

5 5

Microsoft at APE and WIX
by Kevin Epperson 16 Jan '13

16 Jan '13

Hello Good folks of NZNOG - After following several recent threads on this list and other forums regarding Microsoft performance issues in New Zealand, I am pleased to now be in a position to solicit peering sessions at both APE and WIX (details below.) We are also peering with the route servers at both exchanges. Please feel free to email me directly with any related questions and also be on the look out for a Microsoft network engineer at NZNOG next week. Microsoft Details: AS macro: AS-MICROSOFT Suggested max prefixes : 250 Prefer no MD5. NOC E-mail: ioc(a)microsoft.com NOC Phone : 1-425-705-2686 Peering: peering(a)microsoft.com ASN: 12076 APEv4: 192.203.154.162 APEv6: 2001:07FA:0004:c0cb::9aa2 WIXv4: 202.7.0.220 WIXv6: 2001:07FA:0003:ca07::00dc Full details at http://as8075.peeringdb.com To establish a session please set up your side and reply with the details below to peering(a)microsoft.com ASN: IPv4 address: IPv6 address: Approx number of IPv4 prefixes: Approx number of IPv6 prefixes: AS macro: NOC email: NOC phone: Peering email: Regards, -Kevin

1 0

NZNOG13 Update - Space still available in workshops and tutorials
by NZNOG Announcements 14 Jan '13

14 Jan '13

*NZNOG13 RegistrationsThis year, the 10th year of standalone NZNOG meetups is looking to be a cracker. The conference itself is now sold out but we do have a waitlist and some places may become available. You can sign up to the conference waitlist at: http://nznog.org/register We still have places on the tutorials and workshops, so if you are interested you might want to get in sooner than later. Tutorials - Wednesday the 23rd of January - Mikrotik wireless and routing systems (full day) - APNIC - Internet Resource Management IRMe (half day) - APNIC - DNSSEC (half day) - IPv6 Security - Karl Auer, Into6 (half day with morning and afternoon sessions) - Out of Band Management - OpenGear (half day) Workshops - Monday the 21st - Wednesday the 23rd JanuaryIPV6 BGP Routing - Philip Smith (APNIC) and Daniel Griggs (PCH) This workshop is targeted at engineers and network administrators from both ISPs and SOHO/enterprise networks. - ISP network topology overview - ISP IP Addressing Plan - Introduction of Internet routing infrastructure - 2 Byte and 4 Byte AS Numbers - BGP operation - Understanding BGP metric and path selection process - Configuring BGP within an AS [iBGP, route reflector] - Configuring BGP between ASes [eBGP] - Controlling routing update traffic [prefix list, distribute list, route map] - Route Summarization with BGP - BGP Traffic engineering [MED, Local Pref, AS-Path prepend] It is highly recommended that participants bring their own laptop computers (At least Pentium 4, 1gb Ram, DVD drive, with administrative access to system) to practice the lessons learned during the workshops. DNSSec Workshop - Phil Regnauld (NSRC) and Joe AbleyThe course is designed for network engineers, systems administrators, and anyone who is involved in managing DNS operations. - DNS concepts - BIND (DNS server) and Resolver (DNS client) configurations - Reverse DNS - DNS Security - TSIG - DNS security extensions (DNSSEC) - DNS and IPv6 It's more DNSSEC centric than a DNS operations 101 course. Goals - Learn about the real world threats that exploit DNS weaknesses - Understand the risks you run when your DNS isn't secured - Learn about the security extensions for DNS: DNSSEC - Enable signing & validation in the organisation - Learn about the impact of DNSSEC on one's DNS infrastructure - Help participants take the next step, whether it involves deploying their own signing solution, acquiring a vendor based solution, or using a third party service Topics zone signature, key management, automated DNSSEC management using BIND & OpenDNSSEC, Hardware Security Modules (HSM) presentation on key ceremonies, DNSSEC Practice Statements Sponsors NZNOG are grateful for the support we receive from our sponsors. Platinum Sponsor - Vocus Communications Gold Sponsors - Go Wireless NZ - Internet New Zealand - Network Hardware Resale - Alcatel Lucent - Citylink - Kordia - FX Networks - REANNZ Silver Sponsors - Fortinet - Opengear - Brocade - ISPANZ Bronze Sponsors - Allied Telesis Workshop Sponsor - Internet New Zealand For further information: To register: http://www.nznog.org/register Follow us on Twitter: @NZNOG Susbscribe to the NZNOG mailing list: http://www.nznog.org/mailing-list Visit the conference website: http://nznog.org <http://2012.nznog.org.nz/> For general enquiries info(a)nznog.org*

1 0

National Library of New Zealand - Whole of Domain Web Harvest 2013
by Jay Gattuso 14 Jan '13

14 Jan '13

Hi All, This is a quick reminder that the National Library of New Zealand about to embark on its 2013 Whole of Domain Web Harvest. Our partners, the Internet Archive will be commencing a test harvest within the next 24 hours. This test harvest is expected to last a few days, and will attempt to complete a basic resources discovery for all the URIs included in the seedlist for the harvest. >From this test we expect to identify: (1) URIs that are no-longer active, (2) robust approximations for storage requirements and (3) URIs that could result in significant quantities of resources being harvested. These results will be used to hone the seed list in preparation for the harvest proper (running between the 4th and 22nd of February 2013). Please refer to this link for more information: http://natlib.govt.nz/publishers-and-authors/web-harvesting/2013-nz-web-har… Or feel free to drop me a line if you have any questions. Best, Jay Gattuso 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

[offer] Accommodation NZNOG
by Joel Wirāmu Pauling 13 Jan '13

13 Jan '13

Kia ora, just putting out an offer of (free) accommodation for this years conference. We have 1 queen guest bedroom and a bed settee . Reply off list it you want to take up the offer. -Joel http://linkedin.com/in/aenertia http://couchsurfing.org/people/aenertia

1 0

Call for APNIC 35 Policy Proposals
by Skeeve Stevens 12 Jan '13

12 Jan '13

Dear Colleagues, Is there something in APNIC's policies that you think needs an update, could be improved or changed for the better? If so, then why don't you submit a policy proposal for APNIC 35? If you are not sure whether your policy idea has merit or is covered by an existing one, please seek some advice from the Chairs or the community in general by posting to this mailing list. You never know until you ask. Policy proposals will need to be submitted before Wednesday 30 January 2013 to be considered for consensus at the APNIC 35 Policy SIG in Singapore 25 February - 1 March 2013. There are two ways to submit a policy proposal: 1. Use the online form at: http://www.apnic.net/community/policy/proposals/submit 2. Send your proposal in TEXT format to <policy at apnic dot net>. We encourage you to submit proposals well before the deadline. This gives the community more time to consider your proposal and gives you the opportunity to amend your proposal, if needed, based on the community's feedback. More information ---------------- APNIC's policy development process is explained at: http://www.apnic.net/policy View current and past policy proposals at: http://www.apnic.net/policy/proposals Learn more about APNIC 35 at: http://conference.apnic.net/35 We look forward to seeing you in Singapore APNIC Policy SIG Chairs Andy, Skeeve, and Masato * * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Brocade - Cloud ----- Check out our Juniper promotion website! eintellego.mx Free Apple products during this promotion!!!

1 0

Looking for Juniper person experienced with vlan bridging on J Series
by Bryan Tabb 09 Jan '13

09 Jan '13

Hi As subject mentions looking to get some help with what is possible, if what is envisaged is a good or bad idea and some config. Suspect this will only take an hour or two. If interested please drop me a line with contact details. Thanks Bryan Tabb

1 0

NZIX OpenFlow adventures phase 2
by Dean Pemberton 09 Jan '13

09 Jan '13

Hi Everyone, So the OpenFlow router has been up for a wee white now so it seemed about time to let you all poke at it. Phase 2 of the project is to: Deploy an OF switch on an exchange point which can function as a route server. This switch should be able to BGP peer with any peers which currently use the exchange and allow for the exchange of IPv4 prefixes as required. I've used the information on the WIX Peer list webpage (http://wix.nzix.net/peers.html) to pre-configure passive[1] BGP peering sessions for all existing WIX participants. So feel free to use your existing WIX IP addresses and AS numbers to connect to IP: 202.7.0.119 Aut-num: 9483 Things to look for: 1) It should pass you the routes that it learns from the route servers with the Flatnet AS in the path but with the original next hops. This longer path should mean that you won't explicitly prefer the routes from me. Bit of safety there. 2) It will pass you any other routes that people pass me directly. As I mentioned before we've got a few more plans. The next phase will start to take us a bit beyond what the current exchanges offer. In the new year we are going to deploy a similar switch at the APE. This hardware will become part of the single SDN controlled switch that we currently have in Wellington. When you peer with the OpenFlow switch at the WIX you'll get APE prefixes as well. Peer at the APE, you'll get WIX prefixes. Once we can get some traffic on the fabric and a presence at multiple places then we can really start to innovate. . BGP prefix communities based on the millisecond difference between your peering port and the prefix next hop . BGP aware RPF on the exchange (solves the pointing default problem) Got any other ideas. Throw them in the mix and we'll see what we can do. Have a Merry Christmas everyone. Regards, Dean [1] Passive means that I'll never reach out and initiate a session with you. You need to initiate the session with me. Just safer incase people think that I'm TCP Port 179 hax0r-ing them.

8 14

NZNOG13 - Register now and get a free Mikrotik Access Point
by NZNOG Announcements 08 Jan '13

08 Jan '13

*NZNOG13 Is Upon Us Register early for NZNOG13 and receive a free Mikrotik wireless access point and router!! The New Zealand Network Operators Group (NZNOG) is holding their annual conference and training workshops and tutorials in Wellington from the 21st to 25th January 2012. Training workshops and tutorials run from the 21st to the 23rd of January. The conference is then held on the 24th and 25th of January. Our annual conference provides both an opportunity to exchange technical information, and a high-value opportunity for NZ’s networking staff to ‘network’ amongst themselves. This is New Zealand’s only technical networking conference. The event will be held at the Mecure Hotel in Wellington. Accommodation is available on site at a discounted rate for conference attendees as well as in the immediate area. Registrations are open. The cost of attendance has been confirmed at $250, students receive a 60% discount and a fellowship scheme exists should you require assistance to attend. Conference Presentations 24-25th January Confirmed presenters for NZNOG13 include: Scott Bartlett (Orcon) - UFB one year in Andrew McDonald (Vodafone) - RBI Wholesale 12 months. Colin Dyer (GeoNet) and Ewen McNeill (Naos, Consultant) - Geonet: 1pps to 10,000 hits/second. Beatty Lane-Davis - SDN: accelerating the pace of evolution in packet and transport networks Sam Russell (REANNZ) - Thimble: OpenFlow-enabled device David Brownlie (REANNZ) - perfSONAR for measuring performance, and troubleshooting. Donald Love - UFB realities Philip Smith (APNIC) - IPv4 / IPv6 route table analysis for NZ Phil Regnauld (NSRC) - DNSSEC George Michaelson (APNIC) - Last words on IPv6 Stu Fleming (WIC) - On being a WISP Plus updates from NZRS, APNIC, CityLink, IPv6 Task Force, WAND and InternetNZ. Tutorials - 23rd January - Mikrotik wireless and routing systems (full day) - APNIC - Internet Resource Management IRMe (half day) - APNIC - DNSSEC (half day) - IPv6 Security - Karl Auer IPv6Now (half day) - Out of Band Management (TBC) Workshops - 21st - 23rd January IPV6 BGP Routing - Philip Smith (APNIC)This workshop is targeted at engineers and network administrators from both ISPs and SOHO/enterprise networks. - ISP network topology overview - ISP IP Addressing Plan - Introduction of Internet routing infrastructure - 2 Byte and 4 Byte AS Numbers - BGP operation - Understanding BGP metric and path selection process - Configuring BGP within an AS [iBGP, route reflector] - Configuring BGP between ASes [eBGP] - Controlling routing update traffic [prefix list, distribute list, route map] - Route Summarization with BGP - BGP Traffic engineering [MED, Local Pref, AS-Path prepend] It is highly recommended that participants bring their own laptop computers (At least Pentium 4, 1gb Ram, DVD drive, with administrative access to system) to practice the lessons learned during the workshops. DNSSec Workshop - Phil RegnauldThe course is designed for network engineers, systems administrators, and anyone who is involved in managing DNS operations. - DNS concepts - BIND (DNS server) and Resolver (DNS client) configurations - Reverse DNS - DNS Security - TSIG - DNS security extensions (DNSSEC) - DNS and IPv6 Social Events Wednesday Night EventThe Southern Cross<http://www.thecross.co.nz/>bar on Abel Smith Street has been confirmed for the networking event sponsored by Network Hardware Resale. The Southern Cross (affectionately known as 'The Cross') is somewhat of an icon in Wellington with unique decor and an impressive range of boutique beers - not to mention their legendary stone grills and Kiwiana inspired menus. Kick off will be 6PM, Wednesday the 23rd of January. Thursday Night Conference DinnerOne of the highlights of the NZNOG conferences each year is the conference dinner which provides an opportunity for attendees to get together, relax and enjoy a night out. The 2013 event will be held at Zealandia: The Karori Wildlife Experience<http://www.visitzealandia.com/what-is-zealandia/zealandia-in-a-nutshell/>and promises to be a great night! Buses will leave the conference venue for Zealandia at 6PM on Thursday the 24th of January. Accommodation Options Mercure is offering an exclusive room rate for NZNOG attendees starting from: $115.00 room only $135.00 bed and breakfast for one guest, 1 room $155.00 bed and breakfast for two guests, 1 room * Rates include GST. * Rates are per room per night, based on single, double or twin share occupancy To book contact Dean on Dean.Grocott(a)accor.com and mention you are with attending NZNOG 2013 http://www.accorhotels.com/gb/hotel-1991-mercure-wellington/index.shtml Multiple other accommodation options within Wellington exist. Sponsors NZNOG are grateful for the support we receive from our sponsors. Platinum Sponsor - Vocus Communications Gold Sponsors - Go Wireless NZ - Internet New Zealand - Network Hardware Resale - Alcatel Lucent - Citylink - Kordia - FX Networks - REANNZ Silver Sponsors - Fortinet - Opengear - Brocade - ISPANZ Bronze Sponsors - Allied Telesis Workshop Sponsor - Internet New Zealand For further information: To register: hhttp://www.nznog.org/register Follow us on Twitter: @NZNOG Susbscribe to the NZNOG mailing list: http://www.nznog.org/mailing-list Visit the conference website: <http://nznog.org.nz/>http://nznog.org<http://2012.nznog.org.nz/> For information in fellowships info(a)nznog.org*

3 2

Re: [nznog] NZIX OpenFlow adventures phase 2
by Josh Bailey 08 Jan '13

08 Jan '13

Hi Nathan; Hardware flows != OpenFlow flows. OpenFlow is an API. Some reflection on these statements may suggest an answer. Thanks, == If you hit the limit of number of flows, what happens? Does it reject the flow, or does it delete older ones to make room for it? Given there is no default route, what happens if you get a packet that doesn't match a flow? Does it drop it, or punt it to the controller? (ie. is there a default flow to drop) If it deletes older flows, and punts non-matching packets to the controller, that sounds like there's a potential for really bad performance spikes as you approach the upper limits of the flow table. If it deletes older flows and drops non-matching packets, then that's worse. If you simply reject new flows, then that's a bit better, but you've got to make sure that the route reflectors never re-advertise prefixes unless they're installed in to the flow tables successfully, or you drop packets, or punt them to the controller as above. Some interesting issues to consider! Agreed re. VPLS/etc. - but you've got to make sure your switches have reliable connectivity to your controller(s). In a network like WIX, that might be hard, not sure.

4 4

Re: [nznog] Temporary fibre cable across Wanganui river near Harihari - anybody got photos?
by Richard Naylor 08 Jan '13

08 Jan '13

At 11:38 a.m. 3/01/2013, Sam Russell wrote: >I'm sure this looks hilarious, does anyone have pictures of their >thrown fibre? You live a sheltered life and have been denied the goods things.. A good lineman will put a throw line between the two wires you ask for at the top of a pole with great ease. These days a cherry picker seems to be the answer to everything high up. My old throw line finally broke and split. Come to NZNOG-13 and buy me a beer and I'll tell you how it was made. These days I'm a little more elegant and carry a bow and arrow, with fishing line, but its really not as good as a throw line and only really good at blasting through trees. In the old days (before helicopters were cheap to hire), power boards got cables across rivers, gullys and valleys etc using rockets with a draw line. Of course, the drawline was sometimes forgotten, completely by accident, of course. In much the same way it was strange how the 11kV earth sticks kept falling into streams and rivers that had fish in them. Very strange. While a good linesman was amazing, us mere mortals caused much hilarity and rolling around laughing by the gang. Working life used to be so much fun - actually it still is. Leave the office for a day or two and experience Layer 0 engineering..

10 10

Microsoft Office 365 Routing Issues with Telecom/Xtra/Global Gateway?
by Regan Murphy 07 Jan '13

07 Jan '13

Going to get my clients to attempt to log this with Telecom, but it sounds like a widespread problem developing.... http://www.geekzone.co.nz/forums.asp?ForumId=86&topicid=113151 -- Regan

2 1

alcatel.co.nz domain
by Simon Lyall 07 Jan '13

07 Jan '13

This domain seems to be expiring... Just noticed cause a bunch of people are subscribed to this mailing list using it. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 2

Re: [nznog] alcatel.co.nz domain
by Peter Lambrechtsen 07 Jan '13

07 Jan '13

I've forwarded this onto a number of friends & colleagues of mine in ALU. Hopefully one of them will find someone who can sort it... Sent from my HTC Wildfire S on Telecom's XT mobile network. ----- Reply message ----- From: "Simon Lyall" <simon(a)darkmere.gen.nz> To: "nznog" <nznog(a)list.waikato.ac.nz> Subject: [nznog] alcatel.co.nz domain Date: Tue, Jan 8, 2013 9:54 am This domain seems to be expiring... Just noticed cause a bunch of people are subscribed to this mailing list using it. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Authoritative DNS config
by Richard Hector 06 Jan '13

06 Jan '13

This isn't an NZ specific question, and also perhaps a bit basic; hope that's ok. Packaged (debian, ubuntu anyway) versions of BIND come with various default zones configured - localhost, broadcast and root hints. Are any of these actually necessary for an authoritative-only name server? It seems to me they're mostly/only useful for short-circuiting simple/standard queries on a resolver. Is that right? Not having any other zones than my own in my config would make it somewhat easier to configure views. Thanks, Richard

3 3

Temporary fibre cable across Wanganui river near Harihari - anybody got photos?
by Sam Russell 02 Jan '13

02 Jan '13

I'm sure this looks hilarious, does anyone have pictures of their thrown fibre? Also beer -- Sam Russell Network Engineer Research & Education Advanced Network NZ Ltd ddi: +64 4 913 6365 mob: +64 21 750 819 fax: +64 4 916 0064 http://www.reannz.co.nz

1 1

Fwd: NZIX OpenFlow adventures phase 2
by Dean Pemberton 02 Jan '13

02 Jan '13

---------- Forwarded message ---------- From: *Dean Pemberton* Date: Wednesday, January 2, 2013 Subject: NZIX OpenFlow adventures phase 2 To: Truman Boyes <truman(a)suspicious.org> Cc: nznog <nznog(a)list.waikato.ac.nz> Nox at the moment. Happy to have a chat about different controllers if you've got a preference. Dean On Tuesday, January 1, 2013, Truman Boyes wrote: > Hey Dean, > > What are you using for the OFP controller? NOX/POX/Big Switch? > > Cheers, > Truman > > > On 18 Dec, 2012, at 10:40 PM, Dean Pemberton wrote: > > > Hi Everyone, > > > > So the OpenFlow router has been up for a wee white now so it seemed > > about time to let you all poke at it. > > Phase 2 of the project is to: > > Deploy an OF switch on an exchange point which can function as a route > server. > > This switch should be able to BGP peer with any peers which currently > > use the exchange and allow for the exchange of IPv4 prefixes as > > required. > > > > I've used the information on the WIX Peer list webpage > > (http://wix.nzix.net/peers.html) to pre-configure passive[1] BGP > > peering sessions for all existing WIX participants. > > > > So feel free to use your existing WIX IP addresses and AS numbers to > connect to > > > > IP: 202.7.0.119 > > Aut-num: 9483 > > > > Things to look for: > > 1) It should pass you the routes that it learns from the route > > servers with the Flatnet AS in the path but with the original next > > hops. This longer path should mean that you won't explicitly prefer > > the routes from me. Bit of safety there. > > 2) It will pass you any other routes that people pass me directly. > > > > As I mentioned before we've got a few more plans. The next phase will > > start to take us a bit beyond what the current exchanges offer. > > > > In the new year we are going to deploy a similar switch at the APE. > > This hardware will become part of the single SDN controlled switch > > that we currently have in Wellington. > > When you peer with the OpenFlow switch at the WIX you'll get APE > > prefixes as well. Peer at the APE, you'll get WIX prefixes. > > > > Once we can get some traffic on the fabric and a presence at multiple > > places then we can really start to innovate. > > > > . BGP prefix communities based on the millisecond difference between > > your peering port and the prefix next hop > > . BGP aware RPF on the exchange (solves the pointing default problem) > > > > Got any other ideas. Throw them in the mix and we'll see what we can do. > > > > > > Have a Merry Christmas everyone. > > > > > > Regards, > > Dean > > > > > > > > [1] Passive means that I'll never reach out and initiate a session > > with you. You need to initiate the session with me. Just safer > > incase people think that I'm TCP Port 179 hax0r-ing them. > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > -- Regards, Dean

2 1

connection issues to ftp.nz.debian.org
by Hugh Davenport 27 Dec '12

27 Dec '12

Hey, On two of my servers running with different ISP's I've noticed connection issues in the last few days to ftp.nz.debian.org. I can ping it, but can't connect via HTTP or FTP. This is both on my flat server (Snap) and my parents server (Slingshot). When I try from work, which is connected to the WIX, it works fine. hugh(a)hugh-laptop:~$ ping -c 1 ftp.nz.debian.org PING ftp.citylink.co.nz (202.7.6.9) 56(84) bytes of data. 64 bytes from ftp.citylink.co.nz (202.7.6.9): icmp_req=1 ttl=60 time=13.7 ms --- ftp.citylink.co.nz ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.792/13.792/13.792/0.000 ms hugh(a)hugh-laptop:~$ telnet ftp.nz.debian.org 80 Trying 202.7.6.9... telnet: Unable to connect to remote host: Connection timed out hugh(a)hugh-laptop:~$ telnet ftp.nz.debian.org 21 Trying 202.7.6.9... telnet: Unable to connect to remote host: Connection timed out hugh(a)hugh-laptop:~$ On an interesting note, I tried using debian.ihug.co.nz/debian which is listed as a secondary server on http://www.debian.org/mirror/list. This gave me the error. hugh(a)hugh-laptop:~$ sudo apt-get update Hit ftp://debian.ihug.co.nz wheezy InRelease E: Release file for ftp://debian.ihug.co.nz/debian/dists/wheezy/InRelease is expired (invalid since 83d 20h 47min 21s). Updates for this repository will not be applied. hugh(a)hugh-laptop:~$ When I try using netselect-apt I get the following: hugh(a)hugh-laptop:~$ sudo netselect-apt wheezy <snip> The fastest 10 servers seem to be: http://ftp.nz.debian.org/debian/ http://debian.mirror.uber.com.au/debian/ http://mirror.transact.net.au/debian/ http://mirror.cse.unsw.edu.au/debian/ http://mirror.optus.net/debian/ http://mirror.optus.net/debian/ http://debian.nautile.nc/debian/ http://ftp.iinet.net.au/debian/debian/ http://mirror.waia.asn.au/debian/ http://ftp.au.debian.org/debian/ Of the hosts tested we choose the fastest valid for HTTP: http://ftp.nz.debian.org/debian/ Writing sources.list. Done. hugh(a)hugh-laptop:~$ Any thoughts? It used to work fine, and has only cropped up in the last few days. Cheers, Hugh

5 4

TV3 Ondemand Contact
by Ray | Taylor Communications 21 Dec '12

21 Dec '12

Would there be any list members inside Media works by any chance, or would someone have a contact who I can speak to? I seem to be having an issue with TV3 ondemand on our network - the preroll plays but the programme itself does not. Anyone that replies when I click "report issue" doesn't seem to be of any help. We have our own ip assignments from apnic. Maxmind and other such geolocation databases are indeed showing Napier as the location though this took 3 months when we got them a year ago. I was thinking it could possibly be an issue inside our main router with the RTMP protocol but I have proved it isnt. - When I go to http://nzcontent.mediaworks.co.nz I can play the http demo stream, but not the rtmp stream - When I go to http://www.etvlive.gov.et/ I can play both the http and the rtmp stream. This is just some overseas organisation who has a web facing adobe media server similar to tv3's So next I thought there could possibly be a firewall or protocol block of some sort - I can telnet into nzcontent.mediaworks.co.nz on port 1935 without an issue. Its been bugging me since we changed over to our own block of ip addresses with the occasional subscriber complaint about the tv3 service. So anyone you can refer me to inside TV3/mediaworks that can help (beyond the tier1 helpdesk monkeys) would be much appreciated. Ray Taylor Taylor Communications ray(a)ruralkwii.com 06-929-9082 021-483-280 www.taylorcom.co.nz

3 2

My Experiences with 3G (aka 2Degrees are pathetic)
by Skeeve Stevens 17 Dec '12

17 Dec '12

Hey all, So I arrive in Queenstown, go to Dick Smith, and pick up 2 TelecomXT Sims and a 2Degrees Sim. Also bought $270 worth of recharge vouchers. Telecom XT wasn't too much of a problem... ring up a number and recharge the sims.... worked fine. 2Degres. Useless bloody idiots who if I had the time I would lodge a complaint with whatever authority there was in NZ for doing do. So, got their Nano Sim, put it in the iPad Mini... and nothing. Says it sees the 2Degrees towers... but nothing. Won't activate. Call them, they say I need to put it in a phone with Nano slot (iPhone5) to activate... I didn't bother bringing the 5 because I had the Mini. Called last night, they took details, said to call back in the morning. I called this morning, waited an hour for these idiots to figure out why I or they couldn't activate it... and even got the comment when I said that if they are selling these for iPad Mini's and there is no way to activated they said 'Seems a bit stupid doesnt it'. They said someone would call me back... they didnt. I called back tonight, chick read through all the notes... says she couldn't do anything and the escalation meant I would receive a call back by the 21st of December. WTF?! These people are totally useless. Now the chick is telling me that Dick Smith 'should have' known.... really? Dick Smith said they have no idea and get no training whatsoever from 2Degrees, or any of the sims they sell. So my two Telecom XT work fine, but still needed a call to activate then... but 2Degrees is the biggest joke ever. They have no details, instructions or ANYTHING at all about activating sims on iPad's or iPad Mini's. They had the nerve to say I should go back to Dick Smith and get them to activate it... but didn't want to pay the $60 in taxi fare. If anyone knows anyone up there, feel free to forward them my email to them. This is the worst customer experience ever and I will be telling everyone I know not to use them. *frustrated* * * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Brocade - Cloud ----- Check out our Juniper promotion website! eintellego.mx Free Apple products during this promotion!!!

4 3

3G in the South
by Bevan McNaughton 16 Dec '12

16 Dec '12

Down here it seems that Vodafone is the fastest and ha good reliability (little overloading and good consistency), however doesn't have the best coverage. Telecom XT has better coverage but speed and reliability isn't as good. Vodafone may be your best bet. It deems to be consistent enough throughout Qtown, Dunedin & Invercargill (am doing work from those centres with Vodafone on and off often). Regards, -- Bevan McNaughton SouthLoop Invercargill

12 18

Re: [nznog] 3G in the South
by Richard Naylor 16 Dec '12

16 Dec '12

At 02:09 p.m. 16/12/2012, you wrote: >Is it just me or is this the most pathetic options I've ever seen? >I'm used to be able to get pre-paid data in Australia, like 12Gig or >$120 or something. >These plans are offering tiny little megs... "Pathetic" is a good description of the major carriers. Telecom do a 4GByte plan and in December seem to do a 2 for 1 deal. We get 8GB per stick from them Vodafone seem to think 4Gbyte is awesome. We carry a "reverse cell-site" that has sicks on both carriers. It uses external aerials to get that little bit extra. I used it in Wanaka in Jan just before NZNOG and Telecom wasn't too bad. Vodafone looked like it had good download, but it was only in short burst stuff. Sustained thru put was mediocre. We used satellite for the job. The 3G rig was just for us at the motel FYI - identical USB sticks sitting side by side have different performance figures. They're really made for metro areas with "immersive" coverage and in areas with less coverage performance is a struggle. For the Wanaka job, the producer is talking about using a bonded 3G rig to replace microwave link from chopper. It will be interesting.

1 0

3G in the south
by Ernest Cunningham 15 Dec '12

15 Dec '12

Just cut all the plastic around the chip on any 2degrees sim and it will fit in your iPhone 5 fine and work perfect. Ernest Sent from my iPhone

1 0

Advisory - D-root is changing its IPv4 address on the 3rd of January
by Sebastian Castro 13 Dec '12

13 Dec '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Original message can be found here https://lists.dns-oarc.net/pipermail/dns-operations/2012-December/009428.ht… - ------------------------------------------- Advisory ? D-root is changing its IPv4 address on the 3rd of January. This is advance notice that there is a scheduled change to the IPv4 address for one of the authorities listed for the DNS root zone and the .ARPA TLD. The change is to D.ROOT-SERVERS.NET, which is administered by the University of Maryland. The new IPv4 address for this authority is 199.7.91.13 The current IPv6 address for this authority is 2001:500:2d::d and it will continue to remain unchanged. This change is anticipated to be implemented in the root zone on 3 January 2013, however the new address is currently operational. It will replace the previous IP address of 128.8.10.90 (also once known as TERP.UMD.EDU) We encourage operators of DNS infrastructure to update any references to the old IP address, and replace it with the new address. In particular, many DNS resolvers have a DNS root ?hints? file. This should be updated with the new IP address. New hints files will be available at the following URLs once the change has been formally executed: http://www.internic.net/domain/named.root http://www.internic.net/domain/named.cache The old address will continue to work for at least six months after the transition, but will ultimately be retired from service. - --------------------------------------------------- Kind Regards, - -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDLakMACgkQWyqRrHcQWTmrzQCfeDQ0SZX9Wlf3unUUgu5f0pVZ ODQAn3ETzMd0WsaynqnJzX2bHPlPOF8y =5dXZ -----END PGP SIGNATURE-----

1 0

NZ scores first OpenFlow controlled connection to an IX
by Dean Pemberton 10 Dec '12

10 Dec '12

Hi all, Just wanted to share with you all what we think is a world first, right here in New Zealand. Today New Zealand can boast the first SDN controlled OpenFlow switch BGP peering with a public Internet Exchange. Because you're all geeks, I've decided to write the rest of the email as a FAQ: Q: What is SDN and/or OpenFlow? A: It's a new way of thinking about and building network devices. It stands for Software Defined Networking. It's basically a way to separate the control plane from the data plane in order to allow you unprecedented control over what your network can do, while still keeping it blindingly fast. You let the Software do what it's good for (running routing protocols, making policy decisions) and you let the Hardware do what it's good at (forwarding stuff at wire speed, zoooooom!). A match made in heaven Have a look at the wikipedia page http://en.wikipedia.org/wiki/Software-defined_networking Or this presentation from OpenFlow http://www.openflow.org/documents/OpenFlow_2011.pps Q: Why do I care? A: SDN and OpenFlow allow you much more control and flexibility over your network. It's a new technology however, and people are yet to begin playing with it. Q: Sounds like one of those scary technologies like IPv6 and DNSSEC. A: Well if you mean that other people are doing it while you're ignoring it and hoping that it will go away... Then you're right. =) Just like IPv6, before we saw people willing to deploy it on their networks they needed to get some experience with how it worked. We're at that stage with SDNs at the moment. It is because of this need for more experience and public awareness that we've gone ahead with this little project. Q: So what exactly have you done. A: We've deployed an OpenFlow controlled switch on the WIX and along with an OpenFlow controller built a BGP capable router. Q: Details? A: From the WIX looking glass Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 202.7.0.119 4 9483 24345 27397 0 0 0 07:21:59 1 Q: So what? Is that it? A: Hardly. We've got some more phases that we want to develop, so I guess this is a watch this space. Over the next few months, we'll be working on extending past this single box with a view to demonstrating to the NZ Internet community, and beyond, whats really possible with an SDN. Basically we don't want New Zealand falling behind whats happening in the rest of the world. Q: We're not ready for this. It's scary, poke it with a stick!!! A: Thats fine. We've chosen to use New Zealand as the initial production deployment here. But if it looks like thats not going to get the traction needed, then there are other places which this would work in. Lets make this a good Kiwi development moment though. Remember how we're so proud of telling people we had EFTPOS so long before anyone else. Q: Pfffft I've heard of this. It doesn't work! It's not production ready A: Hi, Welcome to the conversation. You're just the sort of person we need paying attention. We're doing this so that people arn't LISTENING about SDN, but are actually seeing it WORK. In a real world production setting. We hope you can stay for the rest of the show. Q: So who else does SDNs. This sounds a little too much like witchcraft to me. A: Well from back in the days of the Juniper M-Series people have been separating Routing Engines from Packet Forwarding Engines. We then started to see multi chassis versions. This is just an extension of the same sort of concept. There are some organisations which run huge-scale SDN style networks. Maybe you've used a search engine or mail platform from one... Q: This sounds like a pretty heavy sales pitch. What are you pushing? A: CYNIC! Nothing. Just like the reason I'm pushing people to think about IPv6 and DNSSEC, I want to see the New Zealand Internet community as a technology innovator, not just someone who swallows down the latest vendor slide-ware. And hey if SDN doesn't work then at least New Zealand still gets to write the book on it. Q: Sounds cool, can I help? A: Sure, anyone's welcome to come and learn along with the rest of us. Drop me a line if you think you can help and we'll see where we can fit you in. As a starter I'm looking for between 1 and 3U of space in Auckland with access to the APE. Q: Where can I hear more. A: If you're lucky I might do a lightning talk on where we've got to and where we're going at the NZNOG conference. Thanks to Prophecy Networks, REANNZ, VUW, Waikato University, Citylink, FX Networks and others, for their contributions and support in getting the project to where it is today and for not wanting it to stop there! Regards, Dean

3 4

Commsday: Russia, allies back off proposal to extend regulation across Internet
by Skeeve Stevens 10 Dec '12

10 Dec '12

Hey all, This was in this mornings Commsday. Seems like great news ...Skeeve ============================================== *Russia, allies back off proposal to extend regulation across Internet* * * In an extraordinary development late last night, Russia and its allies China, Saudi Arabia, Sudan, Egypt and the United Arab Emirates withdrew a radical proposal to overhaul international telecommunications regulations which would have given national governments sweeping new powers to regulate global ICT service providers such as Facebook and Twitter as well as Internet governance. CommsDay was told by sources that International Telecommunications Union secretary-general Hamadoun Toure personally intervened to persuade the Russians to withdraw their proposal following American threats to walk out of the World Conference on International Telecommunications if the revisions were considered for ratification. In a fast moving night:  United States delegation chief Ambassador Terry Kramer denied comments attributed to him by Dow Jones that his country would walk out of the conference if it sought to regulate Internet content. CommsDay has confirmed with Dow Jones that he made the comments now denied.  Russia withdrew, without explanation, a proposal with China, Saudi Arabia, Sudan, Egypt and the United Arab Emirates that would massively increase the ambit of international telecommunications regulations to cover almost all telecommunications and Internet activities. The proposal, leaked on Saturday, was disowned by a member of the Egyptian delegation which last night made a strong statement in favour of Internet freedom. This hinted at serious dysfunction behind the Russian-led coordination efforts.  A steering committee was immediately convened to get the conference, in danger of collapse, back on track. There was reportedly applause in the committee room as progress was made, especially on the detail of who the revised regulations might apply to. However access to the room was blocked by guards. Previously there were concerns that loose wording could extend the ambit of the regulations as far as users of virtual private networks and ham radio operators. The secretive machinations of a working group—the so-called Committee 5—will now apparently give way to open plenary sessions. Observers tell CommsDay that the radical Russian proposals had the effect of galvanising the conference into action. Although Russia and allies have formally withdrawn their proposed treaty revision, other countries may still attempt to advance some of the main points. Australian delegate Dr Bob Horton is believed to have played a major role last night, chairing an ad hoc meeting attempting to resolve the arguWCIT bombshell: SG averts collapse of conference LEAKED: The Russia-led proposalent over how Internet traffic is charged. African states and their supporters seek to restore the old voice traffic settlements regime for Internet traffic to provide a revenue source. The result of these efforts was unclear as we went to press 5AM Australian Eastern Summer Time. CommsDay was told last night that secretary general Toure personally called top Russians and asked them to back off because this would split the conference nproductively. “The head of delegation, considered a young tyro, apparently acted on his own and they shot him down. Partial confirmation is that Touré personally delivered the news to regional meetings before it was announced.” our source said, emphasising this was not officially confirmed. CommsDay sources say that the US delegation’s hundred-plus members fanned out to meet with almost every participating country in a last ditch effort to block the Russia-led move over the weekend. On sheer numbers, the Russia-led proposal would probably win a majority vote but there is an overriding preference by the ITU to forge a consensus on the eventual outcome. The alternative was a walkout by the US delegation and potentially some of its core allies. According to the .nxt website, Poland had also threatened to walk from the event. Australia generally supports the US position backing the status quo on Internet governance. CIVIL SOCIETY OBJECTS: Meanwhile, a group of civil society organisations from the US, Europe, India and Africa has slammed the ITU and WCIT process for a lack of transparency and input from outside groups. In a letter to the ITU, they state “Now that the conference is in session, we wish to call your attention to three immediate and pressing matters: the lack of any official standing to the public comments solicited prior to WCIT at the ITU’s invitation; the lack of access to and transparency of working groups, particularly the working groups of Committee 5; and the absence of mechanisms to encourage independent civil society participation.” ======== To subscribe to Commsday, please visit: http://www.commsday.com/ * * *Skeeve Stevens, CEO - *eintellego Pty Ltd <http://www.commsday.com/> <http://www.commsday.com/> <http://www.commsday.com/>skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Brocade - Cloud ----- Check out our Juniper promotion website! eintellego.mx Free Apple products during this promotion!!!

1 0

.nz Second Key Generation Procedure
by Sebastian Castro 06 Dec '12

06 Dec '12

To the Technical Community: On December 5th 2012, NZRS successfully carried out the Second Key Generation Procedure. During this event, the cryptographic keys required to sign the .nz zones with DNSSEC for the next year were created. During the procedure NZRS also purged the keys that were not longer needed due to key rollovers. More details and links to the documentation trail created by the procedure can be found at https://nzrs.net.nz/content/second-key-generation If you have any questions, feel free to reply to this message or contact us privately. Have a great weekend, -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

1 0

O/T: Request for hardware - 0.5m or 1m Mini SAS 36-Mini SAS 36
by James Baker 06 Dec '12

06 Dec '12

Sorry for the O/T; we're in a bit of a bind and need to find some internal 0.5m or 1m Mini SAS 36-Mini SAS 36 cables ( http://ultracartcgm.s3.amazonaws.com/TMCSC/1876/sas/internal/minisas36-mini… ) I need 4 but stocks seems to be 1 or less. Or a looong lead time. Does anyone know of any stock or does anyone have any handy? Thanks James

1 0

Telstra / Android updates - CDN issues?
by Leon Strong 04 Dec '12

04 Dec '12

Anyone else using any Telstra ip's that are being served by the Telstra/Google/CDN and noticing all android apps are failing? Notice on the redirector that i'm being directed to tnz1, seems to work fine on any other network. Any telstra peeps reading this hear anything from your side? _____________________________________________________________________________ This email has been filtered by SMX. For more information visit smxemail.com _____________________________________________________________________________

2 2

dmzglobal.ape.nzix.net - Packet Filtered
by Chris Hodgetts 03 Dec '12

03 Dec '12

Hello, I know this might not be the correct forum, but thought I would ask. I am trying to get to a govt. departments website, and its VERY slow.. I am seeing this on a ping and traceroute: chris(a)molly:~$ ping rsm.govt.nz PING rsm.govt.nz (116.89.228.176) 56(84) bytes of data. >From dmzglobal.ape.nzix.net (192.203.154.118) icmp_seq=1 Packet filtered >From dmzglobal.ape.nzix.net (192.203.154.118) icmp_seq=2 Packet filtered >From dmzglobal.ape.nzix.net (192.203.154.118) icmp_seq=4 Packet filtered Traceroute: 1. 192.168.100.1 0.0% 25 0.2 0.2 0.2 0.3 0.0 2. 192.168.1.1 0.0% 25 0.5 1.1 0.5 1.6 0.5 3. llu.bng1.nct.orcon.net.nz 0.0% 25 16.2 18.2 14.2 24.4 3.2 4. xe-2-2-0.cre1.nct.orcon.net.nz 0.0% 25 14.3 19.8 13.7 64.4 13.5 5. ge-0-3-0-0.cre1.sky.orcon.net.nz 0.0% 25 15.5 21.2 13.9 111.3 22.0 6. ??? Not sure if it's me, but it appears to be leaving my network OK .. and either getting lost leaving orcon, or having issues at WIX? Might be MED/RSM but is it normal to have nzix doing that? Cheers, and back to beer on such a lovely day..

3 4

DNS format error: their fault or mine?
by Richard Hector 29 Nov '12

29 Nov '12

Sorry if this is off topic. I'm seeing a bunch of this (and have been for ages) in my bind logs: http://pastebin.com/ydL0RhG4 (sample line for archives, when paste goes away: Nov 28 23:14:58 jet named[28427]: DNS format error from 120.204.202.200#53 resolving ns-os1.qq.com/AAAA: invalid response ) My understanding is qq.com is a Chinese IM service (which my flatmate uses). Dig doesn't tell me about any error; it merely doesn't return any AAAA records. Any suggestions on: - whether I should care, or just filter it out of my logcheck email - whether there's something I can fix - whether there's something I can do to figure out in more detail what's happening Note that this is my caching NS, on my home network (behind NAT) Thanks, Richard

6 9

Fw: [members-discuss] Invitation: The untold history of the Internet by Martin Geddes
by Donald Clark 26 Nov '12

26 Nov '12

Hopefully you'll forgive the cross posting. but if anyone out there wants to defend the honour of TCP, they may want to turn up to this… Lots of Martin's stuff is available on SlideShare if you want to explore... Forwarded message: > From: Vikram Kumar <vikram(a)internetnz.net.nz> > Reply To: InternetNZ Members Discussion List <members-discuss(a)mailman.internetnz.net.nz> > To: InternetNZ Members Discussion List <members-discuss(a)mailman.internetnz.net.nz> > Date: Tuesday, 27 November 2012 3:13:23 PM > Subject: [members-discuss] Invitation: The untold history of the Internet by Martin Geddes > > Hi, > > We are organising a talk by Martin Geddes in Wellington at 5 pm on Tuesday, 11th Dec, at InternetNZ's office. > > Martin will tells us the untold history of the Internet, and the unfortunate design errors now baked into every network router. He will also answer a series of provocative questions about the future. > > Details at https://internetnz.net.nz/news/blog/2012/Invitation-untold-history-Internet… > > We will have pizza after the talk to keep the discussion going. > > Please RSVP if you are coming so there is enough pizza for everyone. Please also invite anyone you think might be interested. > > Thanks and hope to see you then, > Vikram >

2 2

Re: [nznog] NZNOG Digest, Vol 119, Issue 14
by Sean Linton 24 Nov '12

24 Nov '12

Thanks, Sam, David, and Dean - Nothing specific motivated my enquiry. Its good to hear some of your thoughts on the issue. And good to see nznog, and in2security had a presence at NetHui_South over the weekend. Cheers, sean On 19 November 2012 12:00, <nznog-request(a)list.waikato.ac.nz> wrote: > Send NZNOG mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.waikato.ac.nz/mailman/listinfo/nznog > or, via email, send a message with subject or body 'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NZNOG digest..." > > > Today's Topics: > > 1. please keep an eye out (Richard Naylor) > 2. Re: youth outreach? (Sam Sargeant) > 3. Re: youth outreach? (David Robinson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 18 Nov 2012 19:41:24 +1300 > From: Richard Naylor <richard.naylor(a)R2.co.nz> > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] please keep an eye out > Message-ID: <20121118064123.BD29B2A061(a)sif.iconz.co.nz> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > > Just a small advisory. I bought 1.5km of fiber for NetHui this week > and it was stolen from the supplier (Corys/Mastertrade) before I got > there to collect it. Its 12 core D-series, single mode LSZH cable > cut as 2x750m. The CCTV footage shows it stolen from the loading bay. > > So if you get offered some cheap fiber, I'm sure Corys would be very > pleased to hear from you. > > Replacement fiber arrived friday pm in one length. After a lot of > winding and splicing, the van is all loaded ready to roll tomorrow. > > I was suspicious that the folks mad keen on cable laying through the > roaring 40's to South America, had nicked it as a part of their project. > > Richard > > > > ------------------------------ > > Message: 2 > Date: Mon, 19 Nov 2012 09:33:39 +1300 > From: Sam Sargeant <sam.sargeant(a)gmail.com> > To: Sean Linton <sean(a)lpnz.org> > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] youth outreach? > Message-ID: <3D1F2ED3-22BD-4D20-93A8-5B2D3B926153(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > On 17/11/2012, at 11:21 AM, Sean Linton <sean(a)lpnz.org> wrote: > > > How has the NZNOG community previously ensured that when a few key > people decide to do something else the organisation doesn't get into > trouble, so new blood keeps coming through? > > Hi Sean, > > Aside from the team of trustees and conference helpers there's no other > organisation to speak of so I'm assuming that's what we're talking about. > > From what I can see there are a couple of trustees who have been appointed > in the last year. If you missed it during the last NZNOG in Christchurch > I'm sure they'll be happy to introduce themselves. On the organising > committee there have been 3-4 new faces in the last two years before I > stopped doing any of the conference work. > > I don't think these have been community efforts; people on the team have > organised themselves quietly enough that I'd guess the wider community was > unaware of any changes. Perhaps you and the list could give feedback on > this approach? I'm wondering if there was something specific that triggered > your question. > > Sam. > >

1 0

Linux and/or Cisco Engineer Roles in Auckland ?
by Ian Batterbee 24 Nov '12

24 Nov '12

Hi all, I posted on this list in August, and do appreciate the replies I got then, however being still without a job, I'm forced to ask again if anyone knows of any senior network or sysadmin roles in Auckland (preferably CBD area). I have a number years of experience with Cisco kit, Linux scripting/automation/sysadmin, in both education (13 years) and ISP (5 years) environments. Please contact me off list if you know of anything. Thanks

1 0

Domain Registry of America sending out invoices again
by Juha Saarinen 23 Nov '12

23 Nov '12

Just a heads-up... got one in the post yesterday, from "Domain Renewal Group" or domainrenewalgroup.com. The physical address given on the envelope is: 189 Queen St Suite 209 Melbourne 3000 Australia The Registry database contains ONLY .COM, .NET, .EDU domains and Registrars. Registration Service Provided By: Domain Registry of America Contact: support(a)droa.com Web:http://www.droa.com Domain name: domainrenewalgroup.com Registrant Contact: Domain Registrar Domain Registry Group 2316 Delaware Avenue Suite 266 Buffalo NY, 14216-2687 US +1.8664340212 +1.8664340211 registrar(a)droa.com Administrative Contact: Domain Registrar Domain Registry Group 2316 Delaware Avenue Suite 266 Buffalo NY, 14216-2687 US +1.8664340212 +1.8664340211 registrar(a)droa.com Technical Contact: Domain Registrar Domain Registry Group 2316 Delaware Avenue Suite 266 Buffalo NY, 14216-2687 US +1.8664340212 +1.8664340211 registrar(a)droa.com Update date: 2011-04-13 Expiration date: 2017-01-03 Hei kona- mai,* -- *Juha Saarinen AITTP* *juha.saarinen.org <http://juha.saarinen.org> <http://twitter.com/juhasaarinen> Twitter <http://twitter.com/juhasaarinen>

1 0

3G in the South
by Skeeve Stevens 23 Nov '12

23 Nov '12

Hey all.. I will be spending 2 weeks in the south Island in December... Queenstown, Dunedin, Invercargil mostly. I need a solid 3G connection - prepaid preferably with some decent data. Anyone got any recommendations? I will be flying into and out of Queenstown. Thanks! * * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Brocade - Cloud ----- Check out our Juniper promotion website for Oct/Nov! eintellego.mx Free Apple products during this promotion!!!

1 0

Hurricane Sandy cleanup, for Verizon
by Criggie 20 Nov '12

20 Nov '12

http://www.theverge.com/2012/11/17/3655442/restoring-verizon-service-manhat… Worth a read - makes you wonder why we put kit in basements in the first place. -- Criggie http://criggie.org.nz/

1 0

youth outreach?
by Sean Linton 18 Nov '12

18 Nov '12

Recently Vikram Kumar Chief Executive at InternetNZ highlighted some of the youth outreach initiatives that InternetNZ is involved with. For example work with NetSafe, the 2020 Communications trust, and ICT-Connect. I think its timely activity. I have a question to anyone who is interested. How has the NZNOG community previously ensured that when a few key people decide to do something else the organisation doesn't get into trouble, so new blood keeps coming through? - Sean

3 2

please keep an eye out
by Richard Naylor 17 Nov '12

17 Nov '12

Just a small advisory. I bought 1.5km of fiber for NetHui this week and it was stolen from the supplier (Corys/Mastertrade) before I got there to collect it. Its 12 core D-series, single mode LSZH cable cut as 2x750m. The CCTV footage shows it stolen from the loading bay. So if you get offered some cheap fiber, I'm sure Corys would be very pleased to hear from you. Replacement fiber arrived friday pm in one length. After a lot of winding and splicing, the van is all loaded ready to roll tomorrow. I was suspicious that the folks mad keen on cable laying through the roaring 40's to South America, had nicked it as a part of their project. Richard

1 0

www.massey.ac.nz huge latency/packet loss last few hrs?
by Barry Murphy 13 Nov '12

13 Nov '12

Anyone know whats wrong with them, we getting some complaints... When their circuit over APE is up, it feels like i'm pinging the moon at times. Barrys-MacBook-Pro.local (0.0.0.0) Wed Nov 14 16:10:19 2012 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 192.168.89.1 0.0% 444 1.1 0.4 0.3 2.9 0.2 2. l0-AKSBRAS.vibecom.co.nz 0.0% 444 0.9 0.8 0.6 2.8 0.3 3. 120.136.0.154 0.0% 444 0.8 1.1 0.6 31.5 2.3 4. massey.ape.nzix.net 0.0% 444 1.1 3.3 0.9 202.1 18.0 5. it028216-vlan2100.massey.ac.nz 94.6% 444 802.5 1463. 8.4 4843. 1842. 6. it032222-virt802.massey.ac.nz 95.5% 444 4691. 1198. 8.6 4691. 1824. 7. 10.100.3.184 95.0% 444 7475. 1395. 9.5 7475. 2050. 8. 10.100.188.2 95.5% 444 12.1 630.9 9.0 4868. 1422. 9. ns-proxy1.massey.ac.nz 95.0% 444 14.4 1122. 9.6 4907. 1603. Anyone from massey that can comment so we can advise downstream clients? Cheers Barry

1 0

Speaking of Wet Fibre to Sydney...
by Jed Laundry 12 Nov '12

12 Nov '12

Greetings, I've just noticed that there's a new AWS region available today: Asia Pacific (Sydney). I would imagine we're going to start to see a trickle of commercial offerings shortly, followed by a rapid increase of data. Before I start probing an instance to find out where/who's connected, does anyone have inside clue about how well connected NZ networks are to this new region? Probing commences after beer. Jed.

2 1

ISPMap topology update
by Barry Murphy 11 Nov '12

11 Nov '12

Hey guys, Guess while we're on the topic of international pipes, I've made a new capture map for http://www.ispmap.co.nz It's noticeable that Pacnet is nearly finished with NZ with only 1 ISP still using them... I guess this will soon go away when the contract expires. Here are the stats comparing to beginning of 05 July 2012 Telstra +2 Telecom -1 Pacnet -4 Vocus +1 Odyssey -1 As per usual, if anything needs updating email me offlist. Cheers Barry Murphy

1 0

Labour alleges failure of Southern Cross Cable
by David Robinson 11 Nov '12

11 Nov '12

http://computerworld.co.nz/news.nsf/news/labour-alleges-failure-of-southern… How much substance and how much Political Grandstanding? Yes a second cable would be nice but be careful saying the sky is falling.

19 27

Re: [nznog] Labour alleges failure of Southern Cross Cable
by Scott Weeks 11 Nov '12

11 Nov '12

--- pieter(a)insync.za.net wrote: From: Pieter De Wit <pieter(a)insync.za.net> SAT2 cable was full, iirc and SAT3 only linked to India etc up the west coast. ----------------------------------------------------------- http://submarinecablemap.com scott _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Labour alleges failure of Southern Cross Cable
by Sam Russell 08 Nov '12

08 Nov '12

One would hope she'd see the irony of using twitter over the link that she claims to be broken Sent from my iPhone On Nov 9, 2012, at 1:31 PM, Tim Price <tim(a)initech.co.nz> wrote: Except for where resiliency was down due to previously scheduled maintenance… Certainly wasn’t seamless from my point of view. But yes, Clare Curran needs to GTFO *From:* nznog-bounces(a)list.waikato.ac.nz [mailto: nznog-bounces(a)list.waikato.ac.nz] *On Behalf Of *Sam Russell *Sent:* Friday, 9 November 2012 3:27 p.m. *To:* Al Twohill *Cc:* nznog *Subject:* Re: [nznog] Labour alleges failure of Southern Cross Cable Presumably a redundant link means that nobody loses service when they accidentally break one of them? It does seem like an excuse to blame National for not propping up Pacific Fibre, rather than anything wrong with a redundant set of links failing over correctly due to a fault, as designed Sent from my iPhone On Nov 9, 2012, at 1:20 PM, Al Twohill <moebiusproject(a)gmail.com> wrote: On 9 November 2012 15:16, David Robinson <nznog(a)karit.geek.nz> wrote: http://computerworld.co.nz/news.nsf/news/labour-alleges-failure-of-southern… How much substance and how much Political Grandstanding? Yes a second cable would be nice but be careful saying the sky is falling. There is a thread discussing it on AUSNOG. Looks like Labour basically quoted that. http://lists.ausnog.net/pipermail/ausnog/2012-November/015297.html _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Open resolvers again
by Juha Saarinen 03 Nov '12

03 Nov '12

Spotted this earlier: http://blog.cloudflare.com/deep-inside-a-dns-amplification-ddos-attack "NZ Attack Sources: 167 AU Attack Sources: 1237" Are the local open resolvers seen as a problem? Hei kona- mai,* -- *Juha Saarinen AITTP* *juha.saarinen.org <http://juha.saarinen.org> <http://twitter.com/juhasaarinen> Twitter <http://twitter.com/juhasaarinen>

10 11

Re: [nznog] Open resolvers again
by Hamish MacEwan 02 Nov '12

02 Nov '12

On 3 November 2012 11:02, Matthew Luckie <mjl(a)caida.org> wrote: > http://en.wikipedia.org/wiki/Extension_mechanisms_for_DNS Oh, there's my misunderstanding right there, "The first set of extensions was published in 1999." Fascinating, ("Domain Information Groper") thanks for the link. Hamish. -- http://hamish.kiwi.me

1 0

Andy Linton is now an OpenFlow expert
by Josh Bailey 01 Nov '12

01 Nov '12

It took 2h. About 30m to make an OpenFlow controller PC out of bunch of trash, and boot my controller DVD. "ed" wasn't available on my controlled DVD so I made Andy use nano to configure it. That slowed us down quite a bit. 90m to put OpenFlow firmware on a 3780 switch, including walking up and down the hill to VUW get 1G SFPs. So if you have any questions about whether OpenFlow/SDN works/forwards packets in hardware - ask Andy. He knows. And has a live CD controller.

3 3

(non-op) shout out to NetHui South, November 2012
by Joe Abley 31 Oct '12

31 Oct '12

Hi all, For those who were not already aware, InternetNZ is planning a NetHui event in Dunedin in a few weeks: http://2012-south.nethui.org.nz/ Your amiable (and humble!) trustees support this effort, which looks to be very shiny and excellent. The programme looks good. You should go. You know, if you want to. Joe Abley NZNOG Trust Marketing Department

1 0

AJ the hero!!!
by Skeeve Stevens 31 Oct '12

31 Oct '12

Hey all, AJ is a hero!!! http://www.smh.com.au/travel/travel-incidents/extremely-obnoxious-no-help-f… * * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Brocade - Cloud ----- Check out our Juniper promotion website for Oct/Nov! eintellego.mx Free Apple products during this promotion!!!

5 5

NZNOG 2013 - registrations open
by Gerard Creamer 30 Oct '12

30 Oct '12

NZNOG 2013 - registrations open ============================= Registrations for New Zealand's pre-eminent technical Internet networking conference - NZNOG 2013 - are now open. Hosted by the New Zealand Network Operators Group, NZNOG 2013 is the country's only technical networking conference, and features a host of plenary sessions, practical workshops and tutorials. Spaces are limited, so register now and join your fellow ICT specialists for a feast of information sharing, technical up-skilling and professional networking. To register, please visit http://www.nznog.org/register What: NZNOG 2013 When: 21 - 25 January 2013 Where: Mercure Hotel, Wellington The platinum conference sponsor is Vocus Communications. ---- Conference structure NZNOG 2013 incorporates two three-day practical workshops, a one-day of technical tutorials and the conference-proper. Workshops: 21 to 23 January, 2013 Advanced routing - taught by Philip Smith, APNIC DNSSEC - trainer to be confirmed Tutorial: 23 January, 2013 Topics to be confirmed Conference-proper: 24 - 25 January, 2013 Programme and keynote speakers to be confirmed A range of pricing options are available, including a heavily-discounted student registration: Main conference (waged) - $250.00 Main conference (student) - $50.00 Practical workshop (advanced routing or DNSSEC) - $150.00 Tutorial - $50.00 ---- Conference Fellowships available Assistance is available to those people that mightn't otherwise be able to attend NZNOG 2013 but have a lot to offer to, or gain from, the NZNOG community. Fellowships are open to all - employed, unemployed, students, programmers. Fellowships will cover conference and tutorial registration fees, and accommodation. Travel assistance may also be considered. Applicants must: - Write a few paragraphs explaining why they need a fellowship to NZNOG 2013 and what they hope to get out of it. - Demonstrate a history of involvement in some aspect of the NZNOG community or an intent to become involved, and how attending NZNOG 2013 will benefit them. - Actually attend the NZNOG sessions! - Fellowship prospects will be helped greatly if applicants are presenting, or intend to present a conference paper, lightning talk or otherwise contribute to the conference. If you are interested in being considered for a fellowship please e-mail talks(a)nznog.org. ---- More information More information about NZNOG 2013 can be found at www.nznog.org. For sponsorship opportunities please contact sponsorship(a)nznog.org. Cheers, Gerard (NZNOG 2013 Organising Committee)

1 0

DKIM vulnerability
by Juha Saarinen 25 Oct '12

25 Oct '12

Thought this would be of operational interest to DKIM users.... http://www.wired.com/threatlevel/2012/10/dkim-vulnerability-widespread/all/ Hei kona- mai,* -- *Juha Saarinen AITTP* *juha.saarinen.org <http://juha.saarinen.org> <http://twitter.com/juhasaarinen> Twitter <http://twitter.com/juhasaarinen>

3 2

Xtra mail admins around?
by Tim Price 17 Oct '12

17 Oct '12

Can someone who looks after Xtra's mail systems please contact me. We're seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process. Regards Tim Price Network Operations Manager DTS Limited.

7 11

NZNOG 2013 - Call for Papers
by Gerard Creamer 17 Oct '12

17 Oct '12

Call for papers - NZNOG 2013 Doing something interesting in the Internetworking space? Submit an NZNOG conference paper and you could win a trip to the next APRICOT meeting in Singapore! ---- The NZNOG organising committee invites papers for its 12th annual conference, to be hosted at the Mercure Hotel, Wellington, New Zealand from 21 – 25 January 2013. There will the three day Workshops 21 – 23 January, a day of tutorials on 23 January with the main conference on 24 – 25 January. The best local conference paper as judged by the organising committee will win a trip to APRICOT 2013, to be held in Singapore, 19 February to 1 March 2013. So, get writing! Conference objective: The NZNOG conference, workshops and tutorials are a once-a-year opportunity for individuals and organisations involved in Internet operations to meet and share the latest in Internet operations, technologies practises and receive high quality training. The event is unique in New Zealand and attracts technical, skilled individuals with a genuine interest in Internet operations and Internetworking technologies. Submit a paper: Presenters are invited to submit abstracts of their paper for consideration by Monday 5 November. Abstracts should be no more than one page long and provide a summary of your networking-related subject matter. To submit your paper please e-mail: talks(a)nznog.org When considering a presentation, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. Note: The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but will help us determine the quality of your proposal and increase the likelihood it will be accepted. The organising committee will evaluate abstracts based on fit with the conference’s objective and its ability to stimulate lively discussions around the current state of New Zealand networking. The best local paper will be judged by a selection of the organising team. Return flights from New Zealand, accommodation, and conference fees will be covered. It will be expected the best paper is submitted by the winner for presentation at APRICOT. More details on paper submission can be found at http://www.nznog.org/call-for-papers For more information about the conference visit www.nznog.org or contact: talks(a)nznog.org -- Netspace Services Limited http://www.netspace.net.nz Phone +64 4 917 8098 Mobile +64 21 246 2266 Level 4, 191 Thorndon Quay, Thorndon PO Box 12-082, Thorndon, Wellington 6004, New Zealand

1 0

TelstraClear 6to4 relay router down again?
by Lloyd Parkes 15 Oct '12

15 Oct '12

Does anyone know if the TelstraClear 6to4 relay is down again? This looks like what happened in May last year, except that this time, I'm working with a brand new router, so it could just be me. I think I've got the hang of the RouterOS firewall and the packet dumps say the 6to4 packets are going out, but I don't trust RouterOS that much yet. Cheers, Lloyd

2 1

If you are using APNIC as an RPKI trust anchor, please update your Trust Anchor Set.
by George Michaelson 14 Oct '12

14 Oct '12

If you are using APNIC as an RPKI trust anchor, please update your Trust Anchor Set. APNIC will be switching to a new RPKI 'split' trust anchor system on the 25th of October. This change is needed to align APNIC administered resources with their allocation hierarchy. These resources will also be certified under each responsible parent registry at the appropriate time. In accordance with RFC6490 the old APNIC Trust Anchor Locator, associated certificate and repository will be removed, when the certificate expires on the 28th of October. 5 new Trust Anchor Locator (TAL) have been published. These will be kept up to date as an independent trust anchor set for resources maintained by APNIC. The production cycle will start on the 25th of October. Relying parties must add these new TAL by the 25th of October in order to maintain continuity of validation. If you have any questions please contact me. George Michaelson (ggm(a)apnic.net) Please add the following to your trust anchor set: rsync://rpki.apnic.net/repository/apnic-rpki-root-afrinic-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuMLL96YV9pf0rZ4Ow/bk cgpoPfsRzkcgmisyCuMUdotHwrp8pepujhohatScRK09ILRrZYCdpX4121MJhqXC P3u3hy9fF0CeARKX/Q82nJccD4dtUp23UcFys8hwJgNYZI910ajkAxwNT//H/TFw oUYbzZGBR7o2awMc7GdQl/j6dgOkV6AfYy5DyDEgOUNHnUxED2rreefL/E2Fr2ST Esar6bTR4Tg4+nVF1PjAkgN0tKZYe4wZ6VmtqV/VTngSLysim6av7ki+JR3cVgVU OqXeh1vPjH2tNu6u9bX37ZrdVb6NBRer9I99IDbKvyhELb6nzo8+Q74zga9HI+Pf QwIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-arin-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAp6vscYtzhe0CfFk5Ro44 llPhsInXtfAxqfYmK7m9V3khkqK3d3/ZAW6pcJm7qW8XhEGl+F5mUeeLIm5JoIhr kT5B5M6uL0VlCCkZJH4h76ybOa83vWITNZEDy9L3c3nK4S+Basu3vYoE4ICXGG+J 7zg5Iw9saV+p03E2w1g16pt1QI3Cnggp6edkeWClEz3aPw/ULOIHb7YmatWwdERl tL9LsuMSKszQLUY7F4XVpxey/rJYAZgzDUh+b6813WAClCkkydNjsbviuekAWJbx sW7Mcw53u30K4g8MP03CjkDOubyoR4Qo99R1UQJCdrRsFKbSSfN/fOA4y7ikc3xs jQIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-iana-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx9RWSL61YAAYumEiU8z8 qH2ETVIL01ilxZlzIL9JYSORMN5Cmtf8V2JblIealSqgOTGjvSjEsiV73s67zYQI 7C/iSOb96uf3/s86NqbxDiFQGN8qG7RNcdgVuUlAidl8WxvLNI8VhqbAB5uSg/Mr LeSOvXRja041VptAxIhcGzDMvlAJRwkrYK/Mo8P4E2rSQgwqCgae0ebY1CsJ3Cjf i67C1nw7oXqJJovvXJ4apGmEv8az23OLC6Ki54Ul/E6xk227BFttqFV3YMtKx42H cCcDVZZy01n7JjzvO8ccaXmHIgR7utnqhBRNNq5Xc5ZhbkrUsNtiJmrZzVlgU6Ou 0wIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-lacnic-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyoYPp3l3DWyPtLWrmRn4 Oux9hQ5bxd0SX/f6ygHxik+I3eMJP5J0Pr2e500tyXb2uKsX9kDqu/kckr+TUMhV BHd5yAv8OAE3YYEvpz/7uTX7cYy2yUeA76OEP75Y88OIQEzGpPLNpIzDxMggxuDh IhkA5xMiUJgVoEgmWSzR+MuRBjv2422wAGB5GpLgYsOjpwvG0VPmhnE+39+10ucQ CLt0Ny5kOR4an2tkvHjm7rzKDnFm8MWxPzAWESdf+8g7ITzSglqxDNiK5E5rdzNt h1Kvp+9RwaFArw6Ky1A4HhnoplN4EfKwxq0YamuKV0ZTTpWyT2+qDuE6sOfHRbJ0 5QIDAQAB rsync://rpki.apnic.net/repository/apnic-rpki-root-ripe-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwsQlXmEklLYApoDo7GEa NNTEGFPU5wJpi04iXuga2xn+g/TMLOlyJbjuPYRtRm/7VbRnN3m9Ta+WETy03+Fm EbXzB4xxhJKVik/ARHBnrBWhLyURy8Q5/XplE9cJein37IE1mIsbKM7o/90S225w 7GuvW7T4kjPWYmBFOywHWsfQO1EdsgiJrkz+Ab67ZkdSIiKHkf2UE6/MrbDEj+QK 9+s/vKH8BtDhaLmTWY+bVvfJ3+AWDH6roo1ozbl5yamQFbLOl3ns30f3yOJcNSNu /qgMQRRyp2sXXQovhTy8yqm3LFspaCWnTmQtBieWZwibuOa4Z27A1FzTMst2T4wY /wIDAQAB

1 0

Xtra DNS
by Simon Lyall 14 Oct '12

14 Oct '12

Can somebody on the team that looks after Xtra's DNS servers please contact me. I'm seeing problems with a specific record that works okay with most/all other NZ ISPs ( the record has a short TTL but has been broken for days ). My work's site has a work-around in place but various other sites ( like some at Mozilla ) will be broken for Xtra customers. The servers I am talking about are: 202.27.184.3 alien 202.27.184.5 terminator 202.27.158.40 dnsc1 202.27.156.72 dnsc2 -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Added a new Range of IP addresses in NZ - Geolocation updates
by Greg Theron 09 Oct '12

09 Oct '12

Hi Guys We have setup an ISP in New Zealand and have allocated part of our Australian IP address space over here. Could I please ask everyone to update their Geolocation Databases to include the 180.222.160.0/20 as being based in Auckland? Thanks heaps Greg inetnum: 180.222.160.0 - 180.222.175.255 netname: TELCOINABOX-AP descr: Telcoinabox Pty Ltd descr: Telcoinabox NZ Limited descr: Level 4, 15 Huron Street, Takapuna, Auckland country: NZ admin-c: TNLN1-AP<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=TNLN1-AP&form_type=advanc…> tech-c: TNLN1-AP<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=%20TNLN1-AP&form_type=adv…> mnt-by: APNIC-HM<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=%20APNIC-HM&form_type=adv…> mnt-lower: MAINT-TELCOINABOX-AU<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-TELCOINABOX-AU&form…> mnt-routes: MAINT-TELCOINABOX-AU<http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-TELCOINABOX-AU&form…> mnt-irt: IRT-TELCOINABOX-AU status: ALLOCATED PORTABLE remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ remarks: This object can only be updated by APNIC hostmasters. remarks: To update this object, please contact APNIC remarks: hostmasters and include your organisation's account remarks: name in the subject line. remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ changed: hm-changed(a)apnic.net 20091014 changed: hm-changed(a)apnic.net 20121009 source: APNIC Greg Theron [cid:image001.png(a)01CDA6D7.4DA3C3D0] Telcoinabox NZ Limited | Level 4, 15 Huron Street, Takapuna, Auckland D: +64 9 4880106 | M: +64 27 874 4783 | F: 0800 883 526 telcoinabox.co.nz Add us on social media: g [cid:image002.png(a)01CDA6D7.4DA3C3D0]<http://facebook.com/telcoinabox> [cid:image003.png(a)01CDA6D7.4DA3C3D0] <http://www.linkedin.com/company/419134?trk=tyah> [cid:image004.png(a)01CDA6D7.4DA3C3D0] <http://twitter.com/#!/telcoinabox_nz> ________________________________ The information contained in this electronic mail transmission is intended by Telcoinabox (NZ) Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission.

4 4

FW: ICANN News Alert -- Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA
by Leo Vegoda 08 Oct '12

08 Oct '12

Hi, The consultation described in the announcement below is being run to gather input on the best way to implement the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA, which was ratified in May. In particular, we are keen to gather input on the most useful registry format for the Recovered IPv4 Pool. If you have a particular preference, please provide input to the consultation. Many thanks, Leo Vegoda From: ICANN News Alert Sent: Thursday, October 04, 2012 1:37 PM Subject: ICANN News Alert -- Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA <http://www.icann.org/> Description: ICANN News Alert <http://www.icann.org/en/news/announcements/announcement-04oct12-en.htm> http://www.icann.org/en/news/announcements/announcement-04oct12-en.htm _____ Implementing the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA 4 October 2012 Forum Announcement: Comment Period Opens on Date: 4 October 2012 Categories/Tags: Internet Protocol Addressing Purpose (Brief): The Board ratified the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA in May. This public comment period is intended to gather input on options open for implementation. Public Comment Box Link: <http://www.icann.org/en/news/public-comment/implementing-ipv4-post-04oct12-…>http://www.icann.org/en/news/public-comment/implementing-ipv4-post-04oct12-… message was sent from:ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536Email Marketing by <http://www.icontact.com/a.pl/144186> Description:iContact - Try It Free! <http://app.icontact.com/icp/mmail-mprofile.pl?r=9828084&l=6333&s=FAC9&m=895…> Manage Your SubscriptionDescription:http://click.icptrack.com/icp/track.php?msgid=89518…

1 0

FW: APE MAC addresses
by Mark Frater 02 Oct '12

02 Oct '12

Anyone know what the rational is around the "official policy around APE" of only having a single MAC address per port? I would have thought that there was some technical merit in allowing at least 2 to cover rotuer replacement (without MAC address spoofing) and offer some peer router diversity options (e.g. either via separate peering sessions or VRRP implementation.) Regards Mark Frater

5 7

New surveillance Laws
by Tony Wicks 30 Sep '12

30 Sep '12

http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10837641 Has anyone complied a definitive guide on what the enacted law means for us as network operators ? thanks

1 0

ETNO SPNP proposal
by Juha Saarinen 25 Sep '12

25 Sep '12

Wrote this earlier today: http://www.itnews.com.au/News/316593,eu-telcos-seek-end-to-settlement-free-… Would be interested to hear what the local view on mandatory SPNP. Hei kona- mai,* -- *Juha Saarinen AITTP* *juha.saarinen.org <http://juha.saarinen.org> <http://twitter.com/juhasaarinen> Twitter <http://twitter.com/juhasaarinen>

8 8

NZ peering - IPv6, Looking glasses etc.
by Sid Jones 17 Sep '12

17 Sep '12

FYI: We've upgraded the the Palmerston North exchange so that it supports IPv4 and IPv6 peering announcements, this means that all five of the NZ peering points operated by Citylink are now dual-stacked. If you want to add IPv6 peering please contact us - peering @ citylink.co.nz You can see who is peering with the route servers using http://nzix.net/peers.html There is also Looking Glass visibility to all the route servers available at http://nzix.net/cgi-bin/lg.cgi Lastly, another reminder that you no longer need to submit filter list updates.

1 0

Security Survey: Please Participate
by Sockrider, Gary 16 Sep '12

16 Sep '12

[http://www.swiftpage1.com/CampResource/2T0ZVZBHI4PY5TEG/header.jpg] ________________________________ Arbor Networks would like to invite you to participate in our annual Infrastructure Security Survey - a survey of service providers, enterprises, government agencies, universities and other network operators around the world. The purpose of the survey is to gauge and report on general security issues, practices, procedures and observations from the industry. All data gathered from the survey will be compiled in the aggregate and published as Arbor’s 8th annual infrastructure security report and accompanying presentations. Individual responses are treated anonymously and no respondent names will appear in the report or presentations. As a reference, you may access a copy of our 7th annual report here: http://pages.arbornetworks.com/rs/arbor/images/WISR2011_EN.pdf<http://www.swiftpage1.com/SpeClicks.aspx?X=2T0ZVZBHI4PY5TEG00Y9WW> To participate in this year's survey, please click on the following link: http://www.arbornetworks.com/survey/ISR2012<http://www.swiftpage1.com/SpeClicks.aspx?X=2T0ZVZBHI4PY5TEG01Y9WW>. You will be directed to a secure (SSL) connection to begin. The survey should take 30 minutes or less to complete. Survey completion by September 28, 2012 would be greatly appreciated. Thank you very much for your consideration. Please feel free to contact me at cmorales(a)arbor.net<mailto:cmorales(a)arbor.net> should you have any questions on the survey or Arbor Networks. Regards, Carlos E. Morales Vice President Systems Engineering and Sales Operations

1 0

Fwd: RIPE NCC now allocating IPv4 address space from the last /8 netblock
by Skeeve Stevens 13 Sep '12

13 Sep '12

* * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Cloud ---------- Forwarded message ---------- From: Eugen Leitl <eugen(a)leitl.org> Date: Sat, Sep 15, 2012 at 2:12 AM Subject: RIPE NCC now allocating IPv4 address space from the last /8 netblock To: NANOG list <nanog(a)nanog.org>, tt(a)postbiota.org, forkit! <fork(a)xent.com> http://arstechnica.com/information-technology/2012/09/europe-officially-run… Europe officially runs out of IPv4 addresses RIPE NCC now allocating IPv4 address space from the last /8 netblock by Iljitsch van Beijnum - Sep 14, 2012 3:20 pm UTC Earlier today, the RIPE NCC (Réseaux IP Européens Network Coordination Centre) announced it is down to its last "/8" worth of IPv4 addresses. This means that it is no longer possible to obtain new IPv4 addresses in Europe, the former USSR, or the Middle East, with one small exception: every network operator that is a "RIPE member" or "local Internet registry" (LIR) can obtain one final block of 1024 IPv4 addresses. To fulfill these requests, the RIPE NCC is keeping that last /8, which contains 16.8 million addresses, in reserve. RIPE NCC None of this comes as a surprise given that the global pool of free IPv4 addresses was emptied in February 2011. APNIC, which distributes IP addresses in the Asia-Pacific region, ran out of IPv4 addresses in May 2011; it has been working under the "final /8" regime ever since. The remaining three Regional Internet Registries are AfriNIC (Africa), LACNIC (Latin America and the Caribbean), and ARIN (North America), which all have enough IPv4 addresses to last at least two more years. Since the depletion of IPv4 address space in the APNIC region, little information has surfaced about how network operators in the region have managed the situation. However, the lack of IPv4 addresses only impacts organizations and consumers who need additional addresses, or who need addresses for the first time. Existing IPv4 users remain unaffected, and so the immediate impact is limited. Also, large network operators get large address blocks from the RIRs and they typically have a pool of unused addresses of their own, so few will be experiencing immediate problems. However, every year for the past five years, some 200 million new IPv4 addresses have been put into use. Without a steady supply of fresh addresses, many Internet-related activities are going to become problematic in the years to come. Fortunately, 20 years ago the Internet Engineering Task Force (IETF) foresaw that the 3.7 billion addresses afforded by the 32-bit IPv4 address space would become a problem, and started working on a replacement: IPv6. But the IPv4 depletion didn't happen as fast as the IETF originally predicted, and IPv6 adoption has languished. But recently, IPv6 adoption got a big push in the form of World IPv6 Launch. Eventually, IPv6 will replace IPv4, but the transition won't be pretty. Reader comments 19 Iljitsch van Beijnum / Iljitsch is a contributing writer at Ars Technica, where he contributes articles about network protocols as well as Apple topics. He is currently finishing his Ph.D work at the telematics department at Universidad Carlos III de Madrid (UC3M) in Spain. @iljitsch

1 0

speedtest.net - Texas to Wellington vs. Texas to Christchurch
by Jeremy Lawson 10 Sep '12

10 Sep '12

I was having some issues transferring to/from one of my Rackspace VPSs, so I run a few tests on speedtest.net from the VPS to various parts of NZ. I expect SOME difference, but these are outrageous. Basically: What the hell is going on in Christchurch? Ping 41ms - Wellington (CityLink) 167ms - Christchurch (Snap) 182 - Culverdon (Amuri Net) Download (transfer to Texas from NZ) 152.79 Mb/s - From Wellington 2.35 Mb/s - From Christchurch 1.99 Mb/s - From Culverdon Upload (transfer to NZ From Texas) 69.28 Mb/s - To Wellington 18.97 Mb/s - To Christchurch 7.48 Mb/s - To Culverdon Source: (each of these are the last of several similar results) http://www.speedtest.net/result/2171916814.png http://www.speedtest.net/result/2171913440.png http://www.speedtest.net/result/2171915443.png ---------------------------------------------------------------------------- Jeremy Lawson

8 8

FW: Request to clear DNS record cache in the ISP Network
by John Gandy 10 Sep '12

10 Sep '12

ISPs may wish to action the attached request from Al-Jazeera received today. Regards J John Gandy Commerce Commission | Chief Adviser 44 The Terrace ‌| PO Box 2351 ‌| Wellington 6140 | New Zealand DDI +64 (0)4 924 3677 | john.gandy(a)comcom.govt.nz<mailto:Alfred.example(a)comcom.govt.nz> [cid:image001.png(a)01CD8FFF.FB2104D0]<https://twitter.com/#!/FutureBroadband> [cid:image002.jpg(a)01CD8FFF.FB2104D0]<http://www.linkedin.com/groups?gid=4036838&trk=hb_side_g> From: telco Sent: Tuesday, 11 September 2012 8:04 a.m. To: John Gandy; Simon Thomson Subject: FW: Request to clear DNS record cache in the ISP Network Importance: High Kind regards, Silvia From: Nabil Belkaid [mailto:BelkaidN(a)aljazeera.net] Sent: Monday, 10 September 2012 11:20 p.m. To: telco Subject: Request to clear DNS record cache in the ISP Network Importance: High Dear Sir/Madam, To whom it may concern We, the Al-Jazeera Network is one of the worlds leading media network, is requesting your cooperation in instructing ISP's within your jurisdiction to clear their DNS cache. Our DNS servers were compromised recently and hackers set a long TTL (Time To Live) timer for our DNS record. Even though we have recovered from the attack, many users within your jurisdiction are unable to reach our services because of the incorrect DNS record for our domain names in the providers network. We are requesting your assistance to reach the providers so that they can clear the caches for the following domains that belongs to AlJazeera Networks. aljazeera.net aljazeera.com aljazeerasport.net aljazeerasport.com ajsdealers.com ajtransparency.com aljazeerait.net aljazeerakiswahili.com aljazeerakiswahili.org aljazeeraportal.net beinsport.net beinsport.fr beinsports.net beinsports.tv thepalestinepapers.com ajnm.me ajb.me aje.me ajtu.me aljazeera-story.net aljazeera.co.uk Aljazeera.com.tr Aljazeera.com.qa Maila.aljazeera.net Mailb.aljazeera.net We kindly request that you instruct the providers within your jurisdiction to take this action immediately. Please note that this is affecting our brand negatively and our ability to deliver the news. Please kindly act immediately. With Regards [cid:aljazeera_logo1] Nabil Belkaid Senior Engineer Media Networks & Security Section IT & Digital Media Department | Technology Division [cid:al_tel1]+974 44897073 | [cid:al_mobile1] +974 33217191 [cid:al_env1] belkaidn(a)aljazeera.net<mailto:belkaidn(a)aljazeera.net> [cid:al_mouse1] www.aljazeera.net<http://www.aljazeera.net> ________________________________ Notice: This email is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. </PRE>############################################################### The information contained in this e-mail may be legally privileged and CONFIDENTIAL. If you are not the intended recipient you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, please delete the message and notify the sender. Any views or opinions presented are solely those of the author and are not those of the Commerce Commission. ###############################################################

1 0

Vic Uni Mail Admin about? SPF rec issue...
by Don Gould 09 Sep '12

09 Sep '12

I do SPF checking. # grep $user mail.log Sep 10 09:05:48 mx tumgreyspf[13335]: 'SPF Permanent Error: Too many DNS lookups': QUEUE_ID=""; identity=mailfrom; client-ip=216.32.181.183; helo=ch1outboundpool.messaging.microsoft.com; envelope-from=$User(a)vuw.ac.nz; receiver=$user(a)tauatapu.net.nz; vuw.ac.nz IN TXT v=spf1 ip4:130.195.81.0/24 ip4:130.195.86.0/24 ip4:202.36.141.0/24 ip4:216.235.196.0/22 ip4:216.235.200.0/21 include:mcs.vuw.ac.nz include:mailprimer.com include:_spf.learningsourceapp.com include:spf.messaging.microsoft.com ~all 1. Is anyone else having this issue with vuw? 2. Should I be doing something to change my config or do others feel that the vuw spf record is to wide? D -- Don Gould 31 Acheson Ave Mairehau Christchurch, New Zealand Ph: + 64 3 348 7235 Mobile: + 64 21 114 0699

5 6

Requesting guidance...
by Steve Holdoway 09 Sep '12

09 Sep '12

As you've been very helpful in the past, can I ask the best way forward in addressing this problem. In an attempt to reduce spam delivery to a local charity mail server, I added FEATURE(`require_rdns')dnl to the sendmail config. It did help. However, it also blocked some important clents as well... barnardos.org.nz - sends via 122-56-8-123.cid.global-gateway.net.nz logon.i.govt.nz - has no IP address ecan.govt.nz - sends via onyx.crc.govt.nz which has no IP address probably being the most important. How do you address this problem. I'm certain they all must have been repeatedly contacted? TIA for all ideas, Steve -- Steve Holdoway BSc(Hons) MIITP http://www.greengecko.co.nz MSN: steve(a)greengecko.co.nz Skype: sholdowa

8 8

Re: [nznog] Vic Uni Mail Admin about? SPF rec issue...
by Don Gould 09 Sep '12

09 Sep '12

Ok, cool. thanks Tim, that answers where to point the finger now. Tim do you mind sharing how you tested that? What tool did you use? Is there a vwu admin on list who would like to comment? Can you fix your spf record so it doesn't cause more than 10 recursive look ups or should I just not bother with spf? D On 10/09/2012 1:07 p.m., Tim Price wrote: > > The recursive lookups in that SFP record come to 14 according to my > checking. > > vuw.ac.nz IN TXT v=spf1 ip4:130.195.81.0/24 > ip4:130.195.86.0/24 ip4:202.36.141.0/24 ip4:216.235.196.0/22 > ip4:216.235.200.0/21 include:mcs.vuw.ac.nz include:mailprimer.com > include:_spf.learningsourceapp.com include:spf.messaging.microsoft.com > ~all > > ·include:mcs.vuw.ac.nz > > omx > > ·include:mailprimer.com > > oinclude:mailprimer.net.nz > > §include:mailprimer.co.nz > > §include:mailprimer.com > > ·include:mailprimer.net.nz (loop?) > > ·include:_spf.learningsourceapp.com > > oinclude:sendgrid.net > > §include:sendgrid.biz > > ·include:spf.messaging.microsoft.com > > oinclude:spfa.frontbridge.com > > oinclude:spfb.frontbridge.com > > oinclude:spfc.frontbridge.com > > *From:*nznog-bounces(a)list.waikato.ac.nz > [mailto:nznog-bounces(a)list.waikato.ac.nz] *On Behalf Of *Scott Howard > *Sent:* Monday, September 10, 2012 12:52 PM > *To:* Don Gould > *Cc:* nznog > *Subject:* Re: [nznog] Vic Uni Mail Admin about? SPF rec issue... > > On Sun, Sep 9, 2012 at 5:44 PM, Don Gould <don(a)bowenvale.co.nz > <mailto:don(a)bowenvale.co.nz>> wrote: > > 2. Should I be doing something to change my config or do others > feel that the vuw spf record is to wide? > > > From http://tools.ietf.org/html/rfc4408#section-10.1 : > > / SPF implementations MUST limit the number of mechanisms and modifiers > that do DNS lookups to at most 10 per SPF check, including any > lookups caused by the use of the "include" mechanism or the > "redirect" modifier. If this number is exceeded during a check, a > PermError MUST be returned. The "include", "a", "mx", "ptr", and > "exists" mechanisms as well as the "redirect" modifier do count > against this limit. The "all", "ip4", and "ip6" mechanisms do not > require DNS lookups and therefore do not count against this limit. > The "exp" modifier does not count against this limit because the DNS > lookup to fetch the explanation string occurs after the SPF record > has been evaluated. > / > > Scott > -- Don Gould 31 Acheson Ave Mairehau Christchurch, New Zealand Ph: + 64 3 348 7235 Mobile: + 64 21 114 0699

3 3

Some Traffic stats
by Simon Lyall 06 Sep '12

06 Sep '12

I just put up some stats on where the NZ eyeballs appear to be, based on some website data and sort by Origin ASN. People here might find it interesting since it might be a rough proxy for market share. http://blog.darkmere.gen.nz/2012/09/where-the-nz-eyeballs-are/ -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Re: [nznog] NZNOG conference
by Mark Foster 03 Sep '12

03 Sep '12

Thanks for posting the actual dates. I didn't think that one would have to go to third party resources for the answer and I'm also aware of "differing opinions" as regards the nature of the overlaps of audience. Sorry for the network purists but some people either wear many hats or have to roster those who do. ..! ("Them and us" approach doesn't do anyone any favours IMHO) Cheers. Simon Lyall <simon(a)darkmere.gen.nz> wrote: > >Colour me confused but when I look online[1] NZNOG 2013 is listed as 21-25 >Jan 2013 which is the week before LCA. > >I'd check the NZNOG website for details but... > >[1] Here: > >http://ws.edu.isoc.org/calendar/index.php?event=DES >http://www.ripe.net/ripe/meetings/calendar/nznog-2 >http://www.apnic.net/events/calendar/2013/nznog-2013 > > >-- >Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ >"To stay awake all night adds a day to your life" - Stilgar | eMT. > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog

4 3

NZNOG conference
by Daniel Griggs 31 Aug '12

31 Aug '12

I was just trying to find some details for the next NZNOG conference, but the NZNOG site appears to be down, downforeveryoneorjustme.com agrees that it's not just me. I think it was announced to be in Wellington but I haven't heard anything further, like dates or any calls for papers. Does anyone else have any details? (organising committee?) -- Daniel Griggs Network Operations e: daniel(a)fx.net.nz d: +64 4 4989567

11 11

Questions from APNIC34 in Cambodia - Returned IPv4 Addresses
by Dean Pemberton 30 Aug '12

30 Aug '12

One of the topics to come up at the APNIC 34 meeting in Cambodia is what happens to any IPv4 addresses which are returned or recovered by APNIC. At present APNIC operates in a mode where it is implementing austerity measures and will only allocate 1024 addresses from their last /8 (103/8) to members on a one off basis. This means that existing and new APNIC members are only able to get a single 1024 address allocation from now on. There are organisations with large IP address allocations (in most cases legacy addressing) who are considering handing them back. JPNIC has already accepted back more than a /11 worth of space. The questions being asked by some members now is what happens to those addresses and how might they be reallocated to other members. In evaluating how recovered addresses may impact its members the Japan Network Information Centre has asked them the following questions and I'd like to give New Zealand organisations a chance to answer them as well. 1. If it were possible to receive an IPv4 allocation of returned addresses from outside of the APNIC final /8 (103/8) block, would you apply for an allocation? 2. Would you use the IPv4 addresses any differently than an allocation from the final /8? (eg, Sign up new customers vs IPv6 transition technologies) 3. Would there be an effect on your IPv6 deployment if further IPv4 addresses could be allocated. 4. What would be the minimum size which would make such an allocation useful 5. There are opinions that rather than focusing on changing IPv4 policy, we should put all efforts towards IPv6 deployment. Taking such opinion into consideration, do you still feel there is a need to re-consider the APNIC final /8 policy (APNIC prop-88)? 6. Any additional comments. Answers/Comments to me or the list, I'm calm either way. Regards, Dean

1 0

Fwd: Asia's Fastest Communications Cable Comes Online
by Skeeve Stevens 23 Aug '12

23 Aug '12

Interesting to know. * * *Skeeve Stevens, CEO - *eintellego Pty Ltd skeeve(a)eintellego.net ; www.eintellego.net Phone: 1300 753 383; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellego ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/networkceoau ; blog: www.network-ceo.net The Experts Who The Experts Call Juniper - Cisco – IBM - Cloud ---------- Forwarded message ---------- From: Joly MacFie <joly(a)punkcast.com> Date: Fri, Aug 24, 2012 at 3:25 PM Subject: Asia's Fastest Communications Cable Comes Online To: North American Network Operators Group <nanog(a)nanog.org> http://www.livescience.com/22538-asias-fastest-communications-cable-comes-o… The fastest-yet communications cable in Asia came online today (Aug. 20). The underwater fiber optic cable links Japan, Hong Kong, the Philippines, Malaysia and Singapore for high-speed, computerized stock trading. The system transmits information at 40 gigabits per second, three milliseconds faster than any other system in the region, the BBC reported<http://www.bbc.co.uk/news/technology-19275490>. "The gain may sound small, but could prove critical to financial trades made out of the region," according to the report. -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast WWWhatsup NYC - http://wwwhatsup.com http://pinstand.com - http://punkcast.com VP (Admin) - ISOC-NY - http://isoc-ny.org -------------------------------------------------------------- -

1 0

Task Force releases ‘metrics’ report, highlighting state of IPv6 in New Zealand
by Dean Pemberton 21 Aug '12

21 Aug '12

Forwarded. ------ Hi, The Task Force has today released its latest metrics report, highlighting aspects of New Zealand's IPv6 landscape. Read more (and download the full report in PDF) at the following link: http://www.ipv6.org.nz/2012/08/22/task-force-releases-metrics-report-highli… Happy reading. Campbell -- Campbell Gardiner Communications Lead, Internet New Zealand Secretariat, New Zealand IPv6 Task Force Web: www.internetnz.net.nz & www.ipv6.org.nz Email: campbell(a)internetnz.net.nz DDI: + 64 4 495 2332 Mobile: + 64 21 506 004 Address: Level 9, Grand Arcade Tower, 16 Willis Street, Wellington 6011

1 0

Auckland Network/Linux Engineer Required
by Sean Weekes 20 Aug '12

20 Aug '12

NATCOM is looking for a Network/Linux Engineer to join our team in Auckland. Enquiries off list please through http://www.natcom.co.nz/careers Regards, Sean. +64 21 217 1223

1 0

Connect with APNIC
by Elly Tawhai 16 Aug '12

16 Aug '12

________________________________________________________________________ Connect with APNIC from anywhere ________________________________________________________________________ Hi NZNOG Community, APNIC social media communities can help you keep up to date with the latest news across the Internet industry! We will share interesting commentary, the latest statistics, news, job opportunities and more. We invite you to share what interests you, including your own published materials and even photos from Internet industry events! APNIC connects with the Internet community on Facebook, Twitter, and LinkedIn. Each platform features exclusive content, including competitions and other offers. Join us at events across the world via APNIC's social media platforms, starting with APNIC 34 in Phnom Penh, Cambodia using the hashtag #APNIC34 and the APNIC 34 Event page on Facebook. Check out other remote participation tools for APNIC 34: http://conference.apnic.net/34/remote Follow APNIC on Twitter: http://www.twitter.com/APNIC Like the APNIC Facebook Page: http://www.facebook.com/APNIC Follow APNIC on LinkedIn: http://www.linkedin.com/company/apnic ________________________________________________________________________ APNIC Secretariat conference(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.

1 0

Brief outage on rs1.wix.net.nz and rs1-v6.wix.net.nz - 10am Tuesday
by Tim Hoffman 15 Aug '12

15 Aug '12

Greetings, As part of our continued effort to develop the NZIX route servers, we are planning to replace rs1.wix.net.nz and rs1-v6.wix.net.nz on Tuesday at 10am. We will observe a change freeze on the rest of our route servers nationwide (including the alternate WIX route servers) during this time. These two route servers (which are currently separate boxes) are being replaced with a single dual-stacked box. Assuming all goes well later next week we'll be replacing rs2.wix.net.nz and rs2-v6.wix.net.nz with a second dual stacked route server - we will advise the details/timing of this once Tuesday's work is complete. Feel free to drop me an email if you have any queries/comments regarding this. Regards, Tim

3 3

Network Engineer role at CityLink
by Dylan Hall 09 Aug '12

09 Aug '12

CityLink is looking for a Network Engineer to join our team in Wellington. Details and a job description are available online: http://www.citylink.co.nz/network-engineer Replies off list please. Thanks, Dylan

1 0

Re: [nznog] Close-up: Milestone for the internet
by Richard Naylor 08 Aug '12

08 Aug '12

At 07:44 p.m. 9/08/2012, Jo - Mesh|net wrote: >Fantastic. I don't know if I've ever mentioned it to him, but I >consider Mr Naylor to be my digital father.. Richard was involved in >connecting my intermediate school in the early 90s and things like >video/audio/whiteboard conferencing with University of Hawaii, and >connecting to sites over a 300 baud modem as a 11 year old really >inspired me to seek connectivity and kick-started my digital life. > >So thanks Richard and all the others of you who continue to foster the >Internet and spark that interest in networks today... Thanks Jo - That would be EBIS with Tony Stanley ? If so I have a video of it that you probably made. It was inspirational. BTW sometimes you get it wrong http://www.bbc.com/future/story/20120703-how-i-turned-down-tim-berners-lee

1 0

Close-up: Milestone for the internet
by Steve Kurzeja 08 Aug '12

08 Aug '12

For those that missed Richard Naylor in action last night with his crocodile clips: http://tvnz.co.nz/close-up/milestone-internet-video-5013663 Regards, Steve

3 2

Wanted Cisco NPE-225
by John Lynch 08 Aug '12

08 Aug '12

Hi all wondering if anyone had an old Cisco NPE-225 they would be willing to part with, Beer or money can be provided. Please contact me off list. :-) Thanks.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES6:AS9503 descr: Route set advertised to AS9439 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2404:3800:0:0:0:0:0:0/32^32-64, 2001:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A:0:0:0:0:0/48^48-64, 2404:1800:0:0:0:0:0:0/32^32-64, 2001:4530:0:0:0:0:0:0/32^32-64, 2400:B400:0:0:0:0:0:0/32^32-64, 2404:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700:0:0:0:0:0:0/32^32-64, 2403:F700:0:0:0:0:0:0/32^32-64, 2001:DF0:2BB:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120718 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES6:AS9503 descr: Route set advertised to AS9439 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2404:3800:0:0:0:0:0:0/32^32-64, 2001:DCE:0:0:0:0:0:0/32^32-64, 2001:DCE:E000:0:0:0:0:0/48^48-64, 2001:DF0:4A:0:0:0:0:0/48^48-64, 2404:1800:0:0:0:0:0:0/32^32-64, 2001:4530:0:0:0:0:0:0/32^32-64, 2400:B400:0:0:0:0:0:0/32^32-64, 2404:130:0:0:0:0:0:0/32^32-64, 2403:E00:0:0:0:0:0:0/32^32-64, 2400:1200:0:0:0:0:0:0/32^32-64, 2403:C200:0:0:0:0:0:0/32^32-64, 2404:1E00:0:0:0:0:0:0/32^32-64, 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2403:7000:0:0:0:0:0:0/32^32-64, 2404:138:103:0:0:0:0:0/48^48-64, 2404:138:104:0:0:0:0:0/48^48-64, 2404:138:4000:0:0:0:0:0/48^48-64, 2404:D000:0:0:0:0:0:0/32^32-64, 2405:3A00:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:D1:0:0:0:0:0/48^48-64, 2405:2600:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64, 2001:DD8:13:0:0:0:0:0/48^48-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2404:6600:0:0:0:0:0:0/32^32-64, 2406:5A00:0:0:0:0:0:0/32^32-64, 2406:1E00:6000:0:0:0:0:0/35^35-64, 2400:6900:0:0:0:0:0:0/32^32-64, 2400:BD00:0:0:0:0:0:0/32^32-64, 2001:DF0:4:0:0:0:0:0/48^48-64, 2404:139:300:0:0:0:0:0/43^43-64, 2404:139:3FF:0:0:0:0:0/56^56-64, 2406:1A00:0:0:0:0:0:0/32^32-64, 2400:E700:0:0:0:0:0:0/32^32-64, 2402:CC00:0:0:0:0:0:0/32^32-64, 2403:A00:0:0:0:0:0:0/32^32-64, 2405:B400:0:0:0:0:0:0/32^32-64, 2001:500:3:0:0:0:0:0/48^48-64, 2403:B700:0:0:0:0:0:0/32^32-64, 2403:F700:0:0:0:0:0:0/32^32-64, 2001:DF0:2BB:0:0:0:0:0/48^48-64, 2400:4800:4006:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120720 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.14.217.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.59.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.176.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120720 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.14.217.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.59.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.176.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120720 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.14.217.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.59.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.176.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120720 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.150.160.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 182.236.120.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.3.80.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.90.56.0/21^21-29, 202.160.112.0/21^21-29, 202.189.160.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.2.120.0/22^22-29, 103.8.232.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.192.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.90.44.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 117.53.150.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.88.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 202.162.72.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 210.54.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.14.3.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.0/24^24-29, 199.7.83.0/24^24-29, 202.6.5.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.14.217.0/24^24-29, 202.20.97.0/24^24-29, 202.21.128.0/24^24-29, 202.21.130.0/24^24-29, 202.27.8.0/24^24-29, 202.27.83.0/24^24-29, 202.27.204.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.70.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.170.0/24^24-29, 202.36.221.0/24^24-29, 202.36.227.0/24^24-29, 202.37.17.0/24^24-29, 202.37.72.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.181.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.187.0/24^24-29, 202.46.188.0/24^24-29, 202.49.59.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.176.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.57.145.0/24^24-29, 203.92.25.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Aug '12

08 Aug '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 180.189.192.0/19^19-29, 202.14.32.0/19^19-29, 202.50.192.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 103.5.72.0/22^22-29, 113.197.64.0/22^22-29, 114.31.212.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 103.4.121.0/24^24-29, 103.8.80.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 182.236.127.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.134.48.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: engineering(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120426 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 120.138.16.0/20^20-29, 210.56.32.0/20^20-29, 223.165.64.0/20^20-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 103.5.72.0/22^22-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 114.134.176.0/23^23-29, 202.36.76.0/23^23-29, 202.37.240.0/23^23-29, 205.233.136.0/23^23-29, 210.4.212.0/23^23-29, 103.8.80.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.27.140.0/24^24-29, 202.27.208.0/24^24-29, 202.36.45.0/24^24-29, 202.36.183.0/24^24-29, 202.37.57.0/24^24-29, 202.37.73.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.46.181.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.0/24^24-29, 202.134.48.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120809 source: NZRR ------------------------------------------------------------

1 0

Changes to rs1.chix.nzix.net - 10am Monday
by Tim Hoffman 06 Aug '12

06 Aug '12

Greetings, As part of our continued effort to develop the NZIX route servers, we are planning to replace rs1.chix.nzix.net on Monday at 10am. We will observe a change freeze on the rest of our route servers nationwide (including rs2.chix.nzix.net) during this time. The new server is dual stacked and will support IPv6 on 2001:7FA:3:5F44::1/64. All the active peers have sessions pre-configured on this, your ipv6 address will be 2001:7FA:3:5F44::X/64, where X is the last octet of your v4 address (not a hex translation like we did to generate the APE v6 addresses) - i.e. if you are 218.100.24.17 then your v6 address will be 2001:7FA:3:5F44::17/64. The v6 peering is running now on this address for all peers, so please configure this up. Later next week we will be replacing rs2.chix.nzix.net with a dual stacked server also, we'll advise the details/timing of this once the rs1 replacement is complete. Changes of note include; Implementing v6 on the route servers. Only accepting up to /24's for v4 and /48's for v6. The only filtering we will provide is to deny bogon routes and defaults from peers. Also we are still on track to roll these changes out on the WIX in the next couple of weeks. Progress :). Feel free to drop me an email if you have any queries/comments regarding this. Regards, Tim

1 0

DNSSEC: co.nz now signed and deployment schedule for the moderated SLD
by Donald Neal 06 Aug '12

06 Aug '12

This message is forwarded on behalf of Sebastian Castro: ----- To our community: NZRS has completed today the deployment of DNSSEC for co.nz, enabling full validation for their sub-domains. All non-moderated second level domains now are DNSSEC-signed. InternetNZ has sent out a media release about this event http://tinyurl.com/crglf4z We also have added to our deployment calendar (http://nzrs.net.nz/dns/dnssec) the dates for the moderated second level domains. In summary, by the end of August the zones cri.nz, health.nz and iwi.nz will be signed. During the first two weeks of September, govt.nz, mil.nz, and parliament.nz will be signed, thus completing the DNSSEC schedule. Any DS records present in the registry for domains under those zones will be included as soon as the trust chain is completed. If you are keen to sign your domains, or they are already signed and need to submit DS records, a list of .nz Registrars who are either DNSSEC Friendly, or offer DNSSEC services can be found at http://dnc.org.nz/registrars Kind Regards, -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535 Donald Neal Senior Network Engineer Direct: +64 9 929 2958 Mobile: 0278081023 Fax: +64 9 929 2959

1 0

Pacific Fibre to Cease Operations - cites not enough investment.
by Joel Wirāmu Pauling 01 Aug '12

01 Aug '12

So if you haven't seen this; my question is if they don't have enough money to go "all the way" to LA why not at least re-align and put some NZ to AU fibre in? http://www.nzherald.co.nz/business/news/article.cfm?c_id=3&objectid=10823806 -JoelW @aenertia +64 21 171 8049

20 43

Network Engineer roles ?
by Ian Batterbee 01 Aug '12

01 Aug '12

Hi all, I'm a little hesitant to post this, because I can't recall what the result of the last discussion on 'is this list an appropriate place to ask about jobs going in the industry' was... So, if the feeling was that it was okay, and anyone has openings going for an experienced network engineer, please let me know off-list. And if not, please imagine some lovely green sunny grassy fields :/

2 1