- NZNOG - lists.nznog.org

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 15 Feb '06

15 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

Webcasting Heads Up
by Richard Naylor 13 Feb '06

13 Feb '06

(Wearing my R2 hat) It appears we will be webcasting the 2nd reading of the NZ Sign Language Bill on 23 Feb 06 at around 3pm (after Parliament's Question Time). This will last for approximately 1 hour and has a reasonable audience in the low hundreds. (they packed the House last reading as well and overflowed into two rooms). For those who are unaware, the NZ Sign Language Bill will establish NZ Signing as the third Official Language of NZ, so the passage of the legislation is of interest to the Hearing Impaired community both in NZ and internationally. As before we will run 2 sets of streams - the main camera mix plus a fixed shot of the sign language interpreters. As we are not bandwidth constrained, we will also be running a full set of streams (56kbps, 128kbps, 384kbps and 2Mbps) and they will be served off servers at the main NZ IX points, plus the USA. CityLink advise me that anyone wanting help with a quick peering session with my routers should speak to Andy Linton. I'm happy to set up short duration/temp sessions. In addition, tomorrow we will be making Bloomberg TV available on our servers. This premiere news service will be of interest to the financial community. At the moment the streams are limited to 256kbps, but please note the "at the moment". The streams are available across all servers without restriction. For those interested, the link is http://www.r2.co.nz/meta/bloombergtv.asx Thanks and happy viewing. Rich

1 0

Re: [nznog] SMTP Greylisting
by Jeremy Strachan 13 Feb '06

13 Feb '06

I'm ignoring your email, if its an important topic you'll send beer to grab my attention first. -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: Tuesday, 14 February 2006 1:41 p.m. To: nznog Subject: Re: [nznog] SMTP Greylisting On Tue, 14 Feb 2006, Craig Whitmore wrote: > If anyone else has tried greylisting before , or has any comments on > it, let me know. Personally I find greylisting a pain. I am subscribed to a couple of lists that use it and it's annoying when my reply to the list takes half an hour to get through instead on 2 minutes. One important thing to watch for is that for larger sites the server that first tries to send your email might not be the one that tries to resend it later. Greylisting sites will thus block the email for a while until the sending site gets lucky and uses the same machine twice in a row. Generating random error messages to sending sites is just asking for trouble IMHO. You really can't determine exactly they will act and how long they will take to retry to send the message. Any delay is 100% your fault although most people using greylisting seem keen to push the blame to the sending site. It's the equivalent of ignoring someone when they first email/call you and saying "If it's important they'll ring back" . Not very polite and possibly not providing the best service to customers. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ 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 12 Feb '06

12 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. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9236 descr: advertised to AS9439 by AMP - AS9236 members: 203.118.136.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jimi.wallace(a)ampcapital.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR

1 0

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

12 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:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/20^20-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050920 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR

1 0

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

09 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:AS10022 descr: Route set 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 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.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

1 0

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

09 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. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS10022 descr: Route set 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 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

1 0

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

08 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: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.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, 202.191.32.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.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

1 0

Re: [nznog] iprimus.net.au
by Gordon Smith 08 Feb '06

08 Feb '06

That's what they have listed http://www.abuse.net/lookup.phtml?DOMAIN=iprimus.net.au ________________________________ From: Paul Adshead [mailto:paul.adshead(a)gmail.com] Sent: Thursday, 9 February 2006 11:40 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] iprimus.net.au Can anyone please confirm the "iprimus.net.au" abuse/spam email address - abuse(a)iprimus.net.au? I can't find it listed. Thanks, Paul.

1 0

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

08 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: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.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 20060201 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.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, 202.191.32.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 --- 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.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 20060201 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.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

1 0

iprimus.net.au
by Paul Adshead 08 Feb '06

08 Feb '06

Can anyone please confirm the "iprimus.net.au" abuse/spam email address - abuse(a)iprimus.net.au? I can't find it listed. Thanks, Paul.

1 0

Someone from Paradise
by Geraint M. Jones 08 Feb '06

08 Feb '06

Would someone from paradise please be kind enough to contact me offlist Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net DDI: +64 (0)4 570 7633 Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240

1 0

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

02 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. --- OBJECT BELOW CREATED: aut-num: AS9788 as-name: NZRR-AS9788 descr: Inland Revenue Department descr: WIX peering at '202.7.1.15' descr: see Citylink RT job #4229 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9788 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: osi(a)ird.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9788 descr: Route set advertised to AS9439 by Inland Revenue Department - AS9788 members: 138.235.0.0/16^16-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: osi(a)ird.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR

1 0

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

02 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:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050909 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050909 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR

1 0

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

01 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 AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND 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 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

1 0

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

01 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 ANY 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 AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385: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 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 AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND 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

1 0

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

31 Jan '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.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.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 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 20050901 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.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 20060201 source: NZRR --- 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.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.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 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 20050901 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.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 20060201 source: NZRR

1 0

SORBs blacklisting Paradise MTAs
by neil gardner 31 Jan '06

31 Jan '06

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.

2 2

Re: [nznog] SORBs blacklisting Paradise MTAs
by Nic Wise 31 Jan '06

31 Jan '06

If it's any help - and I'd expect most people here to know this anyway - Paradise pop up on RBL's so often, I've had to add a whitelist for them in my system, or most of the people I know (who use cable) get blocked. This isn't a new thing at all. :) Cheers Nic > -----Original Message----- > From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] > Sent: Wednesday, 1 February 2006 2:12 p.m. > 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. >

1 0

Update re NZNOG 06 Pricing
by Mark Foster 31 Jan '06

31 Jan '06

In light of recent enquiries, The Organising Committee for NZNOG 06 can confirm that the rates-per-person for attendance at NZNOG06 are likely to be in the ballpark of $250/person. If anything they will wind up lower than this, as sponsorship arrangements are finalised, etc. Note: This does NOT include accomodation, but it does include morning coffee, lunch, and afternoon tea, as well as the conference dinner. More info as it comes to hand; this info will be added to the nznog.org site when I get somewhere that allows SSH out its firewall. :) I hope this info is enough for people to get their respective managers approvals for our excellent-value-for-money event. The guest-speaker list will be further updated tonight as well, so take a peek at nznog.org tomorrow for the latest. Cheers Mark, For the NZNOG Organising Committee.

1 0