- NZNOG - lists.nznog.org

Webcasting Heads Up
by Richard Naylor 13 Feb '06

13 Feb '06

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

1 0

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

13 Feb '06

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

1 0

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

12 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9236 descr: advertised to AS9439 by AMP - AS9236 members: 203.118.136.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jimi.wallace(a)ampcapital.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR

1 0

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

12 Feb '06

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

1 0

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

09 Feb '06

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

1 0

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

09 Feb '06

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

1 0

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

08 Feb '06

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

1 0

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

08 Feb '06

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

1 0

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

08 Feb '06

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

1 0

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

08 Feb '06

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

1 0

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

07 Feb '06

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

1 0

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

02 Feb '06

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

1 0

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

02 Feb '06

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

1 0

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

01 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR

1 0

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

01 Feb '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR

1 0

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

31 Jan '06

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

1 0

SORBs blacklisting Paradise MTAs
by neil gardner 31 Jan '06

31 Jan '06

Hi gents (and gentesses) I reported to Paradise that Sorbs was blacklisting a particular Paradise MTA last night (details below) and their response was that sorbs refuse to whitelist them so there's nothing they can do about it... The further state that "SORBS automatically delist the servers after a 48 hour time period, and mail passing through the once affected mail server should flow as per normal." yet the information pasted below seems to indicate that the particular IP I reported has been on the list since Dec 11th 2005. They're spinning me a line right? The Sorbs record hasn't been updated since Dec 11th! *--- Info from sorbs as of 5 minutes ago *--- Address: 203.96.152.180 Record Created: Sun Dec 11 13:53:04 2005 GMT Record Updated: Sun Dec 11 13:53:04 2005 GMT Additional Information: Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by vampire.isux.com (Postfix) with ESMTP id 58986B90C; Sun, 11 Dec 2005 13:52:40 +0000 (UTC) Currently active and flagged to be published in DNS *--- end info from sorbs *--- Why would Paradise deliberately avoid resolving this issue when pointed out to them? If anyone from Paradise / Telstraclear would like to jump in and explain why your helpdesker effectively refused to do anything about the situation then I'm all ears. Yes, I did report to Paradise through the appropriate mechanism, then I replied to their automated response, then this morning I phoned to report it and had my number taken (no-one has phoned back) and a few minutes ago I received the reply to the original message saying they can't do anything. Cheers - Neil G Neil Gardner Product Manager Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

2 2

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

31 Jan '06

If it's any help - and I'd expect most people here to know this anyway - Paradise pop up on RBL's so often, I've had to add a whitelist for them in my system, or most of the people I know (who use cable) get blocked. This isn't a new thing at all. :) Cheers Nic > -----Original Message----- > From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] > Sent: Wednesday, 1 February 2006 2:12 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] SORBs blacklisting Paradise MTAs > > Hi gents (and gentesses) > > I reported to Paradise that Sorbs was blacklisting a > particular Paradise MTA last night (details below) and their > response was that sorbs refuse to whitelist them so there's > nothing they can do about it... > > The further state that "SORBS automatically delist the > servers after a 48 hour time period, and mail passing through > the once affected mail server should flow as per normal." yet > the information pasted below seems to indicate that the > particular IP I reported has been on the list since Dec 11th 2005. >

1 0

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

31 Jan '06

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

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Jan '06

30 Jan '06

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information. The most recent speakers to be confirmed are Mike Hughes, CTO of London Internet Exchange and Arron Scott of Cisco New Zealand. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 900 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

Information on Global Web Productions
by Craig Whitmore 30 Jan '06

30 Jan '06

Hi there Has anyone got any information on Global Web Productions and the NZ Commerce Comissions Involvement with them in getting them shut down in 1994 with the US CAN-SPAM? Seaching on the web and on the comcom website I cannot find any information at all what involvement they (the comcom) had or what they did or who the people in New Zealand where. Thanks Craig

4 5

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

29 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060130 source: NZRR

1 0

NZNOG06
by Andrew Thompson 29 Jan '06

29 Jan '06

Hi, I am trying to find the registration details for the conference this year but only the schedule seems to be up. I'm just after the cost so I can hit up my boss to shout me. cheers, Andrew

2 1

WIX Issues Saturday Afternoon
by Jonathan Brewer 27 Jan '06

27 Jan '06

Hi Folks, There were some issues with the WIX this afternoon, from approx 11:50 until around 15:00, affecting several connected ISPs. Could someone with an in-depth knowledge of what happened fill us in? Cheers, Jon

2 1

Strange NZ Domain Names and Contents
by Craig Whitmore 26 Jan '06

26 Jan '06

I was looking on Google this morning and came across these strange groups of .NZ domain names as below. Most of them are just recently been registered. (Maybe they are domains which have just become available from others who didn't want them and they where picked up to hopefully to get hits. The name of the sites have nothing to do with anything which is on the sites and all they do is link to lots of places and banners. I can't see anything really illegal on them (apart from linking to know spam/buy viagra etc online sites). Just a heads up for people. Does the NZ Internet Community want people registering 100's of generic .nz domain names in the future to just to get hits and advertise others? Thanks Craig http://www.globalchessenterprises.co.nz http://www.aa-auckland.org.nz www.haynesfilm.co.nz http://gt40.co.nz http://www.fastfinish.co.nz http://www.dissidentvoice.org.nz www.promocodirect.co.nz/ www.heavyloungesuite.co.nz www.farmbarn.co.nz http://www.fastaccess.co.nz/ http://www.ecmtoa.co.nz/ http://www.shaktimigrant.org.nz http://www.infobrok.co.nz

5 5

Re: [nznog] Strange NZ Domain Names and Contents
by Craig Whitmore 25 Jan '06

25 Jan '06

> > > Purchasing what are normally perscription drugs, from a website... > > If the clue phone doesnt ring for that one, no policy change will protect > these people. > > But people ARE legally selling drugs on the Net in NZ, but they are doing it legally.. You send the script to them (or get the doctor to), and they will send you the drugs in the mail. Some Legal Pharmacies: http://www.netpharmacy.co.nz/ http://www.pharmacyweb.co.nz http://www.quinspharmacy.co.nz/ Thanks Craig

5 4

Re: [nznog] Strange NZ Domain Names and Contents
by Craig Whitmore 25 Jan '06

25 Jan '06

Replying to myself but... There is even illegal porn advertised on .co.nz domain names with its registered details in the Russian Federation.(I shant say more) I guess registrars can't vet what people are using the domain names for all the time, but a few of the registrar's I've looked at T&C saying the domain names they are charging the customer for must be used for legal purposes. Thanks Craig > > Also good examples are www.pharmacycare.co.nz and > http://www.discountmeds.co.nz/. Talking for myself.

3 2

NZNOG conference
by David Robb 24 Jan '06

24 Jan '06

Is there any further information available for this? ie costs, who else is speaking? I'm going to need to make a decision very soon as to whether or not I can justify my attendance. Thanks, --David

1 0

WorldxChange Peering WIX / APE
by Term 23 Jan '06

23 Jan '06

1 0

LinuxNet / ACS peering at APE
by Lincoln Reid 23 Jan '06

23 Jan '06

Hi, LinuxNet / ACS is now peering at APE. Ideally we would like to peer with pretty much everyone. If we have an existing bilateral peering relationship with you at WIX and you have an APE presence, feel free to get in touch. I am also interested in hearing from people who want to bilaterally IPv6 peer at WIX or APE. Our details are as follows: ASN: 18119 WIX: 202.7.0.245 : 2001:7fa:3:ca07::f5 APE: 192.203.154.117 : 2001:7fa:4:c0cb::9a75 The IPv4 prefix list is at: http://www.linuxnet.co.nz/linuxnet-prefixlist.txt The IPv6 prefix list is at: http://www.linuxnet.co.nz/linuxnet-prefixlist-v6.txt Cheers, -- Lincoln Reid Systems Engineer ACS - AS18119 lincoln(a)linuxnet.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

1 0

Peering Policies
by Webmaster 20 Jan '06

20 Jan '06

I am currently working on a paper about peering in New Zealand. If you are involved with peering policy in your organisation, could you please send me offlist a copy of your company's policy (or a link to it). Many thanks, Richard >>> "Craig Humphrey" <Craig.Humphrey.Work(a)paradise.net.nz> 01/20/06 2:02 PM >>> _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

CISCO 805 Serial/Ethernet to go to a good home...
by Craig Humphrey 19 Jan '06

19 Jan '06

Hi People, I've come across an old CISCO 805 with serial and ethernet ports on the back. No power, no idea if it works. If you want/need one and are in the Auckland area, give me a yell off list, I'll only charge you a beer if it works... Later'ish Craig

2 1

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

19 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.182.192.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: noc(a)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051202 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR

1 0

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

19 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17435 descr: Route set advertised to AS9439 by WorldxChange Communications - AS17435 members: 58.28.0.0/16^16-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR

1 0

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

18 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24025 descr: Route set for Helix - AS24025 members: 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040304 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24025 descr: advertised to AS9560 by Helix - AS24025 members: 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.240.0/22 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.14.217.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.59.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- PREVIOUS OBJECT: route: 202.50.176.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040304 source: NZRR REPLACED BY: route: 202.50.176.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR

1 0

Re: [nznog] Mail issues in/out of China
by Scott Weeks 18 Jan '06

18 Jan '06

> Thanks for many replies. Guess we can add 'China' to the > keywords such as 'beer' to get everyone's attention!! Nah, Chinese beer isn't all that: http://en.wikipedia.org/wiki/Chinese_beer Further... http://www.foodconsumer.org/777/8/Formaldehyde_illegally_used_in_Chinese_be… scott :-) ----- Original Message Follows ----- From: "Gary T. Benner" <gary(a)123.co.nz> To: jabley(a)isc.org Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Mail issues in/out of China Date: Thu, 19 Jan 2006 12:02:40 +1300 > [Reply] > > HI all, > > Thanks for many replies. Guess we can add 'China' to the > keywords such as 'beer' to get everyone's attention!! > > cheers > > Gary > > At 07:21 on 19/01/2006 you wrote > >To : truman(a)suspicious.org,nznog(a)list.waikato.ac.nz > >CC : nznog(a)list.waikato.ac.nz, > >From: Joe Abley, jabley(a)isc.org > >Content Type: text/plain > >Attached: > > > > >On 17-Jan-2006, at 23:57, Truman Boyes wrote: > > > >> I have used SIP phones in China and I can tell you that > some of the >> firewalls are a lot more advanced than just > blocking applications. I >> was able to place some types > of calls via my USA DDI, while others >> were redirected > to a local chinese gateway. Essentially that means >> that > ALGs were inspecting the SIP invite messages ... quite >> > interesting ... > > >Presumably this is the difference between living in a > region where >the authorities are open about intercepting > communications, in >contrast to other places where > communications are routinely >intercepted in secret? > > > > >Joe > > > >_______________________________________________ > >NZNOG mailing list > >NZNOG(a)list.waikato.ac.nz > >http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > Ref#: 41006 > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Mail issues in/out of China
by Gary T. Benner 18 Jan '06

18 Jan '06

[Reply] HI all, Thanks for many replies. Guess we can add 'China' to the keywords such as 'beer' to get everyone's attention!! cheers Gary At 07:21 on 19/01/2006 you wrote >To : truman(a)suspicious.org,nznog(a)list.waikato.ac.nz >CC : nznog(a)list.waikato.ac.nz, >From: Joe Abley, jabley(a)isc.org >Content Type: text/plain >Attached: > > >On 17-Jan-2006, at 23:57, Truman Boyes wrote: > >> I have used SIP phones in China and I can tell you that some of the >> firewalls are a lot more advanced than just blocking applications. I >> was able to place some types of calls via my USA DDI, while others >> were redirected to a local chinese gateway. Essentially that means >> that ALGs were inspecting the SIP invite messages ... quite >> interesting ... > >Presumably this is the difference between living in a region where >the authorities are open about intercepting communications, in >contrast to other places where communications are routinely >intercepted in secret? > > >Joe > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog > Ref#: 41006

1 0

Apricot2006 Registrations
by Andy Linton 18 Jan '06

18 Jan '06

I know may of you will be at NZNOG in March but if you need more conference time then the annual Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) event is happening in Perth, Western Australia from 22nd February to 3rd March 2006. Registrations for the event are open and early bird is closing on the 14th Jan (tomorrow!). This is the first time that APRICOT will be held in Australia and I've been told they'd really love to see lots of us coming over for it! APRICOT consists of workshops, tutorials, conference, as well as the 6 monthly APNIC meeting. The APRICOT 2006 programme includes: Workshops 22 - 26 February Tutorials 27 - 28 February Conference 1 - 2 March APNIC Member Meeting 3 March Full information about APRICOT 2006 can be seen at http://www.2006.apricot.net Program information is at: http://www.apricot2006.net/index.php/fuseaction/home.program Registration information is at: http://www.2006.apricot.net/index.php/fuseaction/home.registration You are encouraged to register as soon as possible as the early bird registration discount expires on the 14th of January. If you aren't an AU or NZ citizen, visa information is at: http://www.apricot2006.net/index.php/fuseaction/home.visas You must register on-line before submitting a visa application - note that application times for visas for non-ETA countries can be quite lengthy, so please start the registration and application process as soon as you can. You can select a checkbox to request an invitation letter from us to be used for your visa application during registration if you require one, this is an automated process. Accommodation information is at: http://www.2006.apricot.net/index.php/fuseaction/home.accommodation You are encouraged to make arrangements for accommodation as soon as possible as the APRICOT discounted room block expires on the 18th of January. After this date we must release remaining rooms, you then need to compete with the general tourist public for room availability. Sponsorship opportunities still exist for interested companies. Information on Sponsorship is available online at: http://www.apricot2006.net/index.php/fuseaction/home.sponsorship

5 4

Mail issues in/out of China
by Gary T. Benner 17 Jan '06

17 Jan '06

HI all, I have a client with staff member in China who has had consistent difficulty accessing our mail server, both using pop *and* the webmail client. Yet access from within NZ has been faultless. If anyone has had experience in this area, are there issues relating to the Chinese Authorities intercepting such communications, or would it be just to do with the connection? regards Gary Benner 123 Internet Ltd

7 6

Re: [nznog] Studio Cam Update
by Webmaster 16 Jan '06

16 Jan '06

Just so that operators are kept informed, we have been running radio interviews with a strong visual component on the Matinee Idle studio cam. Yesterday was Pets, today is Tattoos. Interest in both the live audio and studio cams has been very high. cheers, Richard Hulse Radio NZ

2 1

IPv6 Connect NZ Domain Servers
by Philip D'Ath 15 Jan '06

15 Jan '06

Does anyone offer commercial hosting of NZ zone files on DNS servers that are IPv6 connected?

2 1

Studio Cam Update
by Webmaster 13 Jan '06

13 Jan '06

Operators should be aware that we are planning an on-air promotion using our studio cams next week. This is not yet confirmed, but I thought I'd give everyone plenty of warning just in case we go ahead. The studio cams operate during the Matinee Idle radio show, 12.30 pm - 5pm on weekdays. (www.radionz.co.nz/phil) The promotion is likely to cause a huge increase in the number of simultaneous viewers. To date we've have seen data rates of between 10 and 40 Mb/s during the show. More than half this data is NZ bound from the US server. The 384 kbs stream is the most popular. There was such a high demand from listeners for the higher data rates, that after the first day of the show we opened these up to customers of non-peering ISPs. regards, Richard Hulse regards, Richard

1 0

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

13 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: 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^+, 74.0.0.0/8^+, 75.0.0.0/8^+, 76.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 89.0.0.0/8^+, 90.0.0.0/8^+, 91.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^+, 121.0.0.0/8^+, 122.0.0.0/8^+, 123.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^+, 189.0.0.0/8^+, 190.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 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 source: NZRR

6 5

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

11 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64524 descr: advertised to AS9439 by Institute of Chartered Accountants of NZ - AS64524 members: 202.27.78.0/24^24-29, 202.27.79.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: nathan.cottle(a)icanz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64524 descr: advertised to AS9439 by Institute of Chartered Accountants of New Zealand - AS64524 members: 203.97.94.0/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: paul.ross(a)nzica.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060112 source: NZRR

1 0

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

11 Jan '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.20.6.0/24^24-29, 202.36.119.0/24^24-29, 202.46.190.0/24^24-29, 202.49.159.0/24^24-29, 202.78.240.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.78.240.0/21^21-29, 202.36.119.0/24^24-29, 202.46.190.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: routing(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060112 source: NZRR

1 0

IANA IPv4 allocations and bogon updates: 121/8, 122/8, and 123/8
by Rob Thomas 09 Jan '06

09 Jan '06

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those of you who receive this note in multiple forums. ] Hi, team. The numerous Team Cymru bogon projects have been updated as of 05 JAN 2006 to reflect the following IANA allocation made on 05 JAN 2006: 121/8 Jan 06 APNIC (whois.apnic.net) 122/8 Jan 06 APNIC (whois.apnic.net) 123/8 Jan 06 APNIC (whois.apnic.net) IANA allocations change over time, so please check regularly to ensure you have the latest filters if you are not using the bogon BGP feed(s). We do announce updates to the bogon projects to sundry lists, such as the bogon-announce list. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the Team Cymru master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/> A quick summary of the documents and projects that have been updated include the following: HTTP The Bogon List - <http://www.cymru.com/Documents/bogon-list.html> The Text Bogon Lists - <http://www.cymru.com/Documents/bogon-bn-nonagg.txt> - <http://www.cymru.com/Documents/bogon-bn-agg.txt> Secure BIND Template - <http://www.cymru.com/Documents/secure-bind-template.html> Secure IOS Template (Cisco) - <http://www.cymru.com/Documents/secure-ios-template.html> Secure BGP Template (Cisco) - <http://www.cymru.com/Documents/secure-bgp-template.html> Secure JUNOS Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-template.htm> Secure JUNOS BGP Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-bgp-template.htm> Ingress Prefix Filter Templates, Loose and Strict (Cisco) - <ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix- Filter-Templates/> Ingress Prefix Filter Template, Loose (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-loose.htm> Ingress Prefix Filter Template, Strict (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-strict.htm> BGP Bogon route-server for AUTOMATED updates of bogon filters - All bogon route-server peers have already received the appropriate BGP prefix updates. - <http://www.cymru.com/BGP/bogon-rs.html> RADb fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#radb> RIPE NCC fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#ripe> DNS Bogon (bogons.cymru.com) zone - <http://www.cymru.com/Bogons/index.html#dns> Monitoring Bogon prefix monitoring - <http://www.cymru.com/BGP/robbgp-bogon.html> Bogus ASN monitoring - <http://www.cymru.com/BGP/asnbogusrep.html> Please feel free to contact Team Cymru <team-cymru(a)cymru.com> with any comments, questions, or concerns. Thank you for your continued support. Thanks, Rob. - -- Rob Thomas Team Cymru http://www.cymru.com/ ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQ8MiDlkX3QAo5sgJAQEHwwP/X6Jh/sZ+j46KosfJ6H3+Wzb7sE3xXjl9 ktuNLb7Xfvo0A4PwUSv5NF5aS4Yp1C5NWZcrBDKkwIMA4WcC7DZK+qvFHeOX7EVS vzXzpw2FGCyImU1m49qNR+437vM0CNVaeFeMc+zjHnnXlsAEVVIhwQ7lz0KE+rlM G2ZKbvaQRyw= =qtQ6 -----END PGP SIGNATURE-----

1 0

ANZ website broken?
by Blair Harrison 31 Dec '05

31 Dec '05

Hmm, Maybe someone pushed a wrong button? domain_name: anz.co.nz query_status: 210 PendingRelease domain_dateregistered: 1997-03-10T00:00:00+13:00 domain_datebilleduntil: 2006-01-01T00:00:00+13:00 domain_datelastmodified: 2005-12-31T22:01:03+13:00 domain_datecancelled: 2005-12-31T22:01:03+13:00 Oops. Internet banking still available via www.anz.com/nz at least. -Blair

1 0

Re: [nznog] Studio Cam Update
by Webmaster 26 Dec '05

26 Dec '05

After receiving a number of requests from people viewing the Matinee Idle studio cams, I have opened up access to the 384k and 2M streams to all comers. This means that all NZ consumers can watch the high rate streams if they want to, regardless of whether their ISP peers or not. Non-peering ISPs may see a big increase in international bandwidth usage between 12:30 pm and 5 pm daily on weekdays until 20 Jan 2006. regards, Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Streaming Event
by Ian Cogill 22 Dec '05

22 Dec '05

Hi There We will be providing live streams of the ASB Classic and Heineken Open tennis from Jan 2 - Jan 14 To ensure all New Zealanders get the best possible service we strongly recommend peering with the R2/Citylink anycast cluster at 202.7.7.90 via WIX, APE and/or PNIX. As it is the holidays we're not exctly sure how many people will be watching coverage online, so this is just a heads up. Regards Ian Cogill Systems Engineer TVNZ Interactive ===================================================================== CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz ================================================================

1 0

Studio Cam Update
by Webmaster 22 Dec '05

22 Dec '05

The studio cams for the Matinee Idle radio show are now in operation with a jpg slide: http://www.radionz.co.nz/nr/programmes/matineeidle I have noted on the web cam page that some customers may not be able to get the high bandwidth streams due to their ISP not peering. These consumers will get a message suggesting that they use one of the lower rate streams or contact their ISP. Time for a beer now, my work is done.... regards, Richard

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Dec '05

22 Dec '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR

1 0

Re: [nznog] ipv6
by Philip D'Ath 22 Dec '05

22 Dec '05

Pretty much every Cisco DSL router supports IPv6. We just need an ISP to start selling the IPv6 transit ... -----Original Message----- From: Richard Hector [mailto:richard(a)walnut.gen.nz] Sent: Thursday, 22 December 2005 2:46 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:35 +1300, Matt Brown wrote: > With the introduction of UBS I'm hoping that it's going to become a > lot more common for ISPs to be able to offer IPv4/IPv6 circuits, even > if it is only on ad Ad-Hoc basis to the 'geeks' to start with. To offer it on UBS, wouldn't your DSL router have to support IPv6? Do any of them? I suppose you could use either a plain modem, or one of those ones that bridges PPPoA to PPPoE, but I've never tried setting one up. Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 11

SANOG VII - Mumbai, India, 16-24 January 2006
by Andy Linton 22 Dec '05

22 Dec '05

South Asian Network Operators Group (SANOG) VII 16-24 January 2006, Mumbai, India Hosted by ISPAI. SANOG VII Program Announcement SANOG VII program and agenda are now published on http://www.sanog.org/sanog7/. SANOG VII is being held by ISP Association of India (ISPAI) in Mumbai, India from 16-24 January 2006. Daniel Karrenberg, Chief Scientist, RIPE NCC and Paul Wilson, DG,APNIC will address the plenary session of SANOG VII. There will be 3 workshops, 10 tutorials, 3 BoFs and over 16 presentations during the event. APNIC will hold a special Open Policy Meeting Showcase at SANOG VII, and for the first time at SANOG, we'll have a Peering Panel and Debate. Registration Discounts available for ISPAI, APNIC, APIA members. Detailed information is available at http:/www.sanog.org/sanog7/ Program and Agenda: Three hands-on workshops: 16-20 January 2006 * ISP Routing and BGP Multihoming Workshop * IPv6 Essentials, Applications and Routing Workshop * Multicast Routing and Applications Workshop Ten Tutorials: 21-22 January 2006 * BGP and High Availability Routing Tutorial, Prasad Babu * DNS / DNSSec Deployment Tutorial, Champika Wijayatunga * IXP Construction and BGP Multihoming, Philip Smith, Gaurab Raj Upadhaya * L2VPN - Changing and Consolidating Networks - Paresh Shah, Md.Waris * Layer2 Attacks and Mitigation techniques, Yusuf Bhaiji * DDoS prevention in Service Provider Networks, Wireless Security,Pravin Mahajan * The Basics of Multicast - Marshall Eubanks, * QoS and Multicast on MPLS Networks , Rajesh Shinde * QoS on Low Bandwidth & High Delay Links, Prakash Shende Birds-of-a-Feather (Special Evening Sessions) : 21-23 January 2006 * Managed Services * Anti-SPAM Tools and Techniques * Internet Society (ISOC) BoF APNIC Special Sessions * APNIC Helpdesk sessions throughout SANOG VII * APNIC Open Policy Meeting Showcase on 24th January 2006 Two Days Conference Program : 23-24 January 2006 * Alternative architectures for Broadcast Video Distribution - Srinath Beldona, Cisco * RA-MPLS services - Kapil Kumar, Reliance * Network Infrastructure for IPTV - Saisree Subramanian, Wipro * Efficient Resource Broker Architecture to Provide Guaranteed QoS - Praveen Kumar, Anna University * Graceful Restart of Routing Protocols - Prasad Babu, Juniper * Backbone Architectures for NLD/ILD: Design; Optmization & Services - Chandan Mendiratta (Cisco) * Network Infrastructure Security in Cellular Data Networks: An Initial Investigation - Vishal Sharma (IIT-Bombay) * Traffic Engineering and Network Planning Tools for MPLS Networks - Dr. Girish P. Saraph (IIT-Bombay) * pmacct; a new player in the network management arena - Paolo Lucente (CNR-Italy) * Flow measurements from the packet-switched NREN PIONIER: technology and experience - Wiktor Procyk (Poznan S&N Center) * Interest Based Group Management Mechanisms for E-learning Design using the Peer to Peer Technologies - Surya (AIT) * Internet Routing Table Update - Philip Smith (Cisco) * INOC - DBA Update - Gaurab Raj Upadhaya ( PCH) * Data Network Management for Telecom Operators in ASIA - Sufi Faruq (AKTEL) Peering Penel and Debate * Nigel Titley, Peering Manager, FLAG Telecom * Sylvie Laperriere, Director- Peering, Teleglobe * Sharad Shangi, Net4India * Gaurab Raj Upadhaya, PCH, (moderator) Local Fellowships are still available. We expect a huge turn out from the region at this SANOG meeting owing to the popularity at previous meets. We also welcome participants from West Asia, with our established collaboration with the RIPE NCC. With more involvement of APNIC in the content of overall program, We hope you would be able to make it to this meeting. The meeting is open to everyone from the operational community, and thus anyone who wants to find out more about Internet operations in South Asia is welcome. You can register for SANOG by sending in the form available at www.sanog.org/sanog7 or using the online registration system. Registrations from inside India can be paid by DD Looking forward to seeing you there. Thanks - SANOG

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

Not being from a service provider my view is somewhat simplistic. Telecom offers a layer 2 service called UBS, which uses L2TP between their RAN and the ISP. Over this PPP runs. So I don't see any reason why an ISP couldn't offer IPv6 over UBS. -----Original Message----- > Pretty much every Cisco DSL router supports IPv6. We just need an ISP > to start selling the IPv6 transit ... The last I knew (which was admittedly many years ago) Telecom's wholesale DSL was a layer-3 service, with frames being routed through a twisty maze of RFC1918-numbered routers before they arrived at the user's ISP. If that was still the case, then surely Telecom would need to route v6 frames between the customer and the ISP for the customer to receive native v6 service? If there has been a subsequent layer-2 wholesale DSL service offered, along the lines that is done elsewhere, is there not still a requirement for Telecom to switch v6 frames from PPPoA into L2TP, or whatever framing is used to present a user's traffic to an ISP?

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

I've tried: Orcon Maxnet WorldXchange Telecom told me that are playing with it, at best, and had no plans to offer it commercially. Didn't bother trying Xtra. I tried to speak to TelstraClear about it, but couldn't really find the right people to understand what I was asking. -----Original Message----- From: Matt Brown [mailto:matt(a)mattb.net.nz] Sent: Thursday, 22 December 2005 2:35 p.m. To: Philip D'Ath Cc: Simon Lyall; nznog Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:26 +1300, Philip D'Ath wrote: > I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've > contacted is prepared to sell me one. Are you able to share who you tried to purchase one off? There seem to be three NZ providers advertising v6 prefixes at the present time: http://www.sixxs.net/tools/grh/dfp/all/?country=nz With the introduction of UBS I'm hoping that it's going to become a lot more common for ISPs to be able to offer IPv4/IPv6 circuits, even if it is only on ad Ad-Hoc basis to the 'geeks' to start with. Cheers -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've contacted is prepared to sell me one. I'm having to use 6to4 tunnelling at the moment. -----Original Message----- Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ?

3 2

Streaming Event
by Webmaster 21 Dec '05

21 Dec '05

Over the summer break we will be providing a Studio Cam for the top rating Matinee Idle radio show, hosted by Phil O'Brien. HTTP://www.radionz.co.nz/nr/programmes/matineeidle This is a first for Radio NZ and as far as I am aware a first for New Zealand Radio in general. We'll be providing video streams at 56k, 128k, 384k and 2 Mbs. Operators should be aware that the Studio Cam will be promoted extensively on air. To ensure all New Zealanders get the best possible service we strongly recommend peering with the R2/Citylink anycast cluster at 202.7.7.90 via WIX, APE and/or PNIX. The US node is intended to serve consumers outside New Zealand. Limited NZ bound bandwidth has been allocated for this event, and operators may experience an increase in help desk calls when this allowance is exceeded. regards, Richard Hulse Radio New Zealand

2 1

ipv6
by Simon Lyall 21 Dec '05

21 Dec '05

Interesting wee discussion about real world IPv6 usage on NANOG that some here might be interested in, some have said things have improved a little in the last 18 months though: http://www.merit.edu/mail.archives/nanog/msg14543.html Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ? Ob Friday Afternoon link (many will have seen before): http://www.livejournal.com/users/pjammer/153928.html -- 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

New IPv6 Address Block Allocated to the RIPE NCC
by filiz＠ripe.net 20 Dec '05

20 Dec '05

[Apologies for Duplicates] Dear Colleagues The RIPE NCC received the IPv6 address range 2A01:0000::/16 from the IANA in December 2005. 2A01:0000::/23 was allocated to the RIPE NCC in July 2005. This latest range includes that previous allocation. You may wish to adjust any filters you have in place accordingly. You can find more information about the IP space administered by the RIPE NCC on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, Filiz Yilmaz RIPE NCC

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Dec '05

18 Dec '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: Route set advertised to AS9439 by AT&T Global - AS2687 members: 152.158.254.0/24^24-29, 152.158.255.0/24^24-29, 202.14.142.0/24^24-29, 202.27.160.0/24^24-29, 202.36.68.0/24^24-29, 202.36.69.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.46.160.0/20^20-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.70.0/24^24-29, 203.163.71.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.119.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050303 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Dec '05

18 Dec '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: Route set advertised to AS9560 by AT&T - AS2687 members: 152.158.254.0/23^23-29, 203.163.70.0/23^23-29, 152.158.213.0/24^24-29, 202.14.141.0/24^24-29, 202.14.142.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.28.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.86.0/24^24-29, 202.135.112.0/24^24-29, 202.135.115.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.98.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Mark.Crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050503 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051219 source: NZRR

1 0

Update: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 17 Dec '05

17 Dec '05

The Systems Administration Miniconf which will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 We are pleased to announce that our programme is 95% finalised and is available online at: http://sysadmin.miniconf.org/program.html and more details of each presentation are on this page: http://sysadmin.miniconf.org/presentations.html Please note that for now the actual times of each presentation have not been finalized while we work with other miniconfs to avoid clashes. While we are no longer accepting full length talks we still have space for Lightning talks, please contact us if you are interested: http://sysadmin.miniconf.org/lightning.html Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Re: [nznog] NZ Security Notifications
by John Martin 16 Dec '05

16 Dec '05

Brendan Murray wrote: > > > If you think there would be some value in this, please email me. > > You can find information about the nsp-security mailing list at > https://puck.nether.net/mailman/listinfo/nsp-security) > > I believe such a closed security mailing list would have a great deal of value, not only to Universities and ISP's within New Zealand (re: aka Russell Fulton) but also to Critical Infrastructure Providers, financial services too. With a great number of sources from Phishing, Pharming attacks being reported with USA and EMEA from APAC, this could also provide an early warning system and possibly assist in shutting down such activity via the participating ISP's. However, in terms of running a script through various snort databases, the issue of privacy looms and authorisation, a better answer might be to use the New Zealand nominated CERT for such operations i.e. Centre for Critical Infrastructure Protection (CCIP) locally as a central collection point etc.. To ensure anonymity etc. It would also be good to add ISC (sans.org) logs to the collective.. With compliance issues only around the corner, New Zealand is relatively unscathed by regulatory/legislation within USA, EMEA, Australia, which statistically looks like it will take a hold within the next 1-2 years. Such a group may provide guidance to organisations, not prepared for the ongoing associated issues of compliance. John Martin Security Practice Leader IBM NZ

1 0

NZ Security Notifications
by Brendan Murray 15 Dec '05

15 Dec '05

(apologies to members of members-discuss(a)internetnz.net.nz for duplication) Yesterday the topic of AusCERT came up on nznog. Many of you probably know that InternetNZ has formed a small group to look at the need/feasibility of a NZ based CERT. It is all in early days yet, but it might be a good time to start looking at some ways of improving security awareness here. We hope to raise some ideas for discussion at the nznog conference next year, but the recent email suggests we could start on some practical matters now. We would like to suggest creating a NZ security community with a nz-sec mailing list, for example. This would have the same sort of intent as the nsp-security mailing list, bringing in people with a genuine interest in security practice and incident handling. We feel that the CCIP list, while valuable, is informative rather than collaborative. The nznog list has been used for security issues where relevant, but network operations is the reason for nznog, not security management. Ultimately the list and list membership, or some variant, would become associated with a NZ CERT if one were to happen, but in the meantime InternetNZ would be happy to host and advertise a moderated list. If you think there would be some value in this, please email me. You can find information about the nsp-security mailing list at https://puck.nether.net/mailman/listinfo/nsp-security) Brendan Murray Chairing the InternetNZ NZCERT Task Force.

7 7

Re: [nznog] NZ Security Notifications
by Barry Greene (bgreene) 14 Dec '05

14 Dec '05

For those who are interested, I've got a draft of some guidelines that can be used to create a group like nsp-sec-nz. Pop me a note and I'll send it. > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Wednesday, December 14, 2005 8:16 AM > To: Joe Abley > Cc: NZNOG List > Subject: Re: [nznog] NZ Security Notifications > > ] While an nsp-sec-nz list sounds like it could be lots of > fun, maybe ] it's also worth mentioning that it's perfectly > possible (and ] reasonable) for operators in nz who fit the > target demographic to ] become subscribers to the existing > nsp-sec list. > > Agreed! The mix of both nsp-sec and nsp-sec-nz would be > quite complimentary and useful. > > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Hotmail
by Jeremy Strachan 14 Dec '05

14 Dec '05

Probably B52 bombers and cruise missiles. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 15 December 2005 12:47 p.m. To: Simon Lyall Cc: nznog Subject: Re: [nznog] Hotmail Simon Lyall wrote: > Violations will result in use of equipment located in California and > other states. Ouuchhhh... that'll stop spammers for sure! Wonder what equipment located in California and other states it is that MSN/Hotmail will use though? -- Juha _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 7

Hotmail
by Simon Lyall 14 Dec '05

14 Dec '05

$ telnet mx2.hotmail.com smtp Trying 65.54.244.168... Connected to mx2.hotmail.com. Escape character is '^]'. 220 bay0-mc6-f18.bay0.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states. Wed, 14 Dec 2005 15:39:37 -0800 helo 250 bay0-mc6-f18.bay0.hotmail.com (3.1.0.17) Hello [202.27.185.139] Mail from:<simon(a)darkmere.gen.nz> 452 Out of memory Connection closed by foreign host. $ -- 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

Re: [nznog] NZ Security Notifications
by Dean Pemberton 13 Dec '05

13 Dec '05

>Would this list have the same sort of policy for membership as nsp-sec? >i.e. an invite only list for people who actually have to do the work >with a policy of kicking out people who don't meet the membership >criteria on an ongoing basis. > >If that's the case then I can see value in such a list but if it's >going to be similar to NZNOG with an "anybody can join" policy then I'm >less interested. > >andy I agree with Andy here. The only list I would be interested in is one which subscribes to the nsp-sec policy. No lurking. You have to be the person who is able to make the changes. Change jobs and you unsub. And some others. It's the only way. An "anyone can join" list will degrade into.... well my opinions here should remain to myself =) I would suggest that people look at joining nsp-sec rather than re-inventing the wheel. Or at the very least getting Rob to host an nsp-sec-nz list with the same policy around it. If you are a large provider, then there is probably already content on nsp-sec that you should know about. Dean.

1 0

Fwd: King Kong streaming tomorrow
by Paul Adshead 13 Dec '05

13 Dec '05

It may be good for someone in Telecom to let their front line staff know about (de-)peering at some point. After spending 15 minutes on the phone, it was quite amusing when they came back from putting me on hold: "I have talked to our tech guys and no-one in Xtra can get to the page either. They think it is a problem with the routing of data for the site at the far end. You could try power-cycling your router though"... Then when I asked for confirmation by email: "We suspect that there has been some stringent ip filtering and this is what could be causing the problem. We can not confirm this the best source of action would be to contact the host of the website for further information." Obviously either highly qualified in providing BS responses or just stupid. It's still annoying that I can't get to see it though... Paul -----Original Message----- From: Mike [mailto:mike(a)nzbox.com] Sent: Wednesday, 14 December 2005 17:20 To: NZNOG Subject: Re: [nznog] King Kong streaming tomorrow Hi Rich and Si Can I suggest you mention which streams will be available internationally in your announcements. Cant see either of these from Seattle ;-) good message for TCL and TNZ though.... Kia ora! You've reached the Citylink anycast node located in San Francisco, California. If you are in NZ, you should ring your ISP and ask them why your traffic is coming to the USA, rather than staying in New Zealand. Useful phone numbers are at TelstraClear (try the wholesale number if you get no joy from residential/business) and the best number for Telecom would appear to be 0800 CALL XTRA [22 55 98]. If you're feeling particularly cussed, ask them what's changed in the two years between the RoTK (when you could reach these streams nationally) and now. International users, we're sorry, sadly, our non-existent budget means that we can't make the Courtenay Place webcam available internationally. Such is life. Mike On Dec 12, 2005, at 8:10 PM, Simon Blake wrote: > Hi all > > A belated notice that the red carpet TV coverage and Courtenay Place > webcam will be streaming tomorrow as part of the King Kong premiere. > The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam > from > embassy.citylink.co.nz (202.7.6.10), both anycast at the major > exchanges. The webcam is running now, informal MMS streams will start > about midday, TV coverage about 3pm. > > We're not expecting the same sorts of loads as RoTK, but who can tell. > > Cheers > Si > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

King Kong streaming tomorrow
by Simon Blake 13 Dec '05

13 Dec '05

Hi all A belated notice that the red carpet TV coverage and Courtenay Place webcam will be streaming tomorrow as part of the King Kong premiere. The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam from embassy.citylink.co.nz (202.7.6.10), both anycast at the major exchanges. The webcam is running now, informal MMS streams will start about midday, TV coverage about 3pm. We're not expecting the same sorts of loads as RoTK, but who can tell. Cheers Si

5 4

NZ use of AusCERT
by Jonathan Brewer 11 Dec '05

11 Dec '05

Hi folks, Are there many among us who are members of AusCERT? Any in the practice of reporting incidents on NZ based hosts to AusCERT? Do AusCERT care to hear about incidents from non-members? Cheers, Jon

2 1

woosh
by Garrrett Stoupe 11 Dec '05

11 Dec '05

Can someone from woosh please contact me off list

1 0

National Bank Phising Scam
by Ashley Petherick 10 Dec '05

10 Dec '05

Morning all, awoke today to a National bank Phishing scam - a pretty ugly one, they didnt put much effort into the email, but the 'verification web page' looks pretty authentic (save the URL http://202.93.254.35:443/cxk/) They ask for your First and Last name, and credit card number, your ATM PIN, and expiration date. Sent from security(a)nationalbank.co.nz / Subject - Verification Required I have advised the site. Account Confirmation Required! Valued National Bank Client, Recently there have been a large number of identity theft attempts targeting National Bank customers. In order to safeguard your account we require that you verify your banking details. This process is mandatory. You may do so by clicking Here <http://202.93.254.35:443/cxk/> <a href="http://202.93.254.35:443/cxk/"> and submitting the required information. Failure to do so may result in a temporary cessation of your account services pending submission. Thank you for your prompt attention to this matter and your co-operation in helping us maintain the integrity of our customers accounts. Please do not reply to this e-mail, as this is an unmonitored alias. If you require further assistance refer to our support centre <http://nationalbank.co.nz/personal/contacts/> <A HREF="http://nationalbank.co.nz/personal/contacts/" TARGET="_blank">. National Bank respects your privacy. Click here <http://nationalbank.co.nz/terms/default.htm> <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank"> to read the National Bank Group Privacy Policy Statement. Electronic Banking services are issued by the National Bank of New Zealand (Electronic Banking services include telephone banking, Netbank and Bpay). A Product Disclosure Statement (PDS) <http://nationalbank.co.nz/terms/default.htm> <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank"> is available for these products on this website or from any branch of the National Bank. © 2005 The National Bank of New Zealand, part of ANZ National Bank Limited

1 0

Re: [nznog] (OT?) Phishers targetting Kiwibank
by Donald Neal 08 Dec '05

08 Dec '05

Andy Linton wrote: > > It would be good if these phishing discussions focussed on > technical aspects > of what can be done by people on this list once the list > knows about the > latest scam. The banks I suspect will make their own > decisions without seeking > advice here. > This thread should now turn to a technical topic or go away. - Donald Neal NZNOG List Administrator Donald Neal |"You know what young, carnivorous, Support Engineer |alien mammal-like monsters are like. NGN Operations |Always getting into scrapes." 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.

4 3

(OT?) Phishers targetting Kiwibank
by Lesley Walker 08 Dec '05

08 Dec '05

I've received a reasonably plausible-looking phish for Kiwibank, appears to have originated in Washington DC. The domain it uses is "kiwibahk.com", registered through bookmyname.com, and I have sent a complaint to the registrar. Does anyone want a copy for reference? Lesley W

11 10

Re: [nznog] (OT?) Phishers targetting Kiwibank
by Regan Murphy 07 Dec '05

07 Dec '05

> They shut down their whole Internet banking site because of a > phishing email ! I would have thought that was somewhat of an > over reaction. That would sure annoy me if I happened to be > one of their customers. Well they wouldn't be the first bank to take this sort of action.... -- Regan

2 1

TelstraClear Down?
by jfp 04 Dec '05

04 Dec '05

Does anybody know what's up with TelstraClear. I can't get to their nameservers from NZ or the US. jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

3 3

Re: [nznog] TelstraClear down
by Stewart Fleming 04 Dec '05

04 Dec '05

DNS certainly gone bang. IP routing still working, but very slow. Denial of service attack? Had a call from my Telstra rep earlier, but that was for a billing error outstanding since February. Maybe they keep the DNS records in the same file...? -- Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET http://networkstatus.telstraclear.co.nz/home/clearnet.html. Reason: DNS lookup failure for: networkstatus.telstraclear.co.nz Apache/2.0.52 (Unix) Server at networkstatus.telstraclear.co.nz Port 80 Traceroute from TC frame relay hosted in ChCh to www.xtra.co.nz 3 218.101.61.74 (218.101.61.74) 28.325 ms 21.328 ms 27.119 ms 4 218.101.61.69 (218.101.61.69) 25.932 ms 18.852 ms 40.947 ms 5 218.101.61.33 (218.101.61.33) 17.685 ms 28.273 ms 124.740 ms 6 ggis-gige-v906.telstraclear.net (203.98.18.67) 43.038 ms 42.818 ms 15.735 ms 7 g0-1-0-4.akcr8.global-gateway.net.nz (210.55.202.49) 18.469 ms 36.399 ms 28.106 ms 8 v4.aksw7.global-gateway.net.nz (210.55.202.51) 46.682 ms 36.813 ms 43.531 ms 9 xtra-dom-2.aksw7.global-gateway.net.nz (203.96.120.150) 32.408 ms 18.452 ms 39.837 ms

3 2

Re: [nznog] TelstraClear Down?
by Simon Allard 04 Dec '05

04 Dec '05

Just the nameservers? They have probably been ACL'ed to stop DNS DDoS attacks, like what xtra etc have done. Simon Allard ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz > -----Original Message----- > From: jfp [mailto:jfp(a)clearfield.com] > Sent: Monday, 5 December 2005 10:20 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: [nznog] TelstraClear Down? > > > Does anybody know what's up with TelstraClear. I can't get to their > nameservers from NZ or the US. > > > jfp. > > ------------------------------------------------------------------------ > Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer > Phone (+64-9) 358 2081 Clearfield Software Ltd > Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place > Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand > ------------------------------------------------------------------------ > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

10 13

Re: [nznog] TelstraClear Down?
by Peter Mott 04 Dec '05

04 Dec '05

Maybe there was an imperical decision taken by AU head office to close it down due to lack of profits. :-) regards Peter Mott MOTT & ASSOCIATES Tel: +64 9 488 9352 Fax: +64 9 486 7017 -/-

2 1

Xen for network services (aka web/mail/dns etc) - OT?
by Simon 02 Dec '05

02 Dec '05

Hi There, I have been discussing the utilisation of Xen in a production environment on a couple of other lists (nzlug, debian-isp etc), but wondering if anyone from this list is using it in new zealand for serving of network services? Please let me know if this is OT. Would like to hear your experiences if so. Simon

6 6

Re: [nznog] [Fwd: Re: Bizarre spam]
by Nic Wise 01 Dec '05

01 Dec '05

I'd go with zombie's :) the . Then new line new line thing means that the rest of whatever your script does is ignored by the SMTP server, and the big long number might be either a "key" to get the target of an attack (eg, HTTP to this server, present this key, get details back) or something, or the IP / DNS name / something else of it, maybe base64'ed or encrypted somehow. I could see a virus/trojan/etc sitting there, polling a pop3 account, looking for emails with those words in the subject, and some form of payload, then it pings up and goes and does something. Maybe the attacked script was used as a "trigger"?? Damn it's time for a beer. N > -----Original Message----- > From: Justin Cook [mailto:justin(a)skull.co.nz] > Sent: Friday, 2 December 2005 3:01 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] [Fwd: Re: Bizarre spam] > > It was, and it's already dealt with. Just looking for the > reason behind it. Adrian is probably on the mark when he > calls it a DoS. > > James Clark wrote: > > > > > Sounds like PHP injection, assume it's PHP. If not ignore me. > > > > These articles explain the cause and fixes in more depth: > > > > http://securephp.damonkohler.com/index.php/Email_Injection > > http://www.nyphp.org/phundamentals/email_header_injection.php > > > > > > Justin Cook wrote: > > > >> I've got a question for the appropriate higher minds. > >> > >> I fixed one of my clients self-built contact forms after I had an > >> inkling that someone was injecting headers into it to use it as a > >> relay. Turns out I was right, but it's beyond me what > they're trying > >> to accomplish: > >> > >> Content-Type: text/plain; charset="us-ascii" > >> MIME-Version: 1.0 > >> Content-Transfer-Encoding: 7bit > >> Subject: which a rising moon now threw from the scattered clouds > >> bcc: charleslegbe(a)aol.com > >> > >> 648a4d46b041327ac30fe4f27a9b72ee > >> . > >> > >> > >> Tons and tons of that just that. What possible use could > this garbage > >> be? Is someone trying to blackhole their domain? > >> > >> Cheers > >> Justin > >> > >> _______________________________________________ > >> NZNOG mailing list > >> NZNOG(a)list.waikato.ac.nz > >> http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Dec '05

01 Dec '05

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:AS17435 descr: advertised to AS9560 by WorldxChange Communications - AS17435 members: 202.182.192.0/19^19-29, 58.28.0.0/16^16-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: gsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050308 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.182.192.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: noc(a)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051202 source: NZRR

1 0

Bizarre spam
by Justin Cook 01 Dec '05

01 Dec '05

I've got a question for the appropriate higher minds. I fixed one of my clients self-built contact forms after I had an inkling that someone was injecting headers into it to use it as a relay. Turns out I was right, but it's beyond me what they're trying to accomplish: Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: which a rising moon now threw from the scattered clouds bcc: charleslegbe(a)aol.com 648a4d46b041327ac30fe4f27a9b72ee . Tons and tons of that just that. What possible use could this garbage be? Is someone trying to blackhole their domain? Cheers Justin

2 1

[Fwd: Re: Bizarre spam]
by Justin Cook 01 Dec '05

01 Dec '05

It was, and it's already dealt with. Just looking for the reason behind it. Adrian is probably on the mark when he calls it a DoS. James Clark wrote: > > Sounds like PHP injection, assume it's PHP. If not ignore me. > > These articles explain the cause and fixes in more depth: > > http://securephp.damonkohler.com/index.php/Email_Injection > http://www.nyphp.org/phundamentals/email_header_injection.php > > > Justin Cook wrote: > >> I've got a question for the appropriate higher minds. >> >> I fixed one of my clients self-built contact forms after I had an >> inkling that someone was injecting headers into it to use it as a >> relay. Turns out I was right, but it's beyond me what they're trying >> to accomplish: >> >> Content-Type: text/plain; charset="us-ascii" >> MIME-Version: 1.0 >> Content-Transfer-Encoding: 7bit >> Subject: which a rising moon now threw from the scattered clouds >> bcc: charleslegbe(a)aol.com >> >> 648a4d46b041327ac30fe4f27a9b72ee >> . >> >> >> Tons and tons of that just that. What possible use could this garbage >> be? Is someone trying to blackhole their domain? >> >> Cheers >> Justin >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog > > >

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 01 Dec '05

01 Dec '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS18119 descr: Route set advertised to AS9560 by Linux Net - 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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051202 source: NZRR

1 0

Re: [nznog] Bizarre spam]
by Justin Cook 01 Dec '05

01 Dec '05

I think they're going to 30 or 40 different AOL addresses. Just trashed about 800 of them so I can't really go back and check for sure. They're being sent from a lot of different IP addresses, some of them in the same range but not always. Probably zombies. Seems like a lot of work to go to for fuck all. Kitto, Adrian - Axon AKL wrote: >Does it all BCC the same mailbox? > >Could be an old fashion dos on the mailbox... (seen it before) > >Cheers > >Adrian > > >-----Original Message----- >From: Justin Cook [mailto:justin(a)skull.co.nz] > >Sent: Friday, 2 December 2005 2:54 p.m. >To: nznog(a)list.waikato.ac.nz >Subject: [nznog] Bizarre spam > >I've got a question for the appropriate higher minds. > >I fixed one of my clients self-built contact forms after I had an > >inkling that someone was injecting headers into it to use it as a relay. > >Turns out I was right, but it's beyond me what they're trying to >accomplish: > >Content-Type: text/plain; charset="us-ascii" >MIME-Version: 1.0 >Content-Transfer-Encoding: 7bit >Subject: which a rising moon now threw from the scattered clouds >bcc: charleslegbe(a)aol.com > >648a4d46b041327ac30fe4f27a9b72ee >. > > >Tons and tons of that just that. What possible use could this garbage > >be? Is someone trying to blackhole their domain? > >Cheers >Justin > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog > >-- >The information contained in this e-mail message is intended only for the >use of the person or entity to whom it is addressed and may contain >information that is CONFIDENTIAL and may be exempt from disclosure under >applicable laws. > >If you read this message and are not the addressee you are notified that >use, dissemination, distribution, or reproduction of this message is >prohibited. If you have received this message in error, please notify us >immediately and delete the original message. You should scan this message >and any attached files for viruses. > >Axon accepts no liability for any loss caused either directly or >indirectly by a virus arising from the use of this message or any >attached file. > > >

1 0

JSR.COM Prefix List Update (and peering request)
by John S Russell 01 Dec '05

01 Dec '05

Hiya all (and sundry), For those of you who peer with jsr.com, here's a prefix update. It's a massive update, since I am DOUBLING the amount of advertised prefixes[1], like woah. New list can be found here: http://jsr.com/prefix For those of you who are not currently peering with jsr.com, please consider doing so. jsr.com is a very very tiny boutique and exclusive as hell co-location service. It's run by geeks, for geeks, generally to service geek whims and projects. There's a fair wack of content on there, including: - The personal mail and web servers for various notable NZ geeks! - [Unable to state due to NDA compliance!] - Up-To-Date Debian Mirrors! - [Unable to state due to a personal promise!] - [Unable to state for fear of reprisal!] If you'd like to set up a direct peering session via APE, please contact jsr(a)jsr.com to arrange it (TelstraClear staff, I'm looking forward to hearing from you!). Sadly we do not yet have a WIX presence, but this is in our roadmap for future growth.[2] If you'd like to discuss co-location in our Sky Tower facility, please also contact jsr(a)jsr.com and have a list of reasons why you're geeky enough or your project is cool enough to merit the allocation of our sweet, precious, incandescent with awesomeness[3], rack units on L48. Cheers, JSR [1] To two. [2] Mind you, so is "Evolve into energy beings, rule universe from on high." [3] Incandescence may actually be caused by thermal dissipation from servers. YMMV.

1 0

Remote server booting
by Simon 01 Dec '05

01 Dec '05

Hi There, Im wondering if anyone has used or is using a good solution to remote boot (from complete power down) servers and equiptment? This i have done in the past by having the bios on the server set to reboot after power fail and that takes care of the rest along with good load UPS's and backup power. But what if you acually had to shut down a server for some reason out-there (backup power fails)? Regards, Simon

19 23

Re: [nznog] Remote server booting
by murphy 01 Dec '05

01 Dec '05

If you are using HP machines (other mobs may have a similar setup) you can take advantage of iLO - Integrated Lights Out. It is a 2nd or 3rd network card in the machine that acts as a management interface. It can be accessed by telnet, ssh, or web (hopefully your core network is still up) and provides access to virtual power buttons, mounting ISO's remotely for full system rebuilds, etc. I spec it in standard with all my server purchases. In scenarios where you are co-locating then this is a must. Providing the network is up and the power cable is plugged into the server (whether the server be physically on or off) then you have full control over its behaviour. Worth a look into. On 12/1/05, nznog-request(a)list.waikato.ac.nz <nznog-request(a)list.waikato.ac.nz> wrote: > Send NZNOG mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.waikato.ac.nz/mailman/listinfo/nznog > or, via email, send a message with subject or body 'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NZNOG digest..." > > > Today's Topics: > > 1. Re: Remote server booting (Regan Murphy) > 2. Re: Remote server booting (Erin Salmon - Unleash Computers Ltd) > 3. NZ Online Security Day (Matthew Poole) > 4. Re: NZ Online Security Day (Juha Saarinen) > 5. Re: Remote server booting (Drew Broadley) > 6. Re: Remote server booting (Joe Abley) > 7. Re: Remote server booting (Gordon Smith) > 8. Re: Remote server booting (Simon Lyall) > 9. Re: Remote server booting (Daniel Lawson) > 10. Re: Remote server booting (Barry Murphy) > 11. Re: Remote server booting (Jeremy Strachan) > 12. Re: Remote server booting (Simon) > 13. Re: Remote server booting (Tony Wicks) > 14. Re: NZ Online Security Day (Steven Heath) > 15. Re: Remote server booting (Nathan Ward) > 16. Re: NZ Online Security Day (Erin Salmon - Unleash Computers Ltd) > 17. Re: NZ Online Security Day (neil gardner) > 18. Re: NZ Online Security Day (Mark Foster) > 19. Xen for network services (aka web/mail/dns etc) - OT? (Simon) > 20. Re: Xen for network services (aka web/mail/dns etc) - OT? > (Erin Salmon - Unleash Computers Ltd) > 21. Re: Xen for network services (aka web/mail/dns etc) - OT? > (Richard Patterson) > 22. Re: Xen for network services (aka web/mail/dns etc) - OT? > (Andrew Thompson) > 23. Re: Xen for network services (aka web/mail/dns etc) - OT? > (Richard Patterson) > 24. Re: Xen for network services (aka web/mail/dns etc) - OT? (Martin) > > > > ---------- Forwarded message ---------- > From: "Regan Murphy" <regan.murphy(a)oasystems.co.nz> > To: "James Clark" <jamesc(a)bofh.co.nz>, <criggie(a)criggie.dyndns.org> > Date: Wed, 30 Nov 2005 12:08:02 +1300 > Subject: Re: [nznog] Remote server booting > > We no longer carry this range of product, and I beleive that the > > manufacturers have discontinued some of the range There website has > > gone but you can try to call them on 0800smitch > > Black Box used to have a local website and produce a Catalog, not sure > if they still do in NZ. They carry a range of remote power units, have > a browse - I'm sure there is something suitable there: > > http://www.blackbox.com/Catalog/Category.aspx?cid=183,1324,1327 > > > -- > Regan > > > > > > ---------- Forwarded message ---------- > From: "Erin Salmon - Unleash Computers Ltd" <erin(a)unleash.co.nz> > To: "Regan Murphy" <regan.murphy(a)oasystems.co.nz>, "James Clark" <jamesc(a)bofh.co.nz>, <criggie(a)criggie.dyndns.org> > Date: Wed, 30 Nov 2005 12:21:09 +1300 > Subject: Re: [nznog] Remote server booting > Black Box does still sell in NZ, but I'm not sure if they have a local > office here or just bring stuff over as required. sales(a)blackbox.com.au. > > Their stuff is good, but on the whole very expensive. > > VMWare, Xen, UML etc all offer remote "power cycling" of hosted domains, but > of course, if the root domain goes down you're still stuck. Needless to say > the other advantages of virtualisation make it pretty attractive. > > Cheers, > > Erin Salmon > Managing Director > Unleash Computers Ltd > Unleash Networks Ltd > Mobile: 021 877 913 > Landline: 03 365 1273 > > -----Original Message----- > From: Regan Murphy [mailto:regan.murphy(a)oasystems.co.nz] > Sent: 30 November 2005 12:08 p.m. > To: James Clark; criggie(a)criggie.dyndns.org > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Remote server booting > > > We no longer carry this range of product, and I beleive that the > > manufacturers have discontinued some of the range There website has > > gone but you can try to call them on 0800smitch > > Black Box used to have a local website and produce a Catalog, not sure > if they still do in NZ. They carry a range of remote power units, have > a browse - I'm sure there is something suitable there: > > http://www.blackbox.com/Catalog/Category.aspx?cid=183,1324,1327 > > > -- > Regan > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > ---------- Forwarded message ---------- > From: Matthew Poole <matt(a)p00le.net> > To: nznog(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 12:38:20 +1300 (NZDT) > Subject: [nznog] NZ Online Security Day > > Is apparently today. One of my co-workers discovered this when he logged > into the WestpacTrust online banking site. > Anyone else heard of this? It was obviously very well publicised, seeing > as a whole company of geeks hadn't heard of it. > > -- > Matthew Poole > "Don't use force. Get a bigger hammer." > > > > > > ---------- Forwarded message ---------- > From: Juha Saarinen <juha(a)saarinen.org> > To: Matthew Poole <matt(a)p00le.net> > Date: Wed, 30 Nov 2005 12:52:12 +1300 > Subject: Re: [nznog] NZ Online Security Day > Matthew Poole wrote: > > Is apparently today. One of my co-workers discovered this when he logged > > into the WestpacTrust online banking site. > > Anyone else heard of this? It was obviously very well publicised, seeing > > as a whole company of geeks hadn't heard of it. > > It's a silly stunt that is best ignored. I don't think geeks are > interested in downloading Hector the Virus Vect... err, Protector, in > order to celebrate Online Security Day. > > -- > Juha > > > > > > ---------- Forwarded message ---------- > From: Drew Broadley <drew(a)corrupt.co.nz> > To: criggie(a)criggie.dyndns.org > Date: Wed, 30 Nov 2005 13:57:56 +1300 > Subject: Re: [nznog] Remote server booting > criggie(a)criggie.dyndns.org wrote: > >>>Im wondering if anyone has used or is using a good solution to remote > >>>boot (from complete power down) servers and equiptment? > > > > > > > > Theres a box called a smitch, which you can remotely turn on or off using > > a SMS message. They're quite pricy at around $300 NZ, but you could put > > one in a place thats otherwise hard to get to... someone's roof-space for > > example. > > > > http://www.cellpower.co.nz/Smitch%20switch.htm <-- out of stock > > http://www.smitch.co.nz/ <-- goes to domainz > > > > They do need a basic lesson in "how to market a product" though :/ > > For a cheaper option, http://ito.client.topshelfmedia.co.nz/Home > > - Drew > > > > > > ---------- Forwarded message ---------- > From: Joe Abley <jabley(a)isc.org> > To: Simon <greminn(a)gmail.com> > Date: Tue, 29 Nov 2005 20:02:06 -0500 > Subject: Re: [nznog] Remote server booting > > On 28-Nov-2005, at 22:44, Simon wrote: > > > Im wondering if anyone has used or is using a good solution to remote > > boot (from complete power down) servers and equiptment? > > If you'd also like a proper serial console (and your server's bios > doesn't already provide you with one) you could do worse than <http:// > www.realweasel.com/>. It's probably hugely expensive if all you want > is a remote power cycle capability though. > > > Joe > > > > > > ---------- Forwarded message ---------- > From: "Gordon Smith" <gsmith(a)wxc.co.nz> > To: <NZNOG(a)list.waikato.ac.nz> > Date: Wed, 30 Nov 2005 14:04:31 +1300 > Subject: Re: [nznog] Remote server booting > These guys also do good solutions: > > http://www.cyclades.com/ > > > > > > ---------- Forwarded message ---------- > From: Simon Lyall <simon(a)darkmere.gen.nz> > To: nznog <NZNOG(a)list.waikato.ac.nz> > Date: Wed, 30 Nov 2005 14:18:49 +1300 (NZDT) > Subject: Re: [nznog] Remote server booting > On Wed, 30 Nov 2005, Gordon Smith wrote: > > These guys also do good solutions: > > > > http://www.cyclades.com/ > > <plug> > > If anyone is going to Linux Conf in Dunedin in January then we are having > a talk by John Bordin from Cyclades on this area at the Sysadmin Miniconf, > See http://sysadmin.miniconf.org/presentations.html (3rd one down) > > The rest of the programme is being finalized and should be published in a > couple of days. > </plug> > > -- > Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ > "To stay awake all night adds a day to your life" - Stilgar | eMT. > > > > > > ---------- Forwarded message ---------- > From: Daniel Lawson <daniel(a)wand.net.nz> > To: Joe Abley <jabley(a)isc.org>, NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 14:33:39 +1300 > Subject: Re: [nznog] Remote server booting > > > > > >>Im wondering if anyone has used or is using a good solution to remote > >>boot (from complete power down) servers and equiptment? > >> > >> > > > >If you'd also like a proper serial console (and your server's bios > >doesn't already provide you with one) you could do worse than <http:// > >www.realweasel.com/>. It's probably hugely expensive if all you want > >is a remote power cycle capability though. > > > > > > I recently picked up a second hand Compaq RILOE card on trademe for > about $70 (there's still a few there). Provides local console > redirection via http, keyboard/mouse intercept, remote power control > (with a custom powercable that fits in between the physical power button > and the psu), etc. These models are a bit old now, but the modern > equivalents (such as the realweasel) look good, and I'd consider them > well worth the money. > > -- > Daniel Lawson > WAND Group, Computer Science Department > University of Waikato > email: daniel(a)wand.net.nz phone: +64 7 838 4136 > > > > > > ---------- Forwarded message ---------- > From: Barry Murphy <barry(a)unix.co.nz> > To: Daniel Lawson <daniel(a)wand.net.nz>, Joe Abley <jabley(a)isc.org>, NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 15:18:29 +1300 > Subject: Re: [nznog] Remote server booting > Hmmm, so basically an IP-KVM ? Does it have a network port or does it share > the systems; do you assign an IP to it and it gives a web based console? > > I'm wondering if i can put this into a system, attach it to a KVM on site > and control up to 8 pc's; though it doesnt appear to have a video output. > > Seems pretty interesting, I may get one to play with. > > Regards > Barry > > > ----- Original Message ----- > From: "Daniel Lawson" <daniel(a)wand.net.nz> > To: "Joe Abley" <jabley(a)isc.org>; <NZNOG(a)list.waikato.ac.nz> > Sent: Wednesday, November 30, 2005 2:33 PM > Subject: Re: [nznog] Remote server booting > > > > > > > > > > >>Im wondering if anyone has used or is using a good solution to remote > > >>boot (from complete power down) servers and equiptment? > > >> > > >> > > > > > >If you'd also like a proper serial console (and your server's bios > > >doesn't already provide you with one) you could do worse than <http:// > > >www.realweasel.com/>. It's probably hugely expensive if all you want > > >is a remote power cycle capability though. > > > > > > > > > > I recently picked up a second hand Compaq RILOE card on trademe for > > about $70 (there's still a few there). Provides local console > > redirection via http, keyboard/mouse intercept, remote power control > > (with a custom powercable that fits in between the physical power button > > and the psu), etc. These models are a bit old now, but the modern > > equivalents (such as the realweasel) look good, and I'd consider them > > well worth the money. > > > > -- > > Daniel Lawson > > WAND Group, Computer Science Department > > University of Waikato > > email: daniel(a)wand.net.nz phone: +64 7 838 4136 > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > > > ---------- Forwarded message ---------- > From: "Jeremy Strachan" <JeremyS(a)cclnz.co.nz> > To: "Barry Murphy" <barry(a)unix.co.nz>, "Daniel Lawson" <daniel(a)wand.net.nz>, "Joe Abley" <jabley(a)isc.org>, <NZNOG(a)list.waikato.ac.nz> > Date: Wed, 30 Nov 2005 15:26:03 +1300 > Subject: Re: [nznog] Remote server booting > > Adderlink. > > We use two (Ak/Wn) attached to our 16 port KVM's to provide IP access to > the consoles. > > The box has one network port and runs a commercial version of VNC, which > behaves better than free VNC. > > Attach it to a UPS, and you can have access to your consoles with power > on or off. > > > Jeremy > > > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Wednesday, 30 November 2005 3:18 p.m. > To: Daniel Lawson; Joe Abley; NZNOG(a)list.waikato.ac.nz > Subject: Re: [nznog] Remote server booting > > Hmmm, so basically an IP-KVM ? Does it have a network port or does it > share the systems; do you assign an IP to it and it gives a web based > console? > > I'm wondering if i can put this into a system, attach it to a KVM on > site and control up to 8 pc's; though it doesnt appear to have a video > output. > > Seems pretty interesting, I may get one to play with. > > Regards > Barry > > > > > > ---------- Forwarded message ---------- > From: Simon <greminn(a)gmail.com> > To: NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 15:31:34 +1300 > Subject: Re: [nznog] Remote server booting > Same here: > > http://www.rextron.com/products/kips01.htm > > Works great, connects to a 8 port KVM switch. It even runs linux, so > you can ssh to it. > > On 11/30/05, Jeremy Strachan <JeremyS(a)cclnz.co.nz> wrote: > > > > Adderlink. > > > > We use two (Ak/Wn) attached to our 16 port KVM's to provide IP access to > > the consoles. > > > > The box has one network port and runs a commercial version of VNC, which > > behaves better than free VNC. > > > > Attach it to a UPS, and you can have access to your consoles with power > > on or off. > > > > > > Jeremy > > > > > > -----Original Message----- > > From: Barry Murphy [mailto:barry(a)unix.co.nz] > > Sent: Wednesday, 30 November 2005 3:18 p.m. > > To: Daniel Lawson; Joe Abley; NZNOG(a)list.waikato.ac.nz > > Subject: Re: [nznog] Remote server booting > > > > Hmmm, so basically an IP-KVM ? Does it have a network port or does it > > share the systems; do you assign an IP to it and it gives a web based > > console? > > > > I'm wondering if i can put this into a system, attach it to a KVM on > > site and control up to 8 pc's; though it doesnt appear to have a video > > output. > > > > Seems pretty interesting, I may get one to play with. > > > > Regards > > Barry > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > > > ---------- Forwarded message ---------- > From: Tony Wicks <tony(a)prophecy.net.nz> > To: Barry Murphy <barry(a)unix.co.nz> > Date: Wed, 30 Nov 2005 15:37:04 +1300 > Subject: Re: [nznog] Remote server booting > Yes, Cyclades does KVM over IP (for example, you can RDP to the KVM) and > also a power strip that lets you power cycle each outlet on demand (as > well as serial console of course). If you need any info drop me a line > (can source them if you like.) > > > > Barry Murphy wrote: > > Hmmm, so basically an IP-KVM ? Does it have a network port or does it share > > the systems; do you assign an IP to it and it gives a web based console? > > > > I'm wondering if i can put this into a system, attach it to a KVM on site > > and control up to 8 pc's; though it doesnt appear to have a video output. > > > > Seems pretty interesting, I may get one to play with. > > > > Regards > > Barry > > > > > > ---------- Forwarded message ---------- > From: Steven Heath <sheath(a)paradise.net.nz> > To: Juha Saarinen <juha(a)saarinen.org> > Date: Wed, 30 Nov 2005 15:39:16 +1300 (NZDT) > Subject: Re: [nznog] NZ Online Security Day > Quoting Juha Saarinen <juha(a)saarinen.org>: > > > Matthew Poole wrote: > > > Is apparently today. One of my co-workers discovered this when he > > logged > > > into the WestpacTrust online banking site. > > > Anyone else heard of this? It was obviously very well publicised, > > seeing > > > as a whole company of geeks hadn't heard of it. > > > > It's a silly stunt that is best ignored. I don't think geeks are > > interested in downloading Hector the Virus Vect... err, Protector, in > > order to celebrate Online Security Day. > > The Net Nanny, err, Net Safe people did a press release about it 2 days ago. > Lots of lead time and all that. Seems they proposed the idea about six months > ago but no one cared... > > http://www.netsafe.org.nz/isgnews/text_generation_release.aspx > > I think I will just stick to Bonzi Buddy. > > > Steven Heath > .nz news & views > +64 21 706 067 > www.nznews.org.nz > > "America is the only nation in history which has gone directly from barbarism > to degeneration without the usual interval of civilization." > > Georges Clemenceau > > > > > > ---------- Forwarded message ---------- > From: "Nathan Ward" <nznog(a)daork.net> > To: nznog(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 15:57:23 +1300 (NZDT) > Subject: Re: [nznog] Remote server booting > > Im wondering if anyone has used or is using a good solution to remote > > boot (from complete power down) servers and equiptment? > > > > This i have done in the past by having the bios on the server set to > > reboot after power fail and that takes care of the rest along with > > good load UPS's and backup power. But what if you acually had to shut > > down a server for some reason out-there (backup power fails)? > > Most of the replies to this ignored his last sentence. > Many (most?) of the BIOSes/motherboards I have seen can either be in > "Power off" or "Last state" when power is reconnected. Few have a "Power > on" option. > > If he shuts down a server, the hardware will power down, and when he power > cycles with his remote power strip, the box stays in "Power off" or the > "Last state" which is.. off. > > If one looses power at a site, the servers reliant on the failed power > rail should shut themselves down before the UPS runs out, in order to > prevent filesystem corruption, which can prolong an outage. > > I see the only real solutions to this being some flavour of lights out > card, or of course, monkeys with cellphones. > > -- > Nathan Ward > > > > > > ---------- Forwarded message ---------- > From: "Erin Salmon - Unleash Computers Ltd" <erin(a)unleash.co.nz> > To: "Steven Heath" <sheath(a)paradise.net.nz>, "Juha Saarinen" <juha(a)saarinen.org> > Date: Wed, 30 Nov 2005 16:34:13 +1300 > Subject: Re: [nznog] NZ Online Security Day > It is incredibly easy to underestimate the volumes of stupid people out > there. You'll notice that most govt department website have things like: > > Name: > Eg. John Smith > > On their contact forms... They don't do that for no reason. > > A bit of education (even if it is pathetically light-weight) can't be a bad > thing. > > Just my $0.02. > > Erin Salmon > Managing Director > Unleash Computers Ltd > Unleash Networks Ltd > Mobile: 021 877 913 > Landline: 03 365 1273 > > -----Original Message----- > From: Steven Heath [mailto:sheath(a)paradise.net.nz] > Sent: 30 November 2005 3:39 p.m. > To: Juha Saarinen > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] NZ Online Security Day > > Quoting Juha Saarinen <juha(a)saarinen.org>: > > > Matthew Poole wrote: > > > Is apparently today. One of my co-workers discovered this when he > > logged > > > into the WestpacTrust online banking site. > > > Anyone else heard of this? It was obviously very well publicised, > > seeing > > > as a whole company of geeks hadn't heard of it. > > > > It's a silly stunt that is best ignored. I don't think geeks are > > interested in downloading Hector the Virus Vect... err, Protector, in > > order to celebrate Online Security Day. > > The Net Nanny, err, Net Safe people did a press release about it 2 days ago. > Lots of lead time and all that. Seems they proposed the idea about six > months > ago but no one cared... > > http://www.netsafe.org.nz/isgnews/text_generation_release.aspx > > I think I will just stick to Bonzi Buddy. > > > Steven Heath > .nz news & views > +64 21 706 067 > www.nznews.org.nz > > "America is the only nation in history which has gone directly from > barbarism > to degeneration without the usual interval of civilization." > > Georges Clemenceau > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > ---------- Forwarded message ---------- > From: "neil gardner" <neil.gardner(a)alliedtelesyn.co.nz> > To: <sheath(a)paradise.net.nz>,<juha(a)saarinen.org>, <erin(a)unleash.co.nz> > Date: Wed, 30 Nov 2005 16:40:02 +1300 > Subject: Re: [nznog] NZ Online Security Day > Hmmmm. That reminds me of some sort of saying... Something about a little knowledge being a dangerous thing... > > Aha - Here we go: > > "A little learning is a dangerous thing; drink deep, or taste not the Pierian spring: there shallow draughts intoxicate the brain, and drinking largely sobers us again. Alexander Pope (1688-1744) - An Essay on Criticism." > > http://en.wikipedia.org/wiki/Alexander_Pope > > And on balance I'd agree - letting someone think they're safer if they take the most lightweight precautions probably isn't a good idea. > > Cheers - N > > > > Neil Gardner > Product Manager > Allied Telesyn Research Ltd > New Zealand > +64 3 339-9509 (ph) > +64 3 339-3001 (fax) > > >>> "Erin Salmon - Unleash Computers Ltd" <erin(a)unleash.co.nz> 30/11/2005 4:34 p.m. >>> > It is incredibly easy to underestimate the volumes of stupid people out > there. You'll notice that most govt department website have things like: > > Name: > Eg. John Smith > > On their contact forms... They don't do that for no reason. > > A bit of education (even if it is pathetically light-weight) can't be a bad > thing. > > Just my $0.02. > > Erin Salmon > Managing Director > Unleash Computers Ltd > Unleash Networks Ltd > Mobile: 021 877 913 > Landline: 03 365 1273 > > -----Original Message----- > From: Steven Heath [mailto:sheath(a)paradise.net.nz] > Sent: 30 November 2005 3:39 p.m. > To: Juha Saarinen > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] NZ Online Security Day > > Quoting Juha Saarinen <juha(a)saarinen.org>: > > > Matthew Poole wrote: > > > Is apparently today. One of my co-workers discovered this when he > > logged > > > into the WestpacTrust online banking site. > > > Anyone else heard of this? It was obviously very well publicised, > > seeing > > > as a whole company of geeks hadn't heard of it. > > > > It's a silly stunt that is best ignored. I don't think geeks are > > interested in downloading Hector the Virus Vect... err, Protector, in > > order to celebrate Online Security Day. > > The Net Nanny, err, Net Safe people did a press release about it 2 days ago. > Lots of lead time and all that. Seems they proposed the idea about six > months > ago but no one cared... > > http://www.netsafe.org.nz/isgnews/text_generation_release.aspx > > I think I will just stick to Bonzi Buddy. > > > Steven Heath > .nz news & views > +64 21 706 067 > www.nznews.org.nz > > "America is the only nation in history which has gone directly from > barbarism > to degeneration without the usual interval of civilization." > > Georges Clemenceau > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > NOTICE: This message contains privileged and confidential > information intended only for the use of the addressee > named above. If you are not the intended recipient of > this message you are hereby notified that you must not > disseminate, copy or take any action in reliance on it. > If you have received this message in error please > notify Allied Telesyn Research Ltd immediately. > Any views expressed in this message are those of the > individual sender, except where the sender has the > authority to issue and specifically states them to > be the views of Allied Telesyn Research. > > > > > > ---------- Forwarded message ---------- > From: "Mark Foster" <blakjak(a)blakjak.net> > To: nznog(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 16:55:44 +1300 (NZDT) > Subject: Re: [nznog] NZ Online Security Day > (large CC list removed...) > > > Hmmmm. That reminds me of some sort of saying... Something about a little > > knowledge being a dangerous thing... > > > > Aha - Here we go: > > > > "A little learning is a dangerous thing; drink deep, or taste not the > > Pierian spring: there shallow draughts intoxicate the brain, and drinking > > largely sobers us again. Alexander Pope (1688-1744) - An Essay on > > Criticism." > > > > http://en.wikipedia.org/wiki/Alexander_Pope > > > > And on balance I'd agree - letting someone think they're safer if they > > take the most lightweight precautions probably isn't a good idea. > > > > Cheers - N > > > > > > *snip* > > You beat me to the punch Neil. > The problem with 'a little knowledge' is you end up with a rash of 'Help! > I'm being DoS'd by (insert IP of your ISP's DNS Servers here)!!! BAN > THEM!' > > Aka the little bit of knowledge is 'knowing you need a firewall to be > safe' and the better bit of knowledge is 'knowing the difference betweem > an attack, and innocent / important internet traffic'. Or at least how to > find out the difference! > > But yeah, given the lack of PR that "Online Security Day" received in the > IT Community it can hardly be given any sort of credibility... you think > buy in from a few major IT outfits and ISPs would be kinda useful? > > Almost as press-worthy as Microsofts announcement re Maori language > support in Windows XP? (When its been available to varying degrees within > alternative OS's for quite some time..)[1] > > Mark. > > [1] I give credit to the fact they've finished it and packaged it. As I > understand it most of the Maori Language work for Linux is in an > incomplete state.... then again when you're throwing thousands of dollars > at a project you can expect to have an edge on small open-source efforts I > guess! > > > > > > > > ---------- Forwarded message ---------- > From: Simon <greminn(a)gmail.com> > To: NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 16:56:58 +1300 > Subject: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > Hi There, > > I have been discussing the utilisation of Xen in a production > environment on a couple of other lists (nzlug, debian-isp etc), but > wondering if anyone from this list is using it in new zealand for > serving of network services? Please let me know if this is OT. > > Would like to hear your experiences if so. > > Simon > > > > > > ---------- Forwarded message ---------- > From: "Erin Salmon - Unleash Computers Ltd" <erin(a)unleash.co.nz> > To: <nznog(a)list.waikato.ac.nz> > Date: Wed, 30 Nov 2005 17:04:17 +1300 > Subject: Re: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > Hi, > > We're using it extensively. We're offering it as a product to customers, > running DNS, qmail, apache, and a number of custom apps on it. The stable > releases are rock solidly reliable, and the development efforts behind it > are giving it new features all the time. At the moment with stable releases > you're limited to running a domain on a single CPU, which is a bit of a > pain, but the next release is going to include virtual processors, so > multiple "real" processors can be sent instructions from one master virtual > processor to which domains are assigned. > > Cheers, > > Erin Salmon > Managing Director > Unleash Computers Ltd > Unleash Networks Ltd > Mobile: 021 877 913 > Landline: 03 365 1273 > > -----Original Message----- > From: Simon [mailto:greminn(a)gmail.com] > Sent: 30 November 2005 4:57 p.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > > Hi There, > > I have been discussing the utilisation of Xen in a production > environment on a couple of other lists (nzlug, debian-isp etc), but > wondering if anyone from this list is using it in new zealand for > serving of network services? Please let me know if this is OT. > > Would like to hear your experiences if so. > > Simon > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > ---------- Forwarded message ---------- > From: Richard Patterson <richard(a)helix.net.nz> > To: Simon <greminn(a)gmail.com> > Date: Wed, 30 Nov 2005 16:55:23 +1300 > Subject: Re: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > Simon wrote: > > >Hi There, > > > >I have been discussing the utilisation of Xen in a production > >environment on a couple of other lists (nzlug, debian-isp etc), but > >wondering if anyone from this list is using it in new zealand for > >serving of network services? Please let me know if this is OT. > > > >Would like to hear your experiences if so. > > > >Simon > > > > > > I've deployed a Xen machine together with linux vservers inside the > virtual Xen domains (don't ask) > > Running exim4/apache/samba/ldap and maybe some other things. > Has been in production for several months now without any issues. > > > -Richard > > > > > > ---------- Forwarded message ---------- > From: Andrew Thompson <andy(a)fud.org.nz> > To: Richard Patterson <richard(a)helix.net.nz> > Date: Wed, 30 Nov 2005 17:48:03 +1300 > Subject: Re: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > On Wed, Nov 30, 2005 at 04:55:23PM +1300, Richard Patterson wrote: > > Simon wrote: > > > > >Hi There, > > > > > >I have been discussing the utilisation of Xen in a production > > >environment on a couple of other lists (nzlug, debian-isp etc), but > > >wondering if anyone from this list is using it in new zealand for > > >serving of network services? Please let me know if this is OT. > > > > > >Would like to hear your experiences if so. > > > > > >Simon > > > > > > > > > > I've deployed a Xen machine together with linux vservers inside the > > virtual Xen domains (don't ask) > > > > Running exim4/apache/samba/ldap and maybe some other things. > > Has been in production for several months now without any issues. > > Can I ask why you would choose this over using something like FreeBSD > jails which provide seperation with no overhead? > > > Andrew > > > > > > ---------- Forwarded message ---------- > From: Richard Patterson <richard(a)helix.net.nz> > To: Andrew Thompson <andy(a)fud.org.nz>, NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 17:54:55 +1300 > Subject: Re: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > Andrew Thompson wrote: > > >On Wed, Nov 30, 2005 at 04:55:23PM +1300, Richard Patterson wrote: > > > > > >>I've deployed a Xen machine together with linux vservers inside the > >>virtual Xen domains (don't ask) > >> > >>Running exim4/apache/samba/ldap and maybe some other things. > >>Has been in production for several months now without any issues. > >> > >> > > > >Can I ask why you would choose this over using something like FreeBSD > >jails which provide seperation with no overhead? > > > > > >Andrew > > > > > > > Customer wanted Xen > > > -Richard > > > > > > ---------- Forwarded message ---------- > From: marty(a)supine.com (Martin) > To: NZNOG(a)list.waikato.ac.nz > Date: Wed, 30 Nov 2005 16:23:24 +1100 > Subject: Re: [nznog] Xen for network services (aka web/mail/dns etc) - OT? > $quoted_author = "Andrew Thompson" ; > > > > Can I ask why you would choose this over using something like FreeBSD > > jails which provide seperation with no overhead? > > raw IP sockets for one... > > cheers > marty > > -- > <shortigo> I can't find my enlightenment configuration files > <BedMan> look in ~/.enlightenment > <shortigo> I don't seem to have one > <hazard> 'the path to enlightment is hard to find' > > http://www.bash.org/?238734 > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >

1 0

Re: [nznog] NZ Online Security Day
by neil gardner 29 Nov '05

29 Nov '05

Hmmmm. That reminds me of some sort of saying... Something about a little knowledge being a dangerous thing... Aha - Here we go: "A little learning is a dangerous thing; drink deep, or taste not the Pierian spring: there shallow draughts intoxicate the brain, and drinking largely sobers us again. Alexander Pope (1688-1744) - An Essay on Criticism." http://en.wikipedia.org/wiki/Alexander_Pope And on balance I'd agree - letting someone think they're safer if they take the most lightweight precautions probably isn't a good idea. Cheers - N Neil Gardner Product Manager Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) >>> "Erin Salmon - Unleash Computers Ltd" <erin(a)unleash.co.nz> 30/11/2005 4:34 p.m. >>> It is incredibly easy to underestimate the volumes of stupid people out there. You'll notice that most govt department website have things like: Name: Eg. John Smith On their contact forms... They don't do that for no reason. A bit of education (even if it is pathetically light-weight) can't be a bad thing. Just my $0.02. Erin Salmon Managing Director Unleash Computers Ltd Unleash Networks Ltd Mobile: 021 877 913 Landline: 03 365 1273 -----Original Message----- From: Steven Heath [mailto:sheath(a)paradise.net.nz] Sent: 30 November 2005 3:39 p.m. To: Juha Saarinen Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] NZ Online Security Day Quoting Juha Saarinen <juha(a)saarinen.org>: > Matthew Poole wrote: > > Is apparently today. One of my co-workers discovered this when he > logged > > into the WestpacTrust online banking site. > > Anyone else heard of this? It was obviously very well publicised, > seeing > > as a whole company of geeks hadn't heard of it. > > It's a silly stunt that is best ignored. I don't think geeks are > interested in downloading Hector the Virus Vect... err, Protector, in > order to celebrate Online Security Day. The Net Nanny, err, Net Safe people did a press release about it 2 days ago. Lots of lead time and all that. Seems they proposed the idea about six months ago but no one cared... http://www.netsafe.org.nz/isgnews/text_generation_release.aspx I think I will just stick to Bonzi Buddy. Steven Heath .nz news & views +64 21 706 067 www.nznews.org.nz "America is the only nation in history which has gone directly from barbarism to degeneration without the usual interval of civilization." Georges Clemenceau _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

2 1

NZ Online Security Day
by Matthew Poole 29 Nov '05

29 Nov '05

Is apparently today. One of my co-workers discovered this when he logged into the WestpacTrust online banking site. Anyone else heard of this? It was obviously very well publicised, seeing as a whole company of geeks hadn't heard of it. -- Matthew Poole "Don't use force. Get a bigger hammer."

4 3

Re: [nznog] Remote server booting
by Jeremy Strachan 29 Nov '05

29 Nov '05

Adderlink. We use two (Ak/Wn) attached to our 16 port KVM's to provide IP access to the consoles. The box has one network port and runs a commercial version of VNC, which behaves better than free VNC. Attach it to a UPS, and you can have access to your consoles with power on or off. Jeremy -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Wednesday, 30 November 2005 3:18 p.m. To: Daniel Lawson; Joe Abley; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] Remote server booting Hmmm, so basically an IP-KVM ? Does it have a network port or does it share the systems; do you assign an IP to it and it gives a web based console? I'm wondering if i can put this into a system, attach it to a KVM on site and control up to 8 pc's; though it doesnt appear to have a video output. Seems pretty interesting, I may get one to play with. Regards Barry

2 1

Re: [nznog] Remote server booting
by Gordon Smith 29 Nov '05

29 Nov '05

These guys also do good solutions: http://www.cyclades.com/

2 1

Re: [nznog] Remote server booting
by Regan Murphy 29 Nov '05

29 Nov '05

> We no longer carry this range of product, and I beleive that the > manufacturers have discontinued some of the range There website has > gone but you can try to call them on 0800smitch Black Box used to have a local website and produce a Catalog, not sure if they still do in NZ. They carry a range of remote power units, have a browse - I'm sure there is something suitable there: http://www.blackbox.com/Catalog/Category.aspx?cid=183,1324,1327 -- Regan

2 1

Re: [nznog] Remote server booting
by Geraint Jones 29 Nov '05

29 Nov '05

There are boards called Eric from Peppercon : http://www.peppercon.com/remoteboards.html I use a few of them and they are just as good as Lights Out cards from HP/Compaq Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net DDI: +64 (0)4 570 7633 Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240 -----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Tuesday, 29 November 2005 11:58 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Remote server booting > Im wondering if anyone has used or is using a good solution to remote > boot (from complete power down) servers and equiptment? > > This i have done in the past by having the bios on the server set to > reboot after power fail and that takes care of the rest along with > good load UPS's and backup power. But what if you acually had to shut > down a server for some reason out-there (backup power fails)? Most vendors have some kind of module available as standard, or as an option. IBM: "Remote Supervisor Adapter" HP: "Lights-Out" Dell: "DRAC" (Dell Remote Access Controller) Obviously, blade chassis, etc. have these built in.. There are also cards that go home made PCs, I believe. APC and others also make remote power switches, which are a power distribution board that let you switch ports on and off individually. This may solve part of your problem for cheaper than lightsout cards in all your servers. I believe the interface is some kind of network thing (ie. web, SNMP or telnet), or maybe RS-232. -- Nathan Ward _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

NZNOG 2006 Presenters
by Donald Neal 28 Nov '05

28 Nov '05

All New Zealanders who offered to be presenters at March's conference should by now have received a response. Well, all except one whose corporate email system is rejecting my emails. Could anyone living in New Zealand who has offered to present and not received a reply please contact me directly. - Donald Neal Donald Neal |"You know what young, carnivorous, Support Engineer |alien mammal-like monsters are like. NGN Operations |Always getting into scrapes." Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

Re: [nznog] Remote server booting
by Simon 28 Nov '05

28 Nov '05

On 11/29/05, Simon <greminn(a)gmail.com> wrote: > > Hire a monkey with a mobile phone and chain him to the side of the > > server. Train him press power when you call... > > Ha - tried that!, but the monkey scoffed down all the bananas we used > with Mr. Fusion to power the servers - so we fired is asre. > And with the cost of monkeys these days - its cheaper to hire a tech admin!

1 0

2day Peering
by Peter Mott 27 Nov '05

27 Nov '05

>>I wonder if Peter Mott has now moved on to something new now... >>Being one of NZ's Internet pioneers... >"ICONZ will keep the 2day.com brand, and founder and chief >engineer Peter Mott remains in the interim with the merged >company." >So for now he's still at 2day/ICONZ... The interim was in fact a fairly short period of time. A young sales chap arrived on day one and took over my office. I have had no participation at a management or operational level since that time. That was back in May. There was a contract in place for my services, but that has since been terminated. I will however be keeping an eye on the industry from my motor yacht :-) regards Peter Mott MV Toccata COASTLINE YACHTS LIMITED Tel: +64 9 488 9352 Fax: +64 9 486 7017 -/-

1 0

2day Peering
by John Johnston 27 Nov '05

27 Nov '05

Guys, The 2day and ICONZ networks have been combined as of last Friday and as such you will be receiving the 2day prefix announcements via ICONZ currently. Anyone that had a peer with 2day and not ICONZ, and wish to peer direct with ICONZ please drop me an email with your details. Peering with 192.203.154.80 and 81 with be reestablished using AS4770 at a later date. Regards John Johnston ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

3 3

UberNetworks
by Tristram J. Cheer 24 Nov '05

24 Nov '05

To the NZNOG list UberNetworks is a new WISP operating in Whangarei, our wireless network has just entered its live trails with a small client base. Currently we are operating in the 202.49.132.0/27 range and wish to post details of our operation on the list, contact details are as follows P.O Box 5083 Phone: 09-438-5472 Fax: 09-438-5473 NOC E-mail: noc(a)ubernet.co.nz NOC 24 Hour phone: 021715823 Since we don't currently have an AS(We are in trails after all) so our details have not been sent to http://usenet.net.nz/noc/ at this point We have the ability to peer at APE and invite interested parties to contact peering(a)ubernet.co.nz if you are interested in peering. Above internet services we have some clients with hosted dedicated servers so I invite all companies peering at APE to get in touch Now that the formal stuff is out of the way I have a favor to ask from the list: Does anybody have a server sitting on a APE connection that they would be willing to allow us to download and upload a 10mbit file to for throughput testing on Monday the 28th? FTP access suits us best, would only need it for the day and the file is random data from /dev/null, if anyone does can they contact me via tristram(a)ubernet.co.nz or via my mobile listed below And just to make sure its on topic there is some beer for anyone able to grant us the above request Cheers ------------------------------------- Tristram Cheer UberNetworks T:(09)438-5472 F:(09)438-5473 M:(021)715-823

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 24 Nov '05

24 Nov '05

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: Route set advertised to AS9560 by SafeNZ - AS24005 members: 202.137.240.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 20050909 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Nov '05

24 Nov '05

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: 203.98.6.0/24^24-29, 203.97.68.0/28^28-29, 219.88.140.0/24^24-29, 60.234.32.0/23^23-29, 202.137.240.0/21^21-29, 202.50.252.0/24^24-29, 203.167.254.0/24^24-29, 203.167.255.0/24^24-29, 203.97.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 20050420 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Nov '05

24 Nov '05

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, 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 20051117 source: NZRR REPLACED BY: 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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Nov '05

24 Nov '05

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, 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 20051117 source: NZRR REPLACED BY: 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

1 0

Re: [nznog] DNS serving IPs outside controlled range
by Brendan Murray 22 Nov '05

22 Nov '05

Stu Fleming <stewart(a)wic.co.nz> wrote: > I have a...friend, let's say...who operates a DNS server at a small > ISP. In a few of the zone files, there are A records that resolve to IP > addresses outside of the Class C that my..friend...controls. My friend > has been told that this is "against the rules" and that it is "causing > problems". I suspect I know what's happening here. It was a particular vexation for me some time ago when I was responsible for a network, and I'm going to guess it's the same one as your ...friend.... is dealing with, and found that 3rd parties were registering IP addresses with 'my' Class B as some other domain name. i.e I 'control' 172.17.0.0/24 as example.com and someone with a host in my range has registered a domain with an external supplier as someotherexample.com using 172.17.224.0/24 ip numbers, say. I looked into it, and asked around, and found that there were no rules stopping it, and no technology. I eventually realised that the external provider was outside my range of control and had to control my clients by telling them that it was against the AUP (as it was) for them to do it this way. If you have a relationship with this other network provider then you're probably better off doing your best to help them and their clients conform to their AUP, on a strictly "getting along with people" thing. But you're doing nothing anyone can stop. > > Questions: > - is resolving an A record outwith the delegated IP range "against the > rules"? discourteous is about it once they've asked you to stop. But you've got paying customers. > - if so, is there any documentation of the rules? should be against their internal AUP and so its someone elses problem > - what potential problems could this cause to the network that contains > the IP address to which the A records point? reverse lookups for what you're hosting resolve to their network address range. Some mail services might choke More likely, (assuming its who I think it is) they're shortly going to change a lot of internal IP numbers and what you're doing might cause them headaches in that process. Not the best way to maintain a relationship. -- Brendan Murray brendan(a)wolfhoundsecurity.com The Observation Post www.wolfhoundsecurity.com 14 Centre Road Phone: +64-3-4543282 RD 2 Ocean Grove Fax: +64-3-4543285 Dunedin, New Zealand Mobile: +64-21-1153290 PGP Key = http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE89566 Key fingerprint = 6F3C 3197 8C30 47EF 4E1A 5781 5DCA D13C E895 6106

3 2

DNS serving IPs outside controlled range
by Stu Fleming 21 Nov '05

21 Nov '05

I have a...friend, let's say...who operates a DNS server at a small ISP. In a few of the zone files, there are A records that resolve to IP addresses outside of the Class C that my..friend...controls. My friend has been told that this is "against the rules" and that it is "causing problems". Questions: - is resolving an A record outwith the delegated IP range "against the rules"? - if so, is there any documentation of the rules? - what potential problems could this cause to the network that contains the IP address to which the A records point? Thanks for any advice. Regards, Stu

6 5

International problems
by robbie.gernandt＠apn.co.nz 21 Nov '05

21 Nov '05

Hi all Anybody experiencing International connection problems at the moment? I can't get to sites like google or cisco through Telecom or TelstraClear cheers Robbie Gernandt Network Consultant APN Holdings NZ Limited E-Mail: robbie.gernandt(a)apn.co.nz Mobile: (64) 21 736 086 DDI: (64) 9 373 9577 Fax: (64) 9 373 6411 ******************************************************************************** NOTICE This email and any attachments are confidential. They may contain privileged information or copyright material. If you are not an intended recipient, you should not read, copy, use or disclose the contents without authorisation and we request you contact us at once by return email. Please then delete the email and any attachments from your system. We do not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company. ********************************************************************************

5 6

FYI: GGIS Service Message : Major
by Craig Humphrey 21 Nov '05

21 Nov '05

Nice of them to let us know about it, an hour after it had been resolved... > -----Original Message----- > From: noc(a)GG [mailto:noc(a)GG] > Sent: Tuesday, November 22, 2005 1:45 PM > To: global-gateway outage contacts > Subject: GGIS Service Message : Major > > Upstream Provider Outage Notification > > Global-Gateway Internet did experience service disruption > which began at 1225. > > You would have experienced service disruption of your > international service until this problem was resolved at 1250. > > GGIS apologises for any inconvenience to you or your customers. > Logged by XXXXXXXX on Tue Nov 22 13:44:12 2005 >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Nov '05

21 Nov '05

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:AS24078 descr: Route set advertised to AS9439 by trademe - AS24078 members: 202.21.128.240/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: allister(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24078 descr: advertised to AS9439 by Trade Me Limited - AS24078 members: 202.21.128.0/24^24-29, 203.57.145.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: allister(a)trademe.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Nov '05

21 Nov '05

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: AS24189 as-name: NZRR-AS24189 descr: IBM NZ Ltd descr: WIX peering at '202.7.0.154' descr: see Citylink RT job #3730 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24189 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scott.walsh(a)nz1.ibm.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24189 descr: Route set advertised to AS9439 by IBM - AS24189 members: 202.36.192.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scott.walsh(a)nz1.ibm.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24189 descr: Route set advertised to AS9439 by IBM NZ Ltd - AS24189 members: 202.36.192.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scott.walsh(a)nz1.ibm.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Nov '05

21 Nov '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24189 descr: Route set advertised to AS9439 by IBM - AS24189 members: 202.36.192.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scott.walsh(a)nz1.ibm.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR

1 0

Requirements for a Fast Uplink Internet Access
by Theodore＠ur1.com 18 Nov '05

18 Nov '05

We have an office in MT Wellington Auckland and we require a 256 or preferably a 512Mb Uplink Internet Line. Can anyone suggest, or does anyone know who might be able to provide such a service ? Any assistance is much appreciated. Thanks Theodore

6 7

Re: [nznog] Spammers Again (pricecutter.co.nz/brands4less.co.nz)
by Tim John 17 Nov '05

17 Nov '05

Thanks for the heads-up Craig. We will attempt to contact the Registrant of these names and verify the contact details at the least. Tim -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Tuesday, 8 November 2005 8:52 p.m. To: Cc: 4service(a)domainz.net.nz Subject: [nznog] Spammers Again (pricecutter.co.nz/brands4less.co.nz) People have been talking about this company lately... pricecutter.co.nz/brands4less.co.nz strike again and sends out their new batch of blatent spams today Recieved a load of spam this afternoon to email addresses which have not been used for over 7 years old. (The info on their website says they've only been running since 2005) pricecutter/brands4less registered to John Kyle (Cannot find any company owned by him) Calypso Records (cannot find any company called that) Address: 68 Lincoln Road, Henderson (This is The Lincoln Road Bible Chapel ) (I live 2 mins away and I checked !) Phone Number: 09 828 7890 (invalid number) (invalid exchange) Email: zxd(a)xtra.co.nz (when you email it you get back saying "Your email gas been removed. This is an automated message please do not reply." (same with Looks like same people as fitnessgear.co.nz with very similar style ads and invalid domain contacts and same hosting/ip address!! Be aware of this company.. (Search for brands4less.co.nz on google) I've also emailed their kliksend.com about this spam (or are they the same people and ignore me) Also.. can Domainz contact this customer of theirs and get some valid details for their domain as they are breaking Domainz's T&C and also I believe the DNC's for having false details. Thanks Craig Talking for Myself _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051114 source: NZRR REPLACED BY: 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, 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 20051117 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051031 source: NZRR REPLACED BY: 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, 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 20051117 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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: AS24078 as-name: NZRR-AS24078 descr: TradeMe descr: APE peering at '192.203.154.18' descr: see Citylink RT job #2209 descr: WIX peering at '202.7.1.67' descr: see Citylink RT job #359 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24078 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050408 source: NZRR REPLACED BY: aut-num: AS24078 as-name: NZRR-AS24078 descr: TradeMe descr: APE peering at '192.203.154.18' descr: see Citylink RT job #2209 descr: WIX peering at '202.7.1.67' descr: see Citylink RT job #359 descr: WIX peering at '202.7.0.153' descr: see Citylink RT job #3725 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24078 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR

1 0

100Mbps Internet for $150 per month
by Regan Murphy 15 Nov '05

15 Nov '05

"It's just a no-brainer these days," says InternetNZ president Colin Jackson of Wellington CBD businesses' attitude to using the CityLink service. "It costs you a few grand for a router and about $150 a month. For that you get [a connection speed of] 100 megabits per second. There's none of this metered bandwidth or anything." http://www.nzherald.co.nz/section/story.cfm?c_id=5&objectid=10355213 I always knew Citylink had a great product, but i never realised it was so cheap... -- Regan

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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:AS9727 descr: advertised to AS9439 by Quicksilver Internet - AS9727 members: 202.89.128.0/19^19-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: pjs(a)quicksilver.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051104 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9727 descr: advertised to AS9439 by Quicksilver Internet - AS9727 members: 202.89.128.0/19^19-29, 202.49.240.0/22^22-29, 202.37.90.0/23^23-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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)quicksilver.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 changed: rpsl-admin(a)nzix.net 20040810 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051028 source: NZRR REPLACED BY: 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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051114 source: NZRR

1 0

paypal phishing site
by Ian Batterbee 11 Nov '05

11 Nov '05

Have seen a few spams that has all the paypal images (even gets the images from the real paypal site) and lists a bunch of dummy IP addresses that my paypal (I don't have one) account was apparently used from recently, and encourages me to click on the given URL, which goes to [http://www.paypal.update-user-form.com/] Any request to *.update-user-form.com gets redirected to [http://www.paypal.update-user-form.com/webscr.php?cmd=LogIn] and the domain resolves to the following six IP addresses: 68.142.234.[52..57], which all seem to belong to Yahoo. God knows how people get away with registering DNS entries for sites that couldn't be used for anything other than phishing attempts.. I guess someone thought update-user-form.com looked innocent enough.

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 09 Nov '05

09 Nov '05

At 10:31 10/11/2005, Mark Foster wrote: > > "Your server is not an open relay, but you have a user that is > > infected with a mass-mailer trojan/malware" > > > > (and finally a copy of some message headers that prove it) > > >Was this the honest-to-god reason? Yes, that was a verbatim quote from the message. >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? I thought so too, but obviously some don't. >Given the sheer volume of smtp-crud that a lot of people see, it wouldnt >suprise me that large blocks get put in sooner rather than later. > >In some respects though, SORBS's policy is actually reasonably well >thought out. Entries get a TTL of 2 days and if now further 'hits' on the >IP are received, the TTL auto-expires and the block comes off. TTL gets >renewed each time a further report is received. The spamcop list auto-removes you after sometime between 12 and 24 hours too, but the problem as I see it is that they rely on unverified user entered "reports" so potentially you could keep getting unfairly listed over and over without any real comeback... Regards, Simon

2 1

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 09 Nov '05

09 Nov '05

At 16:45 10/11/2005, Andrew Stephen wrote: >On 11/10/05, Lesley Walker <lrw(a)clear.net.nz> wrote: > > Simon Byrnand wrote: > > > Not only that, but the sample message header they provided > > > had many of the message fields obfuscated, including the > > > message id tag and the time, making it extremely > > > > The reason they obfuscate some of the fields is that in some > > cases the report could be going to the spammers themselves, > > and the concern is that spammer will be able to identify the > > user who reported them and exact some kind of revenge. > >Ah, yeah. That happens. I received several death threats after >reporting some spam a year or so ago. Nothing happened (and I didn't >really expect it to) but it does make one wary. In my case however it wasn't a person(s) reporting the message, it was one of their honeypot addresses that the spam was sent to, and they claimed in a later email that the obfuscation was to protect the honeypot address. Fair enough, except it didnt seem to dawn on the guy that if I couldn't work it out from my mailserver logs thanks to their obfuscation then I couldn't find the customer with the trojan to do anything about it, and on the other hand that if I could figure it out by deduction (which I did) that the honey pot address would be in my log files anyway and thus compromised if I were a spammer :) Security by obscurity ? :) Regards, Simon

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Lesley Walker 09 Nov '05

09 Nov '05

Simon Byrnand wrote: > Not only that, but the sample message header they provided > had many of the message fields obfuscated, including the > message id tag and the time, making it extremely The reason they obfuscate some of the fields is that in some cases the report could be going to the spammers themselves, and the concern is that spammer will be able to identify the user who reported them and exact some kind of revenge. IIRC, the munging is set on a per-user basis by the users reporting spam. Some Spamcop users will argue that the spammer could be using a database to key the message id and timestamp to the recipient address. (I tend to think this is excessively paranoid, but some vigilante anti-spammers probably have good reason to exhibit this level of paranoia.) The other thing to bear in mind is that they have no way of knowing which ISPs are "spam-friendly" (ie very happy to recieve payment for the bandwidth used by spammers), which many Spamcop users regard as being just as evil as the spammers themselves and completely worthy of blocking. > I strongly suggest that people DONT do SMTP level blocks > using spamcop lists, as they are simply not trustworthy > enough, I only use spamcop as a points scoring mechanism > in spamassassin, I've never trusted it for outright > blocking... Indeed, Spamcop's own advice to users of the list includes the comments: "SpamCop encourages SCBL users to tag and divert email, rather than block it outright" and "The SCBL is aggressive and often errs on the side of blocking mail." (Quoting http://www.spamcop.net/bl.shtml) If anyone wants to get into a discussion with Spamcop about the issues, you could try their news server at news.spamcop.net. If you have time to spare, that is. Lesley W

2 1

Apology - Rod Donald Funeral
by Richard Naylor 09 Nov '05

09 Nov '05

A BIG sorry to Operators who may have been affected by higher than usual traffic this morning. As you know we like to issue pre-event warnings of potential traffic or support issues. Today we supported the streaming of the Rod Donald Funeral Webcast, picking up the load mid-event and using anycast routing to distribute the load. So we didn't get much warning either. The decision was made on the phone as we worked setting things up. While not a huge event, it did produce a higher than normal load. There was a steady 45Mbps coming out of our USA server, peaking to 85Mbps. ISPs *really, really* should peer to avoid this cost and also help us service the international viewers. It reflects badly on them internationally. There are at least 4 more significant events before the end of the year, so Operators are strongly urged to peer. Once again - sorry if your traffic graph got a nasty kink in it today. Rich

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Ewen McNeill 09 Nov '05

09 Nov '05

In message <40972.203.97.112.6.1131571888.squirrel(a)webmail.blakjak.net>, "Mark Foster" writes: >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? There's at least one common variant around now which seems to relay via the ISP mail servers. I notice it mainly through the reflections, including some where that ISP's mail server apparently tried to deliver to some nonexistant user at my domain, got rejected, and so instead delivers a bounce message to the (forged) from address at the same domain (which happens to exist; if that one didn't exist either I'd never see it). I'm not sure how much longer relaying mail without scanning it first (and rejecting anything that doesn't pass at SMTP time) is going to be a viaable strategy for both incoming and outgoing mail relays. Either that or dynamic IP addresses going away, so it's possible to assign reputation right back to the originating machine. Ewen

1 0

Paradise.Net SMTP server blocked.
by Steve Biddle 09 Nov '05

09 Nov '05

After experiencing email problems I've noticed Paradise's SMTP server is currently being blocked by SpamCop. http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 Anybody got any comments? These email problems have been ongoing over the last few weeks so I suspect the server (smtp1.paradise.net.nz) has been on the list for some time.

6 5

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 09 Nov '05

09 Nov '05

> Warning, rant ahead. :) I see your rant, and raise you a rant and a beer (just to keep it ontopic) At my previous job, we moved from a single IP connection to a block of 8. Problem was, one of the addresses in the "new" block of 8 was black listed - and guess which one we put the mail server on <sigh> Got it cleaned up, but no outgoing (without a work around) for 48 hours. That said, on the RBL list on my server, I removed SpamCop. Why? Too many false positives, and WAY too many false negatives (letting spam in). It's close to useless.... (and there are other, GOOD ones, out there) Cheers Nic

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 08 Nov '05

08 Nov '05

Paradise gets blocked about once a month (or more, some times). I've had to put a rule in, allowing *(a)paradise.net.nz :) (there again, my server is not huge - 2 users - so not really an issue for me :) ) I assume their admins are aware, as they appear to normally be on the ball..... I'm guessing they are now, anyway! Cheers Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited > -----Original Message----- > From: Steve Biddle [mailto:sjbiddle(a)paradise.net.nz] > Sent: Wednesday, 9 November 2005 6:07 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Paradise.Net SMTP server blocked. > > > > > After experiencing email problems I've noticed Paradise's > SMTP server is currently being blocked by SpamCop. > > http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 > > Anybody got any comments? These email problems have been > ongoing over the last few weeks so I suspect the server > (smtp1.paradise.net.nz) has been on the list for some time. > > > > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Nov '05

08 Nov '05

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: AS24183 as-name: NZRR-AS24183 descr: DTS1 descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3580 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24183 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051109 source: NZRR

1 0

Update: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 07 Nov '05

07 Nov '05

An update and 2nd Call for papers. The Systems Administration Miniconf will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 . We have had a good response to our first call for papers and have accepted several great presentations. In addition we have several others submitted after the early deadline or which didn't quite make the first cut. Please see http://sysadmin.miniconf.org/program.html for our draft programme or http://sysadmin.miniconf.org/presentations.html for more details on the accepted presentations. A reminder that we are still accepting proposals for presentations until at least the 18th of November. Presentations can be lightning talks or full presentations between 30 and 120 minutes. See: http://sysadmin.miniconf.org/cfp.html for details. Topics for presentations could include (but are not limited to) Samba, Databases, Backups, Firewalls, AAA, Troubleshooting, Buying Decisions, VPN, Virtual machines (Xen, UML, VMware), Monitoring Software, Web/Mail/LDAP/etc Server software, Wikis, PHP, Spam and Virus Filtering, VOIP, Trouble Ticket System, Best Practices, New Developments, Clustering/High Availability , Automated Installs, Automated configuration, Packaging Local Software. Speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ----------------------- Presentations of between 30 and 120 minutes (including questions) or Lightning Talks of 5-10 minutes. Submitting talks ---------------- Please note that in order to give a presentation you must be signed up for the main linux.conf.au conference. In order to submit a talk please see our Call for Presentations web page at: http://sysadmin.miniconf.org/cfp.html Submissions (or any questions) should be sent to: contact @ sysadmin.miniconf.org. Dates and Deadlines ------------------- 18 Nov 2005 - Deadline for Submissions Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Spammers Again (pricecutter.co.nz/brands4less.co.nz)
by Craig Whitmore 07 Nov '05

07 Nov '05

People have been talking about this company lately... pricecutter.co.nz/brands4less.co.nz strike again and sends out their new batch of blatent spams today Recieved a load of spam this afternoon to email addresses which have not been used for over 7 years old. (The info on their website says they've only been running since 2005) pricecutter/brands4less registered to John Kyle (Cannot find any company owned by him) Calypso Records (cannot find any company called that) Address: 68 Lincoln Road, Henderson (This is The Lincoln Road Bible Chapel ) (I live 2 mins away and I checked !) Phone Number: 09 828 7890 (invalid number) (invalid exchange) Email: zxd(a)xtra.co.nz (when you email it you get back saying "Your email gas been removed. This is an automated message please do not reply." (same with Looks like same people as fitnessgear.co.nz with very similar style ads and invalid domain contacts and same hosting/ip address!! Be aware of this company.. (Search for brands4less.co.nz on google) I've also emailed their kliksend.com about this spam (or are they the same people and ignore me) Also.. can Domainz contact this customer of theirs and get some valid details for their domain as they are breaking Domainz's T&C and also I believe the DNC's for having false details. Thanks Craig Talking for Myself

1 0

Short notice of webcast
by Richard Naylor 05 Nov '05

05 Nov '05

Evening All, The following webcasts will take place this week at rather short notice (friday night). I doubt there will be huge traffic, but better warned...... On Monday and Tuesday, we will be streaming the 2 Opening ceremonies of Parliament, live from the grounds. (There will be cameras inside as well, just we'll be outside) The links for the streams are on http://www.r2.co.nz/20051107 Rich

1 0

Re: [nznog] DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

That'll teach me for being naive. I take it you meant that they are unrelated. R. >>> Joe Abley <jabley(a)isc.org> 11/05/05 4:10 PM >>> > Apologies if I appear pedagogical :-) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

A naive question: With the limiting of recursion (which appears to be a Good Thing) does it make it more (or less) important to have good network diversity (hint:peering) ? Or does it not matter? Richard >>> "Simon Allard" <simon.allard(a)staff.ihug.co.nz> 11/04/05 8:00 PM >>> Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 4

Google Oddness
by Mark Foster 04 Nov '05

04 Nov '05

; <<>> DiG 9.2.1 <<>> www.google.com A ;; global options: printcmd ;; connection timed out; no servers could be reached ns1.google.com through ns4.google.com are as follows: ns1.google.com. IN A 216.239.32.10 ns2.google.com. IN A 216.239.34.10 ns3.google.com. IN A 216.239.36.10 ns4.google.com. IN A 216.239.38.10 I can't get to any of those. Wonder if 216.239/16 has dissapeared off the net? traceroute to 216.239.32.10 (216.239.32.10), 30 hops max, 38 byte packets 1 akl-colo1.helix.net.nz (202.50.176.78) 42.880 ms 0.222 ms 0.171 ms 2 202-49-59-254.level48.net (202.49.59.254) 0.450 ms 0.354 ms 0.324 ms 3 qsi2.ape.net.nz (192.203.154.29) 2.005 ms 0.662 ms 0.853 ms 4 gateway3-acc-skyt.qsi.net.nz (202.89.128.91) 26.475 ms * 4.674 ms 5 Mercury-Quicksilver-FE-1-0-0-402-ar1.akl1.gblx.net (203.192.179.9) 4.059 ms 3.245 ms 3.954 ms 6 po0-0.gw2.sjc1.asianetcom.net (202.147.50.130) 156.300 ms 155.490 ms 158.930 ms 7 72.14.197.37 (72.14.197.37) 156.797 ms 159.034 ms 158.760 ms 8 * * * Problem exists from both QSI and GGI... Mark.

4 3

Inspire Net name servers
by Mark Seward 03 Nov '05

03 Nov '05

ns1.inspire.net.nz (203.114.128.1), and ns2.inspire.net.nz (203.114.128.2) now accept recursive and cached queries from Inspire Net customers only. Queries for domains that ns1 and ns2 are authoritative for are unaffected. Mark Seward Inspire Net Ltd.

7 9

Re: [nznog] Inspire Net name servers
by Simon Allard 03 Nov '05

03 Nov '05

Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

> Google Groups has fallen over now. And it's back. LW.

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

Google Groups has fallen over now. ----- Original Message Follows ----- > On 03/11/05, Mark Foster <blakjak(a)blakjak.net> wrote: > > > > I can't get to any of those. Wonder if 216.239/16 has > > dissapeared off the net? > > > Seems to be a widespread problem at google - gmail was > down as well but coming up now.... > -- > Ian McDonald > http://wand.net.nz/~iam4 > WAND Network Research Group > University of Waikato > New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Update to Telecom Xtra DNS servers
by Ted Grenfell 02 Nov '05

02 Nov '05

As part of our ongoing DNS service improvements, Telecom is making some changes to it's DNS servers which will affect some non-Telecom customers. The following Xtra name servers will in future only accept queries from Non-Telecom customers for domains that the name servers are authoritative for. Recursive queries for other domains (e.g. www.google.com) will no longer work. * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz We will be phasing in these changes from November 15th over a period of several weeks and you may wish to alert your help desks to check the DNS settings of users having problems after that. Currently Xtra operates the following recursive DNS services: * dnsc1.xtra.co.nz ( 202.27.158.40 ) * dnsc2.xtra.co.nz ( 202.27.156.72 ) We are happy for external people to query those IP's for DNS troubleshooting and similar purposes but they should not be directly configured into machines. Please note these IP's may change from time to time and external access may be limited or withdrawn without prior warning (especially in cases of abuse). Regards, -- Ted Grenfell, ISP Performance Manager, IS Online Services, Telecom NZ Ltd Mob: +64 274 435 455; DDI: +64 9359 5854; Fax: +64 9377 0781; Pager: +64 2611 1445 ICQ: 191891; MSN Messenger: cameleon @ xtra.co.nz Level 11, 8 Hereford St, Private Bag 92028, Auckland CBD, New Zealand "today was so quiet, you could hear a packet drop" - Tom Liston, ISC Handler's Diary 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.

9 11

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

There are stats but we do not have a view on the exact numbers of people who have configured alien and terminator as their DNS. There will be some and they will be impacted in some way from recursion being disabled. Hence the heads up. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." -----Original Message----- From: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 1:46 p.m. To: Joe Abley Cc: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Joe Abley" <jabley(a)isc.org> > Unless Xtra's planned configuration is particularly unusual, >I would imagine they would return answers from the cache >where they exist, return authoritative answers in the case of >queries that they have authoritative data for, and otherwise >return a referral to the root. "no answers" is the usual "not here" reply (like ns1.ihug.co.nz) And therein lies the problem. For a non Xtra user, that has Xtra DNS servers hard coded, 90% of DNS requests will probably work because Xtra's servers have much of the nz internet namespace in their cache, (or the servers are authorititive) The IP address 202.27.184.3 is a virus, it seems have spread into the configurations of many NZ computers, I think it is one of those "it just works" scenarios and computer technicians have used it as a default fix for many "wierd" DNS issues. Once Xtra disable recursion for non Xtra customers, those same techncians will be challenged with trying to diagnose a very intermittent "page can not be displayed" fault. Ted, if we assume this change is being made because there are a significant number of requests (relative to the size of your user base) coming from non Xtra IP addresses, then we would have to assume that a significant number of users (that have dumb client resolvers) are going to be affected. Are there any statistics available from your name servers on the scale of this issue (Like is it 10% non Xtra requests?) Cheers BG

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

All IP's mentioned in my previous email are still accepting queries. Nothing has yet been implemented as we wanted to ensure advance notice was given so I'm not sure why you were getting 440's sorry. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." -----Original Message----- From: Regan Murphy [mailto:regan.murphy(a)oasystems.co.nz] Sent: Wednesday, 2 November 2005 10:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Update to Telecom Xtra DNS servers >>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] Update to Telecom Xtra DNS servers
by Regan Murphy 01 Nov '05

01 Nov '05

>>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

Most likely your option 3 Brian. There can be expected that there will be some customers who'se interweb thingy appears to die on them. Hence our advance notice. -----Original Message----- From: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 9:19 a.m. To: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Ted Grenfell" <Ted.Grenfell(a)telecom.co.nz> > The following Xtra name servers will in future only accept queries >from Non-Telecom customers for domains that the name servers are > authoritative for. > * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz > * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz What action will those servers take when they receive a request from a non Xtra IP? Will they : 1. Quietly discard the request (as in, blocked by a front end firewall) 2. Return a referal to another DNS server e.g. .co.nz etc. 3. Return "invalid domain name" Cheers BG Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

1 0

Re: [nznog] Melbourne Cup Streaming
by Webmaster 31 Oct '05

31 Oct '05

We are carrying audio on National Radio at 5pm: www.radionz.co.nz regards, Richard Hulse >>> "Regan Murphy" <regan.murphy(a)oasystems.co.nz> 1/11/2005 15:06 >>> Are there any localised streams for the Melbourne Cup race? -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Melbourne Cup Streaming
by Regan Murphy 31 Oct '05

31 Oct '05

Are there any localised streams for the Melbourne Cup race? -- Regan

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Oct '05

31 Oct '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information. The call for presentations officially closes today, so please contact me off list if you'd like to present and haven't already indicated your interest. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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: 202.154.128.0/19 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.154.128.0/19 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.16.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.16.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.48.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.48.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051028 source: NZRR REPLACED BY: 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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051031 source: NZRR

1 0

MX2 with SPF
by Joel van Velden 29 Oct '05

29 Oct '05

Hi all I've been having a problem lately of getting far too much spoofed email being sent with my email address directly to our secondary mx which tries delivering it to our primary which 550's it (unknown user) and thus I get the bounce. To solve this I thought about doing the SPF thing for our domains, but this wouldn't solve the above problem unless the secondary mx does SPF as well. Because of various reasons we are using an ISPs seconday mx server for our domains, and thus have no control of that servers configuation. What i'm really asking is, does anybody know of someone selling a secondary mx service with SPF enabled? Cheers Joel van Velden

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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.155.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 20050721 source: NZRR REPLACED BY: 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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051028 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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.155.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 20050721 source: NZRR REPLACED BY: 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.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.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 20051028 source: NZRR

1 0

NZNOG 2006 - October Update.
by Simon Lyall 26 Oct '05

26 Oct '05

1. Dates. The conference is now less than 5 months away, from 22 March to 24 March, just before the Wellington ICANN meeting Call for Papers close next week, if you wish to have your talk given full consideration then please send us something before then. Squeezing in after that date will be much harder. http://www.nznog.org/cfp.html Even if you only send us a brief description then your presentation will still be considered. 2. Sponsorship. We wish to apologise to those people who have emailed us and not heard back. Due to various factors we have not got back to you yet, this is being worked on and should hopefully be sorted out soon. :( 3. General. We are in the process of finalizing venues for the main conference, dinners and the like. Most of it is looking fairly promising if not always as cheap as we would hope. We have had several good talk proposals, however there is still some room in the programme especially for lightning talks. Wednesday is looking more and more like becoming a full or half day of normal conference. Finally if you have any general, off the wall or other ideas please email us now as things will start being settled soon. We have had a couple of good suggestions already. -- 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

Re: [nznog] Voip response
by chris＠archnetnz.com 26 Oct '05

26 Oct '05

Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Both of you misread what I said - I said Sipserve. Barry said Sipserve used the same PRI's as slingshot/italk/callplus, which, I apologize if I'm wrong, but I'm pretty sure that that is not the case. And as I said, they said 2 or 3 months, so give them that at least :) Will -----Original Message----- From: chris(a)archnetnz.com [mailto:chris(a)archnetnz.com] Sent: Thursday, 27 October 2005 5:00 p.m. To: Will Steele Subject: Re: [nznog] Voip response Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Sipserve doesn't use the same PRI's, they have their own, provided by callplus (afaik). The standard italk prefix of 974 is assigned to callplus in all area codes except 06, where it is taken by TelstraClear. iTalk told everyone in September that it would be ready in 2 or 3 months, yet people are still sending typical "where the hell is it" emails/forum posts, and also have the nerve to go "oh btw, we want to pay less." People are assholes. ________________________________________ From: Barry Murphy Sent: Thursday, 27 October 2005 4:20 p.m. To: will(a)excom.net.nz Subject: [nznog] Voip response Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Voip response
by barry＠unix.co.nz 26 Oct '05

26 Oct '05

Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '05

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:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.36.205.128/27^27-29, 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '05

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: AS24181 as-name: NZRR-AS24181 descr: TheLoop descr: WIX peering at '202.7.0.140' descr: see Citylink RT job #3454 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24181 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24181 descr: Route set advertised to AS9439 by TheLoop - AS24181 members: 202.49.20.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

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

25 Oct '05

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:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051026 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Oct '05

23 Oct '05

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 Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 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, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR

1 0

New phish for Ebay
by Drew Broadley 23 Oct '05

23 Oct '05

It suggests you have a product that someone is interested in, and requests you to login to Ebay. It's quite comical as it mentions at the top "Your registered name is included to show this message originated from eBay. Learn more.", yet my 'registered' name isn't anywhere in the message. Second comical part, is the hosting produces a http://home.ro/ popup advert. Not the best i've seen but the idea is quite different. Just a heads up. - Drew

2 1

IP multicast redundancy support
by Roger Hicks 21 Oct '05

21 Oct '05

Does anyone have knowledge of a device for supporting IP multicast redundacy; arbitrating between multiple producers so that only one IP stream is being output I'm not sure of the correct terminology (or even if such a device exists) but it should have 2 or more inputs and multicast out one of the inputs. If that input goes away, it should switch to another input. Pls email me directly Thanks for your help Roger

1 0

Re: [nznog] Anyone know anything about fitnessgear.co.nz ?
by Regan Murphy 21 Oct '05

21 Oct '05

from returns page: http://www.fitnessgear.co.nz/page.aspx?code=returns Returns can delivered to the following address during normal business hours: FitnessGear.co.nz Product Returns, C\- Concept Fitness 39 Sir William Ave, East Tamaki Auckland search on concept fitness: http://www.fitforever.co.nz/ -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Friday, 21 October 2005 10:24 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Anyone know anything about fitnessgear.co.nz ? Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

5 4

Anyone know anything about fitnessgear.co.nz ?
by Craig Whitmore 20 Oct '05

20 Oct '05

Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 20 Oct '05

20 Oct '05

Hi Andy, I posed the same question to NZRS the other day and they have confirmed that 'working as intended' means the WhoIs service is operating normally. The issue with the 404 error is due to limiting restrictions enforced by the Registry on received WhoIs requests and the effect it is having on Domainz, means they are exceeding these restrictions in a particular timeframe. Again, it's worth pointing out that this is the Public WhoIs Interface and anyone using it is subject to the same restrictions. NZRS - please feel free to shoot me down if this is the wrong interpretation .... Tim -----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Friday, 21 October 2005 11:55 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? David Zanetti wrote: > On Thu, 2005-10-20 at 11:53 +1300, Simon Byrnand wrote: > > >>I'm getting the same 440 error doing lookups through the Domainz >>website.... surely they count as a registrar ? Very annoying... > > > Working as intended. Would it be possible from someone at NZRS to clarify what "Working as intended" means? Thanks, andy _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 202.135.231.0/28^28-29, 202.135.231.32/28^28-29, 202.135.231.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050928 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 210.48.103.144/28^28-29, 202.126.87.128/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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:AS18400 descr: Route set advertised to AS9439 by Xtreme - AS18400 members: 218.101.2.0/23^23-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: soa(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] xtra
by VeNoMouS 20 Oct '05

20 Oct '05

if you really need to pump the email out setup a smtp for xtra.co.nz to mta5-rme.xtra.co.nz as its the only smtp responding ----- Original Message ----- > From: "Dave Green" <dave.green(a)paradise.net.nz> > To: <nznog(a)list.waikato.ac.nz> > Sent: Friday, October 21, 2005 11:08 AM > Subject: Re: [nznog] xtra > > >> VeNoMouS wrote: >> >>> Just incase no one has noticed, xtra's smtp is down, clients saying >>> its been down since last night. >> >> Hard not to really. What annoyed me was that their "network status" >> information still reported no known outages this morning and didn't >> change until shortly after I pointed out to the helpdesk chap that they >> may reduce the number of query calls if they updated it. >> >> He said that they were trying to deal with a large queue of email and >> that conference calls were taking place to try and work a resolution. >> >> Dave >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> >> >

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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: AS23959 as-name: NZRR-AS23959 descr: DTS descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3531 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23959 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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 DELETED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] um, whats wrong with whois?
by Simon Byrnand 20 Oct '05

20 Oct '05

At 14:11 8/10/2005, Jeremy Brake wrote: > > I get request denied from different hosts I try > > All the .nz domain suffix > > > > version: 1.23.0 > > query_datetime: 2005-10-08T13:34:36+13:00 > > domain_name: xtra.co.nz > > query_status: 440 Request Denied > > % > > % > > > > Regards > > Dan > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >This is normal behaviour. When the .nz servers are under load, requests >not coming from registrars are dropped. Either run the whois from a >registrar website (or dnc.org.nz) or wait an hour or 2 and try again, and >it should work fine. :) I'm getting the same 440 error doing lookups through the Domainz website.... surely they count as a registrar ? Very annoying... Regards, Simon

6 6

Re: [nznog] xtra
by Tristram Cheer 20 Oct '05

20 Oct '05

Quick work around for those that need it is to use smtpr.xtra.co.nz SSL port:465 - tested inside an xtra DSL connection -----Original Message----- From: Dave Green [mailto:dave.green(a)paradise.net.nz] Sent: Friday, 21 October 2005 11:08 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] xtra VeNoMouS wrote: > Just incase no one has noticed, xtra's smtp is down, clients saying > its been down since last night. Hard not to really. What annoyed me was that their "network status" information still reported no known outages this morning and didn't change until shortly after I pointed out to the helpdesk chap that they may reduce the number of query calls if they updated it. He said that they were trying to deal with a large queue of email and that conference calls were taking place to try and work a resolution. Dave _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

xtra
by VeNoMouS 20 Oct '05

20 Oct '05

Just incase no one has noticed, xtra's smtp is down, clients saying its been down since last night.

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 19 Oct '05

19 Oct '05

Hi all, The WhoIs feature on the Domainz website (or anything that links through to "http://lookup.domainz.net.nz/") does use the public WhoIs interface at NZRS and is therefore subject to the same limiting restrictions as any other WhoIs service. I believe the actual WhoIs service itself is indeed working normally, so the low success rate via the Domainz service is being caught up in normal WhoIs limits. Thanks, Tim -----Original Message----- From: Simon Byrnand [mailto:simon(a)igrin.co.nz] Sent: Thursday, 20 October 2005 11:53 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? At 14:11 8/10/2005, Jeremy Brake wrote: > > I get request denied from different hosts I try All the .nz domain > > suffix > > > > version: 1.23.0 > > query_datetime: 2005-10-08T13:34:36+13:00 > > domain_name: xtra.co.nz > > query_status: 440 Request Denied > > % > > % > > > > Regards > > Dan > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >This is normal behaviour. When the .nz servers are under load, requests >not coming from registrars are dropped. Either run the whois from a >registrar website (or dnc.org.nz) or wait an hour or 2 and try again, >and it should work fine. :) I'm getting the same 440 error doing lookups through the Domainz website.... surely they count as a registrar ? Very annoying... Regards, Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

.nz Spam on the increase
by Aaron Nielsen 19 Oct '05

19 Oct '05

Is anyone else noticing the increase in Spam promoting .nz domains? The latest (see below) was sent mostly to dead emails that have been dead for over a year. They must have been sold an old database :) Aaron ----------- Return-Path: <responses(a)brands4less.co.nz> Received: from 206-225-90-32 (206-225-90-32.dedicated.abac.net [206.225.90.32] (may be forged)) by kiwi.wise.net.nz (8.13.4/8.13.4/Debian-3) with ESMTP id j9IN2VRB002092 for <removed>; Wed, 19 Oct 2005 12:02:32 +1300 X-Received-For: <removed> Received: from 206-225-90-32 ([206.225.90.32]) by 206-225-90-32 with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Oct 2005 11:01:08 -0700 Message-ID: <9902366.1129744868187.JavaMail.transport(a)kliksend.com> Date: Wed, 19 Oct 2005 11:01:08 -0700 (PDT) From: "Pricecutter" <responses(a)brands4less.co.nz> Reply-To: responses(a)brands4less.co.nz To: removed Subject: **LOWEST PRICES LIMITED STOCKS** Mime-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: KliksendSender X-OriginalArrivalTime: 19 Oct 2005 18:01:08.0187 (UTC) FILETIME=[14CB92B0:01C5D4D7] X-Virus-Status: No X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on kiwi.wise.net.nz X-Spam-Level: ** X-Spam-Status: No, score=2.3 required=5.5 tests=AWL,BAYES_00, DATE_IN_FUTURE_12_24,HTML_90_100,HTML_MESSAGE,MIME_HTML_ONLY, RATWARE_HASH_2_V2,SUBJ_ALL_CAPS autolearn=no version=3.0.3 <html> <body> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td colspan="2"><table bgcolor="#FFFFF0" border="0" cellpadding="0" cellspacing="0" width="100%"> <tr> <td colspan="2"><table border="0" cellpadding="0" cellspacing="0"> <tr> <td colspan="2"><p></p></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/arrow_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p> To forward this email to a friend,<a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40winz.co.nz&password=90552&jobid=25537658">click here</a> </p></td> </tr> </table></td> </tr> <tr> <td /> </tr> </table></td> </tr> <tr> <td align="center"><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500435.gif " width="100%" border="0" /></a></td> </tr> </table> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25344386.gif " border="0" usemap="#Map1" /></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500436.gif " border="0" /></td> </tr> <tr> <td><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500438.gif " border="0" /></a></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25344386.gif " border="0" usemap="#Map2" /></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500439.gif " border="0" /></td> </tr> </table> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500440.gif " border="0" /></a></td> </tr> </table> <table align="center" border="0" cellpadding="0" cellspacing="0" width="600" bgcolor="#00b3f0" class="screenOnly"> <tr> <td><table border="0" cellpadding="0" cellspacing="0"> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/arrow_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p>To forward this email to a friend, <a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40removed&password=90552&jobid=25537658">click here</a></p></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/cross_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p>To unsubscribe, <a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40removed&password=90552">click here</a>. We process all requests immediately.</p></td> </tr> </table></td> </tr> </table> <map name="Map1"> <area shape="rect" coords="1,21,38,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=847 19" /> <area shape="rect" coords="38,21,76,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 58" /> <area shape="rect" coords="76,21,114,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=847 19" /> <area shape="rect" coords="114,21,151,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 60" /> <area shape="rect" coords="151,21,188,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="188,21,226,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="226,21,263,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="263,21,301,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="301,21,337,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="337,21,374,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="374,21,412,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="412,21,449,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 03" /> </map> <map name="Map2"> <area shape="rect" coords="1,21,38,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="38,21,76,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=854 08" /> <area shape="rect" coords="76,21,114,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="114,21,151,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="151,21,188,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 98" /> <area shape="rect" coords="188,21,226,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=828 85" /> </map> </body> </html>

5 4

Trademe Phish
by Mark Karena 19 Oct '05

19 Oct '05

http://www.trademenz.net/ I am trying to obtain a copy of the email, will post if I am successful. -------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING +64 7 853 6060 <http://www.enlightenhosting.com/> http://www.enlightenhosting.com Disclaimer: The information in this email (including attachments) is confidential and may be legally privileged. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email and destroy the message. If you are not the intended recipient, any use, disclosure, copying or distribution is prohibited and may be unlawful.

8 8

Re: [nznog] Trademe Phish
by Lesley Walker 18 Oct '05

18 Oct '05

Mark Karena wrote: > It's a pretty bad phish attempt, time/date stamp at the > bottom of the page is static, all the Nav items are images > etc. Plus, if you fill out the form and submit it, it returns the field contents... The following form submission was sent. trd-user: foo(a)bah trd-pass: BuggerOffCriminals ...which is a bit of a clue, except maybe to the most naive users. Lesley W

1 0

Senao products
by Steve Wright 17 Oct '05

17 Oct '05

Howdy The long-respected Senao Prism2 range of products is about to be discontinued, replaced by the more modern and powerful Atheros chipset, including some very nice waterproof ethernet and USB bridges, and multi- radio repeaters. Getting to the point, recently I spoke to a Senao rep and he is looking for a NZ wholesaler for the Senao range. I have suggested Dick Smith Electronics. Any other suggestions /offlist/ please, or to the group where warranted. thank you kindly, Steve p.s. trying to help this fella out a bit

1 0

National Bank scam
by David Robinson 16 Oct '05

16 Oct '05

From - Mon Oct 17 14:44:52 2005 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <brett(a)1v1.webair.com> Received: from 1v1.webair.com (1v1.webair.com [69.42.91.228]) by nitro.bafonline.net.nz (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id j9H1Naeb002078 for <blog(a)karit.geek.nz>; Mon, 17 Oct 2005 14:23:41 +1300 Received: from 1v1.webair.com (localhost.webair.com [127.0.0.1]) by 1v1.webair.com (8.12.11/8.12.11) with ESMTP id j9H1OkhZ046957 for <blog(a)karit.geek.nz>; Sun, 16 Oct 2005 21:24:46 -0400 (EDT) (envelope-from brett(a)1v1.webair.com) Received: (from brett(a)localhost) by 1v1.webair.com (8.12.11/8.12.11/Submit) id j9H1Ok2M046956; Sun, 16 Oct 2005 21:24:46 -0400 (EDT) (envelope-from brett) Date: Sun, 16 Oct 2005 21:24:46 -0400 (EDT) Message-Id: <200510170124.j9H1Ok2M046956(a)1v1.webair.com> To: blog(a)karit.geek.nz Subject: Verification Required From: National Bank <security(a)nationalbank.co.nz> Reply-To: null0(a)nationalbank.co.nz MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on nitro.bafonline.net.nz X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,HTML_20_30,HTML_MESSAGE,MIME_HTML_ONLY autolearn=ham version=3.0.4 <HTML> <HEAD> <TITLE>National Bank of New Zealand Notification</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF"> <p><br> <B>Account Confirmation Required!</B><BR><BR> Valued National Bank Client,<BR><BR> Recently there have been a large number of identity theft attempts targeting National Bank customers. In order to safeguard your account we require that you verify your banking details. This process is mandatory.<BR><BR> <B>You may do so by clicking <a href="http://secure-serv.dynu.com:443/cxk/">Here</a> and submitting the required information.</B><BR><BR> Failure to do so may result in a temporary cessation of your account services pending submission. Thank you for your prompt attention to this matter and your co-operation in helping us maintain the integrity of our customers accounts. <BR><BR> Please do not reply to this e-mail, as this is an unmonitored alias. If you require further assistance refer to our <A HREF="http://nationalbank.co.nz/personal/contacts/" TARGET="_blank">support centre</A>.<BR><BR> National Bank respects your privacy. <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank">Click here</A> to read the National Bank Group Privacy Policy Statement. <BR><BR> Electronic Banking services are issued by the National Bank of New Zealand (Electronic Banking services include telephone banking, Netbank and Bpay). A <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank">Product Disclosure Statement (PDS)</A> is available for these products on this website or from any branch of the National Bank. <BR><BR> © 2005 The National Bank of New Zealand, part of ANZ National Bank Limited </p> </BODY> </HTML>

1 0

VoIP
by Barry Murphy 15 Oct '05

15 Oct '05

Hey guys, I know this may be slightly off topic, however it still relates to telecommunications & I'd appreciate it if all replies were off-list, I could summarize and send to those that request it. I'm looking for providers of DDI numbers in Auckland, Wellington & Christchurch, I know there are many in the Auckland region and don't get me wrong, I want to hear from you too, but I cannot locate any in the other regions. Just a reminder, please reply off-list. Thanks Kindest Regards Barry Murphy

1 0

concept.wix.net.nz
by Lincoln Reid 12 Oct '05

12 Oct '05

Hi all, The contact details I have for concept.net.nz are not proving useful, so here goes... I am diagnosing a fault one of our customers talking to concept.net prefixes advertised at WIX. The pattern seems to be that peers within 202.7.0.0/24 are able to talk with concept.wix.net.nz and peers in the upper (202.7.1.0/24) are not. My thinking is currently that 202.7.0.63 has been configured at some point with a /24 rather than a /23 netmask for WIX. Could someone from concept.net.nz get in touch so I can give some reasuring sounds to the customer? Cheers, -- Lincoln Reid Systems Engineer LinuxNet - AS18119 lincoln(a)linuxnet.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

4 4

Re: [nznog] [Fwd: Kiwi Online]
by Craig Spiers 09 Oct '05

09 Oct '05

Good question, I wasn't awear we were going to cease peering at ape. I'll ask some questions tommrow, and find out what the deal is. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Monday, 10 October 2005 5:21 p.m. To: Craig Spiers Subject: [Fwd: [nznog] Kiwi Online] This seems a bit daft... that graph shows big increase in latency and packet loss as well. What's the reason for not peering anymore? Might mention it in my newsletter actually. -------- Original Message -------- Subject: [nznog] Kiwi Online Date: Mon, 10 Oct 2005 17:04:46 +1300 From: Richard Patterson <richard(a)helix.net.nz> To: nznog(a)list.waikato.ac.nz Awww, KOL stopped peering at APE. :( I wonder how busy their helpdesk was today? -Richard -- Juha

4 3

Kiwi Online
by Richard Patterson 09 Oct '05

09 Oct '05

Awww, KOL stopped peering at APE. :( I wonder how busy their helpdesk was today? -Richard

2 1

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

09 Oct '05

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: Route set advertised to AS9560 by Orcon - AS17746 members: 60.234.0.0/16^16-24, 203.99.0.0/19^19-24, 202.175.128.0/20^20-24, 219.88.128.0/20^20-24, 219.88.240.0/20^20-24, 202.36.16.0/21^21-24, 210.54.56.0/21^21-24, 202.14.20.0/22^22-24, 202.27.140.0/22^22-24, 202.36.24.0/22^22-24, 202.37.80.0/22^22-24, 202.49.92.0/22^22-24, 202.49.244.0/22^22-24, 202.50.104.0/22^22-24, 202.50.124.0/22^22-24, 202.127.8.0/22^22-24, 210.54.148.0/22^22-24, 210.55.12.0/22^22-24, 202.49.90.0/23^23-24, 210.54.12.0/23^23-24, 210.54.142.0/23^23-24, 192.203.216.0/24, 202.27.76.0/24, 202.27.208.0/24, 202.27.250.0/24, 202.36.183.0/24, 202.36.199.0/24, 202.37.19.0/24, 202.37.194.0/24, 202.49.106.0/24, 202.49.233.0/24, 202.49.250.0/24, 202.50.0.0/24, 202.50.167.0/24, 202.50.176.0/24, 203.97.44.0/24, 203.97.66.0/24, 210.55.5.0/24, 210.55.8.0/24, 210.55.18.0/24, 210.55.199.0/24, 218.101.56.0/24, 202.27.188.128/25, 210.55.0.0/25, 210.55.1.0/25, 210.55.180.128/26, 210.55.193.64/27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)orcon.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031126 changed: rpsl-admin(a)nzix.net 20040302 changed: rpsl-admin(a)nzix.net 20040329 changed: rpsl-admin(a)nzix.net 20040813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR

1 0

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

09 Oct '05

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

1 0

um, whats wrong with whois?
by Dan Clark 07 Oct '05

07 Oct '05

I get request denied from different hosts I try All the .nz domain suffix version: 1.23.0 query_datetime: 2005-10-08T13:34:36+13:00 domain_name: xtra.co.nz query_status: 440 Request Denied % % Regards Dan

4 4

That Cogent/L3 spat
by Juha Saarinen 06 Oct '05

06 Oct '05

So, how is everyone's intarweb? Rip-roaringly routed or just plain rooted? -- Juha Oh! Oh! Un affrontement intercommunitaire!

1 0

Massey University's networks on WIX
by Glen Eustace 06 Oct '05

06 Oct '05

Massey University have recently peered at WIX and PNIX. Specific prefixes from 130.123.0.0/16 will be advertised into each IX. If you peer at WIX and/or PNIX and do not have an open peering policy, can you please add 130.123.0.0 ge 16 to your route filters and let me know. At this time only 130.123.192.0/19 is advertised at WIX and 130.123.128.0/23 at PNIX. Thanks. Glen Eustace ITS, Massey University. G.Eustace(a)massey.ac.nz, ph +64 6 350 5799 x 81005

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Oct '05

05 Oct '05

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: AS18353 as-name: NZRR-AS18353 descr: HDS descr: WIX peering at '202.7.1.13' descr: see Citylink RT job #2308 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18353 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS18353 descr: Route set advertised to AS9439 by HDS - AS18353 members: 202.55.96.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR

1 0

KiwiBank Site Offline.
by Ben Robinson 05 Oct '05

05 Oct '05

This is not the first time they have been down recently. I have seen several of these messages over the past 2 weeks and it has been getting rather annoying. I just rang them and they informed me that they are making upgrades to there system to make a better overall experience for there users and it will be back up at 6pm LOL! Regards, Ben

1 0

Kiwibank online banking site offline
by Jonathon Horsman 05 Oct '05

05 Oct '05

The Kiwibank online banking site has been offline for some time now, due to a 'technical issue': https://www.kiwibank.co.nz/banking/login.asp It's hard to imagine a technical issue requiring several days downtime. Anyone know what's going on there? Cheers Jonathon

3 2

Any XTRA Mail Server Admins available?
by David Howes 04 Oct '05

04 Oct '05

We've been seeing the same 300KB message resend through our servers every few seconds for the last 18 hours (3500 messages so far) from the XTRA mail servers. Can someone that has the ability to resolve this, contact me off-list? I've had no luck with anyone I've spoken to at XTRA/Telecom. - Dave. ---------- The information contained in this e-mail and any attachments is confidential and is intended for the attention and use of the named addressee(s) only. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Chelmer Limited. ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #####################################################################################

2 1

The New Zealand Network Operators' Group
by Donald Neal 03 Oct '05

03 Oct '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information, including the Call for Participation and Papers. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

1 0

Bankdirect phish
by Craig Box 01 Oct '05

01 Oct '05

Just got a phish for BankDirect. The telling part: "<a href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. The domain is registered with DiscountDomains.co.nz to a RODNEY GUISTWITE. admin_contact_name: RODNEY GUISTWITE admin_contact_address1: 9740 CONIFER LANE admin_contact_city: MURRELLS INLET admin_contact_country: US (UNITED STATES) admin_contact_phone: +84 3 6501641 admin_contact_email: directmain(a)yahoo.com The email headers: Received: from firewall.itpartners.co.nz ([10.7.0.254]) by penfold.itpartners.co.nz with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Sep 2005 08:46:23 +1200 Received: from [218.233.125.18] (helo=-1208382648) by firewall.itpartners.co.nz with smtp (Exim 4.34) id 1EL5Iv-0007GJ-5u for craig(a)itpartners.co.nz; Fri, 30 Sep 2005 08:47:04 +1200 Received: from bankdirect.co.nz (-1208528168 [-1208791160]) by google.com (Qmailv1) with ESMTP id 554E5D0054 for <craig(a)itpartners.co.nz>; Thu, 29 Sep 2005 13:13:12 -0700 Date: Thu, 29 Sep 2005 13:13:12 -0700 From: Bankdirect Accounts <accounts(a)bankdirect.co.nz> X-Mailer: The Bat! (v2.00.8) Personal X-Priority: 3 Message-ID: <5432025998.20050929131312(a)bankdirect.co.nz> To: Craig <craig(a)itpartners.co.nz> Subject: New Fraud-Prevention system. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------C0723C19AFB5862" X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: -5.8 {-----} X-Spam-Report: No, hits=-5.8 required=5.0 tests=ALL_TRUSTED,BAYES_00,HTML_MESSAGE,HTML_TAG_EXIST_TBODY autolearn=ham version=3.0.2 Return-Path: accounts(a)bankdirect.co.nz X-OriginalArrivalTime: 29 Sep 2005 20:46:23.0798 (UTC) FILETIME=[DAB2BD60:01C5C536] Craig Box Phone 07 957 2653 IT Partners Ltd Fax 07 957 2659 PO Box 9361 Mobile 021 475 869 Hamilton, New Zealand _________________________________________________________________ #include <standard-disclaimer.h> _________________________________________________________________

8 7

Olfrygt - a word for the NZNOG lexicon
by Andy Linton 01 Oct '05

01 Oct '05

An article in this weekend's Dom Post talked about words in other languages which don't have a direct equivalent in English. The Danes have "olfrygt" - the fear arising from a lack of beer.

2 2