- NZNOG - lists.nznog.org

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

04 Jan '11

The New Zealand Network Operators' Group The NZNOG mailing list exists 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. The NZNOG Trust is registered as a charitable entity under the Charities Act. The trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. Other than the four trustees, the NZNOG does not have a formal membership. Conference NZNOG holds New Zealand's only annual technical networking conference. The next conference is scheduled for Monday to Friday 24-29 January 2011 in Wellington, hosted by Vodafone. This very month as is. Register at http://2011.nznog.org/ if you haven't already. 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 1100 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 | I don't approve of gambling. I'll just | spend my time in the bar. High Performance Computing | - NZNOG 2010 attendee The University of Waikato |

1 0

Nominations to the APNIC Executive Council now open
by Srinivas Chendi 03 Jan '11

03 Jan '11

_______________________________________________________________________ Nominations to the APNIC Executive Council now open _______________________________________________________________________ Four positions on the APNIC Executive Council (EC) will be up for election at APNIC 31 in Hong Kong on Friday, 25 February 2011. The EC represents the APNIC membership and acts in the best interests of the organization. The members whose positions are up for re-election are: - Hyun-Joon Kwon - James Spenceley - Jian Zhang - Kuo-Wei Wu The position held by Kuo-Wei Wu, who was elected to the Board of ICANN, will also be up for election. Nominations are due Wednesday, 9 February 2011 at 17:30 (UTC +10). Nominees do not have to be representatives of APNIC Members, but only APNIC Members may nominate and vote for candidates. Nominations must be made using the online nomination form, which is available now. http://meetings.apnic.net/31/elections/nominate For more information on the EC election process, please see: http://www.apnic.net/community/participate/elections/ec If you have any questions, please contact the APNIC Secretariat at: helpdesk(a)apnic.net _______________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 3646, South Brisbane, QLD 4064 Australia Fax: +61 7 3858 3199 6 Cordelia St, South Brisbane, QLD http://www.apnic.net _______________________________________________________________________ * Sent by email to save paper. Print only if necessary.

1 0

Smartlinx3 Upper Hutt Network issue notice
by Ian Hastie 03 Jan '11

03 Jan '11

There was a fire in the upper floors of CBD Towers Upper Hutt yesterday which disrupted services to some Smartlinx3 customers in the area. The Smartlinx3 UPS equipment held up the systems for 3 hours and normal services were restored once the fire service restored power to the building. Whilst the equipment in CBD Towers (as with all Smartlinx3 POP sites) is powered through a UPS there may be some future interruptions to service for customers located in CBD Towers and our Upper Hutt radio customers whilst repairs are completed in CBD Towers. We will notify our customers of any potential risk of outage once we have more information available from the building owners. Contact SL3 if you have any questions or need more information. Regards Ian Hastie LINKIT Ph +64 (0)21 75-5465

1 0

Possible Scam attack over the phone (Over the christmas break)
by Chris Hodgetts 28 Dec '10

28 Dec '10

Just had a friend call me while his partner was on the phone. They had a call from "Computer Maintenance Department - Melbourne" They 'advised' that the computer was having problems - and they need to connect to the internet. These people were from 'International Routing Systems - and all virus infection notifications get sent to them from around Aus, NZ and UK' My friend was asked to 'press windows key and 'r' key' - at which point they were asked how they got the contact details They were advised 'When you register we get your name and number..' (Interesting they knew the last name of the person to which they were speaking) The called person then asked 'who pays their bills they were told it was the 'Windows Operating system Technical Department' did. and 'you do not pay for our services at all' They asked for the name of the person she was speaking with and after a long time it turned out to be a 'David Smith'. She asked for a phone number to contact them back , and was given 03 856 982 75 (Aus) which turns out to be disconnected. Unsure if this is a scam attack, or what was going on, but just thought as it was 'internet and computer' related, this list might need to know.

3 3

some photos for those at work and bored
by Richard Naylor 26 Dec '10

26 Dec '10

Have been doing some archive tidy ups and found these. Might be of interest to the older folks. http://www.r2.co.nz/20071209/city-net/ - photos of the old WCC computer room before moving upstairs when they did the Civic Centre (ie we stayed put and they refurbished around us - 2 fires and a flood later....we moved) http://www.r2.co.nz/20071209/city-net/micro-vax-cluster.jpg - shows the micro-Vax cluster that was known as "Kosmos" the public side of City-Net. The the units in the 1/2 rack with no top on it. I forget what the other nodes in that cluster were called. Originally Kosmos was a Vax 750 but it wasn't powerful enough. There were other clusters for development and production, as well as a Honeywell for legacy WCC stuff and an IBM AS-400 for the Library. The production cluster had striped and shadowed disks not RAID as they were very expensive - $40k for 450MBytes. http://www.r2.co.nz/20071209/city-net/comms-rack-r.jpg - shows part of the comms rack and the 3 shelves of dial-up modems. One of which the public used. There were supposed to be 3 sets of 8, for IT staff, WCC Staff and public. In the end it was 12/12 between IT and the Public. We used to get 50+ users on Kosmos and with only 12 modems it was obvious they didn't need CityNet as an access gateway. Besides there were by then commercial ISPs and we were starting CityLink (name chosen by Jim Higgins), so we closed (the public side of ) CityNet in 1995 the year we started CityLink. The shelves of modems at the right side of the racks were 9600 bps CODEX modems for stat muxes for all the 80+ remote council locations such as works depot libraries etc. They used Telecom A2 circuits (aka dark copper). Telecom withdrew them and replaced them with digital data circuits. I think we traded the modems in for something or other. There were also at least 3 9600 dial up modems to provide circuits via dial up while we waited for Telecom to provision, or as a backup if the data circuits went down. The leased circuits included Otaki and Palmerston North for the milk plants, CHC (CHC City Council was our dial in node for several years) and AKL for dial in access. There was also fiber to Wellington Regional Council and x.25 to the Valuation Dept, National Library and BRANZ-Info. http://www.r2.co.nz/20071209/city-net/comms-rack-l.jpg - left side of rack - shows Cisco AGS+ and DEC ethernet bridges with fiber to link ethernet to all the local buildings. Our first fiber circuit was between 101 Wakefield St (WCC) and 40 Cuba Street (MED) in 1988. Just above the AGS is (details forgotten) that ran the 64k circuit to VUW. A year or two later we migrated that to a 2Mbps microwave, using VUW as a hop to the works depot in Tory St, now a Te Papa depot. The link to VUW was a spare channel on the 4x2Mbps microwave. Enjoy. Richard

2 1

IP Management software at ISP/Carrier scale
by John Russell 26 Dec '10

26 Dec '10

So, I'm looking at this ipv6 assignment from the good folks at APNIC, and I'm also looking at my current, aging, not-very-scalable IP Management system, and I'm not liking where I see this going. I'm interested to hear NZNOGs suggestions about decent, scalable, software (preferably off-the-shelf) to handle v4 and v6 IP management. Open source stuff welcome, though commercial, supported software is also fine. I'm just wondering what you cool kids are using to manage their address space these days. Feedback, thoughts and opinions welcome. - JSR

11 11

NZNOG11 :: Jan 24 - Jan 28 :: Wellington, New Zealand :: Registration open
by Gerard Creamer 21 Dec '10

21 Dec '10

Finally and at last registrations are open for NZNOG11. http://2011.nznog.org In a fairly open attempt to bribe you all to register quickly, if you register by 31 December 2010 you'll go into the draw to win a 64GB WiFi+3G iPad. NZNOG 2011 : Jan 24 - Jan 28 Intercontinental Hotel, 2 Grey St Wellington, New Zealand Following last years success we are having three day workshops Monday 24 January to Wednesday 26 January, with the conference tutorial day on Wednesday 26 January and the main conference on Thursday 27 January and Friday 28 January. The program is looking pretty sharp again this year, with some great speakers for the main conference including Mike Hughes (until quite recently, London Internet Exchange), Bill Woodcock, (Packet Clearing House), Brian Carpenter (University of Auckland) and Gaurab Raj Upadhaya (Limelight Networks). A big thanks to all of our sponsors - NZNOG couldn't happen without their generosity. In particular our hosts Vodafone, and our platinum sponsor, Vocus. Cheers Gerard For the NZNOG11 Org Team

4 3

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

21 Dec '10

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-ROUTES6:AS38477 descr: Route set advertised to AS9560 by Unleash - AS38477 mp-members: 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2400:C000: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: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101117 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS38477 descr: Route set advertised to AS9560 by Unleash - AS38477 mp-members: 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101222 source: NZRR ------------------------------------------------------------

1 0

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

21 Dec '10

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:AS38477 descr: Route set advertised to AS9439 by Unleash - AS38477 mp-members: 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101210 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES6:AS38477 descr: Route set advertised to AS9439 by Unleash - AS38477 mp-members: 2401:F000:0:0:0:0:0:0/32^32-64, 2407:2400:0:0:0:0:0:0/32^32-64, 2400:C000:0:0:0:0:0:0/32^32-64, 2001:DF0:DC:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101222 source: NZRR ------------------------------------------------------------

1 0

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

21 Dec '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 111.69.0.0/16^16-29, 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, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 27.110.120.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.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.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 140.200.7.0/24^24-29, 143.96.13.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.46.187.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.110.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.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: jonas.bergler(a)staff.snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101111 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 111.69.0.0/16^16-29, 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, 14.1.32.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 27.110.120.0/21^21-29, 120.136.0.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 110.92.16.0/22^22-29, 113.197.96.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.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 140.200.7.0/24^24-29, 143.96.13.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.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.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.39.0/24^24-29, 202.146.186.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 210.7.40.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20101222 source: NZRR ------------------------------------------------------------

1 0