- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 10 May '09

10 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks Second APE6 - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: neil.fenemor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090325 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2002:0:0:0:0:0:0:0/16^16-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 May '09

10 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 May '09

10 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090511 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 May '09

07 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 May '09

07 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.14.32.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.136.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090508 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 06 May '09

06 May '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.90.128.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.176.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.78.128.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 218.100.52.0/23^23-29, 220.233.4.0/23^23-29, 58.87.6.0/24^24-29, 58.96.0.0/24^24-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.5.127.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.15.243.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.187.0/24^24-29, 203.18.197.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.79.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090409 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 112.141.0.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 118.127.176.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 118.127.168.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.136.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.169.180.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 117.18.238.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.100.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.4.226.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.61.2.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.172.156.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.87.6.0/24^24-29, 58.181.65.0/24^24-29, 59.86.180.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.86.190.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 110.76.128.0/24^24-29, 114.111.128.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 116.90.138.0/24^24-29, 117.18.232.0/24^24-29, 117.18.235.0/24^24-29, 117.18.237.0/24^24-29, 119.31.248.0/24^24-29, 119.161.82.0/24^24-29, 119.161.84.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 124.248.140.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.44.0/24^24-29, 202.36.119.0/24^24-29, 202.36.157.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.112.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.37.234.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090507 source: NZRR ------------------------------------------------------------

1 0

Wholesale DSL Opportunity
by Ben Cornish 05 May '09

05 May '09

All, We are looking at expanding our national Australian network into New Zealand, and as such we are looking for a partner to assist us with this. In the short term, we are looking for Transit and also access to Telecom NZ DSL tails(to be handed off as L2TP sessions over Ethernet preferably). Handoff location would be Sky Tower. Is there anyone interested in this opportunity - please contact me off list Thanks Ben Cornish National Network Manager Direct 07 3234 9302 Direct: 02 8235 3520 Mobile 0417 617 204 Email mailto:benc(a)brennanit.com.au Web http://www.brennanit.com.au/ http://www.brennanit.com.au/

1 0

Re: [nznog] 922Mhz SRD Link
by Brislen, Paul, VF-NZ 01 May '09

01 May '09

Hi all. We can't make any public statement about this interference until after the court hearing, early next week, but after that I'm happy to get one of the network guys to come in and chat about it with you if a: that would help, b: that's of interest and c: they're not already here under their own steam. Cheers Paul -------------------------------------------------------------------- This message was sent from my BlackBerry Wireless Handheld from Vodafone ________________________________ From: nznog-bounces(a)list.waikato.ac.nz To: NZNOG(a)list.waikato.ac.nz Sent: Sat May 02 08:55:23 2009 Subject: Re: [nznog] 922Mhz SRD Link Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I’m pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone’s face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=10569… relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ----------------------------------------------------------------------------------------------- Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Vodafone New Zealand Limited.

3 2

Re: [nznog] 922Mhz SRD Link
by andrew＠borg.co.nz 01 May '09

01 May '09

Thanks Ian, Yes I believe that this is likely to be the same problem and the issue is not just causing problems for Vodafone but also smaller operators. The fact that MED have confirmed that they are operating within the allowable channels is of some concern as this would mean there is little that can be done however using equipment legal or not that can squash competition is surely an anticompetitive act. That aside I have completed another can of the area and was wrong on the power levels received from a 3rd cell phone operator, it was just over 2V/m and I'm pretty sure a signal this strong is really not healthy. This was obtained from 150/200m away. Not trying to get up in anyone's face here but I wonder if in fact Telecom are being blamed for something that is being caused by other vendors networks as well. Have MED created some of the issues by slicing the available channels too fine as was the case with out tests of the WiMAX gear recently. And If MED has and is allowing the deployment of equipment that is making the public spectrum un-usable and they can not force the vendors to clean up their act then maybe they need to look at opening up some more USABLE public spectrum rather than just putting it up for auction where again only the big players have the funds available to purchase these ranges (and associated equipment). Regards Andrew -----Original Message----- From: Ian Batterbee [mailto:ibatterb(a)gmail.com] Sent: Friday, May 01, 2009 10:01 PM To: andrew(a)borg.co.nz Subject: Re: [nznog] 922Mhz SRD Link http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5 <http://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=1 0569875> &objectid=10569875 relevant maybe ? andrew(a)borg.co.nz wrote, On Fri 01/05/2009 19:06: Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew _____ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] The Internet is in the news!
by Yun Huang Yong 01 May '09

01 May '09

I think this is the Onion piece: http://preview.tinyurl.com/d5h8np At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -- (__) Share what you know. Yun Huang Yong `\------(oo) Learn what you don't. gumby(a)mooh.org || (__) --' goosmurf(a)yahoo.com \|/ ||w--|| \|/ --

12 12

922Mhz SRD Link
by andrew＠borg.co.nz 30 Apr '09

30 Apr '09

Is there any one in the Manukau region using a 900Mhz SRD link? Over the last month or so we have seen a huge amount of interference on the 900Mhz spectrum that has resulted in problematic links. Although we have not been able to isolate the reason for the interference I would be interested in working with any other user in the area who may be having issues. So far we have found that the recent deployment of telecoms new system based on wideband CDMA has increased the power flux density and as a result it appears that this may be part of the problem. Opposite our site is another carrier operating on 940Mhz and from a distance of 150+m we are picking up their signal at -7db and at a power level of around .8mv/m2 so there could be some inter modulation going on there. I would be keen on comparing notes with anyone else on this. Regards Andrew

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

> >So would you trust a guy in a pink Hawaiian shirt to analyse and > >recommend the future of the internet? Being from Hawaii no, I wouldn't... ;-) Try something like these instead. http://www.alohashirtshop.com/docs/view_image.php?id=11361&width=608 http://www.hawaiian-shirt.net/paradise_found/pf08/bamboo_embroidery_bk_pf.j… ---------- bmanning(a)vacation.karoshi.com wrote: -------------- From: bmanning(a)vacation.karoshi.com pragmatically, WTF are folks going to do when you can't get more IPv4 space from APNIC? Pick the best answer(s): ) IPv6 ) NATs all the way down ) hijack space from others ) find a new line of work as a beer-bottle washer -------------------------------------------------------------- Ipv6 and whatever the new name for NAT-PT is. Then LISP? http://www.1-4-5.net/~dmm/lisp scott ------------------- ------------------- -------------------

1 0

Re: [nznog] The Internet is in the news!
by Scott Weeks 30 Apr '09

30 Apr '09

At 09:23 AM 1/05/2009, Ian Batterbee wrote: >That was so bad I thought I was reading an article from the onion! > >Ruh roh. We'd better all upgrade to Internet 2. -------- gumby_lists(a)mooh.org wrote: -------- From: Yun Huang Yong <gumby_lists(a)mooh.org> I think this is the Onion piece: http://preview.tinyurl.com/d5h8np ------------------------------------------------- That's just about the silliest thing I have seen! "The internet has been up for 5000 days, about 13 years, and hasn't broken down once." According to that the internet was 'started' in 1996! (See RFC 1 by Steve Crocker April 1969) I wonder what the hell I was on in 1987! Surely they wouldn't want to know about the introduction section of RFC 1254: A large number of widely dispersed Internet sites experienced simultaneous slowdown or cessation of networking services for prolonged periods... "youtube transmits more data than the internet." Wow, I didn't know youtube was out of band... ;-) I think the pink aloha shirt was affecting the brain of "sunrise gadget guy". That thing is worse that the old Magnum PI shirts! http://www.mokuman.com/images/magnumpi-shirt_header534.jpg scott ------------------- -------------------- --------------------

2 1

Re: [nznog] The Internet is in the news!
by Stu Fleming 30 Apr '09

30 Apr '09

Isn't a "brown-out" what an "ohnosecond" used to be called, being the approximate period of time between making a live config change and discovering the device non-responsive as a result? Brown-out being more expressive as it also describes the effect on the operator succinctly.

1 0

The Internet is in the news!
by Nathan Ward 30 Apr '09

30 Apr '09

http://technology.timesonline.co.uk/tol/news/tech_and_web/the_web/article61… "Internet users face regular "brownouts" that will freeze their computers as capacity runs out in cyberspace, according to research to be published later this year." Ruh roh. We'd better all upgrade to Internet 2. That beer Jamie made me try last night was pretty good. I forget what it was called. Phew. -- Nathan Ward

5 4

180/8 and 183/8 allocated to APNIC
by Leo Vegoda 30 Apr '09

30 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in April 2009: 180/8 and 183/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFJ+iBAvBLymJnAzRwRAq59AKDYIE9QGQAAJQDuqfQ5Qqo5YiZwWwCg1RNg wwnJkpL3STZw9fDOM7zUToM= =PtJl -----END PGP SIGNATURE-----

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Apr '09

30 Apr '09

The New Zealand Network Operators' Group The NZNOG mailing list exists to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. The NZNOG Trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. The Trust is not yet GST registered, but work is under way to bring that about. Conference In the NZNOG conference, the people are represented by two separate yet equally important groups. The trust, which is responsible for where the money goes, and the organising committee who do most of the actual work. See http://2009.nznog.org/ for details of this year's conference. Discussions are under way between the organising committee and potential hosts of the 2010 conference. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 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. About This Mailing List This list has around 1000 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 APN Online, Citylink, and The University of Waikato. 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 -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Two /8s allocated to APNIC from IANA (180/8, 183/8)
by Elly Tawhai 30 Apr '09

30 Apr '09

_______________________________________________________________________ Two /8s allocated to APNIC from IANA (180/8, 183/8) _______________________________________________________________________ Hi NZNOG Community, The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in April 2009 and will be making allocations from these ranges in the near future: 180/8 183/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

Re: [nznog] CallPlus Routing
by Stu Fleming 29 Apr '09

29 Apr '09

> > On 30/04/2009, at 12:17 AM, Bradley Scarisbrick wrote: >> > It appears fears of an outbreak were unfounded, CP NOC is alive and >> > well, >> > and with a top notch sense of humor for the late shift ... >> > > > Graveyard shift, perhaps When the WHO downgraded the Mexican flu death toll from 152 to 7 the other day, my first thought was a re-enactment of "From Dusk till Dawn"...145 zombies wandering around looking for networking jobs...

1 0

Re: [nznog] CallPlus Routing
by Stephen Barker 29 Apr '09

29 Apr '09

Will oinkment help? Sorry, I'll crawl back under my rock now. Steve > -----Original Message----- > From: Bradley Scarisbrick [mailto:bradleys(a)republic.net.nz] > Sent: Thursday, 30 April 2009 12:18 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: Re: [nznog] CallPlus Routing > > It appears fears of an outbreak were unfounded, CP NOC is > alive and well, > and with a top notch sense of humor for the late shift ... > > > On Wed, 29 Apr 2009 20:31:17 +1000, "Sean K. Finn" > <Sean.Finn(a)ozservers.com.au> wrote: > > Maybe the swine virus is really a Zombie virus in disguise. Uh oh. > > > > -----Original Message----- > > From: nznog-bounces(a)list.waikato.ac.nz > > [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Dean > Pemberton > > Sent: Wednesday, 29 April 2009 7:50 PM > > To: Bradley Scarisbrick > > Cc: NZNOG(a)list.waikato.ac.nz > > Subject: Re: [nznog] CallPlus Routing > > > > Zombie NOC...... Coooooool! > > > > =P > > Dean > > > > Bradley Scarisbrick wrote: > >> Could someone from CallPlus please contact me regarding an > issue with > >> routing to/from that network, CallPlus noc appears lifeless :) > >> > >> Thanks > >> --- > >> > >> Bradley Scarisbrick > >> > >> > >> _______________________________________________ > >> 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 > > -- > --- > > Bradley Scarisbrick > Creative ">P: +64 9 523 5620 > F: +64 9 523 5621 > M: +64 21 545 960 > W: http://www.republic.net.nz > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.12.3/2076 - Release > Date: 04/28/09 18:02:00 > >

1 0

CallPlus Routing
by Bradley Scarisbrick 29 Apr '09

29 Apr '09

Could someone from CallPlus please contact me regarding an issue with routing to/from that network, CallPlus noc appears lifeless :) Thanks --- Bradley Scarisbrick

5 5

NZRR Route Registry Update
by NZRR Database Notifications 28 Apr '09

28 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23958 descr: advertised to AS9560 by DTS Ltd - AS23958 members: 202.68.94.0/23^23-29, 202.174.178.0/23^23-29, 202.174.190.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070907 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23958 descr: advertised to AS9560 by DTS - AS23958 members: 210.48.160.0/20^20-29, 202.68.94.0/23^23-29, 202.20.6.0/24^24-29, 202.36.172.0/24^24-29, 202.68.82.128/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: technical(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090429 source: NZRR ------------------------------------------------------------

1 0

Domain Propagation
by Thomas Rowley 27 Apr '09

27 Apr '09

Lately I've had a lot of issues with domain nameserver changes taking *ages*to propagate in NZ. They seem to propogate really quickly everywhere else in the world from what i can tell. Do some NZ ISP's take longer to update their DNS records for some reason? Anyone else experienced this? Cheers Thomas

18 27

NZRR Route Registry Update
by NZRR Database Notifications 27 Apr '09

27 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-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.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.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.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.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, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.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, 202.124.106.0/23^23-29, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.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.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.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.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.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.106.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, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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 20081124 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ Ltd - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-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.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.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, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.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, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.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, 203.119.56.0/24^24-29, 203.171.223.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Apr '09

27 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-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.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.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.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 202.36.36.0/22^22-29, 202.37.48.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, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.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, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.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.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.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.106.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, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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 20081203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ LTD - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.154.128.0/19^19-29, 210.54.160.0/19^19-29, 114.134.160.0/20^20-29, 202.46.160.0/20^20-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 114.134.176.0/21^21-29, 116.90.128.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 123.108.144.0/21^21-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.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.152.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, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 210.4.208.0/21^21-29, 113.197.64.0/22^22-29, 202.36.36.0/22^22-29, 202.37.48.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, 202.89.4.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.6.116.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.204.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, 202.174.6.0/23^23-29, 203.84.134.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.107.113.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 198.32.66.0/24^24-29, 198.32.71.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.70.0/24^24-29, 202.12.91.0/24^24-29, 202.14.100.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.208.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.183.0/24^24-29, 202.36.218.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.37.205.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.118.0/24^24-29, 202.46.188.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.106.0/24^24-29, 202.49.144.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, 203.119.56.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090428 source: NZRR ------------------------------------------------------------

1 0

Website
by Richard Nelson 27 Apr '09

27 Apr '09

Who is maintaining the NZNOG website at the moment? I'm trying to find some slides that were presented at NZNOG'08 but the links to the slides archives now redirect to the NZNOG'09 page. I was wondering if those slide sets are still available? Thanks, Richard.

3 2

APNIC 28 fellowships - apply now
by Srinivas (Sunny) Chendi 25 Apr '09

25 Apr '09

________________________________________________________________________ The APNIC 28 fellowship program ________________________________________________________________________ Dear At APNIC, we understand that it may be difficult for our members from developing economies to attend APNIC meetings. In response, APNIC provides the fellowship awards to enable people from these developing economies to attend the APNIC meeting free of charge. As an APNIC fellow, you can: ---------------------------- - Acquire hands-on experience in IPv6 transition and deployment strategies - Attend all workshops and tutorials at APNIC 28 - Participate in policy discussions that will affect how your organization accesses Internet number resources - Meet a wide range of people in the Internet industry from around the world For more information about the fellowship award packages, selection process, and submitting an application, please visit our website: http://meetings.apnic.net/28/fellowship Deadline -------- The deadline for submissions is Thursday, 21 May 2009. Sincerely, ________________________________________________________________________ Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3189 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

Telstra IP: 218.101.59.4
by Simon Lyall 23 Apr '09

23 Apr '09

Could whoever is in charge of this Proxy/Spider/whatever please contact me ASAP. I've blocked you for now after I unsuccessfully tried to contact you yesterday and had problems again today. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 1

Two blocks of AS Numbers allocated
by Leo Vegoda 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of two blocks of AS Numbers recently. 53248-54271 Assigned by ARIN whois.arin.net 2009-04-21 54272-55295 Assigned by ARIN whois.arin.net 2009-04-21 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFJ78q5vBLymJnAzRwRAsxhAKCvxeFIPNw/gZnUDnH0Q51wWR7fiACeMKe+ XnUY36jXeaFRj2Ecn+4ZgFE= =cnqY -----END PGP SIGNATURE-----

1 0

What happens when someone attacks your fibre networks?
by Matthew Poole 22 Apr '09

22 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://perens.com/works/articles/MorganHill/ "The city of Morgan Hill and parts of three counties lost 911 service, cellular mobile telephone communications, land-line telephone, DSL internet and private networks, central station fire and burglar alarms, ATMs, credit card terminals, and monitoring of critical utilities. In addition, resources that should not have failed, like the local hospital's internal computer network, proved to be dependent on external resources, leaving the hospital with a "paper system" for the day." (continues in the article). To summarise, it's all very well having redundant systems but if someone takes to the telco infrastructure you still need something that's entirely distinct. Otherwise you end up in a wee bit of a pickle. It's a good case, as if further ones were needed, against BPL. If the power's up but the telco networks are down, interference with ham radio is a "bad thing"[tm]. - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ78f8TdEtTmUCdpwRAtuHAJ9ytrxlD9yY7sTN1ScPldX5qo4ynwCeK4YM HHa8f1TryqH5jpfTbspTXfM= =QKQe -----END PGP SIGNATURE-----

2 1

skype
by James Jones 21 Apr '09

21 Apr '09

http://i.gizmodo.com/5221522/skype-offering-country-unlimited-plan-for-6mon… holy crap NZ is included. do they have a local MGW in NZ? James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Update on Domainz SQL injection attack--- is it fixed yet?
by Robert Cotter 21 Apr '09

21 Apr '09

And have they rolled back the hacks??? Regards Robert Cotter Sales Engineer rcotter(a)distributioncentral.co.nz<mailto:rcotter(a)distributioncentral.co.nz> Distribution Central NZ Unit 2, Level 1, 194 Victoria Street West, Auckland 1001, New Zealand. Mb 64 21 675550, T 64 9 309 8277, F 64 9 309 8276 www.distributioncentral.co.nz<http://www.distributioncentral.co.nz/> Distributor of : Accellion, Acronis, Aruba, Bluecoat, Boll Engineering, Crossbeam, F5, Force10, Fortinet, Infoblox, Netxen, Riverbed, TippingPoint, Xsigo . Vendor product link => www.distributioncentral.co.nz/Section.asp?section=9 This email is for the intended recipient(s) only, Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 9425 5000 or notify sender.

1 0

msn.co.nz
by Michael Jager 20 Apr '09

20 Apr '09

So, I wouldn't normally make a post like this, but I figure one or two people might notice this at some point in the next day or so: mj(a)coalface:~$ whois msn.co.nz | egrep ^ns_name ns_name_01: fatih1.turkguvenligi.info ns_name_02: fatih2.turkguvenligi.info mj(a)coalface:~$ whois msn.co.nz | egrep ^domain_datelastmodified domain_datelastmodified: 2009-04-21T09:44:21+12:00 From my resolver's cache: ;; ANSWER SECTION: msn.co.nz. 3282 IN A 202.58.48.29 ;; AUTHORITY SECTION: msn.co.nz. 20363 IN NS ns4.msft.net. msn.co.nz. 20363 IN NS ns5.msft.net. msn.co.nz. 20363 IN NS ns1.msft.net. msn.co.nz. 20363 IN NS ns2.msft.net. msn.co.nz. 20363 IN NS ns3.msft.net. ;; ADDITIONAL SECTION: ns1.msft.net. 1571 IN A 207.68.160.190 ns2.msft.net. 1593 IN A 65.54.240.126 ns3.msft.net. 18367 IN A 213.199.161.77 ns4.msft.net. 18367 IN A 207.46.66.126 ns5.msft.net. 1302 IN A 65.55.238.126 From the new NS: ;; ANSWER SECTION: msn.co.nz. 14400 IN A 95.211.11.163 ;; AUTHORITY SECTION: msn.co.nz. 86400 IN NS fatih1.turkguvenligi.info. msn.co.nz. 86400 IN NS fatih2.turkguvenligi.info. ;; ADDITIONAL SECTION: fatih1.turkguvenligi.info. 14400 IN A 95.211.11.163 fatih2.turkguvenligi.info. 14400 IN A 95.211.11.163 It's not still April Fools, is it? -Mike

5 4

NZRR Route Registry Update
by NZRR Database Notifications 20 Apr '09

20 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CALLPLUS - AS9790 members: 119.224.0.0/17^17-29, 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 119.224.128.0/20^20-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080304 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus - AS9790 members: 119.224.0.0/17^17-29, 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 119.224.128.0/20^20-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 202.37.22.0/24^24-29, 202.37.75.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: networksnoc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090421 source: NZRR ------------------------------------------------------------

1 0

NAND
by James Jones 19 Apr '09

19 Apr '09

is there any nand experts on here? I just was just wondering why none of the moblie phone providers have but local numbers on a cell like we do in the states. I was just wondering not very familiar with NAND stuff here in NZ. James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

7 6

Vector fibre in Auckland CBD
by Skip Parker 16 Apr '09

16 Apr '09

Morning, Anyone else seeing issues with vector fibre in the cbd today? It seems to coincide with a failure at the Vector switchboard as well... So information seems scarce. Skip Parker Rhema Broadcasting Group On 4/2/09, matthew(a)auscert.org.au <matthew(a)auscert.org.au> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > G'day all, > > We are seeing a decent trojan spam out using Facebook as the hook. The > emails all differ slightly but possess the same characteristics. Eg: > > From: "Facebook presentment" <support60(a)facebook.com> > Subject: Facebook announcement: Great looking girl having fun (Last rated > by Bradford Collins) > > Messages from Your Friends on Facebook, April 01, 2009 > > You have 1 friend requests - Personal Message: > Watch the video titled "Drunk Charlize is dancing striptease on my > Birthday Party, March 28, 2009! We're absolutely shocked!". > > Proceed to view full message: > > hxxp://facebook.shared.id-etsmrnhy5e.subject.876panel. > com/home.htm?/identification/authentication=0616n9m12 > > Added 16 minutes ago. Message ID: FB-06nnzbrxizjrzvr > 2009 Facebook community, Message Center. > > Multiple domains are being used all following a naming scheme of > > [3-5 digit number]panel.com > > Eg: > > 2349panel. com > 43553panel. com > 654panel. com > 876panel. com > 987panel. com > > Is anyone else seeing a decent run of this? > > Just trying to work out how widespread it is as we are preparing to do an > alert on it. > > Apologies if you see this across a few lists - looking for any feedback > on numbers on this (and it is all appreciated). > > Best regards, > > - -- Matthew McGlashan -- > Coordination Centre Team Leader | Hotline: +61 7 3365 4417 > Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 > (AusCERT) | Fax: +61 7 3365 7031 > The University of Queensland | WWW: www.auscert.org.au > Qld 4072 Australia | Email: auscert(a)auscert.org.au > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (FreeBSD) > Comment: http://www.auscert.org.au/render.html?it=1967 > Comment: http://www.auscert.org.au/render.html?it=1967 > > iD8DBQFJ1BXZNVH5XJJInbgRAvMqAJ0cqNWqI3riSyf5Tq9lGzxO9C6xegCcCpl0 > KzfS5kwPQpBMNU4TfhQuqDo= > =zKz3 > -----END PGP SIGNATURE----- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > -- Sent from my mobile device Skip Parker m. 021 793 824 e. skip(a)ignition.net.nz

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '09

14 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Apr '09

14 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090415 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Apr '09

08 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 115.187.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.36.204.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.103.0/24^24-29, 203.18.187.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.25.165.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.29.0.0/24^24-29, 203.29.45.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.61.0/24^24-29, 203.32.82.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.18.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.131.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.56.234.0/24^24-29, 203.57.93.0/24^24-29, 203.145.60.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.171.208.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.8.113.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.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: macca(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 118.92.0.0/15^15-29, 121.90.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 114.129.128.0/18^18-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 58.96.128.0/19^19-29, 115.69.160.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.142.160.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.90.128.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 121.200.32.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 124.155.224.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 122.201.72.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.36.16.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 202.169.176.0/21^21-29, 203.82.208.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.44.24.0/22^22-29, 110.50.16.0/22^22-29, 110.76.132.0/22^22-29, 110.78.128.0/22^22-29, 112.140.176.0/22^22-29, 113.29.240.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 114.141.104.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.86.208.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.153.64.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.4.208.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.170.0/23^23-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 110.50.20.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 114.141.108.0/23^23-29, 115.178.6.0/23^23-29, 118.107.60.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 123.255.222.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.21.136.0/23^23-29, 202.49.148.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.56.14.0/23^23-29, 203.57.0.0/23^23-29, 203.57.78.0/23^23-29, 203.62.210.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.111.104.0/23^23-29, 203.145.62.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.167.254.0/23^23-29, 203.185.194.0/23^23-29, 203.190.222.0/23^23-29, 206.222.230.0/23^23-29, 210.4.214.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 218.100.52.0/23^23-29, 220.233.4.0/23^23-29, 58.87.6.0/24^24-29, 58.96.0.0/24^24-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 59.154.62.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 114.111.142.0/24^24-29, 115.42.20.0/24^24-29, 116.50.58.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.1.0/24^24-29, 122.252.4.0/24^24-29, 122.252.7.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.190.108.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.173.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.71.0/24^24-29, 202.49.106.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 202.50.247.0/24^24-29, 202.50.252.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.158.253.0/24^24-29, 202.160.50.0/24^24-29, 202.160.126.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.1.88.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.5.127.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.15.243.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.187.0/24^24-29, 203.18.197.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.79.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090409 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Apr '09

07 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS38477 descr: advertised to AS9560 by Unleash - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29, 192.88.99.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: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080901 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38477 descr: advertised to AS9560 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Apr '09

07 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: paul.joslin(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 06 Apr '09

06 Apr '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS38477 descr: Route set advertised to AS24388 by Unleash Computers - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29, 192.88.99.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: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081114 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090407 source: NZRR ------------------------------------------------------------

1 0

Trojan spam run with Facebook hook (AUSCERT#2009abf45)
by matthew＠auscert.org.au 01 Apr '09

01 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day all, We are seeing a decent trojan spam out using Facebook as the hook. The emails all differ slightly but possess the same characteristics. Eg: From: "Facebook presentment" <support60(a)facebook.com> Subject: Facebook announcement: Great looking girl having fun (Last rated by Bradford Collins) Messages from Your Friends on Facebook, April 01, 2009 You have 1 friend requests - Personal Message: Watch the video titled "Drunk Charlize is dancing striptease on my Birthday Party, March 28, 2009! We're absolutely shocked!". Proceed to view full message: hxxp://facebook.shared.id-etsmrnhy5e.subject.876panel. com/home.htm?/identification/authentication=0616n9m12 Added 16 minutes ago. Message ID: FB-06nnzbrxizjrzvr 2009 Facebook community, Message Center. Multiple domains are being used all following a naming scheme of [3-5 digit number]panel.com Eg: 2349panel. com 43553panel. com 654panel. com 876panel. com 987panel. com Is anyone else seeing a decent run of this? Just trying to work out how widespread it is as we are preparing to do an alert on it. Apologies if you see this across a few lists - looking for any feedback on numbers on this (and it is all appreciated). Best regards, - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iD8DBQFJ1BXZNVH5XJJInbgRAvMqAJ0cqNWqI3riSyf5Tq9lGzxO9C6xegCcCpl0 KzfS5kwPQpBMNU4TfhQuqDo= =zKz3 -----END PGP SIGNATURE-----

1 0

Fwd: RFC 5514 on IPv6 over Social Networks
by Nathan Ward 01 Apr '09

01 Apr '09

I got this email at 5:25AM today, which is 6:25PM April 1 in Belgium where Eric lives. I guess the joke is on him? It is only 9:25AM PDT though so the RFC editor is in the clear. Anyway, enjoy: Begin forwarded message: > From: rfc-editor(a)rfc-editor.org > Date: 2 April 2009 5:25:42 AM > To: ietf-announce(a)ietf.org, rfc-dist(a)rfc-editor.org > Cc: rfc-editor(a)rfc-editor.org > Subject: RFC 5514 on IPv6 over Social Networks > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5514 > > Title: IPv6 over Social Networks > Author: E. Vyncke > Status: Experimental > Date: 1 April 2009 > Mailbox: evyncke(a)cisco.com > Pages: 6 > Characters: 10127 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-vyncke-ip-over-social-network-01.txt > > URL: http://www.rfc-editor.org/rfc/rfc5514.txt > > > There is a lack of IPv6 utilization in early 2009; this is partly > linked to the fact that the number of IPv6 nodes is rather low. This > document proposes to vastly increase the number of IPv6 hosts by > transforming all Social Networking platforms into IPv6 networks. > This will immediately add millions of IPv6 hosts to the existing IPv6 > Internet. This document includes sections on addressing and > transport of IPv6 over a Social Network. A working prototype has > been developed. This memo defines an Experimental Protocol for the > Internet community. > > EXPERIMENTAL: This memo defines an Experimental Protocol for the > Internet community. It does not specify an Internet standard of any > kind. Discussion and suggestions for improvement are requested. > Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html > . > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor(a)rfc-editor.org. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > USC/Information Sciences Institute -- Nathan Ward

4 4

NZNOG NOC list
by Gerard Creamer 31 Mar '09

31 Mar '09

Hi, Something broke on the NZNOG website when we moved servers and a bunch of NOC list changes were lost. I have reentered as many as I have been able to find based on emails but would appreciate it if you could all check your entries. http://www.nznog.org/?page_id=6 If there is a problem with your entry please email abuse and amendments to info (at) nznog.org and I'll get onto fixing them up. If there are no problems with your entry please keep your abuse and general mutterings about competence to yourself :^) Cheers, Gerard

2 1

The New Zealand Network Operators' Group
by Donald Neal 31 Mar '09

31 Mar '09

The New Zealand Network Operators' Group Work is now nearing completion to establish the NZNOG Trust. The Trust is being set up to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. NZNOG is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference See http://2009.nznog.org/ for details of this year's conference. The plan is that next year's conference will be further south than Auckland. Discussions are now being held with prospective hosts, so if you have a burning desire to host New Zealand's only technical networking conference, now would be the time to speak up. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 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. About This Mailing List This list has around 1000 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 APN Online, Citylink, and The University of Waikato. 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 -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

QoS-IXPs
by Brian E Carpenter 30 Mar '09

30 Mar '09

On behalf of Thomas Knoll: ---------- Forwarded message ---------- Date: Wed, 25 Mar 2009 02:02:42 +0100 (MET) From: Thomas M. Knoll <knoll(a)etit.tu-chemnitz.de> To: nznog(a)list.waikato.ac.nz Subject: QoS-IXPs Dear Sirs, excuse me please for bothering you with the following information, but I thought it could be of use for you as well. Background: I am currently proposing a class of service signalling extension to BGP in order to enhance the current best effort AS interconnection into a simple class-based interconnection. This primitive traffic separation scheme also encompasses lower layer QoS schemes in a consistent manner, which makes it attractive for QoS interested peering partners to meet on peering platforms with Ethernet QoS support. Therefore, I am trying to find out about Internet exchange points, which would a least transparently (untouched) transfer user priority bits across their platform and might even have 802.1p enqueueing and scheduling enabled on their switches. Having said that, I will point you to the current QoS capable IXP list on the web. http://www.bgp-qos.org/qos-ixp/ Furthermore, if you are interested to be recognized by QoS interested peering partners as potential peering platform, I would cordially invite you to register there as well. http://www.bgp-qos.org/qos-ixp/add.php Thank you in advance, Thomas Knoll

23 38

UPDATED CCIP ALERT: Conficker worm
by Paul McKitrick 29 Mar '09

29 Mar '09

Good Evening, CCIP issued an alert on 8/01/2009 about the Conficker worm which attempts to exploit a previously patched stack buffer overflow vulnerability in Microsoft Windows Server Service (MS08-067). CCIP is issuing this update notice to warn organisations of this activity and to prevent further compromises from occurring. The latest variants of the Conficker worm include updates to its ability to communicate to itself and these changes are scheduled to activate on 1 April 2009, it is unknown what will happen on 1 April 2009. CCIP has been working with organisations nationally and with the international Conficker Working Group on this situation and would appreciate being informed of any outbreaks of Conficker or incidents relating to Conficker via incidents(a)ccip.govt.nz as this will assist in CCIP¹s ability to determine the impact of Conficker on New Zealand's networks and to coordinate any responses or flows of information. Further information about Conficker, including how to detect and remove it can be found on the Conficker Working Group website: http://www.confickerworkinggroup.org/wiki/pmwiki.php?n=ANY.GeneralAssistance Further infromation about MS08-067 can be found on Microsofts website: http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx Regards, Paul. -- Paul McKitrick Head of Stakeholder Engagement Centre for Critical Infrastructure Protection D: (+64) 4 498 7645 P: (+64) 4 498 7654 F: (+64) 4 498 7655 E: paul.mckitrick(a)ccip.govt.nz W: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.170.56.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.johnson(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by bcl-nz - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/18^18-29, 58.84.224.0/20^20-29, 114.134.0.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 116.90.128.0/21^21-29, 117.104.176.0/21^21-29, 123.108.144.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.6.116.0/23^23-29, 202.27.88.0/23^23-29, 202.49.164.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.34.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.29.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.168.0/24^24-29, 202.49.183.0/24^24-29, 202.129.253.0/24^24-29, 203.30.174.0/24^24-29, 203.92.25.0/24^24-29, 203.170.56.0/24^24-29, 203.171.4.0/24^24-29, 203.174.26.0/24^24-29, 203.97.62.200/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: philip.tan(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081222 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 26 Mar '09

26 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090327 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 26 Mar '09

26 Mar '09

Thanks for everyone's quick replies. The trick with the 877 was to add "ip tcp adjust-mss 1400" onto the LAN interface and everything started working just like it should. Does anyone have any thoughts about the appropriate segment size to use for traffic in NZ that goes over DSL like this? Thanks again, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

5 4

Linksys + Netgear Worm
by Philip D'Ath 25 Mar '09

25 Mar '09

Oh joy, a worm is now out that infects Linksys and NetGear DSL routers. http://blogs.zdnet.com/BTL/?p=15197 'Psyb0t' worm infects Linksys, Netgear home routers, modems More information has surfaced about the botnet “psyb0t,” the first known to be capable of directly infecting home routers and cable/DSL modems. It was first observed infecting a Netcomm NB5 modem/router in Australia. Members of the website DroneBL, a real-time IP tracker that scans for and botnets and vulnerable machines, came to the conclusion that the “psyb0t” (or “Network Bluepill”) botnet was a test run to prove the technology. After the botnet’s discovery and public outing, the botnet operator swiftly shut it down, APC reports. [Read more: Stealthy router-based botnet worm squirming] However, the most recently discovered generation (dubbed ‘version 18′ in the code) targets a wide range of devices, and contains the shellcode for over 30 different Linksys models, 10 Netgear models, and 15 other models of cable and DSL modems, APC reports. It did not specify which models. APC: A list of 6000 usernames and 13,000 passwords were also included, to be used for brute force entry to Telnet and SSH logins which are open to the LAN and sometimes even the public WAN side of the routers. Generally, routers do not lock a user out after a number of incorrect password attempts, making brute force attacks possible. According to DroneBL, any router that uses a MIPS processor and runs the Linux Mipsel operating system (a simple operating system for MIPS Processors) is vulnerable if they have the router administration interface, or sshd/telnetd in a DMZ, with weak username/passwords. DroneBL noted this includes devices flashed with the open-source firmwares openwrt and dd-wrt, and the group also said that other routers may be vulnerable, as it had observed the bot running on routers based on the Vxworks operating system. Clearly, exploiting a home network ? which are growing in popularity ? has its benefits: they rarely power down, and a router attack enables hackers to exploit a network with greater levels of stealth, since there’s no affect on individual PCs on the network, APC writes. In fact, the staff of DroneBL wrote that the exploit is very difficult to detect, and the only way to discover it is to monitor traffic going in and out of the router itself ?beyond the reach of desktop computer software. In the past, exploits on professional-grade Cisco routers were easier to detect, as Cisco provides dedicated ports for connecting to the router, monitoring internal performance and configuring them. However, the vast majority of home routers sacrifice these features for the sake of cost savings. DroneBL says that the botnet is capable of scanning for vulnerable PHPMyAdmin and MySQL installations, and can also disable access to the control interfaces of a router, (meaning a factory reset is necessary to clear the worm). DroneBL was successful in shutting down the Command & Control channel that the botnet utilized, and the DNS that was hosted with afraid.org was also nullrouted. The Command & Control channel is now defunct, but at the height of its penetration, the botnet was suspected to control 100,000 hosts. Worse, the author of the botnet claimed to have infected 80,000 routers at one point while chatting anonymously on an IRC channel. WHAT DEVICES ARE AFFECTED According to Drone BL: We don’t know. There are so many devices out there that we could not possibly know. Your best bet would be to take action to upgrade the device firmware and secure any passwords if there is concern that the device may be vulnerable. Such actions will help to avoid exploitation by the worm. WHAT TO DO According to DroneBL: Ports 22, 23 and 80 are blocked as part of the infection process (but NOT as part of the rootkit itself, running the rootkit itself will not alter your iptables configuration). If these ports are blocked, you should perform a hard reset on your device, change the administrative passwords, and update to the latest firmware. These steps will remove the rootkit and ensure that your device is not reinfected.

3 2

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Martin Wilkinson 25 Mar '09

25 Mar '09

Have you tried to manually lock down the dsl operating mode? I.e don't let it autodetect Int atm0 Dsl operating-mode itu ________________________________ From: Terry Wilson <terry(a)pds-dn.co.nz> To: nznog(a)list.waikato.ac.nz <nznog(a)list.waikato.ac.nz> Sent: Thu Mar 26 09:55:05 2009 Subject: Re: [nznog] VF / Ihug issues with Cisco ADSL Routers Problem doesn’t go away if I shutdown and bring up interfaces. Not sure if its ADSL2+ related for us as the 827/837s that have shown this behaviour aren’t ADSL2 capable. Virtual interface comes up ok and I can ping the outside world no problem, can connect in via VPN and incoming email works ok (as long as it doesn’t time out) and web works occasionally. I have also tried with the newer adsl firmware from ftp://ftp.cisco.com/pub/access/800 with no success. ________________________________ This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal ________________________________

1 0

Re: [nznog] VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 25 Mar '09

25 Mar '09

Problem doesn't go away if I shutdown and bring up interfaces. Not sure if its ADSL2+ related for us as the 827/837s that have shown this behaviour aren't ADSL2 capable. Virtual interface comes up ok and I can ping the outside world no problem, can connect in via VPN and incoming email works ok (as long as it doesn't time out) and web works occasionally. I have also tried with the newer adsl firmware from ftp://ftp.cisco.com/pub/access/800 with no success. ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

VF / Ihug issues with Cisco ADSL Routers
by Terry Wilson 25 Mar '09

25 Mar '09

Have a lot of sites with 877 / 827 / 837 ADSL routers on ADSL connections, basic configs are all pretty much the same. On Monday last week we started experiencing issues with customers that are on Ihug ADSL accounts. HTTP traffic loads intermittently, incoming SMTP is very slow (100b/sec), pings and VPN appear to work ok. Have tried basic configs and have tested routers ok in our office (through Xtra ADSL line) and they work fine, have tested different Cisco routers with the same results. If however I use a telecom supplied Dlink or a Linksys all in one it all works fine. I have a fault logged with Vodafone but all I'm getting back is that its a Cisco problem. I am going to log a TAC call this morning but I thought I would find out if anyone else has struck this. Thanks, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

VoIP Conference
by James Jones 24 Mar '09

24 Mar '09

Would anyone here be intrested in attending a conference similar to Astricon or ClueCon here in New Zealand? -- James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

11 14

Section 92A to be scrapped
by Jean-Francois Pirus 23 Mar '09

23 Mar '09

FYI: http://www.nbr.co.nz/article/section-92a-be-scrapped-89121 -- ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Technical Manager Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 1st Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

1 0

TCP Well Known Ports SQL File
by Dan Clark 19 Mar '09

19 Mar '09

Gidday, just before I go and re-invent the wheel, does anyone happen to have an up to date SQL dump of TCP Well known ports c/o iana. Cheers Dan Clark

2 2

NZRR Route Registry Update
by NZRR Database Notifications 18 Mar '09

18 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 18 Mar '09

18 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090319 source: NZRR ------------------------------------------------------------

1 0

Sounce of non-peering ranges or paths
by Simon Lyall 18 Mar '09

18 Mar '09

Just wondering what the easiest way is to get a list of NZ IPs ranges that are not peered at APE or WIX? (and maybe other NZIX pops). Need it to be over 90% accurate and easy to recheck every once in a while. Or is it easier to go the other way and start with a list of NZ IPs (from ?) and subtract what is being peered? I promise I won't use this list to target banner ads for other ISPs :) -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 3

Re: [nznog] Sounce of non-peering ranges or paths
by Erin Salmon 18 Mar '09

18 Mar '09

Strictly speaking I believe that's possible, but I'm reasonably sure that if you get a domestic table from one, they includes each other's customer routes. To be sure of course, you could just use both. Erin Salmon Managing Director - Unleash Phone: 03 365 1273 Mobile: 0275 877 913 From: Dan Clark [mailto:danclarknz(a)gmail.com] Sent: 19 March 2009 11:04 a.m. To: Erin Salmon Subject: Re: [nznog] Sounce of non-peering ranges or paths networks could be connected to Telstra and not connected to Telecom? Regards Dan On Thu, Mar 19, 2009 at 10:02 AM, Erin Salmon <erin(a)unleash.co.nz> wrote: Take the APE/WIX lists and subtract the Telecom domestic list? You'll need to be peered* with all the relevant parties of course. *Ahem, or paying for transit. Erin Salmon Managing Director - Unleash Phone: 03 365 1273 Mobile: 0275 877 913 -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: 19 March 2009 11:00 a.m. To: nznog Subject: [nznog] Sounce of non-peering ranges or paths Just wondering what the easiest way is to get a list of NZ IPs ranges that are not peered at APE or WIX? (and maybe other NZIX pops). Need it to be over 90% accurate and easy to recheck every once in a while. Or is it easier to go the other way and start with a list of NZ IPs (from ?) and subtract what is being peered? I promise I won't use this list to target banner ads for other ISPs :) -- Simon 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 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Broadband needed
by Richard Naylor 18 Mar '09

18 Mar '09

Anyone have any capacity (of a few Mbps) in Te Kuiti for 3 days ? If so we have money and beer...... Richard

1 0

Re: [nznog] NZNOG & Discussion Topics (Mark Foster)
by Anton Smith 17 Mar '09

17 Mar '09

> ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 Mar 2009 16:46:39 +1200 (NZST) > From: "Mark Foster" <blakjak(a)blakjak.net> > Subject: Re: [nznog] NZNOG & Discussion Topics > To: "NZNOG List" <nznog(a)list.waikato.ac.nz> > Message-ID: > <58919.119.15.0.26.1237178799.squirrel(a)webmail.blakjak.net> > Content-Type: text/plain;charset=iso-8859-1 > > > On Sat, March 14, 2009 8:44 am, Andy Linton wrote: >> >> On 13/03/2009, at 16:31 , Leo Vegoda wrote: >> >>> In that spirit I'll repeat my suggestion for the update messages to >>> include >>> diffs. >>> >>> I don't know what software is being run but if it's the RIPE database >>> software then the update processor can be told to produce diffs in the >>> notification messages it sends. If it's a different database then >>> I'm fairly >>> sure it's quite easy to plug in. I just know that knowing what the >>> change is >>> is probably a dead useful feature. >>> >>> http://www.ripe.net/db/news/update-changes-200410.html >> >> The back end is IRRD. The NZRR requirements are simple and running the >> RIPE code simply got too hard. >> >> A good suggestion about the diffs and I know it's been asked for >> before. CityLink and I are planning to do some updates/changes to the >> software soon so that people can submit diffs as well as get them in >> the output etc. >> >> If you have any burning requirements let me know and I'll feed it into >> the mix. Joe's idea of a separate list has some merit - again let me >> know directly and I'll come back to the list with results. >> > > NZNOG in the great scheme of things doesn't seem to be so busy that the > NZRR notifications nor discussion on 'related' topics are that big a deal > from where I sit. > > I don't read the NZRR notifications often as they don't relate directly to > my day-to-day work but i glance at them occaisionally as they help me keep > tabs on 'what's going on' out there. Were they bounced to some other > mailing list, I probably wouldn't read them at all as I don't need to see > them so wouldn't 'opt-in'. > > Suggest the same applies to any sort of 'off topic' mailing list that > diverges from NZNOG itself. The value of the list is diluted when less > people are subscribed; the value of NZNOG is among other things, the > knowledge that clooful, relevant people are likely to be reading it. > Who's to say that theyre going to subscribe to another mailing list where > the SNR is likely worse? > > I like relevant subject lines... it's pretty easy to ignore / postpone for > later / delete threads that you're genuinely not interested in, and I > havn't yet seen the volume of traffic on NZNOG suggest an alternative > means is required. At the same time, i'm not sure that a 'chat' list > would draw in the same crowd necessarily. > > (Anyone remember NZNET? Fizzled. Remember?) > > Mark. IMHO. > I don't have any problems with the amount of traffic - the discussion about laws that will affect operations are relevant imho. That and it is nice to see activity and discussion on the list in general. Unfortunately it seems we have a lengthy discussion about "relevancy" almost every time there is something that only a few object to. Regards, Anton

2 1

NZNOG & Discussion Topics
by Jonathan Brewer 15 Mar '09

15 Mar '09

Hi Folks, For the health and happiness of users of this list, could we perhaps keep discussions to OSI Layer 5-1? If I'm way off-base in asking this, someone please throw a beer at me. Cheers, Jon

18 22

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 202.55.96.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090212 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: paul.joslin(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.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.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.129.253.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Mar '09

12 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus - AS4826 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 115.187.128.0/17^17-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.161.64.0/19^19-29, 120.88.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.32.0/19^19-29, 124.6.192.0/19^19-29, 125.213.160.0/19^19-29, 202.14.32.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 202.182.96.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.145.32.0/19^19-29, 203.201.128.0/19^19-29, 210.56.224.0/19^19-29, 113.20.0.0/20^20-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 114.141.96.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 117.55.224.0/20^20-29, 119.15.96.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 174.128.16.0/20^20-29, 202.3.96.0/20^20-29, 202.4.224.0/20^20-29, 202.53.176.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.88.112.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.90.128.0/21^21-29, 116.193.176.0/21^21-29, 116.212.64.0/21^21-29, 119.31.232.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 121.0.0.0/21^21-29, 123.108.144.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 192.173.16.0/21^21-29, 202.36.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.78.240.0/21^21-29, 202.92.240.0/21^21-29, 202.146.208.0/21^21-29, 202.160.112.0/21^21-29, 203.160.8.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 122.100.0.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 125.254.112.0/22^22-29, 140.200.248.0/22^22-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.50.188.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.33.116.0/22^22-29, 203.62.184.0/22^22-29, 203.79.16.0/22^22-29, 203.92.28.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 59.86.160.0/23^23-29, 63.218.156.0/23^23-29, 74.80.126.0/23^23-29, 114.111.132.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.160.230.0/23^23-29, 122.100.6.0/23^23-29, 122.100.8.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.6.42.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.36.204.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.92.94.0/23^23-29, 202.93.4.0/23^23-29, 202.124.106.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.172.156.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.18.102.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.90.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.79.88.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.147.108.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.9.230.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 97.64.46.0/24^24-29, 113.212.98.0/24^24-29, 114.111.128.0/24^24-29, 116.50.58.0/24^24-29, 122.100.15.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.100.53.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.174.0/24^24-29, 202.36.218.0/24^24-29, 202.37.93.0/24^24-29, 202.37.136.0/24^24-29, 202.37.168.0/24^24-29, 202.37.182.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.190.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.106.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.122.132.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.4.154.0/24^24-29, 203.5.45.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.16.243.0/24^24-29, 203.17.4.0/24^24-29, 203.17.68.0/24^24-29, 203.17.95.0/24^24-29, 203.17.183.0/24^24-29, 203.18.94.0/24^24-29, 203.18.136.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.26.204.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.28.14.0/24^24-29, 203.29.0.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.82.0/24^24-29, 203.33.70.0/24^24-29, 203.33.113.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.139.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.57.93.0/24^24-29, 203.63.3.0/24^24-29, 203.63.67.0/24^24-29, 203.79.20.0/24^24-29, 203.92.25.0/24^24-29, 203.96.157.0/24^24-29, 203.98.81.0/24^24-29, 203.111.63.0/24^24-29, 203.111.105.0/24^24-29, 203.119.56.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.166.89.0/24^24-29, 203.171.4.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 205.233.128.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.55.110.0/24^24-29, 210.56.153.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20090114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Connect Pty Ltd - AS4826 members: 115.187.128.0/17^17-29, 118.127.0.0/18^18-29, 125.253.0.0/18^18-29, 203.114.128.0/18^18-29, 58.96.128.0/19^19-29, 114.129.128.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 121.79.192.0/19^19-29, 122.129.128.0/19^19-29, 123.100.128.0/19^19-29, 125.213.160.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.154.128.0/19^19-29, 202.171.160.0/19^19-29, 203.89.64.0/19^19-29, 203.201.128.0/19^19-29, 113.192.0.0/20^20-29, 114.31.192.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 116.213.32.0/20^20-29, 119.161.64.0/20^20-29, 122.201.80.0/20^20-29, 123.50.128.0/20^20-29, 125.253.96.0/20^20-29, 125.254.64.0/20^20-29, 202.53.176.0/20^20-29, 202.78.32.0/20^20-29, 202.93.160.0/20^20-29, 202.144.160.0/20^20-29, 202.153.64.0/20^20-29, 202.191.32.0/20^20-29, 203.83.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 210.48.160.0/20^20-29, 210.56.224.0/20^20-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 115.124.32.0/21^21-29, 115.178.16.0/21^21-29, 116.212.64.0/21^21-29, 119.63.216.0/21^21-29, 119.160.232.0/21^21-29, 120.89.80.0/21^21-29, 121.101.136.0/21^21-29, 125.214.64.0/21^21-29, 125.254.88.0/21^21-29, 166.65.184.0/21^21-29, 202.4.232.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.149.80.0/21^21-29, 203.161.136.0/21^21-29, 203.169.16.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.9.136.0/21^21-29, 210.56.248.0/21^21-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 113.29.240.0/22^22-29, 113.197.64.0/22^22-29, 114.111.132.0/22^22-29, 119.160.228.0/22^22-29, 119.252.176.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 124.108.96.0/22^22-29, 125.214.72.0/22^22-29, 125.254.80.0/22^22-29, 125.254.100.0/22^22-29, 202.4.228.0/22^22-29, 202.37.48.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.93.176.0/22^22-29, 202.93.184.0/22^22-29, 202.129.244.0/22^22-29, 202.169.20.0/22^22-29, 202.177.220.0/22^22-29, 203.11.104.0/22^22-29, 203.12.48.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.62.184.0/22^22-29, 203.92.28.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.128.0/22^22-29, 203.161.160.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.190.232.0/22^22-29, 203.209.192.0/22^22-29, 203.211.56.0/22^22-29, 210.11.144.0/22^22-29, 210.56.244.0/22^22-29, 59.86.186.0/23^23-29, 63.218.156.0/23^23-29, 114.111.130.0/23^23-29, 114.111.138.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 119.15.98.0/23^23-29, 119.31.248.0/23^23-29, 119.160.224.0/23^23-29, 119.161.80.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.200.58.0/23^23-29, 122.201.64.0/23^23-29, 125.254.84.0/23^23-29, 125.254.96.0/23^23-29, 125.254.104.0/23^23-29, 202.3.104.0/23^23-29, 202.6.116.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.138.0/23^23-29, 202.36.204.0/23^23-29, 202.87.30.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.93.188.0/23^23-29, 202.150.60.0/23^23-29, 202.160.48.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.181.28.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.16.60.0/23^23-29, 203.22.70.0/23^23-29, 203.22.224.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.33.60.0/23^23-29, 203.33.228.0/23^23-29, 203.34.8.0/23^23-29, 203.34.122.0/23^23-29, 203.55.174.0/23^23-29, 203.62.210.0/23^23-29, 203.82.216.0/23^23-29, 203.84.134.0/23^23-29, 203.84.216.0/23^23-29, 203.98.64.0/23^23-29, 203.98.76.0/23^23-29, 203.99.146.0/23^23-29, 203.145.62.0/23^23-29, 203.161.134.0/23^23-29, 203.161.158.0/23^23-29, 203.185.194.0/23^23-29, 206.222.230.0/23^23-29, 210.8.34.0/23^23-29, 210.9.230.0/23^23-29, 210.56.240.0/23^23-29, 210.87.34.0/23^23-29, 58.181.65.0/24^24-29, 59.86.185.0/24^24-29, 59.86.189.0/24^24-29, 64.38.214.0/24^24-29, 86.111.216.0/24^24-29, 114.111.128.0/24^24-29, 114.111.137.0/24^24-29, 114.111.140.0/24^24-29, 116.50.58.0/24^24-29, 116.90.131.0/24^24-29, 116.90.135.0/24^24-29, 119.161.82.0/24^24-29, 122.100.4.0/24^24-29, 122.200.128.0/24^24-29, 122.252.4.0/24^24-29, 131.203.0.0/24^24-29, 161.29.0.0/24^24-29, 161.65.0.0/24^24-29, 166.65.0.0/24^24-29, 168.134.2.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 193.108.151.0/24^24-29, 202.3.98.0/24^24-29, 202.14.63.0/24^24-29, 202.20.97.0/24^24-29, 202.22.175.0/24^24-29, 202.27.12.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.205.0/24^24-29, 202.41.194.0/24^24-29, 202.44.75.0/24^24-29, 202.46.176.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.65.13.0/24^24-29, 202.69.216.0/24^24-29, 202.69.219.0/24^24-29, 202.77.136.0/24^24-29, 202.92.242.0/24^24-29, 202.93.190.0/24^24-29, 202.160.50.0/24^24-29, 202.167.229.0/24^24-29, 202.177.207.0/24^24-29, 202.177.212.0/24^24-29, 202.177.217.0/24^24-29, 202.177.218.0/24^24-29, 202.182.112.0/24^24-29, 202.182.119.0/24^24-29, 202.182.120.0/24^24-29, 203.0.155.0/24^24-29, 203.2.210.0/24^24-29, 203.3.126.0/24^24-29, 203.5.45.0/24^24-29, 203.9.49.0/24^24-29, 203.10.77.0/24^24-29, 203.10.78.0/24^24-29, 203.14.211.0/24^24-29, 203.14.230.0/24^24-29, 203.16.25.0/24^24-29, 203.16.26.0/24^24-29, 203.17.68.0/24^24-29, 203.17.183.0/24^24-29, 203.18.22.0/24^24-29, 203.18.94.0/24^24-29, 203.18.103.0/24^24-29, 203.18.187.0/24^24-29, 203.18.235.0/24^24-29, 203.19.66.0/24^24-29, 203.19.212.0/24^24-29, 203.20.18.0/24^24-29, 203.20.113.0/24^24-29, 203.21.17.0/24^24-29, 203.23.105.0/24^24-29, 203.23.191.0/24^24-29, 203.23.194.0/24^24-29, 203.24.22.0/24^24-29, 203.24.61.0/24^24-29, 203.25.165.0/24^24-29, 203.27.100.0/24^24-29, 203.27.248.0/24^24-29, 203.29.0.0/24^24-29, 203.29.45.0/24^24-29, 203.29.77.0/24^24-29, 203.29.176.0/24^24-29, 203.29.180.0/24^24-29, 203.30.33.0/24^24-29, 203.30.138.0/24^24-29, 203.31.48.0/24^24-29, 203.32.61.0/24^24-29, 203.32.82.0/24^24-29, 203.33.171.0/24^24-29, 203.33.254.0/24^24-29, 203.34.110.0/24^24-29, 203.34.140.0/24^24-29, 203.34.200.0/24^24-29, 203.34.202.0/24^24-29, 203.34.235.0/24^24-29, 203.55.18.0/24^24-29, 203.55.38.0/24^24-29, 203.55.115.0/24^24-29, 203.55.131.0/24^24-29, 203.55.158.0/24^24-29, 203.55.254.0/24^24-29, 203.56.27.0/24^24-29, 203.56.186.0/24^24-29, 203.56.230.0/24^24-29, 203.56.234.0/24^24-29, 203.57.93.0/24^24-29, 203.145.60.0/24^24-29, 203.161.132.0/24^24-29, 203.161.144.0/24^24-29, 203.171.208.0/24^24-29, 203.190.217.0/24^24-29, 203.221.207.0/24^24-29, 209.160.82.0/24^24-29, 210.7.46.0/24^24-29, 210.8.113.0/24^24-29, 210.9.34.0/24^24-29, 210.9.134.0/24^24-29, 210.56.153.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: macca(a)vocus.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090313 source: NZRR ------------------------------------------------------------

1 0

Four blocks of AS Numbers allocated
by Leo Vegoda 12 Mar '09

12 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of four blocks of AS Numbers recently. 49152-50175 Assigned by RIPE NCC whois.ripe.net 2009-03-06 50176-51199 Assigned by RIPE NCC whois.ripe.net 2009-03-06 51200-52223 Assigned by RIPE NCC whois.ripe.net 2009-03-06 52224-53247 Assigned by LACNIC whois.lacnic.net 2009-03-11 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.9.1.287 wj8DBQFJuUXxvBLymJnAzRwRAkgiAJ4gPAIF9egizyMbGGB/2MAciOCsdQCfXQfX N4gRb5lyNjDDcKZ4bhf5AqY= =LKc/ -----END PGP SIGNATURE-----

1 0

TelstraClear IP Routing Contact
by Matthew Moyle-Croft 11 Mar '09

11 Mar '09

Hi, I've tried phone numbers in the APNIC whois DB for AS9901 and the numbers on the NZNOG NOC contacts page for TelstraClear (AS9901) but I get "no longer in service". Any chance someone who has an ability to talk BGP engineering could contact me about a routing issue causing high latency to us? Phone call or email is fine (see below for details). Thanks, Matthew -- Matthew Moyle-Croft Internode/Agile Peering and Core Networks Level 5, 162 Grenfell Street, Adelaide, SA 5000 Australia Email: mmc(a)internode.com.au Web: http://www.on.net Direct: +61-8-8228-2909 Mobile: +61-419-900-366 Reception: +61-8-8228-2999 Fax: +61-8-8235-6909

1 0

Fwd: [kiwi foo campers] stubbornness
by Andy Linton 11 Mar '09

11 Mar '09

Seems to me that ISPs should follow TelstraClear's lead and get their ass out of the TCF negotiations ASAP. andy Begin forwarded message: > From: Richard Wood <richard(a)internetnz.net.nz> > Date: 12 March 2009 10:32:37 > To: campers(a)groups.baacamp.org > Subject: [kiwi foo campers] stubbornness > Reply-To: campers(a)groups.baacamp.org > > A spokesman for Justice Minister Simon Power told NZPA it was still > the > Government's preference that the industry should sort out the issue > itself. > > "We're advised that the negotiations are going along in a reasonably > constructive way so we're hopeful that could still happen, even > without > TelstraClear," the spokesman said. > > http://www.guide2.co.nz/politics/news/copyright-negotiations-reasonably-con… >

6 8

TelstraClear have rejected s92a
by Spiro Harvey 11 Mar '09

11 Mar '09

for those who haven't seen: http://www.stuff.co.nz/technology//2252415/TelstraClear-rejects-copyright-c… I believe this means that the law will be suspended and rewritten. -- Spiro Harvey UNIX Specialist, Writer, Editor http://twiddle.starforge.net.nz Give us this day our garlic bread and lead us not into vegetarianism but deliver us some pizza. +++ ATH0

4 7

ASO Call for Comments on Nominees for ICANN Board Seat
by Srinivas (Sunny) Chendi 09 Mar '09

09 Mar '09

Dear Colleagues, Following a public nomination period that closed on 22 February 2009, the ASO Address Council (ASO AC) selected the final set of candidates to fill the ASO seat on the ICANN Board. This seat is currently held by Dave Wodelet, whose term expires in May 2009. The candidates are: - Jody Daniel Newman - Ray Plzak - Jordi Palet Martinez - Rajesh Chharia - Suzanne Woolf - Barry Shein The candidates listed above agree to serve in an ASO seat on the ICANN Board of Directors if selected by the ASO Address Council. In April 2009, the ASO AC will make its final selection to appoint one of these individuals to fill the ASO Board seat. To aid them in making their final selection, the ASO AC members request public comments and statements of support for the candidates. The public comment period will remain open until 23:59 (UTC) on 9 April 2009. You can provide your comments and statements of support for the candidates on the aso-announce mailing list. These will be publicly archived at: http://www.aso.icann.org/lists Alternatively, if you would prefer not to subscribe to that mailing list, you may submit your comments directly to the ASO AC Nominations Committee by sending an email to <nom-com(a)aso.icann.org>. A digest of all comments sent to the mailing list or received by the Nominations Committee will be published on the ASO web site at: http://www.aso.icann.org/elections Best regards, Srinivas (Sunny) Chendi External Relations Manager APNIC For; Axel Pawlik Managing Director RIPE NCC On behalf of the ASO/NRO Secretariat

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.27.192.0/21^21-29, 202.126.80.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.168.0/24^24-29, 202.37.254.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.198.0/24^24-29, 202.169.223.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.230.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: tomi.stark(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 09 Mar '09

09 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS38333 descr: Route set advertised to AS9560 by Symbio Networks - AS38333 members: 115.187.128.0/17^17-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: arman.hossain(a)symbionetworks.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090213 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38333 descr: advertised to AS9560 by Symbio Networks Pty ltd - AS38333 members: 115.187.128.0/17^17-29, 125.213.160.0/19^19-29, 210.80.131.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: arman.hossain(a)symbionetworks.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090310 source: NZRR ------------------------------------------------------------

1 0

APE 6to4
by Michael Fincham 08 Mar '09

08 Mar '09

Hi everyone, Just a quick announcement to say that with the departure of Jasper (who some of you may have met at NZNOG 09/08) we will unfortunately be withdrawing our 6to4 announcements from the APE. This was his project and we no longer have any staff enthusiastic about maintaining it. Expect the routes to disappear at some point in the next few days. If anyone is seriously using this service, feel free to get in touch and we'll see what we can do. -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 DDI: 03 978 1223 Mobile: 027 666 4482

6 10

NZRR Route Registry Update
by NZRR Database Notifications 05 Mar '09

05 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Mar '09

05 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.198.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090306 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 Mar '09

03 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications Ltd. - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090304 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 03 Mar '09

03 Mar '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090127 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications Ltd. - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 203.171.223.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090304 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] APNIC EC Results
by James Spenceley 01 Mar '09

01 Mar '09

Noggers, As Macca and Bambi pointed out, I was elected to the APNIC EC last week (even without emailing every member :-) Thanks to everyone who took the time to fill out proxies and stood in front of fax machines, those who voted online and everyone who generally encouraged others to vote, it was awesome to get so much support ! I owe you all lots and lots of beer. Thanks ! -- James

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 Mar '09

01 Mar '09

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. Work is now under way aimed at establishment of a Trust to ensure that NZNOG can continue to meet. The aim of this work is to provide the legal framework needed to allow a bank account to be operated while avoiding the administrative overhead which would be involved in setting up an Incorporated Society. NZNOG is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference See http://2009.nznog.org/ for details of this year's conference. The plan is that next year's conference will be further south than Auckland. Discussions are now being held with prospective hosts, so if you have a burning desire to host New Zealand's only technical networking conference, now would be the time to speak up. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 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. About This Mailing List This list has around 1000 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 APN Online, Citylink, and The University of Waikato. 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 -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

APNIC EC Results
by McDonald Richards 26 Feb '09

26 Feb '09

Sorry for the cross-post but since a bunch of NZ proxies helped this happen I figured I'd share the news here as well. For all those not watching the live feed, James Spenceley was just elected on to the APNIC EC. I'm sure there will be a more formal announcement later from APNIC but figured you'd all want to know how your proxies went. Macca

3 2

APNIC 27 - Meeting update
by Srinivas (Sunny) Chendi 26 Feb '09

26 Feb '09

________________________________________________________________________ APNIC 27 23-27 February 2009, Manila, Philippines ________________________________________________________________________ Thank you to everyone who contributed to APNIC 27, held in conjunction with APRICOT 2009. The preliminary event participation statistics are: Total number of delegates (including APRICOT): 473 Delegates at APNIC Member Meeting: 114 Economies represented: 40 APNIC member organizations represented: 113 APNIC held remote participation events via video conference in Suva, Fiji and Colombo, Sri Lanka. Attendance figures for these events were: Suva, Fiji 10 Colombo, Sri Lanka 22 Web-based online participation options included a choice of video, audio and text chat. Participation figures for online remote delegates were: Online remote participation feeds 2518 To read, watch or listen to archives from the meeting, go to: http://meetings.apnic.net Elections --------- During the APNIC Member Meeting (AMM) in Manila on Friday, 27 February 2009, the following candidates were elected to the APNIC Executive Council (EC). - Jian Zhang - James Spencley - Kuo-Wei Wu - Hyun Joon Kwon Congratulations to the successful candidates: Election details are available at: http://meetings.apnic.net/elections Meeting decisions ----------------- Policy SIG Seven policy proposals were discussed. The following proposals reached consensus and were subsequently ratified at the APNIC Member Meeting. These proposals are now subject to a 'last call' for comments: prop-050 IPv4 address transfers (with modifications) prop-069 Global policy proposal for the allocation of IPv4 blocks to Regional Internet Registries The following proposals did not reach consensus and have been abandoned: prop-063 Reducing timeframe of IPv4 allocations from twelve to six months prop-060 Change in the criteria for the recognition of NIRs in the APNIC region prop-070 Maximum IPv4 allocation size The following proposals were withdrawn by the author(s): prop-068 Inter-RIR transfer policy prop-067 A simple transfer proposal You can check the status of all policy proposals on the following page: http://www.apnic.net/policy/proposals MoUs Signed ----------- APNIC signed Memorandums of Understanding with the following organizations: NSP (Networkers' Society of Pakistan) ASTI (Advanced Science and Technology Institute PHNOG (Philippine Network Operators Group) Meeting sponsors ---------------- APNIC offers its deepest thanks to the sponsors of APNIC 27, whose invaluable contributions allowed APNIC to offer a meeting program of a very high standard: http://meetings.apnic.net/sponsors Upcoming APNIC meetings ----------------------- APNIC 28 24-28 August 2009 Beijing, China http://www.apnic.net/meetings/28 APNIC 29 1-5 March 2010 Kuala Lumpur, Malaysia http://www.apnic.net/meetings/29 Regards -------------------------------------------------------------------- Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99 ____________________________________________________________________

1 0

Interesting - How a Router's Missed Range Check Nearly Crashed the Internet
by Skeeve Stevens 26 Feb '09

26 Feb '09

>From the front page of Slashdot: Barlaam writes "A bug by router vendor A (omitting a range check from a critical field in the configuration interface) tickled a bug from router vendor B (dropping BGP sessions when processing some ASPATH attributes with length very close to 256), causing a ripple effect that caused widespread global routing instability last week. The flaw lay dormant until one of vendor A's systems was deployed in an autonomous system whose ASN, modulo 256, was greater than 250. At that point, the Internet was one typo away from disaster. Other router vendors, who were not affected by the bug, happily propagated the trigger message to every vulnerable system on the planet in about 30 seconds. Few people appreciate how fragile and unsecured the Internet's trust-based critical infrastructure really is - this is just the latest example." Vendor A, in this case, is a Latvian router vendor called MikroTik. Is this just the 4byte ASN thing from months ago or something new? I knew there was a reason I hated Mikrotik's so much. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

3 2

NZRR Route Registry Update
by NZRR Database Notifications 23 Feb '09

23 Feb '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS10022 descr: advertised to AS9439 by Datacom Systems Wellington Limited - AS10022 members: 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.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: matthewda(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080111 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS10022 descr: advertised to AS9439 by Datacom Systems (Wellington) Limited - AS10022 members: 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.198.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: matthewda(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090224 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes!
by Skeeve Stevens 22 Feb '09

22 Feb '09

I should have mentioned... if you have already assigned your votes for James - and this includes the proxy votes you filled out as AUSNOG2 or have arranged privately. My email is mainly to remind anyone who hasn't done anything with their votes yet and might consider it at the last minute. The reason I have also asked them for myself is that a) I am here onsite, so I can use them, b) most of the other guys are very busy doing their political things and I am happy to spend the time filling out forms to help James and David get elected. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced. From: Sean K. Finn [mailto:Sean.Finn(a)ozservers.com.au] Sent: Monday, 23 February 2009 3:04 PM To: Skeeve Stevens; 'ausnog(a)lists.ausnog.net'; 'NZNOG(a)list.waikato.ac.nz' Subject: RE: [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes! For the benefit of all, Would this be the same as the proxy votes assigned after AusNog02 last year, or if we wanted to re-allocate rights for this election would we need to submit another proxy form? I.e. Were the proxy rights assigned during AusNOG02 for this election? Cheers, Sean. From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Monday, 23 February 2009 1:51 PM To: ausnog(a)lists.ausnog.net; NZNOG(a)list.waikato.ac.nz Subject: [AusNOG] (Urgent) APNIC Executive Council (EC) Election this Week - We need your votes! Hey Everyone, I am here in Manila at the APRICOT 2009/APNIC 27 conference and it looks like this week is going to be a lot of fun with great people to meet as well as some very interesting things happening. The key issue I am sending this email to the AU/NZNOG and Aussie-ISP lists is to appeal to anyone who has not yet decided to, or just plain forgot to do anything about the voting power they may have as an APNIC member. We have a chance of getting two Australians onto the APNIC EC. The current membership is listed at http://www.apnic.net/ec/ and as you can see, it would be massively beneficial if we had some Australian representation. Our two nominations are James Spenceley<http://meetings.apnic.net/elections/james-spenceley.html> from Vocus Communications (www.vocus.com.au<http://www.vocus.com.au>) and David Woodgate<http://meetings.apnic.net/elections/david-woodgate.html> from Telstra. Both of these guys have both been involved in internet policy making for a VERY long time and are both worthy for the positions available on the EC. They are very respected in the Internet Community, both in Australia and NZ and the world over, both having presented policies an given talks at many conferences. If you don't know them and want some more information, please refer to their Nomination profiles by clicking on their names above. There are 10 nominations and 4 positions available with 1 re-standing with most of the nominees are people from countries with massive populations and large voting power such as China, India and so on. If we have any chance to get Australia/NZ to have some involvement in influencing the direction of internet governance and policy going forward, it is time we stood up and did something with out votes instead of wasting them. To me, it doesn't matter if you like or dislike either James or David, have a past or future with these guys, but if you want to support the Internet community in Australia and New Zealand as a whole, I think that these guys are will represent the issues of Australia/New Zealand very well and certainly worth the 5 minutes to fill out the proxy form and help get them elected. Details about the current election are here: http://meetings.apnic.net/elections/index.html The list of current nominations are as listed at: http://www.apnic.net/news/2009/0216a.html If you wish to contribute your votes there are two ways. You can assign proxy, or you can vote online using MyAPNIC, but many have not registered for this, and it is too late now if you already have not. I am happy to be the person for you to allocate your votes to, which you can do once off for this election by using the Proxy Form included. Please note: A proxy appointment is valid only for a single election, so I can only vote for you in this one case. You are not assigning me permanent voting rights for your organisation. If you didn't receive the attached Proxy form you can download a pre-filled one with my details from http://www.eintellego.net/apnic/APNIC27VoteProxySkeeve.pdf, or failing that, use my details below - don't forget to inform me if you are sending me your proxy as I need to know what members I am collecting the forms for. For details: http://meetings.apnic.net/elections/about/proxy.html are the official details on assigning your proxy votes. If you don't know your membership level as it is right now, Aussies please check http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=au&sort=ascending or for the Kiwi's http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=nz&sort=ascending which will show you what APNIC considers your membership level to currently be. Note: You may have more resources than your current level, but your annual membership might not have come up yet. All your votes are useful, even if you are an associate with only 1 vote as they all add up and elections can come down to just a couple of votes. The number of votes you have are as follows: Associate 1 Very small 2 Small 4 Medium 8 Large 16 Very large 32 Extra large 64 My voting will be for James and David, but with the excess votes, I will be following their advice on who else should be supported. If you know anyone on that membership list who isn't using those votes, please contact them... the larger the members the better as it is less work, but every single vote counts. Forward this email to them and they might have the 5 minutes to fill it out. Just remember, it has to be completed by the Corporate Contact. Also, this has to be done today or tomorrow... please spare the 5 minutes to help us have a say in our own future as ISP's and internet community members. If you have any questions, please send them and I will get back to you asap ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

S92a implementation delayed, clause may be suspended.
by Juha Saarinen 22 Feb '09

22 Feb '09

http://bit.ly/3RiQL Bit.ly URL goes to Computerworld NZ. -- Juha Saarinen juha(a)saarinen.org

1 1

(Urgent) APNIC Executive Council (EC) Election this Week - We need your votes!
by Skeeve Stevens 22 Feb '09

22 Feb '09

Hey Everyone, I am here in Manila at the APRICOT 2009/APNIC 27 conference and it looks like this week is going to be a lot of fun with great people to meet as well as some very interesting things happening. The key issue I am sending this email to the AU/NZNOG and Aussie-ISP lists is to appeal to anyone who has not yet decided to, or just plain forgot to do anything about the voting power they may have as an APNIC member. We have a chance of getting two Australians onto the APNIC EC. The current membership is listed at http://www.apnic.net/ec/ and as you can see, it would be massively beneficial if we had some Australian representation. Our two nominations are James Spenceley<http://meetings.apnic.net/elections/james-spenceley.html> from Vocus Communications (www.vocus.com.au<http://www.vocus.com.au>) and David Woodgate<http://meetings.apnic.net/elections/david-woodgate.html> from Telstra. Both of these guys have both been involved in internet policy making for a VERY long time and are both worthy for the positions available on the EC. They are very respected in the Internet Community, both in Australia and NZ and the world over, both having presented policies an given talks at many conferences. If you don't know them and want some more information, please refer to their Nomination profiles by clicking on their names above. There are 10 nominations and 4 positions available with 1 re-standing with most of the nominees are people from countries with massive populations and large voting power such as China, India and so on. If we have any chance to get Australia/NZ to have some involvement in influencing the direction of internet governance and policy going forward, it is time we stood up and did something with out votes instead of wasting them. To me, it doesn't matter if you like or dislike either James or David, have a past or future with these guys, but if you want to support the Internet community in Australia and New Zealand as a whole, I think that these guys are will represent the issues of Australia/New Zealand very well and certainly worth the 5 minutes to fill out the proxy form and help get them elected. Details about the current election are here: http://meetings.apnic.net/elections/index.html The list of current nominations are as listed at: http://www.apnic.net/news/2009/0216a.html If you wish to contribute your votes there are two ways. You can assign proxy, or you can vote online using MyAPNIC, but many have not registered for this, and it is too late now if you already have not. I am happy to be the person for you to allocate your votes to, which you can do once off for this election by using the Proxy Form included. Please note: A proxy appointment is valid only for a single election, so I can only vote for you in this one case. You are not assigning me permanent voting rights for your organisation. If you didn't receive the attached Proxy form you can download a pre-filled one with my details from http://www.eintellego.net/apnic/APNIC27VoteProxySkeeve.pdf, or failing that, use my details below - don't forget to inform me if you are sending me your proxy as I need to know what members I am collecting the forms for. For details: http://meetings.apnic.net/elections/about/proxy.html are the official details on assigning your proxy votes. If you don't know your membership level as it is right now, Aussies please check http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=au&sort=ascending or for the Kiwi's http://www.apnic.net/apnic-bin/memlist.pl?size=&cc=nz&sort=ascending which will show you what APNIC considers your membership level to currently be. Note: You may have more resources than your current level, but your annual membership might not have come up yet. All your votes are useful, even if you are an associate with only 1 vote as they all add up and elections can come down to just a couple of votes. The number of votes you have are as follows: Associate 1 Very small 2 Small 4 Medium 8 Large 16 Very large 32 Extra large 64 My voting will be for James and David, but with the excess votes, I will be following their advice on who else should be supported. If you know anyone on that membership list who isn't using those votes, please contact them... the larger the members the better as it is less work, but every single vote counts. Forward this email to them and they might have the 5 minutes to fill it out. Just remember, it has to be completed by the Corporate Contact. Also, this has to be done today or tomorrow... please spare the 5 minutes to help us have a say in our own future as ISP's and internet community members. If you have any questions, please send them and I will get back to you asap ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

UPDATE: CCIP Alert: Adobe Acrobat unpatched vulnerability
by Paul McKitrick 21 Feb '09

21 Feb '09

UPDATE: Apologies for the previous email that contained the wrong content. Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the critical vulnerability in Adobe Reader and Adobe Acrobat that could potentially allow an attacker to take control of the affected system which was released on February 19: http://www.adobe.com/support/security/advisories/apsa09-01.html CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Adobe have stated that they are expecting to release an update by 11 March 2009 for Adobe 9 and updates for other versions (8 and 7) to follow soon after. Adobe has reported that the following versions are affected: * Adobe Reader 9 and earlier versions * Adobe Acrobat Standard, Pro, and Pro Extended 9 and earlier versions Shadowserver have a write up on their website: http://www.shadowserver.org/wiki/pmwiki.php?n=Calendar.20090219 The US-CERT write up (https://www.kb.cert.org/vuls/id/905281) includes the following mitigation advice: Disable JavaScript in Adobe Reader and Acrobat Disabling Javascript may prevent this vulnerability from being exploited. Acrobat JavaScript can be disabled in the General preferences dialog (Edit -> Preferences -> JavaScript and un-check Enable Acrobat JavaScript). Some vendors ship javascript support in a seperate package. Removing this package may remove javascript support in the Adobe PDF reader. Prevent Internet Explorer from automatically opening PDF documents The installer for Adobe Reader and Acrobat configures Internet Explorer to automatically open PDF files without any user interaction. This behavior can be reverted to the safer option of prompting the user by importing the following as a .REG file: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\AcroExch.Document.7] "EditFlags"=hex:00,00,00,00 Disable the displaying of PDF documents in the web browser Preventing PDF documents from opening inside a web browser may mitigate this vulnerability. If this workaround is applied to updated versions of the Adobe reader, it may mitigate future vulnerabilities. To prevent PDF documents from automatically being opened in a web browser: 1. Open Adobe Acrobat Reader. 2. Open the Edit menu. 3. Choose the preferences option. 4. Choose the Internet section. 5. Un-check the "Display PDF in browser" check box. Do not access PDF documents from untrusted sources Do not open unfamiliar or unexpected PDF documents, particularly those hosted on web sites or delivered as email attachments Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

CCIP Alert: Adobe Acrobat unpatched vulnerability
by Paul McKitrick 21 Feb '09

21 Feb '09

Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the the Critical Microsoft Security Bulletin MS09-002 that was released on February 10: http://www.microsoft.com/technet/security/bulletin/ms09-002.mspx Microsoft have announced a vulnerability in Internet Explorer 7 that could allow remote code execution if a user views a specially crafted Web page. Administrators are advised to patch immediately. Microsoft have rated as Critical for Window XP and Windows Vista and as Moderate for Windows Server 2003 and Windows Server 2008. CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Due to the recent impact of the Conficker worm CCIP wants to ensure that there is awareness of the active exploitation of MS09-002 and to encourage the patching of systems if they have not already been patched. AusCERT have a write up on their website: http://www.auscert.org.au/render.html?it=10477 There is also a write up on the Sourcefire Vulnerability Research Team’s blog: http://vrt-sourcefire.blogspot.com/2009/02/ms09-002-in-wild.html Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

CCIP ALERT: Exploitation of MS09-002
by Paul McKitrick 21 Feb '09

21 Feb '09

Good Afternoon, For those of you who are not already aware, CCIP would like to bring your attention the the Critical Microsoft Security Bulletin MS09-002 that was released on February 10: http://www.microsoft.com/technet/security/bulletin/ms09-002.mspx Microsoft have announced a vulnerability in Internet Explorer 7 that could allow remote code execution if a user views a specially crafted Web page. Administrators are advised to patch immediately. Microsoft have rated as Critical for Window XP and Windows Vista and as Moderate for Windows Server 2003 and Windows Server 2008. CCIP is releasing this alert as it has been made aware of active exploitation of this vulnerability in the wild. Due to the recent impact of the Conficker worm CCIP wants to ensure that there is awareness of the active exploitation of MS09-002 and to encourage the patching of systems if they have not already been patched. AusCERT have a write up on their website: http://www.auscert.org.au/render.html?it=10477 There is also a write up on the Sourcefire Vulnerability Research Team’s blog: http://vrt-sourcefire.blogspot.com/2009/02/ms09-002-in-wild.html Regards, The CCIP Team -- Centre for Critical Infrastructure Protection Government Communications Security Bureau P: +64 4 498 7654 F: +64 4 498 7655 E: info(a)ccip.govt.nz I: www.ccip.govt.nz --- This e-mail contains official New Zealand Government information, which is intended for the use of addressees only. If you have received this e-mail in error, please notify the sender immediately and delete. You should not further disseminate, distribute or copy this e-mail in any way. ---

1 0

NZNOG-09 Videos
by Richard Naylor 20 Feb '09

20 Feb '09

Video and audio (MP3) from NZNOG 09 is available at http://www.r2.co.nz/20090129/ There is both streamed and downloadable versions, and versions in wmv, MP4 and MP3. One talk was not recorded at the request of the presenter. The video isn't too bad - the lighting was a challenge, and there was no one driving the audio desk, so the feed we got varied a little. But it should be quite usable for those who couldn't make it. Richard

1 0

Voting process
by Skeeve Stevens 19 Feb '09

19 Feb '09

Just a quick question about the APNIC EC elections. If someone has a lot of votes/proxies, and they don't get up, are they able to pass their votes to someone else? ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

8 8

New Telstra transparent proxy/config?
by Joel Wiramu Pauling 19 Feb '09

19 Feb '09

Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27 which appears to be a new upstream proxy hop I have not seen before: traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual) Can anyone confirm similar behaviour who is on Telstra cable network, or have further details. Appears to be a netcache proxy. Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1) Kind regards -JoelW

5 6