- NZNOG - lists.nznog.org

TelstraClear to disconnect from WIX route servers
by Dean Pemberton 23 Feb '05

23 Feb '05

At around 1100 today. TelstraClear (AS7714 and AS4768) will disconnect from the WIX route servers. Technical queries should be directed at the TelstraClear Customer Help team (0508 555 500) or to your normal fault escalation point. Business queries should be directed to your TelstraClear account manager. Thanks Dean Pemberton

9 9

ICONZ prefix-list update
by John Johnston 23 Feb '05

23 Feb '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer with ICONZ here is an update. There has been a few adds and removes so please overwrite existing prefix list. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager 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

1 0

who wants some v6 APE action
by Joe Abley 23 Feb '05

23 Feb '05

ISC/F-Root are now live on the APE with IPv6: AS 23710 2001:7fa:4:c0cb::9a62 2001:7fa:4:c0cb::9a63 http://www.isc.org/peering We'll be advertising 2001:500::/48, the F-root prefix [*]. The corresponding AAAA record for F (2001:500::1035) is not in the root zone, yet, so this can be considered pre-production at this time. An application to add the AAAA record is pending with the IANA, however. If anybody would like to set up a native v6 session over the APE, we would be very pleased to peer. We are already peering with the Citylink v6ix route server at the APE, and so people peering with that (or with its counterpart at the WIX) should be able to see us with no additional work [*]. Many thanks to Juniper for their continued support of F in New Zealand: http://www.juniper.net/company/presscenter/pr/2005/pr-050208.html I wonder how many spam filters are going to object to "v6 APE action". [*] the network bits are done; 2001:500::/48 won't actually propagate until the servers have finished their v6alisation, which should happen in the next day or so.

6 10

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

23 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:22:08 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241021280.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR

1 0

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

23 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:20:23 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241019150.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR

1 0

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

23 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:15:51 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241014080.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 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 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR

1 0

Anti-spam legislation update
by Ian McDonald 22 Feb '05

22 Feb '05

>From http://www.stuff.co.nz/stuff/0,2106,3197634a10,00.html Anti-spam law change proposed 24 February 2005 Organisations that send spam could be fined up to half a million dollars and individuals $200,000 under legislation to be introduced to Parliament. Communications Minister David Cunliffe said yesterday that introducing the Unsolicited Electronic Messages Bill would be a priority but no date had been set. The bill "will be an important step in the war against spam," Mr Cunliffe said in a statement. "The legislation will complement codes of practice, technical measures and consumer education to help fight the deluge of spam. It will also help New Zealand's efforts to address this problem at an international level." The bill will apply to e-mails, text messaging and instant messaging requiring that senders of multiple commercial electronic marketing messages only send them to people who have agreed to get them. Senders of promotional electronic messages will be required to stop sending messages if recipients decide to opt out. The bill will also set out requirements relating to accurate sender identification and the provision of an unsubscribe facility. Maximum penalties under the proposed law will be $500,000 for organisations and $200,000 for individualise. The Department of Internal Affairs will enforce the law. "While this bill alone will not solve the problem of spam it is an important step alongside other measures to ensure New Zealand is not a soft target for spammers," Mr Cunliffe said.

1 0

Linux conference Australia 06 in Dunedin.
by Simon Lyall 22 Feb '05

22 Feb '05

Something you may want to put on your calendars: http://lca2006.linux.org.au/ See http://linux.conf.au for more information about this year's conference (to be held in a couple of months). Roughly speaking this is one of the big three Linux conferences held each year. I remember suggesting at one point that if LCA was held in NZ then NZNOG could be a "mini-conference" on the first 2 days of it. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 3

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

22 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1941] Routing updates for APE Route Servers (fwd) - Date: Wed, 23 Feb 2005 16:52:56 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502231652350.21457(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: Route set advertised to AS9560 by CallPlus - AS9790 members: 202.0.151.0/24, 202.36.232.0/24, 202.36.244.0/23^23-24, 202.37.129.0/24, 202.49.34.0/23^23-24, 202.49.62.0/24, 202.50.109.0/24, 202.50.170.0/24, 202.180.64.0/18^18-24, 203.97.152.0/24, 203.100.223.208/20^20-24, 203.184.0.0/18^18-24, 203.215.142.0/23^23-24, 210.55.111.0/24, 210.55.254.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)callplus.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030428 changed: rpsl-admin(a)nzix.net 20040813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-27, 202.37.22.0/24^24-27, 202.37.129.0/24^24-27, 202.49.34.0/23^23-27, 202.50.109.0/24^24-27, 202.180.64.0/18^18-27, 203.97.152.0/24^24-27, 203.100.208.0/20^20-27, 203.184.0.0/18^18-27, 203.215.142.0/23^23-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR

1 0

FYI - Upcoming Webcasts on R2.co.nz
by Richard Naylor 21 Feb '05

21 Feb '05

Evening All, There are several webcasts coming up in the next few weeks. These are brought to your attention so that Help Desks, etc may be forewarned of potential calls. There may even be some network activity. 1-3 March - Hui Taumata - Maori Economic Development Summit, at Te Papa Will be webcast during normal business hours - not likely to have a huge viewer base, but will be webcast in 5 streams as is usual for us. (3 video, 2 audio). Server will be on WIX with limited international capacity. 11-13 March Girl's Day Out - Big Sister Event - AKL Showgrounds It appears to be a 72 hour non-stop webcast with 6 simultaneous cameras. Each camera will stream in 56k, 128k and 256kbps. Which adds up to quite a bit of bandwidth. We will be using 3 carriers to supply the van (which will be bigger, coz we can't fit all the gear in). We do have a web page which allows you to watch all 6 cameras, but don't try it on a telephone modem. The event will (hopefully) use servers on WIX, APE and PNIX and will have national + international routes for operators not peering on those exchanges - but will be heavily rate limited. Operators are STRONGLY urged to peer before the event. This has the potential to be a "large traffic generator" and operators should be aware of this. Fortunately it is a week end. Help Desks may also experience an increase in calls for assistance. 26 March - Wedding in Carterton A Saturday event over Easter week end. Mainly for family of the happy couple. It is unlikely that it will cause any traffic or Help Desk calls as the main audience is in the UK.. Server will be on WIX or APE + international. Early April - Sports event - unconfirmed. We will advise next month if this is going ahead. Thank you for your co-operation. Please contact me if you have any questions. (we don't need any more crew sorry - 2 extras from the office are joining us) Rich (wearing my R2 hat)

1 0

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

21 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1857] Routing updates for WIX Route Servers (fwd) - Date: Tue, 22 Feb 2005 18:09:55 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502221809350.19784(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.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 20050210 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.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 20050222 source: NZRR

1 0

APNIC 19 daily summaries
by Simon Lyall 21 Feb '05

21 Feb '05

Forwarded since the nznog list software rejected it. ---------- Forwarded message ---------- Date: Tue, 22 Feb 2005 13:23:09 +1000 From: Nurani Nimpuno <nurani(a)apnic.net> Subject: [apops] APNIC 19 daily summaries Keep up to date with APNIC 19 daily summaries --------------------------------------------- APNIC is publishing daily summaries of activities at APNIC 19 to keep the Internet community keep up to date with the status of proposed policies and discussion at the meeting in Kyoto. The first daily summary has now been published: http://www.apnic.net/meetings/19/programme/summary/ Daily summaries will be published every day through to Friday. Best regards ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ______________________________________________________________________

1 0

Monitoring etc
by Dan Clark 21 Feb '05

21 Feb '05

no worries, I've found the message I was looking for. Regards Dan

1 0

Monitoring List
by Dan Clark 21 Feb '05

21 Feb '05

Can someone remember the name of that list we setup a wee while back re monitoring etc? Regards Dan Clark Technical Director Synaptic Ltd

1 0

Conference makes the press.
by Simon Lyall 19 Feb '05

19 Feb '05

A little article about the conference at: http://computerworld.co.nz/news.nsf/UNID/3D671C88184ACEBBCC256FAB00804976?O… I'd have hoped for something a little better but better than nothing, the printed version has a group photo. Also could somebody at waikato have a look at warlock.cs.waikato.ac.nz , it seems to have problems (bad dns I think) so the www.nznog.org site is offline. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

nznog 05 videos
by Richard Naylor 18 Feb '05

18 Feb '05

Lots of people have asked for other versions of the video or to be able to get CD copies etc. We can do that if you want (hint $), but to make them more available, we've copied them onto an http server as well. http://s2.r2.co.nz/20050203 I'll get around to putting a link up on the main page soon. Be careful, theres around 2.5GB And the at least one tutorial will go up as well - when I've edited the video down a little and taken out the lunch break etc. rich

1 0

RE: [nznog] crack!
by Donald Neal 17 Feb '05

17 Feb '05

> From: Steve Phillips [mailto:steve(a)focb.co.nz] > Sent: Friday, 18 February 2005 2:18 p.m. > To: nznog > Subject: RE: [nznog] crack! > > On Fri, 18 Feb 2005, Donald Neal wrote: > [snip] > >> > >> right, this is where Donald steps in and says something along > >> the lines > >> of having lost any operational relevance. > > > > Yep. > > > > So was that Donald agreeing that it had lost relevance but > not actually > saying that "it had lost relevance and to please stop posting on this > subject" or was it Donald saying "please dont post anymore on > this subject > as it is no longer relevant" ? That was Donald agreeing that it had lost any operational relevance. Seriously, if a thread has lost all relevance, we should be to stop without needing explicit instructions. The posting to which I was replying is evidence that some on this list do know that. - Donald Neal Donald Neal |"we don't want kids going to Support Engineer |university if they are not going NGN Operations |to success" - Kate Colbert, NZQA 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] crack!
by Donald Neal 17 Feb '05

17 Feb '05

> From: Jamie Baddeley [mailto:jamie.baddeley(a)vpc.co.nz] > Sent: Friday, 18 February 2005 12:09 p.m. > To: Dean Pemberton > Cc: nznog > Subject: Re: [nznog] crack! > > right, this is where Donald steps in and says something along > the lines > of having lost any operational relevance. Yep. - Donald Neal List Administrator etc. Donald Neal |"we don't want kids going to Support Engineer |university if they are not going NGN Operations |to success" - Kate Colbert, NZQA 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

crack!
by Dean Pemberton 17 Feb '05

17 Feb '05

>Ooops! >what was that? >did I just hear The Internet break? >Oh dear. >;-) >jamie >clue:depeer clue:the-sound-of-jamie-jumping-to-conclusions

4 4

crack!
by Jamie Baddeley 17 Feb '05

17 Feb '05

Ooops! what was that? did I just hear The Internet break? Oh dear. ;-) jamie clue:depeer

1 0

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

16 Feb '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: AS24318 as-name: NZRR-AS24318 descr: MinEdu descr: WIX peering at '202.7.0.69' descr: see Citylink RT job #1647 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24318 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050217 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24318 descr: Route set advertised to AS9439 by MinEdu - AS24318 members: 192.105.10.0/24^24-29, 202.37.32.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: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050217 source: NZRR

1 0

NZNOG '05 videos now up
by Jeremy Naylor 16 Feb '05

16 Feb '05

Hey guys, The videos from the NZNOG '05 conference are available online, at: http://www.r2.co.nz/20050203 Feedback to richard.naylor(a)r2.co.nz or jeremy.naylor(a)r2.co.nz Thanks, Jeremy Naylor p: +64 21 374 689 e: jeremy.naylor(a)r2.co.nz w: http://www.r2.co.nz/~jeremy w: http://e-living.wellington.net.nz -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14/02/2005

1 0

Ape looking glass for 202.7.5.32/29
by Barry Murphy 15 Feb '05

15 Feb '05

Hey guys, Looking at ape looking glass for the ip range above (which has been supplied to me by citylink) is already being advertised by another provider (see below). How will this effect me as Maxnet will be advertising this route soon; how does one get an old range removed from rs1 & rs2? BGP routing table entry for 202.7.5.0/24 Paths: (1 available, best #1, table Default-IP-Routing-Table) Advertised to non peer-group peers: 192.203.154.12 192.203.154.14 192.203.154.16 192.203.154.17 192.203.154.28 192.203.154.29 192.203.154.32 192.203.154.33 192.203.154.36 192.203.154.37 192.203.154.44 192.203.154.46 192.203.154.49 192.203.154.67 192.203.154.78 192.203.154.80 192.203.154.81 192.203.154.86 192.203.154.90 192.203.154.91 192.203.154.98 192.203.154.99 192.203.154.101 192.203.154.104 192.203.154.107 192.203.154.108 192.203.154.109 192.203.154.111 192.203.154.112 192.203.154.114 192.203.154.115 23754 192.203.154.4 from 192.203.154.4 (192.203.154.4) Origin IGP, metric 0, localpref 100, valid, external, best Last update: Fri Jan 9 02:11:17 1981 Thanks Barry

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1887] Routing updates for APE Route Servers (fwd) - Date: Wed, 16 Feb 2005 13:57:04 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161356370.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-27, 161.29.0.0/16^16-27, 161.65.0.0/16^16-27, 192.88.85.0/24^24-27, 192.133.31.0/24^24-27, 202.36.226.0/24^24-27, 202.37.86.0/23^23-27, 202.49.80.0/23^23-27, 202.50.52.0/22^22-27, 202.50.196.0/22^22-27, 202.50.200.0/21^21-27, 202.50.208.0/20^20-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050127 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-27, 161.29.0.0/16^16-27, 161.65.0.0/16^16-27, 192.88.85.0/24^24-27, 192.133.31.0/24^24-27, 202.36.226.0/24^24-27, 202.37.86.0/23^23-27, 202.49.80.0/23^23-27, 202.50.52.0/22^22-27, 202.50.196.0/22^22-27, 202.50.200.0/21^21-27, 202.50.208.0/20^20-27, 202.53.176.0/20^20-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1886] Routing updates for WIX Route Servers (fwd) - Date: Wed, 16 Feb 2005 13:56:03 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161352230.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- 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, 192.88.85.0/24^24-29, 202.36.226.0/24^24-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.50.200.0/21^21-29, 202.50.208.0/20^20-29, 192.133.31.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: mplant(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041221 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, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.36.226.0/24^24-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.50.200.0/21^21-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Wed, 16 Feb 2005 13:51:34 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161350450.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS9503 as-name: NZRR-AS9503 descr: FX Networks descr: APE peering at '192.203.154.115' descr: see Citylink RT job #1789 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9503 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050127 source: NZRR REPLACED BY: aut-num: AS9503 as-name: NZRR-AS9503 descr: FX Networks descr: APE peering at '192.203.154.115' descr: see Citylink RT job #1789 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9503 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9503 notify: rpsl-admin(a)nzix.net notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

FW: [Apnic-announce] Unable to travel to Kyoto to attend APNIC 19?
by Nurani Nimpuno 15 Feb '05

15 Feb '05

While I'm at it, I thought it'd be useful to forward this information too. The APNIC meeting is on next week (Mo-Fri) and as explained below, even if you can't travel to Kyoto for the meeting, you can participate in the meeting remotely through video streams, transcripts and jabber chat. The meeting programme is here: http://www.apnic.net/meetings/19/programme/ It's worth noting that 9am in Kyoto is 1pm in NZ. Cheers, Nurani Nimpuno APNIC -----Original Message----- From: apnic-announce-bounces(a)lists.apnic.net [mailto:apnic-announce-bounces(a)lists.apnic.net] On Behalf Of Secretariat Sent: 14 February 2005 17:24 To: apnic-announce(a)apnic.net Subject: [Apnic-announce] Unable to travel to Kyoto to attend APNIC 19? --------------------------------------------- Unable to travel to Kyoto to attend APNIC 19? --------------------------------------------- Attend online instead! You can participate in the meeting from anywhere in the world by taking advantage of APNIC's online video, transcript and chat features. Live meeting features --------------------- The following APNIC 19 sessions will be video streamed and have live transcripts. You can have your input into each of these sessions via the Jabber chat room "room1". Your questions and comments will then be read out to the onsite attendees: Date Time Session ---- ----- ------- 22 Feb 16:00-17.30 Internet governance open forum 23 Feb 11.00-12.30 IPv6 technical SIG 14:00-17.30 Routing SIG 24 Feb 09:00-12.00 Policy SIG 14:00-15:30 Database SIG 16:00-17:30 DNS operations SIG 25 Feb 09:00-17:30 APNIC Members Meeting Note: all times quoted above are local times in Japan. Other APNIC SIG sessions that are not being video streamed will be available by Jabber chat room "room2". Full details on how to participate remotely are available at: http://www.apnic.net/meetings/19/programme/features.html New: webcast tutorials for participating universities ----------------------------------------------------- With assistance from School of Internet (SOI) Asia and the WIDE project, the following tutorials will be broadcast over the network to SOI partner universities: Date Time Session ---- ----- ------- 21 Feb 09:00-12:30 Dynamics of policy process 14:00-17:30 Spam prevention 22 Feb 09:00-10:30 Keynote: security protocol 11:00-12:30 Certification Authority 14:00-17:30 ISP Security Strategy Information about the broadcasts along with details of participating partners will shortly be available on the APNIC website and at: http://www.soi.wide.ad.jp ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> APNIC ph +61 7 3858 3100 http://www.apnic.net fx +61 7 3858 3199 ______________________________________________________________________ See you at APNIC-19 Kyoto, Japan, 21 to 25 Feb 2005 and APRICOT 2005 http://www.apnic.net/meetings ---------------------------------------------------------------------- _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce

1 0

Stuff.co.nz Routing & Peering @ Wix?
by Craig Spiers 15 Feb '05

15 Feb '05

Anyone noticed the ip block maintained by stuff.co.nz is not actually being advertised to the wix route servers? The route I'm receiving, is from Telstra Clear, and is a /24. BGP routing table entry for 202.135.111.0/24, version 235662 Paths: (1 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 4768 2687 203.167.219.181 from 203.167.219.181 (203.97.2.199) Origin incomplete, localpref 100, valid, external, best Are they another 'listen only' peer? Cheers, Craig - ConceptNET

18 26

Notes from NZNOG 05 history of peering session
by Ian McDonald 14 Feb '05

14 Feb '05

Notes from NZNOG 05 history of peering session Folks these are my notes taken down as clarifications/expansions to Joe's notes. Please feel free to tell me where I've got it wrong as I was writing quite quickly…. Talking to Joe there was a suggestion from someone that we put together a Wiki to collect this altogether as a NZ Internet History. Sounds good to me and we could add whole sections on 0867, IPNet and start writing active history on UBS etc. Joe mentioned David Dixon (KCBBS) had done a history page of Internet in NZ which may be a good starting point along with his presentation, these notes and everybody's thoughts... Does anybody have a spare place for a Wiki etc? In the short term do the WLUG members mind if I start a page on there as a temporary home? 1989 KCBBS started Internet link doubled at Waikato from 2.4 to 4.8 Kb/sec Original connection into Waikato was CSNET (sp ??) Connected to DSIR through DSIR routers – 4.8 K links on PC after failing to get working on X25 – Massey was also piggy backed off this as well 1989-1996 Nearly every routing protocol was used except BGP Clear was back through to MCI In effect peering at universities through Tuianet – This was pulled after DOS attack around 1995 at Cybernet conference against ICONZ. Paid for charging for capacity at this time – world leading at the time FreeNet in Wellington 1997/1998 – Home Fibre project canned by Telecom – When did it start? 1998 ADSL launch announced – this was aimed primarily at video July 1998 202.7.0.0/23 – came out of Dunedin City Council. Attempts to give parts of this out to customers through ISPs Citylink – unique as MAN and exchange building out to ISPs 1998 When National Library peered it was on a 386 notebook with two Ethernet cards running Linux 1999 Joe had idea of using Sky tower for peering after riding on a bus and seeing it looming above him ICONZ, Iprolink, KCBBS hosted an abortive exchange through ISDN. Centrex suggested by Max Gustin for this as well. Level 48 at Sky Tower was logical because Clear had fibre and could host internal aerials there also due to type of glass. Correction to a slide – Roger found switch not Richard 1999 192.203.154.0/24 – original owner was Children's Discovery Centre (not sure of this location as didn't hear clearly) Order of acquisitions: Saturn eats Paradise Telstra eats Netlink Telstra eats Saturn i4free was using Clear Network 1994 or 1996 One of International cables broken. Pacrim East built before Pacrim West. Shortly after Pacrim East failed. A couple of people suggested that this was due to a ship pulling anchor just after fixing something else. Between 1995/1996 and 2001. Waikato no longer main connectivity. Rex Croft not looking after .nz. Telecom/Netway got it because nobody else wanted it. Chello ran flat rate cable in Wellington until getting killed in 2001 by Napster. Had a GRE tunnel to Midwest America 2003 MCI were selling Voyager transport. Satellite connection to OzEmail – GRE tunnel also through terrestrial. Subsequent DS3 to Sydney – Late 2003/early 2003 Before Southern Cross Clear and Telecom were sending large packets via satellite and small via cable to help get more traffic through It was May 2004 not Nov 2004 Telstra announce intention to de-peer from APE Early 2004 Telecom withdrew route servers from Exchange Mid 2003 Xtra becomes more residential only. Global Gateway/CID for businesses. Was it at this time Xtra was folded back into Telecom company or earlier?

2 2

RE: [nznog] NZ NPA/NXX
by Donald Neal 14 Feb '05

14 Feb '05

> From: J S Russell [mailto:jsr(a)jsr.com] > Sent: Tuesday, 15 February 2005 1:29 p.m. > To: nznog > Subject: Re: [nznog] NZ NPA/NXX > > On Mon, 14 Feb 2005, Steve Phillips wrote: > > > In the spirit of helpfulness I have thrown together a small > program to > > help you in your endevor. This thread has lost any operational relevance it may have had. Time to leave it alone, people. - Donald Neal List Administrator Donald Neal |Do not look directly at laser with Technical Specialist |remaining good eye. NGN Operations | - Bill Manning 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

Walker Wireless /
by Garrett Stoupe 14 Feb '05

14 Feb '05

If anyone on this list that works for walker wireless / woosh, can you please get hold a hold off me off the list. I need to get some information of our routers on our vpn. Regards Garrett Stoupe Network And Database Administrator Cabbage Tree Press garretts(a)te.co.nz www.te.co.nz www.jobzone.co.nz www.nzcarbuys.co.nz

1 0

NZ NPA/NXX
by Joshua Brady 14 Feb '05

14 Feb '05

Hello all If the phone number for a NZ Company is +64 3 548 1111 would the NPA be 3 and NXX 548? If not, can someone correct me?

6 7

RE: [nznog] NZ NPA/NXX
by Philip D'Ath 14 Feb '05

14 Feb '05

ps. Works great XP with ActiveState perl. -----Original Message----- ... In the spirit of helpfulness I have thrown together a small program to help you in your endevor. ... Hope you find it helpful. (Note, you will need perl installed in /usr/bin/perl, and it will need to be run on some *ix box, also, dont make $x anything other than 0 or weird things may happen, oh, and you can alter $number to be the number of values you require for your database thingy wotsit.)

1 0

RE: [nznog] IP address allocations and geographic areas
by Gordon Smith 14 Feb '05

14 Feb '05

Unfortunately there are some in the U.S. that do block all APNIC space, mainly due to the amount of spam originating from China and Korea. Personally, I think putting Florida into its own address range and null routing it would have a far greater impact on the global spam levels :-) I'd suggest emailing them from an address that isn't blocked and point out the error of their ways Cheers, Gordon

3 2

Re: [nznog] Stuff.co.nz Routing & Peering @ Wix?
by neil gardner 13 Feb '05

13 Feb '05

I'm really sorry for this, but it was just screaming out at me :-) > Speaking of stuff.co.nz, is anyone else having trouble reaching it in the > last half hour ? And trademe ? Seems to be stopping at the hop > nzlapwn1.nz.ip.att.net. I think you mean 'nzlaPWNED1.nz.ip.att.net' :-) Cheers - N. >>> David Zanetti <david.zanetti(a)catalyst.net.nz> 14/02/2005 11:03:22 a.m. >>> [sending to NZNOG properly this time!] On Mon, 2005-02-14 at 10:53 +1300, Simon Byrnand wrote: > Speaking of stuff.co.nz, is anyone else having trouble reaching it in the > last half hour ? And trademe ? Seems to be stopping at the hop > nzlapwn1.nz.ip.att.net. AT&T have an issue. Oddly the traffic is low, 20% of normal instead of the 60% the WIX-AT&T split we found before would indicate. I guess there's a bit of asymetric routing out there :| -- David Zanetti <david.zanetti(a)catalyst.net.nz> Team Leader, Systems Administration Catalyst IT Limited +64-4-8032233 +64-21-402260 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.

1 0

WIX Traffic
by Craig Spiers 12 Feb '05

12 Feb '05

Hi all, What was that last week about someone advertising some new content on wix? Our traffic to wix has more than doubled.. What was the content? Cheers Regards, Craig - ConceptNET

6 7

More Key Signing Stuff
by Joe Abley 09 Feb '05

09 Feb '05

Begin anonymous forwarded message: > I'm going to really prove my ignorance when it comes to all things > pgp. Now that we've done the verification as to who's who, and > everyone owns their own key, what does one do, so sign someone elses > key, or get their key signed by someone else ( should they want to ). I kind of forgot to talk about what we do after we were finished with all the hexadecimal and drivers licences. So here we go: 1. Download the public key ring from buglumber and import it. 2. For each person whose identified you are satisfied with, check the fingerprint on the downloaded keyring against the sheet of verified fingerprints. 3. If you feel like it, sign the key with yours. This is a convenient way to record the fact that you have verified the accuracy of the key. 4. If you feel like it, send the signed public key back to the person who gave it to you. This provides an additional path through the web of trust for people to trust your key, and is generally a handy thing to have. 5. If you feel like it, upload the key with your signature to one or more key servers. This is good for the same reasons that 4 is good. Lather, rinse, repeat for all keys.

5 6

How many ISP's charge their customers to query DNS?
by Chris Hodgetts 09 Feb '05

09 Feb '05

I know this is a "consumer" question, but I find it very strange... Quote from the Paradise Help Desk Email system when questioned about why I was being charged to access kirsty.paradise.net.nz , their secondary DNS Server... "Kirsty is our secondary DNS server, you will get charged traffic connecting to our DNS servers." Any other people working for ISP's wanna comment on if they charge? I know, from what Xtra's support staff said, they don't.. I just find it really hard to believe.

9 9

Denial of Service Attacks
by Anaru Hartley 08 Feb '05

08 Feb '05

Has anyone noticed a surge in DDOS attacks from Asia? One of the Windoze servers I look after has been getting rather nailed these past few days. Most appear to be coming from Japan - at least 5 a day and every time within a few minutes of each other, lasting a minute or two. If I am really lucky, I'll get 20 in one day ... somebody loves me :-)

7 7

Re: [nznog] pop from xtra adsl]
by Gavin Legge 08 Feb '05

08 Feb '05

Thanks for the reply's. I imagine it is a problem with the local setup at the customer site. just wanted to get an idea from the experts before i went there.. Thanks again for the reply cheers Gavin PS - if anyone is interested in a job at DTS as 'technical guy' I'll possibly be leaving soon and I'm sure the boss here would love to hear from you. -- Kind Regards Gavin Legge Technical Manager DTS Limited phone +64 4914 5946 email gavin(a)dts.net.nz cellphone 021 441 299

1 0

RE: [Nznog-org] RE: [nznog] NZNOG 06 - Potential Hosts.
by Peters MCS Mail 07 Feb '05

07 Feb '05

Donald, I was assuming usual timescales when I made the offer - around end Jan/early Feb to make use of available student accommodation. However I'll investigate whether we can be a venue to work around ICANN on 27-31 March as indicated by Keith as that is a very attractive proposition. The issue is that it is in the middle of trimester 1 so our large lecture theatres are generally booked and student accommodation not available. It is more likely to be feasible for 3rd onwards as that is the last week before Easter. Give me a few days to investigate whether this can be arranged. Peter Dr. Peter Komisarczuk School of Mathematics, Statistics and Computer Science Victoria University of Wellington Wellington peterk(a)mcs.vuw.ac.nz Tel: +64 4 463 5661 -----Original Message----- From: nznog-org-admin(a)list.usenet.net.nz [mailto:nznog-org-admin(a)list.usenet.net.nz] On Behalf Of Donald Neal Sent: Wednesday, February 09, 2005 8:21 AM To: Peters MCS Mail Cc: nznog-org(a)list.usenet.net.nz Subject: [Nznog-org] RE: [nznog] NZNOG 06 - Potential Hosts. Peter, Thanks for the offer. When are you offering to host a conference? Or put another way, are you offering to host something aroubnd the time of ICANN (early March 2006) or at another time when cheap accommodation si available? If the later, when roughly is that? - Donald Neal Donald Neal |Do not look directly at laser with Technical Specialist |remaining good eye. NGN Operations | - Bill Manning Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager > -----Original Message----- > From: Peters MCS Mail [mailto:peterk(a)mcs.vuw.ac.nz] > Sent: Tuesday, 8 February 2005 5:03 p.m. > To: 'nznog' > Subject: RE: [nznog] NZNOG 06 - Potential Hosts. > > Simon, > > We'd be happy to host NZNOG 06 at VUW if Wellington is seen as a > reasonable venue. We know there are those who might prefer more > "neutral - driving distance from Auckland" ground, so won't > be offended > if the venue goes to someone else. > > Cheers > > Peter > > Dr. Peter Komisarczuk > School of Mathematical and Computing Sciences > Victoria University of Wellington > Wellington > peterk(a)mcs.vuw.ac.nz > > > -----Original Message----- > From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] > Sent: Tuesday, February 08, 2005 2:29 PM > To: nznog > Subject: [nznog] NZNOG 06 - Potential Hosts. > > > We are looking for potential hosts for NZNOG 06 in around a > year's time. > > If you think that you ( or an organization you are associated with) > might > want to host nznog next year then you should probably start thinking > seriously about it soon. > > We will probably send out a more formal call within the next > week or two > so the decision is made some time in March. > > We already have one early expression of interest. > > If you have questions about what is involved etc then the organizing > people or the WAND group can probably answer them. > > People can probably also suggest possible themes, formats and speakers > at > this point as well. Personally I vote for an on-site Masseuse. > > Email to me (I can summarized or forward) , the list or whoever. > > -- > Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz > "To stay awake all night adds a day to your life" - Stilgar | eMT. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > ------------------------------------------------------------------------ ------ "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." ------------------------------------------------------------------------ ------ _______________________________________________ nznog-org mailing list nznog-org(a)list.usenet.net.nz http://usenet.net.nz/cgi-bin/mailman/listinfo/nznog-org

1 0

NZNOG 06 - Potential Hosts.
by Simon Lyall 07 Feb '05

07 Feb '05

We are looking for potential hosts for NZNOG 06 in around a year's time. If you think that you ( or an organization you are associated with) might want to host nznog next year then you should probably start thinking seriously about it soon. We will probably send out a more formal call within the next week or two so the decision is made some time in March. We already have one early expression of interest. If you have questions about what is involved etc then the organizing people or the WAND group can probably answer them. People can probably also suggest possible themes, formats and speakers at this point as well. Personally I vote for an on-site Masseuse. Email to me (I can summarized or forward) , the list or whoever. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 2

Webcasting FYI - Parliament
by Richard Naylor 07 Feb '05

07 Feb '05

FYI - TVNZ today started streaming Question Time (aka playtime) live from Parliament today. The links are available hidden in the TVNZ website under news -> politics -> 3rd column -> hidden word "live". The video is also being archived in case you missed something....... And its all multi-bit rate - including a stunning 2mbps stream. (must get better cameras) Bringing this back on topic..... it needs a bit better publicity than the current web page, and Network Operators Help Desks may need to explain why a 2mbps stream looks so much better than 56kbps as well as the usual questions like - "why don't I get sound" (coz you haven't turned on the speakers) etc. Congratulations to the folks at TVNZ - a great job. Just look at that 2mbps stream. <sigh> rich

2 2

Re: [nznog] More Key Signing Stuff
by Ewen McNeill 06 Feb '05

06 Feb '05

In message <200502071721.05162.mark(a)mcs.vuw.ac.nz>, Mark Davies writes: >So from the key signing party we should be in the position that for anyone we >have verified we are happy that the pgp key we have the fingerprint for is >indeed for the person we met but the one thing that the process hasn't done >is confirm that all the email addresses listed in the key are under the >control of that person. > >To achieve this last step here is a process (lifted from the NetBSD developers >PGP guidelines): [...] I agree that the "keysigning" party approach generally bypasses actually confirming the email addresses really belong to the person in control of the key. (Which is unfortunate as the email address tends to be one of the more trusted parts.) The usual approach I've seen to confirm that the email address is correct is to send the signed key to the email address listed, encrypted with the key. And not upload the key/signature to a key server. That way only the person in control of both the email address (used) and the key is able to gain access to the signature, and it's not visible to anyone else until they've done so. The NetBSD approach seems to go further and confirm all the uids, providing one follows the elaborate process of tracking each "challenge" that is sent out against the particular uid it belongs to. But I'm not sure it's always necessary if one only signs uids one has other reasons to know are associated with the person in question. (I generally avoid signing uids for which I don't recognise the email address, for instance, unless it's the one to which the key is being sent.) As it happens I've already seen half a dozen new signatures for my key uploaded to the keyservers and not emailed to me, so those people presumably trust the email address for other reasons. Ewen

1 0

Thanks
by Lin Nah 06 Feb '05

06 Feb '05

Thanks to Richard Nelson, Jamie Curtis, Perry Lorier, Leslie and the other folk for organising NZNOG05 and being such wonderful hosts. Thanks To Donald Neal, Joe Abley and other organisers for setting up the programme Thanks to the sponsors who contributed to making it happen. InternetNZ, Citylink, WAND, U of Waikato Juniper, 2day.com, APNIC, De Winter and others I have missed out (but I am sure those at WAND will add to the list). Last but not least Thanks to all who made it there (some despite problems with transport etc). Without the attendees, there would have been no nznog meet. lin

2 1

Re: [nznog] Thanks
by Jonny Martin 06 Feb '05

06 Feb '05

...and thanks to Lin for organising large mounds of people, beer, and food at the unofficial dinners. An enjoyable time had by all I am sure. Cheers, Jonny.

1 0

Peering stuff...
by David Zanetti 05 Feb '05

05 Feb '05

A certain provider of a large amount of content (which I can't name because I haven't got permission to announce this properly) is now peering on WIX. It's ~10-15M at peak. Make sure your prefixes are being sent to the WIX route servers, and you're accepting at least 202.135.111.128/27 from them, and you'll get a nice short path to it instead of via Auckland. If you have some aversion to open peering, well, you can just pay some other provider to get it. :) Enjoy. -- David Zanetti <david.zanetti(a)catalyst.net.nz> Team Leader, Systems Administration +64-4-8032233 +64-21-402260

1 1

pgp key signing
by Joe Abley 03 Feb '05

03 Feb '05

If you want to sign keys this afternoon, and you're currently frantically scrabbling with gpg to try and get your keys into the web page, please continue trying until 4pm. Just after 4pm I'm going to take a snapshot of the keyring, and that's what we'll use for the signing shenanigans. If you haven't figured it out by 4pm, then you can stop trying then :-)

1 0

Streaming Sessions after lunch
by Matt Brown 03 Feb '05

03 Feb '05

Hi All, Coming up this afternoon at the NZNOG'05 Conference we have two programme streams starting at 13:30. You can view the details at www.nznog.org/programme.php. Stream A will have Liz Butterfield from Netsafe talking about NZ's Cybersafety Education Initiative. Stream B will have Joerg Micheel (NLANR) talking about 10GB Abilene Backbone Monitoring, followed by an update on WAND's current research activities. We only have one r2 box here, so only one of these streams will be streamed via r2. If you want to put in your vote as to which one, please reply to me (offlist is fine), before 13:00 today. Cheers -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

2 1

Wellington airport has problems still
by Ian McDonald 03 Feb '05

03 Feb '05

Articles as of midday: Fog Problems Again At Airport 04/02/2005 09:29 AM NewstalkZB Fog is still causing problems at Wellington airport with flights being diverted or delayed. After a day and a half of delays due to low cloud, the airport had only just reopened yesterday morning and airlines were trying to clear the backlog of thousands of passengers. Today, weather conditions at the airport are being described as marginal and deteriorating. Some flights are getting out and one from Nelson has managed to land. Passengers are being advised to check with their airline. Find this item at: http://xtramsn.co.nz/news/0,,11964-4078710,00.html

1 0

RE: [nznog] Notes from NZNOG 05 history of peering session
by Craig Box 03 Feb '05

03 Feb '05

While it's fresh in everyone's minds: > Talking to Joe there was a suggestion from someone that we put > together a Wiki to collect this altogether as a NZ Internet History. > Sounds good to me and we could add whole sections on 0867, IPNet and > start writing active history on UBS etc. I've taken Ian's information, wikified it and put it up on http://www.wlug.org.nz/NewZealandInternetHistory Anyone can edit this - just use YourName as a login ID. (If you can't figure out how to log in, in Bill's words, "you're excused"). If you're linking to something like Telecom, TelstraClear etc, we probably have pages about them already. Please check before linking externally. Craig

1 0

Citylink systems admin
by Barry Murphy 03 Feb '05

03 Feb '05

Hi, Can someone from citylink that can provide me with wix and ape ip space please contact me offlist. I had a chat to Andy some time ago about this, however recently I can't get hold of him so wonder if he is away. Thanks Barry

2 1

Reminder! PGP Key Signing at NZNOG 2005
by Joe Abley 02 Feb '05

02 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reminder! If there are people who are not staying late enough tomorrow to attend, feel free to track me down directly and exchange signatures (or track down someone else who turns up at some other time). Begin forwarded message: > We're going to engage in a frenzy of PGP keysigning at the NZNOG > meeting in Hamilton. People who know what PGP stands for should read > on. People who don't know what PGP is are more than welcome to ask me > off-list, or alternatively ask Google (who at least knows people who > know). > > Here's what we will attempt to do for the meeting next week: > > 1. As soon as you can, generate an ASCII-armoured copy of your public > key and paste it into the convenient form here: > > http://www.biglumber.com/x/web?keyring=5468 > > Consult your PGP software's documentation to find out how to generate > an ASCII-armoured copy of your public key. With GnuPG you use "gpg -a > - --export <your-key-id>". You're looking for a block of ASCII text > which begins with the line "-----BEGIN PGP PUBLIC KEY BLOCK-----". > > 2. Before you set off to the NZNOG meeting, remember two things: > > 2.1. BRING PHOTO ID. Key signing is a process of representing trust, > and if you are interested in getting signatures on your key (and > you're reading, so presumably you are) you should be ready to provide > proof of your identity to other people. Drivers licences, passports, > things of that nature. BRING PHOTO ID. > > 2.2. BRING A TRUSTED COPY OF YOUR PGP KEY FINGERPRINT. This could be > achieved by bringing a laptop with a trusted copy of your public key > on it, or alternatively you could generate the fingerprint of your > public key, write it down and bring the bit of paper with you. BRING A > TRUSTED COPY OF YOUR PGP KEY FINGERPRINT. > > The precise procedure we use at the key signing party will depend on > how many keys are uploaded in the next week; if there's a small > handful we can read signatures aloud -- if there are more, we can try > Len Sassaman's efficient key signing method > (<http://sion.quickie.net/keysigning.txt>). I'll send more words on > this closer to the time. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCAY6O/f+PWOTbRPIRAk41AJ9pQm1q+YiNkYGrnlr+duzA8q2AlQCgvp+7 im7yw9JZLD+cNEkqW09xuHU= =62cR -----END PGP SIGNATURE-----

1 0

Zombie Spam
by Ian McDonald 02 Feb '05

02 Feb '05

Given some of the talks at NZNOG 05 you may find below interesting: Zombie trick expected to send spam sky-high By Jim Hu http://news.com.com/Zombie+trick+expected+to+send+spam+sky-high/2100-7349_3… Story last modified Wed Feb 02 11:25:00 PST 2005 Spam levels are about to skyrocket, according to experts who warned this week that spammers have developed a new way of delivering their wares. According to the SpamHaus Project--a U.K.-based antispam compiler of blacklists that block 8 billion messages a day--a new piece of malicious software has been created that takes over a PC. This "zombie" computer is then used to send spam via the mail server of that PC's Internet service provider. This means the junk mail appears to come from the ISP, making it very hard for an antispam blacklist to block it. Previously, zombie PCs have been used as mail servers themselves, sending spam e-mails directly to recipients. "The Trojan is able to order proxies to send spam upstream to the ISP," said Steve Linford, director of SpamHaus. Linford believes that this Trojan horse was created by the same people who write spamming software. ISPs in the United States may have already been hit. "We've seen a surge in spam coming from major ISPs. Now all of the ISPs are having large amounts of spam going out from their mail servers," Linford said. This will cause serious problems for the e-mail infrastructure, as it is impractical to block mail with domain names from large ISPs. Linford predicts that ISPs will see a growth in the volume of bulk mail they send and receive over the next two months, with spam levels rising from 75 percent of all e-mail to around 95 percent within a year. "The e-mail infrastructure is beginning to fail," Linford warned. "You'll see huge delays in e-mail and servers collapsing. It's the beginning of the e-mail meltdown." Linford said that ISPs need to act fast to take control of the problem. "They've got to throttle the number of e-mails coming from ADSL accounts. They are going to have to act quickly to clean incoming viruses. ISPs have so much spam--they are too understaffed to call people up and tell them they have Trojans on their machines. And no one would know what you're talking about." Antispam company MessageLabs confirmed Linford's findings. "This ups the ante in the need for filters," said Mark Sunner, chief technology officer for MessageLabs. "It makes it more difficult for people who compile blacklists, which is why spammers are doing this. It will put more pressure on ISPs to take greater interest in the traffic they carry and filter at source." The Information Commissioner's Office, the United Kingdom's point-of-call to report spam, said it had received no complaints of bulk spam from ISPs. Some U.S.-based ISPs contacted by News.com said an e-mail meltdown has yet to arrive. But technicians at some of the largest Internet providers have acknowledged the issue and similar exploits in the past. Many, but not all, U.S. ISPs have blocked open relay ports, such as port 25, to shut out spammers from disseminating messages from home-operated servers. The block has helped some broadband ISPs limit the output of zombie spam, and some have noticed the new form of malware taking shape. Time Warner Cable, the nation's second largest cable company, said it had become aware of this spam "vector," as it calls it, and has mechanisms to control it, according to company spokesman Keith Cocozza. He noted that the company's ISP, called Road Runner, has outgoing e-mail limits in place, but declined to elaborate on how the company monitors and responds to this malware issue. Earthlink, which runs a dial-up and broadband service, said it noticed a gradual increase in spam volume coming from its legitimate mail servers since the beginning of 2004. The company claims it has implemented safeguards, such as authenticated SMTP servers and re-routing of legitimate e-mail, to cut down the flow. "Overall we've been able to greatly reduce the amount of spam from our network by routing activities and applying chokepoints," said Trip Cox, Earthlink's chief technology officer. Cox added that the measure have reduced spam from 30 percent of the ISP's total e-mail volume to 2 percent. Dan Ilett of ZDNet UK reported from London.

1 0

CACert Assurance
by Joe Abley 02 Feb '05

02 Feb '05

CACert is a non-evil X.509 certificate authority based in Australia. They give out free certificates to people whose identities they can verify, and they way they verify identities involves a web of trust. I met the CACert people in a meeting in the US last year, and they verified my identity in appropriately paranoid fashion, and made me an Assurer. That means I can act as an introducer. If any of this rings bells, and there's someone at the meeting who would like to be "assured", flag me down at some point and It Will Be Done. Joe

1 0

nznog stream
by Chris Hellberg 02 Feb '05

02 Feb '05

The stream is looking good from Frankfurt. Very little rebuffering (although I think that's the DSL at this end) and clear audio. Watching Dean's interweb presentation right now.

1 0

Transport to NZNOG
by David Zanetti 01 Feb '05

01 Feb '05

Hey all. Due to someone placing an airport in a suboptimal location, I won't be any closer than Auckland to NZNOG conferencage by (hopefully!) 7.30am tomorrow morning. If anyone is planning on driving down in the morning, I would hugely appreciate a lift. Give me a call on the cell number below. Thanks :) -- David Zanetti <david.zanetti(a)catalyst.net.nz> Team Leader, Systems Administration +64-4-8032233 +64-21-402260

2 1

Last mile in CHCH
by Richard Patterson 01 Feb '05

01 Feb '05

What options do people in/around the Christchurch CBD have ? AFAIK TelstraClear cable is fairly predominant around there. Any other options? Local wireless/fibre carriers ? -Richard

11 12

RE: [nznog] Stats from Webcast
by Kenneth Wells 01 Feb '05

01 Feb '05

.. I loved the ..er.. post session "out-takes". Those who watched till the room went dark will know what I'm talking about - as will the few people who came back into the room to check things out for tomorrows sessions.. ..and no matter how "cute" that device on the desk is.. It would probably be missed if stolen... :-) grin grin. Seriously though, great webcasting. The audio is clear and it's easy to hear everyone in the room. Cheers, Kenneth -----Original Message----- From: Richard Naylor [mailto:richard.naylor(a)citylink.co.nz] Sent: Wednesday, 2 February 2005 5:04 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Stats from Webcast Todays webcast Duration 4 hrs 44 min 827MBytes at an average of 405kbps. File copy is 876MB Peak of 26 viewers, average 22. Will be back up at around 8:30 tomorrow - (provided we get here in time) Thanks to the presenter(s), and local camera operator - Matt ? rich _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Stats from Webcast
by Richard Naylor 01 Feb '05

01 Feb '05

Todays webcast Duration 4 hrs 44 min 827MBytes at an average of 405kbps. File copy is 876MB Peak of 26 viewers, average 22. Will be back up at around 8:30 tomorrow - (provided we get here in time) Thanks to the presenter(s), and local camera operator - Matt ? rich

1 0

RE: [nznog] NZNOG Conference "Relays?"
by Craig Box 01 Feb '05

01 Feb '05

>> If anyone is willing to receive emails during presentations with >> comments or questions, would advising of this "live" on the list be >> an acceptable use? > > Or perhaps creation of an alternate list for this specific purpose > would be in order? Sounds like a bloody good idea IMHO. Though > perhaps a question from Hamish would exceed my verboseness capacity > as a relay... There are a number of people here with laptops who "commentate" the conference on #nznog on the Undernet IRC network. Perhaps asking a question in that channel would be the best way to get it asked? Craig

1 0

NZNOG Conference "Relays?"
by Hamish MacEwan 01 Feb '05

01 Feb '05

If anyone is willing to receive emails during presentations with comments or questions, would advising of this "live" on the list be an acceptable use? Not certain of the coverage there, but if you are in coverage and able to check email, this would be a simple DIY solution for those of us who can see and hear, but not speak. Hamish. -- http://del.icio.us/Hamish.MacEwan

3 2

Audio Streams, Webcasts, and IT Conversations
by Mark Derricutt 01 Feb '05

01 Feb '05

Has anyone thought about recording/streaming the sessions from NZNOG this year? Could also be good for whoever's looking after that to contact Doug Kay at IT Conversations ( http://www.itconversations.com/ ) for syndication...

13 18

Re: [nznog] Asx typo...
by Richard Naylor 01 Feb '05

01 Feb '05

At 12:57 PM 2/1/2005 -0800, Mike Savory wrote: >Looks like a typo in the ASX file... its an intelligence test - I just failed.......... >(mms: is misssing a 2....) Its all fixed - sorry about that and thanks for bringing it to my attention.... rich

2 1

RE: [nznog] Last mile in Albany
by Peter Thompson 01 Feb '05

01 Feb '05

We have limited Woosh (non LOS) coverage in Albany. Check www.woosh.com and plug your address into the 'coverage' tool on the homepage. I guess Liz is referring to us as we use 'booster' antennas for our modems. We also have 5.8Ghz (LOS) coverage in parts of Albany, if you want more info contact me off-list and I'll give you the contact details of our man for 5.8 on the North Shore. Regards Pete -----Original Message----- From: Simon Garner [mailto:sgarner(a)expio.co.nz] Sent: Wednesday, 2 February 2005 1:37 p.m. To: Liz Q Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Last mile in Albany On 2/02/2005 1:30 p.m., Liz Q wrote: > On Wed, 02 Feb 2005 13:20, Simon Garner wrote: > >>While we're on the subject... anybody know what's available in the >>Albany area (North Shore)? Other than DSL. >> > > you can get wireless (sometimes requires booster for your aerial) > > Liz > From who/where? :) -Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] asia netcom, sprint
by Mark Frater 01 Feb '05

01 Feb '05

It was Aug/Sep 2002 for Asia Netcom. I think Callplus was one of their first customers. That was back in the days when Quest were also offering bandwidth.. I never really did get the full story about what happened to them.. Unsure about Sprint, but I'm pretty sure it was within 6 months of that. Mark --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.775 / Virus Database: 522 - Release Date: 8/10/2004

1 0

asia netcom, sprint
by Joe Abley 01 Feb '05

01 Feb '05

Does anybody have any estimates on when Asia Netcom and Sprint set up shop selling international transit in Auckland? Handwaving and rampant inaccuracy is fine. Private replies are fine.

4 3

Re: [Nznog-org] Registrations Closed?
by Richard Nelson 31 Jan '05

31 Jan '05

We have now reached the legal limit on the number of people in the room for Thursday. This means that registrations are _really_ closed. There will be no registrations on the day unless we have cancellations or no-shows. We can still take extra people for dinner. Richard Nelson WAND Network Research Group.

3 2

Re: NZNOG Digest, Vol 26, Issue 1
by David 31 Jan '05

31 Jan '05

Re: Multicast in NZ FAQ (Lennon - Orcon) I had a really interesting guy call me up on the helpdesk about a year ago and he spent like an hour on the phone explaining the benefits of mulitcasting. He was trying to convince all the schools to do it in case there was an outbreak of SARS meaning all the schools would be shut and that it would be a good way to push out assignments to students...intersting stuff. Wouldn't viruses be spread quicker via multicast? My 2c Trakman.

1 0

Agenda for spam session on Wednesday
by David Farrar 31 Jan '05

31 Jan '05

Hi all - for those attending the spam session tomorrow as part of NZNOG Conference, the revised agenda FYI is below. You can sleep in :-) 1030 Morning Tea 1100 Welcome - Rodney Prescott 1110 Anti-Spam Technology (David Harris, Richard Jowsey, Simon Lyall) - Sender-ID/SPF (Microsoft) - DomainKeys (Yahoo) - Cisco Initiative - Cascaded statistical filtering 1200 Spam - A dose of reality Simon Lyall, Telecom NZ 1230 Lunch 1330 Spam Trends and Changes (David Harris, Richard Jowsey, Simon Lyall) - Web-bugs/Beacons - Phishing, Mafia links - Trojans - Disposable domains - Zombies - Collateral damage - Blacklists/Blocklists 1500 Afternoon Tea 1530 NZ Anti-Spam Legislation - consequences for industry - Likely shape of legislation (David Farrar) - Code of Practice (Pete Macaulay) 1630 Drinks -- David Farrar e-mail: david(a)farrar.com mob: 027 447 0216, ph: 04 471 0956, fax: 04 471 0946 blog: http://www.kiwiblog.co.nz msn: dpf666(a)hotmail.com, icq: 29964527 Director, Curia Market Research http://www.curia.co.nz Vice-President, InternetNZ http://www.internetnz.net.nz Director, .nz Registry Services, http://www.nzrs.net.nz

1 0

bandwidth in AKL
by Richard Naylor 30 Jan '05

30 Jan '05

Hi There, I have a possible major webcast in AKL at the Showgrounds in mid March. I'm going to need 2 carriers with around 2.5-3 mbps each. I just need to get back to APE, so traffic upstream isn't too great. Current plans are to use Wired Country and IP Star via ICONZ. Any one (incl Telecom and TCL) with something better and do-able before mid March, please contact me off list. Its 3 days live and allowing for set up etc, is a total of maybe 5 days. Thanks - Rich

1 0

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

30 Jan '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 starts tomorrow. See http://www.nznog.org/ for more information about the conference, including how to get there. You may be out of luck if you haven't already registered. If you are going, see http://www.nznog.org/curry_about.php for dinners on Wednesday and Friday. 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 the Auckland, Palmerston North and Wellington exchanges, and some information on others under construction. About This Mailing List This list has around 750 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

backscatter attack
by Spencer Stapleton 30 Jan '05

30 Jan '05

One of our user domains has just been heavily hit by *huge* quantities of Non-Delivery Receipts addressed to random_string(a)domain_name. At it's peak we were seeing around 50,000 NDR's coming in per hr. The worst has passed (<fingers crossed>), but this does raise a couple of issues with the current Internet mail infrastructure. A good discussion of the attack and surrounding issues can be found here at http://www.gossamer-threads.com/lists/spf/discuss/17041. In a nutshell we need Sender Policy Framework (http://spf.pobox.com/) - or something similar ASAP. There is nothing that could stop this happening to us again tomorrow. I don't think I've ever felt so powerless. RBL lists proved useless in the line of defense, as these messages were coming from legitimate sources. We were able to temporarily remove a few IP's here and there where the remote MTA were going overkill throwing these NDR's at us. It would seem that the original spambots that delivered the original message sent it just about everywhere. An interesting stat is that we received NDR's for atleast 352,423 unique recipients (<352,423 unique strings>@domain)!!! We only had a number of things at our disposal to do to limit the damage: Stop generating any 'unknown user' NDR responses ourselves (ignoring RFC876). Split the affected domain away from the rest of our incoming mail stream and then to start removing obvious NDR's from the isolated queues. Remove more NDR's from the queue. <repeat last step again> <and again>... <etc...> Has anyone seen something similar? Did you manage to locate a better solution? I can't say I've enjoyed the last couple of days one bit! Spencer. -- Systems Engineer Compass Communications http://www.compass.net.nz

8 14

Radius?
by Craig Spiers 30 Jan '05

30 Jan '05

What Radius Software are the majority of people out there using? Small Scale.. And large scale.. with SQL Backend? Anyone know anything about freeradius? Regards Craig - ConceptNET

6 5

Multicast in NZ FAQ
by Lennon - Orcon 30 Jan '05

30 Jan '05

Hi Folks.. I have updated a little my "Multicast in NZ" FAQ (http://www.mbone.net.nz) My Wish (Yes I'm dreaming) is get all networks multicast enabled so as people can start to broadcast the content on the net in NZ and if a customer asks, "can I do it" you say "Yes I can". With UBS and Wireless it is possible to get the content out there ,and in the future, if higher speed connections are available which are multicast enabled, Video and other content can get to the customers with people want to see. Yes I know there is no content yet (maybe the big hurdle in people wanting to set it up on their network), but maybe ISP's/Other network providers will want to start to release some content (Radio Stations/Television Stations/Other Content providers) If anyone want to give any suggestions or help, please let me know.. I need some examples of how other people (if anyone else) is setting up their equipment (Like Cisco L2TP termination for UBS etc) which can be put out to other people interested. Thanks Craig

1 0

RE: [nznog] backscatter attack
by Regan Murphy 28 Jan '05

28 Jan '05

"James Riden" writes: >It's best to do SMTP rejects for unknown users; this will >help cut the load on your servers if the forged From addresses >don't exist at your domain. This is relatively straightforward >for most MTAs - I believe postfix can do LDAP queries >against AD, or can talk to a postgresql database. Since >most of the forged addresses will be nonexistent, this should >help quite a bit. >(Bonus - it will also stop you generating this kind of traffic >for other sites in the future.) My mail domain is relatively small - about 40 real users - but I still drop about 1500 mail connections a day for email sent to invalid users. About 200 of these were typically virus initiated (and therefore had attachments) and almost all the rest were spam. My MTA is Mailmarshal and it can easily be configured to do this. You can set up LDAP or Active Directory connectors to hook into your directory servers which makes managing the lookup lists simple. And before I hear cries of "argh, not mailmarshal again..." Its configured so that is does *not* send outbound notifications for viruses etc. -- Regan

2 1

PGP Key Signing at NZNOG 2005
by Joe Abley 28 Jan '05

28 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We're going to engage in a frenzy of PGP keysigning at the NZNOG meeting in Hamilton. People who know what PGP stands for should read on. People who don't know what PGP is are more than welcome to ask me off-list, or alternatively ask Google (who at least knows people who know). Here's what we will attempt to do for the meeting next week: 1. As soon as you can, generate an ASCII-armoured copy of your public key and paste it into the convenient form here: http://www.biglumber.com/x/web?keyring=5468 Consult your PGP software's documentation to find out how to generate an ASCII-armoured copy of your public key. With GnuPG you use "gpg -a - --export <your-key-id>". You're looking for a block of ASCII text which begins with the line "-----BEGIN PGP PUBLIC KEY BLOCK-----". 2. Before you set off to the NZNOG meeting, remember two things: 2.1. BRING PHOTO ID. Key signing is a process of representing trust, and if you are interested in getting signatures on your key (and you're reading, so presumably you are) you should be ready to provide proof of your identity to other people. Drivers licences, passports, things of that nature. BRING PHOTO ID. 2.2. BRING A TRUSTED COPY OF YOUR PGP KEY FINGERPRINT. This could be achieved by bringing a laptop with a trusted copy of your public key on it, or alternatively you could generate the fingerprint of your public key, write it down and bring the bit of paper with you. BRING A TRUSTED COPY OF YOUR PGP KEY FINGERPRINT. The precise procedure we use at the key signing party will depend on how many keys are uploaded in the next week; if there's a small handful we can read signatures aloud -- if there are more, we can try Len Sassaman's efficient key signing method (<http://sion.quickie.net/keysigning.txt>). I'll send more words on this closer to the time. Thanks! Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFB+bVj/f+PWOTbRPIRAi5jAJ93/s+kA1HJnO82JxCqwhAj2mniPQCcC72i uxmFZl1QTdi4ZMk5AXa5u5k= =6Rnh -----END PGP SIGNATURE-----

2 2

Telecom
by Garrett Stoupe 27 Jan '05

27 Jan '05

Is it possible anyone from telecom to contact me off list in regards towards the proxy servers that Telecom uses Garrett Stoupe Network And Database Administrator Cabbage Tree Press garretts(a)te.co.nz www.te.co.nz www.jobzone.co.nz www.nzcarbuys.co.nz

3 2

IANA IPv4 allocations and bogon update: 124/8, 125/8 and 126/8
by Rob Thomas 27 Jan '05

27 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hi, team. [ Apologies to those of you who receive this note in multiple forums. ] The numerous Team Cymru bogon projects have been updated as of 27 JAN 2005 to reflect the following IANA allocation made on 27 JAN 2005: 124/8 Jan 05 APNIC (whois.apnic.net) 125/8 Jan 05 APNIC (whois.apnic.net) 126/8 Jan 05 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. Thanks, Rob. - -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQfl/WlkX3QAo5sgJAQF9bQP9Fr8ME4sMVC27ANxUfgDjbG7SLnI2vnQK FMNkdXSoLdNSulPtcwKu9x6uMxDfQtN1s7Ks2LMC2x8aA/aAMJSgY9zaawmuy6Gv iElHI0mHsRY90YbYVS1o6nXP/RtFFK4GdOgw99LjkAjgm/tEdGrbt6dzaHkCTrAa bbvDFteCeH4= =PPS8 -----END PGP SIGNATURE-----

1 0

Nznog travel
by Scott Walsh 27 Jan '05

27 Jan '05

Hi All, I've driving down to Hamilton for nznog early Wednesday morning (leaving by 6:30) and returning Friday pretty much right the conference close. If anyone would like a ride, get in touch. Thanks Scott Walsh Service Implementation Specialist Integrated Technology Services (ITS) - Passionate about Winning IBM New Zealand Limited

2 1

Nznog dinners
by Lin Nah 26 Jan '05

26 Jan '05

Hi All I am organising the dinners on Wednesday 2 February and Friday 4 February. It won't be anything as organised as the Thursday dinner! It is definitely NOT part of the conference and so a. You have to pay for your own meal, and, b. attendance isn't limited to ppl attending the meet Please read the page about the dinners and if you wish to attend, give me an indicative reply Page on dinners: http://www.nznog.org/curry_about.php Look forward to seeing you there. regards lin Auckland Thursday Night Curry http://auckland.thursdaynightcurry.com

1 0

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

26 Jan '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:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-27, 161.29.0.0/16^16-27, 161.65.0.0/16^16-27, 192.88.85.0/24^24-27, 192.133.31.0/24^24-27, 202.36.226.0/24^24-27, 202.37.86.0/23^23-27, 202.49.80.0/23^23-27, 202.50.52.0/22^22-27, 202.50.196.0/22^22-27, 202.50.200.0/21^21-27, 202.50.208.0/20^20-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050127 source: NZRR

1 0

Slightly OT: Petition to ban someone from the 'net
by Matthew Poole 25 Jan '05

25 Jan '05

Now, I'll preface this by saying that I'm almost certain it's bovine excrement. But once you involve politicians, anything's possible. A friend of a friend (yeah, one of those stories) has raised with him the suggestion that NZ has some system to petition to have someone permanently banned from the Internet. This notional petition only requires 50 signatures. Can anyone confirm such a beast? I imagine there will be peals of laughter accompanying the reading of this e-mail, and I'll be stunned if someone says it does actually exist, but there's no harm in asking the group of people most likely to know. -- Matthew Poole "Don't use force. Get a bigger hammer."

7 7

Two low-severity BIND security advisories (BIND 8, BIND 9)
by Joe Abley 25 Jan '05

25 Jan '05

Advisories for BIND 9 and BIND 8 follow. Note that BIND 9 is only vulnerable if the DNSSEC validator is turned on (it's off by default). Begin forwarded message: > From: Mark Andrews <Mark_Andrews(a)isc.org> > Date: 26 January 2005 17:55:48 GMT+13:00 > To: bind-announce(a)isc.org > Subject: Internet Systems Consortium Security Advisory: BIND: Self > Check Failing > > > Internet Systems Consortium Security Advisory. > BIND: Self Check Failing > 18 November 2004 > > Versions affected: > BIND 9.3.0 > Severity: LOW > Exploitable: Remotely > Type: denial of service > Description: > > An incorrect assumption in the validator (authvalidated) > can result in a REQUIRE (internal consistancy) test failing > and named exiting. > > Workaround: > > Turn off dnssec validation (off by default) at > the options/view level. > > dnssec-enable no; > > Fix: > > Upgrade to BIND 9.3.1 > http://www.isc.org/sw/bind/ > > See also: > http://www.kb.cert.org/vuls/id/938617 Begin forwarded message: > From: Mark Andrews <Mark_Andrews(a)isc.org> > Date: 26 January 2005 17:54:31 GMT+13:00 > To: bind-announce(a)isc.org > Subject: Internet Systems Consortium Security Advisory: BIND: Buffer > Overrun (q_usedns). > > > Internet Systems Consortium Security Advisory. > BIND: Buffer Overrun (q_usedns). > 17 November 2004 > > Versions affected: > BIND 8.4.4 and 8.4.5 > Severity: LOW > Exploitable: Remotely > Type: denial of service > Description: > > It is possible to overrun the q_usedns array which > is used to track nameservers / addresses that have > been queried. > > Workaround: > > Disable recursion and glue fetching. > > Fix: > > Upgrade to BIND 8.4.6 > http://www.isc.org/sw/bind/ > > See also: > http://www.kb.cert.org/vuls/id/327633

2 1

RE: [nznog] Slightly OT: Petition to ban someone from the 'net
by Donald Neal 25 Jan '05

25 Jan '05

> -----Original Message----- > From: Antonio Broughton [mailto:anacarda(a)flerwin.net] > Sent: Wednesday, 26 January 2005 10:58 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Slightly OT: Petition to ban someone > from the 'net > > Matthew Poole wrote: > > That's exactly what I thought. Not to mention that you could get 50 > > signatures simply by standing on the corner of Queen St and > Wellesly St at > > lunchtime. > > This person is apparently adamant (aren't they all?) that > such a thing > > exists. To the point that she's out seeking further details. > > > > ahhh there we go then... a female... 'nuff said... :) I think we can leave that thread there. - Donald Neal NZNOG Liat Administrator/Muggins Donald Neal |A prophecy is a guess that comes Technical Specialist |true. If it doesn't come true, it's NGN Operations |a metaphor. - G'Kar, Babylon 5 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." ------------------------------------------------------------------------------

2 1

How to stop spam
by Juha Saarinen 25 Jan '05

25 Jan '05

http://www.circleid.com/article/917_0_1_0_C/ Some interesting discussion there. -- Juha

2 1

HEADS UP - Upcomming Webcasting Activity
by Richard Naylor 24 Jan '05

24 Jan '05

Next week is the 2005 Premiere Yearling Sale and the event will be webcast live. The dates are Monday 31 Jan through to Friday 4 Feb inclusive. 1000Hrs to 1700Hrs There will be test streams running on Sunday 30 Jan at various times (ie when we get it going). The event web site is www.nzb.co.nz, with the streams originating from R2.co.nz - There will be 5 bit rates (streams) so that users get a choice of stream quality, affordability, etc. The webcast will include the Select Yearling Sale (ie cheaper horses), which is the thursday and friday. At this stage, the Festival Yearling Sale (ie even cheaper horses), on Sunday and Monday 6, 7 February, is *NOT* being webcast. These events are not huge in terms of viewer numbers, but with large sums of money involved ISP Help Desks may receive a few calls from "excited" clients, needing to watch in a hurry etc. (About $60M changes hands during the event - must put my hand out....) The event web page at R2 is http://www.r2.co.nz/20050131 details of the streams etc will be available on that page. The Premiere Sale (first 3 days) is also broadcast on Trackside TV, and SkyTV. Thanks you for your assistance; I hope there aren't too many calls for you. Richard

1 0

Philip Hazel public presentation
by Craig Box 24 Jan '05

24 Jan '05

Hi everyone, As Philip Hazel is in town for the NZNOG conference, the Waikato Linux Users Group have arranged for him to present a public meeting the night before his tutorial (1st February). The talk is entitled "Exim and PCRE: How free software hijacked my life" [1]. Philip will present a non-technical talk on the history of the Exim and PCRE software projects, how they got started, where they are now, and where they are currently going. We thank the NZNOG conference for sponsoring Philip to NZ, but attendance at NZNOG isn't required for attending this talk, so I figured some people here might be interested or know people who are (especially if they were going to a different tutorial). The meeting will start at 7:30pm, in the LitB[2] building at Waikato University. All are welcome, although non members are encouraged to make a gold coin donation. Tea/coffee/biscuits/juice will be provided after the meeting. Hamilton is only a short amble from Auckland and is lovely this time of year. For those unfamiliar with the WLUG, especially people involved in Linux support or administration, you might like to check our wiki out at http://www.wlug.org.nz/. Regards, Craig Box Waikato Linux Users Group Secretary [1] For more information on Philip and the meeting, see http://www.wlug.org.nz/MeetingTopics.2005-02-01 [2] For a map, see http://www.wlug.org.nz/LitB

1 0

Virus Filtering by ISPs vs the need to receive security/abuse traffic
by Mark Foster 21 Jan '05

21 Jan '05

This is one that i've come across from time to time and often pondered myself - Obviously virus traffic can fluctuate up and down and become an annoyingly high percentage of an ISPs total mail load. Thus AV filtering which drops these messages is beneficial and can be provided as a benefit to customers, etc... So what happens to role accounts like, heaven forbid, abuse@ ? And for that matter, if the messages are dropped, is there any logged trace of the fact the message was sent in the first place? The reason I ask is that i've seen at least one ISP to whom i've reported viral infections to recently actually reject the report, because of the 'illegal file attatchment' (where the criteria used was the file extension... not even viral code within the attatchment)... So I had to manually copy/paste headers only to get my point across. The argument can be made that headers are all thats required, and that the actual payload isnt needed - but what if theres occaision where you want said payload? (To provide actual evidence of the infection, to identify what variant of the virus is infected, to help build filters ...?) Do ISPs out there regularly exclude their security team or at least build in means for one-off exceptions on an as-required basis? Do ISPs that drop viral (or suspected viral) traffic do anything to report said infection, or do they just drop the virus and pretend it never happened? (Doesn't actually fix the problem, does it...) Appreciate your thoughts. Mark.

4 5

I guess somebody needs a Beer.
by Simon Lyall 20 Jan '05

20 Jan '05

Sounds like a few people out there had a rough few days. I found this linked at the top of the paradise homepage. http://www2.paradise.net.nz/security_update/news.html Security Update Security issue - email and web hosting A small number of Paradise.net customers may have have experienced email delays and web-hosting problems on Thursday January 20th and Friday January 21st. Early Thursday morning some Paradise email was delayed. Our security people detected a security threat and disconnected a server to preserve the integrity of Paradise.net. This server will be reconnected shortly and backlogged email should be delivered this afternoon (Friday January 21). As part of our security precautions we also disconnected hardware which hosts Paradise web pages. We have been working round the clock to ensure the hardware can be reconnected with no risk to Paradise.net or Paradise users. We expect to restore web pages this evening. We know that an external party has attempted to interfere with Paradise.net. This attempt was picked up and immediate steps were taken to avoid any further impact on Paradise.net customers. Please accept our apologies for any inconvenience these very necessary steps have caused. Our approach, as always, is to take firm steps to preserve the security of Paradise.net and protect our customers. the team at Paradise.net -- 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

Mystery compound in beer fights cancer
by Andy Linton 20 Jan '05

20 Jan '05

Seems that research into this topic is warranted at NZNOG. http://www.newscientist.com/article.ns?id=dn6895

6 7

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

20 Jan '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 21 Jan 2005 13:15:27 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0501211313160.7621(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to WIX by Catalyst-IT - AS23959 members: 202.49.159.0/24^24-29, 202.46.190.0/24^24-29, 202.20.6.0/24^24-29, 203.167.212.32/29, 203.167.247.160/29, 202.7.4.64/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: andrew(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040120 changed: rpsl-admin(a)nzix.net 20040628 source: NZRR

1 0

RE: [nznog] National BGP routing
by Gordon Smith 19 Jan '05

19 Jan '05

> Why are inconsistent AS-paths bad? Operationally, I mean. (I > hadn't had any operational mishaps in all my years at UUNET > because of inconsistent AS-paths, so I'm wondering if > something else causes an issue now?) > > Technically there is nothing wrong with them. As you > observed, it's simply an organisation multihoming using a > private ASN - hopefully their upstreams are stripping out the > private ASN before they propogate the originated prefixes > further. (Mind you, I find it rare for two ISPs to agree > which private ASN to use for a mutual customer to multihome - > often so much easier to obtain a real one.) > > And yes, people can quite easily use public ASNs. It's simply > a case of an APNIC member obtaining an ASN so their customer > can multihome. And that can't be too hard, right? > > philip > -- > Hi Philip, You're quite right. Technically, you can still be pass traffic to the client's endpoint, although the path selected may not be optimal. What can cause issues is if you then start creating routing policies on your route reflectors based on AS-path, especially if you don't have a direct peer with both of the providers that are carrying that customer's traffic. With multiple peering points, you can end up backhauling the traffic over your own links because the routing decisions passed via your IGP are no longer necessarily optimal e.g. I may wish to pass a 10Mbit stream from a Wellington customer to somewhere else in Wellington, via another provider, but the route reflectors see that destination as having a shorter AS path via Auckland. We don't have a destination AS that a metric can be applied to. We can of course apply different costs to the WAN links (and should have done), but the fine-grained control of traffic isn't achievable because the router can't be given much to go on. Policy routing and tagging is an option, but relies on the destination site, who is not necessarily a customer of ours, informing us of changes in their topology so our rules can be updated. APNIC have always been very good when it comes to getting ASN's; I've always found the justification of additional address space to be an ordeal though :-) In my opinion, it would be far more preferable if APNIC allocated an ASN when a customer was given an independent address assignment. After all, the reason that most want independantly allocated space is to multihome... Cheers, Gordon

3 2

National BGP routing
by Gordon Smith 18 Jan '05

18 Jan '05

I'm sure I can't be the only one that notices the BGP inconsistancies in their route tables.... Seeing the latest NZRR update prompted me to check the BGP tables again... We do not and will not accept route advertisements containing private AS numbers from our peers. The reason we don't is the same reason we don't route RFC1918 space externally... If a customer has their own address space and wants to multi-home, they should also have their own AS. Advertising up private AS numbers that should really remain within the network isn't a solution. Inconsistant AS-paths are bad enough, without creating additional problems... At least we're only seeing 5 class C's being advertised at the APE with inconsistant AS-paths at the moment. Perhaps BGP routing could be a topic for discussion at NZNOG 2005? Cheers, Gordon

3 2

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

18 Jan '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Wed, 19 Jan 2005 13:40:23 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0501191339480.4620(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24226 descr: Route set advertised to AS9439 by Catalyst IT - AS24226 members: 202.46.190.0/24^24-29, 202.49.159.0/24^24-29, 202.20.6.0/24^24-29, 202.36.119.0/24^24-29, 210.48.47.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.zanetti(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: 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 --- PREVIOUS OBJECT: route: 202.20.6.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.zanetti(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: route: 202.20.6.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR --- PREVIOUS OBJECT: route: 202.36.119.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.zanetti(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: route: 202.36.119.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR --- PREVIOUS OBJECT: route: 202.46.190.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.zanetti(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: route: 202.46.190.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR --- PREVIOUS OBJECT: route: 202.49.159.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.zanetti(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: route: 202.49.159.0/24 descr: Route for Catalyst IT - AS24226 origin: AS24226 notify: rpsl-admin(a)nzix.net notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR

1 0

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

18 Jan '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: rt(a)citylink.co.nz - Subject: [CityLink #1656] New Object for inclusion into the NZRR Route Registry (fwd) - Date: Wed, 19 Jan 2005 12:25:41 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0501191224520.4620(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.101.112/29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041209 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.101.112/28^28-29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041209 source: NZRR

1 0

Xtra in the SpamHaus SBL
by Peter Macaulay 17 Jan '05

17 Jan '05

I don't know if anyone from Xtra reads this list - trying to get through to anyone who has even an iota of understanding about this type of thing by phone appears to be almost impossible. Xtra has managed to get itself into the SBL realtime blocklist - http://www.spamhaus.org/sbl/sbl.lasso?query=SBL22816 It appears that someone objected to some promotional material sent out by the "House of Travel" travel agent group and has ended up blocking them; this means that one of Xtra's MX (mail exchanger) servers is now blocked by anyone who uses the SBL as a spam filter. If anyone knows anyone at Xtra who can do something about this, could you pass this message on? It's probably inconveniencing a reasonably large number of people. The NZNOG list would be a good place to post this too, I suppose, but I'm not a subscriber. Cheers! -- David -- ------------------ David Harris -+- Pegasus Mail ---------------------- Box 5451, Dunedin, New Zealand | e-mail: David.Harris(a)pmail.gen.nz Phone: +64 3 453-6880 | Fax: +64 3 453-6612 Phrase found in a Soviet Russian-English language guide: "Flying in the TU-114 I felt myself excellently." _______________________________________________ members-discuss mailing list members-discuss(a)internetnz.net.nz http://listserver.internetnz.net.nz/mailman/listinfo/members-discuss -- *Peter Macaulay* /Executive Director/ *InternetNZ */Direct +64 4 495 2113 Skype petermacaulay Mobile +64 21 488 485 /

6 5

(OT) Getting to NZNOG '05
by Jeremy Naylor 16 Jan '05

16 Jan '05

Hey guys, For people who want to know about how to get to the NZNOG '05 conference, you might want to catch the Overlander train that Tranz Scenic run. There's 2 every day (1 from Wellington - Auckland & 1 from Auckland - Wellington). You can get more info about these trains if you want to on Tranz Scenic's web site, at: http://www.tranzscenic.co.nz/services/overlander.aspx Hope this helps. Thanks, -- Jeremy Naylor p: +64 21 374 689 e: jeremy.naylor(a)r2.co.nz w: http://www.r2.co.nz/~jeremy w: http://e-living.wellington.net.nz -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.7 - Release Date: 30/12/2004

3 2

RE: [nznog] Alternative DSL?
by Philip D'Ath 16 Jan '05

16 Jan '05

VDSL switches are a good middle ground between Ethernet switches and DSLAMs ... _____ From: Richards, David [mailto:David.Richards(a)ccc.govt.nz] Sent: Monday, 17 January 2005 5:34 p.m. To: jon.brewer(a)araneo.net.nz Cc: nznog Subject: RE: [nznog] Alternative DSL? Any reason why you aren't thinking Ethernet? - Provided the distances are shot. An Ethernet switch is a lot cheaper than a DSLAM. -- David Richards, Senior Network Engineer IT Services Unit - 'Enabling people through technology' Christchurch City Council, New Zealand Phone: +64 3 941 8689 | Fax: +64 3 941 8989 | Mobile: +64 27 242 7689 email: David.Richards(a)ccc.govt.nz

1 0

OT - Linux Systems Administrator
by Edward Yardley 16 Jan '05

16 Jan '05

**OFF TOPIC** Hi All, Any Linux Systems Administrators looking for work in Wellington please contact me off list or call me on (04) 499-1276. This is a new role, will involve establishing security (intrusion detection), Red Hat environment. Kind Regards Edward. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

6 7

Re: [nznog] 02.net
by Lamar - 02.Net Internet Services 16 Jan '05

16 Jan '05

As Neil pointed out, 02.Net has not gone bust and is still trading. Due to the recent IPNET issue with Telecom, we decided for the money actually made on dialup services and the level of support required that we would no longer continue providing this service. As for Craig's statement about "unable to sell any services.." this is incorrect our Dialup (and all other services) are still working until customers swap over to Orcon (who are contacting customers with our permission). In short, we're getting out of dialup internet because there is no money in continuing these types of services. We are focusing more on corporate and higher speed products, with a lesser level of support required. So, you will still see us around. Any questions or queries can be sent directly through to myself. -- Regards, Lamar (02.Net's Director). >>From the 02.net.nz website... > >>If you are an Internet customer of 02.Net, due to circumstances > outside of our >>control, 02.Net is unable to continue supply of Dialup services at > this time. We >>are working to get this resolved. However, in the meantime Auckland > based ISP >>Orcon Internet Limited have taken over our Dialup customer database. >> >>Orcon will be in contact with Internet customers to advise a change in > dialup >>numbers. However, the statements that Orcon's helpdesk are giving out > of 02.Net >>Internet Services Limited going bust are incorrect. We are trying to > contact the >>Orcon helpdesk manager to get this resolved. >> >>If you have any questions relating to this or any other matters, > please feel free >>to call us on 0800 4 02NET (0800 4 02638) > > Craig - Sure it may be the case, but they have stated specifically on > their web-page that they haven't gone bust. Surely it's not worth making > such statements unless you actually know what's happening? > > Cheers - Neil Gardner. > > > >>>> "Craig Spiers" <craig(a)concept.net.nz> 17/01/2005 1:49:46 p.m. >>> > Maybe of interest to some people on the list.. > > > > 02.net.nz appears to have gone bust - well not gone bust as such, but > is > unable to sell any services.. > > > > > > > NOTICE: This message contains privileged and confidential > information intended only for the use of the addressee > named above. If you are not the intended recipient of > this message you are hereby notified that you must not > disseminate, copy or take any action in reliance on it. > If you have received this message in error please > notify Allied Telesyn Research Ltd immediately. > Any views expressed in this message are those of the > individual sender, except where the sender has the > authority to issue and specifically states them to > be the views of Allied Telesyn Research. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Alternative DSL?
by Jonathan Brewer 16 Jan '05

16 Jan '05

Questions for NZNOG: In a new apartment building with CAT5 run from each unit to a central closet, installed by the developers, who owns the CAT5? If the CAT5 is the property of the building body corporate, is it permissable for an alternative network operator to install their own mini-DSLAM, and provide alternative DSL to building occupants? If this unit is not using Telecom lines, does it need to be Telepermit approved? If competitive DSL is run over spare pairs (not in use by TelecomNZ), will there be any implications for residents who subscribe to JetStream? Am I going to end up in pain for asking these questions? Cheers, Jon

3 2

RE: [nznog] Alternative DSL?
by Regan Murphy 16 Jan '05

16 Jan '05

I read a contract for a development in Auckland recently. There was a clause regarding services that stated that the purchaser must purchase electricity/gas/water from the company that the developers specify. There was also a clause that made it compulsory for future buyers to agree to this too. It may or may not have extended this to other services - I'm not sure - this development also had cat-5 cabled throughout and mentioned broadband internet access as an available service. This clause, among others, put me off investing in the development. I'm pretty sure that to answer your question you would need to check the contracts signed by the owners and check the body corporate rules - I doubt you will get a single situation that covers all developments. You will probably need to negotiate with the manager/body corporates at each location. -- Regan ________________________________ From: Jonathan Brewer [mailto:jon.brewer(a)worldnet.att.net] Sent: Monday, 17 January 2005 3:28 p.m. To: 'nznog' Subject: [nznog] Alternative DSL? Questions for NZNOG: In a new apartment building with CAT5 run from each unit to a central closet, installed by the developers, who owns the CAT5? If the CAT5 is the property of the building body corporate, is it permissable for an alternative network operator to install their own mini-DSLAM, and provide alternative DSL to building occupants? If this unit is not using Telecom lines, does it need to be Telepermit approved? If competitive DSL is run over spare pairs (not in use by TelecomNZ), will there be any implications for residents who subscribe to JetStream? Am I going to end up in pain for asking these questions? Cheers, Jon ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################

1 0

RE: [nznog] Alternative DSL?
by Kristy Edwards 16 Jan '05

16 Jan '05

-----Original Message----- From: Jonathan Brewer [mailto:jon.brewer(a)worldnet.att.net] Sent: Monday, 17 January 2005 15:28 To: 'nznog' Subject: [nznog] Alternative DSL? Questions for NZNOG: In a new apartment building with CAT5 run from each unit to a central closet, installed by the developers, who owns the CAT5? I believe this would be the owner of the building, or the body corporate (which consists of the tenants of the apartments of the building). If the CAT5 is the property of the building body corporate, is it permissable for an alternative network operator to install their own mini-DSLAM, and provide alternative DSL to building occupants? Yes this is permissable. Obviously the building owner / manager would need to approve this. But if the building owner is doing an 'under-the-table' deal with Telecom and stops other providers providing their alternative DSL to building occupants, this can be considered anti-competitive behaviour and Telecom could be taken to the commerce commission for this. If this unit is not using Telecom lines, does it need to be Telepermit approved? No, as it is not using telecom lines! They would need to have their own lines into the building, however. If competitive DSL is run over spare pairs (not in use by TelecomNZ), will there be any implications for residents who subscribe to JetStream? Apart from interference, I would not believe so. Am I going to end up in pain for asking these questions? Cheers, Jon

1 0

Re: [nznog] 02.net
by neil gardner 16 Jan '05

16 Jan '05

>From the 02.net.nz website... >If you are an Internet customer of 02.Net, due to circumstances outside of our >control, 02.Net is unable to continue supply of Dialup services at this time. We >are working to get this resolved. However, in the meantime Auckland based ISP >Orcon Internet Limited have taken over our Dialup customer database. > >Orcon will be in contact with Internet customers to advise a change in dialup >numbers. However, the statements that Orcon's helpdesk are giving out of 02.Net >Internet Services Limited going bust are incorrect. We are trying to contact the >Orcon helpdesk manager to get this resolved. > >If you have any questions relating to this or any other matters, please feel free >to call us on 0800 4 02NET (0800 4 02638) Craig - Sure it may be the case, but they have stated specifically on their web-page that they haven't gone bust. Surely it's not worth making such statements unless you actually know what's happening? Cheers - Neil Gardner. >>> "Craig Spiers" <craig(a)concept.net.nz> 17/01/2005 1:49:46 p.m. >>> Maybe of interest to some people on the list.. 02.net.nz appears to have gone bust - well not gone bust as such, but is unable to sell any services.. 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.

1 0

02.net
by Craig Spiers 16 Jan '05

16 Jan '05

Maybe of interest to some people on the list.. 02.net.nz appears to have gone bust - well not gone bust as such, but is unable to sell any services..

1 0

RE: [nznog] Alternative DSL?
by Richards, David 15 Jan '05

15 Jan '05

Any reason why you aren't thinking Ethernet? - Provided the distances are shot. An Ethernet switch is a lot cheaper than a DSLAM. -- David Richards, Senior Network Engineer IT Services Unit - 'Enabling people through technology' Christchurch City Council, New Zealand Phone: +64 3 941 8689 | Fax: +64 3 941 8989 | Mobile: +64 27 242 7689 email: David.Richards(a)ccc.govt.nz ________________________________ From: Jonathan Brewer [mailto:jon.brewer(a)worldnet.att.net] Sent: Monday, 17 January 2005 15:28 To: 'nznog' Subject: [nznog] Alternative DSL? Questions for NZNOG: In a new apartment building with CAT5 run from each unit to a central closet, installed by the developers, who owns the CAT5? If the CAT5 is the property of the building body corporate, is it permissable for an alternative network operator to install their own mini-DSLAM, and provide alternative DSL to building occupants? If this unit is not using Telecom lines, does it need to be Telepermit approved? If competitive DSL is run over spare pairs (not in use by TelecomNZ), will there be any implications for residents who subscribe to JetStream? Am I going to end up in pain for asking these questions? Cheers, Jon ********************************************************************** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz **********************************************************************

3 2

Re: [nznog] RE: Telecom Outage
by blair.robson＠ihug.co.nz 14 Jan '05

14 Jan '05

Actually other ISPs look like they were effected, Ihug's MOTD suggests this, SNAP had issues too. IPNET or lower level outage.... > > I am interested to know how many other ISPs are effected > by this. > > None. All ISP's using IPNET would be effected (so prolly most of em) > > > Must be a major at Telecoms end. > > What makes you say that ? actually, dont bother answering > this question. You are incorrect in your assumption. > > > Seems to have started at around 10am yesterday! > > Then no doubt they will be working on it, maybe you could > ring them and ask for updates instead of posting this > stuff to the list. I think he probably posted to the list due to a lack of notification. Looks like it has been resolved now anyway. -b. :)

1 0

RE: Telecom Outage
by James Butler 14 Jan '05

14 Jan '05

We run at T.Com DIA link here - from my end it appears that the primary DNS server (202.27.184.3) is down - I can get service only using their secondary James Butler IT Admin NewJobZ _________________________________________________________________ Check out news, entertainment and more @ http://xtra.co.nz/broadband

5 4

Re: [nznog] IPNET down?.........
by blair.robson＠ihug.co.nz 14 Jan '05

14 Jan '05

I would say that IPNET is down or something along those lines.. b. :) > > > > Hi Everyone, > Does anyone know of a fault with Telecoms IP network at > the moment if so any idea of a time it will be solved. > > If anyone has any info please reply. > > Regards > Adam > Dream Net > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Telecom outage?
by Dream Net Sales 14 Jan '05

14 Jan '05

Hi Everyone, Does anyone know of a fault with Telecoms IP network at the moment if so any idea of a time it will be solved. If anyone has any info please reply. Regards Adam Dream Net

4 4

[ISC-Ops #6939] routine maintenance for F-Root in Auckland
by Joe Abley 13 Jan '05

13 Jan '05

I am doing some router upgrades in Auckland which will likely cause some BGP sessions to reset. There is no expected impact on local F-root service. If anybody doesn't currently peer directly with the F-root node across the APE, please feel free to send your details to peering(a)isc.org and we'll get you set up.

2 2

NZNOG 2005 Draft Programme / Registration
by Donald Neal 12 Jan '05

12 Jan '05

A programme for next month's conference can now be read at the conference web site http://www.nznog.org/ . Changes to the programme remain possible. If you're coming, you need to register. This includes speakers, though speakers receive concessional pricing. Any speaker seeking a change to the time slot they have been allocated - whether a different length or a move to a different time - should contact me off list, preferably very soon. - Donald Neal Donald Neal |A prophecy is a guess that comes Technical Specialist |true. If it doesn't come true, it's NGN Operations |a metaphor. - G'Kar, Babylon 5 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

NZNOG - Payments - Late Fees
by Richard Nelson 12 Jan '05

12 Jan '05

Late fees will be charged for NZNOG registrants who have not paid, or arranged payments by Monday. This is an extension by one working day on the announced time. This means that if you have registered and chose the "Defer payment option" you must have arranged your method of payment by Monday afternoon and received confirmation from us. Cheque payments must reach us before the conference. Late fees will be 25% of the conference registration, i.e. the new fees will be: Conference $175 Student Rate $112.50 Tutorial Day $37.50 There are no late fees on accomodation or dinner tickets. Richard Nelson WAND Network Research

1 0

NZNOG - Programme
by Richard Nelson 12 Jan '05

12 Jan '05

The Draft Programme for this years NZNOG Conference is now available at http://www.nznog.org/programme.php Please note that Vijay Gill who was previously announced as a speaker is now not going to be there. Registrations are filling fast. There are no rooms with network ports left on either Wednesday or Thursday nights and there are only a few places left for some of the tutorials. Richard Nelson WAND Network Research

1 0

HEADS UP - Webcast activity - Tsunami Memorial Service
by Richard Naylor 12 Jan '05

12 Jan '05

On Sunday 16 January RadioNZ will be broadcasting an inter-faith memorial service live from Auckland. They will also be streaming it on the Internet via R2.co.nz. The stream will be on internationally routed numbers and not restricted. ISPs may notice some traffic changes and Help Desks may receive more calls relating to web based media. The event will be time limited to 1:15pm to 2:45pm and include one minutes silence at 1:59pm (the webcast will continue altho it will be silent) The RadioNZ web page with details of the event is at http://www.radionz.co.nz/tsunami/ Thanks for your co-operation Rich

1 0

calling wellington internet historians
by Dean Pemberton 12 Jan '05

12 Jan '05

Joe Wrote: [Oh, I think I still owe Dean Pemberton a beer for loaning us a power cable during that install that we never gave back.] Heh - yeah I remember that. I'll collect next month. Those stinky cisco boxes with their special power cables. From memory I might have stolen it from a jug or something we had lying around. More on topic though. I can remember a BOF session at Uniforum 1998 in which all the ISP's sat down and discussed peering. I seem to remember that it was some time after that that things started. That would put the timeframe for the idea at 21-23May 1998. The question of who was first is a hard one. WIX (the route servers) didn't start until later. But National Library peering with Clear would have been one of the first, and that was around July 1998 IIRC. The date on the AS number I applied for supports this kind of time changed: hostmaster(a)apnic.net 19980724 I think Actrix was doing something about that time too. And maybe one of the isp's starting with "I". Maybe it will become clearer over beer. See you all next month. Dean

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jan '05

12 Jan '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: AS9483 as-name: NZRR-AS9483 descr: Flatnet descr: WIX peering at '202.7.0.119' descr: see Citylink RT job #1715 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9483 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: routing(a)flatnet.gen.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050113 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9483 descr: Route set advertised to AS9439 by Flatnet - AS9483 members: 203.97.150.0/24^24-29, 202.0.32.48/29, 202.0.32.88/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)flatnet.gen.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050113 source: NZRR

1 0

APNIC's Training in conjunction with NZNOG'05 Conference
by APNIC Training 11 Jan '05

11 Jan '05

Dear NZNOG Members, APNIC is pleased to invite you to attend APNIC's Training in conjunction with the New Zealand Network Operators Group Conference 2005 as follows: "APNIC Internet Resource Management Essentials" Date: 02 February 2005 Time: Please refer to http://www.nznog.org/index.php. Venue: University of Waikato, Knighton Road, Hamilton, New Zealand Tel: +64 7 838 4466 Who should attend? ------------------ The target audience is technical personnel who are responsible for allocating and/or assigning IP addresses. For example, hostmaster employees of network information centers or ISPs, network planners, designers, and network engineers. Good understanding of networking fundamentals is assumed and upon completion a certificate of participation will be provided. Course Fee: ----------- For registration and other details at http://www.nznog.org/registration.php. A full abstract of the training course is also available at http://www.nznog.org/abstract/irme.pdf . For more information, please visit to http://www.nznog.org/index.php. Best regards, The APNIC Training Team ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ APNIC Training <training(a)apnic.net> Asia Pacific Network Information Centre Tel: +61-7-38583100 http://www.apnic.net Fax: +61-7-38583199 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ See you at APNIC 19 18 - 25 February 2005 Kyoto International Conference Hall (KICH) Kyoto, Japan http://www.apnic.net/meetings/19/index.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Talk Topic for me.
by Simon Lyall 09 Jan '05

09 Jan '05

Looks like I'll be doing a lightning (3-10 minute) talk at nznog this year since there are a couple of 5 minutes gaps. While I've got a fallback topic I'm wondering if anyone has anything they would be particularly like me to talk about. Maybe random email or Usenet stuff, system admin and design, cornflakes, curry, political or historical stuff. Pop me an email and I'll see how they look. No promises since (a) schedule is not confirmed yet and (b) I suspect some suggestions might be "unsuitable" . -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

6 5

ISP Details
by barry＠unix.co.nz 07 Jan '05

07 Jan '05

Hey guys, Im looking for the following details which will be published in an ispmap within the next month. Please reply off list with the ISP name in the subject of the email. ISP: URL: Telephone number: Fax Number: Dialin Number: POP3 Server: SMTP Server: Email Address: Postal Address: AS Number: Upstream Provider(s): The map will be on ispmap.co.nz and will show ISPs international connectivity. For an example of a generated map, please see http://www.ispmap.org.za/topmap.html . Im working with Gregory (author of ispmap.org.za) to add further functionality to the site. Thanks Kindest Regards Barry Murphy ------------------------------------------------------------- This mail sent through UnixCo Webmail: http://www.unix.co.nz/

1 1

calling wellington internet historians
by Joe Abley 06 Jan '05

06 Jan '05

Does anybody happen to remember when peering between ISPs in Wellington using network 10 addresses started happening? I remember Craig Anderson circulating a draft document reserving chunks of 10/8 for people, and some talk about static ARP, but I don't remember when it was. The current address block used on the WIX (202.7.0.0/23) was pulled out of Rex Croft's magic bag of spare addresses in July 1998, according to the list archives, so it was before then. If I was to document a start date for the WIX (e.g. "first BGP session between ISPs was set up", or maybe "first packet was exchanged between citylink/CNHL customers", or something) what would it be? Joe

4 6

NGN survey
by M. Salim KETEVANLIOGLU 04 Jan '05

04 Jan '05

Dear list members, I am working for Turkish NRA and studying for "NGN migration strategies and regulation" and "country applications". I plan to conduct a survey for incumbent operators and application creators for NGN. I would like to contact persons working ngn related in incumbents and application creators. Kind regards, M. Salim KETEVANLIOGLU Telecommunication Assistant Expert Telecommunications Authority Ankara / TURKEY +90 312 550 50 68

1 0

NZNOG 05'
by Joshua Brady 04 Jan '05

04 Jan '05

Hello all, I am booking my flight a bit late, but need to know what airport is going to be easiest to get to from the US. I will be flying KRIC to KLAS for NANOG, then want to transfer over to NZNOG from there (leaving early 02/01/05). Can anyone advise me on what exact airport I'll need to take? Then travel plans from there? Thanks, Joshua Brady

10 12

Re: [nznog] NZNOG 05'
by Ewen McNeill 03 Jan '05

03 Jan '05

In message <F63658CB-5E83-11D9-BF97-000D93B24C7A(a)isc.org>, Joe Abley writes: >On 4 Jan 2005, at 13:52, Joshua Brady wrote: >> One last question I have no problems driving in NZ with a US Licence? > >Your hire car will have three pedals instead of two; there will be this >strange lever in the middle that you use to change gears; the steering >wheel will be on the wrong side; the fuel will be called "petrol" >instead of "gas"; there will be roundabouts and the roads will actually >have bends in them. You can, and possibly should, ask for an automatic when you book your hire car, rather than a manual (stick shift). An automatic will restore the number of pedals to two (accelerator (gas) and brake), and remove the need to use the strange lever in the middle to change gears (well apart from selecting drive/park/reverse). I suspect at least half of most hire fleets are automatics so it shouldn't be too difficult to get one. Unfortunately the steering wheel will continue to be on the right hand side of the car, which you should consider a reminder to drive on the left hand side of the road :-) New Zealand roads specialise in bends, and from memory the Auckland -> Hamilton road is also through fairly rolling country so you'll have both gentle hills and bends to help keep you awake. You may also wish to keep in mind that speed limits are in kilometres per hour (not miles per hour), and speed limits are enforced with speed cameras in various (sometimes hidden) places; fortunately any hire car you get will also have a speedo showing kilometres per hour so it's just a matter of matching up the numbers. >Your US licence will be fine though, as far as I know :-) http://www.newzealand.com/travel/transport/driving-in-nz/driving-in-new-zea… It appears that providing your licence is current in the US, and you carry it with you (at all times while driving) you can drive in NZ for up to 12 months without a problem. Ewen

1 0

Re: [nznog] NZNOG 05'
by Ewen McNeill 03 Jan '05

03 Jan '05

In message <6cdc2eb4050104075957b23612(a)mail.gmail.com>, Joshua Brady writes: >I am booking my flight a bit late, but need to know what airport is >going to be easiest to get to from the US. I will be flying KRIC to >KLAS for NANOG, then want to transfer over to NZNOG from there >(leaving early 02/01/05). Can anyone advise me on what exact airport >I'll need to take? Then travel plans from there? Keep in mind that 1 Feburary 2005 Pacific Time is 2 Feburary 2005 in New Zealand for most of the day (all but 5 hours). And the US->New Zealand flight crosses the date line. So if you leave LAX on the evening of 1 Feburary 2005 you'll arrive in New Zealand on the morning of _3_ Feburary 2005, effectively missing out on 2 Feburary 2005 completely. As the NZNOG conference starts with tutorials on 2 Feburary, and the main conference on 3 February that doesn't leave you much spare time. Given that you have limited time, the best option is most likely to fly into AKL (Auckland, New Zealand) which is the closest major international airport. Then drive from there to Hamilton as Joe suggests. The flight will get in around 06:00 in New Zealand, and the drive will take about 2 hours, so you'll arrive just before the main NZNOG conference assuming you leave the US on the evening of 1 Feburary 2005. Both Qantas and Air New Zealand fly LAX->AKL daily, and most major US airlines code share those flights.[0] If you can get a good deal it may be worth considering flying into CHC (Christchurch, New Zealand), and getting a connecting flight from CHC to HLZ (Hamilton, New Zealand). HLZ is the closest airport to the conference (about 15 minutes in a taxi), but has limited international flights (mainly only from Australia). There are fairly regular connecting flights from CHC -> HLZ throughout the day with Air New Zealand and some with Origin Pacific; the connecting flights would take about 1 hour. If you had more time you could consider flying via Australia (BNE (Brisbane), SYD (Sydney) or MEL (Melbourne)), but the US-> Australia flight takes about 3-4 hours longer than US->AKL, and the Australia -> New Zealand flights take about 4 hours. With connections it'd probably add 10-12 hours to the travel time, which you don't have spare. Ewen [0] There are a few flights from AKL->HLZ (Hamilton, New Zealand -- the closest airport to the conference) daily, taking about 30 minutes flying time, but the first one is 11:50 so it's not much use to you.

3 2

The New Zealand Network Operators' Group
by Donald Neal 31 Dec '04

31 Dec '04

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next annual conference is to be hosted by the WAND group in Hamilton on February 2nd to 4th. That's less than five weeks away. See http://www.nznog.org/ for more information and to REGISTER NOW. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net.nz/ for details of the Auckland, Palmerston North and Wellington exchanges, and some information on others under construction. About This Mailing List This list has around 750 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

Telecom Outage
by Dream Net Internet 31 Dec '04

31 Dec '04

Hello Everyone, Happy New Year!! Does any one know of a Telecom outage around 8.30 last night (new years eve?) Regards Adam Fenech www.dreamnet.co.nz Check out our online store for great deals www.dreamnet.co.nz/store.html

3 2

Upcoming webcast activity
by Richard Naylor 29 Dec '04

29 Dec '04

The following webcasting activity is scheduled for the next few days/weeks. While we don't expect large volumes of traffic, Operators may like to be aware of the activity, as some communities of interest are involved that may generate extra calls to Help Desks. Scouts Jamboree - about now until about 8 Jan ------------------------- We are webcasting their Radio Station and TV station. The URLs are http://www.r2.co.nz/meta.jamradio.asx http://www.r2.co.nz/meta/jamtv.asx These are in windows media 9 format - available from MS. We hope they leave the encoding PC alone long enough for people to be able to listen/watch. It was all go just before my cup of tea.........<sigh> Radio Tarana ------------------- Radio Tarana are now webcasting 24/7 - off their web site www.tarana.co.nz - they are an AKL based Hindi radio station, so locals may be interested. Because of content rights, this webcast may be restricted to NZ based clients only. Radio NZ -------------- National Radio will be starting a programme series on 1 Jan, with each programme available for listening "on-demand" afterwards. The topic is Split Enz so may be popular. Because of RIANZ rights issues, the content will only be available to NZ based clients, using Anycast routing into WIX, where the server is located. ISPs not peering at WIX may receive Help Desk calls asking why the content won't play. On the other hand the weather may be really good and no one will bother with any of this....... Happy Christmas and New Year - Rich

2 1

Re: [nznog] [Inetnum object]
by Andy Linton 24 Dec '04

24 Dec '04

About a month ago Sid Jones and I had a conversation about one of his customers who has a /23 in this space. We raised the issue with APNIC and I attach the thread. There's a clear implication in the mail below that APNIC expect Telecom NZ to cooperate on this issue which seems to be at odds with their behaviour over 202.49.252.0 - 202.49.255.255 as David Robb has noted. I suggest a number of things here: 1) each ISP who routes portions of this block should encourage their customers to write to APNIC requesting that as this block was allocated via the University of Waikato which was operating as a proto NZNIC at the time then this address space should be deemed to be provider independent space which should be administered as other 'swamp' space. For example, here's a record that's recently been obscured as part of this exercise: inetnum: 202.36.137.0 - 202.36.137.255 > netname: NZMFE > descr: Ministry for the Environment > descr: P.O. Box 10-362 > descr: The Terrace > descr: Wellington > country: NZ > admin-c: MB22-AP > tech-c: MB22-AP > notify: dbmon(a)apnic.net > mnt-by: APNIC-HM > changed: hostmaster(a)apnic.net 19931217 > status: ALLOCATED PORTABLE > changed: hm-changed(a)apnic.net 20031020 > source: APNIC This is clearly PORTABLE space and makes no reference to Telecom NZ and the admin-c and tech-c details were updated just over a year ago. Note that this address was allocated in 1993 long before Netway (a Telecom NZ subsidiary) entered the picture at all. Why are APNIC changing the goal posts? 2) the customers should also write to Telecom NZ making clear that their portion of address space was not issued to Telecom NZ but to them by the University of Waikato (acting as a proto NZNIC) and that they want Telecom to relinquish control of this space back to APNIC. 3) I'd encourage APNIC to look again at this. 4) user groups such as InternetNZ, TUANZ etc need to get across this issue and raise it with Telecom NZ 5) I'd suggest the press get their teeth into this but that's probably not necessary as there's no story here. (:-) andy -------- Original Message -------- Subject: Re: [Fwd: [APNIC #624302] 202.27.0.0/16 and http://www.apnic.net/info/faq/privacy-faq.html (fwd)] (fwd) Date: Thu, 4 Nov 2004 09:20:59 +1000 (EST) From: John Tran <john(a)apnic.net> To: asjl(a)citylink.co.nz CC: Anne Lord <anne(a)apnic.net>, Elly Tawhai <elly(a)apnic.net>, Tim Jones <tim(a)apnic.net> Hi Andy, We have searched all our historical emails and records regarding NZNIC as well as all information relating to 202.27.0.0/16. Here is the summary of what we found. Before 1995, the following address ranges had been allocated by APNIC to the University of Waikato, which operated as a gateway for New Zealand, under the name NZGATE: 202.27/16 202.37/16 202.36/16 202.49/16 202.50/16 These ranges were allocated on the basis that NZGATE would make further allocations to their customers. In 1995, Netway Commnication Ltd took over the international gateway function from the University of Waikato and the IP addresses were transfered with APNIC's approval. Netway continued contracting University of Waikato staff to allocate IP addresses on Netway's behalf to its customers. NZNIC was then established by the University of Waikato to obtain provider independent addresses for other organisations like Clear Communication and Netlink. Netway was then transfered to NZtelecom in late 1997, along with the corresponding address space. In November 1998, because of the confusion in the Internet community in New Zealand about whether the address space that they obtained from the University of Waikato was portable or not, APNIC and Brett Telfer (Netgate) re-confirmed that the above ranges would be best managed by NZTelecom. Since then, these address ranges are used by APNIC to determine the membership tier paid by NZtelecom as outlined in: http://www.apnic.net/member/feesinfo.html NZTelcom is able to assist any organisation holding address space with reverse DNS and is able to change the status of DB object to public, if so requested. I hope the above information is useful for you. If you need additional information please contact us. If you would prefer to discuss this further, we can arrange a telephone conference. Regards Son ---------- Forwarded message ---------- Date: Mon, 25 Oct 2004 12:39:44 +1000 (EST) From: Anne Lord <anne(a)apnic.net> To: Andy Linton <asjl(a)citylink.co.nz> Cc: son(a)apnic.net Subject: Re: [Fwd: [APNIC #624302] 202.27.0.0/16 and http://www.apnic.net/info/faq/privacy-faq.html (fwd)] hi Andy, Thanks for your email. I'm no longer involved in handling resource requests, but I have copied Son Tran, the manager of the Member Services department, on this email, who is and who will be able to help you. It certainly looks like this warrants a much closer examination of the records and history and I am sure Son would be happy to talk to you. Best wishes, Anne cc: Son On Fri, 22 Oct 2004, Andy Linton wrote: > Anne, > > I've had a conversation today with Sid Jones about this mail. These blocks > were allocated to the University of Waikato which operated as the proto NZNIC > in the early nineties prior to APNIC handling this work. > > Aaron Scott who is listed in the changed record below went to work for Telecom > NZ when they took over handling the exchange point at Waikato. There are a > significant number of NZ government departments and other "blue chip" > identities listed in the records who don't use Telecom NZ as their ISP and who > believe that they have portable space. Some of them have /21 allocations and > perhaps even /20 allocations. > > This whole set of blocks really should be considered as swamp space. > > I will be raising this issue on the NZNOG mailing list suggesting that those > entities who have had these blocks allocated to then for periods in the order > of 10 years or more should contact you asking for clarification of their position. > > I think it would be good if APNIC took a good look at the allocations within > these ranges and considered what's going on here. > > Happy to discuss - +64 4 910 5654 > > andy > > ---------- Forwarded message ---------- > Date: Thu, 21 Oct 2004 13:44:30 +1000 > From: gpan via RT <helpdesk(a)apnic.net> > To: sid(a)tsnz.net > Subject: [APNIC #624302] 202.27.0.0/16 and > http://www.apnic.net/info/faq/privacy-faq.html > > > Dear Sid, > > Thank you for your enquiry. It was proposed at the APNIC 16 > meeting in 2003 that customer assignments (and sub-allocation > records) need no longer be publicly accessible via normal > 'whois' queries to the APNIC Whois Database. > > Customer registration records must still be registered within > the APNIC Whois Database, in order to document address > utilisation, however a new 'public' database attribute has been > created to allow these records to be excluded from public whois > query results. This is why you are unable to receive any > result when querying the APNIC Whois Database about this > particular /23. You will get the result as: > > inetnum: 202.27.0.0 - 202.27.255.255 > netname: NZGATE-NZ > descr: NZ Gate National Service Provider > descr: Component of University Of Waikato > descr: New Zeland > country: NZ > admin-c: DBK1-AP > tech-c: KS61-AP > remarks: service provider > notify: dbmon(a)apnic.net > mnt-by: APNIC-HM > mnt-lower: NZTELECOM > changed: ARRON(a)WAIKATO.AC.NZ 19950612 > changed: hostmaster(a)apnic.net 20020208 > changed: hm-change(a)apnic.net 20020621 > status: ALLOCATED PORTABLE > source: APNIC > > Information contained within the historical records outlines that > NZTelecom has full authority over the following blocks: > > 202.27.0.0/16 > 202.36.0.0/16 > 202.37.0.0/16 > 202.49.0.0/16 > 202.50.0.0/16 > 203.96.0.0/17 > > Information from those records also outline that the assignments from > these ranges are non portable. > > 202.27.xx.0/23 > > This address space is from a block allocated, by APNIC to NZTelecom. > This means that all assignments made from this block are non portable. > > If your customer would like to see or change their records in APNIC > whois database, please advise them to contact NZ Telecom. > > Best Regards, > Guangliang > > ____________________________________________________________________ > Guangliang Pan, Internet Resource Analyst <gpan(a)apnic.net> > Asia Pacific Network Information Centre phone: +61 7 3858 3100 > http://www.apnic.net fax: +61 7 3858 3199 > Helpdesk phone: +61 7 3858 3188 > email: helpdesk(a)apnic.net > > Please send Internet Resource Requests to <hostmaster(a)apnic.net> > _____________________________________________________________________ > > > [sid(a)tsnz.net - Wed Oct 20 12:27:02 2004]: > > > Hi > > > > I'm writing to you on behalf of one of my customers XXXXXXX > > as we have something of a dilemma. > > > > I believe the XXXXXX applied for some PI address space from the > > university of waikato sometime in the mid-1990s and were allocated > > 203.27.xx.0/23. > > > > I also believe this space was "swamp" space and not allocated to any > > of the various service providers in New Zealand. > > > > > > They have had this space routed to them via effectively the same > > provider since then. The provider for the past 3 years has been > > TelstraClear NZ Ltd, prior to that it was Telstra NZ Ltd and > > previously Netlink > > > > Can you please clarify who the /23 is allocated to. > > > > Can you please clarify if the customer can still use this space while > > connected to the provider they have had for the past decade. > > > > Further if this is the case how do we get the current records updated > > to reflect this sub-delegation. I'm also curious as to what effect > if > > any this has on other customers I have in 202.27/16 > > > > >

9 8

Exim 4 Book
by Jamie Curtis 20 Dec '04

20 Dec '04

Hi all, As Richard announced late last week, Philip Hazel, the lead author of Exim, is attending NZNOG to give a full day workshop on the configuration and administration of Exim servers. A few people have indicated that the Exim 4 book (http://www.uit.co.uk/exim-book/) is hard to get hold of in NZ and Philip recommends it in addition to the Exim tutorial. I have talked to the publisher of the book, and we can arrange a direct shipment of the books to NZ from the UK for the tutorial. They have offered us the book, including shipping, for slightly less than GBP 30, or about NZ$80. This price comes down to less than NZ$70 as we order more. We can only get these prices if we order suitable quantities, so I need people to indicate to me if they are interested in purchasing the book at the tutorial. If we get enough numbers, I will confirm to all interested the exact price before we place the order. As they have to be shipped to us in time for NZNOG at the start of Feb, we need to know numbers ASAP. Cheers, Jamie ----------------------------------------------------------------------- Jamie Curtis office: G.1.01 WAND Group, Dept of Computer Science phone: +64 7 838 4136 University of Waikato, mobile: +64 21 392 102 Hamilton, fax: +64 7 858 5095 New Zealand email: jamie(a)wand.net.nz -----------------------------------------------------------------------

2 2

Orcon contact me
by Jamie Baddeley 16 Dec '04

16 Dec '04

can someone from Orcon contact me offlist ASAP please. jamie

1 0

Re: [nznog] NZNOG Tutorials
by Richard Naylor 16 Dec '04

16 Dec '04

At 08:41 AM 12/17/2004 +1300, Jamie Baddeley wrote: >On Thu, 2004-12-16 at 22:55, Simon Blake wrote: > > He's always keen as mustard for non-royalty-attracting audio, in > > whatever format you've got. If you don't send him something, you got no > > rights to whinge at what he plays. > > >http://creativecommons.org/wired/ > >No whinging from me then! noted - I'll make up a new disk :-) rich

1 0

NZNOG Tutorials
by Richard Nelson 16 Dec '04

16 Dec '04

We have more tutorials for NZNOG'05! Philip Hazel, lead author of Exim is coming from Cambridge, UK to give a one day tutorial on configuring this MTA. Juniper are providing a hands on tutorial on "Border Routing in ISP and Large Private Networks". Due to the hands on nature of this tutorial it is limited to 16 places only. Places will be allocated first come first served based on registration time and a reserve list will be kept. Note that registering for this tutorial does not guarantee a place. Places will be confirmed by email. As always full details are on the website http://www.nznog.org . You can choose which tutorial you wish to attend when you register. Note that any attendees who have already registered and paid for NZNOG'05 who wish to change their details due to these announcements should email registration(a)nznog.org. Due to the first-come first-served arrangements for the Juniper tutorial, these people will get priority. Richard Nelson WAND.

5 6

NZNOG International Speakers
by Richard Nelson 15 Dec '04

15 Dec '04

We are working as hard as possible to confirm the speakers for NZNOG, but it will still be some time till the complete programme is available. To help people who are deciding whether to come, here is the latest list of the planned international speakers. (Topics are still provisional.) Confirmed: Vijay Gill (AOL) "Big Fast Networks" Bill Woodcock (PCH) "INOC-DBA" Bill Norton (Equinix) "Peering" Joe Abley (ISC) "History of NZ Peering" Subject to final confirmation George Michaelson (APNIC) "Address Space Usage" Bill Manning (EP.net) "DNSSEC" Biographical details and talk abstracts will be added to the website as they become available. We also have a couple of extra tutorial streams to add. These will be advertised later today. People who have already registered for NZNOG will be given the opportunity to enroll for these. Richard Nelson WAND

2 1

SPF problems with nznog registration.
by Steve Phillips 15 Dec '04

15 Dec '04

um.. This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: richardn(a)cs.waikato.ac.nz (generated from registration(a)nznog.org) SMTP error from remote mailer after MAIL FROM:<steve(a)focb.co.nz> SIZE=1986: host mail.cs.waikato.ac.nz [130.217.241.36]: 550 Please see http://spf.pobox.com/why.html?sender=steve%40focb.co.nz&ip=130.217.250.15&r… ------ This is a copy of the message, including all the headers. ------ Return-path: <steve(a)focb.co.nz> Received: from [64.246.60.77] (helo=wibble.focb.co.nz) by warlock.cs.waikato.ac.nz with smtp (Exim 3.35 #1 (Debian)) id 1CegkR-0005mq-00 for <registration(a)nznog.org>; Thu, 16 Dec 2004 10:31:51 +1300 Received: (qmail 10492 invoked by uid 501); 15 Dec 2004 21:31:49 -0000 Received: from localhost (sendmail-bs(a)127.0.0.1) by localhost with SMTP; 15 Dec 2004 21:31:49 -0000 Date: Wed, 15 Dec 2004 15:31:49 -0600 (CST) From: Steve Phillips <steve(a)focb.co.nz> To: registration(a)nznog.org Can you guys please fix your registration/mail system ? and someone really should be told that bouncing mail based on SPF records alone is a bad thing [tm] (sending here because I cant seem to mail them directly..) -- Steve.

4 4

RE: [nznog] SSH login attempts
by Philip D'Ath 14 Dec '04

14 Dec '04

No. Most of ours have come from (so far): 64.191.62.135 61.59.33.44 217.107.212.104 219.240.134.41 213.215.76.1 -----Original Message----- From: Chris Hodgetts [mailto:chris(a)archnetnz.com] Sent: Wednesday, 15 December 2004 9:40 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] SSH login attempts Were the majority of attempts comming from: 210.0.192.40 Thats where I seem to be getting the majority of my attempts from. <snip>

2 1

RE: [nznog] Bedlam DL3
by Hamish Macewan 14 Dec '04

14 Dec '04

More scary than funny, the math I mean: "We've got well over 100,000 mailboxes in our email infrastructure, [deletia] he created several distribution lists. Each distribution list had about a quarter of the mailboxes in the company on it (so there were about 13,000 mailboxes on each list)." A quarter of 100,000 is ~13,000? But later: "Remember, there are 25,000 people on this mailing list." Later still: "First off, the original mail went to 13,000 users." Further: "For the sake of argument, let's assume that 10% of the recipients on each message (130) are on each server." 10% of 13,000 would be 1,300? Not in MS land it would seem. It would seem that Corporate blogs are either as garbled as Corporate email or they actually have no clue. Hamish. -----Original Message----- From: James J. Guidera [mailto:james(a)miracle.co.nz] Sent: Wednesday, 15 December 2004 8:52 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Bedlam DL3 As a Wednesday morning laugh, Many people read the blog on msdn on Bedlam DL3? Bit of a laugh.... http://blogs.msdn.com/exchange/archive/2004/04/08/109626.aspx Cheers James

1 0

Re: [nznog] Bedlam DL3
by Lesley Walker 14 Dec '04

14 Dec '04

>Many people read the blog on msdn on Bedlam DL3? > >Bit of a laugh.... >http://blogs.msdn.com/exchange/archive/2004/04/08/109626.aspx Good to see them get a taste of their own medicine. I have no sympathy (for the company) whatsoever, they should have designed the MTA better. (Plenty of sympathy for the poor bastards who had to deal with it though) Lesley Walker Former Exchange admin

1 0

Re: [nznog] SSH login attempts
by Anton Smith 14 Dec '04

14 Dec '04

> Moving the ssh port to something else that 22 seems to help as well. > > -- > Juha Port knocking is an interesting method of protecting your machine. If you're a debian user apt-get install knockd - comes with a fairly simple configuration file as well. The only problem with this is generating the knock sequences, especially when you are out and about and on a foreign machine (can still be done using the venerable telnet for syn packets but netcat or nemesis would be better). Regards, Anton Smith

1 0

SSH login attempts
by Philip D'Ath 13 Dec '04

13 Dec '04

We are getting lots of requests at the moment trying to log into one of our box's via SSH. It happens in 20 minute bursts, with a new request being tried every 6s. After the 20 minutes it goes away for 8 hours. It appears to be a straight dictionary attack, with the attempts cycling though usernames like root, user, test, john, henry, george, frank, alan, adam, server, backup, account, master, sybase, oracle, web, data, webmaster, noc, cip51, cip52, cosmin, pamela, jane, adm, irc, apache, operator, mysql, www-data, matt, www, wwwrun, cyrus, horde, iceuser, rolo, patrick, nobody. It spends most of its time trying to login as root. The requests are mostly coming from Russia, with a couple of other IP's from other countries. The device they are attempting to log into is not advertised in anyway, so was probably picked up during a normal port scan. For the moment I've limited connections to the box for SSH to only be accepted over IPSec, so that's the end of the login attempts. I guess what I'm posting this for is to make sure everybody has a good password policy in place. Someone is actively trying to compromise accounts via SSH.

6 6

Bedlam DL3
by James J. Guidera 13 Dec '04

13 Dec '04

As a Wednesday morning laugh, Many people read the blog on msdn on Bedlam DL3? Bit of a laugh.... http://blogs.msdn.com/exchange/archive/2004/04/08/109626.aspx Cheers James

2 1

XML schema for interface configuration
by Cameron Kerr 12 Dec '04

12 Dec '04

Does anyone know of, or has found a useful XML language for modelling network interface configuration? I just need the basics, more precisely IPv4 interfaces. Manual and DHCP configuration (maybe also ZeroConf) Subnetmask Routes (static, but dynamic would be good also) IPv6 interfaces. ??? DNS configuration Other stuff? (tunnels, p-t-p interfaces, ...) I could model one myself, but I would much prefer input from something more time-proven. I don't need anything with a formal schema. -- Cameron Kerr cameron(a)humbledown.org; http://humbledown.org

2 1

NZNOG Registrations
by Richard Nelson 09 Dec '04

09 Dec '04

Registrations for next years NZNOG Conference are now being accepted at http://www.nznog.org. The conference is again being hosted by the WAND Network Research Group at the University of Waikato. Last year we had 125 registrations. The largest lecture theatre holds 140 so places are strictly limited. There is a tutorial/workshop day before the conference. Tutorials that we have confirmed are: APNIC - IRME LinkIT - Trango Wireless InternetNZ - Spam Handling Accomodation is available on campus. Some rooms (28) are available with Ethernet ports which will be allocated first come first served. All prices and details are available on the website. Late registrations (after January 14) will incur late fees. The main overseas speakers will be confirmed shortly... Richard Nelson WAND.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Dec '04

08 Dec '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 9 Dec 2004 12:48:25 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0412091247560.28480(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.101.112/29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041209 source: NZRR

1 0

[Apnic-announce] Protecting historical records in the APNIC database (fwd)
by John Tran 05 Dec '04

05 Dec '04

Hi all, Just following from last week emails. Here is an announcement that could be interested to some of you. If you wish to know what happening in the APNIC community please subscribe to apnic-annouce mailing list which is available at: http://www.apnic.net/community/lists/index.html Regards son ---------- Forwarded message ---------- Date: Mon, 06 Dec 2004 14:56:11 +1000 From: APNIC Secretariat <secretariat(a)apnic.net> Reply-To: apnic-talk(a)apnic.net, secretariat(a)apnic.net To: apnic-announce(a)apnic.net Subject: [APNIC Members] [Apnic-announce] Protecting historical records in the APNIC database Dear colleagues, The APNIC Secretariat will implement a policy on 14 December 2004 to protect historical records in the APNIC database from unverified transfers, abuse, and unauthorised use. The proposal document, presentation, minutes, and discussion are available at: http://www.apnic.net/docs/policy/proposals/prop-018-v001.html Please note, after 14 December 2004, the maintainer of all historical resource registrations will be changed to "APNIC-HM". To ensure the integrity of information in the APNIC Whois Database, APNIC will not update historical information in the APNIC Whois Database unless the resource holder can establish its right to the resources and enters a formal agreement with APNIC, either as a member or as a non-member account holder. Further details and all supporting documentation will be available on 14 December. If you have any questions regarding this policy, please contact the APNIC helpdesk at: E-mail: helpdesk(a)apnic.net Phone: +61-7-3858-3188 Fax: +61-7-3858-3199 Regards ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ---------------------------------------------------------------------- See you at APNIC 19 Kyoto, Japan, 21 - 25 February 2005 www.apnic.net/meetings ----------------------------------------------------------------------

1 0

APRICOT 2005
by Neil Fenemor 05 Dec '04

05 Dec '04

Can anyone who is going to be attending the next APRICOT in Kyoto, Japan, please drop me a message off list. I wish to discuss beer (just to keep this somewhat near being on topic) Cheers neil

1 0

Viruses originating from Xtra network
by Lesley Walker 05 Dec '04

05 Dec '04

Please forgive me if this is off-topic, I don't know anywhere else to ask for help. How does one get the attention of the abuse people at Xtra? A mailing list that I administer is being attacked by viruses that originate at a Jetstream address (details below). I sent email to abuse(a)xtra.co.nz a couple of days ago and have not had the courtesy of a response, not even a "sod off" answer, or even a bounce. The viruses come in batches from a consistent IP address - the address has changed a couple of times but I think it's the same infected machine because the messages have a consistent "look and feel". The received header looks like this: Received: from srunjn.com (210-86-89-213.jetstream.xtra.co.nz [210.86.89.213]) by [munged] with SMTP id iB1CGab26947; Thu, 2 Dec 2004 01:16:36 +1300 (NZDT) The envelope "from" appears to be randomly generated nonsense as it is different every time, but the originating IP address is consistent for each batch. The messages are designed to look like bounces from various ISPs and companies but in fact contain virus attachments. The latest originating address is 210.86.90.246, as at Sat, 4 Dec 2004 08:36:21 +1300 (NZDT) -- Lesley Walker, Wellington, New Zealand LRW(a)clear.net.nz http://home.clear.net.nz/pages/lrw http://walkinguphills.blogspot.com/

11 12

Re: [nznog] Viruses originating from Xtra network
by Lesley Walker 04 Dec '04

04 Dec '04

Glen wrote: >As one would expect, Xtra get a fair few notifications and I must admit that >I was more than a little surprised to find that their 'abuse team' are the >most responsive of all the ISPs in NZ !! They acknowledge the notifications >by automated return mail and as each incident is closed we get a closure >report. I spoke with them by phone when we were getting the system setup and >they were very supportive and helpful. Then I have to conclude that my email didn't actually get through. But I haven't received a bounce, so it must have been dropped into the bit-bucket somewhere along the way. I must admit it's easy to fall into the trap of treating email as if it were a guaranteed-delivery system so if I've maligned them unfairly I apologise, and I'll try again and see what happens. >Most of the ISPs we send the notifications to are taking them seriously and >do do something. Private companies that have no abuse, no postmaster >address etc are proving to be a pain and there are quite a few of them. I can relate to that! Thanks for your comments. Lesley.

1 0

Re: [nznog] Viruses originating from Xtra network
by Lesley Walker 03 Dec '04

03 Dec '04

Thanks to all who have commented. I will try again when I have time to wait out the infinite hold, and I may try that "Complex" number. I do understand about the need for the IVR to do the right thing for the company's needs, it just bugs the hell out of me that it keeps trying to send me to a sales dude when I'm trying to reach support people. I'm prepared for coping with call centre helpdesk people, if only I can get through to them. I know I sent them enough information to track the user when I emailed them, but what I don't know is whether anyone is paying any attention to the email. A response with a trouble ticket number would be nice, but even an auto-responder would let me know for sure that the mail got through. In the absence of a bounce, I would expect at least an auto-response. Mark Foster wrote: >Noone you talk to over the telephone is going to give you real time >support on a virus infection issue. Of course not. All I want them to do is log a trouble ticket and send it to someone who can (a) understand it, and (b) do something about it. >Their security team do deal with all valid emails to abuse@ even if they >don't acknowledge them directly. Also please bear in mind that nomatter >what ISP is involved, all customers need time to be warned, and get fixed, >before theyll have their accounts nuked. Its a tough call to take someone >off the internet when their only hope is software that needs to be >downloaded _from_ the internet... Sure. But someone who is sufficiently Internet-enabled to have Jetstream probably either has a clue or knows somebody who does, and I would hope that they just need to to be told about it. >Disclaimer: I don't represent Xtra or Telecom or anyone else except yours >truly. This is based on my experiences as an Xtra customer and someone who >has reported virus to Xtra Abuse Team many times! Accepted. >PS: The 'Dial 0' trick is a cop out. With a company as big as Xtra, you >can't realistically expect them to leave a Dial 0 option in there _and >then_ expect to keep call durations down - you wont get the answer you >want from a receptionist, will you? No, but if the IVR doesn't provide appropriate options, I expect a receptionist to be able to put me through to somebody appropriate. They're supposed to know who does what in their organisation. > If their support staff are busy, >theyre busy. Sit on hold, try again later, or email them. (And hope that >they realise their Queues are busy (and they will, theres enough software >there tracking their Queue stats) and modify staffing levels as a result >(also standard callcentre practise.) I hope I don't have to keep waiting while they go out and hire more staff. That'd be a pretty long call! :-) (The batteries in my phone woulf go flat) Thanks again. Lesley.

1 0

Broadband connectivity
by Andy Linton 03 Dec '04

03 Dec '04

While we debate the merits (?) of DSL connectivity and how to handle modem pools here's an example of a service available in Japan. The last couple of pictures tell the story! > Got my 100Mb fiber optic installed yesterday...the connection is > humming. I found the whole process very interesting and think that it > is just amazing. The actual fiber is thinner than a human hair and its > just fantastic. > free install, free for two months, unlimited traffic and no more than > $100 NZD/month. > > I am one happy man : ) > > http://www.jesse-taylor.com/new/misc_images/100mb_install/index.htm

8 8

APRICOT 2005 in Kyoto, Japan
by Philip Smith 03 Dec '04

03 Dec '04

Hi everyone, This is to let you know that the registration for APRICOT 2005 in Kyoto, Japan, from 18th to 25th February 2005 is now open. APRICOT is the Asia Pacific region's Internet operations and technology conference, and consists of workshops, tutorials, conference, as well as the 6 monthly APNIC meeting. Full information about APRICOT 2005 can be had at www.2005.apricot.net. Registration and accommodation information is at: www.2005.apricot.net/registration.html www.2005.apricot.net/accommodation.html You are encouraged to register as soon as possible as the early bird registration discount finishes on the 12th of January. Hope to see you in Kyoto early next year! philip --

1 0

Dialup / Radius
by Blair Harrison 02 Dec '04

02 Dec '04

Hi People, After all the hubbub of DSL activity of late, has anyone been having any issues with Dialup? If you are, are your upstream dialup providers putting priority into solving any dialup issues? I've talked to a few people and it seems that Telecom's IPNet dialup service seems to suffer missing RADIUS Stop records and that this activity seems to have been going on for a long time.. Has anyone ever managed to get an answer out of Telecom as to why this occurs? I'm also wondering how many missing records we're talking about here, does anyone have any actual numbers? Has it increased over the last couple of months? Missing RADIUS records seem to have been just a "fact of life" for most ISPs I know of for some time now, but I'm just wondering to what extent this occurs elsewhere.. Lately we've been noticing a somewhat increased number of missing stop records- to the point that some of our RADIUS-dependant services are suffering a few "errors" .. requiring some extra "fixes" to get around the issue.. One would think that being such a core service, every RADIUS issue ever concieved should have been eliminated years ago.. Obviously some of our national providers think otherwise.. Comments? Please feel free to reply to me offlist. Regards, Blair Harrison Systems Administrator WISE Net | http://wise.net.nz

5 5

[Fwd: IOS and Growing BGP tables]
by Andy Linton 02 Dec '04

02 Dec '04

I've not seen this discussed on nznog. ---------- Forwarded message ---------- Date: Thu, 2 Dec 2004 14:39:01 +1000 From: David J. Hughes <bambi(a)Hughes.com.au> To: Oz-ISP Mailing list <aussie-isp(a)aussie.net>, isp-australia(a)isp-australia.com Subject: [Oz-ISP] IOS and Growing BGP tables Hi, I'm posting this in an attempt to raise a bit of support. I've been arguing for a feature enhancement for IOS that will prolong the life of most Cisco routers that take a full BGP table. The growth of the table is causing concern for many major providers who can see the RAM on their lower end 7200's running out in the near future. Their default solution is not to upgrade the boxes, but to filter out the /24 advertisements. However, for many years in Australia, a /24 was the normal allocation. If they blindly filter out all the /24's then lots of networks in Australia (and other countries) will become unreachable. The proposed features allows you to filter a prefix if there is a less specific prefix already in your table (with various tuneable knobs with respect to next hop etc). Some guys at Cisco have taken this on and filed a bug / feature request for this. The more people that open a TAC case and have it linked to this bug ID the higher the priority of this request will become. It's being supported on the Cisco-NSP mailing list but I thought it worth "rattling the cage" on these lists as well. The more voices the better. The Cisco Bug ID is "CSCsa45474 : Ability to block overlapping BGP prefixes from being installed in RIB". Some history of the discussions is included below. If you have a TAC account and are so inclined, please open a new case and ask the engineer to link it to this bug ID. Thanks Bambi ... Begin forwarded message: > From: David J. Hughes <bambi(a)Hughes.com.au> > Date: 1 December 2004 10:26:18 AM > To: 'cisco-nsp' <cisco-nsp(a)puck.nether.net> > Subject: Re: [c-nsp] Growing BGP tables > > > I hope that most people on this list would open a case to try to get a > feature like this included in upcoming IOS releases. It's about the > only thing that will extend the life of your "RAM limited" routers > without breaking connectivity to historically legitimate /24 > allocations. > > > David > ... > > > On 01/12/2004, at 9:40 AM, Rodney Dunn wrote: > >> For those that have the ability to open a TAC case and they think >> this is something they could use, open a case and have the TAC >> engineer attach the case to this bug: >> >> CSCsa45474 >> Externally found enhancement defect: New (N) >> Ability to block overlapping BGP prefixes from being installed in RIB > ------ Begin forwarded message: Anything that reduces the consumption of RIB and FIB resources as a result of de-aggregation etc would be a very welcome step in the right direction. Thanks for looking into this Rodney. David ... On 24/11/2004, at 3:33 AM, Rodney Dunn wrote: > My point was that you can't do it with BGP > because you don't have a way to request a > re-advertisement from a peer when the > less specific goes away. > > There is a possiblity we could keep the > more specifics out of the RIB which would > save memory there and in the FIB. > > That being said the best that can > be done currently appears to block > the routes from going in the RIB. > We are looking to see how complex that > would be to do. > > Rodney > > > On Tue, Nov 23, 2004 at 11:11:52AM -0600, Brian Feeny wrote: >> >> >> I like this, basically all your doing is getting rid of the redundant >> information which serves no purpose other than taking up space in the >> RIB/FIB anyways. And if someone should further deaggregate or make a >> change, then the new update is going to run its algorithm against the >> current RIB all over again. >> >> >> On Nov 22, 2004, at 4:16 PM, David J. Hughes wrote: >> >>> >>> Hey Rodney, >>> >>> How about ... >>> >>> for each prefix received in update >>> for each more specific prefix in RIB >>> if RIB prefix ge /24 and same next hop as update prefix >>> drop RIB prefix >>> if update prefix ge /24 >>> for each less specific prefix in RIB >>> if RIB next hop same as update next hop >>> drop update prefix >>> >>> something like that would filter during the update and wouldn't >>> require another full copy of the table to be held. I'm sure you >>> guys could come up with something more efficient but the basic idea >>> would work wouldn't it? >>> >>> >>> David >>> ... ---- email "unsubscribe aussie-isp" to majordomo(a)aussie.net to be removed.

1 0

Re: Rescue from alligators in the swamp - note from APNIC
by John Tran 02 Dec '04

02 Dec '04

Hello all, This is a follow up to my previous email. Assignments within the blocks listed below have been restored to the public APNIC Whois Database. If you wish to make any of these assignments private or if you have any questions or concerns please do not hesitate to contact APNIC helpdesk at <helpdesk(a)apnic.net> or phone +61-7-3858-3180. Kind regards, Son > > > 5) Next steps > > > ------------- > > > Under the database privacy policy, all non-portable assignments and > > > non-portable sub-allocations that have not been specifically marked as > > > public have now been made private. However, because some allocations > > > and assignments within certain ranges appear to have been considered > > > 'portable' by default from earlier practices in New Zealand, APNIC > > > will restore the affected ranges from private to public. The ranges > > > in question are: > > > - 202.27.0./16 > > > - 202.36.0.0/16 > > > - 202.37.0.0/16 > > > - 202.49.0.0/16, and > > > - 202.50.0.0/16 > > > > > > Anyone holding addresses from these ranges that they wish to be made > > > private, should contact APNIC helpdesk. The update will be done this > > > week.

1 0

Re: [nznog] Rescue from alligators in the swamp - note from APNIC (fwd)
by John Tran 02 Dec '04

02 Dec '04

Dear Mathew, >*SNIP* a really interesting e-mail > >First, John, that was most enlightening. Thanks. > I am very pleased to read that it was helpful. Thanks. >One point that was raised in this discussion is that, for many NZ (and >other pacific-based) organisations, a /21 is a huge requirement. A lot >of companies can justify a /24, maybe even a /23, or a /22 at a stretch, >but a /21 is just out of the realms of possibility, probably ever. There will always be a balance between aggregation in the routing table and conservation. Not everyone can have portable address space. However as the years have progressed the trend in the community has been to agree to smaller sized initial allocations, recognising that there are those out there with smaller requirements. To qualify for a /21 allocation an organisation needs to demonstrate that they need /23 immediately and /22 in 12 months time. By "allocation" I mean that the organisation has customers that they wish to assign non-portable address space to. If an organisation does not qualify under this policy and is multi-homed or about to be multi-homed, they can apply for an address assignment under the "Small Multi-homing policy". By "assignment" I mean that they will use the address space on their own network and it will not be delegated to customers. There is no minimum or maximum size under this policy. You can find more information on both at: http://www.apnic.net/docs/policy/add-manage-policy.html >APNIC policies seem to be more biased towards the A than the P, even >with >the change from /20 to /21. I do recognise what you are saying. Indeed APNIC has appointed 'liaison officers' for both the Pacific and for South Asia to try to ensure that needs and voices are heard. At the same time there are many ISPs or organisations throughout the entire region with smaller requirements , and perhaps you are observing that it is the large guys who tend to get involved. You need only think of Nepal, Laos, Thailand, Indonesia...... there are many others of course. >... Obviously a country could set up an NIR to >do >smaller allocations, but a lot of the little islands out there are >unlikely to have the infrastructure to run their own NIR with any kind >of >reliability. Not to mention that their sub-allocation requirements >wouldn't justify the resources and expense. The best place to raise these concerns are on the Policy SIG mailing list. I would recommend that you subscribe. More information is at: http://www.apnic.net/community/lists >With this in mind, is there anything that can be done to create >something >like a sub-RIR under APNIC to better serve the needs of the large number The only sub-structures currently within the membership structure are the NIRs and LIRs. NIRs are obligated to follow the policies of APNIC, so that the minimum size will be the same. However they are free to develop some policies that are specific to local conditions. >can >suggest policy, but the actual voting is weighted towards large In policy making there is no voting. (In determining fee structures there is as this is deemed a membership issue). The principle observed is 'consensus'. This means that the majority has to agree. One hand is raised for each person in the room and we try to include those that are participating remotely. It is not necessary for you to turn up to have a voice. Aside from the remote participation facilities (jabber, webcast) there are also periods before (one month) and after (2 months) the meeting where policies are sent to the mailing lists for further comment. The aim of all this is to try to maximise the input across the region, recognising that not everyone can make it to the meeting or can comment at the appropriate time. I hope this helps. Kind regards Son

1 0

Blackholing rfc1918 queries
by Simon Lyall 02 Dec '04

02 Dec '04

Does anyone know the current correct way to blackhole queries for rfc1918 reverses using Bind9? I had a look at as112.net (and 192.0.32.18/31) and googled a bit but I can't seem to find anything. I'm sure somebody was going on about it a year or so back and encouraging everybody to but a certain config in. -- 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] makana.co.nz spam ?
by Mark Foster 01 Dec '04

01 Dec '04

Their Pri NS appears to have IP 202.27.187.82, which based on traceroute is carried via Telstraclear to Snap. Further, if you whois you'll see that its clearly Snap aka Netaccess Christchurch. You may like to try abuse(a)snap.net.nz as a guess. But i've not heard of them before, if it helps. Mark. On Thu, 02 Dec 2004 13:27:08 +1300, Simon Byrnand <simon(a)igrin.co.nz> wrote : > Hi All, > > Has anyone else receved spam from "Makana Confections" <sales(a)makana.co.nz> > recently ? (Or in the past) > *snipped*

1 0

makana.co.nz spam ?
by Simon Byrnand 01 Dec '04

01 Dec '04

Hi All, Has anyone else receved spam from "Makana Confections" <sales(a)makana.co.nz> recently ? (Or in the past) They seem to be at it again, sending unsolicited "promotions" of their products despite previous complaints. Back in April this year they spammed hundreds of our customers (including me personally) with almost identical material to this latest batch, and at the time I forwared abuse complaints to the only relevant email addresses I could find, including soa(a)saraden.co.nz, postmaster(a)saraden.co.nz and abuse(a)saraden.co.nz who going by domainz records appear to be their webhost. At no time did I ever receive any response. Thanks to the wonders of "private" APNIC entries for NZGATE ranges where the address block that the sending mail server resides, its hard to find much more information ;-) (Hopefully that will change if APNIC goes ahead with making the private entries public again) Anybody heard of these guys ? Sent complaints to them before ? Regards, Simon Byrnand iGRIN Internet

1 0

Re: SPF and mail forwarding (was Re: [nznog] Sendmail Question)
by Ewen McNeill 01 Dec '04

01 Dec '04

In message <20041128083138.GB27487(a)walnut.gen.nz>, Richard Hector writes: >On Sat, Nov 27, 2004 at 12:20:03PM +1300, Ewen McNeill wrote: >> usera(a)ispa was one address so subscribed. Unfortunately usera(a)ispa >> actually forwards mail to userb(a)ispb, without rewriting the envelope >> from address -- [bounces because SPF check failed at ispb MX] > >Perhaps I'm a little confused, but if usera is rejecting mail from >servers that he has arranged to forward him mail, that's his own silly >fault? usera doesn't run the mail servers at ispb (or ispa for that matter). It is ispb's mail servers that are doing the SPF check, and rejecting the message, because it's been forwarded in a way that is not compliant with SPF. Other than complaining to ispb -- and they probably wouldn't even know to do so -- usera/userb can do little to influence the message being accepted or rejected at ispb. Viz: 1. spfprotecteddomain MX -> ispa MX: mail from: user(a)spfprotecteddomain rcpt to: usera(a)ispa Result: message accepted (passes SPF check if one is done) 2. ispa configuration for usera says "forward to userb(a)ispb" 3. ispa MX -> ispb MX: mail from: user(a)spfprotecteddomain rcpt to: userb(a)ispb Result: SPF check fails because ispa MX is not in the SPF from list, and message is rejected (and bounced by ispa MX back to user(a)spfprotecteddomain). SPF's answer to this is that mail servers should rewrite the from address -- complete with lots of magic about how it should be done (still being debated). Rewriting it to be "mail from: usera(a)isap" would work just about as well in practice in most situations (bounces go to the "wrong" place, but bounces are largely broken by all the abuse of them going on anyway). This is what procmail and some other things do. FWIW, this is not a theoritical situation. This is really happening right now. And I ended up relaxing some of my SPF statements as a "work around". As I said in the beginning I'd like to see more ISPs that offer "mail forwarding" services to their customers forward that mail in a way that won't cause SPF rejections further down the track. Like it or not SPF is being implemented, and trying to ignore it will not stop your customers mail being bounced. Ewen

3 2

NZNOG '05 Progress and Logo
by Jamie Curtis 01 Dec '04

01 Dec '04

Hi all, Preparation for the NZNOG conference is progressing well with the organising committee working hard on pinning down the final details of the programme. We are currently aiming to open registrations, along with a new look website, sometime next week. One critical component still missing is a logo for this years conference. If there are any of you who feel like getting creative, please feel free to submit logos to me via e-mail. If your logo is chosen as the best, you can expect much kudos at the bar, possibly along with a few free drinks ! As we need the page ready ASAP, logos will need to be submitted as soon as possible, but no later than first thing Monday. Last years logo can be found on the old site: http://www.nznog.org/2004/ Cheers Jamie ----------------------------------------------------------------------- Jamie Curtis office: G.1.01 WAND Group, Dept of Computer Science phone: +64 7 838 4136 University of Waikato, mobile: +64 21 392 102 Hamilton, fax: +64 7 858 5095 New Zealand email: jamie(a)wand.net.nz -----------------------------------------------------------------------

1 0

Rescue from alligators in the swamp - note from APNIC
by John Tran 30 Nov '04

30 Nov '04

Hello all, First, as a general note, it is worth mentioning that there are several staff at the APNIC Secretariat who keenly follow the discussions on NZNOG. Currently, we have been closely following the discussion on the effects of implementing the 'whois privacy' policy on address ranges in use in New Zealand. This email is intended to clarify some of the issues raised, to provide explanations, and to try to identify a path forward. As there have been quite a lot of issues raised, I apologise in advance for the length of this reply. 1) Creating and changing policies --------------------------------- It is not necessary to be a member of APNIC to be involved in the policy making process. Anyone can propose policy changes and take part in the policy discussions. Also, you dont have to attend the meetings to take part. APNIC provides facilities for people not present to take part in discussions while the meetings are actually taking place. In addition, everyone is welcome to join the APNIC mailing lists where policies are proposed and discussed. The main list used to discuss the management of Internet resources is the Policy Special Interest Group (SIG) mailing list. A description of the Policy SIG is available at: http://www.apnic.net/meetings/archive/sigs/policy.html Details of how to subscribe to this and other APNIC mailing lists is available at: http://www.apnic.net/community/lists/ It is highly recommended that anyone holding resources does subscribe to this list (and others) so that they can voice their opinions and give feedback when policies are circulated for comment. You can also find a list of active policies under discussion at: http://www.apnic.net/docs/policy/proposals/ Feedback and participation in developing policies from the NZ community is very much appreciated. 2) Membership fees and criteria for portable allocations and assignments ------------------------------------------------------------------------ The fees for membership can be found here: http://www.apnic.net/member/feesinfo.html The criteria for a minium allocation (/21*) of portable address space are as follows: - the applicant must have used a /23 from their upstream provider or demonstrate an immediate need for a /23; - the applicant must have complied with applicable policies in managing all address space previously allocated to it; - the applicant must demonstrate a detailed plan for use of a /22 within a year; and commit to renumber from previously deployed space into the new address space within one year. [* it is worth noting that the size of the minimum allocation and the criteria for obtaining an allocation were recently lowered from a /20 to a /21 as a result of input and consensus from the community] More information is here: http://www.apnic.net/docs/policy/add-manage-policy.html#9.3 If you wish to obtain a portable assignment of address space as a multihomed organisation you can apply under the small multi-homing assignment policy. The criteria are: - the requestor must be currently multihomed with provider-based addresses, or demonstrates a plan to multihome within one month; and - agree to renumber out of previously assigned address space. The small multi-homing assignments are available to both members and non-members. 3) National Internet Registries (NIRs) -------------------------------------- APNIC recognises NIRs which operate within certain economies. Prospective NIRs must meet specific criteria and adopt the operational policies detailed in: http://www.apnic.net/docs/policy/nir-criteria.html and http://www.apnic.net/docs/policy/operational-policies-nirs.html 4) Whois database privacy policy -------------------------------------- Details of and the motivations for this policy are documented at: http://www.apnic.net/docs/policy/proposals/prop-007-v001.html In summary, the policy means that all non-portable assignments and non-portable sub-allocations will be private by default. Details of these resources remain registered in the whois database but are just not visible to the public. They can be made visible by the custodian of the allocation object through MyAPNIC, to which all APNIC members have access. 5) Next steps ------------- Under the database privacy policy, all non-portable assignments and non-portable sub-allocations that have not been specifically marked as public have now been made private. However, because some allocations and assignments within certain ranges appear to have been considered 'portable' by default from earlier practices in New Zealand, APNIC will restore the affected ranges from private to public. The ranges in question are: - 202.27.0./16 - 202.36.0.0/16 - 202.37.0.0/16 - 202.49.0.0/16, and - 202.50.0.0/16 Anyone holding addresses from these ranges that they wish to be made private, should contact APNIC helpdesk. The update will be done this week. 6) NZTelecom custodianship -------------------------- In regard to the wider issue of NZTelecom as a custodian of the ranges listed above, APNIC operated in good faith, trying to promote aggregation and provide a clearer framework for the custodianship of address space in New Zealand. That said, clearly there are now major concerns being expressed on this mailing list concerning portability of blocks within these ranges. The APNIC Secretariat will examine the records within these ranges and will work with NZTelecom, affected parties, and the community to find an appropriate solution. The solution will not happen overnight but the process is beginning immediately. Of course, APNIC will keep the New Zealand community fully up to date on the progress of the discussions. The APNIC Secretariat would be happy to assist anyone with concerns. If you want to discuss your concerns with us, please call the helpdesk on +61-7-3858-3188 or send email to <helpdesk(a)apnic.net>. 7) The past and the future -------------------------- Clearly, much of this stems back to a time when the framework for allocating and assigning resources was much less defined than it is today. The RIRs, with the community, are trying to provide a responsible framework for managing resources, both historical and existing resources. Some of you may be aware of the ERX transfer project in which resources in use in this region were previously registered in the ARIN database and are now being transferred to the APNIC database and are now managed by APNIC. More information about this project is available at: http://www.apnic.net/db/erx/ Many other steps are being taken. One such example is the policy recently implemented to support transfers of historical address space: http://www.apnic.net/docs/policy/proposals/prop-006-v001.html Others recently approved by the community, but yet to be implemented are: * Recovery of unused address space: http://www.apnic.net/docs/policy/proposals/prop-017-v001.html * Protecting historical records in the whois database: http://www.apnic.net/docs/policy/proposals/prop-018-v001.html I would strongly urge anyone who is a custodian of Internet resources to read these policies and to contact APNIC if they have any queries. Finally it is worth mentioning that four APNIC staff members will be at the forthcoming NZNOG meeting, and will be happy to meet with people and to provide a forum for discussing these issues. Regards Son ____________________________________________________________________ Resources Services Manager <Son(a)apnic.net> Asia Pacific Network Information Centre phone: +61 7 3858 3100 http://www.apnic.net fax: +61 7 3858 3199 Helpdesk phone: +61 7 3858 3188 email: helpdesk(a)apnic.net Please send Internet Resource Requests to <hostmaster(a)apnic.net> _____________________________________________________________________

3 3

Citynet, TelstraClear, Telecom, Orcon
by Joshua Brady 30 Nov '04

30 Nov '04

Could someone from Citynet, TelstraClear, Telecom, Orcon please contact me off-list please. Regards, Joshua Brady

1 0

IPv6 transit in .nz
by Lincoln Reid 30 Nov '04

30 Nov '04

Hi, Is anyone here able to offer international IPv6 transit in New Zealand currently? Ultimately I would like to start publishing AAAA records for some of our infrastructure, which means there is a little more pressure on to provide connectivity more compelling than through a tunnel broker eg. ~500ms, sometimes lossy, sometimes entirely broken. My experience as an end user through a tunnel broker accessing sites with AAAA records like www.apnic.net or www.isc.org is that the performance is often bad enough for me to kill my IPv6 connectivity to maintain sanity. Our requirements are very modest, even a shared 512 kbit is probably fine as long as it works most of the time. If anyone has any pointers get in touch. Cheers, -- Lincoln Reid Systems Engineer LinuxNet - AS18119 lincoln(a)linuxnet.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

1 0

Outage Notifications in a standardised format
by Jamie Baddeley 30 Nov '04

30 Nov '04

Hi people, I'm looking the various ways and means I get notified of early warnings/network outages, and I'm thinking that there's got to be a better way. This better way would probably involve an agreed information format (e.g XML, RSS etc) between all parties. Even just a standard email template. I'd be keen to herd a working group to come up with a standard mechanism for telling each other that the smoke has leaked out (or is about to), and that the rubber band fell off. Add some funkiness, and letting customers know would be so much easier. As usual, however, the usefulness of this is proportional to the number of network operators who agree to the standard...This is an open request to TelstraClear and Telecom - are you interested in working together on this? Can I have a show of hands from those in the NOG who'd be keen to work together to draft a standardised way of Outage Reporting. If we can get enough people together, and do some planning between now and February, then doing a BOF at the conference in February would be the way to go. And by all means, if such a standard already exists, then please point me in the direction of it.. Hands up? jamie --

1 0

Request for historical info
by Barry Murphy 30 Nov '04

30 Nov '04

Hi, I'm trying to gather some data of prices of the internet for the last 10+ years. What I'm looking for is the following for every year you can remember: Year: Monthly hours: ISP price: Product: ADSL/Dial-up Telecom rental price: Any further historical info would be great too, i.e. when the internet was first introduced as a commercial product in NZ, etc. Please reply off list, I'll be publishing the info and advising at a later stage. Thanks Barry

1 1

RE: [nznog] What characterises an NGN?
by Donald Neal 29 Nov '04

29 Nov '04

> -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Monday, 29 November 2004 12:43 p.m. > To: NZ NOG > Subject: [nznog] What characterises an NGN? > > Wrote a bit about Telecom's NGN variant here: > > http://computerworld.co.nz/news.nsf/UNID/C740B2DD592E9EDDCC256 > F58000FBD33 > > I'm curious as to what the NOG thinks of this approach. If I look at: > > http://www.iec.org/online/tutorials/next_gen/ > > an NGN is defined as: > > "The next-generation network seamlessly blends the public switched > telephone network (PSTN) and the public switched data network (PSDN), > creating a single multiservice network. [...]" > > Is it fair to assume that pushing CO functionality to the > network edge > requires an end-to-end managed solution? There seem to be three different questions here. The first concerns what an NGN is. Once upon a time telcos ran phone networks. When they added data services, like X.25, they built separate networks to provide those services. An NGN is about putting together the necessary bits to build a network which carries voice and data over one network instead of several. The pieces tend to include an MPLS core, aggregation devices, and so on. It's tempting to say that they're standard hardware rather than the high-cost proprietary stuff telcos used in the past. But in real life there aren't many really big Junipers outside the carrier space. Anyway, the key point about it is that a telco only has one of it, which provides a range of services. There will be cases where limitations to equipment may dictate how a service can be provided, and others where the telco has some choices. "What the NOG thinks of this approach" may well be influenced by what it is an approach to. It's not clear to me, looking at the article, wha the service is that's being decribed. If the service in question is multipoint VPN's, then it seems to me to make perfect sense that customer routing information has to be shared with the carrier. Otherwise how would the carrier's provider edge routers work out where to send the customer's packets? If the service is point to point tunnelling, that's a different matter. As to whether pushing CO functionality to the network edge requires an end-to-end managed solution, I suspect the real-life answer to be "yes". But with a couple of provisos. The first is that 'end-to-end' for a carrier may not be the same as 'end-to-end' for the customers of the carrier, or for the customers of the customers of a carrier. If a telco is going to sell multiple services over a single piece of wire carrying IP packets, it does make sense for the telco to apply whatever shaping, policing etc, policies it's going to use at the customer premises. I don't immediately see how that could be done without putting a telco-administered box at the customer's premises. But if "A customer can choose to tag their own traffic to the correct QoS value, or Telecom can do this for them in the endpoints", then presumably a customer can mark their own traffic and then have Telecom's box on their premises act simply as Telecom's check that their marking matches whatever the service is supposed to be. The second proviso is really the previous question again. It's quite possible to run lower-quality services over the same, or most of the same infrastructure. I'd be very surprised to see all customers getting the same level of management regardless of what they're paying. All opinions mine only. All comments relate to telco networks in general except where I quote the original article. - Donald Neal Donald Neal |Hydrangea - warning by the Lone Technical Specialist | Ranger's colleague NGN Operations | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 29 Nov '04

29 Nov '04

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next annual conference is to be hosted by the WAND group in Hamilton on February 2nd to 4th, 2005. That's just over three months away. See http://www.nznog.org/ for more information, including a list of confirmed presenters which keeps growing. We've also confirmed that APNIC are to offer a day of "Internet Resource Management Essentials" training on Wednesday, 2nd February. Look for registration to open next week. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net.nz/ for details of the Auckland, Palmerston North and Wellington exchanges, and some information on others under construction. About This Mailing List This list has around 750 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

Windows 2000/2003 Strangeness
by Geraint Jones 29 Nov '04

29 Nov '04

Go gently on me this is probably considered off topic but I can think of nowhere else to post this hardware background : I have 2 windows boxes and a Linux box connected to my internal LAN and to the internet, all 3 have 2 nic's problem : the windows boxes disappear from the internet intermittently for 2 mins or so every now and then and suddenly come back, there is nothing in the event logs' the boxes just disappear for a bit. however the Linux box stays visible all the time. all 3 machines are connected via the same router. I can see nothing wrong with any of the servers and this is making me pull my hair out, any thoughts welcome Cheers Geraint

2 1

Prefix update for Maxnet
by Alastair Johnson 29 Nov '04

29 Nov '04

Hello, Please add 203.89.160.0/19 to your prefix-list for maxnet. APE: 192.203.154.86 WIX: 202.7.0.116 ASN: 9889 thanks! aj -- Network Operations || noc. +64.9.915.1825 Maxnet || cell. +64.21.639.706

1 0

RE: [nznog] Hector Protector
by Donald Neal 29 Nov '04

29 Nov '04

> Simon Lyall wrote: > > Why not just press "Windows logo key"-L ? > > > > http://support.microsoft.com/?kbid=294317 > > It doesn't bring up a cute Disney/Neverland style > anthropomorphic animal > and only works with Windows XP (and keyboards with a Windows > key, which > admittedly most have nowadays). > > Also, you can't launch it with a biggus marketing campaign either... This thread seems to have exhausted its relevant content. - Donald Neal Donald Neal |Hydrangea - warning by the Lone Technical Specialist | Ranger's colleague NGN Operations | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

Hector Protector
by Peter Macaulay 29 Nov '04

29 Nov '04

Off topic, but be charitable. Netsafe have launched their cybersafety ambassador http://www.netsafe.org.nz/hector_protector/hector_protector_default.aspx Please give it a work out. It is pretty important that they have this right, the last thing we want it to have a kid's safety tool able to be hi-jacked. I am happy to pass on comments. -- Peter Macaulay Executive Director InternetNZ Direct +64 4 495 2113 Skype petermacaulay Mobile +64 21 488 485 -- Peter Macaulay Executive Director InternetNZ Direct +64 4 495 2113 Skype petermacaulay Mobile +64 21 488 485

7 8

The Lycos "anti spam screen saver"
by Juha Saarinen 29 Nov '04

29 Nov '04

http://www.theregister.co.uk/2004/11/26/lycos_europe_spam_blitz/ http://news.bbc.co.uk/2/hi/technology/4051553.stm Tempting as it may be to fight abuse with abuse... it doesn't seem right. -- Juha

3 2

What characterises an NGN?
by Juha Saarinen 28 Nov '04

28 Nov '04

Wrote a bit about Telecom's NGN variant here: http://computerworld.co.nz/news.nsf/UNID/C740B2DD592E9EDDCC256F58000FBD33 I'm curious as to what the NOG thinks of this approach. If I look at: http://www.iec.org/online/tutorials/next_gen/ an NGN is defined as: "The next-generation network seamlessly blends the public switched telephone network (PSTN) and the public switched data network (PSDN), creating a single multiservice network. Rather than large, centralized, proprietary switch infrastructures, this next-generation architecture pushes central-office (CO) functionality to the edge of the network. The result is a distributed network infrastructure that leverages new, open technologies to reduce the cost of market entry dramatically, increase flexibility, and accommodate both circuit-switched voice and packet-switched data." Is it fair to assume that pushing CO functionality to the network edge requires an end-to-end managed solution? -- Juha

4 4

Re: Fw: [nznog] Rescue from alligators in the swamp
by Ewen McNeill 28 Nov '04

28 Nov '04

In message <Pine.LNX.4.56.0411281830110.22205(a)green.darkmere.gen.nz>, Simon Lyall writes: >Currently I can get a domain for less than $US 20 per year and that will >get injected in the "DNS routing table" of every provider in the world. >I fail to see why a block of IP addresses should cost more. (a) scarcity: the number of possible IP addresses (4 billion) is rather less than the number of possible domain names (37 ** 63 per name segment) (b) impact on other people's systems: a DNS delegation just sits quitely on a couple of DNS servers in a corner, minding its own business, until someone happens to ask about it; a prefix advertised into the global routing table ends up occupying space in every router in the world with a "full table" and being shuttled around between them fairly often. More DNS delegations means bigger hardware at Verisign (or whoever); more prefixes (eventually) means bigger hardware for all routers that make up the Internet. 2 ** 24 (all possible /24s advertised) is a big number, even at only 64 bytes per routing entry (2 ** 30 bytes of memory). (c) volume: a block of IP addresses consists of multiple addresses; at the US$1250/year mark, that's over 1000 usable addresses. If you were to get 1000 $20 domain names, it'd cost more than US$1250/year :-) (d) scale: the many millions of .com domain names pay for the registry; the few thousand APNIC members need to pay for APNIC to run With all that said, I do sympathise with those with smaller-than-/22 requirements for whom portability and/or the ability to multihome would be useful. And if there's some appropriate way that smaller applications can be fitted within APNIC's requirements it'd be worth considering. However my recollection of what the University of Waikato was doing was that it was largely making allocations along the lines of the proposed "national internet registry" -- at least from the point of view of those receiving the allocations -- and 10 years later, it didn't turn out quite as smoothly as one might have hoped. So if it is done some thought will need to be given as to how one will ensure the "portable" assignments will remain "portable" for an extended period of time. Ewen

3 4

Rescue from alligators in the swamp
by FX Networks 28 Nov '04

28 Nov '04

Given today's discussion about address space etc, FX Networks is prepared to allocate equivalent address space to any ISP that is affected by this policy. reply to this address offlist if you wish to stop using old swamp space.

12 16

Fw: [nznog] Rescue from alligators in the swamp
by Keith Davidson 28 Nov '04

28 Nov '04

I agree in principle with Joe, APNIC are pretty easy to deal with, and for any reasonable robuts requirer of numbers, the costs are hardly prohibitive at US$2,000 one-off, plus US$1,250 per annum. But I guess the argument is that some people have a class C or 2 that they pay nothing for currently and would like to continue to pay nothing. As I said in my previous email, InternetNZ would be happy to step up to the plate if there really is a need - but I doubt we'd be in the business of supplying free number blocks. Keith Davidson Joe Abley stated: > As far as I can see, it's APNIC's job, and they're doing it pretty well > already. > > There seem to be a lot of people assuming that APNIC are hard to deal with > (or that the policies are unreasonable) without ever having tried to deal > with them, or to find out what the policies actually are. > > The economics are pretty simple for ISPs and largish multi-homed > companies: you can pay the cost of renumbering every time you change > provider, or you can pay the membership fees at APNIC and obtain > provider-independent resources. Choose the option that suits your budget. > > Regardless of how much someone might think that every two-person company > deserves provider-independent address space, the unfortunate reality is > that this doesn't scale (and the problem is the routing system, not > address space scarcity). > > > Joe

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 27 Nov '04

27 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: Notification of NZRR Database changes (fwd) - Date: Mon, 29 Nov 2004 09:57:27 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411290955550.12055(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: route-set: AS9560:RS-ROUTES:AS5767 descr: Route set advertised to AS9560 by Xxx Ltd - AS5767 members: 222.43.45.0/22^22-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)lpnz.org mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041129 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Nov '04

27 Nov '04

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:AS5767 descr: Route set advertised to AS9560 by Xxx Ltd - AS5767 members: 222.43.45.0/22^22-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)lpnz.org mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041129 source: NZRR

1 0

Re: SPF and mail forwarding (was Re: [nznog] Sendmail Question)
by Ewen McNeill 27 Nov '04

27 Nov '04

In message <8AC558B6BC09CD42BCAF3C667E2A88CC0FC838(a)red.IFM.local>, Philip D'Ath writes: >Ewen McNeill writes: >>It would be very helpful if operators that provide a mail forwarding >>service (eg, just about every ISP that provides mail services) were to >>do the forwarding in a SPF-compatible manner. > >Wouldn't it be easier to just get those people using SPF that forward >through an ISP to include their ISPs server in the permitted list (which >is what we do)? Alas, this doesn't solve the problem except if you do what I resorted to doing -- for now anyway -- and say "the mail could come from any mail server I guess" ("?all" at the end of the SPF record). Why? To take an actual recent example, I host the Wellylug mailing list and website. The Wellylug website has a feature whereby users can subscribe to "meeting reminders", sent out by email shortly before the monthly meetings. usera(a)ispa was one address so subscribed. Unfortunately usera(a)ispa actually forwards mail to userb(a)ispb, without rewriting the envelope from address -- unknown to anyone else until the mail bounced because the SPF check failed (due to the message now coming from a mail server which wasn't in the SPF list for the domain in the envelope from). Given N subscribers to such a list, at M ISPs, the list of "mail servers the mail might come from" soon grows without bound, especially if one considers that the mail may be forwarded more than once (and yes, I encounter multiple forwards fairly often). As I said, this "what happens to forwarded mail" issue is the single biggest (and most contraversal) problem with SPF. And given that more sites are doing SPF checks it would be very helpful if more ISPs that provide mail forwarding services to their customers did so in a SPF-compatible way. Ewen PS: You might argue that users subscribing to such services should subscribe their final destination address, rather than one that forwards on to another account. However even ignoring the reasons why one might wish to subscribe an address the forwards somewhere else, the chances of all users acquiring such clue to do so seems... low.

2 1

SPF and mail forwarding (was Re: [nznog] Sendmail Question)
by Ewen McNeill 27 Nov '04

27 Nov '04

In message <001801c4d402$0e7ad2d0$0100000a(a)lennons>, "Lennon - Orcon" writes: >We have SPF and SRS implemented on our email servers and yes it does work. Unfortunately there are also a considerable number of systems (including in New Zealand) which forward mail without rewriting the envelope from address, which is required by SPF. This means that when the mail is forwarded it suddenly appears to be coming from a mail server that isn't authorised to send messages for that domain, which results in it being rejected and bounced back to the originator. I've had to relax the SPF statements for some of the domains that I manage in order to compensate for this problem (changing from "-all" to "?all" -- ie, "won't come from anywhere else" to "umm, I guess you might see it from some others too"). It would be very helpful if operators that provide a mail forwarding service (eg, just about every ISP that provides mail services) were to do the forwarding in a SPF-compatible manner. Something like procmail's approach (forward message on with envelope from of the account triggering the forward) is sufficient -- you don't have to do SPF's convoluted envelope from rewriting if you don't want to. I suspect this issue (mail forwarding) will continue to be the biggest obstacle to widespread SPF adoption for quite some time. Ewen

3 2

RE: SPF and mail forwarding (was Re: [nznog] Sendmail Question)
by Philip D'Ath 26 Nov '04

26 Nov '04

Wouldn't it be easier to just get those people using SPF that forward through an ISP to include their ISPs server in the permitted list (which is what we do)? In which case, it is more an issue of educating people who use SPF to include all servers, rather than getting every provider to change their email system. -----Original Message----- ... Unfortunately there are also a considerable number of systems (including in New Zealand) which forward mail without rewriting the envelope from address, which is required by SPF. This means that when the mail is forwarded it suddenly appears to be coming from a mail server that isn't authorised to send messages for that domain, which results in it being rejected and bounced back to the originator. I've had to relax the SPF statements for some of the domains that I manage in order to compensate for this problem (changing from "-all" to "?all" -- ie, "won't come from anywhere else" to "umm, I guess you might see it from some others too"). It would be very helpful if operators that provide a mail forwarding service (eg, just about every ISP that provides mail services) were to do the forwarding in a SPF-compatible manner. Something like procmail's approach (forward message on with envelope from of the account triggering the forward) is sufficient -- you don't have to do SPF's convoluted envelope from rewriting if you don't want to. ...

1 0

Sendmail Question
by Dan Clark 26 Nov '04

26 Nov '04

Hi Guys, Just wondering if anyone has seen the ability to configure sendmail to match from address to the msg id field (after the @) or weather or not it should do this by default. eg: Nov 26 10:55:24 mail sm-mta[15318]: iAPLtBa7015318: from=<forest.stein_rk(a)fyna.com.au>, size=982, class=0, nrcpts=1, msgid=<53fc01c4d339$34ac1af3$45006654(a)africon.co.za>, proto=SMTP, daemon=MTA, relay=[65.126.46.48] I would imagine a hell of alot of SPAM would be returned if our mail server was matching @fyna.com.au with the @africon.co.za and finding that they dont match? I hope I'm on the right track here. Regards Dan Clark

4 3

RE: [nznog] [Inetnum object]
by Donald Neal 25 Nov '04

25 Nov '04

> David Robb wrote: > > >I just got this from APNIC. Anyone else get one? > > > >My initial reaction is "say WHAT!?" > > > >Are Telecom trying to assert authority over IP space which > I'd like to see > >a whole lot of justification as to why it's "theirs". > > One simple answer is that it long has been, and before that was held by The University of Waikato. That Telecom hold a lot of New Zealand's address space isn't a new issue. (See, for instance, the archive for this list for June 1998.) - Donald Neal Donald Neal |Presbyopia - inability to see what Technical Specialist | bishops are for. Operations Engineering | 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." ------------------------------------------------------------------------------

9 8

[Inetnum object]
by David Robb 25 Nov '04

25 Nov '04

I just got this from APNIC. Anyone else get one? My initial reaction is "say WHAT!?" Are Telecom trying to assert authority over IP space which I'd like to see a whole lot of justification as to why it's "theirs". ---------- Forwarded message ---------- Hello, It has been brought to our attention that your organisation's maintainer is currently protecting the following resources: inetnum: 202.49.252.0 - 202.49.255.255 <stuff skipped> However NZTelecom has full authority over the following blocks: 202.27.0.0/16 202.36.0.0/16 202.37.0.0/16 202.49.0.0/16 202.50.0.0/16 Therefore as these assignments are from NZTelcom's blocks in one week's time the maintainer protecting these assignments will be changed to the maintainer of NZTelecom. Please approach NZTelecom for further updates required for these assignments. If you have any question regarding this matter please do not hesistate to contact the APNIC helpdesk at: <helpdesk(a)apnic.net> To discuss this matter further in person a staff member of APNIC will be attending NZNOG5 in Hamilton 2 - 4 February 2005. Regards, APNIC Secretariat

4 3

RE: [nznog] Sendmail Question
by Regan Murphy 25 Nov '04

25 Nov '04

You would probably lose a lot of mail that way. E.g. From: NZRR Database Notifications <rpsl-admin(a)nzix.net> Precedence: bulk Message-Id: <E1CXQJJ-0007Ps-00(a)zoff.wix.net.nz> From: Sun Microsystems <sun-events(a)see.sun.com> Message-id: <0I7P002S8ZMRCO(a)olm-ms2.sun.com> Message-ID: <880B6B3B42770C4E92F35D85732893A0EB910C(a)aklemail01.salesforce.co.nz> From: Fly Buys Service Centre <contactus(a)mailus.co.nz> A lot of mailservers are on subdomains masquerading as the root domain. Also some organisations send mail for different domains (legit ones) from the same mailserver. -- Regan -----Original Message----- From: Dan Clark [mailto:dan(a)scarfies.net] Sent: Friday, 26 November 2004 11:17 a.m. To: 'nznog' Subject: [nznog] Sendmail Question Hi Guys, Just wondering if anyone has seen the ability to configure sendmail to match from address to the msg id field (after the @) or weather or not it should do this by default. eg: Nov 26 10:55:24 mail sm-mta[15318]: iAPLtBa7015318: from=<forest.stein_rk(a)fyna.com.au>, size=982, class=0, nrcpts=1, msgid=<53fc01c4d339$34ac1af3$45006654(a)africon.co.za>, proto=SMTP, daemon=MTA, relay=[65.126.46.48] I would imagine a hell of alot of SPAM would be returned if our mail server was matching @fyna.com.au with the @africon.co.za and finding that they dont match? I hope I'm on the right track here. Regards Dan Clark _______________________________________________ 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 25 Nov '04

25 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 26 Nov 2004 10:24:47 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411261013430.9968(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: initially peering at '192.203.154.17' descr: see Citylink RT job #1552 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR REPLACED BY: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: PNIX peering at '218.100.21.10' descr: see Citylink RT job #1487 descr: APE peering at '192.203.154.17' descr: see Citylink RT job #1552 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17705 import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR

1 0

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

24 Nov '04

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: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: initially peering at '218.100.21.10' descr: see Citylink RT job #1487 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR REPLACED BY: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: initially peering at '192.203.154.17' descr: see Citylink RT job #1552 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR --- PREVIOUS OBJECT: route: 203.114.128.0/19 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR REPLACED BY: route: 203.114.128.0/19 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR --- PREVIOUS OBJECT: route: 203.96.157.0/24 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR REPLACED BY: route: 203.96.157.0/24 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR --- PREVIOUS OBJECT: route: 203.79.88.0/23 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR REPLACED BY: route: 203.79.88.0/23 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS17705 descr: Route set advertised to AS9560 by Inspire Net - AS17705 members: 203.114.128.0/19^19-24, 203.96.157.0/24, 203.79.88.0/23^23-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR

1 0

Re: [nznog] to xtra.co.nz sysadmins
by admin 24 Nov '04

24 Nov '04

thanks to everyone who replied. I was told by my ISP to change the ppp MTU from the default of 1514 to 250 a week ago because I was having problems connecting to another machine so I changed it to 512 just now and that enables me to view those sites again and access the other machine. regards to all tom PS I wasn't pointing the finger, I assumed knossos was correct but you're right about not troubleshooting properly, I only looked up the ns for yellowpages, not telecom. my bad :((

5 5

Re: [nznog] to xtra.co.nz sysadmins
by Ewen McNeill 24 Nov '04

24 Nov '04

In message <5FC2EE64-3EA0-11D9-A37D-000D93B24C7A(a)isc.org>, Joe Abley writes: >On 24 Nov 2004, at 22:11, admin wrote: >> no, orcon told me to use 250 and it seems 1514 is the default in linux. > >The MTU usually depends on the frame size that can be accommodated by >an interface. There is no useful "default" MTU. I seem to remember >hearing from someone that Linux includes the encapsulating frame >headers in its calculations when it interprets an MTU, which would make >1514 make sense for Ethernet. Kind of. That's the first I've heard of that. All the Linux boxes that I administer have a MTU of 1500 (by default, anyway) on their Ethernet interfaces.[0] To the best of my knowledge the MTU figure given to Linux network tools is the same as the MTU figure given to any other OS (ie excluding link layer framing overhead). Some googling turns up several references to "mtu 1514", from various equipment (eg, Cisco loopbacks with a MTU of 1514's, tunnels on various things, PPP interfaces, etc), but it's not clear what made someone consider it a "default".[1][2] There are also various reports of 1514 octet MTUs on ADSL connections (presumably on the interface facing the DSLAM), with various suggestions to change them to other things, including some elaborate "optimisations" based PPPoA or PPPoE overhead and ATM cell tax. 14 octets extra doesn't seem to match PPPoE or PPPoA overhead though. >However, in general, if you reduce your MTU below 1500 bytes you can >expect all the inexpertly-firewalled, pMTUd-enabled servers of the >world to stop sending you packets, sooner or later. Ah, the joys of "I don't know what ICMP is, it sounds dangerous, we'd better block it" firewall administration. Ewen [0] The default MTU on some of the other interface types is different, but a lot of them seem to default to 1500 for Ethernet compatiblity. [1] There are a bunch of people "learnedly" pronoucing that the maximum Ethernet MTU is 1514 but they appear to be deluded; about the only thing which makes some sense is that capturing packets off an Ethernet network with link headers will give you 1514 octet frames (since you don't capture the CRC at the end of the frame), which seems to confuse some people. [2] PPP on a Linux system I tried defaults to 1500 octets, presumably to deal with packets-of-ethernet without fragmentation; but it appears there may be some Linux distributions which ship with PPP defaulting MTU to something else.

2 1

Unable to reach anything but orcon servers on bitstream
by Jonathan Brewer 24 Nov '04

24 Nov '04

Hi Folks, Following email came to the WellyLUG list and I though the situation might be of interest to the NOG community. Given that Telecom is *the* provider of DSL, and bitstream is *the* unbundled option, issues in switching over customers should be paid close attention to! The customer affected now believes the issue to be related to a profile not being set to the right authentication server. Is anyone else out there successfully using unbundled DSL? How can we find out how many Bitstream customers there are? Cheers, Jon -----Original Message----- From: wellylug-admin(a)lists.wellylug.org.nz [mailto:wellylug-admin(a)lists.wellylug.org.nz] On Behalf Of Simon . Sent: Thursday, 25 November 2004 9:35 a.m. To: wellylug(a)lists.wellylug.org.nz Subject: [wellylug] (OT) Unable to reach anything but orcon servers on bitstream My apologies for the non-linux nature of this post. I think I'm hooked up with Bitstream at home now... I'm not 100% sure, and if you've been waiting for over a month like I have, you'd be sceptical too. My internet connection was severed at about 15:30 on Tuesday, and my ADSL router would only synchronise, but was unable to send ATM packets. This changed when I came home last night, and now I'm able to send ATM packets, yet I'm not able to access anything but orcon servers. Below is an email I've sent to orcon, but their helpdesk is insanely understaffed at the moment. The email has been edited to protect the innocent. If anyone can let me know what the problem might be? I have a feeling my account isnt set up properly on the gateway server, and wont let me access anything further. If I try a traceroute to google, it gets as far as the gateway, and then no further. Cheers, Simon Antliff ---------- Forwarded message ---------- Date: Wed, 24 Nov 2004 18:58:31 +1300 (NZDT) From: Simon Antliff <REMOVED> To: support(a)orcon.net.nz Subject: Unable to reach anything other than DNS/mail server Hello, I rang the Helpdesk yesterday, and left a message regarding my ADSL connection not being able to send anything over ATM. I havent heard back about this. Well, this afternoon I find that I am now able to properly connect my ADSL router to the ISP and my routers diagnostic tests all come back as a pass. I assume that I have been moved to Bitstream, since I now connect at a lower rate than before (320 now, versus 2000 yesterday). However, I cannot access anything outside of Orcon, such as google.com. Pinging google reveals that it is unreachable. So is anything else, other than 219.88.240-246.XXX and I can also ping 210.55.12.1 and 210.55.12.2 which I'm using as DNS servers. The gateway that I'm using (was assigned by DHCP) is 219.88.242.171 I am able to use email, since smtp.orcon.net.nz is 219.88.242.10. If I try to ping www.orcon.net.nz I get the following: >From www.orcon.net.nz (219.88.241.90) icmp_seq=1 Dest Unreachable, Bad Code: 10 Here is a tcptraceroute log for www.orcon.net.nz: Tracing the path to www.orcon.net.nz (219.88.241.90) on TCP port 80, 30 hops max 1 192.168.0.1 (192.168.0.1) 72.818 ms 71.805 ms 71.999 ms 2 219.88.242.171 (219.88.242.171) 72.126 ms 71.482 ms 72.079 ms 3 fe-colocation-core.nct.orcon.net.nz (219.88.242.244) 71.774 ms 71.445 ms 69.920 ms 4 www.orcon.net.nz (219.88.241.90) [open] 73.935 ms 73.450 ms 75.942 ms Please let me know if you need any more information. --- contact info snipped --- Cheers, Simon. ---- End of message --- _________________________________________________________________ Need more speed? Get Xtra JetStream @ http://xtra.co.nz/jetstream -- Wellington Linux Users Group Mailing List: wellylug(a)lists.wellylug.org.nz To Leave: http://lists.wellylug.org.nz/mailman/listinfo/wellylug

2 1

to xtra.co.nz sysadmins
by admin 24 Nov '04

24 Nov '04

Hi, Posting here because xtra staff say they have no systems admins :)) I can't access these sites or send mail to telecom.co.nz, whitepages.co.nz or yellowpages.co.nz. all 3 names have similar problems http://www.knossos.net.nz/checkdomain.cgi?domain=telecom.co.nz&submit=Query telecom.co.nz Name servers The following name servers for telecom.co.nz were found in the delegation from co.nz: * ish4.telecom.co.nz, IP address 146.171.13.195 * ish5.telecom.co.nz, invalid host name Authority (SOA) data * Primary name server: ish4.telecom.co.nz, IP address 146.171.13.195 * Contact email address: root(a)ish4.telecom.co.nz * Serial number: 2004112402 (24 Nov 2004) * Secondaries query every 3 hours; retry every 1 hour; expire after 7 days. * Time to live for negative responses: 30 minutes * Time to live of SOA record: 30 minutes Other services No services appear to be assigned to this domain. Additional information indicates an error that can potentially cause access to services to fail. indicates an error that while technically violating standards is unlikely to cause actual problems. No address record for the nameserver ish5.telecom.co.nz could be found. This could be due to the nameserver being removed from service, or bad configuration on another server. If nameserver has been removed from service, it should also be removed from the list of authoritative name servers at the registry for co.nz. The name server ish4.telecom.co.nz is an alias (or CNAME) for smtp1.telecom.co.nz. Name server names are not permitted to be aliases for other names. Remove the CNAME record and replace it with an A (address) record pointing to the IP address of the name server. Alternatively, amend the list of NS records to include smtp1.telecom.co.nz instead of ish4.telecom.co.nz. If the latter course of action is taken, don't forget to update the registry database for co.nz to reflect the change. The list of name servers returned by the nameserver ish4.telecom.co.nz at IP address 146.171.13.195 does not match those listed in the delegation for the domain in the registry for co.nz. (This list is displayed under the ``Name servers'' section above.) Please check the registry data and ensure that it matches the data in the local name servers. The list obtained from ish4.telecom.co.nz is as follows: The name server ish5.telecom.co.nz at IP address did not return SOA data. Please check that this is the correct IP address for the server, and if not, check that the registry for co.nz has the correct data. Only one functioning name server was found. Having only one name server means that any failure of that server will cause names within the domain to become unresolvable. Furthermore, most registries require that a domain have two or more actual functioning name servers. A reverse map (PTR) record for one of the IP addresses referred to could not be found. A PTR record along the lines of the following should be included in the appropriate reverse map domains: 195.13.171.146.in-addr.arpa. IN PTR ish4.telecom.co.nz. DNS delegation checking script copyright © Don Stokes 1999-2004. No liability will be accepted for the accuracy or (mis)use of information presented by this facility. Please read the FAQ for more information.

2 1

FW: [sig-policy] APNIC EC endorses policy decisions from APNIC18
by Nurani Nimpuno 22 Nov '04

22 Nov '04

Hi, I thought I'd forward this, as some of the policies below may be relevant to the NZ community. Kind regards, Nurani Nimpuno ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Nurani Nimpuno <nurani(a)apnic.net> Asia Pacific Network Information Centre (APNIC) http://www.apnic.net PO Box 2131 Milton Tel: +61-7-3858-3100 Brisbane, QLD 4064, Australia Fax: +61-7-3858-3199 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----Original Message----- From: sig-policy-bounces(a)lists.apnic.net [mailto:sig-policy-bounces(a)lists.apnic.net] On Behalf Of APNIC Secretariat Sent: 22 November 2004 16:49 To: apnic-announce(a)lists.apnic.net; sig-nir(a)lists.apnic.net; sig-policy(a)lists.apnic.net Subject: [sig-policy] APNIC EC endorses policy decisions from APNIC18 [Apologies for duplicates] Dear Colleagues, The consensus policy decisions from the 18th APNIC Open Policy Meeting were endorsed by the Executive Council (EC) on November 19th at their regular monthly teleconference. The proposals endorsed by the EC are listed below: [prop-005-v004] - Internet Assigned Numbers Authority (IANA) policy for allocation of IPv6 blocks to Regional Internet Registries [prop-021-v001] - Expansion of the initial allocation space for existing IPv6 address space holders [prop-022-v001] - A proposal to abolish redundant charges in IPv6 allocations [prop-025-v001] - Proposal for an IPv6 IRR service at APNIC Details of each policy proposal, presentations, and minutes of the SIG and Member Meeting discussions are available on the policy proposal index page at: http://www.apnic.net/docs/policy/proposals This is the final stage in the policy development process before implementation. These policies were created in accordance with the policy development process for the Asia Pacific region. More details on this process can be found at the URL below: http://www.apnic.net/docs/policy/dev/ Regards ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 --------------------------------------------------------------------- * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list sig-policy(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy

1 0

OT - Unix Support Team Leader Position
by Edward Yardley 21 Nov '04

21 Nov '04

Hi All, If anyone is interested in a Unix Support Team Leader Position in Wellington ($ open). Please give me a call on one of the numbers below. Must have experience managing a team and have been a Unix admin/engineer. (04) 499-1276 or 021-509-890 Cheers Edward. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

Palmerston North Internet Exchange
by Andy Linton 18 Nov '04

18 Nov '04

Hopefully we got the sniggering about the PNIX out of the way the other day so I'm pleased to announce the opening of a new Internet exchange in Palmerston North. For more details see http://pnix.nzix.net/ We're also working on other exchanges in other centres and are happy to work with anyone wishing to establish open neutral peering points. As always we encourage widespread peering as a strategy to increase robustness and performance.

1 0

Orcon Internet Prefix List Updaet (2004-11-18)
by Craig Whitmore 18 Nov '04

18 Nov '04

Hi For all those peering with Orcon Internet (AS17746) nationally, please update your prefix lists with the following networks (also in attached file). Added: ip prefix-list orcon-national permit 203.86.192.0/20 Regards, Craig Whitmore Orcon Internet Network Operations

2 1

NZNOG 05 - Lightning Talks
by Simon Lyall 16 Nov '04

16 Nov '04

As part of the process of finalising the NZNOG 05 schedule it's been suggested that perhaps we have a session of lightning talks (it's been mentioned before but this is a semi-official call). Lightning talks are talks/presentations that last no more than 5 minutes. Several of them are usually run one after the other so that multiple speakers and topics can be covered in a short time. Here is a good page on the subject with links so where these have been held before and there are more links at the bottom of this email: http://www.justanotherperlhacker.org/lightning/ Possible topics might be (see also the pages linked in this email): - How to use RPSL with NZIX Route Registry. - Advice for finding IT jobs in NZ. - I'm involved in the X project, here is why it is cool. - I want to do cool project X. Does anyone want to help? - A quick way to clone Linux Servers - Interesting stats from the netflow across my APE link. - Building and maintaining a large and popular file archive while avoiding the lawyers. - Successful Project: I did project X. It was a success. Here's how you could benefit. - Failed Project: I did project X. It was a failure, and here's why. - Heresy: People always say X, but they're wrong. Here's why. - You All Suck: Here's what is wrong with the our community. - View from the Far Side, experiences as an IT journalist. - Call to Action: Let's all do more of X / less of X. - Wouldn't it be cool if X? - IF each ISP were an animal which animal would it be. - Someone needs to do X. - Maintaining router configs using awk - Wish List - How to get and keep portable IP addresses cheap. - Why X was a mistake. - Why X looks like a mistake, but isn't. - What it's like to do X. - Where I think the New Zealand Internet is going. - Here's a useful technique that worked. - Experiences with Juniper vs Cisco. - Here's a technique I thought would be useful but didn't work. - Why you shouldn't ever run qmail. What I would like to do at this point is gauge the interest people have in having and giving these talks at nznog05. Please email me if: - If you are interested in giving one (suggest possible topics). - You would like to suggest a topic that someone else could give a talk on ( Feel free to suggest the person) - You think it's a good/bad idea. - Any other questions or comments. I'll go over the emails (and subsequent followups) in the next few days and give a summary. If we get the numbers then I'll probably do one myself ( either on a topic I choose or something others suggest). Assuming we get at least half a dozen people prepared to give talks then I'll see if I can get us a place in the schedule. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full hour long talk. Some links. Advice on giving Lightning Talks: http://www.perl.com/pub/a/2004/07/30/lightningtalk.html A couple more links: http://www.metaart.org/maca/perl/lightning/lightning_what.html http://perl.plover.com/lt/lightning-talks.html http://www.metaart.org/maca/perl/lightning/lightning_what.html -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

NZNOG 2005 Progress Report - 16 November
by Donald Neal 15 Nov '04

15 Nov '04

NZNOG People, We've received a surprising number of late offers to present, some of which we're still working through. That has drawbacks for the organisers, but it's been good to have a high level of interest from presenters, from which a strong technical programme seems to be growing. We're adding the names of presenters as they're confirmed to the conference web site at http://www.nznog.org/ . Expect to see rapid change to that site over coming weeks. In particular, we expect to be opening registration early in December. So you'll have plenty of opportunity to talk to your manager _before Christmas_. - Donald Neal Donald Neal |Presbyopia - inability to see what Technical Specialist | bishops are for. Operations Engineering | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Nov '04

15 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 14:50:39 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161449550.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64558 descr: Route set for AS64558 members: 203.167.235.0/24, 218.101.2.0/23^23-24, 218.101.4.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: dion.hallam(a)xtreme.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031030 changed: rpsl-admin(a)nzix.net 20040217 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64558 descr: advertised to AS9439 by Xtreme Networks - AS64558 members: 218.101.8.0/24^24-29, 203.167.235.0/24^24-29, 218.101.2.0/23^23-29, 218.101.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: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 218.101.8.0/24 descr: Route for Xtreme Networks - AS64558 origin: AS64558 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 218.101.2.0/23 descr: Route for Xtreme Networks - AS64558 origin: AS64558 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 218.101.4.0/24 descr: Route for Xtreme Networks - AS64558 origin: AS64558 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Nov '04

15 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 13:43:36 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161337240.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: Route set advertised to AS9560 by ihug - AS7657 members: 203.109.128.0/17^17-24, 203.173.128.0/17^17-24, 203.118.128.0/18^18-24, 203.96.192.0/19^19-24, 210.55.248.0/21^21-24, 202.49.240.0/22^22-24, 202.50.188.0/22^22-24, 202.21.136.0/23^23-24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.49.46.0/23^23-24, 202.49.88.0/23^23-24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.180.0/23^23-24, 192.107.113.0/24, 202.21.130.0/24, 202.36.44.0/24, 202.49.33.0/24, 202.49.48.0/24, 202.49.63.0/24, 202.49.178.0/24, 202.49.186.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.255.0/24, 210.55.110.0/24, 210.55.184.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031210 changed: rpsl-admin(a)nzix.net 20040813 changed: rpsl-admin(a)nzix.net 20040920 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 192.107.113.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.44.0/24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.37.182.0/24, 202.49.33.0/24, 202.49.46.0/23^23-24, 202.49.63.0/24, 202.49.64.0/24, 202.49.140.0/24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.178.0/24, 202.49.180.0/23^23-24, 202.49.186.0/24, 202.49.249.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.188.0/22^22-24, 202.50.255.0/24, 203.96.192.0/19^19-24, 203.109.128.0/17^17-24, 203.118.128.0/18^18-24, 203.173.128.0/17^17-24, 210.55.110.0/24, 210.55.184.0/24, 210.55.202.0/23^23-24, 210.55.248.0/21^21-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 192.107.113.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.21.130.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.21.136.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.36.44.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.36.230.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.33.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.46.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.63.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.64.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.140.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.178.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.50.188.0/22 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 203.96.192.0/19 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 210.55.110.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR

1 0