- NZNOG - lists.nznog.org

Re: [nznog] Moving DNS providers - best practice.
by Mark Foster 26 Oct '06

26 Oct '06

On Fri, 27 Oct 2006, Peter Mott wrote: > On 27/10/2006, at 3:23 PM, Mark Foster wrote: > >> Ask them do a whois on the domain, and then point out that if they are >> carrying Authoritive NS records for a domain which the rootservers are >> pointing elsewhere - whois tells you this - they are breaking the DNS. > > One could also encourage folks to use different name servers for caching and > not allow recursion on their authoritative servers. That way if they claim > to be authoritative and they are no longer, nobody cares. > > I seem to remember having a discussion about this very thing with a large > provider about 6 years ago and they were not interested in any form of > co-operation that would prevent client internet experience being broken when > a change of delegation took place. They didn't have the capacity to > understand the problem let alone a resolve to solve it. I wonder if anything > has changed :-) Actually a possible 'reason' for this just occurred to me. If you're buying a DNS hosting service from an ISP, does the ISP have the right to cancel said hosting service without authority from the customer? This, I believe, has been a cited reason _not_ to remove legacy DNS (despite what the registry says) for at least one provider i've heard of before now. It makes the issue one of customer-provider liason - and one of monetary/commercial significance - instead of dns/operational significance. I favour the latter. But there may be a valid point here... Mark.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '06

25 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061026 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '06

25 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061026 source: NZRR

1 0

Network Specialist - position available at the National Library Wellington
by Patrick Mchale 25 Oct '06

25 Oct '06

We currently have a position available for a Network Specialist at the National Library of New Zealand, Wellington Vacancy Number: NL1881 http://www.jobs.govt.nz/jobs/viewjob.aspx?OpportunityID=31009 for more details of the National Library http://www.natlib.govt.nz/en/about/2working.html Regards Patrick McHale Network Specialist National Library of New Zealand

1 0

OT Slingshot activations/admin request
by Barry Murphy 23 Oct '06

23 Oct '06

Hi There, First off sorry for the offtopic post, though I'm drinking beer and offering beer to someone that can help me from Slingshot activations / admin. For some odd reason my Italk number fell off the face of slingshot (perhaps it's in fiji or been sold without knowing) since Saturday afternoon. No one till now has been able to help and it's causing issues for people trying to contact me and for me in general. Please reply offlist if you can assist, beer offerings. Cheers Barry -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

national bank phish
by roberth＠plain.co.nz 18 Oct '06

18 Oct '06

heads up on a recent PHISHing attack I guess others may have users complaining about the PHISH just arriving representing itself as the National Bank while the site collecting is http://www.ffmd.org/bilder/www.nbnz.co.nz/login.html We've found a live chat with the web provider for ffmd.org and mailed abuse@@b-one.net who own the IP space. Any other strategies to close an internationally hosted one like this? -Robert

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 210.5.48.0/21^21-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060724 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061019 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES: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, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.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.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 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 20061019 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.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.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 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 20061019 source: NZRR

1 0

New IPv6 block allocated to RIPE NCC
by leo vegoda 17 Oct '06

17 Oct '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv6 address range 2a00::/12 from the IANA in October 2006. This allocation expands two previous allocations. We will begin allocating from this new space in the near future. The minimum allocation size for this /12 has been set at /32. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

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

17 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.24.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: leon.chang(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061018 source: NZRR

1 0

Trogan site and spam run using nuclear tests of North Korea as a hook (AUSCERT#2006ba825)
by matthew＠auscert.org.au 16 Oct '06

16 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Not sure if anyone else has seen this but here it is again if so. First seen discussed per SANS http://isc.sans.org/diary.php?date=2006-10-14 * h t t p://cnnwarnews(dot)com/ uses an iframe to go to * h t t p://www.theaustralian.news.com.au/index/0,,5002460,00.html which is a legit Australian news site but also uses another iframe to open * h t t p://zagevqsoii(dot)biz/dl/adv433_.php and this opens: * h t t p://zagevqsoii(dot)biz/dl/loadadv433.exe If you google for usage of the domain you can see that it has been seeding web forums with supposed "news" stories about North Korea that entice victims to get infected as above: * h t t p://www.google.com/search?q=www(dot)cnnwarnews(dot)com * h t t p://www.google.com/search?q=au(dot)cnnwarnews(dot)com eg: h t t p://sv.wikipedia.org/wiki/The_Forum h t t p://www.kaigai-wedding.com/cgi-bin/wforum3/wforum.cgi?mode=new_sort h t t p://www.depdiknas.go.id/RPP/modules.php?name=Forums&file=posting&mode=topicreview&t=1331 The articles being seeded or spammed around usually look like this: Subject: North Korea vs Australia - nuclear stress Prime minister of Australia John Govard claimed that "..nuclear tests of North Korea was confirmed by seismological data", Associated Press. In connection with increase of probability of nuclear attack from the direction of North Korea Minister of Defence of Australia along with Ministers of Defence of China, South Korea and Russia signed a memorandum on infliction? h t t p://au(dot)cnnwarnews(dot)com/topnews/ The infection process is/was the same as above. Still accessible to the spammed material via: wget --header="Host: au(dot)cnnwarnews(dot)com" h t t p://203.116.50.253/topnews/ The original infector file, loadadv433.exe, is detected as Harnig which grabs: * h t t p://zbobivgcso(dot)biz/dl/loadadv455.exe And this then grabs: * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/ffkzyu * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/oswzvfcm * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/tkshrolhx.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/plgrx.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/rsamiscm * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/djrhd.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/gwrkgq.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/mhghnoxhnv.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/wipfrokuw.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/idlgmwf.php We have submitted all of these binaries to AV and sent shutdown requests for the four key domains above. We haven't seen much discussion of this but maybe the spam run hasn't really taken off yet. The subject of the upcoming spam run will probably look like "North Korea vs Australia - nuclear stress" and have the same text at the forum spams above. Credit to F-Secure for some of their analysis on this. Hope this is of some use. 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.5 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRTSTYCh9+71yA2DNAQIZDwP/SZQYu/hzHAutGUa+6pkQqCRAczlMoqYw rjiCm71mfX++HCEup7IXo9NzW4rTPhCxNfM5q+qhukUZlWLd4QFah2eRk+fFtopT Sf1POAOuWM0knjwBRWPG156bA4jytLIu+UU+M9P8hoFt4MovvQYqPljOsIpSBADe eAgPsGrny8k= =guYP -----END PGP SIGNATURE-----

1 0

Re: [nznog] NZNOG 07 - Call for Participation and Papers
by Simon Lyall 15 Oct '06

15 Oct '06

A reminder that submissions for NZNOG 07 close in 4 days on Friday the 20th. Please contact talks(a)nznog.org if you are interested in holding a SIG or presenting at the main conference. On Tue, 5 Sep 2006, Simon Lyall wrote: > > NZNOG 07 - Call for Participation and Papers > > The next conference of the New Zealand Network Operators' Group is to be held > in Palmerston North, New Zealand between 31 January and 2 February 2007. Our > host is Inspire.net and the venue is to be at Massey University's campus. > > NZNOG meetings provide opportunities for the exchange of technical > information and discussion of issues relating to the operation and > support of network services, with particular emphasis on New Zealand. > > The conference is low priced and has a strong technical focus with the > aim and history of getting a strong turnout of technical personal from > New Zealand Internet orientated companies. > > Conference Overview > ------------------- > > NZNOG 2007 will consist of one day Special Interest Group ( SIG ) Meetings > followed by two days of conference presentations. There will also be > opportunity for more informal and small lightening talks. These are typically > around five minutes long and are organised closer to the actual conference. > > Important Dates > --------------- > > Call for Papers opens: 5 September 2006 > Deadline for speaker submissions: 20 October 2006 > Responses to speaker submissions: 27 October 2006 > Draft program published: 1 November 2006 > Final program published: 18 December 2006 > NZNOG 2007 Conference: 31 January - 2 February 2007 > > SIG Meetings > ------------ > > The first day of the conference is arranged as parallel tracks to > cover subject material which is of interest to particular groups of > attendees. Proposals are requested for workshops, tutorials and other > appropriate special-interest meetings of interest to Network Operators. > > Topics which have been successful in the past, or have been requested > for this year are: > > * Advanced BGP gubbins > * IPV6 implementation > * Service Provider wireless networking > * VoIP > * BIND and DNSSEC > * MPLS and high performance IP backbone routing > * Systems Administration. > > The program committee will consider proposals for tutorials in any of these > or new areas. There is a single day of SIGs with up to five running > concurrently. > > If you have an idea for a tutorial subject that is not listed, please feel > free to submit it to us. > > > Conference Presentations > ------------------------ > > The main conference program for 2007 will be made up of two days with a > single stream where possible. Presentations don't need to fit any particular > fixed length and can be from 30 minutes to 3 hours in length. > > NZNOG conferences have traditionally spanned the entire operational spectrum, > and then some. Proposals for conference presentations are invited for > virtually any topic with a degree of relevance to the NZNOG community. > > Past years' talks have included the following: > > - Internet exchange operations > - Global anycast networks and the building thereof > - Peering, peering, and peering > - Network security > - 10GB ethernet operations > - Advanced networks in NZ > - Current Internet research in NZ > - Wireless networking > - QOS over carrier networks > - Content distribution networks and media streaming > > If you are interested in submitting a talk please fill out the questions > at then end of this document and email them to talks(a)nznog.org . > > Submission Guidelines > --------------------- > > When considering a presentation or SIG, remember that the NZNOG audience > is mainly comprised of technical network operators and engineers with a wide > range of experience levels from beginners to multi-year experience. There is > a strong orientation to offer core skills and basic knowledge in the SIGs > and to address issues relevant to the day-to-day operations of ISPs and > network operators in the conference sessions. > > The inclusion of a title, bio, topic, abstract, and slides with proposals > is not compulsory but each will help us determine the quality of your > proposal and increase the likelihood it will be accepted. > > Final slides are to be provided by 22 January 2007. > > Note: While the majority of speaking slots will be submitted by 20 October > 2006, a limited number of slots may be available for presentations that are > exceptionally timely, important, or of critical operational importance. > > The NZNOG conference is a TECHNICAL conference so marketing and commercial > content is NOT allowed within the program. The program committee is charged > with maintaining the technical standard of NZNOG conferences, and will > therefore not accept inappropriate materials. It is expected that the > presenter be a technical person and not a sales or marketing person. The > audience is extremely technical and unforgiving, and expects that the speakers > are themselves very knowledgeable. All sessions provide time for questions, > so presenters should expect technical questions and be prepared to deliver > insightful and technically deep responses. > > Funding and Support > ------------------- > > NZNOG conferences are community run and funded events that try to keep the > cost to attendees as low as possible so generally we are unable to pay the > travel costs of speakers. There is a limited amount of funding available to > international speakers. > > Conference presenters will not have to pay any registration fee for the day > they are presenting. Discounts for SIG and lightning talk presenters may > be available but are not automatic. > > Lightning talks > --------------- > > Lightning talks are short talks/presentations that last no more than 10 > minutes. This is a good opportunity to get your pet topic out there or > perhaps to get some experience with presenting without having to go to a > full talk. At NZNOG'07 it is planned that there will be at least one > hour long lightning talk session. > > Sponsors > -------- > > There are opportunities remaining for organisations to sponsor various > aspects of the NZNOG meeting. > > Please contact sponsorship(a)nznog.org for more information > > Contact > ------- > > Website > > * www.nznog.org > > General Enquiries > > * info(a)nznog.org > > Talks and Papers > > * talks(a)nznog.org > > > Talk Proposals > -------------- > > Please send all talk proposals (including lightning talks) to talks(a)nznog.org > along with the requested information. Questions regarding talks can be > sent to the same address. > > Sponsorship may be available for a limited number of overseas speakers > to attend the conference, please indicate if you require assistance > with travel and/or accommodation. > > Author's Full Name: > Author's Email Address: > Author's affiliation: > Author's short biography: > Title of Talk: > Abstract: > Length of talk: > Please provide details if a version of this talk has previously been given: > Will travel and accommodation assistance be required: > > > > -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Radio New Zealand Podcasts
by Richard Hulse 15 Oct '06

15 Oct '06

Operators may wish to know that as from today all our podcasts have been increased from 48 to 64 kbs. This is in repsonse to requests from consumers for an improvement in audio quality. Given the current number of downloads being requested, some operators may notice an increase in traffic. regards, Richard Hulse

1 0

NZNOG '06 videos
by Jeremy Naylor 11 Oct '06

11 Oct '06

Hey guys, Just a quick note to let you know that the videos for the talks at NZNOG '06 are now available. Sorry for the delay with them. They're at: http://www.r2.co.nz/20060323 Thanks, -- Jeremy Naylor p: +64 4 978 7371 p: +64 21 374 689 e: jeremy.naylor(a)r2.co.nz w: http://www.r2.co.nz/~jeremy w: http://e-living.wellington.net.nz -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/472 - Release Date: 11/10/2006

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Oct '06

10 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: simon.allard(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061011 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Oct '06

10 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 notify: simon.allard(a)staff.maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: simon.allard(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061011 source: NZRR

1 0

So...
by Justin Cook 09 Oct '06

09 Oct '06

Is everyone enjoying their DSL bandwidth? -- *Justin Cook* Developer http://www.skull.co.nz/ *Skype* justincookskull <skype:justincookskull?call> My status <skype:justincookskull?call>

3 2

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

09 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061010 source: NZRR

1 0

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

09 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.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, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061010 source: NZRR

1 0

Re: [nznog] Voda net off the air
by Alex Hague 08 Oct '06

08 Oct '06

I think a lot of their zone info is missing on their NS... >telnet whois.srs.net.nz 43 vodafone.co.nz % New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 1.23.0 query_datetime: 2006-10-09T16:27:28+13:00 domain_name: vodafone.co.nz query_status: 200 Active domain_dateregistered: 2000-06-28T15:02:12+12:00 domain_datebilleduntil: 2007-06-28T15:02:12+12:00 domain_datelastmodified: 2006-09-28T15:38:57+12:00 domain_delegaterequested: yes %  % technical_contact_name: Vodafone NMC technical_contact_address1: Private Bag 92161 technical_contact_address2: Auckland, New Zealand technical_contact_city: Auckland technical_contact_country: NZ (NEW ZEALAND) technical_contact_phone: +64 93 552313 technical_contact_email: soa(a)vodafone.co.nz % ns_name_01: isdn1ftc.vodafone.co.nz ns_ip4_01: 202.73.206.15 ns_name_02: isdn1ldv.vodafone.co.nz ns_ip4_02: 202.73.198.15 >nslookup > server isdn1ftc.vodafone.co.nz Default Server: isdn1ftc.vodafone.co.nz Address: 202.73.206.15 > set type=MX > vodafone.co.nz Server: isdn1ftc.vodafone.co.nz Address: 202.73.206.15 *** isdn1ftc.vodafone.co.nz can't find vodafone.co.nz: Server failed -----Original Message----- From: Tony Wicks [mailto:tony(a)prophecy.net.nz] Sent: Monday, 9 October 2006 4:20 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Voda net off the air Hmm, this is bad - [root(a)host1 root]# dig www.vodafone.co.nz ; <<>> DiG 9.2.4 <<>> www.vodafone.co.nz ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13333 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.vodafone.co.nz. IN A ;; Query time: 27 msec ;; SERVER: ;; WHEN: Mon Oct 9 16:16:40 2006 ;; MSG SIZE rcvd: 36 [root(a)host1 root]# dig vodafone.co.nz mx ; <<>> DiG 9.2.4 <<>> vodafone.co.nz mx ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44722 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;vodafone.co.nz. IN MX ;; Query time: 20 msec ;; SERVER: ;; WHEN: Mon Oct 9 16:17:06 2006 ;; MSG SIZE rcvd: 32 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Voda net off the air
by Tony Wicks 08 Oct '06

08 Oct '06

Hmm, this is bad - [root(a)host1 root]# dig www.vodafone.co.nz ; <<>> DiG 9.2.4 <<>> www.vodafone.co.nz ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13333 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.vodafone.co.nz. IN A ;; Query time: 27 msec ;; SERVER: ;; WHEN: Mon Oct 9 16:16:40 2006 ;; MSG SIZE rcvd: 36 [root(a)host1 root]# dig vodafone.co.nz mx ; <<>> DiG 9.2.4 <<>> vodafone.co.nz mx ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44722 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;vodafone.co.nz. IN MX ;; Query time: 20 msec ;; SERVER: ;; WHEN: Mon Oct 9 16:17:06 2006 ;; MSG SIZE rcvd: 32

2 1

Yet another Phishing Scam - Kiwibank?
by Mark Foster 05 Oct '06

05 Oct '06

It seems theres yet-another scam going around, interesting to see this one clearly targetting an NZ-Only bank: From: "Kiwi Bank" <accounts(a)kiwibank.co.nz> Subject: Important Changes to the Terms and Conditions Source IP in the case I saw was smtp19.orange.fr ([80.12.242.18]) and the embedded link was: http://mail.ardhi.go.ke/kiwibank.co.nz/banking/login.asp/?F6=1&F7=IB&F21=IB…"> It also includes a statement that requires you to say 'yes or no' to their "new" terms and conditions prior to 10 October 2006. Posted for the benefit of those who choose to either block the destination webserver or the mail relay involved... Mark.

3 2

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

04 Oct '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24111 descr: Route set advertised to AS9560 by nzWireless - AS24111 members: 203.110.28.0/23^23-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040927 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24111 descr: advertised to AS9560 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061005 source: NZRR --- PREVIOUS OBJECT: route: 203.110.28.0/23 descr: Route for nzWireless - AS24111 origin: AS24111 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040927 source: NZRR REPLACED BY: route: 203.110.28.0/23 descr: Route for NZWIRELESS - AS24111 origin: AS24111 notify: rpsl-admin(a)nzix.net notify: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061005 source: NZRR

1 0

Dunedin 5.8GHz
by Stu Fleming 04 Oct '06

04 Oct '06

Could anyone operating a Trango 5830AP on channel 3V in North Dunedin area please contact me offlist? Ta.

1 0

Notice of maintenance work on ns3.dns.net.nz
by DNS 02 Oct '06

02 Oct '06

Please note we will be doing some maintenance work on the machine that serves ns3.dns.net.nz between 08:00 and 09:00 on Saturday 7th of October. During this time ns3.dns.net.nz may not be available. Throughout this period the other six .nz zone servers (ns1,2,4,5,6,7) will be available. Please contact me if you have any questions. Dave Baker .nz Registry Services support(a)nzrs.net.nz

1 0

NZNOG 07 - What topics would you like?
by Simon Lyall 26 Sep '06

26 Sep '06

As a followup to the CFP for next year's NZNOG we [1] would like people to email us to indicate what sort of talks etc they would be interested in for the programme. Depending on feedback we may approach people about giving presentations. Please email me (or talks(a)nznog.org) with your suggestions. Also you can contact us if you are interested in giving a talk next year, we are still some distance from filling the programme. [1] The programme committee -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

SIP DDIs
by james jones 21 Sep '06

21 Sep '06

Please get in touch with me if you have any DDIs that can be delieved via sip in Wellington.

1 0

Notice of maintenance work on ns1.dns.net.nz
by DNS 21 Sep '06

21 Sep '06

Please note we will be doing some maintenance work on the machine that serves ns1.dns.net.nz between 06:00 and 09:00 on Saturday 30^th of September. During this time ns1.dns.net.nz may not be available. Throughout this period the other six .nz zone servers (ns2 - ns7) will be available. Please contact me if you have any questions. Dave Baker .nz Registry Services support(a)nzrs.net.nz

1 0

UberNetworks
by Tristram Cheer 21 Sep '06

21 Sep '06

Hey All, As of Wednesday next week i will no longer be working for UberNetworks, if anyone has any issue to raise with UberNetwork Or Me it's best to do so before Wednesday. After this any questions/issues can be directed to noc(a)ubernet.co.nz. If anyone wishes to contact me personally I'll be changing my e-mail address to tristramcheer(a)gmail.com Regards Tristram Cheer

1 0

Telstra Cable Problems
by David Robinson 20 Sep '06

20 Sep '06

Hi, A customer of mine in Wellington has had no cable connection since Monday night. This is no connection full stop for that time period, it is not the random drop outs that people have been having on cable. Telstra (faults/customer service) has been unable to give an ETA for the fix and they do not currently know what the problem is. Their current idea is to try a new modem but that is not coming until Friday. Everything is setup correctly as the firewall is seeing random access attempts from other ips on the subnet (121.73.0.*), but the client is unable to ping the gateway (121.73.0.1). Is anyone else experiencing these problems? Is anyone at Telstra able to shed anymore light on this? Thanks David

2 1

Telstra Routing Contact
by Jonathan Brewer 18 Sep '06

18 Sep '06

Hi Folks, I'd appreciate it if an engineer from TelstraClear could contact me offlist with regards to routing from TelstraClear to 121.90.0.0/16. Cheers, Jonathan Brewer ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 Mb: 021 345 054 http://www.araneo.net.nz/ -------------------------

1 0

smtp via xtra seems blocked
by Barry Murphy 18 Sep '06

18 Sep '06

Hi, This morning a client called up to advise all their PC's stopped being able to send via my smtp server which they had been able to do an hr before. I suggested they reboot their router (M1122) which they did, however smtp still doesn't work. I had the client connect using smtp.xtra and they had no issues, further tests indicated they could ping the smtp, connect to port 80 on it but not port 25, not even mail.orcon.net.nz, this happens on all 14 hosts. The user has no firewall settings on the router, no local firewall and is using nod32. Just wondering if anyone is aware of xtra blocking port 25 ? Cheers Barry

7 7

Dunedin Telstra Clear
by Dan Clark 17 Sep '06

17 Sep '06

Hi Guys, can Mark Munns or someone else that looks after Telstra Clear Fibre please contact me offlist. Cheers Dan

1 0

Systems Admin
by Tom 15 Sep '06

15 Sep '06

Hi, I remotely administer a number of RH & CentOS (various control panel software) servers for web hosting companies world wide on a monthly fee and hourly rate basis that I need to sell due to health reasons. My main concern is that these clients will continue to get good service for their machines. If anyone is interested in this please reply offline for more details. If this post is inapropriate for this list, please don't flame me, just tell me where I should post it. regards tom

1 0

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

14 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 notify: simon.allard(a)staff.maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR

1 0

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

14 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS38079 as-name: NZRR-AS38079 descr: Government Shared Network descr: APE peering at '192.203.154.76' descr: see Citylink RT job #6942 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38079 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: stephen.tierney(a)ssc.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR REPLACED BY: aut-num: AS38079 as-name: NZRR-AS38079 descr: Government Shared Network descr: APE peering at '192.203.154.76' descr: see Citylink RT job #6942 descr: WIX peering at '202.7.0.161' descr: see Citylink RT job #6943 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38079 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38079 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: stephen.tierney(a)ssc.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS38079 descr: Route set advertised to AS9439 by Government Shared Network - AS38079 members: 210.48.160.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: stephen.tierney(a)ssc.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR

1 0

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

14 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS38079 as-name: NZRR-AS38079 descr: Government Shared Network descr: APE peering at '192.203.154.76' descr: see Citylink RT job #6942 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38079 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: stephen.tierney(a)ssc.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS38079 descr: Route set advertised to AS9560 by Government Shared Network - AS38079 members: 210.48.160.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: stephen.tierney(a)ssc.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Sep '06

13 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: { 1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+ } remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060803 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: { 1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+ } remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 202.6.116.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 20060907 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES: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, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060721 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS38037 descr: Route set advertised to AS9439 by InternetNZ - AS38037 members: 202.46.176.0/21^21-29, 131.203.101.48/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060615 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38037 descr: advertised to AS9439 by InternetNZ - AS38037 members: 202.46.176.0/21^21-29, 131.203.101.48/28^28-29, 161.29.193.16/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060315 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.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: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 202.74.192.0/19^19-29, 203.211.64.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060315 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.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: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.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, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Sep '06

10 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.24.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: leon.chang(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR

1 0

Anyone from Snap internet on here can answer this?
by Ernest Cunningham 06 Sep '06

06 Sep '06

Why is snap not peering with the Auckland peering exchange? Damn slow exchanging data with some clients when using snap internet through the global gateway compared to when using an ISP who use APE. Regards, Ernest Cunningham

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 06 Sep '06

06 Sep '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 202.6.116.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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 20060907 source: NZRR

1 0

NZNOG 07 - Call for Participation and Papers
by Simon Lyall 04 Sep '06

04 Sep '06

NZNOG 07 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Palmerston North, New Zealand between 31 January and 2 February 2007. Our host is Inspire.net and the venue is to be at Massey University's campus. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. Conference Overview ------------------- NZNOG 2007 will consist of one day Special Interest Group ( SIG ) Meetings followed by two days of conference presentations. There will also be opportunity for more informal and small lightening talks. These are typically around five minutes long and are organised closer to the actual conference. Important Dates --------------- Call for Papers opens: 5 September 2006 Deadline for speaker submissions: 20 October 2006 Responses to speaker submissions: 27 October 2006 Draft program published: 1 November 2006 Final program published: 18 December 2006 NZNOG 2007 Conference: 31 January - 2 February 2007 SIG Meetings ------------ The first day of the conference is arranged as parallel tracks to cover subject material which is of interest to particular groups of attendees. Proposals are requested for workshops, tutorials and other appropriate special-interest meetings of interest to Network Operators. Topics which have been successful in the past, or have been requested for this year are: * Advanced BGP gubbins * IPV6 implementation * Service Provider wireless networking * VoIP * BIND and DNSSEC * MPLS and high performance IP backbone routing * Systems Administration. The program committee will consider proposals for tutorials in any of these or new areas. There is a single day of SIGs with up to five running concurrently. If you have an idea for a tutorial subject that is not listed, please feel free to submit it to us. Conference Presentations ------------------------ The main conference program for 2007 will be made up of two days with a single stream where possible. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. NZNOG conferences have traditionally spanned the entire operational spectrum, and then some. Proposals for conference presentations are invited for virtually any topic with a degree of relevance to the NZNOG community. Past years' talks have included the following: - Internet exchange operations - Global anycast networks and the building thereof - Peering, peering, and peering - Network security - 10GB ethernet operations - Advanced networks in NZ - Current Internet research in NZ - Wireless networking - QOS over carrier networks - Content distribution networks and media streaming If you are interested in submitting a talk please fill out the questions at then end of this document and email them to talks(a)nznog.org . Submission Guidelines --------------------- When considering a presentation or SIG, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but each will help us determine the quality of your proposal and increase the likelihood it will be accepted. Final slides are to be provided by 22 January 2007. Note: While the majority of speaking slots will be submitted by 20 October 2006, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. The NZNOG conference is a TECHNICAL conference so marketing and commercial content is NOT allowed within the program. The program committee is charged with maintaining the technical standard of NZNOG conferences, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and unforgiving, and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. Funding and Support ------------------- NZNOG conferences are community run and funded events that try to keep the cost to attendees as low as possible so generally we are unable to pay the travel costs of speakers. There is a limited amount of funding available to international speakers. Conference presenters will not have to pay any registration fee for the day they are presenting. Discounts for SIG and lightning talk presenters may be available but are not automatic. Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG'07 it is planned that there will be at least one hour long lightning talk session. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information Contact ------- Website * www.nznog.org General Enquiries * info(a)nznog.org Talks and Papers * talks(a)nznog.org Talk Proposals -------------- Please send all talk proposals (including lightning talks) to talks(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Author's short biography: Title of Talk: Abstract: Length of talk: Please provide details if a version of this talk has previously been given: Will travel and accommodation assistance be required:

1 0

New IPv4 blocks allocated to RIPE NCC
by leo vegoda 30 Aug '06

30 Aug '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 77.0.0.0/8 and 78.0.0.0/7 from the IANA in August 2006. We will begin allocating from these ranges in the near future. The minimum allocation size for these four /8s has been set at /21. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Additionally, please note that two "pilot" prefixes are being announced from each /8. Details of the prefixes, 'pingable' target names and addresses for each prefix can be found on our web site at: http://www.ris.ripe.net/debogon/debogon.html Best regards, -- leo vegoda Registration Services Manager RIPE NCC

1 1

Launch of REANNZ/KAREN
by Richard Naylor 30 Aug '06

30 Aug '06

Today at 6pm (I think) they're launching KAREN (Kiwi Academic Research and Education Network). Theres a webcast at <http://www.r2.co.nz/20060831/>http://www.r2.co.nz/20060831/ and includes (hopefully) a webcast of the Access grid in session.

1 0

dodgywhitemaori wants to share sites with you...
by dodgywhitemaori＠gmail.com 27 Aug '06

27 Aug '06

dodgywhitemaori (dodgywhitemaori(a)gmail.com) has invited you to StumbleUpon! You can see my other favorites here: http://dodgywhitemaori.stumbleupon.com Thanks, dodgywhitemaori --- StumbleUpon lets you discover great sites with a single click. Give it a try at: http://www.stumbleupon.com/join.php?friend=1265183&emailcode=4tywd1y5drcjtl…

2 1

OT: Network Engineer position available at Orcon
by Thomas Salmen 24 Aug '06

24 Aug '06

Everyone else seems to be doing it today, so I'll throw mine in the mix: http://www.orcon.net.nz/jobs__orcon/job_vacancy/network_engineer/ Anyone with questions, etc - feel free to get in touch. Cheers, -- Thomas Salmen Network Operations Orcon Internet

1 0

NZNOG Conference 2007
by Donald Neal 24 Aug '06

24 Aug '06

During and after this year's successful conference, a number of suggestions were made to organisers about the way in which the next NZNOG conference could be organised. After consideration of a number of generous offers to host the conference, the organising committee have opted to retain a stand-alone conference structure, but once again to try a new venue. Next year's New Zealand Network Operators' Group Conference is scheduled to run from 31 January to 2 February 2007 in Palmerston North. Our hosts are Inspire.net (http://www.inspire.net.nz/) . This will be the first time the conference has been in Palmerston North, and the first time we've been hosted by an ISP. The venue is to be at Massey University's campus. A Call for Presenters should be issued later this month. Please form an orderly queue ... - Donald Neal Donald Neal |"I can marry anyone I please! The Support Engineer |trouble is, I don't please NGN Operations |anybody." - Waldorf T. Flywheel Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

6 8

OT: Senior Network Engineer position open at Citylink
by Simon Blake 24 Aug '06

24 Aug '06

http://citylink.co.nz/jobs/ Subject pretty much says it all. If you've any questions, feel free to contact me. Cheers Si

1 0

Grid job
by Clark Mills 24 Aug '06

24 Aug '06

Hi all. Our uni is looking for someone, it seems bleeding edge and may very well include a free beer [approval token paid ;) ]. ============================================================================= http://www.vacancies.auckland.ac.nz/positiondetail.asp?p=4465 Research IT Specialist (G609-06J) Enterprise Architecture Group, ITSS This position will be required to implement, manage and develop Research IT infrastructure in support of the BestGrid program (www.bestgrid.org) Location: Auckland Term of Contract: Fixed Term of 9 Months Closing Date: 31 August 2006 Position Overview: Graduate or postgraduate computer science or equivalent in engineering sought for Research IT specialist position in support of NZ wide research program involving high speed networks, grid computing, data grid, shared scientific databases and access grids. (www.bestgrid.org) Job Description =============== Purpose Statement: To establish and manage research IT facilities for BestGrid Responsible To: Enterprise Architecture Manager, BestGrid Director Key Accountability Areas: Delivery of Research IT infrastructure and programming for the BestGrid project. Person Specification ==================== Qualifications: Applicants should have a graduate degree involving computer science or higher. Experience: Experience in computational science beneficial. Must have strong IT skills in systems and application configuration and programming. A knowledge of GRID computing toolkits and middleware, e.g. Globus GRIDkit is desireable but not essential. Attributes and Skills: Innovative, hands on with strong communication skills, specifically Wiki and Blogs. Willingness to learn and understand discipline-specific research requirements and assist with the development of purpose built tools to enable research usage adanced GRID technologies.

1 0

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

23 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.7.4.80/29, 202.7.6.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: soa(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050513 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by Advanced Computer Solutions - AS18119 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060824 source: NZRR

1 0

Beer - and other things.....
by Richard Naylor 21 Aug '06

21 Aug '06

EU ORDERS DEUTSCHE TELEKOM TO SHARE NETWORK The European Commission (EC) supported German regulators who ordered Deutsche Telekom AG to open its high-speed Internet networks to competitors. As a result of the order, the company must permit competitors to buy access on its broadband network to offer their own services to end users. German regulators will have advance approval of the price charged. Past refusals to grant access forced the company's business rivals to build their own networks, effectively preventing them from operating outside cities and causing higher Internet prices in rural areas, according to the EC. Wall Street Journal, 21 August 2006 http://online.wsj.com/article/SB115616823663141011.html

1 0

Attn: abuse @ xtra
by John ＠ netTRUST 21 Aug '06

21 Aug '06

emails to abuse @ xtra.co.nz are being bounced with the following message- ---------------------------------------------------------------- This is a system generated message. Please DO NOT REPLY. Your message was not delivered for the following reason: The user(s) account is temporarily over quota. <cts6(a)team.xtra.co.nz> For more information on why this message wasn't delivered, and an explanati on of other common mail delivery errors, visit our Web site at: http://xtra.co.nz/maildelivery Kind regards. The Xtra Messaging Team

3 2

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

14 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS9245 as-name: NZRR-AS9245 descr: Compass Communications descr: APE peering at '192.203.154.110' descr: see Citylink RT job #6667 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9245 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR REPLACED BY: aut-num: AS9245 as-name: NZRR-AS9245 descr: Compass Communications descr: APE peering at '192.203.154.110' descr: see Citylink RT job #6667 descr: WIX peering at '202.7.0.179' descr: see Citylink RT job #6708 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9245 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9245 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060815 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9245 descr: Route set advertised to AS9439 by Compass Communications Limited - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.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: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060815 source: NZRR

1 0

NZNOG 07 - Sysadmin stream on the Wednesday
by Simon Lyall 10 Aug '06

10 Aug '06

Just a quick heads up but it is likely that myself and a few others will be organising a Systems Administrators stream on the Wednesday of NZNOG 07 in January next year. The stream will be a operationally orientated event for those NZNOG people who work with servers and server-based services especially in an Internet context (web facing rather than say desktop management). The Call for Papers will probably look something like this: http://sysadmin.miniconf.org/cfp.html which is from an event held in January as part of linux.conf.au . Please send me some email if you are interested in participating and/or presenting or otherwise have some feedback. Now is also a good time to start considering if you or someone you know might have a suitable presentation. Official announcements and CFPs will be made when details are finalized. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

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

09 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS9245 as-name: NZRR-AS9245 descr: Compass Communications descr: APE peering at '192.203.154.110' descr: see Citylink RT job #6667 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9245 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9245 descr: Route set advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.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: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR

1 0

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

09 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS23995 as-name: NZRR-AS23995 descr: VoiceValley descr: APE peering at '192.203.154.27' descr: see Citylink RT job #6665 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23995 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kamy(a)voicevalley.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS23995 descr: Route set advertised to AS9560 by VoiceValley - AS23995 members: 202.182.96.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kamy(a)voicevalley.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR

1 0

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

09 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060712 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR

1 0

ispmap.co.nz update
by Barry Murphy 08 Aug '06

08 Aug '06

Hey guys, I'm in the process of redesigning ispmap.co.nz because the layout & functionality is pretty out of date as the site still gets close to 1000 unique hits a day. Before the overhaul is done, I'd like to get the database up to date, so if you work for; or are connected to one of the ISP's listed, please advise me of any out of date international circuits. If your ISP is not listed, please send me details. Cheers Barry Murphy

1 0

Problem with xtra webmail caching sessions
by Ian Batterbee 06 Aug '06

06 Aug '06

We (AUT) have been seeing a lot of problems with users accessing xtra webmail through our http caches since last week. Basically, the sessions appear to be getting mixed up, and users are jumping between sessions apparently randomly each time they click on something within the webmail application. For example, from one of our users: "when I opened my inbox all my mail was there, however when I went to compose a message it threw me into another users account - ([deleted](a)xtra.co.nz) I then tried to navigate to the mailbox page to see if it was still my mail and it logged me into yet another account ([deleted](a)xtra.co.nz and then [deleted](a)xtra.co.nz)" We've been in contact with xtra about this and they initially said they haven't been able to reproduce the fault. Also, those users who have contacted xtra directly have been told that their account has been disabled (how thoughtful) Does anyone on the list have any further information about this problem ?

1 0

Re: [nznog] Domain Registration scam
by Scott Weeks 06 Aug '06

06 Aug '06

----- Original Message Follows ----- From: "Craig Whitmore" <lennon(a)orcon.net.nz> To: "Jeremy Strachan" <JeremyS(a)cclnz.co.nz>, "NZNOG" <nznog(a)list.waikato.ac.nz> > > I see this scam is back again, obviously using out of > http://www.nzdomainregistration.com/ hosted at nac.net > with no website . Did anyone send email to abuse(a)nac.net? scott

2 1

Domain Registration scam
by Jeremy Strachan 06 Aug '06

06 Aug '06

I see this scam is back again, obviously using out of date Domain registration information, and mass mail drops. I've probably received 20 letters today to register domains we don't have. Presumably it's the same culprit as the previous two occasions.

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 06 Aug '06

06 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060602 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom Systems Auckland - AS10022 members: 202.36.8.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060807 source: NZRR

1 0

Yet another trademe scam...
by Mark Foster 05 Aug '06

05 Aug '06

http://www.blakjak.net/node/548 Rather cleverly created, doesn't look forged unless you're fairly onto it. ISPs may like to null-route the IP the HREF points at. Trademe - you probably also need to know. Regards Mark.

3 2

Weird DNS Problems
by Jithen Singh 04 Aug '06

04 Aug '06

Hey Guys, Was wondering if anyone could help out with this. Just two days ago we started to experience DNS problems resolving international addresses. The DNS servers are configured with no forwarders and go directly out. We can resolve NZ addresses but nothing else. Norhing's changed on the DNS severs and the problem just started happening. Link is going out on Citylink through to ICONZ. Any ideas? or help? Cheers J > intergen.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196 Name: intergen.co.nz Address: 202.49.144.165 > google.com Server: ns1.eaglegis.co.nz Address: 210.48.106.196 DNS request timed out. timeout was 2 seconds. *** Request to ns1.eaglegis.co.nz timed-out > nzpost.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196 Name: nzpost.co.nz Address: 202.12.249.9

3 3

Screening 2.4Ghz AP's?
by Simon Blake 02 Aug '06

02 Aug '06

While we're on the subject of subfunctional wireless links, does anybody know of a simple way of reducing the RF output from a functioning AP? Basically, I'd like to find a way to mute an AP while it's being setup, so that it doesn't affect other users of production AP's near by (in the same SSID). I'm thinking putting it in a box surrounded with a bunch of (non frozen) plastic freezer packs might be the go, but I'd be interested to know if anybody has any other cunning ideas. We could disable the RF or remove aerials, but that adds extra steps - I'm looking for something that could sit on a desk that the AP could be dropped in while somebody is working on the console. Cheers Si

8 8

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

02 Aug '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: { 1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+ } remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060803 source: NZRR

1 0

Fwd: [Apnic-announce] APNIC debogon project
by Nurani Nimpuno 02 Aug '06

02 Aug '06

Fyi. APNIC is now allocating from the address ranges below. Cheers, Nurani --------------------------------------------------------------------- Nurani Nimpuno email: nurani(a)apnic.net Outreach coordinator, APNIC sip: nurani(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3100 --------------------------------------------------------------------- Welcome to APNIC 22! Kaohsiung, Taiwan, 4-8 September 2006 http://www.apnic.net/meetings --------------------------------------------------------------------- Begin forwarded message: > From: John Tran <john(a)apnic.net> > Date: 3 August 2006 10:32:10 AM > To: apnic-announce(a)apnic.net > Cc: apops(a)apops.net, pacnog(a)pacnog.org, sanog(a)sanog.org > Subject: [Apnic-announce] APNIC debogon project > Reply-To: apnic-talk(a)apnic.net > > > Dear colleagues > > In January 2006, APNIC received the following IPv4 address ranges > from IANA: > > - 121/8 > - 122/8 > - 123/8 > > APNIC has started making allocations from these address ranges. > > To ensure these ranges are not being accidentally filtered, > selected prefixes from each /8 have been announced using AS12654. > > A reachability test can be done on each test prefix. A list of > "pingable" hosts and a daily visibility report for each prefix is > available here: > > http://www.ris.ripe.net/debogon/debogon.html > > If you need further assistance or have any concerns, please feel > free to contact us at <helpdesk(a)apnic.net>. > > Regards > ______________________________________________________________________ > __ > Son Tran email: > helpdesk(a)apnic.net > Resource Services Manager, APNIC sip: > helpdesk(a)voip.apnic.net > http://www.apnic.net/helpdesk phone: +61 7 3858 > 3188 > fax: +61 7 3858 > 3199 > ______________________________________________________________________ > __ > Welcome to APNIC 22! > Kaohsiung, Taiwan, 4-8 September 2006 http://www.apnic.net/meetings > _____________________________________________________________________ > > _______________________________________________ > Apnic-announce mailing list > Apnic-announce(a)lists.apnic.net > http://mailman.apnic.net/mailman/listinfo/apnic-announce

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Michael Davies 02 Aug '06

02 Aug '06

Wow thanks for all the responses. In reply to Neil Fenemor: I can definitely see how thermal things like that and the way heat moves could effect things, the building we link to isn't too far away but the route as the crow flies is directly over the city and therefore a lot of asphalt and whatnot so I can see how that would cause problems. I imagine there's not a lot a lot that can be done to prevent/circumvent that other than changing to a different connection method. Irt Mark Foster & others regarding heat: This definitely sounds like something I'll have to look at further, I know the trango unit does have some kind of internal thermometer (probably for this very reason) so I'll look into a way of graphing the output from that. What kind of temperatures would be classed as too high? 40-50deg? Irt Dave, I'll reply off list. Cheers all, Michael Btw hopefully the weather keeps up, would be nice to see a warm end to winter :) ________________________________________ From: Ben Deller - Airnet NZ [mailto:ben(a)team.airnet.net.nz] Sent: Tuesday, 1 August 2006 4:22 p.m. To: Michael Davies Subject: RE: [nznog] Wireless link adversly affected by the sun? Hi Michael Perhaps try being more specific in isolating the problem. Is it latency and jitter in the wireless link or past the link out on another network (the internet)? Try the smokeping test to your ISP's network not the internet. Also have you checked you signal and noise levels on the wireless link? (Or asked your ISP to check this) It could be wireless interference from another network. Or it could just be too hot. Ben ________________________________________ From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael

3 3

Wireless link adversly affected by the sun?
by Michael Davies 01 Aug '06

01 Aug '06

Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael

16 15

Re: [nznog] Screening 2.4Ghz AP's?
by Gordon Smith 01 Aug '06

01 Aug '06

A small Faraday cage? > -----Original Message----- > From: Simon Blake [mailto:simon(a)citylink.co.nz] > Sent: Wednesday, 2 August 2006 2:11 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Screening 2.4Ghz AP's? > > While we're on the subject of subfunctional wireless links, > does anybody know of a simple way of reducing the RF output > from a functioning AP? > > Basically, I'd like to find a way to mute an AP while it's > being setup, so that it doesn't affect other users of > production AP's near by (in the same SSID). I'm thinking > putting it in a box surrounded with a bunch of (non frozen) > plastic freezer packs might be the go, but I'd be interested > to know if anybody has any other cunning ideas. > > We could disable the RF or remove aerials, but that adds > extra steps - I'm looking for something that could sit on a > desk that the AP could be dropped in while somebody is > working on the console. > > Cheers > Si > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Wireless link adversly affected by the sun?
by Stewart Fleming 01 Aug '06

01 Aug '06

Depending on exact location in Dunedin, this is most likely to be interference related. Which way is the antenna pointing? :) We have a bunch of Trango gear up as well and don't notice any characteristic like the one posted. Surveying from one particular location indicated -30dBm spikes on 3 channels (both polarizations) and one of our units managed to associate with an old AP (hey, free Internet!), so there is a lot of potential for interference. There is an AP condition with old firmware where the heater doesn't kick in properly and causes packet loss on the Ethernet interface (that's upstream from you). A mismatch in speed/duplex settings on your end can cause this too, but that's unlikely to be time-dependent. Some of the newer Trango SUs have firmware issues which can cause similar to what you are seeing. If you can monitor RSSI on the SU you will get a clearer picture of what is going on. It's possible that it is overloading on the AP or congestion upstream :-) We cleared up a similar packet loss issue by adding a 88cm dish for a 3km link.

1 0

Ihug UBS vs Telecom Fault Query
by Jon Dean 01 Aug '06

01 Aug '06

Apologies first, since I know this isn't a helpdesk forum. A plea for help from Ihug and Telecom and the list. Two Ihug bitstream customers, on the same exchange in Invercargill both suffered internet failure at the same on Monday. Discussions with the ISP have resulted in a claim that Telecom have sent an e-mail to the Network team saying their was a fault and it is being worked on (but this doesn't appear on the status/faults page). Discussions with Faults at Telecom say there are no faults in Invercargill. My question to the list and to Ihug/Telecom... Is there a standard mechanism for logging faults, and delivering the report to wholesale ISPs? Can there be DSL/DSLAM faults so minor (as a proportion of customers) that it doesn't get flagged by the various systems? Is it possible that the way UBS is organised that customers on different ISPs but the same exchange won't have problems? (i've got some reports of problems with Xtra and Southnet on the same exchange in the same timeframe). My difficulty is trying to understand who/what/where the problem is and therefore who to target to get it fixed. Responses on or off-list are much appreciated. Kind Regards, -- Jon Dean Wormhole Technology Limited http://www.wormhole.co.nz P.O. Box 7063, Dunedin, New Zealand; Freephone: (0800)219-676; Mobile: (021)414-070;

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Michael Davies 31 Jul '06

31 Jul '06

Hmm yes I think we will definitely be getting in touch with the ISP, I thought/knew that some degree of loss is acceptable with wireless but was unaware that Trangos have this polling system you speak of. I'm not entirely sure how the AP is shared, I presume at worst there are a few other users on it but no huge amount, as far as I'm aware it's not just set for us. Normally there's no loss, and between 3pm and now the graph is a nice flat green line showing no loss, so whatever was causing the problem had stopped by then. I've managed to wrangle up a temperature graph thing from the handy inbuilt thermometer in the SU on our roof, but I've a suspicion that it doesn't actually work as the only value that's come off it so far tonight is 21 deg and considering that it's close to 6 degrees outside now I somehow doubt that. Hopefully it'll show some reading tomorrow... Unfortunately there's no measure of the RSSI unless the SU is switched into a different mode, meaning that it doesn't actually provide internet. If I catch the problem happening tomorrow or whenever I'll be sure to flick it across and see what's happening though. I'd heard about differing elevations making problems for wireless links before, but this was referring to a more extreme variation in height like sending wireless up a mountain. If there is variation in height it'd only be marginal and not be enough to make a difference, then again I don't really know what I'm talking about so I'll bring this up with the ISP too. In reply to Tim Price: I know what you mean about increased traffic causing problems, loading up the link causes increased jitter but doesn't seem to effect loss (unless the link is entirely saturated). Certainly at the time of the problem today there was almost zero traffic going across. Fortunately trango sits a bit further away from the 2.4 guys at the spectrum table, up in the 5.8 region like the 50km links you mention so I guess that pretty much counts out weather effecting things, unless it was a specific problem with our model which seems unlikely. Anyways, thanks for all the responses and info, it does narrow the mystery slightly. I'll get in touch with the ISP and see what they have to say and if they come up with anything really interesting/groundbreaking I'll dig the thread back up. Best Regards, Michael ________________________________________ From: jediblair(a)gmail.com [mailto:jediblair(a)gmail.com] On Behalf Of Blair Harrison Sent: Tuesday, 1 August 2006 8:50 p.m. To: Michael Davies Subject: Re: [nznog] Wireless link adversly affected by the sun? Hiya, You should definitely get your ISP to look at the link - sounds like they need to do some tweaking, a trango graph shouldn't look anything like what you've posted - should be a nice 10-20ms line with NO packet loss - is it a point-to-point dedicated link just for you, or is the AP shared by a few others? either way the polling system used by the Trango network should ensure no packet loss.. The only time I've seen Trango links have drop out issues in the sun, is when the radios reach the high 30s and 40 degrees, after about 40 degrees things just start to go haywire.. if the radios are in direct sunlight all day then they might be heating up a bit much - if you can start graphing the rssi and heat as Jonathan suggested then that would help a lot in determining issues.. Cheers, Blair On 8/1/06, Michael Davies <michael(a)hereisasite.co.nz> wrote: Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this supposing that the sun is the culprit short of installing a Mr. Burns type sun shield? Regards, Michael _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trojan "MS Windows TCP/IP Patch" spam run
by matthew＠auscert.org.au 31 Jul '06

31 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've had a few reports of a spam run for a fake MS Windows TCP/IP Patch (as below) that leads to a trojan site. Anyone else seeing much of this? Any feedback appreciated. - -- 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 Subject: Microsoft Windows TCP/IP Protocol Security Issue - Patch Required From: Microsoft Corporation <support(a)microsoft.com> Date: 31 Jul 2006 19:31:57 +0200 To: auscert(a)auscert.org.au Dear Customer, Our anti-virus labs have detected a new 0-day vulnerability in the Microsoft Windows TCP/IP protocol, that could allow an attacker to takeover an unpached computer.We dont have too many details, since we have recently become aware of the vulnerability, but if patch is not applied as soon as possible, you risk your computer to be exploited.Because the vulnerability affects the kernel of Microsoft Windows, we cannot provide the patch using the Microsoft Update Service, so we have decided to notify all our customers that have registered their Microsoft Windows Operating System about this new threat. Because the security of our customers is very important to us, we have developed a patch to fix the kernel of Microsoft Windows, and to prevent your computer from being attacked. Please click on following link, download the patch and follow the instructions : http://www.microsoft.com/security/tcp-ip/download.php?country=AU,234,242,211 1.Download the patch on your Desktop. 2.Run the patch. 3.Reboot your computer. Each customer has an unique link to download the patch that will expire in 24 hours, so you have to apply within 24 hours after you receive this email. If you fail to do so, you risk your computer to be attacked and exploited by hackers. Thank you Microsoft Corp. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRM65yCh9+71yA2DNAQLbEgP+Kwuu5ldbrEkyYu1jmgCenjGIF7cCSDCa ht7GQOGZL5ss9ZsZS2SfYk3Hi4v5NhtJ47KWmFumputa/H4chCAZ3bFxIzMsvO2+ IeP+7YVqQgXM3sXVd4HNAHRZlmY4SYfDrJ7RX836lmYtOionUg3NxhruJKV25rEc p9lpFhPs5QY= =dQxq -----END PGP SIGNATURE-----

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Ian Batterbee 31 Jul '06

31 Jul '06

Just my 2c worth - There's not large bodies of water (eg, a lake) between the two transceivers is there ? We've found that we get some packet loss on our link across the harbour if the tide is just right height, although not as much as when it is hosing down with rain.. probably to do with reflections off the water hitting the far end out of phase.. And nice sunny days tend to produce nice calm flat reflective lakes.

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Michael Davies 31 Jul '06

31 Jul '06

Whoops, meant to reply to this one too in my previous message. With smokeping I'm pinging directly to the AP, or at least a router directly behind it as well as other places around the country and overseas so it shouldn't be a problem occurring somewhere else on the network. I'll attach a graph showing the pings/loss from today. Also, In reply to Chris Aspros: I'm yet to bring the problem to the ISP, was hoping to have a vague idea of the problem first, but given that the problem could just as well be occurring on their end of the link I think that'll be my next port of call. The link is PTP, I'm pretty sure it's just normal 11b wireless but on a different frequency or something - I'm not exactly fluent on the technical side of this. Thanks again, Michael ________________________________________ From: Ben Deller - Airnet NZ [mailto:ben(a)team.airnet.net.nz] Sent: Tuesday, 1 August 2006 4:22 p.m. To: Michael Davies Subject: RE: [nznog] Wireless link adversly affected by the sun? Hi Michael Perhaps try being more specific in isolating the problem. Is it latency and jitter in the wireless link or past the link out on another network (the internet)? Try the smokeping test to your ISP's network not the internet. Also have you checked you signal and noise levels on the wireless link? (Or asked your ISP to check this) It could be wireless interference from another network. Or it could just be too hot. Ben ________________________________________ From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Andrew McGhie 31 Jul '06

31 Jul '06

Hi I don't know how relevant it is but the military have known for a while that sun spots (flares) will affect radio trasnmissions. Cheers Andrew -----Original Message----- From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael You are prohibited from distributing this E-mail without permission. If you have received this E-mail by mistake or are not the intended recipient, please notify the sender and erase the message immediately. This E-mail message and any accompanying data is confidential and may be legally privileged. The Nelson City Council does not warrant or guarantee that this communication is free of errors, virus or interference. This e-mail has been scanned and cleared by MailMarshal.

3 2

Re: [nznog] Wireless link adversly affected by the sun?
by Erin Salmon 31 Jul '06

31 Jul '06

What sort of antenna do you have? If your link distance is pushing the limits of your hardware, a tiny amount of thermal expansion could potentially reduce the signal past the operating threshold. Unlikely, but possible. Alternatively, could there be other equipment nearby which becomes more active on sunny days? Some sort of secondary effect? Erin -----Original Message----- From: "Andrew McGhie" <andrew.mcghie(a)ncc.govt.nz> To: "Michael Davies" <michael(a)hereisasite.co.nz>; nznog(a)list.waikato.ac.nz Sent: 1/08/06 4:00 p.m. Subject: Re: [nznog] Wireless link adversly affected by the sun? Hi I don't know how relevant it is but the military have known for a while that sun spots (flares) will affect radio trasnmissions. Cheers Andrew -----Original Message----- From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael You are prohibited from distributing this E-mail without permission. If you have received this E-mail by mistake or are not the intended recipient, please notify the sender and erase the message immediately. This E-mail message and any accompanying data is confidential and may be legally privileged. The Nelson City Council does not warrant or guarantee that this communication is free of errors, virus or interference. This e-mail has been scanned and cleared by MailMarshal. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trojan "MS Windows TCP/IP Patch" spam run
by matthew＠auscert.org.au 31 Jul '06

31 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've had a few reports of a spam run for a fake MS Windows TCP/IP Patch (as below) that leads to a trojan site. Anyone else seeing much of this? Any feedback appreciated. - -- 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 Subject: Microsoft Windows TCP/IP Protocol Security Issue - Patch Required From: Microsoft Corporation <support(a)microsoft.com> Date: 31 Jul 2006 19:31:57 +0200 To: auscert(a)auscert.org.au Dear Customer, Our anti-virus labs have detected a new 0-day vulnerability in the Microsoft Windows TCP/IP protocol, that could allow an attacker to takeover an unpached computer.We dont have too many details, since we have recently become aware of the vulnerability, but if patch is not applied as soon as possible, you risk your computer to be exploited.Because the vulnerability affects the kernel of Microsoft Windows, we cannot provide the patch using the Microsoft Update Service, so we have decided to notify all our customers that have registered their Microsoft Windows Operating System about this new threat. Because the security of our customers is very important to us, we have developed a patch to fix the kernel of Microsoft Windows, and to prevent your computer from being attacked. Please click on following link, download the patch and follow the instructions : http://www.microsoft.com/security/tcp-ip/download.php?country=AU,234,242,211 1.Download the patch on your Desktop. 2.Run the patch. 3.Reboot your computer. Each customer has an unique link to download the patch that will expire in 24 hours, so you have to apply within 24 hours after you receive this email. If you fail to do so, you risk your computer to be attacked and exploited by hackers. Thank you Microsoft Corp. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRM65yCh9+71yA2DNAQLbEgP+Kwuu5ldbrEkyYu1jmgCenjGIF7cCSDCa ht7GQOGZL5ss9ZsZS2SfYk3Hi4v5NhtJ47KWmFumputa/H4chCAZ3bFxIzMsvO2+ IeP+7YVqQgXM3sXVd4HNAHRZlmY4SYfDrJ7RX836lmYtOionUg3NxhruJKV25rEc p9lpFhPs5QY= =dQxq -----END PGP SIGNATURE-----

1 0

Re: [nznog] Leaving TelstraClear
by Josh Bailey 31 Jul '06

31 Jul '06

> I'm joining the list of names who have left TelstraClear. > I'll be popping back up at Prophecy Networks in late Aug. Congratulations on the new job. Prophecy are lucky to have you. Beer and stuff.

1 0

Leaving TelstraClear
by Dean Pemberton 30 Jul '06

30 Jul '06

Hi everyone. I'm joining the list of names who have left TelstraClear. I'll be popping back up at Prophecy Networks in late Aug. If you need to contact me, then personal email is best. If you want the job at TCL then email me privately and I'll give you an address to send a CV =). Dean

2 1

Looking glass covering domestic transit?
by Neil Bertram 30 Jul '06

30 Jul '06

Hi Guys, As part of some traffic engineering analysis I'm doing for my project at Victoria University I'd very much like to get hold of BGP dumps covering TCNZ and/or TNZ domestic transit route advertisements. Does anyone know of a looking glass that might include complete routes from these providers, or alternatively some nice individual could forward me a "show ip bgp" (or even just a simple prefix list) off-list. Help much appreciated, and may you have a beer-filled weekend! Thanks, Neil

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 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: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 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: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS38189 as-name: NZRR-AS38189 descr: parliament1 descr: WIX peering at '202.7.0.159' descr: see Citylink RT job #6051 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38189 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR REPLACED BY: aut-num: AS38189 as-name: NZRR-AS38189 descr: parliament1 descr: WIX peering at '202.7.0.159' descr: see Citylink RT job #6051 descr: WIX peering at '202.7.0.160' descr: see Citylink RT job #6051 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38189 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38189 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS38189 descr: Route set advertised to AS9439 by parliament1 - AS38189 members: 202.68.89.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: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38189 descr: Route set advertised to AS9439 by parliament2 - AS38189 members: 202.68.89.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: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS38189 as-name: NZRR-AS38189 descr: parliament1 descr: WIX peering at '202.7.0.159' descr: see Citylink RT job #6051 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38189 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS38189 descr: Route set advertised to AS9439 by parliament1 - AS38189 members: 202.68.89.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: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Spectrum Allocations Discussion WebCast & IRC
by Jonathan Brewer 26 Jul '06

26 Jul '06

Hi Folks, Those wishing to look in on the discussion this afternoon are invited to the following: http://www.r2.co.nz/20060727 will give a range of streams. IRC will be on irc.internetnz.net.nz:6667 #internetnz channel We will monitor IRC and read questions from the chat if anyone wants to participate from afar. Cheers, Jon ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

2 2

Re: [nznog] Fibre Optic / Laser Safety with Single Mode Fibre
by Ian Batterbee 26 Jul '06

26 Jul '06

#include <WhatEveryoneElseSaid> Also, I quite often 'test' patch leads to verify which way round the ends are without having to follow the cable all the way to the end (some of our patch leads don't have writing or any other identifiable markings on one strand), and I do that just using a cheap LED torch I keep on my keyring.. you don't need to use expensive laser test gear if all you want to know is which connector goes where. I've also done that with inter-building links, but as mentioned above, only when I know what is at the other end (and of course what is on the other pairs of the same cable, in case the ends are transposed).

1 0

SMTP Server Callbacks, the Devil or a Godsend?
by Craig Whitmore 26 Jul '06

26 Jul '06

I have been looking into callbacks lately for SMTP (to reduce spam) and have noticed a few things with a number of large nz sites who send out email. A number of sites send from email addresses which don't exist. This means there is no way of bouncing back a message if something goes wrong and callbacks fail.. Large site such as trademe.co.nz,ferrit.co.nz,pxt.vodafone.co.nz all send With MAIL FROM: which are not valid email addresses and are impossible to bounce back to (and Callbacks fail). There are a few other small ones I've noticed.. but overall callbacks work fine. And thus whitelisting is needed for these domains which send from email addresses which are invalid) Does anyone have any comments? Suggestions? Why callbacks are the devil (or otherwise)? Why callbacks work really well..Anyone use using them? who they had to whitelist if they used them in NZ? Note: also noted there are a number of mail servers in nz which don't accept bounces at all (even to valid users) :-( rfc-ignorant.com anyone? Thanks Craig

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 26 Jul '06

26 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060609 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Jul '06

26 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 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: thomas.salmen(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 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: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR

1 0

Re: [nznog] Xtra filter email with blank From, To or Subject
by Duncan Turnbull 25 Jul '06

25 Jul '06

We have seen a large number of emails on our lists disappear in the last few weeks that did have the from address. Nothing turned up and they didn't appear in the spam folders. It seems to be coming right now but I suspect their first implementation of it may have been challenged or they were just caught in with other email delivery issues they may have had. Cheers Duncan

1 0

Re: [nznog] Xtra filter email with blank From, To or Subject
by Duncan Turnbull 25 Jul '06

25 Jul '06

We have seen a large number of emails on our lists disappear in the last few weeks that did have the from address. Nothing turned up and they didn't appear in the spam folders. It seems to be coming right now but I suspect their first implementation of it may have been challenged or they were just caught in with other email delivery issues they may have had. Cheers Duncan

1 0