- NZNOG - lists.nznog.org

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

05 Mar '09

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:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR ------------------------------------------------------------

1 0

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

05 Mar '09

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR ------------------------------------------------------------

1 0

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

03 Mar '09

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:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications Ltd. - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090304 source: NZRR ------------------------------------------------------------

1 0

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

03 Mar '09

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:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications Ltd. - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090304 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] APNIC EC Results
by James Spenceley 01 Mar '09

01 Mar '09

Noggers, As Macca and Bambi pointed out, I was elected to the APNIC EC last week (even without emailing every member :-) Thanks to everyone who took the time to fill out proxies and stood in front of fax machines, those who voted online and everyone who generally encouraged others to vote, it was awesome to get so much support ! I owe you all lots and lots of beer. Thanks ! -- James

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 Mar '09

01 Mar '09

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. Work is now under way aimed at establishment of a Trust to ensure that NZNOG can continue to meet. The aim of this work is to provide the legal framework needed to allow a bank account to be operated while avoiding the administrative overhead which would be involved in setting up an Incorporated Society. NZNOG 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 See http://2009.nznog.org/ for details of this year's conference. The plan is that next year's conference will be further south than Auckland. Discussions are now being held with prospective hosts, so if you have a burning desire to host New Zealand's only technical networking conference, now would be the time to speak up. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland 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 around 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

APNIC EC Results
by McDonald Richards 26 Feb '09

26 Feb '09

Sorry for the cross-post but since a bunch of NZ proxies helped this happen I figured I'd share the news here as well. For all those not watching the live feed, James Spenceley was just elected on to the APNIC EC. I'm sure there will be a more formal announcement later from APNIC but figured you'd all want to know how your proxies went. Macca

3 2

APNIC 27 - Meeting update
by Srinivas (Sunny) Chendi 26 Feb '09

26 Feb '09

________________________________________________________________________ APNIC 27 23-27 February 2009, Manila, Philippines ________________________________________________________________________ Thank you to everyone who contributed to APNIC 27, held in conjunction with APRICOT 2009. The preliminary event participation statistics are: Total number of delegates (including APRICOT): 473 Delegates at APNIC Member Meeting: 114 Economies represented: 40 APNIC member organizations represented: 113 APNIC held remote participation events via video conference in Suva, Fiji and Colombo, Sri Lanka. Attendance figures for these events were: Suva, Fiji 10 Colombo, Sri Lanka 22 Web-based online participation options included a choice of video, audio and text chat. Participation figures for online remote delegates were: Online remote participation feeds 2518 To read, watch or listen to archives from the meeting, go to: http://meetings.apnic.net Elections --------- During the APNIC Member Meeting (AMM) in Manila on Friday, 27 February 2009, the following candidates were elected to the APNIC Executive Council (EC). - Jian Zhang - James Spencley - Kuo-Wei Wu - Hyun Joon Kwon Congratulations to the successful candidates: Election details are available at: http://meetings.apnic.net/elections Meeting decisions ----------------- Policy SIG Seven policy proposals were discussed. The following proposals reached consensus and were subsequently ratified at the APNIC Member Meeting. These proposals are now subject to a 'last call' for comments: prop-050 IPv4 address transfers (with modifications) prop-069 Global policy proposal for the allocation of IPv4 blocks to Regional Internet Registries The following proposals did not reach consensus and have been abandoned: prop-063 Reducing timeframe of IPv4 allocations from twelve to six months prop-060 Change in the criteria for the recognition of NIRs in the APNIC region prop-070 Maximum IPv4 allocation size The following proposals were withdrawn by the author(s): prop-068 Inter-RIR transfer policy prop-067 A simple transfer proposal You can check the status of all policy proposals on the following page: http://www.apnic.net/policy/proposals MoUs Signed ----------- APNIC signed Memorandums of Understanding with the following organizations: NSP (Networkers' Society of Pakistan) ASTI (Advanced Science and Technology Institute PHNOG (Philippine Network Operators Group) Meeting sponsors ---------------- APNIC offers its deepest thanks to the sponsors of APNIC 27, whose invaluable contributions allowed APNIC to offer a meeting program of a very high standard: http://meetings.apnic.net/sponsors Upcoming APNIC meetings ----------------------- APNIC 28 24-28 August 2009 Beijing, China http://www.apnic.net/meetings/28 APNIC 29 1-5 March 2010 Kuala Lumpur, Malaysia http://www.apnic.net/meetings/29 Regards -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99 ____________________________________________________________________

1 0

Interesting - How a Router's Missed Range Check Nearly Crashed the Internet
by Skeeve Stevens 26 Feb '09

26 Feb '09

>From the front page of Slashdot: Barlaam writes "A bug by router vendor A (omitting a range check from a critical field in the configuration interface) tickled a bug from router vendor B (dropping BGP sessions when processing some ASPATH attributes with length very close to 256), causing a ripple effect that caused widespread global routing instability last week. The flaw lay dormant until one of vendor A's systems was deployed in an autonomous system whose ASN, modulo 256, was greater than 250. At that point, the Internet was one typo away from disaster. Other router vendors, who were not affected by the bug, happily propagated the trigger message to every vulnerable system on the planet in about 30 seconds. Few people appreciate how fragile and unsecured the Internet's trust-based critical infrastructure really is - this is just the latest example." Vendor A, in this case, is a Latvian router vendor called MikroTik. Is this just the 4byte ASN thing from months ago or something new? I knew there was a reason I hated Mikrotik's so much. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

3 2

NZRR Route Registry Update
by NZRR Database Notifications 23 Feb '09

23 Feb '09

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:AS10022 descr: advertised to AS9439 by Datacom Systems Wellington Limited - AS10022 members: 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.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: matthewda(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080111 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS10022 descr: advertised to AS9439 by Datacom Systems (Wellington) Limited - AS10022 members: 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.198.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: matthewda(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090224 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes!
by Skeeve Stevens 22 Feb '09

22 Feb '09

I should have mentioned... if you have already assigned your votes for James - and this includes the proxy votes you filled out as AUSNOG2 or have arranged privately. My email is mainly to remind anyone who hasn't done anything with their votes yet and might consider it at the last minute. The reason I have also asked them for myself is that a) I am here onsite, so I can use them, b) most of the other guys are very busy doing their political things and I am happy to spend the time filling out forms to help James and David get elected. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced. From: Sean K. Finn [mailto:Sean.Finn(a)ozservers.com.au] Sent: Monday, 23 February 2009 3:04 PM To: Skeeve Stevens; 'ausnog(a)lists.ausnog.net'; 'NZNOG(a)list.waikato.ac.nz' Subject: RE: [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes! For the benefit of all, Would this be the same as the proxy votes assigned after AusNog02 last year, or if we wanted to re-allocate rights for this election would we need to submit another proxy form? I.e. Were the proxy rights assigned during AusNOG02 for this election? Cheers, Sean. From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Monday, 23 February 2009 1:51 PM To: ausnog(a)lists.ausnog.net; NZNOG(a)list.waikato.ac.nz Subject: [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes! Hey Everyone, I am here in Manila at the APRICOT 2009/APNIC 27 conference and it looks like this week is going to be a lot of fun with great people to meet as well as some very interesting things happening. The key issue I am sending this email to the AU/NZNOG and Aussie-ISP lists is to appeal to anyone who has not yet decided to, or just plain forgot to do anything about the voting power they may have as an APNIC member. We have a chance of getting two Australians onto the APNIC EC. The current membership is listed at http://www.apnic.net/ec/ and as you can see, it would be massively beneficial if we had some Australian representation. Our two nominations are James Spenceley<http://meetings.apnic.net/elections/james-spenceley.html> from Vocus Communications (www.vocus.com.au<http://www.vocus.com.au>) and David Woodgate<http://meetings.apnic.net/elections/david-woodgate.html> from Telstra. Both of these guys have both been involved in internet policy making for a VERY long time and are both worthy for the positions available on the EC. They are very respected in the Internet Community, both in Australia and NZ and the world over, both having presented policies an given talks at many conferences. If you don't know them and want some more information, please refer to their Nomination profiles by clicking on their names above. There are 10 nominations and 4 positions available with 1 re-standing with most of the nominees are people from countries with massive populations and large voting power such as China, India and so on. If we have any chance to get Australia/NZ to have some involvement in influencing the direction of internet governance and policy going forward, it is time we stood up and did something with out votes instead of wasting them. To me, it doesn't matter if you like or dislike either James or David, have a past or future with these guys, but if you want to support the Internet community in Australia and New Zealand as a whole, I think that these guys are will represent the issues of Australia/New Zealand very well and certainly worth the 5 minutes to fill out the proxy form and help get them elected. Details about the current election are here: http://meetings.apnic.net/elections/index.html The list of current nominations are as listed at: http://www.apnic.net/news/2009/0216a.html If you wish to contribute your votes there are two ways. You can assign proxy, or you can vote online using MyAPNIC, but many have not registered for this, and it is too late now if you already have not. I am happy to be the person for you to allocate your votes to, which you can do once off for this election by using the Proxy Form included. Please note: A proxy appointment is valid only for a single election, so I can only vote for you in this one case. You are not assigning me permanent voting rights for your organisation. If you didn't receive the attached Proxy form you can download a pre-filled one with my details from http://www.eintellego.net/apnic/APNIC27VoteProxySkeeve.pdf, or failing that, use my details below - don't forget to inform me if you are sending me your proxy as I need to know what members I am collecting the forms for. For details: http://meetings.apnic.net/elections/about/proxy.html are the official details on assigning your proxy votes. If you don't know your membership level as it is right now, Aussies please check http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=au&sort=ascending or for the Kiwi's http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=nz&sort=ascending which will show you what APNIC considers your membership level to currently be. Note: You may have more resources than your current level, but your annual membership might not have come up yet. All your votes are useful, even if you are an associate with only 1 vote as they all add up and elections can come down to just a couple of votes. The number of votes you have are as follows: Associate 1 Very small 2 Small 4 Medium 8 Large 16 Very large 32 Extra large 64 My voting will be for James and David, but with the excess votes, I will be following their advice on who else should be supported. If you know anyone on that membership list who isn't using those votes, please contact them... the larger the members the better as it is less work, but every single vote counts. Forward this email to them and they might have the 5 minutes to fill it out. Just remember, it has to be completed by the Corporate Contact. Also, this has to be done today or tomorrow... please spare the 5 minutes to help us have a say in our own future as ISP's and internet community members. If you have any questions, please send them and I will get back to you asap ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

S92a implementation delayed, clause may be suspended.
by Juha Saarinen 22 Feb '09

22 Feb '09

http://bit.ly/3RiQL Bit.ly URL goes to Computerworld NZ. -- Juha Saarinen juha(a)saarinen.org

1 1

(Urgent) APNIC Executive Council (EC) Election this Week - We need your votes!
by Skeeve Stevens 22 Feb '09

22 Feb '09

Hey Everyone, I am here in Manila at the APRICOT 2009/APNIC 27 conference and it looks like this week is going to be a lot of fun with great people to meet as well as some very interesting things happening. The key issue I am sending this email to the AU/NZNOG and Aussie-ISP lists is to appeal to anyone who has not yet decided to, or just plain forgot to do anything about the voting power they may have as an APNIC member. We have a chance of getting two Australians onto the APNIC EC. The current membership is listed at http://www.apnic.net/ec/ and as you can see, it would be massively beneficial if we had some Australian representation. Our two nominations are James Spenceley<http://meetings.apnic.net/elections/james-spenceley.html> from Vocus Communications (www.vocus.com.au<http://www.vocus.com.au>) and David Woodgate<http://meetings.apnic.net/elections/david-woodgate.html> from Telstra. Both of these guys have both been involved in internet policy making for a VERY long time and are both worthy for the positions available on the EC. They are very respected in the Internet Community, both in Australia and NZ and the world over, both having presented policies an given talks at many conferences. If you don't know them and want some more information, please refer to their Nomination profiles by clicking on their names above. There are 10 nominations and 4 positions available with 1 re-standing with most of the nominees are people from countries with massive populations and large voting power such as China, India and so on. If we have any chance to get Australia/NZ to have some involvement in influencing the direction of internet governance and policy going forward, it is time we stood up and did something with out votes instead of wasting them. To me, it doesn't matter if you like or dislike either James or David, have a past or future with these guys, but if you want to support the Internet community in Australia and New Zealand as a whole, I think that these guys are will represent the issues of Australia/New Zealand very well and certainly worth the 5 minutes to fill out the proxy form and help get them elected. Details about the current election are here: http://meetings.apnic.net/elections/index.html The list of current nominations are as listed at: http://www.apnic.net/news/2009/0216a.html If you wish to contribute your votes there are two ways. You can assign proxy, or you can vote online using MyAPNIC, but many have not registered for this, and it is too late now if you already have not. I am happy to be the person for you to allocate your votes to, which you can do once off for this election by using the Proxy Form included. Please note: A proxy appointment is valid only for a single election, so I can only vote for you in this one case. You are not assigning me permanent voting rights for your organisation. If you didn't receive the attached Proxy form you can download a pre-filled one with my details from http://www.eintellego.net/apnic/APNIC27VoteProxySkeeve.pdf, or failing that, use my details below - don't forget to inform me if you are sending me your proxy as I need to know what members I am collecting the forms for. For details: http://meetings.apnic.net/elections/about/proxy.html are the official details on assigning your proxy votes. If you don't know your membership level as it is right now, Aussies please check http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=au&sort=ascending or for the Kiwi's http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=nz&sort=ascending which will show you what APNIC considers your membership level to currently be. Note: You may have more resources than your current level, but your annual membership might not have come up yet. All your votes are useful, even if you are an associate with only 1 vote as they all add up and elections can come down to just a couple of votes. The number of votes you have are as follows: Associate 1 Very small 2 Small 4 Medium 8 Large 16 Very large 32 Extra large 64 My voting will be for James and David, but with the excess votes, I will be following their advice on who else should be supported. If you know anyone on that membership list who isn't using those votes, please contact them... the larger the members the better as it is less work, but every single vote counts. Forward this email to them and they might have the 5 minutes to fill it out. Just remember, it has to be completed by the Corporate Contact. Also, this has to be done today or tomorrow... please spare the 5 minutes to help us have a say in our own future as ISP's and internet community members. If you have any questions, please send them and I will get back to you asap ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

UPDATE: CCIP Alert: Adobe Acrobat unpatched vulnerability
by Paul McKitrick 21 Feb '09

21 Feb '09

UPDATE: Apologies for the previous email that contained the wrong content. Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the critical vulnerability in Adobe Reader and Adobe Acrobat that could potentially allow an attacker to take control of the affected system which was released on February 19: http://www.adobe.com/support/security/advisories/apsa09-01.html CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Adobe have stated that they are expecting to release an update by 11 March 2009 for Adobe 9 and updates for other versions (8 and 7) to follow soon after. Adobe has reported that the following versions are affected: * Adobe Reader 9 and earlier versions * Adobe Acrobat Standard, Pro, and Pro Extended 9 and earlier versions Shadowserver have a write up on their website: http://www.shadowserver.org/wiki/pmwiki.php?n=Calendar.20090219 The US-CERT write up (https://www.kb.cert.org/vuls/id/905281) includes the following mitigation advice: Disable JavaScript in Adobe Reader and Acrobat Disabling Javascript may prevent this vulnerability from being exploited. Acrobat JavaScript can be disabled in the General preferences dialog (Edit -> Preferences -> JavaScript and un-check Enable Acrobat JavaScript). Some vendors ship javascript support in a seperate package. Removing this package may remove javascript support in the Adobe PDF reader. Prevent Internet Explorer from automatically opening PDF documents The installer for Adobe Reader and Acrobat configures Internet Explorer to automatically open PDF files without any user interaction. This behavior can be reverted to the safer option of prompting the user by importing the following as a .REG file: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\AcroExch.Document.7] "EditFlags"=hex:00,00,00,00 Disable the displaying of PDF documents in the web browser Preventing PDF documents from opening inside a web browser may mitigate this vulnerability. If this workaround is applied to updated versions of the Adobe reader, it may mitigate future vulnerabilities. To prevent PDF documents from automatically being opened in a web browser: 1. Open Adobe Acrobat Reader. 2. Open the Edit menu. 3. Choose the preferences option. 4. Choose the Internet section. 5. Un-check the "Display PDF in browser" check box. Do not access PDF documents from untrusted sources Do not open unfamiliar or unexpected PDF documents, particularly those hosted on web sites or delivered as email attachments Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

CCIP Alert: Adobe Acrobat unpatched vulnerability
by Paul McKitrick 21 Feb '09

21 Feb '09

Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the the Critical Microsoft Security Bulletin MS09-002 that was released on February 10: http://www.microsoft.com/technet/security/bulletin/ms09-002.mspx Microsoft have announced a vulnerability in Internet Explorer 7 that could allow remote code execution if a user views a specially crafted Web page. Administrators are advised to patch immediately. Microsoft have rated as Critical for Window XP and Windows Vista and as Moderate for Windows Server 2003 and Windows Server 2008. CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Due to the recent impact of the Conficker worm CCIP wants to ensure that there is awareness of the active exploitation of MS09-002 and to encourage the patching of systems if they have not already been patched. AusCERT have a write up on their website: http://www.auscert.org.au/render.html?it=10477 There is also a write up on the Sourcefire Vulnerability Research Team’s blog: http://vrt-sourcefire.blogspot.com/2009/02/ms09-002-in-wild.html Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

CCIP ALERT: Exploitation of MS09-002
by Paul McKitrick 21 Feb '09

21 Feb '09

Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the the Critical Microsoft Security Bulletin MS09-002 that was released on February 10: http://www.microsoft.com/technet/security/bulletin/ms09-002.mspx Microsoft have announced a vulnerability in Internet Explorer 7 that could allow remote code execution if a user views a specially crafted Web page. Administrators are advised to patch immediately. Microsoft have rated as Critical for Window XP and Windows Vista and as Moderate for Windows Server 2003 and Windows Server 2008. CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Due to the recent impact of the Conficker worm CCIP wants to ensure that there is awareness of the active exploitation of MS09-002 and to encourage the patching of systems if they have not already been patched. AusCERT have a write up on their website: http://www.auscert.org.au/render.html?it=10477 There is also a write up on the Sourcefire Vulnerability Research Team’s blog: http://vrt-sourcefire.blogspot.com/2009/02/ms09-002-in-wild.html Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZNOG-09 Videos
by Richard Naylor 20 Feb '09

20 Feb '09

Video and audio (MP3) from NZNOG 09 is available at http://www.r2.co.nz/20090129/ There is both streamed and downloadable versions, and versions in wmv, MP4 and MP3. One talk was not recorded at the request of the presenter. The video isn't too bad - the lighting was a challenge, and there was no one driving the audio desk, so the feed we got varied a little. But it should be quite usable for those who couldn't make it. Richard

1 0

Voting process
by Skeeve Stevens 19 Feb '09

19 Feb '09

Just a quick question about the APNIC EC elections. If someone has a lot of votes/proxies, and they don't get up, are they able to pass their votes to someone else? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

8 8

New Telstra transparent proxy/config?
by Joel Wiramu Pauling 18 Feb '09

18 Feb '09

Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27 which appears to be a new upstream proxy hop I have not seen before: traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual) Can anyone confirm similar behaviour who is on Telstra cable network, or have further details. Appears to be a netcache proxy. Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1) Kind regards -JoelW

5 6

S92A - Public demonstration at MIDDAY parliament grounds
by Andrew Ruthven 18 Feb '09

18 Feb '09

[Forwarded, very last minute, sorry for the late warning] Hi folks, So today there is a public demonstration at MIDDAY on Parliament grounds in support of MPs speaking against Section 92A. Details are here: http://creativefreedom.org.nz/story.html?id=127 "In Wellington on the steps of Parliament on Thursday 19th at MIDDAY with a petition handover at 12:30pm. This is a postive event where we will hand out hundreds of CDs and thank the politicans that support us - so please keep it friendly and polite. While we appreciate people arranging their own demonstrations it might be best if we don't dilute our numbers with multiple events. We want everyone reading this to email everyone they know in Wellington about this. We can't let this be another internet protest that results in few people turning up. This is important so we need to prove it in numbers. NOTE: Please don't wear all black as that has negative associations with other demonstrations but instead come along with bright clothes and BLACK PLACARDS!" As an example of how to be awesome do this: http://coffee.geek.nz/public-demonstration.html Now here's the sobering bit... We need everyone you can get to be there. This is a lot about establishing the credibility of the anti-S92A voice in numbers. If you can bring your friends and co-workers that's the kind of thing that will make this work. We need all of your support -- don't think that other will do it -- we need you to be there MIDDAY. Thanks, Matthew Holloway Creative Freedom -- Andrew Ruthven, Wellington, New Zealand At home: andrew(a)etc.gen.nz | linux.conf.au 2010 | Follow the signs. Visit Wellington! | http://www.penguinsvisiting.org.nz

2 1

NZRR Route Registry Update
by NZRR Database Notifications 18 Feb '09

18 Feb '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES6:AS131110 descr: Route set advertised to AS9439 by Slush Technologies - AS131110 mp-members: 2001:4410:2005:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dene(a)slush.ca mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080910 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES6:AS131110 descr: Route set advertised to AS9439 by Dane Foster - AS131110 mp-members: 2001:4410:2005:0:0:0:0:0/48^48-64, 2001:0470:a080:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dane(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090219 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Feb '09

16 Feb '09

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:AS24183 descr: advertised to AS9439 by DTS Ltd - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.27.88.0/23^23-29, 202.174.178.0/23^23-29, 202.174.184.0/23^23-29, 202.174.190.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 203.170.56.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: vaa(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090120 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24183 descr: advertised to AS9439 by DTS Ltd - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.27.88.0/23^23-29, 202.174.178.0/23^23-29, 202.174.184.0/23^23-29, 202.174.190.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 203.170.56.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: vaa(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090217 source: NZRR ------------------------------------------------------------

1 0

FileMaker Pro 10 - now with IPv6
by Skeeve Stevens 15 Feb '09

15 Feb '09

Hey all, Just a bit of data for you network guys and application hosting guys out there... Filemaker Pro 10 which has just been released is saying that it "Complies with Internet Protocol Version 6 standards." http://www.filemaker.com/products/fmp/all_features.html Good to see mainstream applications adopting and promoting it. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

10 14

2009 APNIC EC Election – Voting criteria
by Srinivas (Sunny) Chendi 12 Feb '09

12 Feb '09

_______________________________________________________________________ 2009 APNIC EC Election – Voting criteria _______________________________________________________________________ The APNIC Executive Council (EC) 2009 elections will be held at the APNIC Member Meeting (AMM) on Friday, 27 February 2009. The members whose positions are up for reelection are Kuo-Wei Wu, Kusumba Sridhar, Mao Wei, and Ming-Cheng Liang. Voting criteria --------------- Only APNIC Members or their assigned proxies may vote at the EC elections. Voting may be done online using MyAPNIC, or onsite with a paper ballot at the AMM. By default, all voting rights are controlled by the Member’s Corporate Contact. To cast a vote the Corporate Contact may vote themselves, or may assign voting rights to another registered APNIC contact (using MyAPNIC), or appoint external representatives as a proxy to vote on their behalf. A proxy voter may be any individual and need not be an employee of the Member organization or APNIC Members in their own right. A proxy appointment is only valid when confirmed by the APNIC Secretariat. Proxy voters may only vote onsite and must be registered for the AMM. For more information about appointing a proxy, see http://meetings.apnic.net/elections/about/proxy.html Online voting ------------- Online voting opens on 16 February 2009 and closes on 25 February 2009 (09:00 UTC+8, Manila time). It is only available with valid digital certificate access to the MyAPNIC Member website. An online vote cannot be withdrawn after it has been submitted. Onsite voting ------------- Onsite voting takes place at the AMM on 27 February 2009. Ballots can be collected by the Corporate Contact, a Member representative with voting rights assigned by the Corporate Contact, or a proxy voter. For more on how to vote and the list of current nominees, see http://meetings.apnic.net/elections/about/voting/how.html Regards -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99 ____________________________________________________________________ * Join us for APNIC 27 in Manila, 23-27 February 2009! * A fun week of workshops, seminars, and policy discussion awaits! * * For more information, see: http://meetings.apnic.net ____________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 11 Feb '09

11 Feb '09

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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-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, 203.84.134.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.49.141.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 20081219 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, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 202.55.96.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-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, 203.84.134.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.49.141.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 20090212 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Feb '09

10 Feb '09

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:AS42 descr: Route set advertised to AS9560 by PCH1 - AS42 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS42 descr: advertised to AS9560 by Packet Clearing House - AS42 members: 74.80.64.0/18^18-29, 199.249.112.0/20^20-29, 204.61.216.0/23^23-29, 198.182.167.0/24^24-29, 199.7.64.0/24^24-29, 199.7.77.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)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090211 source: NZRR ------------------------------------------------------------

1 0

Nominations for APNIC Executive Council closes soon
by Srinivas (Sunny) Chendi 05 Feb '09

05 Feb '09

_______________________________________________________________________ Nominations for APNIC Executive Council closes soon _______________________________________________________________________ Nominations for four positions open for election on the APNIC Executive Council (EC) will close on 13 February 2009 (17:30 UTC+10). Nominees do not have to be representatives of members, but only APNIC members may nominate and vote for candidates. The EC positions up for reelection are Kuo Wei Wu, Kusumba Sridhar, Mao Wei, and Ming-Cheng Liang. Nominations must be made using the online nomination form: http://meetings.apnic.net/elections/nominate.html The election will be held at APNIC 27 on Friday, 27 Febrary 2009. For more information on nominations received, proxy registration, current EC members, and the role of the EC, please refer to: http://meetings.apnic.net/elections/about/index.html Nominees should note that positions on the APNIC EC are currently voluntary and that APNIC may not be able to reimburse EC members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at: secretariat(a)apnic.net Regards, -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99 ____________________________________________________________________ * Join us for APNIC 27 in Manila, 23-27 February 2009! * A fun week of workshops, seminars, and policy discussion awaits! * * For more information, see: http://meetings.apnic.net ____________________________________________________________________

1 0

Telstra Fibre Outage?
by Chris Hodgetts 04 Feb '09

04 Feb '09

Anyone else experiencing any issues with Telstra Clear fibre?

11 14

Looking for Cisco1841 Rack Ears.
by Dean Pemberton 03 Feb '09

03 Feb '09

Hi all. Does anyone have a set of rack ears which would fit a Cisco1841. Willing to exchange for cash or beer (see this post is AUP compliment now too). Thanks Dean

1 0

Wellington Power Outage
by Joel Wiramu Pauling 03 Feb '09

03 Feb '09

Just to show some solidarity, there is a power outage currently in parts of Wellington. NEC house (Manners/Taranaki) and the WCC/Library building are affected. The information I have just states it was cut due to a Transformer issue and are stating up to 4 hours before it is restored. -JoelW

2 2

Widespread Auckland Power Outage 2009-02-03
by Jonathan Brewer 03 Feb '09

03 Feb '09

Hi Folks, Starting around 13:06 this afternoon, a number of parts of Auckland lost power. At a glance, I saw some of our monitored subscribers with unprotected (or underprotected) devices go down in: Ellerslie Mt. Richmond Newmarket Otahuhu Parnell Penrose Westfield Regards, Jon

18 24

NZRR Route Registry Update
by NZRR Database Notifications 03 Feb '09

03 Feb '09

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: ------------------------------------------------------------ --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES:AS9733 descr: advertised to AS9560 by Netspace Services - AS9733 members: 210.4.208.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: gerard(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090204 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Widespread Auckland Power Outage 2009-02-03 (fwd)
by Mark Foster 02 Feb '09

02 Feb '09

Mind your reply-to's, Joel :) Forwarded as intended for the list. ---------- Forwarded message ---------- Date: Tue, 3 Feb 2009 16:59:45 +1300 From: Joel Wiramu Pauling <aenertia(a)aenertia.net> To: Mark Foster <blakjak(a)blakjak.net> Subject: Re: [nznog] Widespread Auckland Power Outage 2009-02-03 Out of curiosity how many people on this list have Sustainable UPS collection/top up schemes in place in parts of their networks. I.e Solar/Wind feeders to battery units? I know diesel generators are the norm, but I have also seen solar array powered gear work pretty well (NZ Wireless I believe have Solar fed battery arrays on their Somes Island AP). -JoelW 2009/2/3 Mark Foster <blakjak(a)blakjak.net>: > > > On Tue, 3 Feb 2009, Patrick Jordan-Smith wrote: > >> >> On 3/02/2009, at 3:43 PM, Nicholas Lee wrote: >> >>> You would think that Transpower would learn not do work to critical >>> systems in the middle of a hot day when it would be a peak. >> >> Personally I'd prefer to have the time when there is risk of power >> cuts during the day - at least there is a big light in the sky (most >> days.) Much easier than trying to find the candles when the power cuts >> out at 10pm and it all goes dark. Much easier to deal with traffic >> issues. >> > > Yes, and people are at work to deal with the ramifications, instead of > being on callback/overtime and delayed to respond... > > After all, UPS is just brownout protection, right? > > :-) > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 Feb '09

01 Feb '09

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 See http://2009.nznog.org/ for details of the conference just finished. The plan is that next year's conference will be further south than Auckland. Discussions are now being held with prospective hosts, so if you have a burning desire to host New Zealand's only technical networking conference, now would be the time to speak up. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland 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 around 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

Outage at iPrimus Datacentre - 55 King St, Melbourne
by Skeeve Stevens 31 Jan '09

31 Jan '09

Hey all, Little detail at present... but the iPrimus DC in 55 King St Melbourne seems to have had a complete failure. Power, UPS and Generator have apparently all failed. Anyone else have more detail, feel free to follow up. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

Re: [nznog] NZNOG streams...
by Richard Naylor 27 Jan '09

27 Jan '09

At 11:06 a.m. 28/01/2009, Neil Gardner wrote: >OK, you've all got a lot uglier and the format of the conference is >significantly different this year... > >I don't for example, recall anyone leading conference speakers around >in a ring while they were dressed in horse costumes. > >Additionally, the discussion on BGP for resilient services sounded a >lot more like a horsie auction than I expected. Classic !!! I confess - we recycle URLs. The NZNOG streams will be sorted tonight after we finish setting up and the bandwidth works. The horses are actually live on another 2 streams. NZNOG will have 4 and a test link to Manila has one. and as of 10:30 this morning, the Reserve Bank has another one. So let me apologise in advance if the NZNOG opening ceremony is a little less than expected. At 0900 when RBNZ announce a new cash rate, I'm live switching the feed from the van at NZNOG. I could either get this right or horribly wrong..............

2 1

NZNOG streams...
by Neil Gardner 27 Jan '09

27 Jan '09

OK, you've all got a lot uglier and the format of the conference is significantly different this year... I don't for example, recall anyone leading conference speakers around in a ring while they were dressed in horse costumes. Additionally, the discussion on BGP for resilient services sounded a lot more like a horsie auction than I expected. Are the NZnog streams up anywhere? Yes I followed the links on the NZnog site... http://2009.nznog.org/streaming Cheers - N

8 8

Re: [nznog] NZNOG Digest, Vol 73, Issue 24
by Jeff Sutton - AKBREW 27 Jan '09

27 Jan '09

-----Original Message----- From: nznog-request(a)list.waikato.ac.nz [mailto:nznog-request(a)list.waikato.ac.nz] Sent: Wednesday, 28 January 2009 11:07 a.m. To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 73, Issue 24 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. Re: Juniper J2320, rate limit based on bgp community (national/international) (Truman Boyes) 2. Re: Juniper J2320, rate limit based on bgp community (national/international) (Barry Murphy) 3. Vendor reception at NZNOG - Open to all (Nathan Ward) 4. Re: Vendor reception at NZNOG - Open to all (Neil Gardner) 5. Re: Vendor reception at NZNOG - Open to all (Nathan Ward) 6. NZRR Route Registry Update (NZRR Database Notifications) 7. NZRR Route Registry Update (NZRR Database Notifications) 8. NZNOG IRC Channel (Mark Foster) 9. Re: NZNOG IRC Channel (Scott Howard) 10. NZNOG streams... (Neil Gardner) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Jan 2009 11:56:25 +1100 From: Truman Boyes <truman(a)suspicious.org> Subject: Re: [nznog] Juniper J2320, rate limit based on bgp community (national/international) To: Craig Spiers <Craig.Spiers(a)staff.solarix.co.nz> Cc: Nznog <nznog(a)list.waikato.ac.nz> Message-ID: <85A47E88-60DA-40BA-8DDE-9DF52A11142E(a)suspicious.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hey there, What you want is destination class policing / source class policing based on destination class usage (DCU) This allows you to have policing based on BGP communities instead of managing prefix lists. This is supported on J-series since 8.5R1. Basically you want to: 1. apply bgp communities to routes learned from specific peers (international tag, domestic tag, etc). 2. write a policy that matches on tagged routes, and has an action of 'then destination-class INTERNATIONAL' etc... 3. apply the policy as as export policy to the forwarding-table. 4. configure accounting for destination-class-usage on interfaces that you wish to collect account for ... 5. configure a firewall filter that matches on destination-class and polices traffic to the correct rate. I can unicast you some configs once I dig them up from back in the day. DCU/DCP is a highly scalable way to provide differentiated accounting / policing for specific aggregate services. I have seen this deployed with 40+ regional zones. Cheers, Truman Boyes On 22/01/2009, at 2:21 PM, Craig Spiers wrote: > Hi All.. > > To try and better explain what barry is trying to do.. hes trying to > traffic shape certain IP addresses on his network based on the BGP > community a specific route is a member of.. > > Eg domestic traffic is a member of community 100 and international is > 200 > > Eg 1.2.3.4 on his network communicating with a route dest in community > 100 = 128k > Eg 1.2.3.4 on his network communicating with a route dest in community > 200 = 64k > > I do this on our cisco's using BGP with ip-qos-map's and a service > policy on the interface.. hes looking for the juniper equivalent.. > > Any ideas? > > > Kind Regards, > > Craig Spiers - Network Manager > Solarix Limited > DDI: +64 9 974 4753 | FAX: +64 9 523 8057 FAULTS: 0800 89 41 42 > MOB: +64 21 857 183 | email: craig.spiers(a)staff.solarix.co.nz > The information contained in this email is privileged and confidential > and > intended for the addressee only. If you are not the intended recipient > you > are asked to respect that confidentiality and not disclose, copy or > make > > use of its contents. If received in error you are asked to destroy > this > email and contact the sender immediately. > > > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Thursday, 22 January 2009 3:42 p.m. > To: Nznog > Subject: [nznog] Juniper J2320,rate limit based on bgp community > (national/international) > > Hey Guys, > > Hope this fits in with the AUP, however I'd hope so as not many forums > show > how to rate-limit based on national/international traffic as they > don't > bill accordingly, however in NZ this is standard practice so hoping > someone > with juniper knowledge can assist me here. > > Basically I want to allow all traffic to/from national without > rate-limit, > then restrict international, for eg 128k. > > icepick(a)NCCORE01# show firewall > policer 128k { > if-exceeding { > bandwidth-limit 128k; > burst-size-limit 4500; > } > then discard; > } > filter 128k { > term 1 { > from { > forwarding-class assured-forwarding; > } > then accept; > } > term 2 { > from { > forwarding-class best-effort; > } > then { > policer 128k; > accept; > } > } > } > > > > icepick(a)NCCORE01# show policy-options policy-statement Orcon-Primary- > In > term 1 { > from community [ Orcon-Local Orcon-National Orcon-Peering > Orcon-Telstra > Orcon-Telecom ]; > then { > local-preference 110; > forwarding-class assured-forwarding; > accept; > } > } > term 2 { > from { > route-filter 0.0.0.0/0 upto /24; > } > then { > local-preference 110; > forwarding-class best-effort; > accept; > } > } > term 3 { > from { > route-filter 0.0.0.0/0 exact; > } > then { > local-preference 120; > accept; > } > } > term 4 { > then reject; > } > > > icepick(a)NCCORE01# show interfaces ge-0/0/1 unit 55 > description "Test interface"; > vlan-id 55; > family inet { > filter { > input 128k; > output 128k; > } > address 113.21.x.x/29; > } > > > The problem I'm running into is all traffic is being rate-limited at > 128k, > rather than just the international. I was able to find one example > located > at > http://archives.devshed.com/forums/networking-100/policer-based-on-commu > nity-2015343.html > however this describes the use of destination-class where I only have > forwarding-class so I'm not sure if this has been depreciated or > renamed > or > not supported by J2320. > > I understand this may be a question for JTAC, however I'd like to hear > from > users here in NZ that have managed to get this going with junos. To > keep > the list sane, please reply offlist, if many people are interested > I'll > post the working solution after being tested for archive purposes. > > Public holiday for Aucklanders next monday, extra long weekend of > beer, > mmmmm > > Thanks > 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 > ------------------------------ Message: 2 Date: Tue, 27 Jan 2009 14:02:09 +1300 From: Barry Murphy <barry(a)unix.co.nz> Subject: Re: [nznog] Juniper J2320, rate limit based on bgp community (national/international) To: Truman Boyes <truman(a)suspicious.org> Cc: Craig Spiers <Craig.Spiers(a)staff.solarix.co.nz>, Nznog <nznog(a)list.waikato.ac.nz> Message-ID: <42d6b86dda5ad39384980a4346e7b3ce(a)localhost> Content-Type: text/plain; charset="UTF-8" Hi Truman, Yes this was how I planned to do it, if you note my second to last paragraph, my J2320 doesn't seem to have destination-class available at the policer level. Thanks Barry On Tue, 27 Jan 2009 11:56:25 +1100, Truman Boyes <truman(a)suspicious.org> wrote: > Hey there, > > What you want is destination class policing / source class policing > based on destination class usage (DCU) This allows you to have > policing based on BGP communities instead of managing prefix lists. > This is supported on J-series since 8.5R1. > > Basically you want to: > > 1. apply bgp communities to routes learned from specific peers > (international tag, domestic tag, etc). > 2. write a policy that matches on tagged routes, and has an action of > 'then destination-class INTERNATIONAL' etc... > 3. apply the policy as as export policy to the forwarding-table. > 4. configure accounting for destination-class-usage on interfaces that > you wish to collect account for ... > 5. configure a firewall filter that matches on destination-class and > polices traffic to the correct rate. > > I can unicast you some configs once I dig them up from back in the day. > > DCU/DCP is a highly scalable way to provide differentiated > accounting / policing for specific aggregate services. I have seen > this deployed with 40+ regional zones. > > Cheers, > Truman Boyes > > > > On 22/01/2009, at 2:21 PM, Craig Spiers wrote: > >> Hi All.. >> >> To try and better explain what barry is trying to do.. hes trying to >> traffic shape certain IP addresses on his network based on the BGP >> community a specific route is a member of.. >> >> Eg domestic traffic is a member of community 100 and international is >> 200 >> >> Eg 1.2.3.4 on his network communicating with a route dest in community >> 100 = 128k >> Eg 1.2.3.4 on his network communicating with a route dest in community >> 200 = 64k >> >> I do this on our cisco's using BGP with ip-qos-map's and a service >> policy on the interface.. hes looking for the juniper equivalent.. >> >> Any ideas? >> >> >> Kind Regards, >> >> Craig Spiers - Network Manager >> Solarix Limited >> DDI: +64 9 974 4753 | FAX: +64 9 523 8057 FAULTS: 0800 89 41 42 >> MOB: +64 21 857 183 | email: craig.spiers(a)staff.solarix.co.nz >> The information contained in this email is privileged and confidential >> and >> intended for the addressee only. If you are not the intended recipient >> you >> are asked to respect that confidentiality and not disclose, copy or >> make >> >> use of its contents. If received in error you are asked to destroy >> this >> email and contact the sender immediately. >> >> >> -----Original Message----- >> From: Barry Murphy [mailto:barry(a)unix.co.nz] >> Sent: Thursday, 22 January 2009 3:42 p.m. >> To: Nznog >> Subject: [nznog] Juniper J2320,rate limit based on bgp community >> (national/international) >> >> Hey Guys, >> >> Hope this fits in with the AUP, however I'd hope so as not many forums >> show >> how to rate-limit based on national/international traffic as they >> don't >> bill accordingly, however in NZ this is standard practice so hoping >> someone >> with juniper knowledge can assist me here. >> >> Basically I want to allow all traffic to/from national without >> rate-limit, >> then restrict international, for eg 128k. >> >> icepick(a)NCCORE01# show firewall >> policer 128k { >> if-exceeding { >> bandwidth-limit 128k; >> burst-size-limit 4500; >> } >> then discard; >> } >> filter 128k { >> term 1 { >> from { >> forwarding-class assured-forwarding; >> } >> then accept; >> } >> term 2 { >> from { >> forwarding-class best-effort; >> } >> then { >> policer 128k; >> accept; >> } >> } >> } >> >> >> >> icepick(a)NCCORE01# show policy-options policy-statement Orcon-Primary- >> In >> term 1 { >> from community [ Orcon-Local Orcon-National Orcon-Peering >> Orcon-Telstra >> Orcon-Telecom ]; >> then { >> local-preference 110; >> forwarding-class assured-forwarding; >> accept; >> } >> } >> term 2 { >> from { >> route-filter 0.0.0.0/0 upto /24; >> } >> then { >> local-preference 110; >> forwarding-class best-effort; >> accept; >> } >> } >> term 3 { >> from { >> route-filter 0.0.0.0/0 exact; >> } >> then { >> local-preference 120; >> accept; >> } >> } >> term 4 { >> then reject; >> } >> >> >> icepick(a)NCCORE01# show interfaces ge-0/0/1 unit 55 >> description "Test interface"; >> vlan-id 55; >> family inet { >> filter { >> input 128k; >> output 128k; >> } >> address 113.21.x.x/29; >> } >> >> >> The problem I'm running into is all traffic is being rate-limited at >> 128k, >> rather than just the international. I was able to find one example >> located >> at >> http://archives.devshed.com/forums/networking-100/policer-based-on-commu >> nity-2015343.html >> however this describes the use of destination-class where I only have >> forwarding-class so I'm not sure if this has been depreciated or >> renamed >> or >> not supported by J2320. >> >> I understand this may be a question for JTAC, however I'd like to hear >> from >> users here in NZ that have managed to get this going with junos. To >> keep >> the list sane, please reply offlist, if many people are interested >> I'll >> post the working solution after being tested for archive purposes. >> >> Public holiday for Aucklanders next monday, extra long weekend of >> beer, >> mmmmm >> >> Thanks >> 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 >> > ------------------------------ Message: 3 Date: Tue, 27 Jan 2009 14:33:01 +1300 From: Nathan Ward <nznog(a)daork.net> Subject: [nznog] Vendor reception at NZNOG - Open to all To: nznog <nznog(a)list.waikato.ac.nz> Message-ID: <17CA2F72-294E-4358-BB5E-06FBF51F83BF(a)daork.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hi all, Wednesday night we are running a "vendor reception", similar to the "gear and beer" evenings at NANOG. Renaissance have generously made a prize available for the evening - an iPod Nano. This will be an open bar, with finger food. Network operators and related parties can attend - even people who are not attending the main conference. Please bring some business cards - one for to go in the prize jar, and one to put in your name tag holder if you are not a conference attendee. Please RSVP to info(a)nznog.org and let us know if you are attending, and also anyone you are bringing with you so we can put you on some kind of list. It would be great to see you here, to get a taste of the NZNOG conference, and a drink or two[1]. -- Nathan Ward [1] or three. ------------------------------ Message: 4 Date: Tue, 27 Jan 2009 14:47:30 +1300 From: Neil Gardner <nznog(a)neilnz.com> Subject: Re: [nznog] Vendor reception at NZNOG - Open to all To: nznog <nznog(a)list.waikato.ac.nz> Message-ID: <632d599d0901261747n2388b020xdfdb1083b02857a2(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 I've been politely waiting, and mid afternoon on the day before the conference seems like a reasonable time to ask again... What's the deal with streaming of the conference talks / discussions / full and frank exchange of view sessions? Cheers - N ------------------------------ Message: 5 Date: Tue, 27 Jan 2009 15:34:54 +1300 From: Nathan Ward <nznog(a)daork.net> Subject: Re: [nznog] Vendor reception at NZNOG - Open to all To: nznog <nznog(a)list.waikato.ac.nz> Message-ID: <58FF2B25-CBDE-4975-8063-5397D65B9B2A(a)daork.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On 27/01/2009, at 2:47 PM, Neil Gardner wrote: > I've been politely waiting, and mid afternoon on the day before the > conference seems like a reasonable time to ask again... > > What's the deal with streaming of the conference talks / discussions / > full and frank exchange of view sessions? R2 are doing streaming, as per usual. I'm pretty sure we've said that on the list already. This will be for the main conference, not the tutorial days. So, Thurs+Fri. We have microphones, plus microphones for anyone asking questions. -- Nathan Ward ------------------------------ Message: 6 Date: Tue, 27 Jan 2009 16:08:54 +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: <E1LReJq-0003lj-IU(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:AS17435 descr: advertised to AS9560 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 7 Date: Tue, 27 Jan 2009 16:22:11 +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: <E1LReWh-0004Pr-B6(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: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 8 Date: Tue, 27 Jan 2009 22:36:06 +1300 (NZDT) From: Mark Foster <blakjak(a)blakjak.net> Subject: [nznog] NZNOG IRC Channel To: nznog(a)list.waikato.ac.nz Message-ID: <Pine.LNX.4.64.0901272233100.27157(a)skyhawk.blakjak.net> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Hi all A headsup that #NZNOG on the Undernet IRC Network is open for NZNOG'rs to lurk in, and to perhaps provide some means of interaction between those that are here and those that, well, aren't. the DNS aliases us.undernet.org and eu.undernet.org are likely suspects if you dont know any other valid server addresses to try to connect to. See you there, Mark. ------------------------------ Message: 9 Date: Tue, 27 Jan 2009 12:57:20 -0800 From: Scott Howard <scott(a)doc.net.au> Subject: Re: [nznog] NZNOG IRC Channel To: Mark Foster <blakjak(a)blakjak.net> Cc: nznog(a)list.waikato.ac.nz Message-ID: <f1dedf9c0901271257l68036743ud3ddbc4521f20393(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" On Tue, Jan 27, 2009 at 1:36 AM, Mark Foster <blakjak(a)blakjak.net> wrote: > the DNS aliases us.undernet.org and eu.undernet.org are likely suspects if > you dont know any other valid server addresses to try to connect to. Or even the far more relevant nz.undernet.org :) (Sure, it's just a CNAME to "us", but that's not the point...) Scott

1 0

NZNOG IRC Channel
by Mark Foster 26 Jan '09

26 Jan '09

Hi all A headsup that #NZNOG on the Undernet IRC Network is open for NZNOG'rs to lurk in, and to perhaps provide some means of interaction between those that are here and those that, well, aren't. the DNS aliases us.undernet.org and eu.undernet.org are likely suspects if you dont know any other valid server addresses to try to connect to. See you there, Mark.

2 1

NZRR Route Registry Update
by NZRR Database Notifications 26 Jan '09

26 Jan '09

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:AS17435 descr: advertised to AS9439 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Jan '09

26 Jan '09

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:AS17435 descr: advertised to AS9560 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 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, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR ------------------------------------------------------------

1 0

Vendor reception at NZNOG - Open to all
by Nathan Ward 26 Jan '09

26 Jan '09

Hi all, Wednesday night we are running a "vendor reception", similar to the "gear and beer" evenings at NANOG. Renaissance have generously made a prize available for the evening - an iPod Nano. This will be an open bar, with finger food. Network operators and related parties can attend - even people who are not attending the main conference. Please bring some business cards - one for to go in the prize jar, and one to put in your name tag holder if you are not a conference attendee. Please RSVP to info(a)nznog.org and let us know if you are attending, and also anyone you are bringing with you so we can put you on some kind of list. It would be great to see you here, to get a taste of the NZNOG conference, and a drink or two[1]. -- Nathan Ward [1] or three.

2 2

Juniper J2320, rate limit based on bgp community (national/international)
by Barry Murphy 26 Jan '09

26 Jan '09

Hey Guys, Hope this fits in with the AUP, however I'd hope so as not many forums show how to rate-limit based on national/international traffic as they don't bill accordingly, however in NZ this is standard practice so hoping someone with juniper knowledge can assist me here. Basically I want to allow all traffic to/from national without rate-limit, then restrict international, for eg 128k. icepick(a)NCCORE01# show firewall policer 128k { if-exceeding { bandwidth-limit 128k; burst-size-limit 4500; } then discard; } filter 128k { term 1 { from { forwarding-class assured-forwarding; } then accept; } term 2 { from { forwarding-class best-effort; } then { policer 128k; accept; } } } icepick(a)NCCORE01# show policy-options policy-statement Orcon-Primary-In term 1 { from community [ Orcon-Local Orcon-National Orcon-Peering Orcon-Telstra Orcon-Telecom ]; then { local-preference 110; forwarding-class assured-forwarding; accept; } } term 2 { from { route-filter 0.0.0.0/0 upto /24; } then { local-preference 110; forwarding-class best-effort; accept; } } term 3 { from { route-filter 0.0.0.0/0 exact; } then { local-preference 120; accept; } } term 4 { then reject; } icepick(a)NCCORE01# show interfaces ge-0/0/1 unit 55 description "Test interface"; vlan-id 55; family inet { filter { input 128k; output 128k; } address 113.21.x.x/29; } The problem I'm running into is all traffic is being rate-limited at 128k, rather than just the international. I was able to find one example located at http://archives.devshed.com/forums/networking-100/policer-based-on-communit… however this describes the use of destination-class where I only have forwarding-class so I'm not sure if this has been depreciated or renamed or not supported by J2320. I understand this may be a question for JTAC, however I'd like to hear from users here in NZ that have managed to get this going with junos. To keep the list sane, please reply offlist, if many people are interested I'll post the working solution after being tested for archive purposes. Public holiday for Aucklanders next monday, extra long weekend of beer, mmmmm Thanks Barry

3 3

System Administrators Miniconf draft schedule
by Ewen McNeill 25 Jan '09

25 Jan '09

The NZNOG 2009 conference starts tomorrow (Wed 2009-01-28) with the tutorial day, including the System Administrators Miniconf. As previously announced the System Administrators Miniconf is being held in more of a BoF style (shorter intro talks, more discussion) with a more flexible schedule than previous years. But for the benefit of those who are hoping to switch back and forth between tutorials, this is approximately what we intend to have in terms of ordering and timing: -=- cut here -=- Intro/Welcome Ewen McNeill: Scaling System and Network monitoring Peter Mott: VMware in a production environment Jonny Martin: PCH VMWare Platform * Morning Tea * Amos Jeffries: Squid web caching Michael Robinsion: Configuration automation (puppet, cfengine, etc) Jonny Martin: ENUM intro -=- cut here -=- About the only thing which is actually fixed is the morning tea (10:30-11:00) and the start (at approximately 09:00). I believe we have the room for at least half a day, and perhaps the full day, so we're open to adding more topics (or a general "problem solving" type BoF) after the things listed above. Ewen

1 0

One room available at the NZNOG venue this week.
by Jonny Martin 25 Jan '09

25 Jan '09

Hi All, We've had one room become available at the conference venue for this week, it's available for Tuesday through Friday nights. If you still haven't sorted your accommodation out for this week, then you may be in luck. First to reply to me gets it. Cheers, Jonny.

1 1

Xtra DNS Servers
by Jonathan Wood 25 Jan '09

25 Jan '09

Hi there all, I just got this message from our friends at telecom Dear Customer, On Saturday morning (24 January 2009) an unforeseen technical fault affected some Telecom customers. Broadband and Dial-Up internet connections were working, however you may have had problems accessing Xtra email, as well as some services on the Yahoo!Xtra website. Our technical teams worked swiftly to identify and resolve the problem, and the majority of services were restored by midday. We apologise if you were impacted or inconvenienced by the interruption. Sincerely, The Team at Telecom This email is being sent to you as it is a service related message about products and services you have with Telecom. It is not a promotional email. This email is being sent on behalf of Telecom NZ Ltd by Jericho Ltd. Telecom New Zealand. 8 Hereford Street, Freemans Bay, Auckland 1011, NZ. jonno

1 0

Re: [nznog] Use of .0 and .255 in address pools
by Scott Weeks 25 Jan '09

25 Jan '09

: Curiousity about what people are using as far as : addressing pools these days - lots of /24s (and : excluding the end addresses), or bigger blocks? : More specifically, is anyone handing out the .0 : and .255 addresses, or are there still sufficient : CPE/endpoints out there which cope poorly with : those addresses? :: I've been handing out /23s for years now and have :: had zero problems with the middle 0 and 255. ::: I guess I should qualify my statement. I have ::: been handing out /23s with no problems at all ::: on a eyeball network. Not on a content network. :::: I know Telecom were/are handout out .0 addresses :::: on their 3G connections too. It's a pain Can you elaborate on this? Are you still talking about the 'middle' .0 and .255 IPs of /23s and larger? What troubles have you seen and what kind of mobile devices are you talking about? scott ----------------------------- ----------------------------- -----------------------------

1 0

Re: [nznog] Use of .0 and .255 in address pools
by Scott Weeks 24 Jan '09

24 Jan '09

------ surfer(a)mauigateway.com wrote: ------- ------ ender(a)paradise.gen.nz wrote: -------- Curiousity about what people are using as far as addressing pools these days - lots of /24s (and excluding the end addresses), or bigger blocks? More specifically, is anyone handing out the .0 and .255 addresses, or are there still sufficient CPE/endpoints out there which cope poorly with those addresses? ------------------------------------------ I've been handing out /23s for years now and have had zero problems with the middle 0 and 255. ------------------------------------------- I guess I should qualify my statement. I have been handing out /23s with no problems at all on a eyeball network. Not on a content network. scott ----------------------- ----------------------- -----------------------

2 1

Xtra DNS Servers
by Nick Larsen (ZeroOne Operations) 23 Jan '09

23 Jan '09

Hi, Is anyone having trouble resolving domains hosted on {alien,terminator}.xtra.co.nz? Xtra's DNS servers seem to have disappeared (at least from the locations I've tried from). Kind regards, Nick Larsen Network Technician DDI +64.4.471.4447 Freephone 0800 ZEROONE Ph +64.4.499.0018 Fax +64.4.499.0019 Address Level 4, United Building. 107 Customhouse Quay, Wellington, New Zealand

6 8

Re: [nznog] [AusNOG] Cisco Pricing.. blah
by Skeeve Stevens 23 Jan '09

23 Jan '09

Thank God! -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced. > -----Original Message----- > From: Tom Storey [mailto:tom(a)snnap.net] > Sent: Saturday, 24 January 2009 12:54 PM > To: skeeve(a)skeeve.org > Cc: ausnog(a)ausnog.net; nznog(a)list.waikato.ac.nz; Skeeve Stevens > Subject: Re: [AusNOG] Cisco Pricing.. blah > > > On 24/01/2009, at 11:55 AM, Skeeve Stevens wrote: > > > Then January 9th 09 of 18% > > > > Now it is going up another 18% on 30th January 09 > > > Not quite. > > The price rise on Jan 9 was pushed back to Feb 1, so only one 18% > increase (thankfully). > > Tom

1 0

Re: [nznog] [AusNOG] Cisco Pricing.. blah
by Tom Storey 23 Jan '09

23 Jan '09

On 24/01/2009, at 11:55 AM, Skeeve Stevens wrote: > Then January 9th 09 of 18% > > Now it is going up another 18% on 30th January 09 > Not quite. The price rise on Jan 9 was pushed back to Feb 1, so only one 18% increase (thankfully). Tom

1 0

FW: Cisco Pricing.. blah
by Skeeve Stevens 23 Jan '09

23 Jan '09

Hey all, Cisco had a price rise 1st November 08 Then January 9th 09 of 18% Now it is going up another 18% on 30th January 09 Fun oh fun. I assume this effects NZ as well, but not sure to what % ...Skeeve From: http://www.lansystems.com.au/NewsAndEvents/News/NewsItem.asp?objid=168&cont… As you are most likely aware there will be a Cisco price increase effective close of business Friday 30th January 2009. The price increase of approximately 18% will affect all hardware orders. All orders received by 12pm AEDST on Friday 30th January 2009 will be processed by Westcon Group at the quoted pricing. Any orders received after this time will need to be requoted at the new pricing. All quotes for Cisco hardware products will only be valid until 12pm AEDST 30th January 2009. There will be no delays providing Cisco quotations following the price increase. Westcon Group will continue to maintain our standard Cisco quoting turnaround times. Please continue to send all quote requests to support(a)westcongroup.com.au<mailto:support(a)westcongroup.com.au>. A friendly reminder of Westcon's purchase order requirements: * All Cisco orders require valid end user information. * Any amendments received after 30th January 2009 to orders placed prior to Friday 30th January 2009 will be at the new pricing. * Any orders without valid or correct Cisco Deal ID information placed prior to the 30th January 2009 will need to be amended at the new pricing. No exceptions will be made to the above requirements. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced. NOC, NOC, who's there?

1 0

Try these DNS servers on Xtra's network
by Robert Cotter 23 Jan '09

23 Jan '09

202.27.158.40 202.27.184.5 202.27.184.3 202.27.156.72 Regards Robert Cotter Sales Engineer rcotter(a)distributioncentral.co.nz<mailto:rcotter(a)distributioncentral.co.nz> ________________________________ This email is for the intended recipient(s) only. Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 8986 5000 or notify sender.

2 1

Use of .0 and .255 in address pools
by David Robb 21 Jan '09

21 Jan '09

Curiousity about what people are using as far as addressing pools these days - lots of /24s (and excluding the end addresses), or bigger blocks? More specifically, is anyone handing out the .0 and .255 addresses, or are there still sufficient CPE/endpoints out there which cope poorly with those addresses? --David

8 10

2009 APNIC Member and Stakeholder Survey
by Elly Tawhai 21 Jan '09

21 Jan '09

_______________________________________________________________________ 2009 APNIC Member and Stakeholder Survey _______________________________________________________________________ Hi NZNOG Community, The 2009 APNIC Member and Stakeholder survey has now closed and APNIC would like to thank all those who participated. Your input will directly affect APNIC activities, in particular: * the assessment of APNIC performance; * where APNIC member revenue should be invested; and * IPv6 readiness in the Asia Pacific region APNIC appreciates the time and effort you have taken to complete the survey (or those parts relevant to you). KPMG are now collating the results and this will be made available to all stakeholders (both members and non-members) as soon as possible. KPMG have informed us of the following winners of the prize draw: Apple i-phone ------------- Name: Chinbaatar Bazargur Economy: MONGOLIA Eee PCs ------- Name: Doug Purdie Economy: AUSTRALIA Name: Praveen Pai Economy: INDIA APNIC thanks you for Having Your Say! Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ________________________________________________________________________

1 0

Re: [nznog] Use of .0 and .255 in address pools
by Scott Weeks 21 Jan '09

21 Jan '09

------ ender(a)paradise.gen.nz wrote: -------- From: David Robb <ender(a)paradise.gen.nz> Curiousity about what people are using as far as addressing pools these days - lots of /24s (and excluding the end addresses), or bigger blocks? More specifically, is anyone handing out the .0 and .255 addresses, or are there still sufficient CPE/endpoints out there which cope poorly with those addresses? ------------------------------------------ I've been handing out /23s for years now and have had zero problems with the middle 0 and 255. scott ----------------------- ----------------------- -----------------------

1 0

Re: [nznog] Wellington Power Outage
by Craig Spiers 19 Jan '09

19 Jan '09

Yep all of our gear is back too.. --- original message --- From: "Matthew Poole" <matt(a)p00le.net> Subject: Re: [nznog] Wellington Power Outage Date: 21st January 2009 Time: 9:16:38 am -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Looks like it's just come back. My mail server just returned to life. Jonathan Brewer wrote: | Hi Folks, | | For those in the rest of the country wondering what's gone wrong in | Wellington, we started seeing end users disappear at 07:44 this morning from | a power outage. It looks like parts of the CBD, Te Aro, Kandallah, | Roseneath, Kelburn, Mt. Cook, Brooklyn, and Melrose are still without power. | | | | Too many tea kettles and hair dryers at the same time I guess. | | | | Regards, | | Jon | | | | | ------------------------------------------------------------------------ | | _______________________________________________ | NZNOG mailing list | NZNOG(a)list.waikato.ac.nz | http://list.waikato.ac.nz/mailman/listinfo/nznog - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl2MR8ACgkQTdEtTmUCdpyoCACfdc1rxUkkUaExubiaTY61FDYR JK8An0rJ8DmsSVKVmMS4FeKKQj5ya+dq =MWV/ -----END PGP SIGNATURE----- _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Wellington Power Outage
by Jonathan Brewer 19 Jan '09

19 Jan '09

Hi Folks, For those in the rest of the country wondering what's gone wrong in Wellington, we started seeing end users disappear at 07:44 this morning from a power outage. It looks like parts of the CBD, Te Aro, Kandallah, Roseneath, Kelburn, Mt. Cook, Brooklyn, and Melrose are still without power. Too many tea kettles and hair dryers at the same time I guess. Regards, Jon

3 2

APNIC 27 - Last days for Early Bird registration
by Srinivas (Sunny) Chendi 19 Jan '09

19 Jan '09

_______________________________________________________________________ Last days for Early Bird registration _______________________________________________________________________ Register now to take advantage of a discount of up to 25% on your registration in our early bird special. http://meetings.apnic.net/register PROGRAM HIGHLIGHTS ------------------ Check the latest information update for the content-packed APNIC 27 / APRICOT 2009 program. IPv6 in 3D ----------- Is your IPv6 world feeling a little flat? Flesh it out with this three-dimensional plenary! Hear speakers share their practical experiences from three layers of the network stack. http://meetings.apnic.net/program/ipv63d/index.html Internet Governance Pulong --------------------------- Gather to discuss how we can overcome the challenges facing Internet operators across our region. http://meetings.apnic.net/program/igov/index.html ARE YOU READY FOR APNIC 27? --------------------------- Book your travel ---------------- Manila is also the gateway to the many popular tourist destinations of the Philippines. The APNIC 27 Meeting website has all the information you need to plan your APNIC 27 trip. http://meetings.apnic.net/manila Join the policy discussion --------------------------- Draft policy proposals are now online for review and discussion. Be a part of the policy development process by participating in the APNIC policy mailing list and in the Policy SIG session at APNIC 27. http://www.apnic.net/docs/drafts Executive Council nominations and proxies ----------------------------------------- Four positions on the APNIC Executive Council are open in the election at the APNIC Member Meeting in Manila on Friday, 27 February 2009. Nominate your candidate http://meetings.apnic.net/elections/nominate.html If you would prefer to assign your votes to a proxy, APNIC is currently accepting proxy nominations. The nomination form should be faxed to +61-7-38583199 or emailed to helpdesk(a)apnic.net. Complete a proxy form http://www.apnic.net/meetings/proxy.html For more on APNIC 27, visit: http://www.meetings(a)apnic.net _______________________________________________________________________ Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99 _______________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '09

19 Jan '09

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/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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.49.164.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.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.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.208.21.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: david.johnson(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 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/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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.49.164.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.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.170.56.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: david.johnson(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090120 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '09

19 Jan '09

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:AS24183 descr: advertised to AS9439 by DTS Ltd - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.27.88.0/23^23-29, 202.174.178.0/23^23-29, 202.174.190.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.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: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070907 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24183 descr: advertised to AS9439 by DTS Ltd - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.27.88.0/23^23-29, 202.174.178.0/23^23-29, 202.174.184.0/23^23-29, 202.174.190.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 203.170.56.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: vaa(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090120 source: NZRR ------------------------------------------------------------

1 0

I-Root available on WIX
by Dylan Hall 19 Jan '09

19 Jan '09

Citylink is pleased to announce that the i-root name servers are now being anycast on the WIX. They are announcing the ranges to the route servers at present. Anyone interested in a private peering session can contact Autonomica directly (please provide the following information): AS: 8674 WEL IP's: 202.7.0.209 AND 202.7.0.210 Macro: AS-NETNOD-ANYCAST Contact: peering(a)netnod.se

1 0

Re: [nznog] enum
by Michael Sutton 15 Jan '09

15 Jan '09

FYI. So now who will be the next who dares to request our Country's delegation and be denied and how many more years will New Zealand wait before those that decide policy realize that there is a national opportunity cost to their inaction. Sincerely Michael Sutton -----Original Message----- From: enum-announce-admin(a)ripe.net [mailto:enum-announce-admin(a)ripe.net] On Behalf Of RIPE NCC Staff Sent: Wednesday, 14 January 2009 11:58 p.m. To: james(a)freedomnet.co.nz Cc: enum-announce(a)ripe.net Subject: [enum-announce] Fw: NCC#2008124814 [RE: [Re: enum request for 4.6.e164.arpa - correction]] Dear James, the RIPE NCC has received the following answer from ITU-T TSB and therefore will not delegate the zone as you have requested. Kind regards, Marco Schmidt RIPE NCC ----- Begin forwarded message ----- Date: Wed, 14 Jan 2009 11:36:46 +0100 From: <richard.hill(a)itu.int> To: <enum-request(a)ripe.net> Subject: RE: NCC#2008124814 [Re: enum request for 4.6.e164.arpa - correction] Message-Id: <334A4109C6BEA14ABB48EBCF274A6C8A03D79119(a)MAILBOX1.blue.itu.ch> The ITU Telecommunications Standardization Bureau (TSB) objects to this request because no approval for delegation of the code 64 has been received from the concerned country, New Zealand. Until formal approval is given in writing by the Director of TSB, no delegation should take place for this code. Richard Hill ----------------------------------------- Richard Hill Counsellor, ITU-T SG2 and SG3 International Telecommunication Union Place des Nations CH-1211 Geneva 20 Switzerland > -----Original Message----- > From: RIPE NCC Staff [mailto:enum-request(a)ripe.net] > Sent: Wednesday, December 24, 2008 8:56 AM > To: enum-announce(a)ripe.net; Hill, Richard > Subject: Fw: NCC#2008124814 [Re: enum request for 4.6.e164.arpa - > correction] > > ----- Begin forwarded message ----- > > Date: Wed, 24 Dec 2008 09:26:34 +1300 > From: "James Jones" <james(a)freedomnet.co.nz> > To: enum(a)ripe.net, enum-request(a)ripe.net > Subject: Re: NCC#2008124814 enum request for 4.6.e164.arpa - correction > Message-Id: <6104c3e30812231226h190be2b0p15f4fa71fa744983(a)mail.gmail.com> > > > % ENUM Request Form > > % You can use this form to request ENUM delegation of an E.164 country > code. % Submit the completed form to <enum-request(a)ripe.net>. > % Please see ripe-385 for instructions on how to complete this form. > > #[GENERAL INFORMATION]# > % > % Please do not change the value of the two fields below. > > request-type: enum > form-version: 1.0 > > #[REQUESTER DETAILS]# > % > % Please add your contact details. > > name: James Jones > phone: +6421763939 > fax-no: > e-mail: james(a)freedomnet.co.nz > > #[ORGANISATION DETAILS]# > % > % Which organisation is requesting the delegation? > > legal-organisation-name: Freedom Networks Limited > organisation-location: Levin, New Zealand > website: http://www.freedomnet.co.nz > > #[DATABASE TEMPLATE]# > % > % Please complete all of the fields below. > > domain: 4.6.e164.arpa > descr: Freedom Networks Limited > org: ORG-FNL5-RIPE > admin-c: JJN15-RIPE > tech-c: JJN15-RIPE > zone-c: JJN15-RIPE > nserver: enum1.freedomnet.co.nz > nserver: enum2.freedomnet.co.nz > mnt-by: Freedom_Networks > changed: james(a)freedomnet.co.nz 20081223 > source: RIPE > > #[SUPPLEMENTAL COMMENTS]# > % > % Please add more information if you think it will help us understand > % this request. > > We would like to be the registrar for enum lookup for New Zealand. We > believe this is right direction for VoIP and terminations services. > Please let us know if you have any further questions. > > #[END of REQUEST]# > ------ End forwarded message ------ ------ End forwarded message ------

10 15

NZNOG09 Update
by Jonny Martin 14 Jan '09

14 Jan '09

Hi All, The complete program for NZNOG09 is now up. Thanks to Neil and the program committee for their efforts in putting the program together. http://2009.nznog.org/ For all those of you who missed out on accommodation at the venue itself we have an unofficial second hotel - Five Forty on Great South - which is 1 km away. Rooms are currently $110/night single, $135/night twin. Note that NZNOG does NOT have a block booking or any particular arrangement in place with the hotel. It is up to you to book directly with the hotel. http://www.540.co.nz/ There are already a number of conference attendees booked into this hotel so you will not be alone if you decide to stay there. Cheers, Jonny. (for the NZNOG 09 Org team)

1 0

NZNOG'09 Lightning Talks
by Neil Fenemor 14 Jan '09

14 Jan '09

Hi, NZNOG'09 is fast approaching. This year it is being held in Auckland, but as I am sure you have all registered by now (and if you haven't, head over to http://2009.nznog.org/register ), I'm now seeking interest for lightning talks. Lightning talks are very short 5-10 minute talks on a wide range of topics. It is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to do a full talk. This year we are aiming to have two separate sessions, one for general lightning talks, and one for IPv6 related talks while we run the IPv6 hour. If you are interested in speaking, please send a brief description to talks(a)nznog.org Kind Regards, Neil Fenemor NZNOG'09

2 1

NZNOG streaming as per previous years?
by Neil Gardner 14 Jan '09

14 Jan '09

I've browsed the site but can't find mention of live streams of the presentations. Is this going to happen again this year? I haven't been able to organise time to attend in person but there look like some very interesting presentations I can make time for at my desk. Cheers - N

2 1

NZRR Route Registry Update
by NZRR Database Notifications 13 Jan '09

13 Jan '09

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:AS4826 descr: advertised to AS9560 by Vocus - AS4826 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, 115.187.128.0/17^17-29, 113.192.0.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.161.64.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.32.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.14.32.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.89.64.0/19^19-29, 203.145.32.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 116.213.32.0/20^20-29, 117.55.224.0/20^20-29, 119.15.96.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.88.112.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.193.176.0/21^21-29, 116.212.64.0/21^21-29, 119.31.232.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.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.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 125.254.112.0/22^22-29, 140.200.248.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.33.116.0/22^22-29, 203.62.184.0/22^22-29, 203.79.16.0/22^22-29, 203.92.28.0/22^22-29, 203.161.128.0/22^22-29, 203.161.140.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.184.0/22^22-29, 203.185.228.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.211.56.0/22^22-29, 59.86.160.0/23^23-29, 63.218.156.0/23^23-29, 74.80.126.0/23^23-29, 114.111.132.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.160.230.0/23^23-29, 122.100.6.0/23^23-29, 122.100.8.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.6.42.0/23^23-29, 202.12.90.0/23^23-29, 202.36.204.0/23^23-29, 202.92.94.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.90.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.79.88.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.161.134.0/23^23-29, 203.161.136.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 203.185.226.0/23^23-29, 206.222.230.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.59.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.122.132.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.124.0/24^24-29, 203.4.154.0/24^24-29, 203.5.45.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.16.243.0/24^24-29, 203.17.4.0/24^24-29, 203.17.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.28.14.0/24^24-29, 203.29.0.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.230.0/24^24-29, 203.63.3.0/24^24-29, 203.63.67.0/24^24-29, 203.79.20.0/24^24-29, 203.92.25.0/24^24-29, 203.96.157.0/24^24-29, 203.98.81.0/24^24-29, 203.111.63.0/24^24-29, 203.111.105.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.185.225.0/24^24-29, 203.190.217.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.0/24^24-29, 4.53.16.144/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tech(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081215 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - AS4826 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 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, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.161.64.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.32.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.14.32.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.145.32.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 113.20.0.0/20^20-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.141.96.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 117.55.224.0/20^20-29, 119.15.96.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 174.128.16.0/20^20-29, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.88.112.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.90.128.0/21^21-29, 116.193.176.0/21^21-29, 116.212.64.0/21^21-29, 119.31.232.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 192.173.16.0/21^21-29, 202.36.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.92.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.160.8.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 125.254.112.0/22^22-29, 140.200.248.0/22^22-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.50.188.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.33.116.0/22^22-29, 203.62.184.0/22^22-29, 203.79.16.0/22^22-29, 203.92.28.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 59.86.160.0/23^23-29, 63.218.156.0/23^23-29, 74.80.126.0/23^23-29, 114.111.132.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.160.230.0/23^23-29, 122.100.6.0/23^23-29, 122.100.8.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.6.42.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.36.204.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.92.94.0/23^23-29, 202.93.4.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.90.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.79.88.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.9.230.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 97.64.46.0/24^24-29, 113.212.98.0/24^24-29, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.174.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.168.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.190.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.106.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.122.132.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.4.154.0/24^24-29, 203.5.45.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.16.243.0/24^24-29, 203.17.4.0/24^24-29, 203.17.68.0/24^24-29, 203.17.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.0/24^24-29, 203.18.136.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.26.204.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.28.14.0/24^24-29, 203.29.0.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.139.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.57.93.0/24^24-29, 203.63.3.0/24^24-29, 203.63.67.0/24^24-29, 203.79.20.0/24^24-29, 203.92.25.0/24^24-29, 203.96.157.0/24^24-29, 203.98.81.0/24^24-29, 203.111.63.0/24^24-29, 203.111.105.0/24^24-29, 203.119.56.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.171.4.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 205.233.128.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.55.110.0/24^24-29, 210.56.153.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090114 source: NZRR ------------------------------------------------------------

1 0

Announcing Dragon Research Group; sponsored by Team Cymru
by Marcel van den Berg 12 Jan '09

12 Jan '09

Hi All, Below is the announcement of the Dragon Research Group. Forwarding this message to the NZNOG list in case anyone is interested. :::: In close cooperation with Team Cymru, Dragon Research Group is announcing the launch of a new volunteer research organization dedicated to further understanding online criminality and providing actionable intelligence for the benefit of us all. The Dragon Research Group is a 'not for profit' entity and as envisioned will be comprised of a geographically dispersed set of trusted volunteers who are passionate about making the Internet more secure. Start up resources will be donated by Team Cymru but DRG will rely on donations from other organizations in the future. To meet its intended purpose, there will be a rigorous vetting procedure but selected applicants will become part of a group that will have access to the data and tools to really make a difference in the fight against online crime. The secure infrastructure is already in place and we're currently finalizing some of the procedural details. Please expect a formal launch announcement in the near future. Meanwhile, if you would like to express an interest in becoming part of or making a donation to this exciting new group, please contact dragon(a)cymru.com. ::::: Cheers! Marcel van den Berg, Team Cymru. marcel(a)cymru.com | desk: +1 312 924 4045 | CellNZ: +64 210 69 2203 PGP Key at http://www.cymru.com/teamcymrukey.txt

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Jan '09

12 Jan '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES6:AS17705 descr: Route set advertised to AS9439 by Inspire Net Ltd - AS17705 mp-members: 2404:1800:0:0:0:0:0:0/33^33-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dave(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090113 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES6:AS17705 descr: Route set advertised to AS9439 by Inspire - AS17705 mp-members: 2404:1800:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090113 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] FW: The Cidr Report
by Mark Davies 12 Jan '09

12 Jan '09

On Sunday 11 January 2009 03:41:26 Joe Abley wrote: > On 10 Jan 2009, at 00:42, jamie baddeley wrote: > >> 151.135.0.0/16 AS4768 CLIX-NZ TelstraClear Ltd > > > > Any reason why our friends at TCL are announcing (what appears to > > be) an > > unallocated block? > > An old CAIDA report included the following line": > > 595 151.135.248.1 gateb.opus.co.nz 151.135.248.0/22 8366 as4763np1at2 [...] > 4763 sounds right for an ex-Netlink block. I don't know who Opus are, > but their domain is still registered and has a Wellington address on > it, which also sounds right for an ex-Netlink block. Opus is an International Civil Engineering Consultancy firm (ex Works Consultancy). 151.135.0.0/16 is their old class B. They "gave it back" a couple of years ago as they were basically only using it behind a firewall and they wanted to be good net citizens (My wife contracts to them). cheers mark

2 1

Appointment of NZRS Chief Executive
by Andy Linton 12 Jan '09

12 Jan '09

This extract is from an NZRS press release went out earlier today - I'm posting it to the list given the recent discussion on this list regarding Enum and the reference to it here. .nz Registry Services is delighted to announce the appointment of Jay Daley to the position of Chief Executive of NZRS. Jay was formerly Director of IT at Nominet UK, one of the world’s leading domain name registries, and brings to his new role a wealth of experience in registry management, leadership and strategic management, and critical technology systems management. He combines a passion for technical excellence with a desire to foster a culture of consensus decision‐ making, lifelong learning, knowledge sharing and excellent customer service. One of Jay’s notable recent successes has been heading the implementation of Enum in the UK, the first diversification undertaken by Nominet UK.

1 0

A very rough overview of current state of NZ IPv6 deployment.
by Dean Pemberton 11 Jan '09

11 Jan '09

I'm not cross-posting I swear =) The following information was just posted to the IPv6 Steering Group TechSIG list and as it's got network operational content I'm posting it here as well. http://www.geek.nz/ipv6/ It's a quick stab (not complete by any means at all) at a survey of the state of IPv6 deployment within New Zealand. Discussion around this is in full flight on the TechSIG list. For those of you who missed what list I'm talking about. Here is the the invitation again. Dean ---------------------------- A workshop at held at InternetNZ on the 28 November in Wellington saw the formation of a New Zealand IPv6 Steering Group. This group includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. The members of this steering group consist of invited senior representatives from the following organisations: InternetNZ TUANZ ISPANZ Telecommunications Carriers Forum Digital Development Forum Telecom TelstraClear WorldXChange Orcon FX Networks REANNZ Canterbury Development Corporation Kordia Cisco Vodafone Juniper Networks Alcatel Lucent Braintrust Prophecy Networks This steering group will primarily be concerned with high level discussion regarding the deployment of IPv6 within New Zealand. The steering group will not necessarily be a place where technical discussion takes place. As with so many things these days, a combination of business and technical expertise must be bought together to solve a given problem. To this end at the same workshop a Technical Special Interest Group (TechSIG) was also established. The goals of this group are: . To act as a central point for IPv6 technical discussion within the New Zealand Internet community. . To identify to the IPv6 Steering Group any business related barriers to IPv6 deployment which have been identified by the SIG's technical contributors. . To comment and provide potential solutions to technical related barriers identified by members of the IPv6 Steering Group. . To stimulate the production of relevant technical documentation. The co-conveners of this group are Andy Linton Nathan Ward Brian Carpenter Dean Pemberton A mailing list has been created and membership is open to all interested parties. Subscription details can be found at the link below; http://listserver.internetnz.net.nz/mailman/listinfo/ipv6-techsig I would encourage anyone who has an interest in the deployment and growth of IPv6 to join and contribute to the list. Please do not feel that this is a 'Networking Specialist Only' list. The deployment of IPv6 (and depletion of IPv4) has just as significant an impact on system administrators and content/application providers as it does on network administrators. I welcome all technical viewpoints onto the list. Thank you for your time. Dean Pemberton (Co-convener, IPv6 Steering Group Technical SIG)

2 2

Re: [nznog] NZNOG 2009 Network Management Miniconf
by Ewen McNeill 11 Jan '09

11 Jan '09

In message <20081220012229.F382C112733(a)wat.la.naos.co.nz>, Ewen McNeill writes: >If you've registered for NZNOG 2009 (http://2009.nznog.org/register) >you will have seen that we are holding another network administrators >miniconf on the Wednesday tutorial day. One more reminder to send us (a) topics you'd like to see discussed, and (b) offers to introduce a specific topic. This is your chance to talk with your peers about layer 7 issues which are of relevance to you. To date we have had suggested: - configuration automation (puppet, cfengine, and friends) - scaling network monitoring (eg, distributed nagios) - virtualisation (VMWare ESX, etc) No one showed any interest in talking about ENUM (either having it as a topic, or giving an intro talk), so perhaps that topic is too last week. We'd be happy to host it if there is still interest, particularly if those trying to get the 4.6.e164 delegation are willing to turn up and talk about it. Please send additional topics (and ideally offers to present for 5-15 minutes as an intro to the topic) to: <talks09(a)nznog.miniconf.org> Simon Lyall and Ewen McNeill Network Administrators Miniconf

1 0

[Fwd: Re: NZNOG list as NZNOC list.....]
by Gerard Creamer 11 Jan '09

11 Jan '09

On 12/01/2009 2:27 p.m., Andy Linton wrote: > > > And of course that page is already there. Doh! > > It's at http://www.nznog.org/?page_id=6 And this thread has prompted quite a few updates to the NOC list, which is fantastic. If there are any more changes or alterations please send them to info (at) nznog.org and I'll do them all at the same time. Cheers, Gerard

1 0

Compass Networks Email Servers IP addresses on RBL List again
by Robert Cotter 11 Jan '09

11 Jan '09

It looks like Compass have got one of their email servers IP addresses on a RBL IP list . 203.152.112.39 The tester i am using is http://www.fortiguardcenter.com/antispam/antispam.html#spamlookup Could some body let them know please, so I stop getting complaints from my partner about the stupid anti-spam system flagging legitimate emails wrong. Regards Robert Cotter ________________________________ This email is for the intended recipient(s) only. Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 8986 5000 or notify sender.

8 12

Re: [nznog] FW: The Cidr Report
by jamie baddeley 09 Jan '09

09 Jan '09

> -----Original Message----- > From: cidr-report(a)potaroo.net [mailto:cidr-report(a)potaroo.net] > Sent: Saturday, 10 January 2009 12:00 a.m. > To: cidr-report(a)potaroo.net > Cc: apops(a)apops.net; afnog(a)afnog.org; nanog(a)merit.edu; eof-list(a)ripe.net; routing-wg(a)ripe.net > Subject: The Cidr Report > > This report has been generated at Fri Jan 9 21:13:41 2009 AEST. > The report analyses the BGP Routing Table of AS2.0 router and generates a report on aggregation potential within the table. > > Check http://www.cidr-report.org for a current version of this report. > 8<---SNIP--------------- > > Possible Bogus Routes > > 151.135.0.0/16 AS4768 CLIX-NZ TelstraClear Ltd Folks, Any reason why our friends at TCL are announcing (what appears to be) an unallocated block? Jamie

3 2

Informational - Vocus Outage at APE - 12/01/2009
by McDonald Richards 08 Jan '09

08 Jan '09

Date: 12/1/2009 2:00 AM AEDT to 12/1/2009 4:00 AM AEDT Advisory Type: Informational Services: Data Service Affecting: APE Connectivity Advisory Notes: Due to planned works on Monday the 12th of January commencing at 2:00AM AEDT the Vocus ASN 4826 peering session at APE will be down for a brief period. Please address any questions or concerns to noc(a)vocus.com.au. Regards, Vocus NOC

1 0

NZNOG09 not too far away now...
by Jonny Martin 07 Jan '09

07 Jan '09

Hi All, NZNOG09 is now less than three weeks away. Please register now if you haven't already! Please don't leave it until the last week as so many of you tend to do :). http://2009.nznog.org/ The NZNOG block booking at the Mount Richmond Hotel for NZNOG09 has now completely sold out. Given that we block booked virtually the entire hotel you'll find it hard to get accommodation there for the duration of the conference if you haven't already booked it. We have a great list of speakers again this year, as well as not one, but two social functions which are at no additional cost thanks to our generous sponsors. Thanks, and look forward to seeing you in Auckland, City of Sales... Jonny. For the NZNOG09 org team.

1 0

Re: [nznog] enum
by Michael Sutton 06 Jan '09

06 Jan '09

This is my third email on the subject of ENUM. (on a diet) Firstly; I would appreciate and hope that experts including members of NZNOG do not argue to justify why USER ENUM should NOT be implemented in New Zealand. It is not up to individuals to quantify how it will be used or the value of it to end users and application developers in the fullness of time. It is instead up to our community to actively promote and facilitate the use of any reasonable protocol on the Internet. The truly unique fact about 4.6.e164.arpa is that it is an officially sanctioned/moderated top level domain using the stable DNS ENUM services. ENUM (the protocol) is operational around the world and also in New Zealand via DNS client USER ENUM enquiries made both to countries already actively using e164.arpa as well as other registries such as e164.org TLD's. For myself I see this as a real issue of my personal Internet usage rights in New Zealand. Imagine if we were still considering whether New Zealand should have its own CC TLD. That is the situation we are in with respect to USER ENUM 4.6.e164.arpa. I cannot opt-in to register my New Zealand telephone number and all my associated communication services while ~50 countries can. Imagine if each internet protocol had to be approved by local entities such as the MED, TCF and InternetNZ. Eg. email or http/https web or skype or h323 - such a scenario is impossible to countenance. Yet User ENUM 4.6.e164.arpa delegation has been "frozen" for years by agreements between the MED (TCF and InternetNZ). 4.6.e164.arpa delegation must be approved by the MED and as such I recommend that the MED delegate it to themselves and fast track operation and policy implementation. New Zealand Telco companies who are members of the TCF already use PROVIDER ENUM as a backroom routing protocol. There is nothing they need from USER ENUM 4.6.e164.arpa but they do need to co-operate with the authentication process for establishing USER ENUM registrations. The political issue here of USER ENUM is why New Zealanders are being 'prevented' from using this service. We need a least cost, least capture USER ENUM Registry to be established which puts ENUM client users as well as application developers interests as the prime consideration. Issues concerning +1 delegation: Previous emails suggested that the United States +1 delegation was lapsed as there was no demand - This is not the situation. It is useful to appreciate that +1 represents a number of Caribbean countries as well as Canada and the United States and the complications that this fact originally had. +1 had been registered delegated for trial to "CC1 ENUM LLC" (a private company Country Code 1 ENUM Limited Liability Company). This Company's shareholders include AT&T, Sprint-Nextel, and Verizon etc - Board Papers show the stake-holder were/are not in themselves interested in supporting USER ENUM instead their primary goal was PROVIDER ENUM with delegation of 1.e164.arpa to the Company. The US State Department however "refused" to renew the +1 registration to CC1 ENUM LLC in February 2008 as the Company does not need the delegation to operate PROVIDER ENUM. Indeed the Company is proceeding with PROVIDER ENUM using 1.e164.us. (which is not a sanctioned ITU ENUM). Then in May of 2008, positively supported by United States Representatives, the ITU SG adopted "new" guidelines to cover delegation of numbers such as +1 which represent multiple countries. Therefore Canada and the other Caribbean countries are also supporting this guideline. What appears to have happened is that because CC1 ENUM LLC was only really interested in routing optimization, the US Government has pulled the plug on it because it was making no plan for USER ENUM and rather than letting the LLC remain as the Delegee the U.S.G. decided to prevent capture by this entity. This situation closely mirrors that in New Zealand - the networks want PROVIDER ENUM but eschew USER ENUM. The actions of the US Government in May 2008 (Geneva) show that they are very keen for USER ENUM to be enabled for the 1.e164.arpa countries. My advice to the Minister: On the 19th December 2008 I wrote to Ministers of the NZ Government requesting (in one part) that implementation of USER ENUM be expedited and set as a KPI of the relevant Ministry. I was completely unaware at the time of the application that was to be made on the 23rd of December by Mr. Jones for delegation of 4.6.e164.arpra. Unless the ITU receives a letter from the MED within 60 days of Mr. Jones' application the ITU will refuse the application. This notice of refusal will then be communicated by the email list to every international subscriber to the list (private/corporate/government) and will show New Zealand, I suggest, in a disorganized and poor light. (No criticism of Mr. Jones) Should this ENUM 4.6.e164.arpa registration situation then be repeated again and again and again then Kiwis will look like Thanksgiving turkeys. Best regards Michael Sutton ( Previously InternetNZ's ENUM Task Force Chairperson.) http://www.awacs.co.nz (NZNOG conference timing provides conflicts with my current schedule :( ) I suggest Andrew Ruthven and Don Christie from Catalyst be invited to attend any panel session NZNOG has)

3 2

108/8 and 184/8 allocated to ARIN
by Leo Vegoda 04 Jan '09

04 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to ARIN in December 2008: 108/8 and 184/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.9.0.397 wj8DBQFJYcuzvBLymJnAzRwRAiHoAJ9ElxHBdXiQEYcWTE+QMKIA4+0rpwCgmbTy w5fYf3la3xtY5SjT5w+dS/w= =xUKB -----END PGP SIGNATURE-----

1 0

Call for Nominations to the APNIC Executive Council
by Sunny 04 Jan '09

04 Jan '09

_______________________________________________________________________ Call for Nominations to the APNIC Executive Council _______________________________________________________________________ Four positions on the APNIC Executive Council (EC) will be opened for election at APNIC 27 in Manila on Friday, 27 February 2009. The members whose positions are up for reelection are Kuo Wei Wu, Kusumba Sridhar, Mao Wei, and Ming-Cheng Liang, who were all elected at APNIC 24 in Bali on 2 March 2007. Nominations are due by the close of business on Tuesday, 13 February 2009 at the latest (17:30 UTC+10 Brisbane time). Nominees do not have to be representatives of members, but only APNIC members may nominate and vote for candidates. Nominations must be made using the online nomination form which will be available from 5 January 2009: http://meetings.apnic.net/elections/nominate.html If you are unable to vote online or attend APNIC 27, you can still make your vote count by appointing a proxy to represent you at the meeting. Proxy forms are available at: http://www.apnic.net/meetings/proxy.html For more information on nominations received, proxy registration, current EC members, and the role of the EC, please refer to: http://meetings.apnic.net/elections/about/index.html Online voting will be available for this election via the MyAPNIC web site and will open soon after the nomination period closes. Nominees should note that positions on the APNIC EC are currently voluntary and that APNIC may not be able to reimburse EC members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at: secretariat(a)apnic.net. Regards, _______________________________________________________________________ APNIC Secretariat email: secretariat(a)apnic.net http://www.apnic.net sip: info(a)voip.apnic.net phone: +61 7 3858 3100 _______________________________________________________________________

1 0

NRO NC appointments
by Sunny 04 Jan '09

04 Jan '09

______________________________________________________________________ NRO NC appointments _______________________________________________________________________ Dear NZNOG members, The APNIC Executive Council is pleased to announce the appointment of Tomohiro Fujisaki as a representative on the Number Resource Organization (NRO) Number Council (NC) for another year. His term of appointment runs from 1 January 2009 to 31 December 2009. Please note that NRO NC representatives now fulfil the role of ICANN's ASO Address Council. Responsibilities of NRO NC representatives are outlined in the ASO Memorandum of Understanding (MoU) at: http://www.nro.net/documents/aso-mou.html More information on the roles and functions of the NRO and ASO is available at: http://www.apnic.net/community/aso/aso_ac.html _______________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61 7 3858 3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net _______________________________________________________________________

1 0

The New Zealand Network Operators' Group
by Donald Neal 04 Jan '09

04 Jan '09

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 Our next conference is to be hosted by FX Networks in Auckland on 28-30 January 2009. See http://2009.nznog.org/ for more information and to register. 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 around 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

Any Juniper heads out there?
by Nick Larsen 04 Jan '09

04 Jan '09

Hi All, I have a Juniper J2320 running JunOS 9.0 R2.10 Enhanced Services, on which I'm trying to configure as an IKE gateway in hopes that I can connect using NetScreen-Remote or some other IPsec software from various DSL links (Dynamic IKE endpoints and NAT traversal). Is anyone familiar with Juniper and IPsec/IKE? Any tips welcome. Regards, Nick Larsen PS: I have looked at many pieces of documentation, but they're either for static endpoints, or using X-Auth with RADIUS. Or perhaps I'm just being blind.

1 0

Re: [nznog] enum
by James Jones 03 Jan '09

03 Jan '09

On Mon, Jan 5, 2009 at 7:09 AM, James Jones <james(a)freedomnet.co.nz> wrote: > Due to a funds shortage I will not be attending NZNOG09. I really wish > I could go!!! If some how you still wanted to do it I could make > myself available by phone if you guys could find a speaker phone....:) > > On Mon, Jan 5, 2009 at 7:07 AM, Dean Pemberton <nznog(a)deanpemberton.com> wrote: >> Don Gould wrote: >>> >>> How about outlining how you'd like to see the system used in NZ? I would like to see like to see the system being used by providers first. Also I would like to see used by end users, with no restrictions. If you put you number in the registery you need to be able to accept the call from anyone. >>> >>> How about putting a shout out for support for your ideas? It needs to operate like an open source project where we have volenteers that help keep the servers running. It would need take donations for providers and end users possible to help offset server and colo costs. On ther surface I would like to see run like e164.org, but have it a little more robust and production worthy. >>> >>> >>> >>> >> /me puts on his Org Committee hat >> >> I'm sure even at this late stage we could find space for an enum talk or >> panel discussion. >> Is this something that people are interested in? Anyone want to volunteer? >> James are you registered for the conference? >> >> >> Dean >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> > > > > -- > James Jones > Managing Director > Freedom Networks > +64 6 3678300 > +1 413 771 1402 > james(a)freedomnet.co.nz > -- James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Re: [nznog] enum presentation: was: enum
by Ewen McNeill 03 Jan '09

03 Jan '09

In message <4960FAF6.1070202(a)deanpemberton.com>, Dean Pemberton writes: >Don Gould wrote: >> How about outlining how you'd like to see the system used in NZ? >> How about putting a shout out for support for your ideas? > >/me puts on his Org Committee hat >I'm sure even at this late stage we could find space for an enum talk or >panel discussion. The Network Systems Miniconf (one of the tutorials on Wednesday) would be happy to provide time for a enum talk and/or panel discussion if someone would volunteer to lead it off. (The topic seems very relevant to the "layer 7" approach of the miniconf, schedule we are planning is very flexible so we can allow time to discuss the issue in detail.) An offer to lead a session about enum and/or indications that this would be a useful topic welcomed. Details below (as per earlier post); suggestions of other topics also still welcomed. Ewen -=- cut here -=- From: Ewen McNeill <ewen(a)naos.co.nz> To: nznog(a)list.waikato.ac.nz Date: Sat, 20 Dec 2008 14:22:29 +1300 Subject: [nznog] NZNOG 2009 Network Management Miniconf If you've registered for NZNOG 2009 (http://2009.nznog.org/register) you will have seen that we are holding another network administrators miniconf on the Wednesday tutorial day. We'd like to try a different format this year and have a few BoF-style sessions on various ISP systems/network management topics, each with a brief introductory talk followed by an extended discussion period (10-30 minutes depending on interest in the topic). We would like suggestions for topics of interest to anyone planning on coming to the miniconf. We would also welcome any offers to speak for a few minutes (5-15 minutes) on a topic as a lead into discussion. This is your opportunity to find out what your peers at other ISPs have found does or does not work. Some topics that have been mentioned in informal discussion, or happened in previous years: - system configuration automation (puppet, bcfg, cfengine, etc) - system/network monitoring (nagios, etc, especially scalability) - mail systems/spam filtering/webmail But there are plenty of other possible topics so let us know what is relevant to you at present. Please send topic suggestions and offers to talk to: <talks09(a)nznog.miniconf.org> Simon Lyall and Ewen McNeill Network Administrators Miniconf -=- cut here -=-

1 0

Re: [nznog] enum
by James Jones 03 Jan '09

03 Jan '09

oops..sent correction On 2008-12-23, at 09:16, Leo Vegoda wrote: > On 23/12/2008 5:34, "David Farrar" <dpf(a)ihug.co.nz> wrote: > >> There's been some discussions and trials in the past between >> InternetNZ and the Telco Carrier Forum. As far as I know there are no >> current plans to delegate the domain. >> >> It is worth noting that the ITU will only delegate the domain if >> instructed to by the MED, so the MED would need to be satisfied with >> whomever is proposed to operate it. > > I suppose we'll find out soon enough: > > http://www.ripe.net/maillists/ncc-archives/enum-announce/2008/msg00011 > .html Impressive nameserver diversity in that proposal: nserver: enum1.freedomnet.co.nz nserver: enum1.freedomnet.co.nz Joe _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog -- James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

24 47

Re: [nznog] enum
by James Jones 03 Jan '09

03 Jan '09

I am trying as much info as posibble. I would like to see open enum system, in which anyone can register their numbers. I would like to see it back by providers as well. I really don't want anything in return, execcpt to able to have cheaper call routing for everyone. Steve I can understand your dubiousness in regards to the application. I am not trying to hide anything. Also to clarify, I am a contractor for ALU, but I am not tied Telecom. -----Original Message----- From: "Steve Phillips" <steve(a)focb.co.nz> To: "nznog" <nznog(a)list.waikato.ac.nz> Sent: 1/5/09 1:45 AM Subject: Re: [nznog] enum Don Gould wrote: > I'm sorry but I really feel a call to order is required here! Certainly. > I've read over half the posts in this thread and see no reason for false > accusations. False accusations ? the thing I'm finding is that people are asking for more information and we are getting 'yes yes, we will give you the information if you ask for it !' which isn't actually giving anyone anything about the intentions behind the application. This is very typical of commercial entities (and infact, anyone trying to divert attention away from something) when they are about to do something that will not necessarily be in the publics best interest. This has been an exceedingly common tactic in the NZ Internet industry since it started. The lack of any positive from JONES JAMES F and the ability to silently sidestep any real questions on his companies intentions for the enum allocation raise warning bells in my mind. I guess you've got a different outlook. Good for you, at least you're still smiling as you get shafted. > How about outlining how you'd like to see the system used in NZ? I really don't think it will ever get used, which is probably for the best. I also think allocating/activating it with no set plan as to how this is going to be implemented is dangerous. All it would take is a reasonably large carrier (verizon ? etc..) to perform a lookup, get a response and incorrectly route a call and you'd end up with chaos (keeping in mind that this is _supposed_ to be an official way route PSTN allocated numbers via IP). How are number allocations going to be handled ? how about coping with number portability ? do we sub delegate based on the NAD ? if the NAD has control then why is a private/commercial entity looking after the allocation ? is this entity going to charge to gain access to this system (even tho its open ! yay for word games) and if so, how much and will any charges slow adoption ? oh, and answering Craigs questions would also be nice. > How about putting a shout out for support for your ideas? I dont have any ideas other than 'it should be allocated to the MED/DNC/Peter Mott in order to stop this sort of thing from happening. > Seems to me that there are people here who are just jealous that > someone's trying to do something with this enum stuff. Yup, what a wonderful conclusion you've come to. I'd just like to make sure that a system such as enum, that is seen as a standard (with a low uptake, granted) does not fall in to the hands of some crowd that will in all likely-hood exploit it to make $$, prove to me that this is NOT the case and i'll happily shut up. (and yeah, I know there are checks around the allocations and I would _hope_ that they all work swimmingly, but call be a skeptic - especially when there are names such as Alcatel-Lucent and Telecom NZ behind the application based on the original e-mail sent to the list) > How about getting this thread moving back in a positive direction rather > than a pointless flame?! I find anything questioning why a public standard falls under the control of an unknown commercial entity, in order to line someones pockets, to have a reasonably valid point. If you see this as being pointless, then feel free to use your delete button or ignore the thread. I know, doom and gloom - but I have yet to meet anyone that can predict the future and looking back after the fact and saying 'oops, we maybe shouldn't have done that' doesn't really help things move forward. The NZ Internet industry has done that too often in the past, why are we doing it again now ? -- Steve.

1 0

Report on IPv4 address list
by Ian McDonald 02 Jan '09

02 Jan '09

Thought this might interest a few people: http://arstechnica.com/news.ars/post/20090102-the-year-in-ipv4-addresses-al… -- Web: http://wand.net.nz/~iam4/, http://www.jandi.co.nz Blog: http://iansblog.jandi.co.nz

2 1

VoIP Peering - was Re: enum
by Richard Naylor 30 Dec '08

30 Dec '08

At 08:52 a.m. 31/12/2008, Scott Howard wrote: >Eventually something is going to be needed to allow for optimal >routing between the multitude of VOIP providers - be that enum or >something else... OK lets cut to the guts of the problem. How do we get VoIP peering sooner rather than later ? Tomorrow, yet another year will have passed. Progress starts today. Assumption 1 - The big T(s) make about 50% of revenue off the PSTN equivalent to about $2.5B, so don't expect any co-operation. Assumption 2 - it has to be neutral - the Govt should NOT be involved. Of course they are welcome to peer, in fact its a surprise that Govt depts don't have inter-Dept peering already, its a bit of a no brainer for them. Maybe GSN was going to get there...... Assumption 3 - it has to be simple, so that VoIP providers and end users can get involved. (besides I'm on holiday and my horizons are sleep, food and beer) Assumption 4 - It should be distributed and scaleable.. (are you peering with your city, your region, your country or the World ?) So we need something NOW, that can be migrated if required. But we shouldn't be waiting on committees or politicians. Richard

4 3

Re: [nznog] enum
by Michael Sutton 29 Dec '08

29 Dec '08

I would suggest that NZNOG community read InternetNZ's ENUM archive there are two major ENUM related reports as well as an Open Source Software that InternetNZ released. I enclose some links to downloads and documents I refer to (see below). ENUM should be activated for New Zealand as it is an enabler which permits systems and network developers to utilize ENUM in a transparent way to the end user but which enhances the phone address lookup and uses the DNS which is already globally implemented. Note The ENUM system also enables PSTN numbers to be entered and used (subject to the rules of the Registry). Here's some points: 1. While an InternetNZ Councilor from 2003 - July 2007* and as Chair of the ENUM Task force I advocated for ENUM to be fast tracked and activated with a Personal User Agent software (UCI PUA service). ENUM has however been frozen since 2006 by agreements between MED, TCF and InternetNZ to delay ENUM which IMHO does not support our interest's of choice through ENUM operation and access. 2. In my opinion the MED should be required by Government to request delegation of 4.6.e164.arpa (ENUM) unto itself. MED should host ENUM on trial servers on their own ip address space which should be used for boot-strap testing and which can then be transitioned with technical delegation, operation and policy being determined on a fast track basis. The Government should include in the MED's key performance indicators measurements to incentivise their role in the implementation of ENUM for New Zealand. 3. There were discussions resulting in the current situation but there has been no ENUM Trial between InternetNZ, the TCF, NAD and MED. 4. In 2005 InternetNZ as part of the then ENUM initiative and research - INZ funded a UCI, PUA, ENUM (ETSI EG 284 004) software prototype which was developed by CatalystIT (extreme programming - shouts to AndrewR) which used the ENUM directory system, but the trial did not activate the 4.6.e164.arpa delegation, which it would in practice, or trial an ENUM authorization and registration process. In connection with this work: The final version ETSI EG 284 004 in September 2007 recommendations stated that UCI & PUA will use the public ENUM e164.arpa as a global directory. The work of InternetNZ and CatalystIT in New Zealand was recognized in reports on this matter to the European Commission and was used during the development of the final ETSI Guide/Standard which was approved in Europe by vote in 2007. The APEC Business Advisory Council's Report to the APEC Leaders in Bussan also included direct reference to this work. Note PUA is a Personal User Agent routing firewall system for client of isp telco services and UCI is an opt-in Universal Communications Identifier. Recently an Italian company undertaking a research and development contract for communication services for blind people (was contracted by the Italian Ministry of Science to implement a system using UCI PUA ENUM) communicated and requested access to InternetNZ's reports and the open source program code that InternetNZ released. 5. InternetNZ has $20,000 allocated for ENUM in the current place holder budget. 6. The ITU will not approve the ENUM delegation application of James Jones as the MED will not send a letter of endorsement to the ITU in support of this application - or will they. Regards Michael Sutton http://www.awacs.co.nz http://www.internetnz.net.nz/proceedings/tf/archive/enum http://www.internetnz.net.nz/proceedings/tf/archive/enum/pua-uci-feasibility -1-1-4-smaller.pdf http://www.internetnz.net.nz/proceedings/tf/archive/enum/Complete%20Enum%20T rial%20Report%20040705.pdf http://www.internetnz.net.nz/proceedings/tf/archive/enum/enumback.html * resigned.

3 3

Alternative Accommodation for NZNOG09
by Skeeve Stevens 25 Dec '08

25 Dec '08

Hey all, Just tried to book a room at Mount Richmond Hotel & Conference Centre (did people realise they only had 44 guest rooms?) and they are fully booked out on 29/1/09 to 30/1/09. I don't know the geography well, but I am wondering if anyone knows anywhere that is close to the venue? ...Skeeve -- Skeeve Stevens, CEO eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there?

2 3

enum
by JONES JAMES F 22 Dec '08

22 Dec '08

Is anyone doing anything with 4.6.e164.arpa domain? James Jones

6 6

Re: [nznog] enum
by lenz 22 Dec '08

22 Dec '08

from what i've seen in europe the registries love it and the users don't really take it. the main problem i've seen there is that the validation process is way too complicated for the normal domain registrar and the customer. the registration numbers in germany and austria are not too impressive either. the swiss guys killed their enum project afaik. cheers lenz > > On Tue, Dec 23, 2008 at 12:56 PM, Nathan Ward <nznog(a)daork.net> wrote: > >> On 23/12/2008, at 12:44 PM, JONES JAMES F wrote: >> > Is anyone doing anything with 4.6.e164.arpa domain? >> > >> http://www.internetnz.net.nz/projects/enum/index.html >> >> Seems to me that it could tie in to TUANZ/INZ stuff. >> >> I'd question whether it's worthwhile going through all the >> bureaucratic nightmare to get a limited lifetime bridge between the >> PSTN and the Internet. >> Why not just use SIP URIs? >> >> -- >> Nathan Ward >> >> >> >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> > >

1 0

NZRR Route Registry Update
by NZRR Database Notifications 22 Dec '08

22 Dec '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:AS64526 descr: Route set for Infometrics - AS64526 members: 210.48.109.80/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030717 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64526 descr: advertised to AS9439 by Infometrics Ltd / Gareth Morgan Investments - AS64526 members: 210.48.110.0/26^26-29, 210.48.109.80/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mike(a)gmi.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081223 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 22 Dec '08

22 Dec '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:AS38294 descr: Route set advertised to AS24388 by ServerWorks Ltd - AS38294 members: 202.124.127.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: russell(a)serverworks.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070608 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS38294 descr: advertised to AS24388 by Serverworks Ltd - AS38294 members: 113.130.120.0/22^22-29, 202.124.127.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: russell(a)serverworks.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081223 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 22 Dec '08

22 Dec '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:AS38451 descr: Route set advertised to AS9560 by SMX - AS38451 members: 203.84.134.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: leon.strong(a)smx.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38451 descr: advertised to AS9560 by SMX Ltd - AS38451 members: 113.197.64.0/22^22-29, 203.84.134.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: leon.strong(a)smx.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081223 source: NZRR ------------------------------------------------------------

1 0

APE content on GigE
by Barry Murphy 21 Dec '08

21 Dec '08

Afternoon to those still at work this week... Is anyone aware of content off APE that's on GigE? Are the ftp.citylink.co.nz servers on GigE? I'm just trying to gauge what the quickest theoretical speed one could get of APE if connected at gigE. Cheers Barry Murphy P.s. for those on holiday, enjoy your beer and time off.

2 1

NZRR Route Registry Update
by NZRR Database Notifications 21 Dec '08

21 Dec '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081222 source: NZRR ------------------------------------------------------------

1 0

Very funny xtra bound mail (yahoo) goes via another provider
by Barry Murphy 19 Dec '08

19 Dec '08

Heya, While drinking beer and playing with the routing table, i notice that mail destined for Xtra: xtra.co.nz. 799 IN MX 20 mx2.tnz.mail.yahoo.com. xtra.co.nz. 799 IN MX 10 mx1.tnz.mail.yahoo.com. Now goes via Vocus, a new operator selling international bandwidth in NZ: root(a)accounting:/home/icepick# traceroute mx1.tnz.mail.yahoo.com traceroute to mx1.tnz.mail.yahoo.com (124.108.96.67), 64 hops max, 40 byte packets 1 FIREWALL (60.234.66.130) 0.433 ms 0.630 ms 0.389 ms 2 * * * 3 * * * 4 vocus.ape.net.nz (192.203.154.123) 2.029 ms 1.840 ms 3.055 ms 5 ip-42.192.31.114.vocusconnect.net.au (114.31.192.42) 25.294 ms 25.707 ms 26.766 ms 6 as17457-1.bdr02.syd01.nsw.vocusconnect.net.au (114.31.200.38) 26.161 ms 26.152 ms 26.022 ms 7 gi1-2.bas2.aue.yahoo.com (203.84.216.202) 26.164 ms gi1-1.bas1.aue.yahoo.com (203.84.216.198) 26.283 ms 26.306 ms I find it great that xtra bound MX traffic is now "Local" again as it transits APE, but I find it funny that it's another operator supplying the bandwidth rather than telecom. I know this may not be news to everyone yet, and yes, it's not the first time I've mentioned (1) vocus in the last week, but from what I can tell they seem to be doing a good job for the NZ internet so far. (1) I'm in no way affiliated to vocus. Cheers Barry P.S. my views are mine only and not those of my employer, * insert rest of disclaimer here *...

5 7

xtra tedium.
by Steve Holdoway 19 Dec '08

19 Dec '08

Is there anyone from xtra/yahoo who reads this list? I've run out of things that I can do to get your servers to accept my mail. This is what I get, and trying to follow up using the case number supplied just leads to another copy of the FAQ automatically sending to me. It's *always* mx2.tnz.mail.yahoo.com that does this to me, mx1 seems quite happy. Dec 20 16:10:06 server sendmail[15781]: mBK3A4JE015618: to=<recipient(a)xtra.co.nz>, ctladdr=<steve(a)greengecko.co.nz> (1018/1018), delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=128042, relay=mx2.tnz.mail.yahoo.com. [124.108.96.67], dsn=4.0.0, stat=Deferred: 421 Message from (210.5.53.81) temporarily deferred - 4.16.50. Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html All the recommendations - PTR, SPF, DKIM, no html, etc have been followed. I'm starting to believe that it's this server that is plain misconfigured. Steve -- Steve Holdoway <steve(a)greengecko.co.nz>

2 1

NZNOG 2009 Network Management Miniconf
by Ewen McNeill 19 Dec '08

19 Dec '08

If you've registered for NZNOG 2009 (http://2009.nznog.org/register) you will have seen that we are holding another network administrators miniconf on the Wednesday tutorial day. We'd like to try a different format this year and have a few BoF-style sessions on various ISP systems/network management topics, each with a brief introductory talk followed by an extended discussion period (10-30 minutes depending on interest in the topic). We would like suggestions for topics of interest to anyone planning on coming to the miniconf. We would also welcome any offers to speak for a few minutes (5-15 minutes) on a topic as a lead into discussion. This is your opportunity to find out what your peers at other ISPs have found does or does not work. Some topics that have been mentioned in informal discussion, or happened in previous years: - system configuration automation (puppet, bcfg, cfengine, etc) - system/network monitoring (nagios, etc, especially scalability) - mail systems/spam filtering/webmail But there are plenty of other possible topics so let us know what is relevant to you at present. Please send topic suggestions and offers to talk to: <talks09(a)nznog.miniconf.org> Simon Lyall and Ewen McNeill Network Administrators Miniconf

1 0

Do you grok DNSSEC?
by Sam Sargeant 18 Dec '08

18 Dec '08

Hi all. There are two conferences coming up early next year that have a track on DNSSEC. Both NZNOG and APRICOT are looking to find people who have experience and would be happy to share their thoughts. My feeling is that actual use in .nz is small however I'd love to hear from you if there's something you've done with DNSSEC. Ideally we'd like people who are willing to talk in Manilla or Auckland but even just a few shared thoughts are appreciated. http://2009.nznog.org/ http://apricot2009.net/ BTW, registrations are open for both. Register now! :) Sam.

6 5

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '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:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '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:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.254.0/23^23-29, 202.53.189.0/28^28-29, 161.29.126.128/29, 161.29.192.160/29, 161.29.193.80/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.192.160/29, 161.29.193.80/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Dec '08

18 Dec '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 Limited - 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.193.144.0/21^21-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.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.46.189.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081204 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - 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.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.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.46.189.0/24^24-29, 202.49.140.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.129.253.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR ------------------------------------------------------------

1 0

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

17 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR ------------------------------------------------------------

1 0

IPv6 Steering Group Technical SIG - Announcement/Invitation
by Dean Pemberton 17 Dec '08

17 Dec '08

A workshop at held at InternetNZ on the 28 November in Wellington saw the formation of a New Zealand IPv6 Steering Group. This group includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. The members of this steering group consist of invited senior representatives from the following organisations: InternetNZ TUANZ ISPANZ Telecommunications Carriers Forum Digital Development Forum Telecom TelstraClear WorldXChange Orcon FX Networks REANNZ Canterbury Development Corporation Kordia Cisco Vodafone Juniper Networks Alcatel Lucent Braintrust This steering group will primarily be concerned with high level discussion regarding the deployment of IPv6 within New Zealand. The steering group will not necessarily be a place where technical discussion takes place. As with so many things these days, a combination of business and technical expertise must be bought together to solve a given problem. To this end at the same workshop a Technical Special Interest Group (TechSIG) was also established. The goals of this group are: . To act as a central point for IPv6 technical discussion within the New Zealand Internet community. . To identify to the IPv6 Steering Group any business related barriers to IPv6 deployment which have been identified by the SIG's technical contributors. . To comment and provide potential solutions to technical related barriers identified by members of the IPv6 Steering Group. . To stimulate the production of relevant technical documentation. The co-conveners of this group are Andy Linton Nathan Ward Brian Carpenter Dean Pemberton A mailing list has been created and membership is open to all interested parties. Subscription details can be found at the link below; http://listserver.internetnz.net.nz/mailman/listinfo/ipv6-techsig I would encourage anyone who has an interest in the deployment and growth of IPv6 to join and contribute to the list. Please do not feel that this is a 'Networking Specialist Only' list. The deployment of IPv6 (and depletion of IPv4) has just as significant an impact on system administrators and content/application providers as it does on network administrators. I welcome all technical viewpoints onto the list. Thank you for your time. Dean Pemberton (Co-convener, IPv6 Steering Group Technical SIG)

1 0

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

17 Dec '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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 122.102.108.0/22^22-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.205.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.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 20081121 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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-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, 203.84.134.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.49.141.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 20081219 source: NZRR ------------------------------------------------------------

1 0

Microsoft releasing emergency patch for perilous IE flaw
by Dean Pemberton 16 Dec '08

16 Dec '08

Interesting reading. http://news.yahoo.com/s/afp/20081216/ts_alt_afp/uschinaitinternetsoftwarecr… Microsoft will release an emergency patch on Wednesday to fix a perilous software flaw allowing hackers to hijack Internet Explorer browsers and take over computers. The US software giant said on Tuesday that in response to "the threat to customers" it immediately mobilized security engineering teams worldwide to deliver a software cure "in the unprecedented time of eight days." According to researchers at software security firm Trend Micro, attacks based on the vulnerability in the world's most popular Web browser are spreading "like wildfire" with millions of computers already compromised.

1 0

FW: Media Release - Industry agrees - IPv6 transition plan needed
by Mark Foster 16 Dec '08

16 Dec '08

This just came to my attention... Industry agrees - IPv6 transition plan needed Media Release - 15 December 2008 Following a workshop convened by the Ministry of Economic Development, major ICT industry and stakeholder organizations have agreed on the need for New Zealand to develop a transition plan from IPv4 to IPv6, the next generation Internet addressing protocol. The transition plan will include education, and identification and removal of roadblocks to IPv6 deployment. There is growing urgency for the Internet to support both IPv4 and IPv6, which together will offer vastly increased resources. More than one million new devices connect to the Internet every week and the pool of four billion IPv4 addresses is expected to be exhausted by 2010. IPv6 supports a much larger pool of addresses, enough to assign an IP address to each grain of sand in a fine layer covering the entire planet. Internet advocacy group InternetNZ, a key sponsor of IPv6-related initiatives in New Zealand, has agreed to provide continued support for furthering IPv6 as a national industry initiative under the auspices of the Digital Development Forum. The forum is a multi-stakeholder initiative designed to promote New Zealand's transition into the digital economy. The workshop was held on 28 November in Wellington and saw the formation of an IPv6 Steering Group, which includes representatives from telecommunications carriers, internet service providers, ICT vendors, and industry and user associations. A complete list of stakeholder organizations is included at end of this release. Telecommunications industry consultant Dr Murray Milner has been confirmed as independent convenor for the steering group. Milner says IPv6 provides much more flexibility in allocating addresses, and will allow Internet growth in New Zealand to keep pace with the expected worldwide trend. InternetNZ Executive Director Keith Davidson says the initiative is more than welcomed and indicates increasing recognition that IPv6 deployment will be a business-critical issue as IPv4 exhaustion looms. While this is not a Y2K scenario, unless New Zealand has a clear plan for the introduction of IPv6 then there is an increased risk of Internet black holes developing. "This may mean that communication via the internet may not be possible in the near future between parts of New Zealand's IPv4-based Internet and certain developing countries such as China and India, where IPv6-only Internet infrastructure is currently being deployed," says ISPANZ President Jamie Baddeley. Digital Development Council Executive Director Paul Alexander points out that it is not time to panic but it is time for the ICT industry to get organised and reach out to the wider business community to explain the issue. CEO of the Telecommunications Carrier's Forum Ralph Chivers says that progress can only be made with a co-coordinated and concerted effort across the ICT sector to ensure New Zealand has a timely and trouble-free transition to IPv6. IPv6 was highlighted in Digital Strategy 2.0, which mirrored the growing urgency expressed in global ICT technical forums on the need for leadership amongst key industry stakeholders in transitioning to IPv6. IPv4 was deployed in the mid 1980's, at a time when billions of Internet connections were never contemplated. IPv6 has been under development since the mid 1990's, and currently exists in small pockets around the world. TUANZ Chief Executive Ernie Newman says that users welcome the initiative and that TUANZ stands ready to take an active part in educating users once equipment suppliers and the registry have ensured they are fully prepared and have clarified the major steps users need to take. Next steps include development of a technical education plan to stimulate IPv6 skills in New Zealand's ICT and academic sectors. This will be followed by development of a roadmap for the deployment of IPv6 for New Zealand and a business sector outreach programme. A national IPv6 Hui anticipated for September 2009 is also planned. For more information contact: Murray Milner Independent Convenor IPv6 Steering Group 027 443 0120 murray.milner(a)xtra.co.nz Keith Davidson Executive Director InternetNZ 021 377 587 exe.dir(a)internetnz.net.nz Industry organizations supporting the need for a transition plan to IPv6: * InternetNZ * TUANZ * ISPANZ * Telecommunications Carriers Forum * Digital Development Forum * Telecom * TelstraClear * WorldXChange * Orcon * FX Networks * REANNZ * Canterbury Development Corporation * Kordia * Cisco * Vodafone * Juniper Networks * Alcatel Lucent * Braintrust

15 27

Vendor Reception at NZNOG09
by Nathan Ward 15 Dec '08

15 Dec '08

Hi all, At NZNOG09 in January we are intending on trying something a little new - having a "Vendor Reception" on the Wednesday evening. This is to give vendors the chance to meet people with glossy pieces of paper handy, and also to encourage the social aspect of the conference and networking with industry peers. The format of this is roughly: - Vendors/someone wanting to sell something sets up some sort of stand, table, demo, whatever[1] around a room/pool. - Vendor swag encouraged[2]. - Open bar, possibly dinner depending on numbers and budget. - Informal. We may do a bit at some point early in the evening where vendors can stand up and read out a short[3] personals ad - we'll decide how that goes closer to the time based on how many people are interested in participating and exhibiting, and other arbitrary criteria we have yet to invent. This will be open to sponsors automagically. Non-sponsors can participate, and would be asked to contribute to offset the cost of drinks and food for the evening. Please contact me on nznog(a)daork.net if you're interested in exhibiting. Cheers! -- Nathan Ward [1] Jonny "Mr Marketing" Martin suggests a bar leaner with a bottle of some premium liquor. [2] Those FX coffee mugs from 2002 or whenever it was were great, I still use mine but I feel it's time for a change. Hint hint. [3] "Short": adjective. An arbitrary period of time in minutes counted on one hand.

1 0

Telstraclear datacentre offline?
by Joel van Velden 15 Dec '08

15 Dec '08

Hi Can anyone else confirm that the telstra clear north shore datacentre is offline? Last hop to our box or www.telstraclear.co.nz is: ge-9-0-927.u11.telstraclear.net Have obviously tried from more than one ISP :) -Joel

4 3

NZNOG09 Fellowships
by Jonny Martin 15 Dec '08

15 Dec '08

Hi All, NZNOG09 is being hosted by FX Networks at the Mount Richmond Hotel and Conference Centre in Mt. Wellington, Auckland from Wednesday 28 to Friday 30th January, 2009. Following on from the successful fellowship program offered last year there will once again be a small number of fellowship packages available. Fellowships are open to all - employed, unemployed, students, programmers. The aim of this is to provide assistance to those people that mightn't otherwise be able to come - but have a lot to offer to, or gain from, the NZNOG community. Fellowships will cover conference and tutorial registration fees, and up to three nights accommodation at the NZNOG venue. Travel assistance may be considered if applicants are able to provide solid justification for why it would be needed. Up to five fellowship packages are being made available. Applicants must: - Write a few paragraphs explaining why they need a fellowship to NZNOG'09 and what they hope to get out of it. - Their employer can't or won't cover them and they're having to cover costs personally or they're a student / unemployed. - Demonstrate a history of involvement in some aspect of the NZNOG community or an intent to become involved, and how attending NZNOG'09 will benefit them. - Actually attend the NZNOG sessions! Fellowship prospects will be helped greatly if applicants are presenting, or intend to present a conference paper, lightning talk, convene a BOF, or otherwise contribute to the conference. Submissions will be evaluated by the NZNOG 2008 organising committee. We need to be satisfied that there is a legitimate need for the fellowship. Email your submissions to talks(a)nznog.org - and while you are there, why not tell us about the talk/lightning talk/BOF you wish to provide... Closing date for applications Monday 15th December Successful applicants will be notified by Wednesday 17th December. Cheers, Jonny.

1 1

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

14 Dec '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:AS4826 descr: Route set advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 113.20.0.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: macca(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - AS4826 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, 115.187.128.0/17^17-29, 113.192.0.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.161.64.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.32.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.14.32.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.89.64.0/19^19-29, 203.145.32.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 116.213.32.0/20^20-29, 117.55.224.0/20^20-29, 119.15.96.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.88.112.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.193.176.0/21^21-29, 116.212.64.0/21^21-29, 119.31.232.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.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.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 125.254.112.0/22^22-29, 140.200.248.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.33.116.0/22^22-29, 203.62.184.0/22^22-29, 203.79.16.0/22^22-29, 203.92.28.0/22^22-29, 203.161.128.0/22^22-29, 203.161.140.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.184.0/22^22-29, 203.185.228.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.211.56.0/22^22-29, 59.86.160.0/23^23-29, 63.218.156.0/23^23-29, 74.80.126.0/23^23-29, 114.111.132.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.160.230.0/23^23-29, 122.100.6.0/23^23-29, 122.100.8.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.6.42.0/23^23-29, 202.12.90.0/23^23-29, 202.36.204.0/23^23-29, 202.92.94.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.90.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.79.88.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.161.134.0/23^23-29, 203.161.136.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 203.185.226.0/23^23-29, 206.222.230.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.59.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.122.132.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.124.0/24^24-29, 203.4.154.0/24^24-29, 203.5.45.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.16.243.0/24^24-29, 203.17.4.0/24^24-29, 203.17.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.28.14.0/24^24-29, 203.29.0.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.230.0/24^24-29, 203.63.3.0/24^24-29, 203.63.67.0/24^24-29, 203.79.20.0/24^24-29, 203.92.25.0/24^24-29, 203.96.157.0/24^24-29, 203.98.81.0/24^24-29, 203.111.63.0/24^24-29, 203.111.105.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.185.225.0/24^24-29, 203.190.217.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.0/24^24-29, 4.53.16.144/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tech(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081215 source: NZRR ------------------------------------------------------------

1 0

Anyone got a WiSpy in Auckland?
by Nathan Ward 14 Dec '08

14 Dec '08

Hello all, I need to go do a spectrum sweep of the venue for NZNOG09, so that we can figure out what frequencies we can use, and any problems we're going to run in to. Is there someone who has one of these in Auckland and can lend it to me for an afternoon? Will pay in beer at the conference :-) -- Nathan Ward

1 0

NZNOG 2009 - air travel to Auckland
by Alastair Johnson 13 Dec '08

13 Dec '08

With NZNOG just around the corner, I noticed that Air New Zealand currently has a sale on for domestic travel... including for people who need to get to Auckland in late January. The sale ends on Wednesday. It might be worth looking into this if you're coming up to NZNOG - and I hope you are. http://www.airnewzealand.co.nz/airfares_offers/hotdeals/hot_deals_fares/che… aj (apols for the somewhat OT post, but I think this will be useful to some)

1 0

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

10 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081212 source: NZRR ------------------------------------------------------------

1 0

vector faults on aucklands north shore (albany)
by Craig Spiers 10 Dec '08

10 Dec '08

Hi All, Can anyone shed any light on who the service provider is that has looped their service provider ports off the albany vector switch twice in the last week? They are causing a broadcast storm which is taking out the network in the greater north shore area. Come on guys!!! #!@#!@#$@%$@ Cheers craig - solarix

1 0

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

10 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR ------------------------------------------------------------

1 0

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

10 Dec '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:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081211 source: NZRR ------------------------------------------------------------

1 0

Christchurch City ~2.08 to 2.28 GHz Range
by James Wix 08 Dec '08

08 Dec '08

Morning all, Has anyone in the CHCH region happened to have turned on some gear in the around 2.1 - 2.28 GHz spec over night? If you have could you contact me off list please. Beer etc. James DDI. +64 9 916 6512 | M. +64 21 226 6048 | F. +64 9 916 6404 E. james.wix(a)kordia.co.nz | W. www.kordiasolutions.com This email and attachments: are confidential; may be protected by privilege and copyright; if received in error may not be used, copied, or kept; are not guaranteed to be virus-free; may not express the views of Kordia™; do not designate an information system; and do not give rise to any liability for Kordia™.

1 0

APNIC Member and Stakeholder survey
by Elly Tawhai 07 Dec '08

07 Dec '08

_______________________________________________________________________ Member Survey 2009 - Have Your Say! _______________________________________________________________________ Hi NZNOG Community, APNIC will be conducting a member and stakeholder survey from 8 December 2008 to 9 January 2008 to assess the performance and development of APNIC. As a valued stakeholder in the Asia Pacific region, your opinion helps shape the future direction of APNIC therefore, on behalf of APNIC, I would to personally invite you to participate in this survey. The survey is conducted in three parts: - an assessment of APNIC performance, - where APNIC member revenue should be invested, and - IPv6 readiness in the Asia Pacific region. The survey is conducted independently by KPMG and the process is entirely neutral, guaranteeing the highest quality result. The feedback from the survey will directly inform APNIC activities so we strongly encourage you to participate. The survey should take you no more than 20 minutes to complete and is open to all stakeholders (members and non-members). Those who complete the survey will be in the draw to win: - one of two ASUS Eee PCs, or - an iphone. For more information on how you can participate in the survey visit: http://www.apnic.net/survey/2009 Kind regards, Elly APNIC

1 0

Palmerston North 5.8Ghz
by Dave Mill 04 Dec '08

04 Dec '08

Hi there If anyone is operating in, or in particular, making changes to the 5.8Ghz wireless space in Palmerston North could they please contact me offlist. Cheers Dave @ InSPire

1 0

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

03 Dec '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 Limited - 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.193.144.0/21^21-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-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, 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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - 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.193.144.0/21^21-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.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.46.189.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081204 source: NZRR ------------------------------------------------------------

1 0

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

03 Dec '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:AS23838 descr: Route set advertised to AS9560 by Solarix - AS23838 members: 120.136.48.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig.spiers(a)solarix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080512 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23838 descr: advertised to AS9560 by Solarix Limited - AS23838 members: 120.136.48.0/21^21-29, 113.21.224.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: craig.spiers(a)solarix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081204 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 02 Dec '08

02 Dec '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 Limited - 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.193.144.0/21^21-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, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - 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.193.144.0/21^21-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-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, 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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 02 Dec '08

02 Dec '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, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081124 source: NZRR REPLACED BY: 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, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081203 source: NZRR ------------------------------------------------------------

1 0

DSL Wholesale in NZ
by Skeeve Stevens 30 Nov '08

30 Nov '08

Hey all, Here in Australia getting a handoff from a wholesale ISP who will deliver DSL tails as L2TP is an easy thing. Taking them as L2TP allows you to do lots of cool things like put the services in MPLS VRF's and so on. I need to know if this is possible in NZ. What I am looking for is a provider that can deliver national coverage, and can provide a handoff back in Auckland. We're only talking a small number of tails... i.e. <100 initially as this is for a private corporate network. The handoff would be in the SkyTower then at which point I will get an international VLAN back to Sydney to plug them into the corporate network over here. There may or may not be the requirement for some transit in NZ... I haven't decided exactly how I am doing some parts of the solution yet... but for now we can assume that there will be none - but we may do peering. I am sure there are many hosted/managed options, but I'd prefer to take handoff of the services into my own router... Cisco 2821/3845 or something and then take care of everything ourselves. Any thoughts please let me know. ...Skeeve -- Skeeve Stevens, CEO eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there?

2 2

NS7 .nz Name Server Replacement
by DNS 30 Nov '08

30 Nov '08

Over the last few weeks the New Zealand Registry Service (NZRS), has been working on the changes required to replace the .nz name server operated by Telecom (NS7.DNS.NET.NZ) with a new server operated and managed by the NZRS. The changes for the replacement server are now complete and the new server is in operation. The new IP address (202.46.188.130) for NS7 has been made to the root servers by IANA. There is no impact on the .nz DNS as a result of the change. This change is one of several that NZRS is undertaking as part of a project to make improvements to the .nz DNS infrastructure. Dave Baker .nz Registry Services (NZRS)

1 0

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

30 Nov '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 Our next conference is to be hosted by FX Networks in Auckland on 28-30 January 2009. Registration is now open. For more information see http://2009.nznog.org/ . 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 around 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

Re: [nznog] Xtra are broked
by Spirit Wireless 28 Nov '08

28 Nov '08

Anyone know the geographical extent of the outage it all died here in Katikat at 2208pm no PPP. Dreadful customer service. No notice and no advice during outage. Maurice -----Original Message----- From: nznog-request(a)list.waikato.ac.nz [mailto:nznog-request(a)list.waikato.ac.nz] Sent: Saturday, 29 November 2008 12:00 p.m. To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 71, Issue 22 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. Xtra are Broked... (Mark Foster) 2. Re: Xtra are Broked... (Bill Walker) 3. Re: Xtra are Broked... (Kyle Carter) 4. Re: Xtra are Broked... (Mark Foster) 5. Re: Xtra are Broked... (Philip Seccombe) ---------------------------------------------------------------------- Message: 1 Date: Fri, 28 Nov 2008 21:53:25 +1300 (NZDT) From: Mark Foster <blakjak(a)blakjak.net> Subject: [nznog] Xtra are Broked... To: NZNOG(a)list.waikato.ac.nz Message-ID: <Pine.LNX.4.64.0811282152100.2262(a)skyhawk.blakjak.net> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > www.xtra.co.nz Server: alien.xtra.co.nz Address: 202.27.184.3 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to alien.xtra.co.nz timed-out At this point in time noone i've spoken with appears to be able to talk DNS to Xtra, which is having flow on effects as you may imagine (i.e. MX records aren't being supplied). A headsup for those who havn't already noticed. Mark. ------------------------------ Message: 2 Date: Fri, 28 Nov 2008 22:43:17 +1300 From: Bill Walker <Bill.Walker(a)staff.snap.net.nz> Subject: Re: [nznog] Xtra are Broked... To: "NZNOG(a)list.waikato.ac.nz" <NZNOG(a)list.waikato.ac.nz> Message-ID: <450C73DF8617BA44AA8BE812B3E921AC03F7293CAD(a)TOM.staff.snap.net.nz> Content-Type: text/plain; charset="us-ascii" All traffic dropped off at 9pm, DNS disapeared and so did their routes. We've been trying to get hold of Telecom by phone and email, no luck so far. Broadband users are still connected, but if they disconnect they can't reconnect. Cheers, Bill ________________________________________ From: Mark Foster [blakjak(a)blakjak.net] Sent: Friday, 28 November 2008 9:53 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] Xtra are Broked... > www.xtra.co.nz Server: alien.xtra.co.nz Address: 202.27.184.3 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to alien.xtra.co.nz timed-out At this point in time noone i've spoken with appears to be able to talk DNS to Xtra, which is having flow on effects as you may imagine (i.e. MX records aren't being supplied). A headsup for those who havn't already noticed. Mark. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.10/1813 - Release Date: 27/11/2008 9:02 a.m. ------------------------------ Message: 3 Date: Sat, 29 Nov 2008 09:42:08 +1300 From: "Kyle Carter" <kyle(a)feet.net.nz> Subject: Re: [nznog] Xtra are Broked... To: <NZNOG(a)list.waikato.ac.nz> Message-ID: <3AB24E0C024548EAA59D8671AA6C5E29(a)Game> Content-Type: text/plain; charset="us-ascii" Telecom sure had issues last night My dsl wouldn't pass any traffic, and then after rebooting the dsl modem I couldn't get any PPP. Im back online now (after giving up and going to bed), but couldn't get hold of anyone on the xtra helpdesk. Trying to contact them resulted in dropped calls, or beeping (as in no such extension) after being forwarded from the 'some xtra users are having issues surfing websites' message.. Xtras website I couldn't get to from my iphone.. telecoms website was also down.. The automated message on the phone system said 'no known problems on the xtra network' however if you chose to talk to a technical support person you got a message saying there was a fault with surfing and checking email. No ETA. If someone from xtra is on the list, how about you put a decent procedure for changing outage notification messages. And ensuring that your phones maybe don't rely on the same infastructure? Just my rant for the week.. Does anyone know what kind of failure was needed for this error? Or was it just a list of separate systems that all died. (it is the leadup to xmas, everything starts to break then) Kyle Carter -----Original Message----- From: Bill Walker [mailto:Bill.Walker(a)staff.snap.net.nz] Sent: Friday, 28 November 2008 10:43 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] Xtra are Broked... All traffic dropped off at 9pm, DNS disapeared and so did their routes. We've been trying to get hold of Telecom by phone and email, no luck so far. Broadband users are still connected, but if they disconnect they can't reconnect. Cheers, Bill ________________________________________ From: Mark Foster [blakjak(a)blakjak.net] Sent: Friday, 28 November 2008 9:53 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] Xtra are Broked... > www.xtra.co.nz Server: alien.xtra.co.nz Address: 202.27.184.3 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to alien.xtra.co.nz timed-out At this point in time noone i've spoken with appears to be able to talk DNS to Xtra, which is having flow on effects as you may imagine (i.e. MX records aren't being supplied). A headsup for those who havn't already noticed. Mark. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.10/1813 - Release Date: 27/11/2008 9:02 a.m. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ------------------------------ Message: 4 Date: Sat, 29 Nov 2008 09:48:42 +1300 (NZDT) From: Mark Foster <blakjak(a)blakjak.net> Subject: Re: [nznog] Xtra are Broked... To: Kyle Carter <kyle(a)feet.net.nz> Cc: NZNOG(a)list.waikato.ac.nz Message-ID: <Pine.LNX.4.64.0811290944190.9273(a)skyhawk.blakjak.net> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Sat, 29 Nov 2008, Kyle Carter wrote: > Telecom sure had issues last night > > My dsl wouldn't pass any traffic, and then after rebooting the dsl > modem I couldn't get any PPP. Classic example of why 'Reboot your Router' is often not the right advice; a partial breakage (based on reports, DNS failed but access for many customers kept working) escalates to full breakage when you reboot (failure to establish PPP links). I've heard reported that people were able to surf once they set up alternative DNS servers. > Im back online now (after giving up and going to bed), but couldn't > get hold of anyone on the xtra helpdesk. Trying to contact them > resulted in dropped calls, or beeping (as in no such extension) after > being forwarded from the 'some xtra users are having issues surfing websites' message.. > > Xtras website I couldn't get to from my iphone.. telecoms website was > also down.. This morning I can't get to http://xtra.co.nz/help but (of course) http://xtra.co.nz redirects to Yahoo just fine. http://www.telecom.co.nz was down overnight, and now points to a 'scheduled upgrade' notice. I can however receive responses to DNS queries to alien.xtra.co.nz this morning, which is a big plus. > The automated message on the phone system said 'no known problems on the > xtra network' however if you chose to talk to a technical support person > you got a message saying there was a fault with surfing and checking email. > No ETA. Have to concur that automated systems like this need some consistency. 'no known problems' makes a farce of the system, I for one never take automated messages like that seriously from Telecom anymore. After over an hour on a hold queue last night, I too gave up and went to bed. > If someone from xtra is on the list, how about you put a decent procedure > for changing outage notification messages. And ensuring that your phones > maybe don't rely on the same infastructure? Whilst I agree, I also hear rumours of a power failure at MDR. That'd break all manner of things, I presume. Mark. ------------------------------ Message: 5 Date: Sat, 29 Nov 2008 11:54:38 +1300 From: "Philip Seccombe" <philip(a)turnstone.co.nz> Subject: Re: [nznog] Xtra are Broked... To: "Mark Foster" <blakjak(a)blakjak.net>, "Kyle Carter" <kyle(a)feet.net.nz> Cc: NZNOG(a)list.waikato.ac.nz Message-ID: <D775FE22DA44E145A612D100966B6E0A449353(a)server.truetechnologies.local> Content-Type: text/plain; charset="iso-8859-1" The Site maintenance message is amusing, 1400pm huh? "Unfortunately the www.telecom.co.nz website is unavailable right now as we are upgrading our system between the hours of 08:00 and 14:00pm 29 November." I'll be sure not to reboot my router, sounds pretty serious Philip Seccombe -----Original Message----- From: Mark Foster [mailto:blakjak(a)blakjak.net] Sent: Sat 11/29/2008 9:48 AM To: Kyle Carter Cc: NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] Xtra are Broked... On Sat, 29 Nov 2008, Kyle Carter wrote: > Telecom sure had issues last night > > My dsl wouldn't pass any traffic, and then after rebooting the dsl modem I > couldn't get any PPP. Classic example of why 'Reboot your Router' is often not the right advice; a partial breakage (based on reports, DNS failed but access for many customers kept working) escalates to full breakage when you reboot (failure to establish PPP links). I've heard reported that people were able to surf once they set up alternative DNS servers. > Im back online now (after giving up and going to bed), but couldn't get hold > of anyone on the xtra helpdesk. Trying to contact them resulted in dropped > calls, or beeping (as in no such extension) after being forwarded from the > 'some xtra users are having issues surfing websites' message.. > > Xtras website I couldn't get to from my iphone.. telecoms website was also > down.. This morning I can't get to http://xtra.co.nz/help but (of course) http://xtra.co.nz redirects to Yahoo just fine. http://www.telecom.co.nz was down overnight, and now points to a 'scheduled upgrade' notice. I can however receive responses to DNS queries to alien.xtra.co.nz this morning, which is a big plus. > The automated message on the phone system said 'no known problems on the > xtra network' however if you chose to talk to a technical support person > you got a message saying there was a fault with surfing and checking email. > No ETA. Have to concur that automated systems like this need some consistency. 'no known problems' makes a farce of the system, I for one never take automated messages like that seriously from Telecom anymore. After over an hour on a hold queue last night, I too gave up and went to bed. > If someone from xtra is on the list, how about you put a decent procedure > for changing outage notification messages. And ensuring that your phones > maybe don't rely on the same infastructure? Whilst I agree, I also hear rumours of a power failure at MDR. That'd break all manner of things, I presume. Mark. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog -- This message was scanned by the Turnstone managed spam filter and is believed to be clean.

4 4

Xtra are Broked...
by Mark Foster 28 Nov '08

28 Nov '08

> www.xtra.co.nz Server: alien.xtra.co.nz Address: 202.27.184.3 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to alien.xtra.co.nz timed-out At this point in time noone i've spoken with appears to be able to talk DNS to Xtra, which is having flow on effects as you may imagine (i.e. MX records aren't being supplied). A headsup for those who havn't already noticed. Mark.

5 5

NZNOG09 Registration now open
by Jonny Martin 26 Nov '08

26 Nov '08

Hi all, Registration for the NZNOG09 conference is now open. Please do register early. http://2009.nznog.org/register We're being hosted by FX Networks at the Mount Richmond Hotel and Conference Centre in Mt. Wellington, Auckland from Wednesday 28 to Friday 30th January. We haven't had a conference in Auckland for quite some years now, so this is the perfect opportunity for all those Aucklanders who find it difficult to travel to get there. The initial list of talks is online now. The website will be updated over the coming days and weeks with full details and additional speakers as they are confirmed. Speakers for NZNOG09 include James Spenceley (Vocus), Bill Manning (EP.NET) James Sinclair (PIPE Networks), IANA, Gordon Paynter (National Library), and many other quality speakers. Tutorials on offer are the Sysadmin Miniconf, Security, IPv6, and DNSSEC/DNS operations. Block accommodation, as in virtually the entire hotel, has been arranged at $110 per night. This is bookable through the NZNOG09 registration site. Twin rooms are available for those wishing to keep costs down. Once again the conference fees have been kept down at just $225 for the three days. This includes both the vendor/sponsor cocktail reception on the Wednesday night and conference dinner on the Thursday night, and lunch and tea breaks on all three days. In addition to providing a superb backdrop for social functions, the outdoor pool also provides a perfect medium for the Perry Lorrier IPoSomething challenge :). Now is the time to approach your boss and obtain approval to get to the conference. Cheers, Jonny.

1 0

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

26 Nov '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:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR ------------------------------------------------------------

1 0

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

26 Nov '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 Limited - 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.193.144.0/21^21-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, 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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081016 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - 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.193.144.0/21^21-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, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR ------------------------------------------------------------

1 0

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

26 Nov '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR ------------------------------------------------------------

1 0

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

26 Nov '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR ------------------------------------------------------------

1 0

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

26 Nov '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081127 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Nov '08

23 Nov '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 Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.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, 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.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 210.4.212.0/23^23-29, 192.88.85.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.45.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.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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 20081031 source: NZRR REPLACED BY: 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, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081124 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Nov '08

23 Nov '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 Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.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, 210.4.208.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.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.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, 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.45.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.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.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 20080812 source: NZRR REPLACED BY: 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, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.106.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 203.119.56.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081124 source: NZRR ------------------------------------------------------------

1 0

Windows 2008 R2 and IPv6
by Regan Murphy 23 Nov '08

23 Nov '08

While reading the pre-beta documentation for Windows 2008 R2 I came across the following paragraphs under the section entitled "Simplified Remote Connectivity for Corporate Computers": "In order to benefit from DirectAccess, you must be able to access the resources within your intranet by using IPv6. If your organization has an IPv6 routable infrastructure, no IPv6 translation is required. If you have resources that only have IPv4 addressing, you will need to provide IPv6-to-IPv4 transition services." (page 69) http://download.microsoft.com/download/F/2/1/F2146213-4AC0-4C50-B69A-12428F… Perhaps Windows 7 and Server 2008 R2 might provide a good reason for customers to look at deploying IPv6 after all.. -- Regan

2 1

NZRR Route Registry Update
by NZRR Database Notifications 20 Nov '08

20 Nov '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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 122.102.108.0/22^22-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.49.141.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 20081031 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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 122.102.108.0/22^22-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.205.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.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 20081121 source: NZRR ------------------------------------------------------------

1 0

iiNet being sued for 'complicit' copyright infringement
by Mark Foster 19 Nov '08

19 Nov '08

Not strictly operational, I know - but something that relates to recent discussions on this list and would probably be of interest to many. http://www.computerworld.com.au/article/268184/film_industry_sues_iinet_ove… Also found on Slashdot. http://tech.slashdot.org/tech/08/11/20/1411213.shtml I dare say the outcome of this case will make for a fairly interesting caselaw reference... Cheers Mark.

1 0

Re: [nznog] Vodafone NOC
by Erin Salmon 19 Nov '08

19 Nov '08

Could I take this opportunity to invite anyone who doesn't have a working noc(a)ispname.blah email address to get one? Or get on INOC-DBA... -Erin -----Original Message----- From: "Peter Mott" <peter(a)swizzle.co.nz> To: "nznog" <NZNOG(a)list.waikato.ac.nz> Sent: 20/11/08 1:47 p.m. Subject: [nznog] Vodafone NOC Sorry for the noise, Can somebody from IHUG/Vodafone NOC contact me off list regarding a peering issue. regards Peter Mott Swizzle | Wholesale Hosted Servers +64 21 279 4995 -/- _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

[OT] Australian Networks & Peering
by Erin Salmon 19 Nov '08

19 Nov '08

Hi All, Could anyone recommend me a contact across the ditch who is familiar with Australian IP network topology, and in particular IXPs and their participants? Replies off-list appreciated. Cheers, Erin Salmon Managing Director - Unleash Phone: 03 365 1273 Mobile: 0275 877 913

1 0

Caching peer-to-peer traffic: a done thing?
by Cameron Kerr 19 Nov '08

19 Nov '08

I'm updating my labnotes for my network management paper regarding the use of proxy caches, and previously I have pointed to the possibility of caching peer-to-peer traffic as shown in the paper Deconstructing the Kazaa Network http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=837393 I would like to know whether or not caching of peer-to-peer is something that ISPs actually do today, and if not why not. I imagine there are probably some interesting legal interactions, but I'm eager to find out how industry is moving in this field. -- Cameron Kerr <ckerr(a)cs.otago.ac.nz> Teaching Fellow, Computer Science, University of Otago

14 18

icann accredited registrar that doesnt suck
by Peter Mott 19 Nov '08

19 Nov '08

I have been out of this scene for a while, but if anybody knows of a registrar that actually works with minimum of fuss and no human interaction please ping me off list. The sun is shining outside and I don't really have the motivation to build one. But if I have to ... regards Peter Mott Swizzle | Wholesale Hosted Servers Tel. +64 21 279 4995 -/-

2 1

Vodafone NOC
by Peter Mott 19 Nov '08

19 Nov '08

Sorry for the noise, Can somebody from IHUG/Vodafone NOC contact me off list regarding a peering issue. regards Peter Mott Swizzle | Wholesale Hosted Servers +64 21 279 4995 -/-

1 0

We don't need no sales dept, we don't need no... err... How to get Data pricing, rant...
by Don Gould 19 Nov '08

19 Nov '08

Afternoon all, WARNING: If you're not in the mood for a rant about sales departments then hit <DEL> now! :) I'm trying to do some forward planning (yes I know.... I shouldn't have even considered it!) I want to know what it will cost to get better upstream speed from my shop on Mairehau. (2mbit HFC is ok at present, but won't be soon) So I called TCL, FX and TNZ. How does one talk to someone that knows about something other than ADSL? TNZ get the prize for being the most amusing, I listened politely for some time to the woman telling me all the features of their new firewall product for SOHO, before explaining that it was a bit like a half ton ute and I was looking for a price for an 18 wheeler. That was after I'd been through 3 operators and 4 VMS systems. TCL was quicker to get me speaking to a person... but took me time to get him past the $34.95 + GST plan. Is VDSL2 @ 7mbit really all they have off those nodes in Chc? Aren't they fibre fed? And surly they wouldn't put a VDSL dslam in for 1 customer? I'm the only person pulling data off the node at present. (Some TV, but apparently either everyone's getting BB from Vodafone 3G or Telecom DSL, or they're just not getting data in Mairehau) FX, no VMS, YEAH! err.... all staff in sales meeting and have yet to hear back. /rant Cheers Don

1 0

Re: [nznog] 2008 NZNOG weblinks broken
by Gerard Creamer 18 Nov '08

18 Nov '08

Sorry, you are correct, that is a typo. It should have been: info (at) nznog.org Here's a free txt fish for you }<> While I'm here, I think I lost a NOC list change - I usually get these done within a day of receiving them, so if you emailed a NOC list update a while ago and it hasn't been done please resend it. Thanks, Gerard On 19/11/2008 5:23 p.m., Paul Adshead wrote: > info @ NGnog.org <http://nog.org> ??? > > 2008/11/19 Gerard Creamer <gerard(a)netspace.net.nz > <mailto:gerard(a)netspace.net.nz>> > > > Hi, > > This is all slightly broken as we are finalising the program and > stuff. > An announcement will be made shortly regarding this. > > All inquiries can be made to info (at) ngnog.org > <http://ngnog.org/> in the meantime > > Thanks, > Gerard > > > On 19/11/2008 4:46 p.m., Cameron Kerr wrote: > > Apologies for putting this on-list, but the current conference site > > has no contact address. > > > > The 2008 site (2008.nznog.org <http://2008.nznog.org/>) has > all(?) of its links pointing to > > conference.nznog.org <http://conference.nznog.org/> which then > redirects you to the front page of the > > 2009 site. > > > > >

1 0

2008 NZNOG weblinks broken
by Cameron Kerr 18 Nov '08

18 Nov '08

Apologies for putting this on-list, but the current conference site has no contact address. The 2008 site (2008.nznog.org) has all(?) of its links pointing to conference.nznog.org which then redirects you to the front page of the 2009 site. -- Cameron Kerr <ckerr(a)cs.otago.ac.nz> Teaching Fellow, Computer Science, University of Otago

2 1

National Library of New Zealand Whole of Domain Harvest Consultation Meeting
by Dean Pemberton 17 Nov '08

17 Nov '08

Hi Everyone. As promised here are the salient points/outcomes from the Whole of Domain Harvest 2008 meeting with National Library. If anyone has any specific questions about the meeting or the topics discussed, then please feel free to contact me offline. Date: 11 November 08, National Library of New Zealand Subject: National Library of New Zealand Whole of Domain Harvest Consultation Meeting Present: National Library of New Zealand DNC, Internet NZ, Citylink, LIAC, NZNOG MED Apologies : ISPANZ Actions: Future Harvests Technical Solutions/Process: . Present harvest proposals with regard to robots/txt policy at a future date. . National Library of New Zealand and DNC to discuss request for the .nz zonefiles in future harvests and also consider an archive opt in clause as part of registration. . Discuss issue of the collector being added to blacklists with Internet Archive. . Consider the possibility of content providers sending their websites through for legal deposit in future. . With regard to the Internet Archive using 2 IP addresses (1) Honouring robots.txt(1) Not honouring robots.txt. Ask the NZNOG community whether they noticed significant differences in the behaviours between the two crawlers. Future Harvests Communications: . In future it is crucial that people are informed prior to any harvest. The discussion group include key people who will help to disseminate that message and are willing to inform their customers. . To develop a follow up plan covering technical issues, communication plans for future web harvests which they will share with the group in the coming months. . To present at the Network Operators Conference in January. . To share the analysis of the harvest details once it is available. The National Library would like to pass on their thanks to all attendees for their participation in the meeting and the excellent contributions to the discussion which will inform future web harvest activity.

1 1

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

17 Nov '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:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.254.0/23^23-29, 202.53.189.0/28^28-29, 161.29.126.128/29, 161.29.192.160/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080626 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.254.0/23^23-29, 202.53.189.0/28^28-29, 161.29.126.128/29, 161.29.192.160/29, 161.29.193.80/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR ------------------------------------------------------------

1 0

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

17 Nov '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: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081118 source: NZRR ------------------------------------------------------------

1 0

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

17 Nov '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: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081118 source: NZRR ------------------------------------------------------------

1 0

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

17 Nov '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: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 113.130.120.0/22^22-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081118 source: NZRR ------------------------------------------------------------

1 0

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

17 Nov '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:AS9503 descr: Route set advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: service(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081114 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR ------------------------------------------------------------

1 0

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

17 Nov '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081118 source: NZRR ------------------------------------------------------------

1 0

E&M to IP Interface
by Dan Clark 15 Nov '08

15 Nov '08

Gidday, Does anyone know a supplier for an E&M to IP Interface? Or E&M to Ethernet. Regards Dan

3 2

Hi All
by Mike Shaw 15 Nov '08

15 Nov '08

I've tried to unsubscribe a couple times now, and neither seems to have been successful. Can whoever is admin for this list please delete my address... Cheers, Please visit www.bulletpoints.co.nz http://blog.sculptureonthegulf.co.nz Mike Shaw Account Manager www.bulletpr.co.nz Level 2, 8-10 Whitaker Place P O Box 2051 Auckland, New Zealand e. mikes(a)bulletpr.co.nz, m.+64 21 903 181 t. +64 9 306 4004, f. +64 9 373 4374 This communication is confidential. If you have received it by mistake you must not use, disclose, copy or retain it. Please immediately notify us by return e-mail and then delete this e-mail. Views expressed in this communication may not be those of Bullet PR.

1 0

phishing site for ISPs?
by Barry Murphy 15 Nov '08

15 Nov '08

Evening, Anyone from slingshot on here and can confirm this is a phishing site or some strange 3rd party site that slingshot is using? Never seen phishers target ISP accounts before? I have an italk account with slingshot, so this makes me wonder if perhaps a database has been compromised containing email accounts, or if someone is just targeting any & every .nz email address; has anyone else without a slingshot acc seen this? See attached. Barry

5 6

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

14 Nov '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: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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:AS7657 descr: advertised to AS9439 by Vodafone/IHUG Ltd - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 174.128.16.0/20^20-29, 202.73.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 210.4.208.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.50.188.0/22^22-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 203.84.134.0/23^23-29, 203.147.108.0/23^23-29, 97.64.46.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 203.119.56.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.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: ada.mccallig(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081022 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Vodafone NZ - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 174.128.16.0/20^20-29, 202.73.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 210.4.208.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.50.188.0/22^22-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 203.84.134.0/23^23-29, 203.147.108.0/23^23-29, 97.64.46.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 203.119.56.0/24^24-29, 203.171.4.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.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: jack.lee(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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:AS64550 descr: Route set for AS64550 members: 203.97.237.96/28, 203.98.12.48/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64550 descr: advertised to AS9439 by Te Papa Tongarewa - AS64550 members: 203.98.2.160/27^27-29, 203.97.237.96/28^28-29, 203.98.12.48/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ewen(a)naos.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 202.160.112.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.124.106.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 202.49.16.0/20^20-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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081115 source: NZRR ------------------------------------------------------------

1 0

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

14 Nov '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:AS7657 descr: advertised to AS9560 by Vodafone/IHUG Ltd - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 174.128.16.0/20^20-29, 202.73.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 210.4.208.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.50.188.0/22^22-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 203.84.134.0/23^23-29, 203.147.108.0/23^23-29, 97.64.46.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 203.119.56.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.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: ada.mccallig(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081022 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Vodafone NZ - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 174.128.16.0/20^20-29, 202.73.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 210.4.208.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.50.188.0/22^22-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 203.84.134.0/23^23-29, 203.147.108.0/23^23-29, 97.64.46.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 203.119.56.0/24^24-29, 203.171.4.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.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: jack.lee(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR ------------------------------------------------------------

1 0

Solarix
by Richard Naylor 14 Nov '08

14 Nov '08

Would someone from Solarix contact me off list please regarding power at your Wellington POP. Thanks Richard 021 897 089

1 0

Re: [nznog] Solarix]
by Craig Spiers 13 Nov '08

13 Nov '08

Uh Oh! Sounds like we're in trouble! Kind Regards, Craig Spiers - Network Manager Solarix Limited DDI: +64 9 974 4753 | FAX: +64 9 523 8057 FAULTS: 0800 89 41 42 MOB: +64 21 857 183 | email: craig.spiers(a)staff.solarix.co.nz <mailto:craig.spiers(a)solarix.co.nz?subject=From%20Signature> The information contained in this email is privileged and confidential and intended for the addressee only. If you are not the intended recipient you are asked to respect that confidentiality and not disclose, copy or make use of its contents. If received in error you are asked to destroy this email and contact the sender immediately. -------- Original Message -------- Subject: [nznog] Solarix Date: Sat, 15 Nov 2008 12:44:31 +1300 From: Richard Naylor <richard.naylor(a)R2.co.nz> <mailto:richard.naylor(a)R2.co.nz> To: nznog(a)list.waikato.ac.nz Would someone from Solarix contact me off list please regarding power at your Wellington POP. Thanks Richard 021 897 089 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

5 4

Auckland - Networking Supplies?
by McDonald Richards 13 Nov '08

13 Nov '08

Hi Folks, Just wondering if anyone could recommend to me a place in the Auckland CBD for picking up supplies (Cat5e cables etc). The closer to Sky Tower, the better. Thanks, Macca

7 8

110/8 and 111/8 allocated to APNIC
by Leo Vegoda 12 Nov '08

12 Nov '08

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in November 2008: 110/8 and 111/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA

1 0

New IPv4 allocation for APNIC (110/8 and 111/8)
by Elly Tawhai 12 Nov '08

12 Nov '08

________________________________________________________________________ New IPv4 allocation for APNIC (110/8 and 111/8) ________________________________________________________________________ Hi NZNOG Community, The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in November 2008 and will be making allocations from these ranges in the near future: 110/8 111/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Kind regards, Elly APNIC

1 0

Host of Internet Spam Groups is Cut Off
by Regan Murphy 12 Nov '08

12 Nov '08

So, are all your mailservers twiddling their thumbs now with nothing to do? > Host of Internet Spam Groups is Cut Off > Spam Drops After Internet Providers Disconnect a California Hosting Firm > http://www.washingtonpost.com/wp-dyn/content/article/2008/11/12/AR200811120… -- Regan

4 3

FW: Host of Internet Spam Groups is Cut Off
by Curtis Bayne 12 Nov '08

12 Nov '08

I just received the following message about two mins after I received yours. I'd like to point out the spoofed From: domain. Ironic. -----Original Message----- From: Bruce Wood [mailto:BillysanitaryPrice(a)washingtonpost.com] Sent: Wednesday, 12 November 2008 8:40 PM To: xxx Subject: Re: watch her come over and over again -----Original Message----- From: Regan Murphy [mailto:regan.murphy(a)oasystems.co.nz] Sent: Thursday, 13 November 2008 12:29 PM To: nznog(a)list.waikato.ac.nz Subject: [nznog] Host of Internet Spam Groups is Cut Off So, are all your mailservers twiddling their thumbs now with nothing to do? > Host of Internet Spam Groups is Cut Off > Spam Drops After Internet Providers Disconnect a California Hosting Firm > http://www.washingtonpost.com/wp-dyn/content/article/2008/11/12/AR200811120… -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DNS TTL
by Stuart MacIntosh 11 Nov '08

11 Nov '08

Hello NZNOG Quick question, hopefully. How common is it for DNS server admins to manipulate TTLs of NS records, on their recursive/customer-facing servers? Also, when seeing a reply from a caching server (query A-type) NS is returned correctly but not the A record. Why is this (typically)? Stuart MacIntosh ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

6 5

Changes to Telecom NZ e-mail infrastructure.
by Greg Soffe 11 Nov '08

11 Nov '08

NZNOG This message is to inform you that Telecom New Zealand Ltd. will be making changes to its corporate messaging infrastructure. We will be specifically making changes to the way we send outbound email for staff and business. This change will culminate in the addition of an IP address for our outbound email services. The IP address 146.171.15.100 will be an authoritative source for email from the email domains below: telecom.co.nz aapt.com.au gen-i.co.nz gen-i.com.au chorus.co.nz davanti.co.nz ferrit.co.nz tnzi.co.nz tnzi.com aaptmobile.com.au computerland.co.nz If you have white listed our current IP ( 146.171.15.200 ; ish7.telecom.co.nz ) or you wish to receive Telecom corporate email unhindered then you will need to add the IP address 146.171.15.100 to your email relay's access control list and/or whitelist before Tuesday the 18th of November to avoid any issues. Please note this change is not in any way affecting any of Telecom's customer email networks in xtra.co.nz, connect.com.au, aapt.net.au or any hosted email services, It is for Telecom staff & business email only. If you have any questions regarding this change please feel free to contact me or your Telecom NZ representative? Thank you for your time. Greg Soffe Mail Administrator Asst. Manager Telecom Internet Registry Network Security Operations E greg.soffe(a)telecom.co.nz <mailto:greg.soffe(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz/> ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

2 2

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

08 Nov '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:AS45181 descr: Route set advertised to AS9560 by Swizzle - AS45181 members: 198.32.71.0/24^24-29, 203.119.56.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)swizzle.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080502 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS45181 descr: advertised to AS9560 by Swizzle Limited - AS45181 members: 116.90.76.0/22^22-29, 198.32.71.0/24^24-29, 203.119.56.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)swizzle.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081109 source: NZRR ------------------------------------------------------------

1 0

National Library domain harvest.
by Dean Pemberton 07 Nov '08

07 Nov '08

Morning, As mentioned earlier, I'm going to be a participant at a meeting to discuss the recent National Library domain harvest. I want to make sure that I represent whatever concerns people from this community may have about this. I've summarised the mailing list conversation in a previous post and will be taking these to the meeting. I've also received feedback offline from individuals and organisations. If anyone has anything they would specifically like raised, or a question put, then please contact me off list and make sure that I have it before CoB Monday. Thanks all. I'll post salient points back to the list after the meeting. Dean

1 0

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

04 Nov '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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.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, 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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: neil.fenemor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080918 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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: 130.195.0.0/16^16-29, 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.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, 203.147.108.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.36.219.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 20081017 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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.14.32.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, 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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080912 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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: 130.195.0.0/16^16-29, 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.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, 203.147.108.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.36.219.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 20081017 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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.14.32.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, 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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080912 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.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 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.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.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, 202.55.105.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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 Ltd - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 117.18.80.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.36.172.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.180.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.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.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: praneel.prasad(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 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/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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.49.164.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.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.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.208.21.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: david.johnson(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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: 130.195.0.0/16^16-29, 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.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, 203.147.108.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.36.219.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 20081017 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23655 descr: advertised to AS9560 by SNAP Internet Ltd - AS23655 members: 130.195.0.0/16^16-29, 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, 203.99.132.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.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, 203.147.108.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.36.219.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 20081105 source: NZRR ------------------------------------------------------------

1 0

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

04 Nov '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/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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.49.164.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.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.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.191.7.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 20081022 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia Ltd - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.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, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 117.18.80.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.36.172.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.180.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.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.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: praneel.prasad(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081105 source: NZRR ------------------------------------------------------------

1 0

New Zealand the trendsetter - US de-peering
by Dean Pemberton 03 Nov '08

03 Nov '08

http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/10-3…

7 7

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

02 Nov '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. Our next conference is to be hosted by FX Networks in Auckland on 28-30 January 2009. See http://list.waikato.ac.nz/pipermail/nznog/2008-September/014419.html for the 2009 Call for Participation. 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 around 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

Farmside Techs?
by Dan Clark 01 Nov '08

01 Nov '08

Gidday, anyone representing Farmside watch this list? Please contact me offlist. Regards Dan Clark

1 0

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

30 Oct '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 Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.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, 210.4.208.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.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.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, 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.45.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.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.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 20080812 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ Ltd - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.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, 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.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 210.4.212.0/23^23-29, 192.88.85.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.45.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.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.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 20081031 source: NZRR ------------------------------------------------------------

1 0

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

30 Oct '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 Maxiumum 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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-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, 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.49.89.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 20081002 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, 114.134.160.0/20^20-29, 202.55.96.0/20^20-29, 114.134.176.0/21^21-29, 119.47.112.0/21^21-29, 202.189.160.0/21^21-29, 122.102.108.0/22^22-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.49.141.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 20081031 source: NZRR ------------------------------------------------------------

1 0