- NZNOG - lists.nznog.org

Re: [nznog] What is this?
by Arron Scott (ascott) 10 Jun '06

10 Jun '06

Are you sure about that? The 9k6 leased line was run on a pair of Paradyne error correcting leased line Async Modems, which John Houlker smuggled into New Zealand stating it was a computer, off the top of my head. The Paradynes were ditched personally by me, after I found them hidden under the raised flooring in the Comms room at the back of the Computer Room. They were sitting beside the old router, the name of which I can't remember anymore, which was a PC chassis, before that was replaced by the Cisco MGS which ran the internet from when it was upgraded to the 64k Synchronous Serial link. If they indeed came from UoW, you would need to check with John Houlker as to whether they were ever turned on or not, I'm not aware of when the Net in NZ ran at 14k4, but that was a wee bit before my time. Arron Scott -----Original Message----- From: Perry Lorier [mailto:perry(a)coders.net] Sent: Friday, 2 June 2006 5:08 p.m. To: Patrick Jordan-Smith Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] What is this? Patrick Jordan-Smith wrote: > On 2/06/2006, at 4:51 PM, Perry Lorier wrote: > > >>http://www.wlug.org.nz/archive/history/ >> >>Anyone guess what this modem was last used for? and when/where? We >>powered it on, it still works :) > > > Is it the modem used after the link from Waikato -> Hawaii was > upgraded from 9.6k? Yup. One of the guys around here had it propping up his TV after deciding it just couldn't be thrown out. It's a 14k4 modem, I believe it's for leased line operation (haven't plugged it into a serial port to find out). After we powered it on we noticed the "110v" label on the back, maybe running it at 240v means it'll run at 28k8? :) It complains about "Carrier Not Detected" for some strange reason. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

11 17

Re: [nznog] Is there a Telecom paging tcp interface at all ?
by Roger Williams 10 Jun '06

10 Jun '06

>use an SMS transport provider (*cough* ..) >who can also reach the 026 network via SMPP. Small typo. That's SNPP. http://www.snpp.info/ http://www.faqs.org/rfcs/rfc1861.html So, does Telecom provide a public gateway to their paging system that speaks SNPP? If so, that might be what Ian was looking for in his original post. Roger

2 1

Re: [nznog] Is there a Telecom paging tcp interface at all ?
by Roger Williams 09 Jun '06

09 Jun '06

>Does anyone know if it is possible to connect to [something] at telecom >via tcp/ip that allows message sending to alphanumeric pagers, or is >that still only accessible via dialup modem to pacnet ? Does Telecom's "AirPage" qualify? "AirPage is a Telecom service, which allows you to receive short e-mails on your alphanumeric pager from anywhere in the world." http://www.telecom.co.nz/content/0,8748,201412-201962,00.html -- Roger Williams, GNS Science, New Zealand : www.gns.cri.nz

18 26

Re: [nznog] Is there a Telecom paging tcp interface at all ?
by Ian Batterbee 09 Jun '06

09 Jun '06

Dave Green Wrote: >I've used Linux + Asterisk as a local "roll-your-own" gateway for >dialling alphanumeric pagers .. everything from outage alerts to wake-up >calls. > > > How exactly are you doing that ?.. specifically, how are you sending the alpha part of alphanumerics without dialling pacnet ?

2 1

spamming the list
by Ian Batterbee 09 Jun '06

09 Jun '06

As the person who started the topic about sending to alphanumeric pagers, I feel partly responsible for the resulting p*ss*ng contest that some of the list members have found necessary. To them I say, there's no need for personal abuse on this list - if you disagree with someone else's decision to buy a $700 box then that's fine, but I'ld much rather my inbox wasn't full of messages about who is right and who is wrong. Thanks.

2 1

Dept. Internal Affairs staff?
by Will Steele 09 Jun '06

09 Jun '06

Are there any department of internal affairs staff familiar with the "Life Event Validation" system (or any other person familiar with it, for that matter) subscribed to this list? If so, please contact me off-list. Thanks, Will.

1 0

BEER LOSES TOP SPOT TO IPOD
by Richard Naylor 09 Jun '06

09 Jun '06

Just goes to show that the quality of education has dropped. BEER LOSES TOP SPOT TO IPOD For only the second time in ten years, drinking beer has been relegated to second on Student Monitor's biannual survey of what is "in" on campus, with iPods slotting in at number one. The only other thing to unseat beer: the Internet, in 1997. Eric Weil of Student Monitor said of the latest results of its Lifestyle and Media Study, "We knew iPods were pervasive on campus as a learning and entertainment device, but we didn't see it rating that high." Between spring 2006 and spring 2006, iPods jumped from 59 percent of students saying they were "in" to 73 percent. Rounding out the top ten spots on the survey are Facebook (which tied beer for second), drinking other alcohol, text messaging, downloading music, going to clubs, instant messaging, working out, and coffee. Dan Updegrove, vice president for information technology at the University of Texas at Austin, pointed out that the speed with which "Internet-based phenomena can emerge" accounts for having so many technologies on the top ten that did not even exist several years ago. USA Today, 7 June 2006 http://www.usatoday.com/tech/news/2006-06-07-ipod-tops-beer_x.htm

1 0

Re: [nznog] Is there a Telecom paging tcp interface at all ?
by Will Steele 09 Jun '06

09 Jun '06

I'm sure this thread already ended with the below message, which was over 15 posts ago. Note how the person who asked the original question says that the suggested solution qualifies as an answer to his question, and he does not ask for any further information. Judging from this, it is fairly possible to come to the conclusion that you do not need to flame the shit out of each other with irrelevant messages telling JJ what a n00b he is. Everyone go back to bed now. Monday is days away. Will -----Original Message----- From: Ian Batterbee [mailto:ian.batterbee(a)aut.ac.nz] Sent: Friday, 9 June 2006 9:53 p.m. To: Roger Williams Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Is there a Telecom paging tcp interface at all ? That, uh, certainly seems to qualify, yes. Thanks. Roger Williams wrote: >>Does anyone know if it is possible to connect to [something] at telecom >>via tcp/ip that allows message sending to alphanumeric pagers, or is >>that still only accessible via dialup modem to pacnet ? >> >> > >Does Telecom's "AirPage" qualify? > > "AirPage is a Telecom service, which allows you to > receive short e-mails on your alphanumeric pager > from anywhere in the world." > > http://www.telecom.co.nz/content/0,8748,201412-201962,00.html > > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Is there a Telecom paging tcp interface at all ?
by Ian Batterbee 09 Jun '06

09 Jun '06

Does anyone know if it is possible to connect to [something] at telecom via tcp/ip that allows message sending to alphanumeric pagers, or is that still only accessible via dialup modem to pacnet ?

2 1

Jobs... (semi-operational)
by Scott Walsh 08 Jun '06

08 Jun '06

Hi, Sorry for the spam, it is semi-operational though. Putting together a new NOC style team in Wellington, if of interest: https://forms.bpfj.intronet.com/ibm/Forms/ap/expro/VacancyDetails.jsp?va cancyCode=80684 https://forms.bpfj.intronet.com/ibm/Forms/ap/expro/VacancyDetails.jsp?va cancyCode=80685 https://forms.bpfj.intronet.com/ibm/Forms/ap/expro/VacancyDetails.jsp?va cancyCode=80687 To keep it more operational, off to find beer. Thanks Scott Walsh Service Implementation Specialist Integrated Technology Services (ITS) - Passionate about Winning IBM New Zealand Limited Level 2, 48 Greys Ave, P.O Box 6840, Wellesley Street, Auckland, New Zealand DDI: +64 9 359 4104 Fax: +64 9 309 3242 Mob: +64 21 307 763 LSC: 0800 802 729 Office: 0800 801 800

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Jun '06

08 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.36.170.0/24^24-29, 202.36.227.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tsalmen(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060302 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060609 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 07 Jun '06

07 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17492 descr: Route set advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.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: matthew.oram(a)vectornetworks.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050518 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17492 descr: advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29, 202.0.151.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: Patrick.Balmer(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060608 source: NZRR

1 0

Telecom BRI
by Sam Banks 06 Jun '06

06 Jun '06

Hi Guys Does anyone know the default settings for Telecom BRI ISDN lines. Point to multipoint or Point to point? TE or NT? TX and RX gain? Thanks Sam -- A good friend will help you move, a really good friend will help you move a body.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '06

05 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - 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, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.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.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 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.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.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, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '06

05 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - 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, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.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.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 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.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.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, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR

1 0

Strange increase/decrease in mail rejection stats
by Simon 05 Jun '06

05 Jun '06

Hi There, I have noticed that since XTRA moved to their new mail platform, that we have had a steady increase in rejected email from fepXX.xtra.co.nz (mainly rejected due to invalid from' domain name). However, as of this morning at about 1pm, the rejected rate dropped right back to minimal again. Is someone at XTRA allowed to let us know if there have been mail system changes at their end? - and if there is any impact beyond the above? Just checking as its a bit strange to see a graph do that without getting all "OK, what do i need to check now..". Cheers Simon

1 0

Re: [nznog] What is this?
by Webmaster 03 Jun '06

03 Jun '06

Luxury. We used to live in a paper bag... I remember using a 300 bps modem to connect to bulletin boards way back when. R >>> shane hobson <shane(a)liteup.co.nz> 2/06/2006 19:33 >>> I used to use Pacnet on a 1200/75 modem on a regular basis. That would have been late 80's from memory. Shane Bill Walker wrote: > Ian McDonald wrote: > >>> In which case it was half the Internet - and if all we had was 14K for >>> the whole country - well, say no more. >>> >>> Its debatable if that really was an Internet connection in the modern >>> sense. >>> >>> >>> >> Well I was using it for NNTP, SMTP, FTP on the Waikato link when it >> was 2.4K and then 4.8K and it seemed like the Internet to me then.... >> >> > I remember a 1200bps dial up modem my dad had.... > > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 5

Re: [nznog] What is this?
by Jeremy Strachan 02 Jun '06

02 Jun '06

In which case it was half the Internet - and if all we had was 14K for the whole country - well, say no more. Its debatable if that really was an Internet connection in the modern sense. 14K poses a significant restriction on what was actually possible, even back then. and yes - it is 14K each way - because a leased line is two pairs (four wires), not two wires like a home user has with a dial-up modem. It's a full duplex link, and yes we (cough) have moved along way in nearly 20 years, broadband may be faster on occasions. And not detecting a cariier - it can't detect the carrier signal from the modem at the other end - because both should see each others carrier. -----Original Message----- From: Perry Lorier [mailto:perry(a)coders.net] Sent: Friday, 2 June 2006 4:59 p.m. To: Jeremy Strachan Subject: Re: [nznog] What is this? [offlist so as not to give the game away] > ah, so young ... Its pre-Internet .. > Not quite, it was the modem used out of Waikato for New Zealands Internet connection around 1989ish. I think that means it's not "Pre Internet", it /was/ the Internet!

6 6

What is this?
by Perry Lorier 01 Jun '06

01 Jun '06

http://www.wlug.org.nz/archive/history/ Anyone guess what this modem was last used for? and when/where? We powered it on, it still works :)

5 5

Re: [nznog] What is this?
by Jeremy Strachan 01 Jun '06

01 Jun '06

2400, 4800, 9600, and yes even 14.4K was possible, and 19.2K. It probably ran over leased (conditioned) dedicated lines. It looks like a 1987 date on the back to me ... It is probably both large and heavy. Jeremy -----Original Message----- From: Joseph Miller [mailto:joseph(a)digiweb.net.nz] Sent: Friday, 2 June 2006 4:58 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] What is this? It can't be that old - it's a whole 14.4k!

1 0

Re: [nznog] What is this?
by Jeremy Strachan 01 Jun '06

01 Jun '06

ah, so young ... Its pre-Internet .. -----Original Message----- From: Perry Lorier [mailto:perry(a)coders.net] Sent: Friday, 2 June 2006 4:52 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] What is this? http://www.wlug.org.nz/archive/history/ Anyone guess what this modem was last used for? and when/where? We powered it on, it still works :) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jun '06

01 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.83.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060210 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060602 source: NZRR

1 0

[RIR] Deprecation of ip6.int Scheduled for June 1, 2006
by bmanning＠vacation.karoshi.com 31 May '06

31 May '06

On Thu, Mar 02, 2006 at 09:19:56AM -0500, Member Services wrote: > In August 2005, RFC 4159 Deprecation of ip6.int was published as Best > Current Practice. This RFC noted that maintenance of ip6.int is no > longer required and that the Regional Internet Registries adopt a > schedule for cessation of ip6.int. All the RIRs have agreed to deprecate > ip6.int on June 1, 2006. Further note that ARIN no longer modifies any > of the zones it administers under ip6.int effective December 7, 2005. > > Ginny Listman > Director of Engineering > American Registry for Internet Numbers and: On Tue, 16 May 2006 11:09:10 +0200, Andrei Robachevsky wrote: > Below is the proposed plan of ip6.int deprecation. Could you please > check if it is detailed enough to be properly coordinated, or if it > misses something. > > Andrei > > ip6.int deprecation plan > ------------------------- > > Advance Work: > > Contact Bill Manning at bmanning(a)vacation.karoshi.com and > hostmaster(a)ep.net before the 25th of May and ask him to schedule the > following: > > o June 1st 12:00 GMT: Remove all delegations within the 2.ip6.int zone. > > RIR Plan (common) > > o May 30th 12:00 GMT: Drop TTL on authoritative NS records within the > ip6.int zones to 3600. > > o June 1st 12:00 GMT: All delegations within the ip6.int zone are > removed. No RIR Action needed, other than checking. > > o June 1st 13:00 GMT - 23:59 GMT: All RIR's remove their respective > ip6.int zones from their servers. ........ while i noted the following: not all the zones or data in ip6.int are being removed.... so no, i am not changing the TTLs. the delegations that the RIR's have asked to be removed are scheduled for automatic removal. I will check on the process when i wake up roughly 3.5 hours later. I will be glad to send you email at that time to confirm removal. --bill ....... that being said, the RIR requested delegations have been removed from the IP6.INT zone. what remains is: # dig 2.ip6.int. axfr @::1 ; <<>> DiG 9.3.2 <<>> 2.ip6.int. axfr @::1 ; (1 server found) ;; global options: printcmd 2.ip6.int. 86400 IN SOA dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600 2.ip6.int. 86400 IN NS z.ip6.int. 2.ip6.int. 86400 IN NS dot.ep.net. 2.ip6.int. 86400 IN NS flag.ep.net. 0.0.1.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 0.0.1.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 0.0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 1.0.1.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 1.0.1.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 1.0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 2.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 2.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 2.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 2.ip6.int. 86400 IN SOA dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600 ;; Query time: 4 msec ;; SERVER: ::1#53(::1) ;; WHEN: Thu Jun 1 06:44:20 2006 ;; XFR size: 14 records (messages 14) --bill

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '06

31 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18353 descr: Route set advertised to AS9439 by HDS - AS18353 members: 202.55.96.176/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: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18353 descr: advertised to AS9439 by Revera - AS18353 members: 202.55.99.0/24^24-29, 202.55.96.176/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: Marc.Nienkemper(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060601 source: NZRR

1 0

FW: GGIS Service Message : Major
by Paul Adshead 31 May '06

31 May '06

FYI -----Original Message----- From: noc(a)global-gateway.net.nz [mailto:noc(a)global-gateway.net.nz] Sent: Thursday, 1 June 2006 00:28 To: global-gateway outage contacts Subject: GGIS Service Message : Major GGIS Backbone Update Global-Gateway Internet is currently experiencing service disruption which began at 21:40 hrs, 31/05/06date You are likely to experience major international congestion of your service until this problem is resolved. A cable fault has been identified in the USA near San Francisco. Currently, we are have no expected time for restoration. GGIS apologises for any inconvenience to you or your customers, and an update will follow within 2 hours. Logged by Andrew Murray on Thu Jun 1 00:27:59 2006

3 2

Police Hoax Email
by Keith Davidson 30 May '06

30 May '06

Just a heads up for anyone not aware of this... Keith Davidson www.police.govt.nz/news/release/2445.html Hoax police email 10:03am 31 May 2006 A hoax email is circulating within New Zealand which purports to be a notification from NZ Police. The email has this subject line - "Notification from Police New_Zealand" The email is clearly a hoax but is causing some concern in the public with callers contacting police for clarification. The email suggests that recipients are "under suspicion of financial machination." It then asks receivers to fill in details and fax or email details. Police are investigating the email which does contain a trojan virus. The virus will be filtered out so long as computers have anti-virus software on their machines. Members of the public who are receiving the email with the subject line - "Notification from Police New_Zealand" - should simply delete it and do not need to contact Police about the matter. ENDS

1 0

wireline.co.nz domain
by Grant Zanetti 30 May '06

30 May '06

Can anyone at telecom tell me why they're sending emails from this domain (wireline.co.nz) when it has no useful DNS? Where is my mail system supposed to send bounces etc?

1 0

Podcasting Heads Up
by Webmaster 29 May '06

29 May '06

Operators should be aware that due to increased demand on our podcasting service, and the number of requests we've had to increase the quality of the files, we'll be increasing the data rates of all files offered from our US mirror. At the moment all US files have the same names as NZ hosted files, but are actually lower rates. Over the next 2 weeks this will change, with the US server becoming a full mirror. The data rates of files will double (from 24k to 48k) to match those hosted in NZ. We've been able to do this because we have extra capacity in the US and can serve the extra traffic at no additional cost to us. At present NZ bound traffic from the US server sits at 10-15 Mb/s during the day. Local operators who do not peer with our NZ servers will see an increase in international inbound traffic (about double) from the US mirror over the next two weeks. After that you should allow for an increase of 10-15% per week - our current growth rate. Those who peer with our servers in New Zealand are not affected by this change. regards, Richard Hulse Radio NZ

1 0

[Fwd: APNIC ip6.int services to end 1 June 2006]
by Andy Linton 29 May '06

29 May '06

Not that this isn't because the IPv6 camp are giving up and going home. (:-) andy -------- Original Message -------- Subject: APNIC ip6.int services to end 1 June 2006 Date: Mon, 29 May 2006 21:31:42 +1000 From: sanjaya(a)apnic.net To: asjl(a)citylink.co.nz Dear colleagues, APNIC will cease all ip6.int reverse delegation services at approximately 10:00 UTC+10 (00:00 UTC) on 1 June 2006. At that time, APNIC will withdraw the delegations for the following sub-domains under 1.0.0.2.ip6.int: 2.0.1.0.0.2.ip6.int 3.0.1.0.0.2.ip6.int c.0.1.0.0.2.ip6.int d.0.1.0.0.2.ip6.int e.0.1.0.0.2.ip6.int f.0.1.0.0.2.ip6.int 4.4.1.0.0.2.ip6.int 5.4.1.0.0.2.ip6.int 8.1.0.0.2.ip6.int 9.1.0.0.2.ip6.int a.1.0.0.2.ip6.int All ip6.int delegations within these sub-domains will then cease to be recognised by most DNS resolvers (although cached delegation information may take some time to expire). APNIC will back-up all whois objects associated with these sub-domains and will continue to monitor DNS traffic during this period to review behaviour. However, as the IETF has formally deprecated ip6.int for reverse-DNS, re-delegation is not expected to occur. Regards, Sanjaya ______________________________________________________________________ Technical Services Manager <sanjaya(a)apnic.net> APNIC ph +61 7 3858 3100 http://www.apnic.net fx +61 7 3858 3199 ______________________________________________________________________

3 2

(no subject)
by Russell STREET 25 May '06

25 May '06

Hello.. . TelstraClear hosts this NZ root name server replica on its infrastructure. We are physically moving the servers that run this name server this weekend. This will cause an outage to ns4.dns.net.nz at around 6AM Saturday 27th May 2006 for around 2 minutes, when we migrate the routing for the name server from one site to the new site. Russell (TelstraClear IS Operations)

1 0

Re: [nznog] Cell Tax
by Mark Seward 25 May '06

25 May '06

Interesting numbers. After a few weeks of bad performance on an Internet feed I look after I was drawn back to an issue I thought was long buried. This circuit was dropping 4-5% of its traffic at well below advertised capacity. The delivery method was ethernet over ATM/AAL5 (RFC1483). The usual suspects were rounded up and shot (duplex and error counters, purple switches, the cleaning lady). The next question was overhead for cell tax and encapsulation. 12% seems to be the allowance by our supplier. IIRC this is the same as was used 10 years ago for ATM VCs delivered directly to routers (no ethernet involved); nanog has a few dusty posts about this number. It seems this is no longer enough. Perhaps average packet sizes have changed since then if 12% was ever a reasonable number. In the end our supplier ramped overhead to about 20% and the pipe has performed nicely since. For an ethernet service, I don't understand why they don't simply provision the VC (VBR) as large as the customer bearer can handle and let the end devices do the shaping. Michael's numbers including AAL5 padding give this new figure some context: Upstream: cell tax = 14.84% (18.09% AAL5) Downstream: cell tax = 18.35% (23.43% AAL5) Is anyone aware of a recent study of packet size distribution on Internet traffic? CAIDA have some information from the AIX in 1999, NLANR from '97, and Sprint do a semi-regular dump from their ipmon project. http://www.caida.org/analysis/AIX/plen_hist http://www.nlanr.net/NA/Learn/packetsizes.html http://ipmon.sprint.com/packstat/packetoverview.php >From netflow stats on this link, I see a similar story with 64, 576 and 1536B being the points of most interest. The percentage of 1536B packets (~25) I think is larger now than previously. Has anyone had similar frustrations with PVC dimensioning? Does anyone else still use ATM? :) Mark. On 5/23/06, Michael Newbery < Michael.Newbery(a)team.telstraclear.co.nz> wrote: > > Prompted by Mark Seward, we have had a look at the cell tax incurred for > our > customers, in those cases where we are unfortunate enough to have to > transit > an ATM pipe. Which has not been the usual case on our network but becomes > interesting for things like UBS. > > This enables us to answer the question: for a pipe of x bps sufficient to > carry pure IP, how much bigger must the ATM PVC be to carry the same load? > > > IP_bw = x > ATM_bw = ceiling(x/48)*53 > Diff = ATM_bw - IP_bw > Cell_tax = Diff/IP_bw > > For a sample SAMP, we calculate the mean cell tax as > (sum(ceiling( SAMP/48)*53) - sum(SAMP))/sum(SAMP) > > Looking at a 24 hour sample, we get: > Upstream: cell tax = 14.84% > Downstream: cell tax = 18.35% > > I understand that this is somewhat at variance with the standard > provisioning rules applied by another provider. > -- > Michael Newbery IP Architect TelstraClear Limited > Tel: +64-4-920 3102 Mobile: +64-29-920 3102 Fax: +64-4-920 3361 > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

2 1

InternetNZ Internet Governance Positions
by Keith Davidson 24 May '06

24 May '06

Pardon the intrusion and slightly off topic subject: Interested in Internet governance? InternetNZ is recruiting directors to sit on the Board of its subsidiary company, New Zealand Domain Name Registry Ltd (trading as .nz Registry Services or "NZRS"); and members to sit on the .nz Oversight Committee ("NZOC"), which has stewardship of the .nz domain name space. These positions provide an exciting opportunity to contribute to the good governance of the .nz domain name space. Company directors and those with general governance skills are encouraged to apply for the appropriate positions. The retiring incumbents are eligible for reappointment. Complete descriptions and application details for both roles can be found online at www.internetnz.net.nz/vacancy. More information on the Office of the Domain Name Commissioner can be found at www.dnc.org.nz; and about the registry company at www.nzrs.net.nz. Applications by email to vacancy(a)internetnz.net.nz are invited from suitably qualified people, and close at midnight on Saturday 3 June. Please follow the links above for further details. If you are aware of anyone who you feel would be appropriate for one of the vacancies, we would be most grateful if you could forward this information to them. Furthermore, it is coming up to AGM time for InternetNZ and we are always on the lookout for enthusiastic people to serve on our Council and various committees and working groups. Links to further details on these positions are at www.internetnz.net.nz/vacancy. Any successful recruitment from a connection with NZNOG will result in a reward of provision of beer to all associated. Regards Keith Davidson Executive Director - InternetNZ

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 May '06

24 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060523 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060525 source: NZRR

1 0

Xtra mail issues to AOL.com
by Drew Broadley 24 May '06

24 May '06

Could someone on Xtra's side please contact me offlist in regards to this. In the last four plus days this has happened and mail coming from AOL to Xtra is fine. -----Original Message----- From: "Mail Administrator"<Postmaster(a)xtra.co.nz> Sent: 25/05/06 8:54:57 a.m. To: "goldenfleece(a)clear.net.nz"<goldenfleece(a)clear.net.nz> Subject: Mail System Error - Returned Mail This is a system generated message. Please DO NOT REPLY. Your message was not delivered for the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 4 days and 0 hours. Host aol.com is not responding. The following recipients did not receive this message: <wooluk(a)aol.com> For more information on why this message wasn't delivered, and an explanati [Message truncated. Tap Edit->Mark for Download to get remaining portion.]

1 1

for those who have spare time today and aren't here.....
by Richard Naylor 22 May '06

22 May '06

http://www.r2.co.nz/20060524/

2 1

Sorbs - Further Notification
by Bruce Harding 22 May '06

22 May '06

For those using Sorbs for any sort of blocking, you may have trouble receiving mail from Inspire Net now that they have chosen to block our 2 primary Mail servers. -- Bruce Harding Inspire Net Ltd Phone : 06 357 8559 Fax : 06 353 1154 Mobile : 021 519 024

3 2

Re: [nznog] DNS lookup for IPs of healthalliance.co.nz
by Clement Ashwal 22 May '06

22 May '06

Thanks for all your inputs guys. Since 2:15pm the nslookup for the URLs and also to all the SMTP servers hosted by Healthalliance have started to work by itself without anybody having to do any changes. I did get in touch with the Healthalliance techs and they seemed to have done nothing at all. Quite mysterious I must say. Hope it continues to work without any disruptions. Clement Ashwal Sr Network Analyst The University of Auckland + 6493737599 x 87993 -----Original Message----- From: jfp [mailto:jfp(a)clearfield.com] Sent: Tuesday, 23 May 2006 1:42 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] DNS lookup for IPs of healthalliance.co.nz Well it looks like ns1.healthalliance.co.nz is down. dig www.healthalliance.co.nz @210.54.1.142 works dig www.healthalliance.co.nz @210.54.1.143 fails. given the the reverse DNS for 210.54.1.143 and 210.54.1.142 is also on those servers, you're going to get timeouts galore. ns1.healthalliance.co.nz. 86400 IN A 210.54.1.143 ns2.healthalliance.co.nz. 86400 IN A 210.54.1.142 jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 May '06

22 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060523 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 May '06

22 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060523 source: NZRR

1 0

Cell Tax
by Michael Newbery 22 May '06

22 May '06

Prompted by Mark Seward, we have had a look at the cell tax incurred for our customers, in those cases where we are unfortunate enough to have to transit an ATM pipe. Which has not been the usual case on our network but becomes interesting for things like UBS. This enables us to answer the question: for a pipe of x bps sufficient to carry pure IP, how much bigger must the ATM PVC be to carry the same load? IP_bw = x ATM_bw = ceiling(x/48)*53 Diff = ATM_bw - IP_bw Cell_tax = Diff/IP_bw For a sample SAMP, we calculate the mean cell tax as (sum(ceiling( SAMP/48)*53) - sum(SAMP))/sum(SAMP) Looking at a 24 hour sample, we get: Upstream: cell tax = 14.84% Downstream: cell tax = 18.35% I understand that this is somewhat at variance with the standard provisioning rules applied by another provider. -- Michael Newbery IP Architect TelstraClear Limited Tel: +64-4-920 3102 Mobile: +64-29-920 3102 Fax: +64-4-920 3361

1 0

DNS lookup for IPs of healthalliance.co.nz
by Clement Ashwal 22 May '06

22 May '06

Hi, If somebody could throw some light on this issue would very much appreciate. We are having problems resolving few of the following URLs from our DNS servers at the University. www.countiesmanukaudhb.org.nz <http://www.countiesmanukaudhb.org.nz/> webmail.middlemore.co.nz www.waitematahealth.co.nz <http://www.waitematahealth.co.nz/> www.healthalliance.co.nz and others. All these names are registered with Healthalliance. There have been no changes to our DNS whatsoever and the reverse-lookups are working fine. Clement Ashwal Sr Network Analyst - ITSS The University of Auckland Private Bag 92019 Auckland New Zealand Phone + 64 9 3737599 x 87993 CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately.

6 5

SORBS still listing Telecom static IPs as dynamic...
by Paul Adshead 22 May '06

22 May '06

It appears that SORBS are atill listing Telecom static IP ranges (- which my address is in,) as dynamic ranges. Wasn't this in the process of being fixed weeks/months ago? Does anyone have any ideas on how long this is going to be until it's resolved? The whole SORBS situation over the past months is becoming a total joke, with mail admins I know turning off their use of SORBS - there is just far far far too many false positives... :-( Paul. -----Original Message----- From: System Administrator Sent: Thursday, 18 May 2006 15:58 To: <customer> Subject: Undeliverable:RE: <mail subject> Your message did not reach some or all of the intended recipients. Subject: RE: <mail subject> Sent: 18/05/2006 15:58 The following recipient(s) could not be reached: Robert Reid on 18/05/2006 15:58 You do not have permission to send to this recipient. For assistance, contact your system administrator. <mailserver.mycompany.co.nz #5.7.1 smtp;554 5.7.1 Rejected 210.55.xx.xxx is a dynamic IP (see: http://www.au.sorbs.net/faq/dul.shtml for more information)>

13 21

IPv6 allocation and APNIC
by Brendon Wyber 22 May '06

22 May '06

Hi, Anyone had experience with getting a range of IPv6 numbers allocated to them through APNIC? Does NZ have the equivalent of a NIR (National Internet Registry) set up for allocation of IPv6? Cheers Brendon ========================================= Brendon Wyber, Wide Area Network Consultant, IT Department, University of Canterbury, Private Bag 4800, Christchurch, New Zealand. Phone: +64 3 364 2336 Fax: +64 3 364 2332 email: brendon.wyber(a)canterbury.ac.nz

3 2

IHUG Peering policy
by Simon Allard 22 May '06

22 May '06

Hi NZNOG :-) IHUG is changing its peering policy for peering over WIX and APE. We will no longer be directly peering with our current peers but will continue to peer with the route reflectors. Customers of IHUG who require APE/WIX peering directly will not be affected by this policy. This change is not because we don't like peering; it's just our way of trying to make our network simpler to manage. We are aware that some isp's are not huge fans of the route reflectors and prefer direct peering. We have heard all the arguments about why direct peering is much better than the "evil route reflectors of doom", but we personally have had no problems with them and they have proven to be reliable. If you have any questions, please contact me off list. Thank you :-) Simon Allard Ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Re: [nznog] Routing question
by Justin Cook 21 May '06

21 May '06

Thanks to everyone who responded, particularly JSR. All sorted and working great.

1 0

Routing question
by Justin Cook 21 May '06

21 May '06

Quick question from a routing noob: I've just acquired 210.48.96.88/30. The two IP addresses in the block are intended for a couple of vmware instances. We're not using anything nice like a Cisco router, just a Linksys stand-in for now. It has some basic static routing capabilities. I had a short conversation with Iconz support but I'm not feeling very confident about the result. I've been instructed (or rather I said "this is what we came up with" and I got a vague "yes") to add the following entry to the routing table (where 202.37.231.84 is the existing IP that we're using as an external address): Destination: 210.48.96.88 Subnet: 255.255.255.252 Gateway: 202.37.231.84 Interface: Local It's the gateway bit we're unsure of - won't this cause a loop? My mate is concerned that it's not going to work as it needs to be on the same subnet. Cheers Justin

3 3

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by IHUG - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: pshem.k(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by IHUG - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: pshem.k(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Are there any blakjak.net mail admins on this list?
by Juha Saarinen 20 May '06

20 May '06

The subject of the message is: Re: [nznog] SORBS still causing serious problems... The address to which the message has not yet been delivered is: blakjak(a)blakjak.net Delay reason: SMTP error from remote mail server after RCPT TO:<blakjak(a)blakjak.net>: host mx.blakjak.net [202.50.176.75]: 451 Dynamic IP Addresses See: http://www.sorbs.net/lookup.shtml?xxx.xxx.xxx.xxx "Does this not go back to people using the dnsBL the wrong way... (!) People who choose to use them to _drop_ mail need to instead be using them to _score_ mail... Surely people who are losing mission-critical services due to this should instead be petitioning relevant ISPs to change their dnsBL practises?" Yes yes! I agree! On a more serious note, even Outblaze bounces messages now based on the wrong SORBS listing. @#(*)^$@!!! -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

2 2

E mails
by suzanne gerrard 20 May '06

20 May '06

3 2

Ihug Mail Admin?
by Erin Salmon - Unleash 20 May '06

20 May '06

Hi, If there are any Ihug Mail Admins floating around on the list would you be so good as to put your hand up? One of your customers is sending out thousands of promo newsletters with several images attached. It has been running since Friday and a number of our clients are already facing several hundred dollar excess usage charges from our good friends at Telecom from downloading it all. They have stupidly put the addresses in the CC field, and I believe the problem may be that some of the CC field recipients are running MS Exchange 2000. There is a bug if it is configured for open relaying which resends emails to the list of addresses if there are more than a certain number. I recall having this issue a year or two ago, but Im a bit hazy on the details, and Im not a mail guru myself. The KB seems to be taking this convenient moment to throw an error when I try to search it. If I recall correctly, SP3 for Exchange 2000 fixed the problem, so with any luck there would only be only server in the recipient list with the problem and we can stamp it out. If anyone recalls this Exchange issue, Id appreciate a steer too. Cheers, Erin Salmon Managing Director Unleash Technology Solutions <http://www.unleash.net.nz/> Phone: +64 3 365 1273 Mobile: +64 21 877 913 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.6.1/344 - Release Date: 19/05/2006

3 3

Static IP in a hurry ?
by Richard Naylor 19 May '06

19 May '06

Anyone from Xtra online tonight ? I have one of your customers who needs a static IP number in a hurry. A family member has died and they're webcasting the tangi. We've had 3 number changes in as many minutes. - They'll pay. Rich

1 1

SORBS still causing serious problems...
by Kris Angerano 19 May '06

19 May '06

Heya NZ guys. I work for an ISP out in Oregon US (EasyStreet). And we have recently been hit hard by the mistakes at SORBS. They have mistakenly added our 209.x static group as a dynamic IP range and blocked them all. This has been happening for 5 days now. We have submitted tickets to Matthew and his crew describing the problem and we even gave him our entire Dynamic and Static IP Blocks. To no avail, our RT ticket sits there untouched and the problem is unresolved. RT 77734, 76636 The worse part is we use SORBS, so initially we couldn't even receive some of our own customers email. Since then we have whitelisted our own IP block to solve that problem. But that isn't even a band aid. I called Matthew yesterday and he explained to me about his current 'troubles' so I didn't give him a hard time about our ticket. But this is getting ridiculous. A significant part of our 209.x block is business customers with their own mail servers. They are getting frustrated and we may start to lose business because of this. If anyone cares or has their eyes open out there, we need some help please! Thanks, Kris A

5 5

Re: [nznog] SORBS still listing Telecom static IPs as dynamic...
by Donald Neal 18 May '06

18 May '06

> > > > Please don't use American English. Won't someone please think of the > > children! > > > > American English, thats an oxymoron isnt it ? > I have no doubt of the relevance of most of this thread, but it seems to have now run its course. - Donald Neal List Asministrator Donald Neal |"Email is not to be used to pass on Support Engineer |information or data. It should be NGN Operations |used only for company business." Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

1 0

Re: [nznog] SORBS still listing Telecom static IPs as dynamic...
by Scott Weeks 18 May '06

18 May '06

----- Original Message Follows ----- From: "Jamie Riden" <jamesr(a)europe.com> > > No other blacklist operates like - or generates the hate > > - that S(ORBS) does. > > Actually, I've seen people say that and worse about every > single blacklist including SBL, which is probably the most > conservative one, all the way back to the MAPS original. They all say that if you're not a spammer, you have to pay LOTS of money to people they tell you to pay to be delisted? http://www.au.sorbs.net/faq/spamdb.shtml "Third and finally, if you are really not a spammer, or you are truly reformed, de-listing is relatively easy. You donate US$50 to a charity or trust approved by, and not connected with, SORBS for each spam received related to the listing. This is referred to as the SORBS 'fine'." scott

5 4

Re: [nznog] SORBS still listing Telecom static IPs as dynamic...
by Jeremy Strachan 18 May '06

18 May '06

My view is SORBS is a crock of shit, as was ORBS. If the day ends in "y" they block it ... Its called all care - no responsibility... They will blacklist entire (static) IP ranges with no warning, and no realistic way of removing the block, and treat everyone like s..t. The process is inherently flawed, because of the way static ranges end up on their list without reasonable checks. If they blocked a single IP address - then fine, its their wholesale and cavalier attitude to blocking entire ranges that is the root cause of the problem I have with S(ORBS), and why they are hated so much by people like me. No other blacklist operates like - or generates the hate - that S(ORBS) does. If they vanished tommorrow, the world would be a better place. Jeremy -----Original Message----- From: Tony Wicks [mailto:tony(a)prophecy.net.nz] Sent: Thursday, 18 May 2006 7:06 p.m. Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] SORBS still listing Telecom static IPs as dynamic... >> > One would wonder why any sane mail admin wouldnt pull data from as > many sources as possible when deciding on how to score spam. > Sure, but surely there has to be some measure of accuracy involved ? I mean SORBS is about as accurate as choosing every even IP address on Monday and public holidays, every odd one on every other day. It's just not even close to being what it is supposed to be billed as. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

ANZ Phish
by Joseph Miller 16 May '06

16 May '06

Just a heads-up: I just got sent a phishing scam email for the ANZ... Subject is ANZ Account Security Measures, included link ends up at: http://www.sunrise.cc/bbs/anz.php Relevant parts of the header as follows: Received: from [210.205.6.77] (helo=web-77.blueweb.co.kr) by exorsus.net with esmtp (Exim 4.52) id 1FgAyH-0006MQ-Oq for joff(a)XXXXXXXX.com; Wed, 17 May 2006 13:37:15 +1200 Received: (from apache(a)localhost) by web-77.blueweb.co.kr (8.11.6/8.11.6) id k4H1avJ20690; Wed, 17 May 2006 10:36:57 +0900 Date: Wed, 17 May 2006 10:36:57 +0900 Message-Id: <200605170136.k4H1avJ20690(a)web-77.blueweb.co.kr> To: joff(a)XXXXXXXXXXX.com Subject: ANZ Account Security Measures From: <service(a)anz.com> Reply-To: service(a)anz.com -- Thanks, Joseph Miller Application Developer _________________________________________ http://www.digiweb.co.nz Webhosting, Dedicated Servers, E-commerce Phone: (64 3) 351 6713 PLEASE NOTE: The information contained in this email message and any attached files may be confidential and subject to privilege. The views expressed may not necessarily be the official view of Digiweb New Zealand Limited. All technical advice and opinions are offered on a 'no-liability' basis. If you are not the intended recipient, you are notified that any use, disclosure or copying of this email is unauthorised. If you have received this email in error, please notify us immediately by reply email and delete the original. Thank you.

1 0

Xtra Nationwide outage?
by Tristram Cheer 15 May '06

15 May '06

Anybody know anything about this? I got phones ringing off the hook from people saying xtra's got a nationwide outage right now. Rat got their cable again? -- ----------------------- Tristram Cheer UberNetworks Level 1 2a Vine St Whangarei 0101 M:021-715-823 W:09-438-5472 F:09-438-5473

6 6

Xtra on Spamcop now.
by Chris Hodgetts 14 May '06

14 May '06

May 15 11:12:35 caitlin postfix/smtpd[20038]: NOQUEUE: reject: RCPT from fep03.xtra.co.nz[210.54.141.243]: 554 Service unavailable; Client host [210.54.141.243] blocked using bl.spamcop.net; Blocked - see http://www.spamcop.net/bl.shtml?210.54.141.243; from=<someuser(a)xtra.co.nz> to=<user(a)domainname.com> proto=ESMTP helo=<fep03.xtra.co.nz> May 15 11:12:35 caitlin postfix/smtpd[20038]: disconnect from fep03.xtra.co.nz[210.54.141.243]

6 5

Re: [nznog] Xtra on Spamcop now.
by Ted Grenfell 14 May '06

14 May '06

So a particular customer of ours is having all email from you marked up as spam? Kind Regards, Ted Grenfell ISP Performance Manager T +64 9 359 5854 (extn 93254) F +64 9 377 0781 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford Street, Private Bag 92028, Auckland CBD, New Zealand ________________________________ "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." > -----Original Message----- > From: Joseph Miller [mailto:joseph(a)digiweb.net.nz] > Sent: Monday, 15 May 2006 11:47 a.m. > To: Ted Grenfell; nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Xtra on Spamcop now. > > Ted Grenfell wrote on 15/05/06 11:35: > > What IP addresses are you sending to Joseph? > Sending to mta.xtra.co.nz (210.54.141.1) > > > Any logs you can flick through? > I'll get our mail admin to dig up some SMTP delivery logs when he gets a > spare second, and we've got > someone who's going to send us some mail headers from a junked mail > > > What exactly do you mean by "Junked"? > All the mail is being put in the xtra customer's Junk mail folder > > > > > -- > Thanks, > Joseph Miller > Application Developer > _________________________________________ > http://www.digiweb.co.nz > Webhosting, Dedicated Servers, E-commerce > Phone: (64 3) 351 6713 > > PLEASE NOTE: The information contained in this email message and any > attached files may be > confidential and subject to privilege. The views expressed may not > necessarily be the official view > of Digiweb New Zealand Limited. All technical advice and opinions are > offered on a 'no-liability' > basis. If you are not the intended recipient, you are notified that any > use, disclosure or copying > of this email is unauthorised. If you have received this email in error, > please notify us > immediately by reply email and delete the original. Thank you.

3 2

Re: [nznog] Xtra on Spamcop now.
by Joseph Miller 14 May '06

14 May '06

Ted Grenfell wrote on 15/05/06 11:35: > What IP addresses are you sending to Joseph? Sending to mta.xtra.co.nz (210.54.141.1) > Any logs you can flick through? I'll get our mail admin to dig up some SMTP delivery logs when he gets a spare second, and we've got someone who's going to send us some mail headers from a junked mail > What exactly do you mean by "Junked"? All the mail is being put in the xtra customer's Junk mail folder -- Thanks, Joseph Miller Application Developer _________________________________________ http://www.digiweb.co.nz Webhosting, Dedicated Servers, E-commerce Phone: (64 3) 351 6713 PLEASE NOTE: The information contained in this email message and any attached files may be confidential and subject to privilege. The views expressed may not necessarily be the official view of Digiweb New Zealand Limited. All technical advice and opinions are offered on a 'no-liability' basis. If you are not the intended recipient, you are notified that any use, disclosure or copying of this email is unauthorised. If you have received this email in error, please notify us immediately by reply email and delete the original. Thank you.

1 0

Hosting Providers w/ unlimited traffic plans
by Jonathan Brewer 14 May '06

14 May '06

Hi Folks, We would like to hear from any web hosting provider with unlimited international traffic plans (rate shaped) or arrangements for dual US/NZ servers. A menu of service like "3U box hosting = $n, international traffic @ $n per 64kbps would be appreciated. Cheers, Jon ------------------------- Araneo Limited 230B Left Bank Cuba Street Wellington 6001 Ph: 04 978 7350 Fx: 04 978 7355 Mb: 021 345 054 http://www.araneo.net.nz/ -------------------------

1 0

Re: [nznog] Community Attributes
by Philip D'Ath 11 May '06

11 May '06

Perhaps a good place to start would be to get APE and WIX to implement a common policy, and then those that peer at those locations are likely to follow suit. -----Original Message----- ... Another thing I've also been thinking about is community attributes. Using it to turn on remote blackholing with upstreams is useful, and we saw at NZNOG the approach to communicate enhancements or variations of that. But lowest common denominator suggests that using an agreed set of community attributes (which works for everyone) to convey stuff is something that should be worked on first. So, combining an agreed set of local_pref's and some community attributes might be the basis of building a broader, and faster exchange between participants. Community String Attributes 1000 Route is locally-originated, and should be exported 1000 Route is locally-originated, but should be suppressed towards peers 1002 Route is a blackhole route 1100 Route was learnt from a customer 1200 Route was learnt from a peer 1300 Route was learnt from a backbone 1400 Route was learnt from a transit provider (domestic/international) Local Preference Values 130 - locally-originated 120 - customers 110 - peers 90 - backbone 85 - domestic 80 - international ...

3 4

Latest Opera Version (8.52) and Secure Sites
by Craig Whitmore 11 May '06

11 May '06

Just a headsup to NZ ISP's who may have customers using the latest version of Opera and unable to connect correctly to some secure sites such as the ANZ Bank Website. http://my.opera.com/community/forums/topic.dml?id=138010 Thanks Craig Whitmore

1 0

Your Local 'Local Preference' Preferences
by jamie.baddeley＠vpc.co.nz 09 May '06

09 May '06

Hi, Snazzy subject line huh? ;-) Anyway, Was pondering the impact of path-stuffed networks being announced into the APE combined with operators not actually setting APE learnt routes with a higher local pref. In other words, how many operators out there are not preffing up APE learnt routes? Cheers jamie

5 5

APNIC 22 update #2
by Nurani Nimpuno 09 May '06

09 May '06

Hi NZNOG:ers, I'm forwarding on an update about the APNIC 22 meeting in September. If you have any questions about it, don't hesitate to shoot me a mail. Also, if you want an invitation letter (pdf, or printed and posted to you), contact me and I can arrange it. Cheers! Nurani ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Asia Pacific Network Information Centre Ph :+61-7-38583100 PO Box 2131 Milton, QLD 4064 Fax:+61-7-38583199 Australia http://www.apnic.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [Apologies for duplicates] APNIC 22 update #2 Invitation to APNIC 22 ______________________________________ 22nd APNIC Open Policy Meeting 4-8 September, 2006, Kaohsiung, Taiwan ______________________________________ Dear APNIC members and friends, It is our pleasure to invite you to attend the 22nd APNIC Open Policy Meeting, being held in Kaohsiung, Taiwan. Hosted by TWNIC (Taiwan Network Information Center), APNIC 22 includes an innovative program that showcases presentations on operational Internet issues. Details of the program will be released closer to the meeting; however, a draft schedule is now available at: http://www.apnic.net/meetings/22/program Contents -------- 1. Meeting registraion is open 2. APNIC fellowships 3. Sponsorship opportunities 4. Visa information 1. Meeting registration ---------------------- Meeting registration site is now open. Please visit: http://www.apnic.net/cgi-bin/registration.pl?event_id=90 Early bird registration will end on 14 July, 2006. 2. APNIC fellowship ------------------- The APNIC fellowship program provides basic assistance to Internet professionals from developing economies around the region. If you are interested in applying for an APNIC 22 fellowship, please visit: http://www.apnic.net/meetings/22/fellows The deadline for applications is 26 May, 2006. 3. Sponsorship opportunities ---------------------------- Sponsoring an APNIC meeting will provide you with a range of opportunities to expose your organisation to the Asia Pacific Internet community. If your organisation is interested in sponsoring APNIC 22, please visit: http://www.apnic.net/meetings/22/sponsors 4. Visa information ------------------- Some meeting attendees may require a visa to visit Taiwan. Attendees who require a visa should apply promptly after completing the meeting registration to ensure that the visa is issued on time. All necessary information can be found at: http://www.apnic22.tw/apnic22_visas.htm Any questions? Please contact the APNIC Secretariat at <meetings(a)apnic.net>. We look forward to seeing you in Kaohsiung! Regards, ______________________________________________________________________ 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 ---------------------------------------------------------------------- See you at APNIC 22! Kaohsiung, 4-8 September, 2006 www.apnic.net/meetings ______________________________________________________________________

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 May '06

09 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS9897 as-name: NZRR-AS9897 descr: jsr.com descr: APE peering at '192.203.154.102' descr: see Citylink RT job #5456 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9897 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jsr(a)jsr.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9897 descr: Route set advertised to AS9560 by jsr.com - AS9897 members: 202.49.89.0/24^24-29, 205.233.243.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: jsr(a)jsr.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 May '06

09 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR

1 0

New IP ranges for Xtra's email platform
by Ted Grenfell 08 May '06

08 May '06

Very shortly (later this week or early next week) we will be modifying DNS entries for Xtra's SMTP servers to point to a new email platform and we would like to draw your attention to the new network IP address ranges that will then be in use as per below: 210.54.141.0/24 210.55.11.0/24 If you've configured any of the existing Xtra mail server IP's in to any of your systems then it might be worthwhile adding the above ranges as well taking note not to delete any existing entries as that may impact normal delivery at this time. If you rely solely on DNS for selecting IP's to deliver email through to Xtra's SMTP servers then you do not need to make any changes. -- Kind Regards, Ted Grenfell ISP Performance Manager T +64 9 359 5854 (extn 93254) F +64 9 377 0781 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz <mailto:ted.grenfell(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 11, Telecom House, 8 Hereford Street, Private Bag 92028, Auckland CBD, New Zealand ________________________________ "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."

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 08 May '06

08 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.37.129.0/24^24-29, 202.49.34.0/23^23-29, 202.50.109.0/24^24-29, 202.180.64.0/18^18-29, 203.97.152.0/24^24-29, 203.100.208.0/20^20-29, 203.184.0.0/18^18-29, 203.215.142.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: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-27, 202.37.22.0/24^24-27, 202.37.129.0/24^24-27, 202.49.34.0/23^23-27, 202.50.109.0/24^24-27, 202.180.64.0/18^18-27, 203.97.152.0/24^24-27, 203.100.208.0/20^20-27, 203.184.0.0/18^18-27, 203.215.142.0/23^23-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR

1 0

FYI: Trademe phish ...
by Jamie Riden 08 May '06

08 May '06

Haven't seen a trademe phish before. The actual link goes to http://www.furutech.co.kr/bbs/data/trademe.php . You might want to warn and filter. cheers, Jamie Subject: TradeMe Account Security Measures Dear foo(a)example.co.nz , We recently noticed one or more attempts to log in to your TradeMe account from a different IP addresses. If you recently accessed your account while traveling, the unusual log in attempts may have been initiated by you. However, if you did not initiate the log ins, please visit TradeMe as soon as possible to check-up your account information: http://www.trademe.co.nz/members/login.aspx Thanks for your patience. Sincerely, TradeMe ---------------------------------------------------------------- Please do not reply to this e-mail. Mail sent to this address cannot be answered. Email ID 376223

1 0

[Fwd: Skybox Security Solutions announcement]
by Justin Cook 07 May '06

07 May '06

Some interesting spam I received. Reading through it I noticed they claim to test your security with a botnet. Are these guys serious? I'm guessing that the only definition of' 'botnet' out there these days is an armada of compromised PCs. -------- Original Message -------- Subject: Skybox Security Solutions announcement Date: Mon, 08 May 2006 10:00:21 +0800 From: <114_reunited(a)jaydees.net> Reply-To: <114_reunited(a)jaydees.net> Skybox Security Solutions *Simulated DDoS Network Attacks and Network Intrusions* *Customer Challenge: * Large corporations often hire consultants to conduct quarterly penetration (DDoS) testing on specific segments of their corporate network. This testing can cost over hundreds of thousands of dollars, and also exposes the network to many potential disruptions. These disruptions are the result of the intense DDoS attacks testers can impose on live networks in order to isolate vulnerabilities and weaknesses. Since the network is constantly changing, and DDoS attacks are rarely dispersed from a centralized location, the penetration test results often become nullified and end up being limited to a small portion of the total network. *The Skybox Solution: *Skybox Security performs accurate and non-intrusive DDoS attacks across a larger portion of the corporate network. The tests are modeled and analyzed through an automated process via our large botnet network rather than manually performed on a live network. As a result, the tests are repeated rigorously on a scheduled basis without any fear of network disruption. Through DDoS attack and access simulation, vulnerability exposures as well as security control weaknesses are revealed instantly. DDoS attack simulation discovers all possible attack scenarios and reveals the step by step process that an attacker or worm may follow. It illustrates specific vulnerabilities to be exploited and network access traversed for each exploitable path. Access simulation calculates network access privileges determined by firewall and routing configuration. Our botnet helps characterize the interconnectivity between any two given points, reporting not just whether access is possible, but also the detailed path to reach a final destination. Based on these combined results, security personnel are able to determine what additional DDoS attacks are necessary and where to deploy our organizations penetration testers. *Awards:* Info Security - Info Security Hot Companies 2006 The Wall Street Journal - One of the most innovative companies in 2005 Information Security Magazine - Product of the year Network Magazine - Most Visionary Security Product Network Magazine - Best of the Best in all categories Secure Enterprise Magazine - Editor's Choice Gartner - " Cool Vendor " in the security & privacy space SC Magazine Awards 2006 Winner - The Best Security Solution for Financial Services IM2005 Award finalist - Information Security and Product of the Year *Company Profile:* Eran Reshef Founder, Chairman & CEO of Blue Security ( www.bluesecurity.com <http://www.bluesecurity.com>) A serial entrepreneur, Eran is currently the founder, chairman & CEO of Blue Security, the do-not-disturb registry pioneer. Prior to Blue, Eran co-founded Skybox Security and served as its Chairman. Prior to Skybox Eran founded and managed Sanctum (acquired by WatchFire), the leader in web application security. Eran holds a variety of security- related patents that are based on his inventions. Rina Shainski General Partner at Carmel Ventures ( www.carmelventures.com <http://www.carmelventures.com>) Following a successful career leading business development and R&D operations in high-growth software companies, Rina has been investing in software companies ever since. Before joining Carmel she served as the VP Business Development at Clal Industries and Investments where she was responsible for software investments. From 1989 to 1996, Rina held several managerial positions in Tecnomatix including VP Business Development and R&D Director. Rina serves on the boards of Followap Communications, Skybox Security, mFormation and Silicon Design Systems. Rina holds a B.Sc. degree in Physics from Tel Aviv University and a Master of Science degree in Computer Science from Weizmann Institute. *Contact Information:* 2077 Gateway Place, Suite 550 San Jose, California 95110 USA Phone: 866-6SKYBOX Phone: 408 441 8060 Fax: 408 441 8068 Regional Offices (Israel) 60 Medinat Hayehudim St. P.O.Box 4109 Herzliya Pituach 46140 Israel Phone: +972-9-9545922 Fax: +972-9-9545933

5 4

new netblocks for Callplus/Slingshot
by Kevin Stewart 07 May '06

07 May '06

We are about to start advertising our new address blocks at the APE and WIX 124.197.0.0 /18 and 203.160.112.0/20 here is our current prefix list ASN 9790 ip prefix-list callplus-networks seq 5 permit 124.197.0.0/18 ip prefix-list callplus-networks seq 10 permit 202.36.232.0 ip prefix-list callplus-networks seq 15 permit 202.37.22.0 ip prefix-list callplus-networks seq 20 permit 202.49.34.0/23 le 24 ip prefix-list callplus-networks seq 25 permit 202.50.109.0 ip prefix-list callplus-networks seq 30 permit 202.180.64.0/18 ip prefix-list callplus-networks seq 35 permit 203.97.152.0 ip prefix-list callplus-networks seq 40 permit 203.100.208.0/20 ip prefix-list callplus-networks seq 45 permit 203.160.112.0/20 ip prefix-list callplus-networks seq 50 permit 203.184.0.0/18 ip prefix-list callplus-networks seq 55 permit 203.215.142.0 ip prefix-list callplus-networks seq 60 permit 203.215.143.0 -- Kevin Stewart Network Engineer DDI ++ 64 9 919 6120 Mobile ++ 64 21 885 505 Email kevins(a)callplus.co.nz ----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.

2 1

Re: [nznog] Oh dear, no more room on the intarweb
by barry＠unix.co.nz 07 May '06

07 May '06

I'm sure majority of the devices would be added on an internal network such as telstra clears cable tv (digital) and cable modems (management), only 1 live ip is assigned for internet services. From memory a few mobile providers assign you a internal ip too and you're nat'ed out to the net. But yeah IPv6 is just around the corner. Thanks Barry > http://www.techweb.com/wire/networking/187200459 > > > -- > Juha Saarinen > www.geekzone.co.nz/juha > www.computerworld.co.nz > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

12 23

Re: [nznog] Oh dear, no more room on the intarweb
by Philip D'Ath 07 May '06

07 May '06

It allows each machine to have a globally unique IP address, without any form NAT. NAT breaks several protocols, and generally makes life more difficult. Also, if you want to use the same port for several machines (like 443) and you only have a single IP address then it makes life more difficult. For example, we have a single IPv4 address on a DSL tail. However, our entire network is IPv6 enabled using a 6to4 tunnel. We have several of our servers providing an https service. Thanks to IPv6 I can now easily browse to any of these servers from any of the remote locations that we have already IPv6 enabled. We are looking to actively start using IPv6 at many of our clients this year. We'll be using 6to4 tunnels again (because no one sells IPv6 transit ...). This means we can load a management agent on their machines, and have our server talk to those agents over a VPN. Normally we would have the grief of ensuring their private IP address range is different from all of our other client addresses ranges. With every machine having a globally unqiue IPv6 address this is no longer an issue. Of course, there is always an IPv4 RFC1918 clash, and we end up with the option of limited management, or a renumbering exercise. The sooner everyone adopts IPv6, and we can easily get native IPv6 transit the better. -----Original Message----- Still, I'm a little puzzled why a single IPv4 address (with lots of NAT behind it) is really any different from a single IPv6 prefix with lots of bits on the right hand side.

1 0

Re: [nznog] Oh dear, no more room on the intarweb
by Andy Linton 07 May '06

07 May '06

Joe complained that the Dancing Turtle wasn't enough justification to go to IPv6 but clearly the risk of eternal damnation should be a good reason. Devout Catholics will soon be issued with an IPv6 address at Mass on Sundays and those who don't have one that's regularly used.... -------- Original Message -------- Subject: [ipv6-wg] The Pope gets IPv6 PA space (not PI :) Date: Wed, 19 Apr 2006 09:28:30 +0200 From: Jeroen Massar <jeroen(a)unfix.org> Reply-To: jeroen(a)unfix.org Organization: Unfix To: v6ops(a)ops.ietf.org <v6ops(a)ops.ietf.org>, nanog(a)merit.edu <nanog(a)merit.edu> CC: ARIN PPML <ppml(a)arin.net>, ipv6-wg(a)ripe.net inet6num: 2a01:b8::/32 netname: VA-VATICAN-20060418 descr: Holy See - Vatican City State country: VA So now that IPv6 is officially blessed go deploy it :) Greets, Jeroen

1 0

search engine that shows illegal downloads
by Antonio Broughton 07 May '06

07 May '06

Hi, just found this news article.. http://tvnz.co.nz/view/page/411365/711264 what interested me most, was this "search engine" that allows the federation to see "any illegal downloading in New Zealand" 1) Is this something Telecom has come up with :) (couldn't resist it) 2) How do they determine if its illegal, or not just someones home made video of Debbie does Auckland etc 3) How would this be possible? The third question is the most serious one, just wondering how there could be a search engine that showed this information? This would have to be implemented at the backbone level? -- Antonio Broughton

5 4

Re: [nznog] Oh dear, no more room on the intarweb
by Philip D'Ath 06 May '06

06 May '06

I've tried to buy commercial IPv6 connectivity in NZ. I can't buy it, full stop. -----Original Message----- ... IPv6 has been well-and-truly implemented. It's the deployment that's missing. To replay a conversation that we had in Wellington earlier in the year: Deployment costs money; money requires budget; budget requires either revenue or cost reduction (or both). Who is willing to pay more for IPv6, given that pretty much the only extra content available for your money will be a lonely, somewhat poorly-animated Japanese turtle? (Don't all shout at once.)

2 1

Re: [nznog] Oh dear, no more room on the intarweb
by Philip D'Ath 06 May '06

06 May '06

How about every ISP in NZ. -----Original Message----- From: Lindsay Druett [mailto:lindsay(a)wired.net.nz] Sent: Sunday, 7 May 2006 8:09 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Oh dear, no more room on the intarweb ... Anyway, what doesn't support IPv6 now ? I'm picking that what doesn't support IPv6 now is more than likely to be either upgraded or in the bin by 2008.

1 0

Oh dear, no more room on the intarweb
by Juha Saarinen 06 May '06

06 May '06

http://www.techweb.com/wire/networking/187200459 -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 May '06

04 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060209 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 source: NZRR --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060209 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 source: NZRR

1 0

Re Xtra's Usenet Cancellations...
by Mark Foster 03 May '06

03 May '06

My little impromptu polls raised ~70 responses, results as follows: http://www.blakjak.net/node/495/results What are your thoughts on Xtra's decision to cancel its Usenet service? A smart move, handled appropriately. 3% (2 votes) A smart move, but badly implemented. 4% (3 votes) An understandable move, handled appropriately. 6% (4 votes) An understandable move, badly implemented. 40% (27 votes) A bad move, but the implementation was acceptable. 1% (1 vote) A bad move, and badly implemented. 45% (30 votes) Total votes: 67 http://www.blakjak.net/node/496/results Usenet: Usage Query. I use Usenet every day. 25% (18 votes) I use Usenet every few days. 13% (9 votes) I use Usenet once a week. 6% (4 votes) I use Usenet occaisionally. 11% (8 votes) I used to use it regularly, I don't anymore. 32% (23 votes) I'm aware of what Usenet is, but have never used it. 10% (7 votes) I've never heard of Usenet. 3% (2 votes) Total votes: 71 It seems that whilst opinion is divided as to whether cancelling their usenet service was a bad move or not, there is general agreement that the way in which this was actioned was 'bad' (tm). In fact it seems that only 7 votes from 67 - or a fraction over 10% - think that it was done well. Speaks for itself, doesn't it? Also interesting to see that certainly from the NZNOG community - and a few other smallish communites I circulated the poll to - Usenet still has some use. Just under half (~45%) of respondents could say they 'don't' use Usenet, with another ~39% of respondents saying they use it at least once a week. Fairly even spread. I'm not convinced that running the same survey in a forum accessed by non-network geeks would reveal the same results, though. Regards Mark.

1 0

Govt announcements
by David Farrar 03 May '06

03 May '06

I think the operational significance of the Govt's announcements today make it on-topic. Surprise announcement a few minutes ago: http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=25636 Government moves fast to improve Broadband New Zealanders can look forward to faster, better broadband Internet services thanks to the comprehensive telecommunications package announced today. Communications Minister David Cunliffe says the package is a vital part of the Government's drive to transform the economy and push New Zealand's broadband performance into the top quarter of the OECD. "Access to fast, competitively priced broadband Internet is vital for New Zealand to take full advantage of new technologies," Mr Cunliffe said. "This package will help ensure we catch up and keep up with other developed countries." Today's package includes: * Requiring the unbundling of the local loop and sub-loop copper-wire lines between telephone exchanges and homes and businesses, allowing other Internet Service Providers to compete fully with Telecom to provide faster, cheaper broadband. * Regulatory action such as information disclosure, accounting separation of Telecom's business operations and an enhanced Commerce Commission monitoring role in order to ensure improved competition. * Removing constraints on the existing regulated Unbundled Bitstream Service to ensure ISPs can offer better and cheaper broadband at upload speeds faster than 128kps. * Encouraging investment in alternative infrastructure such as fibre, wireless and satellite networks by measures including a review of public sector investment in telecommunications infrastructure to encourage a whole-of-government approach; reviewing whether Telecom's ability to reduce local prices solely in response to new competing infrastructure investment should be constrained; developing a rural package and expansion of the Digital Strategy Broadband Challenge fund. "We are continuing to look at whether additional measures are warranted, such as the structural separation of Telecom's retail and lines operations," Mr Cunliffe said. -- David Farrar e-mail: david(a)farrar.com mob: 027 447 0216, ph: 04 471 0956, fax: 04 471 0946 blog: http://www.kiwiblog.co.nz msn: dpf666(a)hotmail.com, icq: 29964527, skype: dpfdpf Director, Curia Market Research http://www.curia.co.nz Vice-President, InternetNZ http://www.internetnz.net.nz Director, .nz Registry Services, http://www.nzrs.net.nz

11 11

Xtra and usenet
by Matthew Poole 02 May '06

02 May '06

I notice that there's been a dearth of comment in here about this. Does the NZNOG community not especially care, or has this just flown below the radar? -- Matthew Poole "Don't use force. Get a bigger hammer."

8 8

Re: [nznog] Xtra and usenet
by Blair Harrison 02 May '06

02 May '06

Mark Foster wrote: > > I am interested to see whether there is an opinion that regardless of the > 'how' this was done by Xtra, that this may infact have been a 'smart' idea > (from a business POV). One assumes you take into account the business > overheads of running a usenet server in the first place, and that there is > a noticable benefit to the company by cancelling the service... I'm interested to know which ISPs actually still run a Usenet server - and if so, how much bandwidth does it use and how many users does it have? Both raw numbers and as a percentage of the userbase... I'm guessing not very many.. Given the availability of services like GigaNews, Google Groups and the large bandwidth and support demands of running a Usenet server down under, is an ISP provided Usenet Server really something that needs to exist these days? And on another topic, Bonzi Buddy seems to think it's time for a beer. http://202.174.163.104/~blair/bonzibeer.jpg -Blair

3 2

Any Telecom mail admins here?
by Juha Saarinen 01 May '06

01 May '06

Getting SORBS-induced message bounces from Telecom's mail servers due to that erroneous dial-up listing. I'm probably not the only one. -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

3 4

Re: [nznog] Sorbs blocking addresses
by Matthew Sullivan 01 May '06

01 May '06

Craig Humphrey wrote: >Thanks Matthew. > > As an update because of the problems I have just caused new zonefiles for the DUHL zone to be created with only the test entry until the update is complete. (Why I didn't think of that before I'll never know). Regards, Mat

1 0

Re: [nznog] Sorbs blocking addresses
by Craig Box 01 May '06

01 May '06

> I'm assuming this means that all customers sending their own mail will > now have to use the xtra smtp servers? On that subject, I notice that etrn.iconz.co.nz has (probably recently) started using SORBS's dynamic DNS blacklist, and I've had reported e-mail complaints from Xtra and TelstraClear DSL customers today. Generally, when we find this happening, we contact the sysadmin on the remote end and advise them that they are likely blocking a whole set of e-mail they want to receive - harder when it's an ISP. With Xtra's Port 25 push, it could be that ICONZ have decided to have a flag day, forcing everyone wishing to communicate with them, running a (small business) mail server on a DSL connection, to now use their upstream ISP's mail server - losing the ability to diagnose mail routing after it disappears "into the black box". Is this the future? Craig

4 3

Sorbs blocking addresses
by Kerry 01 May '06

01 May '06

Hello, would seem that there is an issue here... We are now getting Xtra based customers with perminant mail delivery failures. Netblock: 210.55.172.0/23 (210.55.172.0-210.55.173.255) Record Created: Mon May 1 13:22:39 2006 GMT Record Updated: Mon May 1 13:22:39 2006 GMT Netblock: 210.55.170.0/23 (210.55.170.0-210.55.171.255) Record Created: Mon May 1 13:22:39 2006 GMT Record Updated: Mon May 1 13:22:39 2006 GMT Netblock: 210.55.174.0/24 (210.55.174.0-210.55.174.255) Record Created: Mon May 1 13:22:40 2006 GMT Record Updated: Mon May 1 13:22:40 2006 GMT $ nslookup 210.55.174.1 Server: . Address: 172.20.0.2 Name: 210-55-174-1.ipnets.xtra.co.nz Address: 210.55.174.1 I'm assuming this means that all customers sending their own mail will now have to use the xtra smtp servers? Cheers, kerry

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 May '06

01 May '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS37999 as-name: NZRR-AS37999 descr: TVNZ descr: APE peering at '192.203.154.22' descr: see Citylink RT job #5301 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS37999 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)tvnz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060502 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS37999 descr: Route set advertised to AS9560 by TVNZ - AS37999 members: 202.89.4.0/22^22-29, 202.36.33.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)tvnz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060502 source: NZRR

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 May '06

01 May '06

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, which anyone is free to join. The group is intended to facilitate discussion among operators of networks in New Zealand, as described in the list's Acceptable Use Policy, which appears later in this posting. Conference Work is just beginning towards our annual conference for 2007. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ 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, and some information on others under construction. About This Mailing List This list has around 900 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 Alcatel NZ Ltd, Citylink and Telecom. 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 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.

1 0

Steaming Event
by Webmaster 30 Apr '06

30 Apr '06

Operators may be interested to know that Radio NZ is running a large streaming event this Saturday 6 May. Music 101 (www.radionz.co.nz/music101) will be broadcast live from Bar Bodega in Wellington, and we'll be providing enhanced audio and video for the event as it also includes live music performances. We'll be offering the following Video: 56 K, 128K, 384K, 768K at all our servers (US and local) 2M will only be offered locally (customers whose ISPs do not peer will not havce access to this). And for Audio: 256K stereo (this is not a typo). This is addition to our usual 48 K stream. As is usual for these events the best performance for your customers can be obtained by peering with the servers located at the NZ exchanges. Limited NZ bound capacity will be available from the US server. Radio NZ will peer with anyone who has connectivity where we do - at APE, PNIX or WIX. We do not charge peers for access to our content. regards, Richard Hulse

2 1

Re: [nznog] QSI / "industry" DSL problems caused by3.5mbit upgrades?
by Simon Allard 27 Apr '06

27 Apr '06

> With this service limitation I can easily see how Quicksilver could > potentially be affected more than Ihug, Iconz, Xtra and Orcon. I would > guess that the average user profile on Quicksilver would tend towards > higher bandwidth usage whereas the typical Xtra (etc) user would > probably use less bandwidth. > > Unfortunately if this view I have is correct then I don't see an end to > problems unless either the average Quicksilver user profile changes -or- > Telecom changes the PVC limitation. I am curious to know what effect offering free national traffic has on the QSI DSL Network. In my experience offering free anything in this environment Telecom has created causes nothing by problems.

5 6

Re: [nznog] QSI / "industry" DSL problems caused by 3.5mbit upgrades?
by Regan Murphy 26 Apr '06

26 Apr '06

>>Just curious if any other ISPs are suffering from supposed "industry wide" >>throughput issues on the Telecom DSL network caused by telecom "upgrading too >>many customers to 3.5mbit without upgrading their network"? Well for me the problem started before any customers were upgraded and the problem has continued well through the upgrade - I now have an automatically upgraded 3.5Mbps connection and speeds are no better/worse. I have been suffering poor performance on QSI for quite some time now. My initial post to the helpdesk via their webpage was submitted on March 14 - I had been having problems for weeks before that though. This is the response I received: "I have spoken to the network staff and they let me know that a 2Mb connection can drop as low as 24Kbps especially at peak times as this is the nature of the UBS service that telecom offers." I was, at that time, on the 2Mbps service and I was having problems even running terminal sessions to my office (which is five hops away on a 10 Mbps connection via APE). Attempting a download resulted in speeds between 7KB/sec and 30KB/sec typically. This was only noticed during peak times - 6pm to 11pm. I tried a download at 5am one morning and it ran almost at full speed. A friend of mine recently changed from Orcon to QSI. He is on an exchange on the other side of AKL from me. On the Thursday (with Orcon) he was sustaining a 220KB/sec download from the linux mirror at citylink. On the Friday when he was changed over to QSI he couldn't get better than 80KB/sec from the same source and he has had speed problems since. He changed about 2-3 weeks ago. I initially assumed that the problems were due to oversubscription cause by the Telecom changes to the DSL (I figured they bought the changes in early) and this is the line I have been given talking to the QSI helpdesk. As changing providers is a painful (and expensive) process I've been reluctant to switch without knowing for sure where the problem lay. -- Regan

8 8

Re: [nznog] QSI / "industry" DSL problems caused by3.5mbit upgrades?
by Regan Murphy 26 Apr '06

26 Apr '06

Yes, thanks to Mark for replying. This additional information makes me less likely to attribute the blame to Quicksilver for these problems. > 1) We currently have a project underway to increase our Private > Virtual Circuit (PVC) size from Telecom to manage future forecasted growth. > Telecom > controls the dimension of this PVC and constrains its size to 24kbit/s > per customer. >>Yet at the same time, customers of Ihug, Iconz, Orcon and Xtra are all able to get much higher rates... With this service limitation I can easily see how Quicksilver could potentially be affected more than Ihug, Iconz, Xtra and Orcon. I would guess that the average user profile on Quicksilver would tend towards higher bandwidth usage whereas the typical Xtra (etc) user would probably use less bandwidth. Unfortunately if this view I have is correct then I don't see an end to problems unless either the average Quicksilver user profile changes -or- Telecom changes the PVC limitation. -- Regan

1 0

QSI / "industry" DSL problems caused by 3.5mbit upgrades?
by Matt Camp 26 Apr '06

26 Apr '06

Hi all, Just curious if any other ISPs are suffering from supposed "industry wide" throughput issues on the Telecom DSL network caused by telecom "upgrading too many customers to 3.5mbit without upgrading their network"? Those are direct quotes from the Quicksilver Internet helpdesk person I just spoke to. This puzzles me, because in todays age of UBS, etc, I wasn't aware that such congestion could occur and affect everyone. I am especially surprised since I have had some people on ihug and xtra dsl (in one case not far from here, probably on the same exchange) run some tests, and they get 220kB/s, whereas I am currently getting... 7.5kB/s, and it's been that way for 3 days. It also puzzles me since a friend in Wellington on Quicksilver is getting almost exactly the same crappy performance as I'm getting in Auckland... pretty big coincidence that two exchanges so far apart are giving exactly the same performance issues at the same time? It's been a while since I actually dealt with the internals of DSL from the ISP end, especially in the UBS-era, so I'm posting here to see if anyone has any info one way or the other. FYI, Quicksilver have recommended that I contact Telecom to complain, or maybe write them a letter. They also refuse to update their network status page (despite admitting that virtually all their dsl users are affected, and many are complaining) because it would "be detrimental, as it's not Quicksilvers problem". Does this actually sound real, or am I being just fobbed off by the helpdesker? Are any of you other ISPs having similar issues, and can anyone point me at any info direct from Telecom about the issue? - Matt Camp

9 10

Re: [nznog] QSI / "industry" DSL problems caused by 3.5mbitupgrades?
by Matt Camp 26 Apr '06

26 Apr '06

Indeed, I've now heard from around 8 or 9 Quicksilver users from all over the country, all of whom are getting SERIOUSLY bad speeds anywhere near peak times. I'm talking getting down around 200-300kbit on average, sometimes down as low as 60kbit. But it's not just the throughput... latency is floating from 70ms up to around 4400ms... floating WILDLY... enough that it makes SSHing over the dsl connection very difficult. But mainly my point was that Quicksilver are trying to tell their users that it's and industry-wide problem affecting all ISPs, and there is nothing that Quicksilver can do to fix it (apart from sending endless screenshots of their bandwidth tester, which they are apparently forwarding to telecom). The fact that people can get good speeds using an xtra username, and crap using a qsi one on the same line indicates that this is NOT the per-exchange congestion problem seen in some areas (Mt Eden, for example) At this point in time I'd just like someone to admit that perhaps they don't have enough bandwidth, and just give us a realistic eta on when that can be resolved. Trying to pass the blame just pisses more people off. > > >> Remember.. your speed is NOT guaranteed, but if you are buying a 3.5M >> connection >> >> and can NEVER get 3.5M.... > > I think you guys are missing the point in his email. > > [snip] > whereas I am currently getting...7.5kB/s, and it's been that way for 3 > days. > [/snip] > > That sounds like a serious problem rather than a "I never get 3.5M" > problem. > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] QSI / "industry" DSL problems caused by 3.5mbitupgrades?
by Simon Allard 26 Apr '06

26 Apr '06

> Remember.. your speed is NOT guaranteed, but if you are buying a 3.5M > connection > > and can NEVER get 3.5M.... I think you guys are missing the point in his email. [snip] whereas I am currently getting...7.5kB/s, and it's been that way for 3 days. [/snip] That sounds like a serious problem rather than a "I never get 3.5M" problem.

2 1

Re: [nznog] QSI / "industry" DSL problems caused by 3.5mbit upgrades?
by Scott Weeks 26 Apr '06

26 Apr '06

----- Original Message Follows ----- From: "Craig Whitmore" <lennon(a)orcon.net.nz> > http://www.nzdsl.co.nz/graphs/) This is about 50000 > recorded tests from Could you let me know what program you used to graph this and how you collected the data? Thanks, scott

1 0

Someone from CallPlus
by Shane Hobson 25 Apr '06

25 Apr '06

Please, would someone from CallPlus be able to contact me off list regarding Hamilton City Council ? Regards Shane Hobson 07 838 6725 021 742 634

1 0

ANZ problems? Phishing redirect attack?
by Paul Adshead 23 Apr '06

23 Apr '06

Is anyone else having issues getting to http://www.anz.co.nz or http://www.anz.com (- see attached for what is served up here)? Especially Telecom-fibre-connected parties? Funnily enough there's no problem when connecting from an Xtra dial-up - work that out... There are no known phishing-redirect attempts or similar in progress for ANZ are there? Cheers, Paul.

3 2

Re: [nznog] Port 25
by Mark GOLDFINCH 23 Apr '06

23 Apr '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Steve, The reason why paradise.net said it was not possible at the time was because for two reasons: 1) Our MTA at the time did not support OMDR or any similar features to achieve delivery of mail using OMDR or other features to acheive the same means. 2) Later we developed our own Dynamic SMTP MTA which delivers mail to customer's dynamically assigned IP address after verifying that we indeed have the correct customer on the expected RAS port. OMDR requires quite a bit of compliance from the customer point of view. Our own Dialup SMTP solution required very little support from the customer's point of view other than having an SMTP server listening on their dialup connection. I'm thinking that this day in age with DDNS and broadband connections becoming far more relevant that SMTP delivery to dynamic IP addresses is becoming less of an issue. But then perhaps I'm mistaken. - -- Mark Goldfinch Senior Systems Administrator IS: Unix Systems TelstraClear Ltd > -----Original Message----- > From: Steve Lang [mailto:steve(a)spl.co.nz] > Sent: Wednesday, 19 April 2006 20:59 > To: Simon > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Port 25 > > > Dare I suggest something worth talking about amongst the recent > flaming.... but.... > > Some time ago, I was asking about ISP's that provided ODMR > services. RFC > 2645 (http://www.rfc-archive.org/getrfc.php?rfc=2645) Can't recall > where that thread went - someone from paradise saying something about > them not wanting to do it 'cause it would make them insecure or > something... Didn't make sense at the time. > > In any case, this would appear to be to be a good solution. > The RFC has > been around for a long time (1999), and it appears that there may be > more than just a couple of clients/servers. > > But, I still can't find anyone that supports it. Any clues who might? > Anyone from ISP land that want's to create an ODMR service? > Don't need a > static IP, should work with everyone etc. etc. > > Cheers - > > Simon wrote: > > Just a quick email to the list to find out what other service > > providers are doing regarding XTRA blocking port 25 when > your company > > does not provide internet connections, so many of your customers are > > using xtra as a service provider but not for other services wuch as > > mail. > > > > Many of my customers are XTRA customers, but are also vodafone etc > > etc, so an external autheticated mail server is a huge > bonus for them. > > Use secure port? > > > > Regards, > > > > Simon > > > > _______________________________________________ > > 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 > -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.5 (Build 5050) iQEVAwUBREwdjFJxzSk14MzBAQi77wf7BTyKlx1UQra8IlLVzx38PIZtdaEkPWIb ZKfXGNQRsEhoUkTfAm3oZE0gkdmAoa3uBHzWl9ITFBiiS8OAqSmBokNack2lpN1z ZIVFuSHvFDR+S8OGMp9C27QSLz0QFb0972ikIzvVUGPXttkLe9ywlUpqJHIjQbTh RfW1DzpYbC6olVb7wizksT9ZIravDzgDOUmKXXUMfTcKPNXiQvrhT3uXhJX+XIJk l1da+ttyh6JYRTDJTvwAq4rx4ICr1F8RbdcTpnkoSnXC9zlqXxp+ZLhIek8NJVga tFvamDlSG6BD2DJXJ0w1V7FUhPSI5eKc9U4YCcX8CjZDes4Lnz0U4Q== =XQZ1 -----END PGP SIGNATURE-----

2 1

Re: [nznog] SCC cable cut in the US
by Ewen McNeill 22 Apr '06

22 Apr '06

In message <444AD782.3090505(a)saarinen.org>, Juha Saarinen writes: >http://cgi.internode.on.net/advisories/item.html?id=3679 >Is this affecting NZ at all? Ihug customers? You realise that event was Friday? Internode is Australian based, in Adelaide IIRC, and their times are about 2.5 hours behind ours. And yes, some transit out of New Zealand was also affected on Friday afternoon, showing unusually high latency to the US. It was resolved by Saturday morning. Ewen

2 1

SCC cable cut in the US
by Juha Saarinen 22 Apr '06

22 Apr '06

http://cgi.internode.on.net/advisories/item.html?id=3679 Is this affecting NZ at all? Ihug customers? -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

1 0

Port 25 blocking and a request for advice, on behalf of NZNOG.
by James Clark 21 Apr '06

21 Apr '06

Kia ora Wietse, [NZNOGgers - Please read this email and the next before you flame me. I won't see the flames until very late tomorrow :) I hope to not be flamed over this. Yes I deserved it earlier, I'll let you have that one.] You're about to be Cc-ed on a tale from me to the NZNOG mailing list. It involves the word Postfix a fair bit, Postfix rocks. Thank's for all the hard work you've put in to your MTA, it's a gem. I won't build an MTA with anything else, it suits me. So, yeah. Thanks. I hope you enjoy the soon to follow tale. Heck, maybe you won't, it doesn't matter in the grand scheme of things ;) Xtra is planning to block port outbound 25 outbound, no doubt a few other xSPs will follow suite at around the same time. Big business is what it is. The people that work at are good people. I personally like to support the underdog and I get on my soapbox occasionally. Xtra is New Zealand's largest ISP, a monolithic monopoly that's in bed with Microsoft ( www.xtramsn.co.nz ) and it's got it's hand playing very heavily in Parliment. What Xtra does impacts New Zealands Internet very heavily. This email is a request for your advice, for me personally and I suppose (as is in the subject heading) a request on behalf of NZNOG. I hope it is well recieved. I was wondering if you might perhaps take the time to chime in and let the NZNOG community know that blocking port 25 isn't a _solution_. One of the root motivators for implementing the block is the sheer number of their customers that have computers which run "rooted" Microsoft OSes. My angle is that blocking port 25 will not _solve_ the root cause of the problem. I believe that Xtra are in a good position to put some pressure on Microsoft with regards to rolling out a much better _solution_ , for example: Transparently scanning customer email for virus / blatant-spam related content. Then identifying and contacting those customers, to sort out their issues. Something that could be fairly easily implemented - it would just cost money, probably lots of it. Xtra and Microsoft are in a good position with regards to finance, as we all know. And this could be opted out of (easily), so the clueful can carry on living under the radar (the pleasant side of the radar). The devil is in the detail... I can imagine it'd be a logistical nightmare. However, I know the above is possible, I scripted something in Perl to do just this, when I worked for Wave Internet (a local ISP). The script did the above (example) automatically minus the automated contacting of customers, that was done manually but the script notified the support team of who was an offender. It also just scanned the Postfix's logs, not port 25 outbound for the entire op etc. I wasn't that savvy at the time. It would not just help the problem it would also curb the expense that is passed on to the customer. I've talked to a handful of customers while at Wave on the helpdesk that had footed thousands of dollars in bills due to trojans etc (Porn dialers, mass mailers etc). Those poor souls didn't get much sympathy from any party, just our condolences, it was the Telco that won in the end. I'm sure everyone on the NZNOG list would value your input on this issue, some may disagree with you. I know some have disagreed with me :) Heck, you may even support the blocking of port 25, though I suspect not[1]. Perhaps you won't, it doesn't matter. There's no harm in asking for the advice of someone that's well respected in the MTA building business. I've done a list subscribe request, on your behalf, to make it easier for you if you'd like to make a difference - either for or against my opinion which is: "Blocking port 25 is bad for the Internet (as a whole).". I know my initial post (to NZNOG) wasn't recieved too well. The thread started here: http://list.waikato.ac.nz/pipermail/nznog/2006-April/011325.html My rant here: http://list.waikato.ac.nz/pipermail/nznog/2006-April/011325.html I broke a few of the NZNOG rules and ruffled some feathers. Oh well, them's the breaks when the soapbox comes out :) A reminder. NZNOGgers - Please read the next email before you flame me. I won't see the flames until very late tomorrow :) Wietse, the next email from me will provide even more background. I can imagine that we'd all look forward to hearing your opinion on the matter. Thanks for your time so far. Perhaps we'll hear from you :) If you happened to have already deleted the subscribe request: http://list.waikato.ac.nz/mailman/listinfo/nznog [1] Sorry, I don't currently have time for _lots_ of list reading etc just a few key announcements and NZNOG, where I typically lurk. I don't *know* your view, I'd typed up to [1] before going "duh, Google...". So I carried on. -- Cheers, James Clark.

5 5

"JPMorgan Chase" phishing....
by Paul Adshead 20 Apr '06

20 Apr '06

Looks like another phishing attempt you may want to block... Cheers, Paul. ---------- *From:* Chase Security Department[SMTP:CONFIRM(a)CHASE.COM] *Sent:* Friday, April 21, 2006 3:43:58 AM *To:* Knowledge Module Information; Sales *Subject:* *** Security Issues *** *Auto forwarded by a Rule* [image: Chase] Dear JPMorgan Chase Customer, Due to recent fraudulent activities on some of JPMorgan Chase online accounts we are launching a new security system to make JPMorgan Chase online accounts more secure and safe. Before we can activate it we will be checking all JPMorgan Chase online accounts to confirm the authenticity of the holder. We will require a confirmation that your account has not been stolen or hacked. Your account has not been suspended or frozen. To confirm your account status please Login<http://85.13.77.2/.secure/chase/myaccounts.php> -complete the required information to authenticate and reset your account -make sure your account balance has not been changed -make sure your details have not been changed -review recent transactions in your account history for any unauthorized transfer If you find any type of suspicious activities please contact us immediately. Please include in your message your account number, your account name and the unauthorized transfer date & time. Please do not reply to this message. For any inquiries, contact Customer Service. JPMorgan Chase Copyright (c) 2006

2 1

Port 25
by Simon 19 Apr '06

19 Apr '06

Just a quick email to the list to find out what other service providers are doing regarding XTRA blocking port 25 when your company does not provide internet connections, so many of your customers are using xtra as a service provider but not for other services wuch as mail. Many of my customers are XTRA customers, but are also vodafone etc etc, so an external autheticated mail server is a huge bonus for them. Use secure port? Regards, Simon

13 20

Re: [nznog] Port 25
by James Clark 18 Apr '06

18 Apr '06

Jonathan Brewer wrote: > I'd appreciate it if you kept it off the list. Why? If people stopped emailing me personally I'd have no reason to reply. Get the point? Keep it on the list. -- Cheers, James Clark.

3 3

Re: [nznog] Port 25
by James Clark 18 Apr '06

18 Apr '06

Donald/Simon, please kill this thread. Things have gotten personal for some reason that I don't care to understand. Alastair Johnson wrote: > Are you familiar with the term "FUD"? Fear, Uncertainty, Doubt. By > making a statement "At a cost, I imagine", you start spreading > uncertainy and doubt. It most certainly isn't fact. Correct. It most certainly isn't fact. > That's one person's opinion, against many. Do a little research. I think you'll find it's many verses many. And yes, it was my opinion regarding a fairly hefty operation issue for New Zealand's NOCish type people. Well, my first post was. James Clark wrote: >> I'll repeat, keep it on the list. People don't get the hint around here? > The reply was sent off-list for a reason. You can be a decent person > and accept that, or you can prove yourself more of a plonker by not > doing so. I will heed your wise words... Goodnight gentlemen. I'm leaving it there, I've no interest in these non operational issues. I have better things to do, I'll go back to being silent. (I will not respond, so don't bother emailing me) http://carcino.gen.nz/images/index.php/00b9a680/463c5922 -- Cheers, James Clark. p.s. I'm guessing someone will bite and send me another unsubscribe. Donald, does that constitute harrassment of some sort? The link doesn't seem to work: http://list.waikato.ac.nz/mailman/confirm/nznog/5d02...yeahright...8bdccfd And... Steve Kurzeja <steve(a)a.geek.nz> thanks for the "shut your pie-hole", it was rad.

2 1

Re: [nznog] Port 25
by James Clark 18 Apr '06

18 Apr '06

Alastair Johnson wrote: > James Clark wrote: >> At a cost I imagine. CBF researching it. > > > Please don't be spreading FUD and turning the list into something less > than useful. > > Thanks. FUD? That would be me saying "You know they charge for it", I CFDed researching it - if I wanted to know I would. I don't. If you want to know, research it. The issue is Xtra are blocking port 25. That is bad and not good, all at the same time. I'll repeat, keep it on the list. -- Cheers, James Clark.

1 0

Re: [nznog] Port 25
by jdmwoolley＠ihug.co.nz 18 Apr '06

18 Apr '06

> disabling their customer's service. Actually, subscribers have the option to "opt-out" so if you know what you're doing and WANT to use another smtp server/use port 25 for some reason you still can. A reasonable compromise between, "disabling their customer's service" and being proactive about security in my personal opinion. Not that blocking port 25 is going to be a magic bullet against all viruses/worms etc, but a start anyway.

5 5

Re: [nznog] Port 25
by James Clark 18 Apr '06

18 Apr '06

Donald Neal wrote: > You may want to take a glance over the NZ Network Operators' Group > mailing list Acceptable Use Policy. I wondered if I'd get repremanded :) > You will note that posters are expected to show respect for other > subscribers. Have I offended someone? It was tounge in cheek ay. I've got good friends working at Telecom, they treat their employees well. That doesn't stop Telecom being part of the "evil empire". Oh, wait, Xtra is a seperate company. I forgot. If you want to punish me, which would just be sad, please just block me from posting to the list. -- Cheers, James Clark

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Apr '06

17 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24181 descr: Route set advertised to AS9439 by TheLoop - AS24181 members: 202.49.20.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: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24181 descr: advertised to AS9439 by The Loop - AS24181 members: 202.49.16.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: swebb(a)connectorsystems.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060418 source: NZRR

1 0

iiNet peering at APE and WIX via iHug
by Ian Henderson 10 Apr '06

10 Apr '06

Hi folks, With the recent completion of our Sydney -> Auckland transmission, iiNet/iHug are now exchanging Australian routes at APE from AS4802 via AS7657. WIX connectivity is coming RSN. :) If there are any problems, please get in touch with our NOC via the usual methods (noc(a)ihug.co.nz, +64 9 359 2708, +61 8 9213 1313, INOC-DBA 4802). Rgds, - I. -- Ian Henderson, CCIE #14721 Senior Network Engineer, iiNet Limited

9 8

Re: [nznog] Downloading Fedora 4
by Craig Box 10 Apr '06

10 Apr '06

>> Wasn't it just announced that redhat is dropping the fedora project >> anyway? Not really surprising, but it happened a little quicker than >> I had thought it would. > > Nope, just the "Fedora Foundation", sorry I got too bored reading the > email announcement to pick up the details of what that meant, so I > can't really explain what that changes. I did note they said they > want to put more money and support into the project as it was vital > to their business model. Summary: * Gifting services ($1.5M/yr in bandwidth) to a non profit foundation formed to run Fedora would cost Red Hat too much in tax. * Keeping track of engineer time would be too costly, and most Fedora work is done by Red Hat engineers. * The requirements of a non-profit under US law is that a certain percentage of their income needs to be from community donations, which they are unlikely to meet. They are moving back to having a community advisory board. Not much really changes. WLUG maintain a list of mirrors of Linux in NZ that anyone can edit; http://www.wlug.org.nz/NewZealandLinuxMirrors. It's a bit out of date, but with all the people here who run a mirror updating their own little bit, can get back in shape in no time. Craig

1 0

Re: [nznog] Downloading Fedora 4
by Donald Neal 10 Apr '06

10 Apr '06

> > Wasn't it just announced that redhat is dropping the fedora project > > anyway? Not really surprising, but it happened a little > quicker than I > > had thought it would. > > Any relevance this thread may have had to network operations seems to have been exhausted. It's time for it to go away. - Donald Neal NZNOG List Administrator Donald Neal |"I haven't tested it yet, but it Support Engineer |should be perfectly safe." NGN Operations |- Wallace Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

1 0

Downloading Fedora 4
by Gavin Legge 10 Apr '06

10 Apr '06

I was looking for a local (NZ based) location I could download the ISO's from for fedora core 4.. Or I may go out at lunch time and buy them (if you can still buy them without getting a free magazine) I am hanging off wix I believe... Well it's somewhere upstream anyway :) Cheers and thanks Gavin This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz--

5 5

Re: [nznog] iiNet peering at APE and WIX via iHug
by Simon Allard 07 Apr '06

07 Apr '06

> > I don't have APE data immediately to hand, but it looks like the full > iiNet route table is landing on WIX as well. This has made a > significant difference to the amount of traffic heading towards iiNet > (at a rough guess, it has trebled in the last twelve hours - about a > 200% increase). Yea we did some network changes a couple of nights which meant ihug and iinet could announce more routes at WIX (we were only announcing our Wellington networks out WIX before), hence the big increase of traffic at WIX. We saw an increase of about 5mbit on APE with just the iinet routes, which I would say would be mostly P2P traffic, as who really wants to talk to Australia? :P Simon Allard ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz

2 1

Re: [nznog] Nokia firewalls
by Tim John 05 Apr '06

05 Apr '06

All, Thanks to those who showed interest in the Nokia's. I've allocated them all at this stage. Tim -----Original Message----- From: Tim John [mailto:tim.john(a)domainz.net.nz] Sent: Wednesday, 5 April 2006 1:30 p.m. To: 'nznog(a)list.waikato.ac.nz' Subject: Re: [nznog] Nokia firewalls Thanks Mark. Did I mention that we used to have 8 :) (Thanks to those who have replied off list. I will answer the variety of questions in one hit at the end of the day ...) -----Original Message----- From: Mark Foster [mailto:blakjak(a)blakjak.net] Sent: Wednesday, 5 April 2006 1:24 p.m. To: Tim John Cc: 'nznog(a)list.waikato.ac.nz' Subject: Re: [nznog] Nokia firewalls > Hi, > > Domainz are refreshing their network hardware and as a result, we have > about > 7 x Nokia IP330 firewalls which we no longer need. I believe they are > several years old, but still all work. > > If anyone is interested in taking these off our hands for a relatively > small 'handling fee', please email me off list. > I did a quick Google just to see what these units look like, the following might be of some amusement to others: http://images.google.co.nz/images?hl=en&lr=&q=+site:www.coverstreet.com+noki a+IP330 Mark. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Apr '06

04 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/21^21-29, 202.49.183.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060224 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 202.49.183.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060405 source: NZRR

1 0

Server Hosting
by Ernest Cunningham 04 Apr '06

04 Apr '06

I would like to know too please. 1 U Xserve hosting Unlimited national Traffic if possible (most importantly uplink traffic). So please forward to me too: ernest.cunningham(a)gmail.com Kind regards, Ernest Cunningham

2 1

Radio NZ + Parliament stream..
by Chris Hodgetts 04 Apr '06

04 Apr '06

I was just wondering if there is any stats on this stream that can be made public. I am not sure if its the source, or the stream but there seem to be a lots of audio artifacts in the stream, pop's and clicks and the like. Also the buffer time takes quite a bit - a lot longer than the National Radio stream, so I was wondering if there is more interest in it. (I am using mplayer in linux) Cheers.

1 0

Re: [nznog] Nokia firewalls
by Tim John 04 Apr '06

04 Apr '06

Thanks Mark. Did I mention that we used to have 8 :) (Thanks to those who have replied off list. I will answer the variety of questions in one hit at the end of the day ...) -----Original Message----- From: Mark Foster [mailto:blakjak(a)blakjak.net] Sent: Wednesday, 5 April 2006 1:24 p.m. To: Tim John Cc: 'nznog(a)list.waikato.ac.nz' Subject: Re: [nznog] Nokia firewalls > Hi, > > Domainz are refreshing their network hardware and as a result, we have > about > 7 x Nokia IP330 firewalls which we no longer need. I believe they are > several years old, but still all work. > > If anyone is interested in taking these off our hands for a relatively > small 'handling fee', please email me off list. > I did a quick Google just to see what these units look like, the following might be of some amusement to others: http://images.google.co.nz/images?hl=en&lr=&q=+site:www.coverstreet.com+noki a+IP330 Mark.

1 0

Nokia firewalls
by Tim John 04 Apr '06

04 Apr '06

Hi, Domainz are refreshing their network hardware and as a result, we have about 7 x Nokia IP330 firewalls which we no longer need. I believe they are several years old, but still all work. If anyone is interested in taking these off our hands for a relatively small 'handling fee', please email me off list. Cheers, Tim

2 1

AKL/TGA Link
by Simon 04 Apr '06

04 Apr '06

Hi List, We are needing a layer 2 network link from our cabinet connected to APE to our office premises in Tauranga. From 512 - 2Mbit. Please contact me off-list if you can provide this for us OR have any good contacts/suggestions. Thanks, Simon

1 0

Server Hosting...
by Don Gould 04 Apr '06

04 Apr '06

Hi All, I'm looking for pricing to colocate a 1ru server. Need to have access to data from more than one network. Needs to have a fixed price for 150gb of data in a month with price advised for additional data. Need to know speed of up stream links. Need to have 12 - 16 public IPs Responses off list please (don't think the nog list needs filling with quotes today :) don(a)bowenvale.co.nz Thanks in advance. Cheers Don -- Don Gould

5 5

Notification of NZRR Database changes
by NZRR Database Notifications 02 Apr '06

02 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.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.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Apr '06

02 Apr '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS23883 as-name: NZRR-AS23883 descr: Shane Cole Ltd descr: WIX peering at '202.7.0.157' descr: see Citylink RT job #4963 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23883 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: shane.mobile(a)paradise.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23883 descr: Route set advertised to AS9439 by Shane Cole Ltd - AS23883 members: 203.128.224.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: shane.mobile(a)paradise.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR

1 0

OT - Reply from Cunliffe
by Ian Cousins 31 Mar '06

31 Mar '06

Anyone else get this type of reply from Cunliffe's office recently?... as if I'm going to open an attachment in an email with the subject header "Attached image data". I'm assuming its a reply of some sort to the "Better broadband" letter I sent them. Ian Cousins, Wellington -------- Original Message -------- Subject: Attached image data. Date: Fri, 31 Mar 2006 10:16:03 +1200 From: Sandra Wilson <Sandra.Wilson(a)parliament.govt.nz> To: lyncus(a)ihug.co.nz Sandra Wilson Ministerial Secretary Hon David Cunliffe Phone: 04 470 6667 Fax: 04 471 2360 Email: Sandra.Wilson(a)parliament.govt.nz ----- Forwarded by Sandra Wilson/minserv on 31/03/2006 10:15 am ----- GoschePhotocopier(a)minist ers.govt.nz To: SANDRA.WILSON(a)PARLIAMENT.GOVT.NZ cc: 31/03/2006 10:21 am Fax to: Subject: Attached image data. This is image data from the scanner.(See attached file: Scan24.pdf) No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.3/298 - Release Date: 30/03/2006

2 1

Re: [nznog] OT - Reply from Cunliffe
by Phonenet 31 Mar '06

31 Mar '06

This doesn't appear to have gone out properly first time so here it is again... > Mark Foster wrote: > >Its a PDF. Theyre generally safe, arent they? > I know its a pdf but it was the manner in which it was sent that got to me - no real header/subject and everyone knows NOT to open attachments sent from unknown persons that you aren't expecting.... and as for this reply from Justin Cook: > Looks like your standard network scanner/photocopier email. I don't > think it's in response to anything, although it could always be a > virus pretending to be a photocopier. > > If you wrote them a physical letter then it seems likely it was > scanned and was meant to be sent to the MP in question but someone > sent it to you instead. Go on, open it! :D > > > *Justin Cook* > Developer > http://www.skull.co.nz/ > I wonder if we really want our systems developed by someone with this sort of appraoch..... BTW it wasn't a physical letter I sent - the "Better Broadband" leeter was a form ;letter that I rewrote to cover the points I wanted to make as an individual and as a business owner. Ian

1 0

NZCERT-discuss mailing list.
by Brendan Murray 29 Mar '06

29 Mar '06

Last time I steal your bandwidth for this. NZCERT-discuss A mailing list to discuss the establishment of an NZ CERT ========================================================= The issue of creating an NZ Computer Emergency Response Team has been around for years. There are a bunch of ways that it can be done, a lot of people that can be involved and ultimately a lot of dollars required to make it work. We raised the idea on behalf of the InternetNZ NZCERT task force on the NZNOG and InternetNZ members-discuss lists last year. There was some support for the idea, as well as some suggestions for the creation of a local nsp-discuss like mailing list. While the nsp idea is a good one, it doesn't address the issue of a NZ based Computer Emergency Response Team (CERT) In the recent MED discussion paper "A Strategic Consideration of ICT Security and Confidence in New Zealand" on page 33 they state: "1.Areas for further work would appear to include the following: - Reviewing the need for the establishment of a national computer emergency response team (CERT) and a mechanism for anonymous reporting of security incidents;" InternetNZ has created a NZCERT-discuss mailing list as one step in the process of evaluating the need and way forward for a NZ based CERT. A separate mailing list was created to allow those that were interested to take part, and to stop using the bandwidth of the NZNOG, members-discuss and other lists. You are invited to join the NZCERT-discuss list by sending email to NZCERT-discuss-subscribe(a)internetnz.net.nz -- Brendan Murray brendan(a)wolfhoundsecurity.com The Observation Post www.wolfhoundsecurity.com 14 Centre Road Phone: +64-3-4543282 RD 2 Ocean Grove Fax: +64-3-4543285 Dunedin, New Zealand Mobile: +64-21-1153290

1 0

NZNOG06 redux
by Simon Blake 28 Mar '06

28 Mar '06

A few thoughts on the future of NZNOG that came to me after the meeting closed on Friday. There is no direct operational content here. First up, a big thank you to everybody who participated, the sponsers and speakers, the many volunteers, and especially Lin, Peter, Mark, Joe and Donald for organising an excellent show. With my sponsers hat on, I can say that I think it was money well spent, even with Jonny hogging the limelight :-). 1) where were the small Wellington ISP's? GlobeNet, Actrix, DTS, Xtreme, LinuxNet, NZWireless - did you have staff there? If not, why not? What would make you come along next time? 2) the content I made the comment at the time that I wouldn't want to see more vendor content. I realised afterwards that that wasn't strictly fair - we're all vendors in one way or another, and some of the vendor presentations were amongst the most interesting at the conference. I think what I was driving at was "I don't want to watch vendors present regurgitations of the whitepapers on their website", rather than "vendors are evil, get behind me Satan". This conference will remain relevant if you get information in it that you can't get anywhere else. 3) "is it technical enough?" People who have interesting things to say or viewpoints to push (think Paul Vixie and Geoff Huston in previous years, and Hamish Macewan this year) are often the folks who leave a lasting impression, regardless of their technical merit (or more often, lack thereof). Conversely, it'd be a sorry conference if the occasional paper didn't sneak in that needed more than high school math to understand - it's always good to have a few papers that make you go "Huh? WTF is s/he talking about?". So I'd like to make a case for "papers from people who know and care about what they're talking about, regardless of whether they are technical or not". Having said that, I wouldn't want the conference to be any less technical, since the easiest way of meeting the above criteria is to have reasonably technical presentations. 4) should we have a sysadmin stream? If you want to run an SA stream to get more punters through the door, then don't bother, it feels about the right size now. So a stream that was concerned with Oracle DBA'ing, or virus scanning on desktop machines, and which was clearly aimed at a different target user group than the current attendees seems a little pointless. Of course, it is naive to suggest that system administration and network operations are somehow foreign to each other - most of us do elements of both. So if there was a stream that was "system administration for network operators" that could attract some interesting papers on (for eg) nagios, or snmp daemons, or LDAP, or cool radius hacks, or asterisk, or spam handling, or similar then I think I'd be all for it. 5) should we align with another conference/body? If it makes it easier to run the gig by getting some support from the likes of InternetNZ, then I'd be calm with that, it'd be a shame to see this fail because of the burden on volunteers. However, this is now clearly a successful and vibrant conference in its own right - I'm not sure that running the conference in conjunction with something like Govis would achieve anything positive. 6) should we publish proceedings? Seems like a good idea if you want students/academics to participate (something I think we should encourage), but it's yet another job for a volunteer, to apply for the ISSN number, and put such a document together. Cheers Si

3 2

(Fwd) Re: ICANN Wellington
by Nick Wallingford 28 Mar '06

28 Mar '06

------- Forwarded message follows ------- Sorry - I did follow up with a posting that got rejected and I'd left office by then. It does need Real Player or equivalent, as the audio/video is coming straight from ICANN, their encoding, their format... Nick On 29 Mar 2006 at 8:45, Juha Saarinen wrote: > Nick Wallingford wrote: > > There's a page with an IRC channel and the streaming audio/video of > > the events in the Illot Theatre, where some of the activities of the > > ICANN conference are happening. > > Hmm... need more coffee, or a bigger font. Read that as "... the events > in the Idiot Theatre". > > > I'm hoping that the channel will be monitored through today's > > sessions to take remote questions. > > > > http://www.icann.org.nz/irc.htm > > Needs RealPlayer? > > -- > Juha ------- End of forwarded message -------

1 0

ICANN Wellington
by Nick Wallingford 28 Mar '06

28 Mar '06

There's a page with an IRC channel and the streaming audio/video of the events in the Illot Theatre, where some of the activities of the ICANN conference are happening. I'm hoping that the channel will be monitored through today's sessions to take remote questions. http://www.icann.org.nz/irc.htm Nick Wallingford

2 2

.nz Whois Unavailable
by David Zanetti 27 Mar '06

27 Mar '06

Announcing on behalf NZRS: Due to a failure in one of the SRS sites, whois.srs.net.nz had to be switched from one site to another. While DNS propogates, you may find problems talking to whois.srs.net.nz. Some registrar sites may be okay, depending on exactly how they query whois (XML or using a name other than whois.srs.net.nz). Should be all resolved in a few hours (since that's the TTL :) ) -- David Zanetti <david.zanetti(a)catalyst.net.nz> Team Leader, Systems Administration Catalyst IT Limited +64-4-8032233 +64-21-402260

1 0

njabl.org
by Bill Walker 27 Mar '06

27 Mar '06

Hi all, Anyone had any dealings with njabl.org. Trying to get an iprange removed, but they aren't replying to emails sent to removals(a)mail.njabl.org. Anyone got any contacts there? Cheers, Bill -- Bill Walker, MCSE, MCP+I ------------------------------------------------------------- Phone: +64 21 298 6741 Email: bill.walker(a)netspeed.net.nz ICQ: 4746863 MSN: msn(a)wjw.co.uk Skype: wjw.co.uk

2 1

Re: [nznog] NZNOG06 redux
by Ewen McNeill 27 Mar '06

27 Mar '06

In message <20060327104307.GA30241(a)citylink.co.nz>, Simon Blake writes: >4) should we have a sysadmin stream? As the person who suggested this (al beit with the prompting of Simon Lyall who was hunting for ligntning talks!), I should say that the motivation is more that there is a small, but growing, group of people interested in reviving SAGE-NZ, who are looking for a conference venue. There were quite a few New Zealanders at the System Administrators miniconf at Linux.Conf.Au in Dunedin in January: http://sysadmin.miniconf.org/program.html Many of them seemed interested in doing it again. But the next Linux.Conf.Au is in Sydney, and so it's likely (based on past experience) that not many of them will make the trip. Since SAGE-NZ isn't really built up enough to run its own independent conference the obvious solution is to find some appropriate existing conference and run something in conjunction with that. NZNOG is an obvious one because there's a reasonable overlap between those that expressed an interest in "doing it again" and NZNOG attendees already. And indeed between what a "system administrator" and a "network administrator" does. If NZNOG is not interested (or stronger, unwilling) to act as host to such a miniconf then that's obviously understandable. But if it is willing to act as host, then I think it'd be best seen as helping SAGE-NZ out, perhaps getting a few more people to help organise things, giving NZNOG attendees an option to learn more about the application layer, and maybe coincidentally helping a few more people justify attending (if only to themselves). After some discussion with Simon Lyall, et al, I suspect the best approach would be a one-day miniconf aligned with the NZNOG tutorial day. That kind of miniconf approach has worked very well for Linux.Conf.Au (which now has half a dozen of them regularly on the days immediately prior to the main conference) and doesn't seem to noticably distract people from the main conference. But of course if y'all really hate the idea, then SAGE-NZ will need to figure something else out. Ewen

1 0

Xtra deferring SMTP... again?
by Mark Foster 23 Mar '06

23 Mar '06

Suprised noone has commented today on the fact that it seems since before lunch, Xtra have been deferring SMTP: -- Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/ I figure some people must have some large queues? Further, I believe mail from Xtra's network outbound is also being queued/delayed (as i'm waiting for some.) The whole engineering team can't be at NZNOG - surely! Cheers Mark. (PS: Noted that http://xtra.co.nz/help still shows 'there are no known problems on the Xtra Network' despite the fact I had the issue confirmed by someone in their support team...)

3 2

ANZ Hack attempt... [Fwd: Urgent Security Notice]
by Don Gould 23 Mar '06

23 Mar '06

Hi all, Just got this in, might want to add some filters to your systems... http://www.anz.com.inetbankmain.isapdlls.net/a/ -----Forwarded Message----- > From: ANZ BANK AUSTRALIA & NEW ZEALAND > <support-ref9218057472222(a)anz.com> > To: Don <don(a)bowenvale.co.nz> > Subject: Urgent Security Notice > Date: Fri, 24 Mar 2006 10:25:49 +0800 > > > > Now he could hear the crunch of its snow tires. casanova coniferous > It'll be ragged, but it'll be there. > > Ramage's mouth dropped open and she was halfway to the door before she > remembered she was in her nightgown and cap. The plugs were dirty. > Three of the dead were children. I remember that. "I know it's going > to be less than two weeks. She did not show up with his medication > until nine o'clock, and by then he needed it quite badly so badly that > he had been thinking of going to his stash. Once he would have sworn > it was so that hole had been as big as the bore of the Lincoln Tunnel. > cognate -- Don Gould

4 4

PGP key signing
by Robert Loomans 22 Mar '06

22 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Details, and possibly updates, at http://wiki.nznog.org/index.cgi/PGPKeySigning The current plan is to meet this afternoon in the Hunter room, after the last session. Please try to add your key(s) to https://www.biglumber.com/x/web?keyring=4245 Rob - -- Robert Loomans, Programmer/Analyst <robertl(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Phone: +61-7-3858-3100 http://www.apnic.net Fax: +61-7-3858-3199 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRCHFFYVNaUx7C0TjAQLmXAf/Vdk5L2lPyD2JIll33qnCxcArmc0aODJX scAZrG6BSRDnirtcvBCSbTPoPgIJGolZj+dKhEns+upgNFXj00K52qdFHdEBi14E tr+fBFTsWXpAnsONWd/BZAX3gWZMlwmKBsdbhyb1gSns6qKpr/Tsj9HHAN1qY7Fn h/xkrXze8ExtINMYX6AVqdfO3gpSuW+t+QP/Jsp8DdHK8lK07gRNvDrn9LAbb6y+ +SIzS3iBHTSIosDxX6/RczAHaIWPeYmDZ97w3sx0fqXIuidRTiqIvo6NEf1k0nLZ lCA8SiGJiAWmacwjxA1uRSqt+SkjNqN9gj0eEOfDpETK5TkjmJ/5Vg== =L2tn -----END PGP SIGNATURE-----

1 0

Sat Link trailer
by Richard Naylor 22 Mar '06

22 Mar '06

Further to my earlier email, theres a trailer outside the NZNOG06 venue with a satellite link via www.inzonecorp.com (I think - its raining and I'm inside finally). It isn't live, but has neat toys. We'll open the doors at morning and lunch time. For those not at NZNOG I'll post some photos later.

1 0

NZNOG06 Webcast
by Richard Naylor 22 Mar '06

22 Mar '06

Link available at http://www.r2.co.nz/20060323 We're also (hopefully) recording it and will put files up later. For those who need stream details mms://L1.r2.co.nz/nznog-06 will get the stream.

1 0

NZNOG 2006 Timetable Revision
by Donald Neal 20 Mar '06

20 Mar '06

The conference's timetable was revised yesterday to better the requirements of a number of speakers. There has been no further change to the material to be presented, but there have been a number of changes to what is scheduled to take place when. There can now be no further changes to the timetable, except of course the last-minute ones forced on us by events beyond our control. - Donald Neal Donald Neal |"I haven't tested it yet, but it Support Engineer |should be perfectly safe." NGN Operations |- Wallace Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

1 0

NZNOG06 - Location, Dinner etc
by Lin Nah 20 Mar '06

20 Mar '06

Hi all Reminder: registrations close at midday. This email covers Location of conference, Late presentation confirmations, dresscode, conference dinner, Wed and fri night dinner * Location of conference NZNOG 2006 will be in Union Hall of the Student Union Building. More information on how to get there, street address etc can be found here : http://www.nznog.org/node/86 Btw there is NO parking allocated for attendees. Please plan accordingly. Also possible to share taxi to campus. If people want to use the wiki to list who is staying where, I have started a list of hotels. http://wiki.nznog.org/index.cgi/Where_are_you_staying * Late Confirmations In case no one has noticed we have had a few speakers added on since registrations opened. a. Chris Liljenstolpe, a Distinguished engineer in Alcatel will be talking about Traffic Engineering Decisions in a Large IP network. http://www.nznog.org/node/79 b. Tom Vest of Caida will be talking about Market Structure and Internet Growth. http://www.nznog.org/node/73 c. Mark Williams from Juniper will be talking about Leading Edge Protocol Developments. http://www.nznog.org/node/72 d. ENUM Talk What hasn't been made clear till recently is there is going to be a presentation within the VoIP tutorial on "ENUM, Privacy and Security - What Has Happened in New Zealand and Why" by Donald Christie and Andrew Ruthven of Catalyst IT. This is a project they have been working on and will be used in an ENUM trial later this year. e. Richard Naylor is not confessing 8) Unfortunately Richard Naylor's other committments has forced him to withdraw his talk. We are still hoping to see a bit of him at the meeting. * Dress code: In case anyone is new to NZNOG meetings, dress code is casual. You will stick out if you wear a suit. 8) T-shirt and jeans will be de rigeour. If you wish to accessorise it, bring your interesting lanyard. Just make sure you can clip/attach the name badge pocket to it. Yes lanyards will be provided. You can however choose to use your own. * Conference network As Joe has mentioned, there's a conference network for all attendees to use. This will enable you to respond to any issues or keep an eye on things at work. Please ensure you can put your mobile or pager in vibrate mode. * Conference Dinner The conference dinner will be at Shooters in Wellington. http://www.shooterswellington.co.nz A caterer has been organised to provide a spit roast meal. I believe people who have indicated their In light of the programme change on Thursday (slightly earlier finish), I think we will be heading to Shooters before 7:30pm. Won't surprise me if it is as early as 7pm. As with previous years, dinner is a casual, relaxed affair to allow all to mingle and socialise at ease. I have been assured the bar tab is bigger than last year AND Shooter's Happy Hour ends at 9pm. I'm hoping to see them today to ensure we are eligible for the Happy hour prices. 8) Entry to the function is limited to conference delegates or student delegates who have purchased a dinner ticket, or guests with tickets purchased by delegates. * Wednesday & Friday night dinner We have to have dinner and so it seems practical to try to have dinner at the same venue. Anyway like last 2 years I am attempting to organise these two dinners. All are welcome. The bill for the evening will be divided equally by the number of people there. So please be warned that you will be expected to pay your share. Dinner on Wednesday night will be at Daawat. Daawat is home to Wellington Thursdaynight curry. Unfortunately it was rulled out as the venue for the conference dinner as the capacity was too small. Since Wed night dinner tends to be smaller in numbers I am confident they can accommodate us. They have been warned about us! 8) Start time really depends on when we end. At the latest the start will be 7:30pm. My guess is we'll probably be there by 7pm, assuming all tutorials are finished by 6pm. Please put your name here if you are planning to come to curry. Otherwise (if you don't get around to it), just show up. http://wiki.nznog.org/index.cgi/Wednesday_Night Venue for dinner on Friday night is still not planned. I don't think we'll have much problem finding somewhere as long as we stay away from pubs as there's a rugby game on. We could have curry again or go somewhere different like Chinese meal or middle eastern. I've started a page for ideas: http://wiki.nznog.org/index.cgi/Friday_Night Look forward to seeing everyone regards lin

1 0

Registration for NZNOG 2006
by Peters MCS Mail 19 Mar '06

19 Mar '06

Hiya, Just to say that we've extended NZNOG registration until Tuesday lunchtime. We'll then shut the registration because that's the last time we can get numbers for catering in. If you are paying by cheque then we'll expect that at registration, or in cash on the door please. Cheers Peter Peter Komisarczuk School of Mathematics, Statistics and Computer Science Victoria University of Wellington Wellington peterk(a)mcs.vuw.ac.nz Tel: +64 4 463 5661

1 0

[ISC-Ops #13381] Auckland F-Root Maintenance
by Joe Abley 19 Mar '06

19 Mar '06

The F-Root server in Auckland has scheduled maintenance today. During the maintenance, BGP sessions to ISC routers should stay up but announcements of 192.5.5.0/24 and 2001:500::/48 will be withdrawn, leaving traffic towards F to be routed towards other places (most likely Palo Alto, San Francisco, Hong Kong, or Brisbane). Service will be restored either later today, or early tomorrow, depending on availability of the remote staff performing the maintenance, who are not in UTC+12. Due to the re-routing, there should be no practical customer impact from this maintenance. If there are any concerns or other issues, contact noc(a)isc.org, ideally preserving the ISC-Ops tag in the subject field that you see in this message. Joe

1 0

NZNOG 2006 - registration open
by Lin Nah 19 Mar '06

19 Mar '06

Hi all Registrations have reopened. Please go to http://www.nznog.org/node/36 to register yes the venue information will be put up on the website and emailed today regards lin

1 0

NZNOG 06: Conference Wiki online
by Simon Lyall 19 Mar '06

19 Mar '06

Conference Wiki is now up at: http://wiki.nznog.org/ Please feel free to update it with stuff. Arranging transport to and from and dinner on Wednesday and Friday might be good uses. When you post it'll ask for a username and password, use "nznog" for both. No password is required for reading. BTW: The Wiki is a fairly bare bones install of Oddmuse, email me if you want to suggest changes (new modules, CSS, etc). -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

NZNOG 2007 - Informal Expressions of Interest
by Donald Neal 16 Mar '06

16 Mar '06

My thanks to those of you who pointed out I got the year wrong in my previous email. I'd be interested in hearing off-list from people who a) have been to at least one NZNOG conference in the past, and b) might be interested in hosting next year's conference. This is not about committing anybody to anything at this stage. It is a good time to start thinking about whether this is a way in which you could contribute to the community, whether as a single hosting organisation or in cooperation with others. Of course, I look forward to seeing you next week. - Donald Neal 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.

1 0

NZNOG 2008 - Informal Expressions of Interest
by Donald Neal 16 Mar '06

16 Mar '06

I'd be interested in hearing off-list from people who a) have been to at least one NZNOG conference in the past, and b) might be interested in hosting next year's conference. This is not about committing anybody to anything at this stage. It is a good time to start thinking about whether this is a way in which you could contribute to the community, whether as a single hosting organisation or in cooperation with others. Of course, I look forward to seeing you next week. - Donald Neal 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.

1 0

next week's meeting network
by Joe Abley 16 Mar '06

16 Mar '06

The network for next week's meeting is up and running at Vic (thanks to all concerned in making that happen). Here are the layer-3 details for those who want to open firewall holes, etc before they arrive and realise they can't reach their routers: IPv4: 169.222.252.0/24 IPv6: 2001:4401:3::/64 The meeting network is attached to the WIX, and peering with a few people (including the WIX route servers). If anybody else would like to turn up direct peering (or donate transit), send mail to noc(a)nznog.org.

2 1

Why copy Tradme's website to phish when you......
by Tristram Cheer 15 Mar '06

15 Mar '06

1 0

Congestion on Telecom bandwidth towards the Commonwealth Games streams
by Simon Blake 15 Mar '06

15 Mar '06

Hi Folks. Those of you who are using Telecom to get at the Commonwealth Games streams (rather than peering) may want to flush your DNS cache entries for "media6.tvnz.co.nz" (yes, we know the TTL's should have been wound down earlier, it got missed). If you do this, the RR DNS load balancing should kick in thus: before: $ host media6.tvnz.co.nz media6.tvnz.co.nz has address 202.7.7.65 after a cache clear, you should get: $ host media6.tvnz.co.nz media6.tvnz.co.nz has address 202.7.7.65 media6.tvnz.co.nz has address 202.7.7.57 Cheers Si

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 14 Mar '06

14 Mar '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.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: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050121 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060315 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Ltd - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.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: noc(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050907 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060315 source: NZRR

1 0

WTS some stock with best price from Kevin
by Kevn Wong 13 Mar '06

13 Mar '06

Dear Partner, Now we have the follows products in stock, if you are interesting in them, please feel free to contact me, they are 100% genuine and new, I hope that you don't miss it. Best Regards Kevin GIGABYTE USB 2.0 802.11G 54Mbps Wireless Lan card, the part number is GN-WB01GS, our offer is US$22.00/Pcs Ipod Nano 2GB US$145.00/Pcs Ipod Nano 4GB US$181.00/Pcs Sony Memory Stick 2GB US$79.50/Pcs Best Regards Kevin Room 2106, BaoAn Plaza, ShenNan Road,Shen Zhen City,China Tel: +86 755 26120509 Fax: +86 755 82816704 MSN: w_qifan(a)hotmail.com

1 0

Re: [nznog] Audio / Video recording in NZnog?
by Donald Neal 13 Mar '06

13 Mar '06

Neil, The plan is that conference sessions be videoed. Whether they'll be streamed will depend on whether the necessary resources, human and otherwise, are available. The timing of the Commonwealth Games is not helpful from that point of view. - Donald Neal -----Original Message----- From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] Sent: Tue 14/03/2006 11:43 AM To: nznog(a)list.waikato.ac.nz Subject: [nznog] Audio / Video recording in NZnog? Hi people... Are the conference presentations going to be videoed / streamed? Can attendees get copies of these or are we permitted to make our own? Answers on the back of a postcard please, to: Neil "I'm not reinventing the wheel again" Gardner Allied Telesis Labs NZ Chch, 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.

1 0

Audio / Video recording in NZnog?
by neil gardner 13 Mar '06

13 Mar '06

Hi people... Are the conference presentations going to be videoed / streamed? Can attendees get copies of these or are we permitted to make our own? Answers on the back of a postcard please, to: Neil "I'm not reinventing the wheel again" Gardner Allied Telesis Labs NZ Chch, NZ Cheers .. *** Note the change of name from Allied Telesyn Research, to *** *** "Allied Telesis Labs Limited" (ATL-NZ) *** Neil Gardner Router Product Manager Allied Telesis Labs Limited 27 Nazareth Ave / P.O Box 8011 / Christchurch New Zealand DDI +64 3 339 9509 Fax +64 3 339 3001 NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesis Labs Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesis Labs.

1 0

Re: [nznog] Campbell Live tonight
by Regan Murphy 12 Mar '06

12 Mar '06

>>"Theresa, if the data caps are only present because of the cost of international data, why are there data caps in place on UBS connections? >Wholesale UBS connections only connect end-users with local ISPs, and are therefore 100% local and non-international. Can you explain?" >I didn't see the show, but was this question asked? I'm guessing not. >JSR Forgive me for my late revival of the thread... I finally saw the segment and came away with one question: When they decided our entry-level broadband plans (based on the new prices etc. etc.) compete on a world scale, did they include the cost of the phone line rental in their baselining? As far as I know you still cannot purchase an ADSL connection without first purchasing a telephone line rental which costs $42.20 (Auckland cost according to the latest prices I received from Telecom). These costs when added together represent a minimum cost of $72.15 for broadband (under xtra's new plans) which is more than the $1.50 per day cost that Teresa referred to on the Campbell Live segment. Is this dual-charging common in the other OECD countries - especially those with LLU? -- Regan

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 12 Mar '06

12 Mar '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS23730 as-name: NZRR-AS23730 descr: NZNOG descr: WIX peering at '202.7.1.237' descr: see Citylink RT job #4804 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23730 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jabley(a)hopcount.ca mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060313 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23730 descr: Route set advertised to AS9439 by NZNOG - AS23730 members: 169.222.252.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: jabley(a)hopcount.ca mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060313 source: NZRR

1 0

Sponsor proposal ISP (Read)
by Felix Alcantara 10 Mar '06

10 Mar '06

Comments: We contact you concerning an advice and offer we would like to state, we would like to know if you are interested on providing some services regarding IRC networks especially to Undernet.org Details: we would like to locate a server (hardware) on your main site to be able to provide full peerings to our Server. Conditions: You will have full control of our activities, thru managing our Ports and Filtering our data transfer thru your peerings. And also we will maintain you informed of our root pass for further access of your tech members to monitor our inner activity. The benefits your site could gain from this deal are what I consider fair enough. Not only the MOTD (which is viewed daily by at least 2000 users) but also a support channel for your customers. Furthermore, please take a moment to have a look at the list containing the current Undernet sponsoring sites. This can be retrieved at http://www.undernet.org/sponsors.php . Why shouldn't you? Tech Request: we only need to have our server connected to the peerings, and a Dedicated IP with a reversed Host that could be irc.ispname.net. And we would like full approval of your NOC to allow use this IP to link to Undernet.org. Indeed Denial of Service Attacks are extremely damaging for small networks. However, I am sure that as long as we do not attract attention upon us, in the event of approval and linkage, we would be 'unspotted' by those who enterprise such actions. As such, I can guarantee you that no one from the Server Staff would perform actions that by their nature would attract Denial of Service attacks towards the server and your network. Sincerely, Félix Alcántara 1-(809)-854-9853 E-mail: speakz(a)speakz.org Speakz @IRC

12 16

NZNOG AUP
by Andy Linton 10 Mar '06

10 Mar '06

5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable.

1 0

Secure Space at Level 48
by jamie.baddeley＠vpc.co.nz 07 Mar '06

07 Mar '06

Hi, I'm organising the existence of a secure community cabinet at Level 48, Sky Tower. Right now the choice is pay the money for a complete rack/footprint, or take some space in the existing community racks. The thing is that I'd like to have my own key to a small amount of space (i.e. 10 or 20U). The price would be somewhere in between the current choices. Can anyone who'd be interested in having this sort of facility please email me offlist, and assuming enough are prepared to do it, a Secure Community Cabinet shall magically appear.... Cheers jamie

1 0

NZNOG 2006 Conference Speakers
by Donald Neal 06 Mar '06

06 Mar '06

Could any speaker who has not already received a draft conference timetable and instructions on how to register please contact me off-list. Thanks. A full draft timetable should appear on the conference web site late today. - Donald Neal Programme Coordinator Donald Neal |"Mouths are in oversupply but Support Engineer |brains/eyes are not." - Alan Cox NGN Operations | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Mar '06

05 Mar '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS10200 descr: advertised to AS9560 by NetSmart Ltd - AS10200 members: 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.37.168.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: paul(a)netsmart.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050315 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10200 descr: advertised to AS9560 by NetSmart Ltd - AS10200 members: 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: paul(a)netsmart.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060306 source: NZRR

1 0

NZNOG - Book your accommodation & travel ASAP
by Lin Nah 05 Mar '06

05 Mar '06

HI all Accommodation Things appear to be quite busy in Wgtn around that time and so you don't really want to be without somewhere to bunk down for the few hours between end of evening outing and wake up for the morning. The message I am getting from some of these providers are book ASAP. There's actually not one provider I rang up who had enough free rooms to accommodate all of us. Hence multiple places listed. Warning: Some of the accommodation providers are holding some rooms for us till sometime this week. They get released to general sale after that date. For example Nomads Capital are only holding rooms till 8 March. http://www.nznog.org/node/63 Despite having negotiated those rates, some of the rates offered by Wotif are slightly better (rates on Wotif tend to be GST inclusive whereas rates quoted to me (and put on website) are GST exclusive. Wotif accommodateion in Wgtn: http://www.wotif.co.nz/Search.jsp?refine=simpleSearch&country=2&region=3587 Travel There are some airfare specials that will end soon. eg AirNZ domestic sale is ends on 16 March for travel betwen 1 Mar - 31 Oct Other info look at the domestic travel section here: http://www.nznog.org/node/65 Obviously if you are going to book accommodation and travel, it won't take a couple of minutes for you to register for nznog! http://www.nznog.org/node/36 Regards Lin ps yes some of the pages do need some anchors so you can go to the right sections quickly. They'll be added. Just more important to get the information up and out to you guys. pps There will be a page going up soon on the social events. 8) As before, Wed and Fri night stuff won't be part of official conference fee.

1 0

Re: [nznog] OT: TradeMe sold
by Cameron Rangeley 05 Mar '06

05 Mar '06

Well done Walton.... C -----Original Message----- From: Nic Wise [mailto:nic.wise(a)aftermail.com] Sent: Monday, 6 March 2006 2:08 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] OT: TradeMe sold Fairfax owns stuff.co.nz et al. So.... <hands network map to someone else> >From all the articles, they sound like they are leaving TM alone. My guess is, they bought it to hit Australia. TM is just so much cleaner than eBay. > -----Original Message----- > From: Matthew Poole [mailto:matt(a)p00le.net] > Sent: Monday, 6 March 2006 1:58 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] OT: TradeMe sold > > > Not strictly network related, but to keep it roughly on-topic > I would imagine that the $700m that Fairfax is paying to > acquire TradeMe will buy a few beers. > > Anyone know who Fairfax use for the connectivity? Might we > see TM go offline again as corporate IT flexes its > institutional stupidity and de-invents the wheel vis peering? > > -- > Matthew Poole > "Don't use force. Get a bigger hammer." > > _______________________________________________ > 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 The information contained in this e-mail message is intended only for the use of the person or entity to whom it is addressed and may contain information that is CONFIDENTIAL and may be exempt from disclosure under applicable laws. If you read this message and are not the addressee you are notified that use, dissemination, distribution, or reproduction of this message is prohibited. If you have received this message in error, please notify us immediately and delete the original message. You should scan this message and any attached files for viruses. True Technologies accepts no liability for any loss caused either directly or indirectly by a virus arising from the use of this message or any attached file. All Prices unless otherwise stated are exclusive of GST. ##################################################################################### To find out how to say goodbye to SPAM and non productive emails with MailMarshal contact True Technologies (09) 2736973 #####################################################################################

1 0

OT: TradeMe sold
by Matthew Poole 05 Mar '06

05 Mar '06

Not strictly network related, but to keep it roughly on-topic I would imagine that the $700m that Fairfax is paying to acquire TradeMe will buy a few beers. Anyone know who Fairfax use for the connectivity? Might we see TM go offline again as corporate IT flexes its institutional stupidity and de-invents the wheel vis peering? -- Matthew Poole "Don't use force. Get a bigger hammer."

2 1

Re: [nznog] OT: TradeMe sold
by Nic Wise 05 Mar '06

05 Mar '06

Fairfax owns stuff.co.nz et al. So.... <hands network map to someone else> >From all the articles, they sound like they are leaving TM alone. My guess is, they bought it to hit Australia. TM is just so much cleaner than eBay. > -----Original Message----- > From: Matthew Poole [mailto:matt(a)p00le.net] > Sent: Monday, 6 March 2006 1:58 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] OT: TradeMe sold > > > Not strictly network related, but to keep it roughly on-topic > I would imagine that the $700m that Fairfax is paying to > acquire TradeMe will buy a few beers. > > Anyone know who Fairfax use for the connectivity? Might we > see TM go offline again as corporate IT flexes its > institutional stupidity and de-invents the wheel vis peering? > > -- > Matthew Poole > "Don't use force. Get a bigger hammer." > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

New IP to ASN Mapping Services
by Rob Thomas 01 Mar '06

01 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those who receive this post in multiple forums. ] Team Cymru is happy to announce the availability of various service options dedicated to mapping IPv4 numbers to BGP prefixes and ASNs. These services come in various flavors, including: * Whois, DNS, HTTP, HTTPS Each of the services is based on the same BGP feeds from 50+ BGP peers, and is updated at 4 hour intervals. Using a single IP or ASN one can obtain any of the following information: * BGP Origin ASN * BGP Peer ASN * BGP Prefix * Prefix Country Code (assigned) * Prefix Registry (assigned) * Prefix Allocation date * ASN Country Code (assigned) * ASN Registry (assigned) * ASN Allocation date * ASN Description The country code, registry, and allocation date are all based off of data obtained directly from the regional registries including: ARIN, RIPE NCC, AFRINIC, APNIC, LACNIC. The information returned relating to these categories will only be as accurate as the data present in the RIR databases. The ASN descriptions are based off of data obtained from cidr-report. For a summary on how to use these services please visit the following web page: <http://www.cymru.com/BGP/asnlookup.html> If you have any comments, questions, or suggestions please feel free to contact us at: team-cymru(a)cymru.com. Thanks! Rob. - -- Rob Thomas Team Cymru http://www.cymru.com/ ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBRAciKlkX3QAo5sgJAQFS4gP8CXz2ZIlzfK5+/6bj7TZVN33e29eifH0+ WKjfbrVKEchQTwCjvkoowtH9Mcr8H0iqf4vb9sQLAxojedFe39Gi5xtW+BGFQ1Te hwdrF0n5QaGjecV0ID+XAzgGxrwC+4CVfaLtYG8mL/SD2VlUs6SpaN22YGjMRKM2 8y0LT9HAly0= =1moY -----END PGP SIGNATURE-----

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '06

01 Mar '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.36.170.0/24^24-29, 202.36.227.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tsalmen(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060302 source: NZRR

1 0

192.203.154.23 natcom.ape.net.nz
by Russell Fulton 01 Mar '06

01 Mar '06

Would whoever is responsible for this router please drop me a line off list. Nothing really urgent :) Or if someone can point me to a contact address... Russell -- Russell Fulton, Information Security Officer, The University of Auckland New Zealand

2 1

NZNOG 06 - March 22-24 , Registrations online
by Simon Lyall 28 Feb '06

28 Feb '06

NZNOG 06 - Registrations now online. http://www.nznog.org The next conference of the New Zealand Network Operators' Group is to be held in Wellington, New Zealand between 22-24 March 2006. The conference is on the week before the ICANN meeting in Wellington so people can attend both events. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of networked services, with particular emphasis on New Zealand. The conference has a strong technical focus with the aim of attracting a strong turnout of technical personnel. The conference fee is affordable to most to encourage greater participation This year we have a strong programme of New Zealand and overseas speakers on a wide range of topics over 3 days. The programme includes talks on VoIP, DNSSEC, IPv6, BGP, 10G Networks, Peering, QoS and Content-delivery. NZNOG 2006 registration fee is $250 for three days See http://www.nznog.org for more details. My apologies if you see multiple copies of this announcement. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Feb '06

28 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS64646 OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060301 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS64646 OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES OR AS64646 AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES OR AS64646 AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060301 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Feb '06

28 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS64646 OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060301 source: NZRR

1 0

The New Zealand Network Operators' Group
by Donald Neal 28 Feb '06

28 Feb '06

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, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's THIS MONTH. See http://www.nznog.org/ to register. Seating is as ever limited, and places are allocated on a "first come, first served" basis. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ 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, and some information on others under construction. About This Mailing List This list has around 900 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 Alcatel NZ Ltd, Citylink and Telecom. 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 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.

1 0

Re: [nznog] Campbell Live tonight
by Peter Mott 25 Feb '06

25 Feb '06

>So, no it's not public domain (though publicly available, >albeit streaming only) and no the permission of the copyright >holder was not sought. It's just an alternative for those >without the means to stream. Above appears to be a modern day term for justified theft of somebody elses property. If I was TV3 I would be inviting you to an education programme down at the local court house. regards Peter Mott MOTT & ASSOCIATES Tel: +64 9 488 9352 Fax: +64 9 486 7017 -/-

11 14

The Origins of "2006 NZ Census - Are you a New Zealander"
by Craig Whitmore 24 Feb '06

24 Feb '06

A little (lot) OT but.... Does anyone know the origins of this email. It seems its going around like wildfire at the moment. Yes I could ask the person who sent it to me who sent it to them and so on and so on.. its getting a little anoying now.. I have 10 copies already from just this morning. I guess its like the last Census where the email about being a Jedi was sent around. Subject: 2006 NZ Census - Are you a New Zealander? Did you know that New Zealand is pretty much the only place in the world that you can not actually be a New Zealander? Whenever you fill out a form or survey in New Zealand you can tick the box to say you are Maori, Tongan, Samoan, Australian, European (or NZ born of European Decent), Asian, etc but there is no box provided to say "Yes, I am a New Zealander and I am proud to be one" In Australia, you can be an Australian... In fact in Australia you can be a New Zealander. etc.. etc Thanks Craig

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Feb '06

23 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 202.49.128.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050627 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/21^21-29, 202.49.183.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060224 source: NZRR

1 0

IMPORTANT: Re NZNOG Registration!
by Mark Foster 23 Feb '06

23 Feb '06

Folks, For all registrations - despite what has been posted previously - please treat the following url as authoritive. All persons registering to attend the conference MUST read the content on this page, even if you've gone direct to VUW's reg page. http://www.nznog.org/register Note that www.nznog.org has had a major overhaul and is probably worth a look. My thanks to Lin, Donald and Joel for their assistance with this. Mark - nznog.org conference webmaster-of-sorts....

2 2

APNIC 21 - Participate in the meeting from anywhere
by Nurani Nimpuno 22 Feb '06

22 Feb '06

+ + + + + NEWSFLASH: New services starting at APNIC 21! - Live streaming audio - Podcasts + + + + + Dear APNIC members and friends APNIC 21 begins in a few days. Here are some last minute tips on making the most of the meeting. 1. Remote participation ----------------------- Can't make it in person to APNIC 21 in Perth? Then follow the events online in real time anywhere in the world via: - Jabber chat rooms - Live transcripts - Streaming video - Streaming audio In addition, you can now access the Jabber chat rooms using your web browser. Archives of the audio, video and transcripts will also be available soon after each session. For more information on how to participate online, go to: http://www.apnic.net/meetings/remote 2. Meeting checklist --------------------- With less than a week remaining before the meeting, it is important to do the following: 1. Register online 2. Choose a voting option for the APNIC EC election 3. Book your hostmaster consultation online For assistance, please go to: http://www.apnic.net/meetings/21 Or contact: <meetings(a)apnic.net> We look forward to seeing you in Perth! Best regards ------------------------------------------------------------------------ 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-3219 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ------------------------------------------------------------------------ See you at APNIC 21 Perth, Australia, 27 February - 3 March 2006 http://www.apnic.net/meetings/21 ------------------------------------------------------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Feb '06

22 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64551 descr: advertised to AS9439 by Breathe Communications - AS64551 members: 161.29.192.32/27^27-29, 202.135.231.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: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050908 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64551 descr: advertised to AS9439 by Breathe Communications - AS64551 members: 161.29.192.32/27^27-29, 202.135.231.48/28^28-29, 202.160.118.224/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: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060223 source: NZRR

1 0

NZNOG 2006 registration and online payment web page(s)
by Peters MCS Mail 22 Feb '06

22 Feb '06

Apologies to the list for the long wait. Here are the links for NZNOG 2006 conference registration https://www.mcs.vuw.ac.nz/cgi-bin/events/nznog and for those only interested in the APNIC Internet Resource Management tutorial: https://www.mcs.vuw.ac.nz/cgi-bin/events/apnic Regards Peter

1 0

Fwd: FW: SORBs blacklisting Paradise MTAs
by Paul Adshead 22 Feb '06

22 Feb '06

Having previously been listed on the SORBS list, I can say from personal experience that trying to get any information from them is like trying to draw blood from a stone. You just give up - there is quite literally nothing you can do. The legal stuff on their site says something like "you are not supposed to block access based on information on this site", yet that is exactly why their site has been created. That's their legal 'get out' to avoid all liability. Their attitude stinks. They are quite happy to cripple your business for days/weeks at a time and their response time after an issue has been resolved is pathetic. Paul -----Original Message----- From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] Sent: Wednesday, 1 February 2006 14:12 To: nznog(a)list.waikato.ac.nz Subject: [nznog] SORBs blacklisting Paradise MTAs Hi gents (and gentesses) I reported to Paradise that Sorbs was blacklisting a particular Paradise MTA last night (details below) and their response was that sorbs refuse to whitelist them so there's nothing they can do about it... The further state that "SORBS automatically delist the servers after a 48 hour time period, and mail passing through the once affected mail server should flow as per normal." yet the information pasted below seems to indicate that the particular IP I reported has been on the list since Dec 11th 2005. They're spinning me a line right? The Sorbs record hasn't been updated since Dec 11th! *--- Info from sorbs as of 5 minutes ago *--- Address: 203.96.152.180 Record Created: Sun Dec 11 13:53:04 2005 GMT Record Updated: Sun Dec 11 13:53:04 2005 GMT Additional Information: Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by vampire.isux.com (Postfix) with ESMTP id 58986B90C; Sun, 11 Dec 2005 13:52:40 +0000 (UTC) Currently active and flagged to be published in DNS *--- end info from sorbs *--- Why would Paradise deliberately avoid resolving this issue when pointed out to them? If anyone from Paradise / Telstraclear would like to jump in and explain why your helpdesker effectively refused to do anything about the situation then I'm all ears. Yes, I did report to Paradise through the appropriate mechanism, then I replied to their automated response, then this morning I phoned to report it and had my number taken (no-one has phoned back) and a few minutes ago I received the reply to the original message saying they can't do anything. Cheers - Neil G Neil Gardner Product Manager Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

5 5

Re: [nznog] HEADS UP - upcoming webcast
by Richard Naylor 22 Feb '06

22 Feb '06

To save answering this question many times At 04:34 PM 2/22/2006 +1300, you wrote: >On Wed, 22 Feb 2006, Richard Naylor wrote: > > This is an excellent opportunity to show what the Internet can deliver in > > terms of interesting and compelling content. Arrangements have been made > > with Telecom NZ to make traffic flows optimal and we thank them for their > > support and co-operation. > >So does this mean people getting DSL via Xtra will be able to watch it? yes.

15 19

Re: [nznog] Campbell Live tonight
by Donald Neal 22 Feb '06

22 Feb '06

> >So, no it's not public domain (though publicly available, > >albeit streaming only) and no the permission of the copyright > >holder was not sought. It's just an alternative for those > >without the means to stream. > > Above appears to be a modern day term for justified theft of somebody > elses property. If I was TV3 I would be inviting you to an education > programme down at the local court house. > > > regards > > Peter Mott I think we've agreed that advertising on this list copies of copyrighted material made without the consent of the copyright holder is not an acceptable use of the list. Which means this thread can now go away? - Donald Neal Donald Neal |"Mouths are in oversupply but Support Engineer |brains/eyes are not." - Alan Cox NGN Operations | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

1 0

FW: HEADS UP - upcoming webcast
by Steve Biddle 21 Feb '06

21 Feb '06

Will this be a single simulcast of the TVNZ feed or will there be multiple feeds available? One of the great things overseas in countries with satellite TV operators covering both the commonwealth and olympic games has been the mutiple feeds allowing you to watch a single channel showing a bit of everything(much like out broadcast in NZ) and then other channels dedicated to showing other events live. I've been trying to find out if TVNZ have any plans to do such a thing with their FTA satellite channels but haven't heard anything as of yet. > -----Original Message----- > From: Richard Naylor [mailto:richard.naylor(a)citylink.co.nz] > Sent: Wednesday, 22 February 2006 16:10 > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] HEADS UP - upcoming webcast > > > Afternoon all, > > R2/Citylink has been contracted by TVNZ to assist with the > webcasting of > the Commonwealth Games next month, starting on 15 March and > concluding on > 26 March. On most days the webcast will run from around 10am > until 1 am > with breaks for things like News and Close Up. > > Because of broadcast rights, this webcast is being restricted > to NZ and > will use TVNZ/R2/CityLink servers located in Auckland and Wellington > connected via APE and WIX. > > In the case of wild demand, there are extra servers on > standby at each > location. > > Operators should be aware that this event is taking place > during business > hours and many viewers only access may be via their PC and > this webcast. > Traffic volumes may be higher than normal and support calls > to Help Desks > may be increased, particularly at sites where ports 80, 554 > or 1755 are > blocked. > > This is an excellent opportunity to show what the Internet > can deliver in > terms of interesting and compelling content. Arrangements > have been made > with Telecom NZ to make traffic flows optimal and we thank > them for their > support and co-operation. > > If you have any concerns, please contact me for further details. > > Thanks - Richard > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

21 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '192.203.154.5' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '192.203.154.5' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

21 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '202.7.0.7' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '192.203.154.5' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

21 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '202.7.0.7' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

21 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050331 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/24^24-29, 202.7.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 mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: Route set advertised to AS9439 by MediaNET - AS23755 members: 202.7.4.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: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR

1 0

HEADS UP - upcoming webcast
by Richard Naylor 21 Feb '06

21 Feb '06

Afternoon all, R2/Citylink has been contracted by TVNZ to assist with the webcasting of the Commonwealth Games next month, starting on 15 March and concluding on 26 March. On most days the webcast will run from around 10am until 1 am with breaks for things like News and Close Up. Because of broadcast rights, this webcast is being restricted to NZ and will use TVNZ/R2/CityLink servers located in Auckland and Wellington connected via APE and WIX. In the case of wild demand, there are extra servers on standby at each location. Operators should be aware that this event is taking place during business hours and many viewers only access may be via their PC and this webcast. Traffic volumes may be higher than normal and support calls to Help Desks may be increased, particularly at sites where ports 80, 554 or 1755 are blocked. This is an excellent opportunity to show what the Internet can deliver in terms of interesting and compelling content. Arrangements have been made with Telecom NZ to make traffic flows optimal and we thank them for their support and co-operation. If you have any concerns, please contact me for further details. Thanks - Richard

1 0

Re: [nznog] NZNOG conference
by Donald Neal 20 Feb '06

20 Feb '06

> From: David Robb [mailto:ender(a)paradise.gen.nz] > Sent: Wednesday, 25 January 2006 10:18 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] NZNOG conference > > Is there any further information available for this? ie > costs, who else is > speaking? > > I'm going to need to make a decision very soon as to whether > or not I can > justify my attendance. As to who is speaking, we've run into a problem with a number of speakers agreeing to provide abstracts to go on the web site, then not getting around to providing them. You know who you are. Among our more virtuous speakers are Mark Foster Bridging the Gap Between Support and the NOC Richard Hulse The Economics of Peering Peter Komisarczuk Location Determination for WLAN and 3G Hamish MacEwan Peering - The Customer Perspective Ian McDonald TCP Congestion Control Andrew McMillan Extending SPF to include policy for TLS Dean Pemberton Investigations into Internet Background Radiation Geoff Scrimgeour Welcome to The Loop Scott Walsh Network Security through Firewall Segregation Bill Woodcock Building Global Content-Distribution Networks I expect to announce more during the coming week. - Donald Neal Donald Neal |"I'm busy. I have papers to read, Support Engineer |reports to write, bosses to NGN Operations |infuriate." - Lt. Giardello Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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.

3 2

Cisco 3550 replacement
by Jacky Lam 19 Feb '06

19 Feb '06

Hi all, I'm currently looking for a CPE that can replace the Cisco 3550 we currently deploy in our network. Key features that I'm looking for are as follows: Hierarchical QOS Traffic shaping/policing L3VPN functionality(VRF-lite) BGP OSPF dot1q some sort of spanning tree Any help would be really appreciated, Jacky

2 1

Help: Questionaire...
by Mark Foster 18 Feb '06

18 Feb '06

Hi Team, I'm doing some legwork in aid of my presentation at NZNOG06 Conference. If the reader is what you might call 'Helpdesk' and would be interested in answering a brief questionaire about your job, please drop me an email off list. All information collected will be used in aid of the presentation, noones details will be disclosed to anyone else, it'll remain anonymous, etc. I'm particularly after perspective from those who work in tech support, either for ISPs or larger companies. I may have something for 'NOC type people' at a later stage, too. Thanks for your help Mark.

1 0

Re: [nznog] NZNOG Digest, Vol 38, Issue 12
by ganda y situmorang 17 Feb '06

17 Feb '06

On Sat, 18 Feb 2006 12:00:04 +1300 nznog-request(a)list.waikato.ac.nz wrote: > 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. Notification of NZRR Database changes > (NZRR Database Notifications) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 17 Feb 2006 16:01:02 +1300 >From: NZRR Database Notifications <rpsl-admin(a)nzix.net> > Subject: [nznog] Notification of NZRR Database changes > To: nznog(a)list.waikato.ac.nz > Message-ID: <E1F9vri-0007kB-LU(a)zidane.citylink.co.nz> > > > > Dear Colleague, > > This is to notify you that some object(s) in NZRR >database > which you either maintain or are listed as >to-be-notified have > been added, deleted or changed. > > 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. > > --- > PREVIOUS OBJECT: > > route-set: AS9560:RS-ROUTES:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9560:RS-ROUTES:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > --- > PREVIOUS OBJECT: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > > > ------------------------------ > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > End of NZNOG Digest, Vol 38, Issue 12 > ************************************* ======================================================================================== Ikuti Lomba Puisi Online Jawa Timur, dapatkan hadiah menarik setiap bulannya dan hadiah total senilai 60 juta rupiah hanya di http://www.plasa.com (Khusus Jawa Timur) ========================================================================================

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Feb '06

16 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR

1 0

SMTP Greylisting
by Craig Whitmore 15 Feb '06

15 Feb '06

I have been playing around with greylisting recently on a couple of test domains and it works pretty well (reduces the number of spam coming from malwared machines who don't retry sending their spam by over 90% before any spam checkers get to it), but I've noticed a number of real mail NZ servers not knowing what a 451 SMTP message is, and they treat it like a fail and they don't send the message again. (Yes I know I can whitelist good known NZ SMTP Serversto not Greylist from them) If anyone else has tried greylisting before , or has any comments on it, let me know. Thanks Craig

10 12

Providers located at Northcote DC
by Barry Murphy 15 Feb '06

15 Feb '06

Hey there beer drinkers, Is anyone here hosting equipment at Vectors Data Center on Northcote Road, Auckland? I currently use Orcon as my bandwidth provider (both national & international) but am looking for backup routes, so if you have connectivity to either Telstra or direct to APE at the facility, please give me a hola offlist. Cheers Barry

1 0

Re: [nznog] SMTP Greylisting
by Ewen McNeill 14 Feb '06

14 Feb '06

In message <20060214230142.GZ26689(a)citylink.co.nz>, Simon Blake writes: >We've been using greylisting here for the last six months, and it's made >a huge difference to the amount of noise [.... through other filters ....] >I would set your timeout to be really low - 15 seconds would be as >effective as 30 minutes, as far as I can see. I can't help wondering how long this beneficial effect of greylisting will last. It's not _that_ difficult for a spammer to ask their purchased botnet to run its spam list twice. Worst case they need twice as many bots. It's not like it's hard to buy 0wn3d machines these days. Those with greylisting enabled get the message once; those without may well get it twice. Bonus. If greylisting becomes relatively common that's exactly what I'd expect spammers to do. And viruses to do. (Viruses can simply follow the same PRNG or discovered list twice. Perhaps 30-60 minutes apart. Not much extra work, for much more effectiveness.) So what do we do next? Defer twice before accepting? Give up on greylisting? And then get two copies (or three copies)? Seems to me that the end result of this particular "arms race" is that mail delivery gets permanently delayed (since no one can "safely" turn off greylisting without getting multiple copies of the junk), and we end up no further forward on the spam/virus problem. Not that I really see an option which doesn't end up "email becomes even more useless" over a relatively short period of time. Frankly I'm amazed it's lasted this long. We've had 5+ years of what is effectively a sustained denial-of-service attack on email. Ewen

2 1