- NZNOG - lists.nznog.org

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

Small interruptions to APE at L48 Sky Tower over the next week
by Simon Blake 27 Nov '07

27 Nov '07

Hi all Most affected parties should already be aware, but I'll repeat it here in case the change control messages didn't get to the right people - we're replacing gear on L48 over the next week. Between 12:01 and 6:00 on Thursday 28 through Dec 5, (excluding Saturday and Sunday morning), there will likely be short interruptions to every connection to the Citylink cabinet on L48. More info at http://news.clnz.net/2007/11/16#Level-48-Sky-Tower-Project Cheers Simon

2 2

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

27 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: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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071108 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071128 source: NZRR ------------------------------------------------------------

1 0

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

27 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: 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071108 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071128 source: NZRR ------------------------------------------------------------

1 0

APNIC 25 Call for Proposals
by Elly Tawhai 25 Nov '07

25 Nov '07

APNIC 25 25 February - 29 February 2008 Howard Plaza Hotel Taipei, Taiwan Dear colleagues Special Interest Groups (SIGs) will be held at the 25th APNIC Open Policy Meeting. We invite you to submit proposal presentations for these sessions. There are two types of presentations: - Policy proposal (P) A proposal which requires feedback and community consensus before it can proceed. - Informational (I) Typically a status report delivered to convey information to the audience. Informational presentations may be presented in SIG sessions. * Submitting policy proposals To submit a policy proposal before the 28 January 2008 deadline, you have two options: 1. Use the online form at: http://www.apnic.net/cgi-bin/policy_proposal.pl 2. Send your proposal in TEXT format to the appropriate SIG Chair, CCing <sig(a)apnic.net>. * Submitting informational proposals Send your proposal in TEXT format to <program(a)apnic.net>, preferably before 28 January 2008. Agenda slots will be allocated on a first-come first-served basis, so it is advisable to submit your proposal as soon as possible. More information ---------------- SIG archives and guidelines for presenters are available at: http://www.apnic.net/meetings/archive/sigs/ SIG chairs can be contacted at: * Policy SIG <sig-policy-chair(a)apnic.net> * Database SIG <sig-db-chair(a)apnic.net> * DNS operations SIG <sig-dns-chair(a)apnic.net> * IPv6 technical SIG <sig-ipv6-chair(a)apnic.net> * IX SIG <sig-ix-chair(a)apnic.net> * NIR SIG <sig-nir-chair(a)apnic.net> * Routing SIG <sig-routing-chair(a)apnic.net> We look forward to seeing you in Taipei! Kind regards, Elly ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

An explanation of what went wrong at Mayoral Drive on 4/11
by Matthew Poole 21 Nov '07

21 Nov '07

ComputerWorld article. http://s0.tx.co.nz/at/tep34n279457j138688i194855f2c4680224a4t9s4z During testing a UPS failed to start a generator, then its batteries went flat and the systems it was feeding had to be restarted. Fire and Police were hit hard because they'd only very recently consolidated to a single database from three region-based ones, and hadn't had a DR drill (one was planned) so it was the first time they'd actually done a cut-over. That sod Murphy strikes again! -- Matthew Poole "Don't use force. Get a bigger hammer."

9 14

Re: [nznog] An explanation of what went wrong at Mayoral Drive on 4/11
by Russell Sharpe 20 Nov '07

20 Nov '07

I agree with you on that as well as my comments Peter :| -----Original Message----- From: Peter Mott [mailto:peter(a)mott.co.nz] Sent: Wednesday, 21 November 2007 20:02 To: Russell Sharpe Cc: 'NZNOG' Subject: Re: [nznog] An explanation of what went wrong at Mayoral Drive on 4/11 On 21/11/2007, at 7:45 PM, Russell Sharpe wrote: > IMHO. This type of incident enforces my feeling that some providers > are only interested in profits, not customer service. :( and a gross > lack of investment More likely due to a lack of ... * personal ownership of having it stay going * basic problem solving skills * understanding of how it works * consequences for when you screw up Blame management if you want, but I would start with parents and schools. Time for a beer. regards Peter Mott -/-

1 0

Re: [nznog] An explanation of what went wrong at Mayoral Drive on
by Stewart Fleming 20 Nov '07

20 Nov '07

> -----Original Message----- > From: nznog-request(a)list.waikato.ac.nz > [mailto:nznog-request(a)list.waikato.ac.nz] > Sent: Wednesday, 21 November 2007 12:00 p.m. > Message: 2 > Date: Wed, 21 Nov 2007 09:38:51 +1300 (NZDT) > From: Matthew Poole <matt(a)p00le.net> > Subject: [nznog] An explanation of what went wrong at Mayoral Drive on > 4/11 > To: NZNOG <nznog(a)list.waikato.ac.nz> > Message-ID: <Pine.LNX.4.62.0711210935340.8793(a)maverick.blakjak.net> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > ComputerWorld article. > http://s0.tx.co.nz/at/tep34n279457j138688i194855f2c4680224a4t9s4z > > During testing a UPS failed to start a generator, then its > batteries went flat and the systems it was feeding had to be > restarted. Interesting that there was a similar power-related failure of emergency systems in the South Island a few days after this incident. And that a similar incident occurred at the Telecom Dunedin exchange about 6 months ago (UPS test, generator started, sparked, caused a fire, fire happened to be in same room as mains cutover switch...UPS ran flat.)

1 0

NZNOG 2008 registrations are up/up
by Jonny Martin 20 Nov '07

20 Nov '07

The NZNOG 2008 website is up and registrations are now open. http://conference.nznog.org Hope you can make it to Dunedin, Jan 23-25 2008! Cheers, Jonny.

3 2