- NZNOG - lists.nznog.org

Significant power outage in Wellington
by Simon Blake 09 Dec '07

09 Dec '07

Power to a good chunk of central Wellington went out around 3:58pm this afternoon. Seems to be between Customhouse Quay and Courtenay Place, we've seen at least these buildings down: -- Date: Mon, 10 Dec 2007 16:15:22 +1300 Subject: tentative list of power affected sites Willbank House (57 Willis St) BDO House, 99-105 Customhouse Quay Guardian Trust House (15 Willeston St) Cigna House (28-48 Mercer St) Economous Building/Hibernian House (4 Bond St) Perpetual Trust House (111-115 Customhouse Quay) Computerland House (154 Featherston St) Todd Building (95 Customhouse Quay, cnr Customhouse and Hunter) Synergy House (Queens Wharf) Optimation House (1-13 Grey St) HP Tower/Hotel Intercontinental (163-175 Featherston St) Lumley House (3-11 Hunter St) Exchange Place (5-7 Willeston St) Willeston Centre (22-28 Willeston St) NZX Centre (11 Cable St) United Building (107 Customhouse Quay) CMC Building (89 Courtenay Place) Conservation House (18-32 Manners St) Sovereign House (34 Manners Street) MSO House (19 Edward St) BNZ Trust House (50 Manners St) Axon House (1 Willeston St) NEC/Panasonic House (40 Taranaki St) Cheers Si

3 2

Re: [nznog] NZNOG '08 Talks
by Ewen McNeill 09 Dec '07

09 Dec '07

In message <eedb5d410712091222j7181d91eja34beb9c8ec64727(a)mail.gmail.com>, "Neil Fenemor" writes: >As some of you will have noticed, we're getting more of the talks confirmed >and up for NZNOG'08. However there is still a spot for you to speak. There are also still a few speaking slots at the Sysadmin Miniconf (held on the Wednesday); details here: http://nznog.miniconf.org/ (We're a little behind on the draft programme, as we're still waiting on a few speakers to provide titles/abstracts.) I'd be particularly interested in someone to speak on content distribution networks, and someone to speak on deploying IPv6-aware applications, but proposals for anything related to ISP systems administration will be gratefully received. Please email proposals and any questions to <talks08(a)nznog.miniconf.org> Ewen

1 0

NZNOG '08 Talks
by Neil Fenemor 09 Dec '07

09 Dec '07

Hi, As some of you will have noticed, we're getting more of the talks confirmed and up for NZNOG'08. However there is still a spot for you to speak. While the majority of the talks are 30 minutes, we are able to accommodate 20 minutes, or if you prefer a 5 minute lightning talk. If you're interested in talking, feel free to email myself, or the program committee on prog08(a)nznog.org For all your NZNOG'08 needs, visit http://conference.nznog.org/ Look forward to hearing from you. Cheers, neil NZNOG'08

1 0

APNIC Training - next week.
by Jonny Martin 04 Dec '07

04 Dec '07

For those of you who haven't already found out, APNIC are running training in Wellington and Auckland next week: Wellington, 11 December: http://www.apnic.net/training/registration/ 2007/register-20071211.html Auckland, 13 December: http://www.apnic.net/training/registration/ 2007/register-20071213.html Training will be the Extended Internet Resource Management Essentials (IRME), followed by a hostmaster consultation session the following morning in each location. The IRME course won't be covered at NZNOG08, so this is your chance to attend the training. This is a good course for anyone who works at an organisation that currently holds, or is looking at obtaining APNIC allocations. To those of you who think you know it all already, well I don't believe you! :). Cheers, Jonny.

1 0

New Zealand Meraki Experiences?
by Hamish MacEwan 04 Dec '07

04 Dec '07

Hi, Anyone have any experience with the Meraki wireless mesh networking system, formerly MIT's RoofNet, in the New Zealand environment that they would be prepared to share with a group interested in investigating the technology? http://meraki.com/about/ http://www.technologyreview.com/Infotech/19260/?a=f Hamish. -- http://del.icio.us/Hamish.MacEwan http://urltea.com/3jm?GoogleSharedItems

2 2

NRO Number Council election: Call for nominations
by Elly Tawhai 03 Dec '07

03 Dec '07

[Apologies for duplicates] Dear colleagues This is a call for nominations of individuals from the Asia Pacific region to serve on the NRO Number Council. As of 31 March 2008 one Asia Pacific Number Council seat will become vacant. This seat will be filled until 31 December 2009 by an individual nominated through this open call. The selection process will involve an open election to be held during the APNIC 25 Open Policy Meeting in Taipei, Taiwan on Friday 29 February 2008. The elected individual must be willing to serve an 18-month term beginning 1 April 2008. * Deadline for nominations: 24 January 2008 * Election scheduled for: 29 February 2008 There will also be an online voting facility available to APNIC members through MyAPNIC. This service will open on Wednesday 13 February 2008 and close at 09:00 UTC+8, Wednesday 27 February 2008. More information on how to cast your vote online will be available in MyAPNIC over the coming weeks. For full details on the position and how to nominate please see: http://www.apnic.net/community/nro/nc/call-nomination.html Please note that the NRO Number Council representatives now fulfil the role of ICANN's ASO Address Council. Responsibilities of NRO NC representatives are outlined in the ASO Memorandum of Understanding at: http://www.nro.net/documents/aso-mou.html With best regards APNIC Secretariat --------------------------------------------------------------------- APNIC Secretariat email: secretariat(a)apnic.net http://www.apnic.net sip: info(a)voip.apnic.net phone: +61 7 3858 3100 ---------------------------------------------------------------------

1 0

APNIC IPv6 transit exchange
by Terry Manderson 28 Nov '07

28 Nov '07

Dear NZnog Colleagues, APNIC is facilitating IPv6 adoption in the Asia Pacific region with an IPv6 Transit Exchange. This will allow APNIC to support IPv6 and at the same time expand IPv6 awareness, use, and understanding of IPv6 in the Asia Pacific region. The IPv6 Transit Exchange is a Reasearch and Development effort and will continue to run for as long the participants require the service, however a horizon may be set when commercial providers offer native IPv6 services in a commercial relationship. APNIC will additionally advertise prefixes and negotiate peers for both 2byte and 4byte Autonomous System numbers (AS) to ipv6 neighbors of this service. The preference for the IPv6 exchange is that is an MLPA style service. That is, we will re-advertise all routes presented to us. And the more routes you are willing to advertise the better! As such, any organisations willing to offer full transit will be greatly appreciated. Any organisation with an IPv6 prefix is welcome, and encouraged to join. Please see the following link for more information: [http://icons.apnic.net/index.php? option=com_content&task=view&id=3432&Itemid=94] Cheers, Terry -- Terry Manderson email: terry(a)apnic.net Network Operations Manager, APNIC sip: info(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3100

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Nov '07

28 Nov '07

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Nov '07

28 Nov '07

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

1 0

Xtra Mail Admin Contact Off List re White List
by Don Gould 27 Nov '07

27 Nov '07

If any one knows how I get babyonthemove.co.nz white listed with Xtra's email system could they please contact me. At present the 25 franchises who have broadband accounts with Xtra are finding that email forwarded to their @xtra.co.nz account is going missing. We have set up their addresses so that the email is forwarded automatically to their relivant xtra account. If others have tried this sort of thing and discovered that you just can't do it this way then I'd like to know. eg. east.chch(a)babyonthemove.co.nz --> whatever(a)xtra.co.nz west.chch(a)babyonthemove.co.nz --> whoever(a)xtra.co.nz We did this because we didn't want to have to explain to each franchise holder how to set up Outlook or Thunderbird to retrieve mail from the the babyonthemove.co.nz mail server. WHY THIS LIST/NOT THIS LIST PLEASE! I've already rung level 1 support. The first person I spoke to told me "you're not with us", after she's asked me for my phone number, despite my explaining who I was and why I was calling. To her credit she did not cut me off, she put me through to a broadband helpdesk person who did not know what a 'white list' was. He also didn't cut me off, and put me though to a person who did at least know what a white list is. He referred me to http://xtra.co.nz/help/0,,4155-7793692,00.html which referred me to http://help.yahoo.com/l/us/yahoo/mail/yahoomail/postmaster/bulk.html which I filled out. It then sent me a 1200 word email about spam. That was the point I felt I'd read enough, talked to enough people who were clearly not in control of the situation and wanted to speak to a person who has actually been through this process and can tell me if I'm chasing my tail or actually in the right direction. Or, do I have to simply bite the bullet and make everyone set up mail readers? Cheers Don -- Don Gould 2/59 Peverel Street, Riccarton, Christchurch, New Zealand Phone: +64 3 348 7235 - Mobile: +64 21 114 0699 www.thinkdesignprint.co.nz

6 7