- NZNOG - lists.nznog.org

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