- NZNOG - lists.nznog.org

TNC Christchurch
by Russell Tester 13 May '08

13 May '08

Hi all, I'd like to gauge the interest level for a Thursday night curry in Christchurch. I myself am becoming quite a curry fan, and unless my radar is faulty aren't aware of any similar regular event for like minded individuals down here in the south. If you are interested I'd appreciate a reply off list and if there is enough interest we can see about formalizing the proceedings. Cheers, Russ

1 0

ip ranges
by Vaafuti Alauni (Vaa) 13 May '08

13 May '08

Hi everyone, Hope anyone can help me here. My problem is, some of our IP ranges appear to be filtered by some network providers. Could anyone please point me to the right direction or unblock our ranges ? Our ranges are : 202.20.0.0/21 - I believe this does not have any issues 202.68.80.0/21 - some blocks in this /21 have issues connecting to some sites, 202.68.86.0/23 Thanks kindly

4 5

Orcon Bandwidth Issues today..
by Chris Hodgetts 12 May '08

12 May '08

Hello, I am just wondering if anyone else is experiencing issues with Orcon's bandwidth as of late. We seem to be getting about 87% packet loss from the following hop. 3. ge-0-3-0-200.cr1.nct.orcon.net.nz 87% 69 520 2 2 4 47 This seems to be causing issues more for download than upload, upload speeds +1.5mbit download speeds about 20 - 40kbps.... but that makes sense because out of the 520 packets, only 69 have been returned. I have noticed these issues for both National and International, however International more noticeable. Orcon advised that: Update (2008-05-12): The expected fix is taking slightly longer to deploy than we had originally anticipated. This should be resolved this week. ...This week... anyway.... I don't actually think that status was in relation to this, but I loved the "should be resolved this week". great estimate. I called Orcon today at about 16:45, but by the time anyone answered me it was just on 17:00 and all corp. support had gone home, but they assured it was being looked into, but could not give me a reference number. Anyway........... it's about time for a beer.... (not that I drink)

5 4

List of NZ ISP MTA IP Addresses
by Barry Murphy 07 May '08

07 May '08

Hi, Does anyone have a list of most of the NZ ISP MTA's? I'd like to set a negative score on as many as possible to ensure legit email isn't classed as spam. Off-list replies appreciated, if there is a lot of requests for the same info, I shall collect aggregate and forward on. Thanks in advance. Barry Murphy

2 1

Dunedin city fibre
by Stu Fleming 06 May '08

06 May '08

Anyone got specifics on the new fibre network being rolled out by Delta Utilities in Dunedin? Timeframes? Topology? Costs?

2 1

Mott returns to Internet Industry
by Peter Mott 06 May '08

06 May '08

Good morning people, A quick heads up that we are back. A huge thank you to my contractors and the team at Citylink for helping kick off the new venture. We currently have kit in Kingston St and have connected to the APE (AS45181), but expect to roll out in other locations over the coming months. I've also managed to sign up to InternetNZ (clearly nobody remembered me) and we will be applying to join ISPANZ soon. We look forward to sharing our beer budget (fruit cocktails anybody?) with you at the next NZNOG conference. p.s This message is not intended to be a breach of policy 6 of the list AUP regards Peter Mott Swizzle | Wholesale Hosted Servers -/-

2 1

NZRR Route Registry Update
by NZRR Database Notifications 06 May '08

06 May '08

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 - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.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.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-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, 199.212.92.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.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.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.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.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.232.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.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080318 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.0/21^21-29, 120.138.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.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-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, 199.212.92.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.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.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.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.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.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080507 source: NZRR ------------------------------------------------------------

1 0

Tui update - please accept my routes and give me free transit. No really. Please?
by Nathan Ward 03 May '08

03 May '08

Hello all, A few weeks back we were loaned 2 x /24s[1] and 2 x ASNs by APNIC R&D, big thanks to Geoff Huston. One ASN and /24 lives on the Tui route- server at APE, and the others on the Tui route-server at WIX. They are: - APE: AS24021 203.147.108.0/24 - WIX: AS45163 203.147.109.0/24 These /24s are used for the unit's 6to4 address, which is used for 2 things: - BGP peer address for remote Tui boxes. - Next hop for v6 routes from native exchange peers. These routes are only given to remote Tui boxes that are on networks that are visible from APE/WIX. The first Tui route-server has been installed by Andy on WIX today, we're looking to get the APE one in next week. If you are on WIX, can you please accept 203.147.109.0/24 from the WIX v4 route-servers. If you prefer private peering on the exchange we can do that too, drop me an email - nward(a)braintrust.co.nz. Same for the APE /24 next week. Now, that gets these two /24s visible to networks that are visible at APE/WIX, however that doesn't get us to networks that aren't. If you can see these two /24s, please transit them - ie. advertise them to your peers and transit providers. That let's networks that don't peer (for whatever reason) still use Tui boxes in their networks. If you transit these /24s, the only data you'll see going across your network to/from these networks is BGP traffic in 6to4. You won't see any actual data, just BGP control messages. The routing policy only gives next hops in these /24s if the remote Tui box is in a network visible to the exchange (in which case you won't transit packets for that network) - if it's not, it only gets information about other Tui boxes, and that data goes direct between Tui boxes. I've been trying to figure out how to explain this clearly in words.. hopefully that makes sense. I'll follow up with a picture if needed. In short - please accept and re-advertise those two /24s to your peers, customers, and internationally to help out this Tui project, they are very low traffic and only carry control data, I promise. We're talking kilobits per second here, so it's really nothing. Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you. Big thanks go to InternetNZ for hardware and support, APNIC for v4 and ASNs, and Citylink for exchange connectivity, hardware, etc. -- Nathan Ward Braintrust Ltd. nward(a)braintrust.co.nz +64-21-431675 [1] - No, the irony of burning 2 /24s to help encourage v6 adoption is not lost on me :-)

3 4

domain name nznog.org.nz
by Craig Whitmore 01 May '08

01 May '08

Hi there folks.. I've had "control" of the domain name nznog.org.nz for a quite a while ago after I retrieved it from the person who falsely registered it in 2003 (I'm not naming names but most of you know who it was). The question is.. at the moment it is not actually doing anything so does someone want it so they can use it with nznog as I'm thinking of just cancelling it at the moment. Thanks Craig

3 2

Request for Feedback: Industry Best Practice Programme
by Keith Davidson 01 May '08

01 May '08

Hello all, InternetNZ seeks input from NZNOG on a proposed Industry Best Practice Programme that would develop and document a range of local Internet operational and technical best practice standards. A brief overview of the Industry Best Practice Programme was given to NZNOG conference attendees in January, and we are looking for further feedback on the proposal via the NOG mailing list. InternetNZ Industry Best Practice Programme The proposed 'InternetNZ Industry Best Practice Programme' aims to create a community of technical practice in New Zealand by encouraging collaboration between network and service operators in defining best practice standards. Technical best practice documents would be developed by small working groups. These would form flexible codes of practice relating to the New Zealand Internet, allowing ISP's, content providers and other Internet service companies to select an overall best fit for their business. For instance, a DoS Response/Containment document would likely define and outline what steps would be taken in New Zealand should a large scale denial of service attack occur here. Other examples of best practice documents could include: - Routing Registry Practices - Use of BGP communities - Mail Server Operations - Peering Practices - Phishing Response/Containment - Emergency Response (Security) - Natural Disaster Response - Datacentre Standards and Classification Participants are more than welcome to suggest other best practice document topics. Development Process InternetNZ is looking to finalise a few areas of the proposed development process listed below: Best practice documents specifying New Zealand ICT industry-accepted technical practices and processes would be drafted by working groups comprising two to four technical/industry experts. Note: Working group members can be drawn from a range of NZ-based online communities and industry organisations such as NZNOG, e-Government, the TCF and ISPANZ. Draft documents, and subsequent iterations, would be floated on the NZNOG mailing list for open debate and discussion, to achieve broad consensus and approval. Following consensus, finalised drafts would be published by InternetNZ as a best practice document and filed on a public website. InternetNZ would promote and publish the finalised best practice documents, and provide administrative and secretarial support. Development Incentives To encourage development of best practice documents InternetNZ would provide a yearly travel grant, awarded to members of the top four successful working groups that have had documents published. Travel would be earmarked for international travel to technical conferences, with the published best practice document being presented and/or compared with similar best practices from other countries. The InternetNZ Technical Policy Committee will select which documents are subject to a development incentive. Your feedback on this proposal is most welcome. We are particularly interested in your views on how broad consensus would be achieved via the NZNOG list, and suggested approaches for defining the top four best practice working groups. Feel free to contact me off list also. Regards, Keith Davidson Executive Director - InternetNZ

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Apr '08

30 Apr '08

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list. The group is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference We hold New Zealand's only technical networking conference. See http://www.nznog.org/?page_id=4 for details of conferences from 2004 to 2008. Work is now under way in preparation for the next conference, to be held in the North Island in early 2009. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland, Hamilton or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has between 900 and 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Kiwicon 2k8 - Call For Papers
by Simon Howard 30 Apr '08

30 Apr '08

[-------------------------------------------------------------------------] _.-.. __ .__ .__ ,'9 )\)`-.,.--. | | _|__|_ _ _|__| ____ ____ ____ 2k8 `-.| `. | |/ / \ \/ \/ / |/ ___\/ _ \ / \ \, , \) | <| |\ /| \ \__( <_> ) | \ `. )._\ (\ |__|_ \__| \/\_/ |__|\___ >____/|___| / |// `-,// \/ \/ \/ ]|| //" "" "" BAAAAAAaaaa!!11 [-------------------------------------------------------www.kiwicon.org---] Holy sheepshit, internets! Blanket-Man[1] has wrung out his loin cloth and is ready to fly-tackle more heavy metal t-shirt wearing nerds with large egos and irc handles. Yes, it's time to open up your ~/haxing folder and get your talk together for Kiwicon 2k8! We've put out the black t-shirts, and deflated some satellite radomes, so where, as our more criminal yet fetchingly bikini clad cousins might say, the bloody hell are you? The Kiwicon Crüe is proud to announce the call for presenters for the second installment of New Zealand's very own security conference: Kiwicon 2k8. [About] Kiwicon2k8 is intended to be an informal conference, drawing on the wider security community of Australia and New Zealand. It will be held in Wellington, New Zealand, on the weekend of the 27th and 28th of September, 2008. Kiwicon's focus is on sharing information; ideas, code, and good whisky, in a rabelaisan carnival of security, nerdery, and *nix beards. Last year, the inaugural Kiwicon ended up being kind of a big deal: highlights included tmasky's mighty Crackstation, the debut of Beau Butler as an "ethical hacker" making Microsoft "look like turkeys", and of course the Kiwicon Hax0r Quiz, with the winner taking the grand prize of An Illustrated Guide to the Commoner Skin Diseases. Hope it came in handy for the post-con diagnosis phase, dude. This year, Kiwicon's own Bogan is already making anti-virus vendors quake in their little signature-laden booties at Defcon's Race to Zero, and the cauldron of 0h-0h-0hday in Brett Moore's secret Insomnia lair is bubbling over with pernicious brew. If you missed last Kiwicon (not "professional enough"? couldn't convince your boss it wasn't a hoax?) then find one of the 230+ people who were there and ask them if they're just-not-gonna-bother this year. [Venue] Our hosts for the weekend will, once again, be Victoria University of Wellington. If you have any memory of last year's Kiwicon, then it'll look disturbingly familiar. The campus has the advantage of being close to the center of the city and its' various amenities. This includes cheap accommodation, good coffee, and, more importantly, several good pubs serving good, non-Australian, beer. [Costs] Kiwicon2k8 is a non-profit, non-commercial, non-corporate-funded event. Attendance for the entire weekend will cost $50 for employed individuals (self-employed and salaried). There is a discounted rate of $30 for students and the unemployed. GST receipts can be issued upon request. If your management can't be convinced of the value of something that only costs $50, we're happy to issue you with some kind of personalised limited edition invitation in crayon, glitter pen, and macaroni (spray-painted gold for that luxe look) for the low enterprise-only price of $500. [Topics] Suggested topics include but are not limited to: - Crowd Control Techniques and Panic Modeling - Information Warfare / Industrial Espionage - Malware (Viruses, Spam, Phishing, Botnets) - Cellular Networks (GSM,GPRS,CDMA,3G,4G) - Application Security, Testing, Fuzzing - Government Spy Networks / Surveillance - Nanotechnology / Quantum Computing - Access Control and Authentication - Wireless / Bluetooth / Infrared - Social Engineering / Trolling - Breaking EAL Certified Kit - Forensics / Antiforensics - Banking / ATMs / Carding - Exploitation Techniques - Layer 1/2/3 Nastiness - Reverse Engineering - Phreaking / VoIP - Virtualisation - Web Security - Lockpicking - Biometrics - Hypnosis - Crypto - Ohday - 23 There is no pre-determined talk length but we ask that speakers limit their presentation to an hour, including some question time. Since Kiwicon is a non-profit organisation, there is no funding available for travel and/or accomodation, even for IT rockstars. However, if your talk is accepted, a formal letter will be provided for employer leverage, and almost certainly, unless you're a complete jackoff, people will try and buy you beer. To submit a presentation to Kiwicon2k8, send an email to cfp(a)kiwicon.org with the following information: Name or Handle: Country of Residence: Employer (if applicable): Presentation Title: Presentation Length: Presentation Synopsis: Brief Bio: [CFP Submissions] Please submit your CFP by email to cfp(a)kiwicon.org, no later than 8:47pm NZST, Sunday 17th August 2008. There will be two rounds of selection, with the first half of the talks chosen in early August, so submit early for a better chance of acceptance. [Contacts & Further Information] Email us: kiwicon(a)kiwicon.org Check the site: http://www.kiwicon.org/ Drop by silc: silc.isig.org.nz:2706/kiwicon Join the list: kiwicon-subscribe(a)lists.isig.org.nz Greetz and thanks to all who helped make Kiwicon 2k7 the awesomeness it was, we'll see you fuckers again this year. Thick, meaty props to Pipes for stepping up and making 2k7 happen. We would miss you, but Sharrow's just as tall, and better looking. Sorry pal. -- The Kiwicon Crüe, 2k8 - Bogan, Metlstorm & Sharrow. \m/ [1] http://en.wikipedia.org/wiki/Ben_Hana

1 0

Carrier-neutral colo and peering in Auckland
by Mark Newton 24 Apr '08

24 Apr '08

Hi. I'm after some information about carrier-neutral colocation in the Auckland area in New Zealand. I'd be looking at installing a rack worth of equipment, consuming a couple of kW of power at most. It'd need to be in a facility that's well- serviced by TNZ, TelstraClear or Vector Communications; But preferably able to interconnect with arbitrary other carriers so that we can provide our Australian business/corporate/wholesale customers with IP and MPLS access to their NZ offices (or vice versa) with minimal obstacles. Nearby availability of peering exchanges would be a definite plus. AS4739 has a fairly promiscuous peering policy, and we prefer bilateral peering relationships outside Australia, but MPLA works for us too if it's easy. I'm a bit of a novice when it comes to the New Zealand "scene". If anyone feels inspired to send me some off-list information or advice, I'd appreciate it. Regards, - mark -- Mark Newton Email: newton(a)internode.com.au (W) Network Engineer Email: newton(a)atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82282999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223

3 2

Re: [nznog] Carrier-neutral colo and peering in Auckland (MRN)
by Marc Richard Nienkemper 23 Apr '08

23 Apr '08

Hi Mark, I've sent you a message off-list. Cheers, MRN -----Original Message----- From: nznog-request(a)list.waikato.ac.nz [mailto:nznog-request(a)list.waikato.ac.nz] Sent: Thursday, April 24, 2008 12:00 PM To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 64, Issue 11 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. Carrier-neutral colo and peering in Auckland (Mark Newton) 2. Re: Carrier-neutral colo and peering in Auckland (Jonathan Brewer) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Apr 2008 21:14:42 +0930 From: Mark Newton <newton(a)internode.com.au> Subject: [nznog] Carrier-neutral colo and peering in Auckland To: NZNOG(a)list.waikato.ac.nz Message-ID: <177FDD80-E69B-4CCD-BA6E-BC2A532113F5(a)internode.com.au> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hi. I'm after some information about carrier-neutral colocation in the Auckland area in New Zealand. I'd be looking at installing a rack worth of equipment, consuming a couple of kW of power at most. It'd need to be in a facility that's well- serviced by TNZ, TelstraClear or Vector Communications; But preferably able to interconnect with arbitrary other carriers so that we can provide our Australian business/corporate/wholesale customers with IP and MPLS access to their NZ offices (or vice versa) with minimal obstacles. Nearby availability of peering exchanges would be a definite plus. AS4739 has a fairly promiscuous peering policy, and we prefer bilateral peering relationships outside Australia, but MPLA works for us too if it's easy. I'm a bit of a novice when it comes to the New Zealand "scene". If anyone feels inspired to send me some off-list information or advice, I'd appreciate it. Regards, - mark -- Mark Newton Email: newton(a)internode.com.au (W) Network Engineer Email: newton(a)atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82282999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 ------------------------------ Message: 2 Date: Thu, 24 Apr 2008 07:29:41 +1200 From: "Jonathan Brewer" <jon.brewer(a)araneo.net.nz> Subject: Re: [nznog] Carrier-neutral colo and peering in Auckland To: <NZNOG(a)list.waikato.ac.nz> Message-ID: <20080423192935.AB9153E0010(a)mx1.its.waikato.ac.nz> Content-Type: text/plain; charset="us-ascii" Hi Mark, It's hard to beat Sky Tower if you want a facility that's well serviced by New Zealand telecommunications providers. All the providers are there in some way or another. APE and F-Root servers are there. The tower managers, JDA, are not related to any of the carriers, so they're as neutral as you can get. Drawbacks are fairly limited and relatively expensive floor space and cooling options. Good for routers and switches, maybe not so good for blade servers or high-density, high heat applications. Cheers, Jon www.araneo.net.nz -----Original Message----- From: Mark Newton [mailto:newton(a)internode.com.au] Sent: Wednesday, 23 April 2008 11:45 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] Carrier-neutral colo and peering in Auckland Hi. I'm after some information about carrier-neutral colocation in the Auckland area in New Zealand. I'd be looking at installing a rack worth of equipment, consuming a couple of kW of power at most. It'd need to be in a facility that's well- serviced by TNZ, TelstraClear or Vector Communications; But preferably able to interconnect with arbitrary other carriers so that we can provide our Australian business/corporate/wholesale customers with IP and MPLS access to their NZ offices (or vice versa) with minimal obstacles. Nearby availability of peering exchanges would be a definite plus. AS4739 has a fairly promiscuous peering policy, and we prefer bilateral peering relationships outside Australia, but MPLA works for us too if it's easy. I'm a bit of a novice when it comes to the New Zealand "scene". If anyone feels inspired to send me some off-list information or advice, I'd appreciate it. Regards, - mark -- Mark Newton Email: newton(a)internode.com.au (W) Network Engineer Email: newton(a)atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82282999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ------------------------------ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog End of NZNOG Digest, Vol 64, Issue 11 *************************************

1 0

Contracts and FX Networks
by Andrew Hooper 21 Apr '08

21 Apr '08

I would be interested to know if any of the small operators have successfully negotiated a contract with FX Networks and how was your experience from the negotiation to implementation? Andrew Hooper www.bushwireless.com <http://www.bushwireless.com/> +64 9 533-6470 +64 21 212-9200 broadband for those hard to reach places. <skype:bushwireless?call> My status <http://www.skype.com/go/download> Get Skype and call me for free.

1 0

Invitation to APNIC 26
by Elly Tawhai 21 Apr '08

21 Apr '08

Hi NZNOG Community, For those who do not know the next APNIC meeting will be held in Christchurch, New Zealand on 25-29 August 2008. ________________________________________________________________________ Why your organisation should be represented at APNIC 26? ________________________________________________________________________ It is our pleasure to invite your organisation to attend the APNIC 26 meeting a week of workshops, tutorials, policy and operational discussions, and social events. Attending APNIC 26 will enable your organisation to: - Have your say on policy proposals that directly affect the way your organisation accesses Internet number resources; or, you can present your own proposals - Hear world-class speakers discuss cutting edge Internet resource management research such as IPv6 transition and network security - Learn about best practice in Internet resource management to make your business more efficient and profitable - Make valuable contacts for building business relationships When: 25-29 August 2008 Venue: Christchurch Convention Centre, Christchurch, New Zealand For more information about APNIC 26 and how you can participate, please see: http://www.apnic.net/meetings/26 Hope to see you there! Kind regards, Elly ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Senior Internet Resource Analyst, APNIC sip: hostmaster(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '08

14 Apr '08

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: AS9560:RS-ROUTES:AS10200 descr: advertised to AS9560 by NetSmart Ltd - AS10200 members: 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.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: paul(a)netsmart.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060306 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10200 descr: advertised to AS9560 by Netsmart Ltd - AS10200 members: 124.248.128.0/20^20-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.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: shaun(a)netsmart.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080415 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '08

14 Apr '08

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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080205 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080415 source: NZRR ------------------------------------------------------------

1 0

500-mile email limit
by Matthew Poole 13 Apr '08

13 Apr '08

http://www.ibiblio.org/harris/500milemail.html A wee bit OT, but not hugely. And rather amusing all the same. -- Matthew Poole "Don't use force. Get a bigger hammer."

2 1

NZRR Route Registry Update
by NZRR Database Notifications 10 Apr '08

10 Apr '08

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: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080411 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080411 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Apr '08

10 Apr '08

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: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080411 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Apr '08

10 Apr '08

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: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia Limited - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080227 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080411 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Apr '08

09 Apr '08

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:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080410 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Apr '08

09 Apr '08

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:AS17705 descr: advertised to AS9439 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17705 descr: advertised to AS9439 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.0/24^24-29, 203.92.25.0/24^24-29, 210.7.46.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080410 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Apr '08

08 Apr '08

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:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080409 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Apr '08

08 Apr '08

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: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080409 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Apr '08

08 Apr '08

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:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080409 source: NZRR ------------------------------------------------------------

1 0

DNS/SMTP/Mailservers "doing it wrong"
by Phil Snowdon 06 Apr '08

06 Apr '08

Why can't people correctly configure Mail and DNS correctly these days. If all legitimate mail servers had their forward and reverse DNS mapping configured correctly I could simply use the postfix reject_unknown_reverse_client_hostname, and instantly get rid of 10s of 1000's of unwanted spam messages. However there are many servers set up in NZ where the forward and reverse DNS do not match, or there are no PTR records at all. After all this is outlined in RFC 1912 (section 2.1) and RFC 1033 Most of the big ISP mail servers are OK, but then they have customers running their own mailservers and this is where the problem lies. I have some numbers from tests over the weekend and it doesn't look good. I am being too hopeful to expect mailservers to be configured correctly? I'm stuck between wanting to do things properly and help reduce SPAM on one side, and having customers on the other saying why can't I get mail from XXX. While I can make an effort to try and contact the administrators of these mail servers the shear numbers make it difficult and even then i imagine the response would be 'well i can deliver mail to xxxx so it must be your systems that are broken'. I know this isn't a silver bullet by any means, but every little helps. Any comments? Phil

9 10

NZRR Route Registry Update
by NZRR Database Notifications 06 Apr '08

06 Apr '08

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: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080129 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080407 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 06 Apr '08

06 Apr '08

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: 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080129 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080407 source: NZRR ------------------------------------------------------------

1 0

Kordia/PIPE Trans-tasman link..
by Simon Lyall 06 Apr '08

06 Apr '08

Kordia and PIPE sign MoU to build new trans-Tasman submarine cable http://www.kordiasolutions.com/node/1203 -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

adding looking glass field to NOC list?
by Martin Barry 01 Apr '08

01 Apr '08

i was just trying to track down looking glasses in NZ to check how people were seeing routes advertised by $work[0]. none of the global lists i came across listed any NZ ones. any pointers to existing lists would be appreciated. a suggestion would be to add that kind of information to the NOC list (http://www.nznog.org/?page_id=6) for ASes that have a looking glass. cheers marty -- M. Cullen "I suffered from chronic hypochondria for years, eventually went to a naturopath, and was cured with a course of broad-spectrum placebos." [1] [1] - http://www.smh.com.au/articles/2003/12/08/1070732142498.html

4 6

PING!
by Drew Broadley 31 Mar '08

31 Mar '08

....

3 2

The New Zealand Network Operators' Group
by Donald Neal 31 Mar '08

31 Mar '08

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list. The group is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference We hold New Zealand's only technical networking conference. If you weren't there this year, take a look at http://2008.nznog.org/ and http://www.r2.co.nz/20080124/ to see what you missed. Work is now under way on preparation for the next conference, to be held in the North Island in early 2009. An announcement of the location and dates should be made later this month. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland, Hamilton or Wellington. Operators' Contact List See http://www.nznog.org/ and follow the link "NOC List" for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has between 900 and 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Citylink, Telecom and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

.co.nz Domains
by bigalownz 29 Mar '08

29 Mar '08

can someone tell me why .co.nz domains are the most expensive domains ? where as most are about $6 - $15 but .co.nz are $30 - 60 and even $100 thanks

13 15

NZRR Route Registry Update
by NZRR Database Notifications 27 Mar '08

27 Mar '08

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:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071129 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Mar '08

27 Mar '08

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:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071129 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Mar '08

27 Mar '08

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: AS9560:RS-ROUTES:AS23655 descr: Route set advertised to AS9560 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: james(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071024 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.146.186.0/24^24-29, 203.96.112.0/24^24-29, 210.7.40.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080328 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 17 Mar '08

17 Mar '08

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 - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-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.50.200.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-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, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.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.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.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.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.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.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.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.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.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.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-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, 199.212.92.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.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.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.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.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.232.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.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080318 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 17 Mar '08

17 Mar '08

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: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-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.50.200.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-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, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.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.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.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.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.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.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.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.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070221 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.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.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-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, 199.212.92.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.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.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.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.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.232.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.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080318 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 15 Mar '08

15 Mar '08

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: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 97.64.46.0/24^24-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061116 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 174.128.16.0/20^20-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 198.32.71.0/24^24-29, 202.7.5.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080316 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 15 Mar '08

15 Mar '08

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:AS23754 descr: advertised to AS9439 by Citylink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 97.64.46.0/24^24-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.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: simon(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070423 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 174.128.16.0/20^20-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 198.32.71.0/24^24-29, 202.7.5.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080316 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '08

09 Mar '08

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:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '08

09 Mar '08

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: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29, 192.138.251.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '08

09 Mar '08

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:AS17705 descr: Route set advertised to AS9439 by Inspire Net - AS17705 members: 203.79.88.0/24^24-29, 203.79.89.0/24^24-29, 203.96.157.0/24^24-29, 203.114.128.0/18^18-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)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050307 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17705 descr: advertised to AS9439 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 121.79.192.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080310 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Who has WiFi for Viaduct Harbour?
by peter＠team.swizzle.co.nz 06 Mar '08

06 Mar '08

If I was a visitor to NZ I might find your comment a little unhelpful if not offensive, but since I am a Kiwi and well known to many here, I am more than a little puzzled by your sharp rebuke. The reality is there is a significant international event on here and lots of inbound visitors, many who are used to having access to public wifi wherever they go. There was not only a lost opportunity for revenue here, but we are sending some international people away with a poor impression of our country. -------------------------- -----Original Message----- From: "Harris, Chris" <C.J.Harris(a)massey.ac.nz> Date: Fri, 7 Mar 2008 16:36:28 To:<peter(a)team.swizzle.co.nz> Subject: RE: [nznog] Who has WiFi for Viaduct Harbour? Go home then -----Original Message----- From: peter(a)team.swizzle.co.nz [mailto:peter(a)team.swizzle.co.nz] Sent: Thursday, 6 March 2008 3:43 p.m. To: Jonathan Brewer; nznog List Subject: Re: [nznog] Who has WiFi for Viaduct Harbour? I have a big boat for sale down there and also have heard people asking about. Connecting via iridium to send email is rather expensive, but hey this is a third world country afterall. -------------------------- -----Original Message----- From: "Jonathan Brewer" <jon.brewer(a)araneo.net.nz> Date: Thu, 6 Mar 2008 15:13:15 To:<nznog(a)list.waikato.ac.nz> Subject: [nznog] Who has WiFi for Viaduct Harbour? Hi Folks, We've had a bunch of requests recently for WiFi coverage of the Viaduct in Auckland. - WiFi isn't something we do - I've seen a heap of 2.4GHz gear at Sky Tower pointed down at the Viaduct Can anyone step forward and take these eager requests off our hands? Thanks, Jonathan Brewer -------------------------------- Araneo Limited 232A Left Bank 116 Cuba Street Wellington 6011 ph: 04 978 7350 fx: 04 978 7355 mb: 021 345 054 -------------------------------- _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Akamai hosted content (corrupted downloads, slow speed)
by Stewart Fleming 05 Mar '08

05 Mar '08

Hi, We are seeing some weird issues with downloads from Akamai sourced content to some but not all of our network addresses. Typically the issues that we see are slow download speeds (20KB/sec) and corrupted downloads (e.g. compressed EXE will not execute). We first noticed this issue last year with the cut in the fibre between Manila and Hong Kong, but then it cleared up only to recur about a week ago. Two questions: - has anyone else in the NZNOG community experienced similar issues in the same timeframe? - what is the best avenue to pursue to resolve this issue with Akamai directly? (I've tried e-mailing ccare(a)akamai.net but have yet to hear back) Thanks for any advice. Regards, Stu

1 0

Who has WiFi for Viaduct Harbour?
by Jonathan Brewer 05 Mar '08

05 Mar '08

Hi Folks, We've had a bunch of requests recently for WiFi coverage of the Viaduct in Auckland. - WiFi isn't something we do - I've seen a heap of 2.4GHz gear at Sky Tower pointed down at the Viaduct Can anyone step forward and take these eager requests off our hands? Thanks, Jonathan Brewer -------------------------------- Araneo Limited 232A Left Bank 116 Cuba Street Wellington 6011 ph: 04 978 7350 fx: 04 978 7355 mb: 021 345 054 --------------------------------

3 2

NZRR Route Registry Update
by NZRR Database Notifications 03 Mar '08

03 Mar '08

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: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CALLPLUS - AS9790 members: 119.224.0.0/17^17-29, 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 119.224.128.0/20^20-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080304 source: NZRR ------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 02 Mar '08

02 Mar '08

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list. The group is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference We hold New Zealand's only technical networking conference. If you weren't there this year, take a look at http://2008.nznog.org/ and http://www.r2.co.nz/20080124/ to see what you missed. Work is now getting under way on preparation for the next conference, to be held in the North Island in early 2009. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland, Hamilton or Wellington. Operators' Contact List See http://www.nznog.org/ and follow the link "NOC List" for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has between 900 and 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Citylink, Telecom and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

'Registering' a DNS server
by Gerard Creamer 27 Feb '08

27 Feb '08

We've just set up a new DNS server for a client whose domain name is a .co.nz name, and we can't make it a primary or secondary for .com or .net names. In the (distant) past we've 'registered' name servers with Network Solutions, and then it's been all good. Now that the registries are with Verisign there seems to be no way to register anything other than a name server on a .com or .net name, and that has to be completed via the registrar (Tucows, Godaddy etc). I'm not sure whether I'm being particularly dense or if this is actually a difficult thing to do - can someone please let me know what the process is now for registering a .nz server to enable it to be a primary or secondary for .com or .net names. Thanks, Gerard

13 22

Re: [nznog] heads up to registries re Day in the Life of the Internet
by k claffy 27 Feb '08

27 Feb '08

hi folks, many of you have already heard about it, but we want to remind folks of the 'day in the life of the Internet' 2008 experiment: we're coordinating dns (and possibly other types of) measurements from a single (2)day period in mid-march 2008. we will repeat our simultaneous root server collections from 2007, and try to expand our coverage to include other TLDs, and hopefully data from other levels of the hierarchy, e.g., caching resolver data. we'd also like to compare statistics from secured vs unsecured zones. we're hoping this experiment provides data to help answer questions operators care about, e.g., IPv6 adoption, DNSSEC adoption, pollution to root servers, use of unallocated addresses in the wild, reverse DNS deployment, <send us your questions> (working list at: http://www.caida.org/projects/ditl/questions/ ) OARC is providing special support for this project, and Duane is executing some practice runs with participations this week, to test measurement/transport logistics. DNS-based participation should not require much work, ideally running 'dnscap' on/near DNS server(s) and sending the pcap files to OARC: (public.oarci.net) but there are other methods of participation too, depending on your policy constraints. (indexing data into datacat and controlling distribution of the data through your own AUP, or submitting more "cooked" data, e.g., logfile summaries, RRD graphs, reports based on data collected internally by networks during the DITL dates. if you are interested in donating the time and energy and (some form of) data to this project, please let duane, kenjiro, or me know and we'll get you started. URLs with details: http://www.caida.org/projects/ditl/ duane's nanog talk last week: http://www.caida.org/publications/presentations/2008/nanog_dw_ditl/ dns-specific guidance: http://www.caida.org/research/dns/roottraffic/dnsroot_measurement_recommend… thanks, k

1 0

YouTube "IP hijacking"
by Juha Saarinen 26 Feb '08

26 Feb '08

Fat thread on NANOG: http://www.merit.edu/mail.archives/nanog/msg06299.html Did anyone in NZ notice? -- Juha

5 7

NZRR Route Registry Update
by NZRR Database Notifications 26 Feb '08

26 Feb '08

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: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080213 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia Limited - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080227 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Feb '08

26 Feb '08

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: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071213 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080227 source: NZRR ------------------------------------------------------------

1 0

OSPF on a Mac
by Matthew Poole 25 Feb '08

25 Feb '08

Greetings all Anyone know of any implementations of OSPF that run on OS X? Preferably something I don't have to build from source, but from what little I've found on Google thus far I don't think that's an option. -- Matthew Poole "Don't use force. Get a bigger hammer."

3 2

Orcon DSL (Beer Involved)
by Jasper Bryant-Greene 21 Feb '08

21 Feb '08

If there's anyone on the list from Orcon and/or Telecom who has the ability to provision Orcon DSL by midnight tonight to a Wellington address for a broadband monitoring company who shall not be named, I would appreciate a ping off-list. Significant quantities of beer are involved. -jasper

1 0

Update to the IPv4 Registry¹s Format and Content
by Leo Vegoda 21 Feb '08

21 Feb '08

This message has been sent to several lists. I apologise for duplicates. IANA has improved the format for the IPv4 Address Space registry. At the same time, the entries that were marked ³Various Registries² have been replaced with references to the Regional Internet Registry (RIR) that provides WHOIS and reverse DNS service for that /8 allocation. If you want to machine-process the IPv4 registry, the new fields are: * Prefix * Designation * Date * Whois * Status * Note where the Date will always be of the form ³YYYY-MM² and the status has the following possible values: RESERVED, LEGACY, ALLOCATED and UNALLOCATED /8 allocations that contain legacy assignments in them that are now managed by the RIRs have the text ³Administered by² in the Designation column. Legacy assignments refer to IP address allocations made before the RIR system was established. Reserved address space held by IANA does not have a date listed. The registry can be found at: http://www.iana.org/assignments/ipv4-address-space If you have questions about the structure of the new format, please send e-mail to iana(a)iana.org. Kind regards, Leo Vegoda Manager, Number Resources - IANA

1 0

Using nolisting to reduce spam
by Glen Eustace 19 Feb '08

19 Feb '08

Yesterday, I came across the concept of 'nolisting' as a technique for reducing the volume of inbound spam. It wasn't something I had previously come across so have done some reading on the topic. http://nolisting.org as a starting point. For such a simple technique, I was surprised by its impact. Simply speaking, the idea is to use a primary MX that doesn't listen on port 25 but simply rejects the connection. Well behaved MTAs will all try the secondary MX(es) and delivery will occur. Many spambots only try the primary so there is an immediately benefit, less inbound to check in other ways and a consequential increase in the available resources on the mail server(s). I set it up on one domain and behavior seems to be exactly as described. My reading suggests that there is no negative impact on legitimate mail and no noticeable additional latency in delivery as the switch from the primary to secondary on a reject is almost instantaneous. I was wondering whether anyone else has had any experience with this technique and if so whether the claim that it has no negative impact is true. Also, if people haven't heard of it, it may be something people might want to look at as another weapon in the anti-spam war. Glen.

18 24

query_status: 440 Request Denied Another one bites the dust
by Barry Murphy 18 Feb '08

18 Feb '08

query_status: 440 Request Denied from 4 sources, including dnc site. Barry

3 2

DNS sub-domain best practice
by Matthew Poole 18 Feb '08

18 Feb '08

My employer (part of a large educational institution) is delegated a bunch of 4LD zones within our org's 3LD space. These are utilised in a flat fashion, with staff machines, lab machines and servers all present as hosts inside various 4LDs. One 4LD has literally thousands of For obvious reasons, I'd like to move at least some stuff into 5LD space, starting with the labs. However, when I suggested this, my boss shot me down with "Too much typing. If it's a problem then we should differentiate at the 4th level." The only way to deal with that kind of attitude would appear to be a formal proposal (there are other issues in our DNS that need to be tidied up, so it's not just a proposal for this one thing), and I want to include some industry references about best practice in zone structuring. However, Google's not being kind to me at present. All it wants to tell me about is AD and MS DNS, and we're using bind so that doesn't translate so well. Anyone got some guides that I can refer to when I talk about why we shouldn't be using the 4LD as our functional level for all things? -- ËMatthew Poole "Don't use force. Get a bigger hammer."

2 1

Local Government Broadband Forum
by Richard Naylor 17 Feb '08

17 Feb '08

The above event will be webcast live, after a change in plans. The URL for the webcast is http://www.r2.co.nz/20080220/ There are test tones and bars on the streams now for interested folks to test their connectivity. The test pattern will be replaced by live video and/or audio on Wednesday and Thursday morning. The recorded video of the event will be available in the week beginning 25 February. Richard

1 0

Upcoming APNIC EC elections.
by Jonny Martin 17 Feb '08

17 Feb '08

[apologies for duplicates] Hi All, For those of you not already aware, the APNIC Executive Council elections are coming up, due to close at the 25th APNIC Open Policy Meeting in Taipei (25 - 29th Feb 2008). David Hughes from Australia has been nominated for the EC and would make both for a great member to represent the internet interests of Australia, NZ, and South Pacific. There hasn't been an ANZ based person on the EC since Geoff Huston in 2003. Given the impending implosion of the v4 internet it's a pretty important time for the ANZ/ Pacific internet community to have a member on the EC familiar with the region and it's many challenges. David has a wealth of experience, and has been heavily involved in the APNIC and operator community in the Asia Pacific region for many years now. He is a most suitable candidate for this role. More info on David here: http://www.apnic.net/meetings/25/elections/ec/david_hughes.html Wondering why you should care? The EC are effectively the Board of Directors of APNIC. They set the budget, fee schedules, provide policy and strategic guidance to APNIC, and a host of other duties outlined at: http://www.apnic.net/ec/ec-role.pdf If you don't know already, then find out who your APNIC corporate contact is and make sure they get involved and vote. Online voting opens on 13 Feb. I'll be at APNIC25 so if you don't want or have time, or care to vote, then it's easy to appoint a proxy to vote on your behalf. I'm more than happy to do this for you - all you have to do is fill out the proxy form below. Form already filled out with my details for your convenience. I'm also happy to relay any comments or questions you have on the policy proposals being discussed at the meeting. Details of current proposals are at: http://www.apnic.net/meetings/25/ Cheers, Jonny. APNIC Proxy voting form. (taken from http://www.apnic.net/meetings/ proxy.html) (Note that there are also SIG and AsiaPac NRO votes taking place at APNIC25, you can fill out the proxy form with specific votes you want here, or entrust me to make an appropriate choice). --- Proxy voting form APNIC Member Meeting - 29 Feb 2008 To register your proxy, please print and complete this form and return it by fax to +61-7-3858-3199 before 9:00am Taipei time (UTC +8:00) on Wednesday, 27 February 2008. Note: Your APNIC Membership must be current on the day of the meeting, in order for your proxy to have effect. I/We ___________________________________________________________ (person's name) of _____________________________________________________________ (company name) being a member of APNIC with _______________ votes HEREBY APPOINT _____________Jonny Martin________________________ (person's name) of _________________________FX Networks_________________________ (company name) or failing him/her ________________________________________________________________ (person's name) of _____________________________________________________________ (company name) to be my/our proxy to vote for me/us at the meeting of members to be held on 29 February 2008 and at any adjournment thereof. _______Voting for David Hughes from Melbourne IT________________ (Any restrictions on voting to be inserted here) Signed this _____________ day of ____________________ _________ (day) (month) (yr) ________________________________________________________________ (member's account name - eg "ABCNET-AP") ________________________________________________________________ (member's signature) ________________________________________________________________ (member's contact phone number) ________________________________________________________________ (member's contact facsimile number) ________________________________________________________________ (member's contact email address) ---

2 1

NZNOG '08 Presentation Videos
by Dean Pemberton 14 Feb '08

14 Feb '08

Hi all. R2 have the NZNOG 2008 Presentation videos up on their website. http://www.r2.co.nz/20080124/ Knock yourself out. =) Dean

2 1

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '08

14 Feb '08

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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 changed: rpsl-admin(a)nzix.net 20070716 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian Based on the work done at Team Cymru http://www.team-cymru.org/?sec=8&opt=25 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 changed: rpsl-admin(a)nzix.net 20070716 changed: rpsl-admin(a)nzix.net 20080215 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '08

14 Feb '08

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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 changed: rpsl-admin(a)nzix.net 20070716 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 14.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 46.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 changed: rpsl-admin(a)nzix.net 20070716 source: NZRR ------------------------------------------------------------

1 0

173/8 and 174/8 allocated to ARIN
by Leo Vegoda 14 Feb '08

14 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to ARIN in February 2008: 173/8 and 174/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Kind regards, Leo Vegoda Manager, Number Resources - IANA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHtItTvBLymJnAzRwRAq4hAJsF7zELnkKFSHvGccPpoCK+ypwOLgCfZYgA YJOrIPDwVY2rkq7tQ+wXPAo= =Ame2 -----END PGP SIGNATURE-----

1 0

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

12 Feb '08

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: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.171.4.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080213 source: NZRR ------------------------------------------------------------

1 0

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

12 Feb '08

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: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 116.90.132.0/24^24-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080213 source: NZRR ------------------------------------------------------------

1 0

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

12 Feb '08

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:AS9245 descr: advertised to AS9439 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070813 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9245 descr: advertised to AS9439 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 116.90.132.0/24^24-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.30.174.0/24^24-29, 203.171.4.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080213 source: NZRR ------------------------------------------------------------

1 0

BNZ Scam
by Tim Price 10 Feb '08

10 Feb '08

Heads up on a bnz scam i just got through. Link goes to http://tohkoh.notlong.com/ which redirects to http://72.21.54.146/~dallas/www.bnz.co.nz/Internet_Banking/index.html -- Kind Regards Tim Price Technical Manager thepacific.net Ltd tim(a)tpnet.co.nz +64 3 5439095

2 1

Tech help needed in Christchurch
by Andy Linton 10 Feb '08

10 Feb '08

Wildly off topic but there is a beer reward! My son has recently moved to study in Christchurch and taken his PC which runs Ubuntu with him. He's having problems getting it to boot and needs help from someone with clue. Replies off list to me please. Thanks andy

1 0

Policy proposals at APNIC 25
by Elly Tawhai 07 Feb '08

07 Feb '08

Hi NZNOG members At APNIC's 25 Open Policy Meeting in two weeks, the community will be discussing a number of proposals related to the depletion of remaining unallocated IPv4 address pool. If your network will need more IPv4 addresses in the next few years, these proposals will affect you. In the lead up to APNIC 25, the community is currently discussing the proposals on the APNIC Policy SIG mailing list. It's great to see that some NZNOG members are already contributing to the debate. Policy is driven by input from the community. So I encourage you to read the discussions to date and add your thoughts to the Policy SIG mailing list. We need to know what you want so APNIC policies best meet your needs. Policy proposals under discussion --------------------------------- prop-050: IPv4 address transfers prop-052: Cooperative distribution of the end of the IPv4 free pool prop-053: Changing minimum IPv4 allocation size to /24 prop-054: NIR operational policy document revision prop-055: Global policy for the allocation of the remaining IPv4 address space prop-056: IPv4 soft landing prop-057: Proposal to change IPv6 initial allocation criteria prop-058: Proposal to create IPv4 shared use address space among LIRs You can read more about the proposals at: http://www.apnic.net/policy/proposals How to join the discussion -------------------------- You can view the Policy SIG mailing list archive at: http://mailman.apnic.net/mailing-lists/sig-policy The bulk of discussion about proposals to be presented at APNIC 25 has occurred in January and February this year. To join the mailing list, go to: http://www.apnic.net/community/lists Kind regards, Elly ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Feb '08

07 Feb '08

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:AS64622 descr: Route set advertised to AS9439 by Brookers - AS64622 members: 202.27.88.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: mukesh.patel(a)thomson.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050629 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64622 descr: advertised to AS9439 by Thomson Brookers - AS64622 members: 202.27.88.0/23^23-29, 202.27.90.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: Michael.Fletcher(a)thomson.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080208 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] NZNOG Digest, Vol 62, Issue 6
by Hosting Direct Ltd 05 Feb '08

05 Feb '08

DNC, Whois: I got back from there team this message: "There was a temporary blip and order has been restored so you should be able to access the whois server. Stuart Anderson Compliance Officer Domain Name Commission". Regards Ben -----Original Message----- From: nznog-request(a)list.waikato.ac.nz [mailto:nznog-request(a)list.waikato.ac.nz] Sent: Wednesday, 6 February 2008 12:00 p.m. To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 62, Issue 6 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. NZRR Route Registry Update (NZRR Database Notifications) 2. dns access denied, from at least 5 hosts (Chris Hodgetts) 3. Re: dns / whois (for .nz) access denied, from at least 5 hosts (Chris Hodgetts) 4. Re: dns access denied, from at least 5 hosts (Mike Bordignon) 5. Re: dns access denied, from at least 5 hosts (Mark Foster) 6. Re: dns access denied, from at least 5 hosts (Chris Hodgetts) 7. Re: dns access denied, from at least 5 hosts (Barry Murphy) 8. Re: dns access denied, from at least 5 hosts (Craig Whitmore) 9. Re: dns access denied, from at least 5 hosts (Joe) 10. Re: dns access denied, from at least 5 hosts (Blair Harrison) 11. Re: dns access denied, from at least 5 hosts (Blair Harrison) 12. Re: dns access denied, from at least 5 hosts (Chris Hodgetts) 13. Sysadmin Miniconf slides online (Ewen McNeill) ---------------------------------------------------------------------- Message: 1 Date: Tue, 05 Feb 2008 14:27:49 +1300 From: NZRR Database Notifications <rpsl-admin(a)nzix.net> Subject: [nznog] NZRR Route Registry Update To: nznog(a)list.waikato.ac.nz Message-ID: <E1JMCbF-0000JG-B9(a)totti.citylink.co.nz> 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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxium Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080205 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 2 Date: Tue, 05 Feb 2008 15:14:56 +1300 From: Chris Hodgetts <chris(a)archnetnz.com> Subject: [nznog] dns access denied, from at least 5 hosts To: nznog(a)list.waikato.ac.nz Message-ID: <1202177696.29924.34.camel(a)julia.intra.jungledrum.co.nz.> Content-Type: text/plain Hello, Just doing a whois on a few domain names, and I am getting access denied. I have tried on 5 different hosts, on 5 different networks, and all getting the same response. I have even gone to the dnc.org.nz page and nothing of note there. It's been like this for what seems like 10 - 15 minutes, but might be longer. Any clues? ------------------------------ Message: 3 Date: Tue, 05 Feb 2008 15:16:24 +1300 From: Chris Hodgetts <chris(a)archnetnz.com> Subject: Re: [nznog] dns / whois (for .nz) access denied, from at least 5 hosts To: nznog(a)list.waikato.ac.nz Message-ID: <1202177784.29924.36.camel(a)julia.intra.jungledrum.co.nz.> Content-Type: text/plain On Tue, 2008-02-05 at 15:14 +1300, Chris Hodgetts wrote: > Hello, > > Just doing a whois on a few domain names, and I am getting access > denied. > > I have tried on 5 different hosts, on 5 different networks, and all > getting the same response. > > I have even gone to the dnc.org.nz page and nothing of note there. > > It's been like this for what seems like 10 - 15 minutes, but might be > longer. > > Any clues? > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog ------------------------------ Message: 4 Date: Tue, 05 Feb 2008 15:18:49 +1300 From: Mike Bordignon <mike(a)gmi.co.nz> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: Chris Hodgetts <chris(a)archnetnz.com> Cc: nznog(a)list.waikato.ac.nz Message-ID: <47A7C789.2050809(a)gmi.co.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed on 5/02/2008 3:14 p.m. Chris Hodgetts wrote: > Hello, > > Just doing a whois on a few domain names, and I am getting access > denied. > > I have tried on 5 different hosts, on 5 different networks, and all > getting the same response. > > I have even gone to the dnc.org.nz page and nothing of note there. > > It's been like this for what seems like 10 - 15 minutes, but might be > longer. > > Any clues? I get the same thing.. I seem to get a 440 Request Denied each and every time I try to whois a domain name. ------------------------------ Message: 5 Date: Tue, 5 Feb 2008 15:24:37 +1300 (NZDT) From: Mark Foster <blakjak(a)blakjak.net> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: Mike Bordignon <mike(a)gmi.co.nz> Cc: nznog(a)list.waikato.ac.nz Message-ID: <Pine.LNX.4.62.0802051523340.11258(a)maverick.blakjak.net> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed I assume we're talking about .nz based on the reference to the DNC... I just queried one fine both from cli and from the DNC's website. Mark. On Tue, 5 Feb 2008, Mike Bordignon wrote: > > on 5/02/2008 3:14 p.m. Chris Hodgetts wrote: >> Hello, >> >> Just doing a whois on a few domain names, and I am getting access >> denied. >> >> I have tried on 5 different hosts, on 5 different networks, and all >> getting the same response. >> >> I have even gone to the dnc.org.nz page and nothing of note there. >> >> It's been like this for what seems like 10 - 15 minutes, but might be >> longer. >> >> Any clues? > > I get the same thing.. I seem to get a 440 Request Denied each and every > time I try to whois a domain name. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > ------------------------------ Message: 6 Date: Tue, 05 Feb 2008 15:28:02 +1300 From: Chris Hodgetts <chris(a)archnetnz.com> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: Mark Foster <blakjak(a)blakjak.net> Cc: nznog(a)list.waikato.ac.nz Message-ID: <1202178482.29924.38.camel(a)julia.intra.jungledrum.co.nz.> Content-Type: text/plain Someone with quick fingers (and I think you know who you are) must have done something.. because it is now working.. Took a long time to work though! Must have been about 15 minutes.. On Tue, 2008-02-05 at 15:24 +1300, Mark Foster wrote: > I assume we're talking about .nz based on the reference to the DNC... > > I just queried one fine both from cli and from the DNC's website. > > Mark. > > > > On Tue, 5 Feb 2008, Mike Bordignon wrote: > > > > > on 5/02/2008 3:14 p.m. Chris Hodgetts wrote: > >> Hello, > >> > >> Just doing a whois on a few domain names, and I am getting access > >> denied. > >> > >> I have tried on 5 different hosts, on 5 different networks, and all > >> getting the same response. > >> > >> I have even gone to the dnc.org.nz page and nothing of note there. > >> > >> It's been like this for what seems like 10 - 15 minutes, but might be > >> longer. > >> > >> Any clues? > > > > I get the same thing.. I seem to get a 440 Request Denied each and every > > time I try to whois a domain name. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > ------------------------------ Message: 7 Date: Tue, 5 Feb 2008 16:20:19 +1300 (NZDT) From: "Barry Murphy" <barry(a)unix.co.nz> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: "Chris Hodgetts" <chris(a)archnetnz.com> Cc: nznog(a)list.waikato.ac.nz Message-ID: <1829.58.28.159.65.1202181619.squirrel(a)www.secure.unix.co.nz> Content-Type: text/plain;charset=iso-8859-1 Yeah, I had this same problem a few months back where someone from .nz finally responded to this list saying "there is no problem" where many people were getting the same issue as me... Once again the outage was only 20mins or so, see http://list.waikato.ac.nz/pipermail/nznog/2007-November/013617.html Thanks Barry > Someone with quick fingers (and I think you know who you are) must have > done something.. because it is now working.. > > Took a long time to work though! > Must have been about 15 minutes.. > > > On Tue, 2008-02-05 at 15:24 +1300, Mark Foster wrote: >> I assume we're talking about .nz based on the reference to the DNC... >> >> I just queried one fine both from cli and from the DNC's website. >> >> Mark. >> >> >> >> On Tue, 5 Feb 2008, Mike Bordignon wrote: >> >> > >> > on 5/02/2008 3:14 p.m. Chris Hodgetts wrote: >> >> Hello, >> >> >> >> Just doing a whois on a few domain names, and I am getting access >> >> denied. >> >> >> >> I have tried on 5 different hosts, on 5 different networks, and all >> >> getting the same response. >> >> >> >> I have even gone to the dnc.org.nz page and nothing of note there. >> >> >> >> It's been like this for what seems like 10 - 15 minutes, but might be >> >> longer. >> >> >> >> Any clues? >> > >> > I get the same thing.. I seem to get a 440 Request Denied each and >> every >> > time I try to whois a domain name. >> > >> > _______________________________________________ >> > NZNOG mailing list >> > NZNOG(a)list.waikato.ac.nz >> > http://list.waikato.ac.nz/mailman/listinfo/nznog >> > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > ------------------------------ Message: 8 Date: Tue, 5 Feb 2008 16:38:50 +1300 From: "Craig Whitmore" <lennon(a)orcon.net.nz> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: <barry(a)unix.co.nz>, "Chris Hodgetts" <chris(a)archnetnz.com> Cc: nznog(a)list.waikato.ac.nz Message-ID: <E9A679E4C7074C1D80604FE2405AFF54(a)CraigPC> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original > http://list.waikato.ac.nz/pipermail/nznog/2007-November/013617.html > > Thanks > Barry > I had the same problem last time from various machines and networks and I tested this time as well from various places and the problem was defiantely there. Thanks Craig ------------------------------ Message: 9 Date: Tue, 05 Feb 2008 16:26:12 +1300 From: Joe <h4xz0r(a)loose.net.nz> Subject: Re: [nznog] dns access denied, from at least 5 hosts To: barry(a)unix.co.nz Cc: nznog(a)list.waikato.ac.nz Message-ID: <47A7D754.7040207(a)loose.net.nz> Content-Type: text/plain; charset="iso-8859-1" By the time I'd got around to testing this it had come right. Any official explanation? Joe. Barry Murphy wrote: > Yeah, I had this same problem a few months back where someone from .nz > finally responded to this list saying "there is no problem" where many > people were getting the same issue as me... Once again the outage was only > 20mins or so, see > http://list.waikato.ac.nz/pipermail/nznog/2007-November/013617.html > > Thanks > Barry > > > >> Someone with quick fingers (and I think you know who you are) must have >> done something.. because it is now working.. >> >> Took a long time to work though! >> Must have been about 15 minutes.. >> >> >> On Tue, 2008-02-05 at 15:24 +1300, Mark Foster wrote: >> >>> I assume we're talking about .nz based on the reference to the DNC... >>> >>> I just queried one fine both from cli and from the DNC's website. >>> >>> Mark. >>> >>> >>> >>> On Tue, 5 Feb 2008, Mike Bordignon wrote: >>> >>> >>>> on 5/02/2008 3:14 p.m. Chris Hodgetts wrote: >>>> >>>>> Hello, >>>>> >>>>> Just doing a whois on a few domain names, and I am getting access >>>>> denied. >>>>> >>>>> I have tried on 5 different hosts, on 5 different networks, and all >>>>> getting the same response. >>>>> >>>>> I have even gone to the dnc.org.nz page and nothing of note there. >>>>> >>>>> It's been like this for what seems like 10 - 15 minutes, but might be >>>>> longer. >>>>> >>>>> Any clues? >>>>> >>>> I get the same thing.. I seem to get a 440 Request Denied each and >>>> >>> every >>> >>>> time I try to whois a domain name. >>>> >>>> _______________________________________________ >>>> NZNOG mailing list >>>> NZNOG(a)list.waikato.ac.nz >>>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>>> >>>> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> >> > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Sysadmin Miniconf slides online
by Ewen McNeill 05 Feb '08

05 Feb '08

For those that are interested, all the slides that are available from the Sysadmin Miniconf on Wednesday 23rd January 2008 are now online: http://nznog.miniconf.org/programme08.html Thanks to the speakers for speaking (and making their slides available for reference), and to Simon Lyall for hosting the miniconf website. Ewen

1 0

dns access denied, from at least 5 hosts
by Chris Hodgetts 04 Feb '08

04 Feb '08

Hello, Just doing a whois on a few domain names, and I am getting access denied. I have tried on 5 different hosts, on 5 different networks, and all getting the same response. I have even gone to the dnc.org.nz page and nothing of note there. It's been like this for what seems like 10 - 15 minutes, but might be longer. Any clues?

7 10

NZRR Route Registry Update
by NZRR Database Notifications 04 Feb '08

04 Feb '08

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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxium Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080205 source: NZRR ------------------------------------------------------------

1 0

New phishing site
by Michael Fincham 03 Feb '08

03 Feb '08

Hi guys, If you're yet to catch this one, http://www.fanebook.com/index.php is phishing for Facebook passwords. -- -Michael Fincham Unleash Technology Solutions www.unleash.co.nz Phone: 0800 750 250

2 2

TelstraClear Cable
by Tony Wicks 03 Feb '08

03 Feb '08

I've just been informed that TelstraClear has quietly stopped wholesale access to its cable network. While it has been a stupid situation over the last few years in that TelstraClear has been selling wholesale access that is slower and more expensive than their retail offering (and complaining about Telecom doing the same on their network), to just stop all together seems bizarre. Another interesting decision from TelstraClear's wholesale department to go right along with their starting the whole de-peering mess I suppose. All at the same time that the TelstraClear technical people have been doing a nice job of improving access and redundancy to the cable network, I'm guessing no one has told the techs....

4 3

Re: [nznog] TelstraClear Cable
by Tony Wicks 03 Feb '08

03 Feb '08

Tony, Just wondering where you heard this as I am sat at home right now on a Wholesale TelstraCable connection that runs straight into our network. If they are dropping wholesale I'll have a busy week next week moving our customers. Hmm.. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited They informed me this when I asked to check for cable availability for a couple of customers. My impression is they are refusing to add new connections for wholesale customers not so much existing ones. But who knows ? You would have thought some sort of official announcement would have been appropriate not just (quote) – “we do not resale cable modems” And further clarification when asked – “We no longer wholesale cable modems” I know there has been very little interest from wholesale ISP’s in wholesaling cable (that can be expected when the wholesale price exceeds the Telco’s retail price and at lower speeds), but it does seem strange. Especially with the work being done to improve the wholesale access and redundancy to the network. This reeks of a its too hard to do the paperwork so we’ll just tell customers we don’t do it anymore if they ask. Its really quite disappointing, I wonder what they would do if Telecom came along and asked for wholesale access.

2 1

CDNs in NZ?
by Simon Lyall 03 Feb '08

03 Feb '08

Just wondering if anyone is aware of any commercial Content Delivery Networks with distributed NZ-based Internet delivery points apart from Akamai and Citylink? By "commercial" I mean ones that people can buy delivery off, not "internal only" ones such as the root servers. By "distributed" I mean a minimum of APE and WIX. Connectivity to the other half of the NZ eyeballs would be good too. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

5 5

colville fibre
by Fred Look 02 Feb '08

02 Feb '08

hello folks does anyone know where exactly telecom is up to with the fiber cable for northern coromandel we were promised "before christmas" and workers came and layed lots of fiberoptic then.......... nothing tried telecom site but no info who might i ask or better still apply some encouragement to Fred Look brees

2 1

Re: [nznog] Orcon traffic going intl to telstraclear for some ranges
by Barry Murphy 30 Jan '08

30 Jan '08

Thanks, Just as I suspected. On calling orcon they said they were un aware of the issue, even though it had been present for 2hrs 30 mins (I always give them time to fix something incase they caused it and to allow others to call in). I logged a case and it's now been an hr with no word back, so I'm not sure what the issue is, will call them now. Thanks for the input people. Cheers B > A trace from my Orcon dsl to www.telstraclear.co.nz goes via asianetcom. I > suspect Orcon may not be listening to telstraclear's domestic prefix > list.. > or their domestic Telstra circuit has gone dead.. > > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Thursday, January 31, 2008 3:14 PM > To: Joe > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Orcon traffic going intl to telstraclear for some > ranges > > Yeh as per my trace, clear was ok, telstraclear.co.nz , paradise.net.nz > and a few others were not. Just like to hear from those that see the same > issue, and I'm guessing it may be an orcon only fault. > > Cheers > B > > >> Test from 202.20.5.34 (DTS Ltd) >> Host >> Loss% Snt Last Avg Best Wrst StDev >> 1. >> 192.168.1.1 >> 0.0% 10 0.3 0.3 0.2 0.3 0.0 >> 2. >> dts-uh-gw-dmz2.dts.net.nz >> 0.0% 10 2.0 2.5 2.0 4.6 0.8 >> 3. >> dts-slx-gw.dts.net.nz >> 0.0% 10 2.5 2.3 1.8 3.1 0.4 >> 4. >> g1-0-1159b.u21.tar.telstraclear.net >> 0.0% 10 4.1 6.1 4.1 18.5 4.4 >> 5. >> ae1-844.ie4.telstraclear.net >> 0.0% 10 3.3 4.2 3.2 9.3 1.9 >> 6. >> ge-1-2-0-843.ie1.telstraclear.net >> 0.0% 10 13.3 25.4 13.3 62.5 18.5 >> 7. >> front1-clix.clear.net.nz >> 0.0% 10 13.8 14.3 13.5 16.4 1.0 >> 8. >> karma.clear.net.nz >> 0.0% 10 14.5 15.0 13.7 16.9 1.2 >> >> Looks fine from here. >> >> Regards, >> >> Joe. >> >> Barry Murphy wrote: >>> Anyone else noticed this since 12 this afternoon, traffic to some >>> telstra >>> ip ranges going international even though they appear in my national >>> routing table supplied by orcon... I've confirmed this from one other >>> host >>> (tr.meta.net.nz) on orcon, anyone else? >>> >>> Telstra DSL customers, their web hosting division and a few others are >>> going international then back into the country, however some clear >>> sites >>> are fine as per below: >>> >>> traceroute to karma.clear.net.nz (203.97.32.100), 64 hops max, 40 byte >>> packets >>> 1 primary (60.234.66.129) 0.635 ms 0.624 ms 0.586 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.523 ms 0.638 ms >>> 0.681 ms >>> 3 60.234.9.8 (60.234.9.8) 0.735 ms 1.384 ms 0.837 ms >>> 4 203.97.2.161 (203.97.2.161) 3.436 ms 3.243 ms 3.865 ms >>> 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 3.546 ms 7.114 >>> ms >>> 3.424 ms >>> 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 6.000 ms 3.777 >>> ms >>> 5.136 ms >>> 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.288 ms 15.050 >>> ms >>> 14.254 ms >>> 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 15.076 ms 42.059 >>> ms >>> 14.670 ms >>> 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.554 ms 11.333 ms >>> 11.358 ms >>> 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.270 ms >>> 12.990 >>> ms 13.572 ms >>> 11 front1-clix.clear.net.nz (203.167.243.212) 13.052 ms 13.249 ms >>> 12.983 ms >>> 12 karma.clear.net.nz (203.97.32.100) 13.143 ms 13.142 ms 13.069 ms >>> >>> >>> traceroute to 121-72-28-16.dsl.telstraclear.net (121.72.28.16), 64 hops >>> max, 40 byte packets >>> 1 primary (60.234.66.129) 0.642 ms 0.590 ms 0.557 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.549 ms 1.177 ms >>> 0.944 ms >>> 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 7.836 ms 6.838 ms >>> 5.536 ms >>> 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 5.077 ms >>> 3.406 ms 1.778 ms >>> 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 1.274 ms >>> 2.696 >>> ms 1.902 ms >>> 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.995 ms 29.158 >>> ms >>> 35.145 ms >>> 7 gi1-3.gw2.syd1.asianetcom.net (202.147.40.190) 31.912 ms 24.378 >>> ms >>> 26.212 ms >>> 8 61.88.133.205 (61.88.133.205) 27.267 ms 28.816 ms 28.926 ms >>> 9 GigabitEthernet1-4.ken12.Sydney.telstra.net (139.130.65.145) >>> 33.790 >>> ms 30.153 ms 26.487 ms >>> 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 30.889 ms >>> 28.365 ms 26.615 ms >>> 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 30.871 >>> ms >>> 28.709 ms 27.337 ms >>> 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 26.592 ms >>> 27.205 ms 28.404 ms >>> 13 unknown.net.reach.com (134.159.126.33) 27.117 ms 27.875 ms >>> 30.866 >>> ms >>> 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.229 ms 52.308 >>> ms >>> 58.073 ms >>> 15 203.167.233.14 (203.167.233.14) 52.988 ms 54.358 ms 53.908 ms >>> 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 29.688 ms 27.061 ms >>> 29.254 ms >>> 17 218.101.61.163 (218.101.61.163) 29.570 ms 29.038 ms 36.667 ms >>> 18 *^C >>> >>> >>> traceroute to www.paradise.net.nz (203.96.152.127), 64 hops max, 40 >>> byte >>> packets >>> 1 primary (60.234.66.129) 0.624 ms 0.638 ms 0.571 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.426 ms 0.446 ms >>> 0.426 ms >>> 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 2.177 ms 1.786 ms >>> 2.296 ms >>> 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 2.946 ms >>> 2.431 ms 1.834 ms >>> 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 0.990 ms >>> 2.633 >>> ms 2.567 ms >>> 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 25.366 ms 25.566 >>> ms >>> 25.068 ms >>> 7 gi1-2.gw2.syd1.asianetcom.net (202.147.40.182) 25.462 ms 24.029 >>> ms >>> 23.939 ms >>> 8 61.88.133.205 (61.88.133.205) 27.373 ms 26.260 ms 28.539 ms >>> 9 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 28.342 >>> ms >>> 31.793 ms 28.448 ms >>> 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 27.120 ms >>> 28.729 ms 34.028 ms >>> 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 34.244 >>> ms >>> 28.564 ms 29.506 ms >>> 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 197.367 ms >>> 204.040 ms 200.955 ms >>> 13 unknown.net.reach.com (134.159.126.33) 26.861 ms 31.010 ms >>> 29.032 >>> ms >>> 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.340 ms 50.991 >>> ms >>> 50.760 ms >>> 15 203.167.233.14 (203.167.233.14) 56.734 ms 51.162 ms 52.239 ms >>> 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 26.802 ms 25.833 ms >>> 27.581 ms >>> 17 218.101.61.162 (218.101.61.162) 27.050 ms 26.124 ms 31.480 ms >>> 18 218.101.61.42 (218.101.61.42) 43.502 ms 44.411 ms 46.399 ms >>> ^C >>> >>> >>> traceroute to www.clear.net.nz (203.97.33.220), 64 hops max, 40 byte >>> packets >>> 1 primary (60.234.66.129) 0.607 ms 0.610 ms 0.575 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.467 ms 0.833 ms >>> 0.523 ms >>> 3 60.234.9.8 (60.234.9.8) 0.537 ms 0.489 ms 0.495 ms >>> 4 203.97.2.161 (203.97.2.161) 19.630 ms 9.418 ms 6.234 ms >>> 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 11.222 ms 6.493 >>> ms >>> 3.908 ms >>> 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 4.781 ms 5.040 >>> ms >>> 3.573 ms >>> 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.362 ms 15.289 >>> ms >>> 13.767 ms >>> 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 14.173 ms 15.508 >>> ms >>> 14.625 ms >>> 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.188 ms 11.102 ms >>> 11.259 ms >>> 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.479 ms >>> 12.812 >>> ms 12.576 ms >>> 11 front1-clix.clear.net.nz (203.167.243.212) 12.714 ms 12.948 ms >>> 13.112 ms >>> ^C >>> >>> Cheers >>> Barry >>> >>> >>> _______________________________________________ >>> NZNOG mailing list >>> NZNOG(a)list.waikato.ac.nz >>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>> >>> >> >> > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Orcon traffic going intl to telstraclear for some ranges
by Barry Murphy 30 Jan '08

30 Jan '08

Anyone else noticed this since 12 this afternoon, traffic to some telstra ip ranges going international even though they appear in my national routing table supplied by orcon... I've confirmed this from one other host (tr.meta.net.nz) on orcon, anyone else? Telstra DSL customers, their web hosting division and a few others are going international then back into the country, however some clear sites are fine as per below: traceroute to karma.clear.net.nz (203.97.32.100), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.635 ms 0.624 ms 0.586 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.523 ms 0.638 ms 0.681 ms 3 60.234.9.8 (60.234.9.8) 0.735 ms 1.384 ms 0.837 ms 4 203.97.2.161 (203.97.2.161) 3.436 ms 3.243 ms 3.865 ms 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 3.546 ms 7.114 ms 3.424 ms 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 6.000 ms 3.777 ms 5.136 ms 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.288 ms 15.050 ms 14.254 ms 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 15.076 ms 42.059 ms 14.670 ms 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.554 ms 11.333 ms 11.358 ms 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.270 ms 12.990 ms 13.572 ms 11 front1-clix.clear.net.nz (203.167.243.212) 13.052 ms 13.249 ms 12.983 ms 12 karma.clear.net.nz (203.97.32.100) 13.143 ms 13.142 ms 13.069 ms traceroute to 121-72-28-16.dsl.telstraclear.net (121.72.28.16), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.642 ms 0.590 ms 0.557 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.549 ms 1.177 ms 0.944 ms 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 7.836 ms 6.838 ms 5.536 ms 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 5.077 ms 3.406 ms 1.778 ms 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 1.274 ms 2.696 ms 1.902 ms 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.995 ms 29.158 ms 35.145 ms 7 gi1-3.gw2.syd1.asianetcom.net (202.147.40.190) 31.912 ms 24.378 ms 26.212 ms 8 61.88.133.205 (61.88.133.205) 27.267 ms 28.816 ms 28.926 ms 9 GigabitEthernet1-4.ken12.Sydney.telstra.net (139.130.65.145) 33.790 ms 30.153 ms 26.487 ms 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 30.889 ms 28.365 ms 26.615 ms 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 30.871 ms 28.709 ms 27.337 ms 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 26.592 ms 27.205 ms 28.404 ms 13 unknown.net.reach.com (134.159.126.33) 27.117 ms 27.875 ms 30.866 ms 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.229 ms 52.308 ms 58.073 ms 15 203.167.233.14 (203.167.233.14) 52.988 ms 54.358 ms 53.908 ms 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 29.688 ms 27.061 ms 29.254 ms 17 218.101.61.163 (218.101.61.163) 29.570 ms 29.038 ms 36.667 ms 18 *^C traceroute to www.paradise.net.nz (203.96.152.127), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.624 ms 0.638 ms 0.571 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.426 ms 0.446 ms 0.426 ms 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 2.177 ms 1.786 ms 2.296 ms 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 2.946 ms 2.431 ms 1.834 ms 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 0.990 ms 2.633 ms 2.567 ms 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 25.366 ms 25.566 ms 25.068 ms 7 gi1-2.gw2.syd1.asianetcom.net (202.147.40.182) 25.462 ms 24.029 ms 23.939 ms 8 61.88.133.205 (61.88.133.205) 27.373 ms 26.260 ms 28.539 ms 9 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 28.342 ms 31.793 ms 28.448 ms 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 27.120 ms 28.729 ms 34.028 ms 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 34.244 ms 28.564 ms 29.506 ms 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 197.367 ms 204.040 ms 200.955 ms 13 unknown.net.reach.com (134.159.126.33) 26.861 ms 31.010 ms 29.032 ms 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.340 ms 50.991 ms 50.760 ms 15 203.167.233.14 (203.167.233.14) 56.734 ms 51.162 ms 52.239 ms 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 26.802 ms 25.833 ms 27.581 ms 17 218.101.61.162 (218.101.61.162) 27.050 ms 26.124 ms 31.480 ms 18 218.101.61.42 (218.101.61.42) 43.502 ms 44.411 ms 46.399 ms ^C traceroute to www.clear.net.nz (203.97.33.220), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.607 ms 0.610 ms 0.575 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.467 ms 0.833 ms 0.523 ms 3 60.234.9.8 (60.234.9.8) 0.537 ms 0.489 ms 0.495 ms 4 203.97.2.161 (203.97.2.161) 19.630 ms 9.418 ms 6.234 ms 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 11.222 ms 6.493 ms 3.908 ms 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 4.781 ms 5.040 ms 3.573 ms 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.362 ms 15.289 ms 13.767 ms 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 14.173 ms 15.508 ms 14.625 ms 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.188 ms 11.102 ms 11.259 ms 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.479 ms 12.812 ms 12.576 ms 11 front1-clix.clear.net.nz (203.167.243.212) 12.714 ms 12.948 ms 13.112 ms ^C Cheers Barry

4 5

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

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: AS9560:RS-ROUTES:AS24025 descr: advertised to AS9560 by Helix - AS24025 members: 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24025 descr: advertised to AS9560 by Helix - AS24025 members: 202.14.217.0/24^24-29, 202.37.179.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080115 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxium Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.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, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

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:AS64546 descr: Route set for Intelligroup - AS64546 members: 210.48.106.48/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: cam(a)intelligroup.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040311 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64546 descr: advertised to AS9439 by Soltius New Zealand Limited - AS64546 members: 210.48.106.48/29, 210.48.106.160/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Paul.Trainor(a)soltius.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR ------------------------------------------------------------

1 0

Sky Tower power issues?
by Sid Jones 29 Jan '08

29 Jan '08

Anyone else got power issues at the Sky Tower..... We're getting an interesting story from an upstream about the status of the electricity. Call this me double-checking. -- cheers, Sid

2 1

Percentage of users that do peer-to-peer
by Nathan Ward 28 Jan '08

28 Jan '08

Hi guys, A short questionnaire for those of you who sell Internet services, if I may: 1) How many users (as a percentage) on your network use peer to peer? 2) Can you break that down in to: - Users that use p2p 1-3 days per month on average - Users that use p2p 1-6 days per week on average - Users that use p2p 6-7 days per week on average 3) What percentage of your network traffic is peer to peer? (by bitrate /and/ by packetrate, if possible) 4) What percentage of your users are users that do more than say, 80% of their traffic as peer to peer 5) Do you have a histogram available of % of users for various different amounts of data per month? If you reply, please do it offlist, I won't tell anyone your secrets, etc. I'm only after percentages. I don't work for any competing ISPs right now, so can't use your info competitively, this is for some Internet research work I'm doing - believe it or not in the IPv6 area. Findings will be publicly available and based on an aggregate of all ISPs who give me data, and I'll likely talk about my findings at the next NZNOG meeting. For the good of the Internet community and all that. If you have some kind of p2p shaping boxes, they tend to have these sorts of stats available. If you can only provide one or two of these stats, that's still really useful. Cheers! -- Nathan Ward

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Jan '08

28 Jan '08

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: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080129 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Jan '08

28 Jan '08

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: 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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 20080129 source: NZRR ------------------------------------------------------------

1 0

pdf presentations from conference
by Mark Smith 28 Jan '08

28 Jan '08

are the presentations from the conference up on the web page yet? -- Mark Smith E mark.smith(a)endace.com P +64 7 957 0540 W http://www.endace.com Endace Technologies, Limited 85 Alexandra Street Hamilton Endace delivers absolute performance for monitoring and intervention over the widest range of network types and software applications.

5 6

Mac bits left behind at NZNOG08
by Jonny Martin 28 Jan '08

28 Jan '08

A Mac mini-DIV to DVI and 3-pin to cloverleaf mains lead where behind at NZNOG last week. Let me know if they belong to you, and I'll send them off. Cheers, Jonny.

2 1

Updated .nz Domain Growth Statistics
by Blair Harrison 25 Jan '08

25 Jan '08

Hello List, I've updated my graphs once again and they are available to view at http://jedi.school.nz/nzdg.html Please let me know if you have any comments or ideas for other ways to display this information. Cheers, Blair

1 0

Perry's NZNOG'08 IP-over-something challenge!
by Nathan Ward 23 Jan '08

23 Jan '08

I hereby issue the challenge to get IP running over the dishes photographed at: http://unobtainium.braintrust.co.nz/~nward/dishes/ Normally, you'd stand at one and talk, and someone standing at the other would hear you.. you've all played with these before. Perry's challenge is to make two laptops talk to each other, using sound. Note: These photos were taken in winter, which is why those girls have lots of warm stuff on. I have a tshirt on today, but it's raining a little. -- Nathan Ward

15 20

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by yuri 23 Jan '08

23 Jan '08

On 24/01/2008, Bruce Kingsbury wrote: > > > Does one person standing at one dish speaking IP and the person at the > > other end reconstituting packets count as a solution? > > What, an IPoV solution? Hmmm.. You mean like this http://xkcd.com/257/ ? Yuri

1 0

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by Stu Fleming 23 Jan '08

23 Jan '08

> > From: Matthew Poole <matt(a)p00le.net> > Subject: Re: [nznog] Perry's NZNOG'08 IP-over-something challenge! > > > For those who don't understand the terminology, Ed's talking about pouring > roughly 15L/sec of cold, high-pressure water on said drunk students. Who, > presumably, won't stay drunk for long :P You obviously haven't been to Dunedin lately... Does one person standing at one dish speaking IP and the person at the other end reconstituting packets count as a solution?

2 1

NZNOG 2008 live stream
by Jonny Martin 22 Jan '08

22 Jan '08

Hi All. The live stream is available at http://www.r2.co.nz/20080124/ Recordings of all the sessions will also be available online after the conference, thanks to Richard Naylor and co. at R2. Cheers, Jonny.

1 0

Could someone from Compass, Orcon, DTS, Xtreme, Actrix, etc. please contact me off-list?
by Jonathan Brewer 22 Jan '08

22 Jan '08

Preferably in Dunedin. There's this conference going on, with at least 130 network admins present, and there are a couple of companies conspicuously absent. Regards...

1 1