- NZNOG - lists.nznog.org

Sysadmin Miniconf at NZNOG 08
by Simon Lyall 07 Aug '07

07 Aug '07

A reminder that we are looking for talks for the Sysadmin Miniconf at NZNOG 2008 in January ( see http://nznog.miniconf.org/ ) . Last year we had quite a good turnout and talks presented ( http://nznog.miniconf.org/2007.html ) We are really keen to get a good programme for 2008. As such we would be very interested in suggestions both from potential speakers and also from people who might want to hear about particular topics or technologies . On thing we are doing this year is encouraging people to give a talk about their site, what technologies, hardware, software, methods, policies they may use etc. The idea is to give others an idea about what other people use in the "real world" . It could be wide ranging or just about one thing like how you handle logs or documentation. We'd really like to encourage people to give these sort of talks. Anyway if you have an idea either for yourself or someone else (or suggestions on who we could approach) then please send an email to the team at talks08 @ nznog.miniconf.org Full details on the website: http://nznog.miniconf.org/ -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

A passing.
by Jamie Baddeley 06 Aug '07

06 Aug '07

http://www.stuff.co.nz/4156176a28.html A moments silence please. A True Electronic pioneer of New Zealand. Rest in peace Angus. jamie

1 0

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

06 Aug '07

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: AS24074 as-name: NZRR-AS24074 descr: NZ Post descr: WIX peering at '202.7.1.2' descr: see Citylink RT job #10237 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24074 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070807 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24074 descr: Route set advertised to AS9439 by NZ Post - AS24074 members: 202.12.248.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: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070807 source: NZRR

1 0

global-gateway.net.nz and possible MTU problems
by Scott Howard 03 Aug '07

03 Aug '07

We've got a client in Thailand who is having having trouble with traffic from a number of sites - all of which go through global-gateway.net.nz. Based on the symptoms I'm guessing it may be an MTU issue (along with the other end blocking ICMP) - anyone seen this with global-gateway.net.nz before? If anyone here is responsible for that network I'd appreciate it if you could contact me off-list. Thanks, Scott.

6 6

29 Peering Points
by Philip D'Ath 02 Aug '07

02 Aug '07

Just thinking about all these Telecom peering points. Assuming that Telecom allocate IP addresses as they are requested by incoming broadband connections, as opposed to by geographic peering point, then there will be no way to summarise addresses at these peering points. So this will imply that those ISP which do peer at these points will have to listen to a good 100k odd /32 announcements (at the larger peering points). I could easily see the routing table having to contain 200k to 300k additional /32 routes if you want to allow least cost routing to work its best. If there are redundant paths then this could increase a lot more. Then consider the case when a /32 appears to be from Dunedin, and then the next second it appears to be from Wellington (because the Dunedin broadband user lost their session, and a new Wellington use just acquired their dynamic IP address). Then consider all the places these routes could be redistributed to within different ISPs, and potentially outside of their own AS. Then consider [non telecom] peering points that only accept a /24 or bigger. Not that anything is wrong with asymmetric routing, but doing it almost to the customer edge is going to make solving connectivity issues much more difficult (I can access this web site, but not that web site ...). I can see a lot of potential for route flapping, and for frequent routing updates to occur. I can also see the potential for short term route loops occurring. I see route stability issues arising in NZ's future, or have I missed something?

11 14

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '07

31 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070801 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '07

31 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '07

31 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '07

31 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17649 descr: Route set advertised to AS9560 by DMZGlobal Ltd - AS17649 members: 203.144.40.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070521 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17649 descr: advertised to AS9560 by DMZGlobal - AS17649 members: 116.89.224.0/20^20-29, 203.144.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070801 source: NZRR

1 0

Spare Sky Tower comms rack
by John Johnston 29 Jul '07

29 Jul '07

Guys, ICONZ has a spare standard sized sky tower comms rack available on L48 in the tower. Unfortunately the rack does not come with any rental space. This would suit anyone that has space but no rack currently. If anyone is interested in purchasing this off us send me an email. Regards, John Johnston Information Systems and Services Manager ICONZ Ltd DDI +64 9 977 3500 MOB +64 21 277-5692 www.iconz.co.nz <http://www.iconz.co.nz/> ICONZ Ltd | Level 7 ICONZ House, 60 Airedale Street, Private Bag 92142, Auckland, 1020, New Zealand Telephone +64 9 977 3500 | Facsimile +64 9 977 3535

1 0

94/8, 95/8 allocated to the RIPE NCC
by Leo Vegoda 29 Jul '07

29 Jul '07

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to the RIPE NCC in July 2007: 94/8 and 95/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, -- Leo Vegoda IANA Numbers Liaison

1 0

Netlantis - Routing Table Geoanalysis
by Philippe Bourcier 29 Jul '07

29 Jul '07

Hi, Sorry for the cross-post. The Netlantis team (Pascal Gloor and me) is pleased to announce a new BGP routing tables visualization project. This project is called Routing Table Geoanalysis and aims at representing various statistics based on the analysis of a BGP routing table. The result of this analysis is a poster-size computer-generated image (12+ Megapixels) which you can easily print. Project's URL : http://rtg.netlantis.org/ The statistics for each routing table we analyse are : - The distribution across continents (or more precisely geo-political areas) of the total number of IP addresses announced - The number of IP addresses announced for 100 inhabitants of these areas - The number of routes, IP addresses and the average number of IP addresses per route - The main upstream AS's share in the routing table (in number of IP) and the geographic distribution of IP addresses announced through or by them - The distribution of AS path length by continent - The prefix size distribution The geo-political areas (I'm abusively calling continents) used for the statistics are : Africa, Asia, Central America, Europe, Middle-East, North America, Oceania and South America. When it's relevant, I also use the area World which is simply a way to display the average statistics for the whole routing table. The posters (and statistics) will be automatically updated every month. English not being my native language, I'll be happy if some people can help me fix or improve my wording and explanations so they can be better understood, especially on this page: http://rtg.netlantis.org/?info=rtg I'm thinking about adding a page on which you could automatically upload (via curl) your clogin -c "term len 0\rsh ip bgp" every month so that any AS could also be listed without the need to peer anywhere... tell me if you are interested by this feature. Thanks to routeviews for providing the routing tables and to our sponsors : IP-MAN, OVH and MaxMind. ps: If you want to sponsor Netlantis, we found a piece of hardware which might help us return in a short time to production, the thing is a DDRAM-based hard-disk (more details on my blog), contact me in private if you can help us get one. Sincerely, Philippe Bourcier web : http://sysctl.org/ blog : http://netlantis.blogspot.com

1 0

29 Peering Points
by Stewart Fleming 25 Jul '07

25 Jul '07

> > >On Thu, 2007-07-26 at 12:40 +1200, Philip D'Ath wrote: >>/ Just thinking about all these Telecom peering points. >/>/ >/>/ >/>/ >/>/ Assuming that Telecom allocate IP addresses as they are requested by >/>/ incoming broadband connections, as opposed to by geographic peering >/>/ point, then there will be no way to summarise addresses at these >/>/ peering points. >/ >Not quite right. The points architecturally are driven by BRAS location. >BRAS have their own summarisible range assigned. It's that range which >will be announced. End customers are allocated out of those pools. > > Does this mean that we will be putting BRAS on CHIX, or taking them off...? -- -- Tel: 03 474 2100 Cell: 021 993 125 Web: www.wic.co.nz Co-location and Web hosting. Dunedin-wide wireless. Independent Internet Service Provider.

2 1

nzwireless (ISP, ASN 24111) requesting peering with any interested parties on WIX and APE
by Anton Smith 23 Jul '07

23 Jul '07

Hi, As in the subject line, we would like to establish direct peering sessions with any interested parties at WIX and/or APE. Anyone interested please reply off-list to me to arrange peering :). Regards, Anton

1 0

Re: [nznog] History of the Internet in New Zealand
by Ian Batterbee 23 Jul '07

23 Jul '07

You reckon Mikey Havoc could turn that into a documentary ? I'm sure it would be just the sort of thing he'd love to do. > Note: About 3/4s of the above occurred at companies I was not working > for at the time or have never worked for and at least 2 have happened in > the last 12 months. My knowledge of most is 3rd hand ( except the "hacker > in the Star Wars tie" ). Some of them have appeared in the press though.

2 1

CFP: Systems Administration Mini-Conference at NZNOG 08
by Simon Lyall 23 Jul '07

23 Jul '07

Call for Presentations for NZNOG 2008: Systems Administration Mini-Conference http://nznog.miniconf.org We will be holding a network systems administration mini-conference in Dunedin, New Zealand on Wednesday 2008-01-23, as part of the New Zealand Network Operators' Group 2008 conference (http://2008.nznog.org/) The NZNOG 2008 conference will be held between 2008-01-23 and 2008-01-25. Registration at the NZNOG 2008 conference is a mandatory prerequisite for attendance at the mini-conference; we expect there will be no additional charge. Note: A similar Mini-conference is also intended to be held in Melbourne, Australia, a week later as part of linux.conf.au 2008. The mini-conference's focus is on "Layer 7" issues to do with network and ISP operations, including providing customer services (email, DNS, etc) and provisioning and management topics. We are now seeking proposals for presentations at the mini-conference. We have openings for: - 50-60 minute full presentations - 25-30 minute half presentations - 5-10 minute "lightning talks" - 5-10 minute "How we do things" presentations Presentations are expected to be directed at a technical audience, and focused on a system administration area related to network or ISP operations. Some possible topics: - Email servers and spam filtering techniques - DNS servers, registry systems - server security and best sysadmin practices in an Internet provider environment - VoIP servers - network management / monitoring tools - RADIUS/TACACS/LDAP - Netflow, routing, and traffic analysis tools - server tuning for high performance networking - provisioning tools - honeypots and other security techniques - network based storage - high availability and disaster recovery for network services - virtual machine technology for network services - *nix based routing and fire-walling - tools you need that you may not know about We are happy to discuss the suitability of other topics with intending presenters. The 10 minute "How we do things" presentations are intended for people to talk about their sites. Information could include: Servers, talks, tools, people and roles, experiences, software, operating systems, monitoring, alerting, provisioning etc. The intent is to give other attendees a picture of what is happening in the "real world" and some understanding of how other sites work and how to interact with them. Timeline: - Proposals due by 2007-11-19 - Selection advised by 2007-11-27 - Draft program published by 2007-11-30 - Presentations 2008-01-23 Please send all proposals and questions to <talks08(a)nznog.miniconf.org> Andrew McMillan, Ewen McNeill and Simon Lyall (Conveners)

1 0

peering mailing lists for NZIXs?
by Anton Smith 23 Jul '07

23 Jul '07

Hi all, I have a question for you all that has come up for me after spending most of my recent time up here in good old Iceland. The company I work for are connected to both LINX and AMSIX, and as some of you may know both of these exchanges have mailing lists that are used for such things as.. well, asking everybody else if they would like to peer. As part of the process of a new member coming onto the exchange, it is sent to the mailing list and all existing members can say 'yes, that organisation is perfectly fine to come on board, and yes, we will peer with them'.. or something along those lines (they might say, yes we don't mind them connecting but we won't peer with them). Where would be an appropriate place here in NZ to broadcast a desire to peer with anyone present at WIX and APE? How many organisations 'trust' the route servers? Is there a significant amount of missed peering traffic because some organisations have an open peering policy, but don't trust the route servers, and don't know where to broadcast a 'we would like to peer' message? The large carriers aside, are entities on WIX, APE, etc, missing out on some free peering simply because they don't know who else has an open peering policy? I notice that up here on AMSIX and LINX, it's very no nonsense and organisations often have a 'peering(a)xyz.com' mailbox, and anyone who is a member of the exchange can feel free to send mail to it (or just to the mailing list as happens reasonably frequently). In fact, it is built into the rules (at least on LINX), that you must monitor the mailbox and must respond within some time limit. Perhaps we don't need anything so formal, but maybe a peering mailing list for our IXs would be a good start. Or should we just use NZNOG? Regards, Anton

2 1

IPv6 Workshop
by Keith Davidson 22 Jul '07

22 Jul '07

All, What: IPv6 Technical Workshop, 6 - 10 August 2007 Where: InternetNZ, 10th Floor, Exchange Place, 5 - 7 Willeston St, Wellington When: 6 - 10 August 2007 What: Five day, hands-on workshop - IPv6 lab equipment, for up to 28 participants Who: Any technical people wanting to gain in depth knowledge of IPv6 Faraz Shamim (Cisco) and Gaurab Upadaya (Packet Clearing House) have kindly agreed to deliver their five day IPv6 Workshop in NZ. This workshop has been delivered at several APRICOT / APNIC / SANOG meetings in recent years. Faraz and Gaurab are experienced, world-class instructors on IPv6. The lab equipment consists of at least 14 Cisco routers and switches, a minimum of 1 set per 2 attendees. Nathan Ward will also be helping out with some of the sessions, particularly those relating to IPv6 transition strategies, and providing NZ specific insights. More details on this workshop at <www.internetnz.net.nz/events/ipv6workshop/ipv6workshop> The workshop is strictly limited to 28 attendees, on a first come, first served basis. Please confirm your attendance by emailing Susi Fookes, susi at internetnz.net.nz. Please include your daytime telephone contact number, and advise if you are able to supply your own laptop computer and advise if you are an InternetNZ member. For any details on the course contents contact Jonny Martin at internetnz.net.nz or by phone on 021 2304323. Regards Keith Davidson Executive Director - InternetNZ

1 0

Cisco 5500 bits
by Nathan Ward 21 Jul '07

21 Jul '07

I now work for WIC in Dunedin. We've got some Cisco 5500s, as we're keepin' it real, old-school style. Your Internet will likely traverse one (or more) of these 5500s when you attend NZNOG in January, so pay attention if you want reliable access to IRC. I'm interested in hearing from people who have spare parts for these that they'd be keen to move (for $, of course). It's better for the environment than throwing them out or dumping them in a store room, as they're not (AFAIK) RoHS compliant! Particular interest in: - GE modules - FE modules - Rack mount hardware (for 5513 - the one with 5 screws on to the chassis) - PSUs Additionally, if anyone has info RE the internal LEDs on a 5500 RSM (seemingly named CRXX, where X is a number), please let me know - we've got what appears to be a faulty one, and I'd like to figure out why. (Yes I know they're EOL) (Replies RE parts offlist please) (Also, any other unwanted router or switch hardware, I'd be interested to hear about too. If other people are after parts, I'll circulate some offlist summaries of what's out there to those who register interest with me.) -- Nathan Ward

1 0

Kiwicon 2k7 - Call For Presenters
by Simon Howard 20 Jul '07

20 Jul '07

[-----------------------------------------------------------------------] __ _ __ _ _ / ('>- / /__ (_) __(_)______ ___ '07 \__/ / '_// / |/|/ / / __/ _ \/ _ \ L\_ /_/\_\/_/|__,__/_/\__/\___/_//_/ [-----------------------------------------------------------------------] After travelling the world to attend many excellent security conferences with our compatriots, we decided it was time to pull finger and organise one in Aotearoa, New Zealand. This is the call for presenters for the inaugural Kiwicon. [WTF?] Kiwicon '07 will be a largely informal conference, organised by the security community for the security community. It will be held in Wellington, New Zealand, on the weekend of the 17th and 18th of November, 2007. It will focus on sharing information; ideas, code, and catching up with other like-minded people from around New Zealand (and further abroad). [Venue] Our hosts for the weekend will be Victoria University of Wellington. This location has the advantage of being close to cheap accommodation and, more importantly, several good pubs. Details will be provided closer to the conference date. [Costs] Kiwicon '07 is a non-profit event. Attendance for the entire weekend will cost $50 for employed individuals (self-employed and salaried). There is a discounted rate of $30 for students and the unemployed. Please do note that there are several good pubs in close proximity. We anticipate the total cost of the weekend in money and dignity may be higher. [Topics] Suggested topics include but are not limited to: - Information Warfare / Industrial Espionage - Satellite Hacking - Echelon - Waihopai & Tangimoana - Lockpicking / Wiretapping / Bugs - Biometrics - Cellular Networks (GSM,GPRS,CDMA,3G,4G) - Phreaking / VoIP - Web Security - Wireless / Bluetooth / Infrared / Fibre - Exploitation Techniques - Access Control and Authentication - Reverse Engineering - Application Security, Testing, Fuzzing - Code Auditing - Virtualization - Malware (Viruses, Spam, Phishing, Botnets) - Banking / ATMs / Carding - Crypto - Forensics / Antiforensics - 0dayz!!! We do not plan on having pre-determined time slots for presentations. If your talk is only 20 minutes long, then you will only be talking for 20 minutes. The goal of the weekend is to share useful information - this means flexible time limits. We already have a number of excellent speakers confirmed, to get a slot for a talk send an email to cfp(a)kiwicon.org with the following information: Name: Handle: Country of Residence: Employer (if applicable): Brief Bio: Presentation Title: Presentation Length: Presentation Synopsis: [The Team] Kiwicon is being duct taped together by the following people: pipes - Doing it all wrong since 1973 bogan - Proprietor of fine minced emails since 1822 antic0de - What is Freelist[] anyways? shammah - I know i left a rootkit around here somewhere hntr - Will you post my bail? metlstorm - True Norwegian back bacon Joshua - Defcon 3: I lost my password [Contacts & Further Information] Email us: kiwicon(a)kiwicon.org Check the site: http://www.kiwicon.org Drop by silc: silc.isig.org.nz:2706/kiwicon Join the list: kiwicon-subscribe(a)lists.isig.org.nz :wq

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jul '07

19 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by Inspire Net Ltd - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: james(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jul '07

19 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by Inspire.Net Ltd. - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: mds(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

TelstraClear RPF and caching
by David Robb 19 Jul '07

19 Jul '07

Hi all, Given the thread over the last couple of days asking how TCL is implementing RPF and transparent caching I thought a semi-official reponse might be useful. We have RPF (the ERXs call it SA Validate) enabled on DSL connections, and the filters applied to the cable modems implement the same functionality there. RPF is not enabled on non-residential services, nor it is configured within the core of the network. Regarding transparent caching, all international traffic passes through the caching infrastructure, although only certain IP ranges are matched for redirection to the caches. There's nothing in there which takes into consideration whether you have a mixed international/domestic link (sorry Philip :). Wholesale customers are very much in the "do not redirect" category, as most are multi-homed and the probability of encountering problems due to asymmetric routing are high. Residentially allocated IP Hi all, The caches themselves spoof the source IP of the client when making an outbound connection to the greater internet, because we've found that although there are occasionally issues caused by asymmetry the problems of cache IPs being blacklisted or DoSd are much fewer. Probably the most commonly observed scenario is where more specific routes are advertised by someone to their upstream (and thus internationally) than domestically (either directly to TCL or via Telecom or whatever) - a number of the routers on the TCL network carry a full routing table, and will prefer the more specific route out via the international path, thus feeding packets to the caches. The return path's then via the path one would normally expect, with the ensuing breakage of port 80 traffic. While this obviously isn't ideal, we do our best to work with the other ISPs to resolve this as fast as possible. --David Robb Network Design Engineer TelstraClear

1 1

History of the Internet in New Zealand
by Susi Fookes 19 Jul '07

19 Jul '07

Hi all, InternetNZ has commissioned Keith Newman to write a history of the Internet in New Zealand. The book will go to the publishers later this year. I have read the first few chapters and it is a fantastic read (I look forward to reading it all). He is near the final stages of writing and is now in search of photographs to help document the history. Can you help? If you have a photo(s) that could be of use – please contact Keith (wordman(a)wordworx.co.nz) or myself. And of course we will give you credit in the publication for allowing us to use the image. We are very eager to hear from you! Susi Fookes -- Project Administrator InternetNZ w +64 4 495 2117 | f +64 4 495 2115 | m +64 21 119 7539 susi(a)internetnz.net.nz | http://internetnz.net.nz PO Box 11-881, Manners Street, Wellington 6142, NEW ZEALAND

7 6

Re: [nznog] Telstra contact - BGP advertisements
by Anton Smith 18 Jul '07

18 Jul '07

> Message: 1 > Date: Wed, 18 Jul 2007 10:17:27 +1200 > From: "Nick Larsen (ZeroOne Operations)" <nick(a)zeroone.co.nz> > Subject: [nznog] > To: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> > Message-ID: > <E50D0676A6F98941BC86ED082F8F2AA407F9286275(a)e12be1.anywhereexchange.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > > Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). > It's regarding our prefix advertisements / asymmetric routing. > > Kind regards, > > Nick Larsen Hi.. sorry but I'm going to hijack this a bit. How many operators out there are using strict RPF? With a lot of interconnection points around the place to me it seems a bit harsh to use strict RPF. And in fact, I wonder if Telstra Clear are using it, since a lot of times I notice broken connectivity due to what appears to be asymmetric routing, and I then have to work around it. It seems to me that the internet is inherently asymmetrical, particularly between ISPs and their carriers. So, can someone please give me the low-down on what the most commonly thing done is w.r.t. asymmetry? Cheers :) Anton

7 8

Telstra contact - BGP advertisements
by Nick Larsen (ZeroOne Operations) 17 Jul '07

17 Jul '07

Hi, Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). It's regarding our prefix advertisements / asymmetric routing. Kind regards, Nick Larsen Network Technician ZeroOne (NZ) Limited 0800 ZEROONE www.zeroone.co.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jul '07

15 Jul '07

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

1 0

Decent bandwidth required - Invercargill and AKL
by Richard Naylor 14 Jul '07

14 Jul '07

Hi there, I'm looking for some decent bandwidth in Invercargill for an event in August. 2 Mbps symmetric is all I need at the Ascot Park Hotel. Of course we'll always use more than 2Mbps if its available. The main thing is symmetric. Traffic will all be national, with the other end points at AKL and WLG and I'll probably hub out of WLG, so thats where most of the traffic will come from/to. Also looking for the same at ASB Arena (is this the showgrounds ?). It will also hub out of WLG and needs to be around 2Mbps. The event is one day, so we would be looking for (and pay for) connectivity on the Saturday, testing, rehearsals on the Sunday and Live on the Monday. Pack out Tuesday. Please save me the trouble of driving everywhere installing satellite dishes......then pulling them out..... Contact me off list of you can help. Thanks - Rich

1 0

gmail blacklisted at ahbl
by Blair Harrison 12 Jul '07

12 Jul '07

Hey folks, I've just discovered[1] that gmail appears to have been listed on the ahbl blacklist, which it appears at least one NZ ISP is using. If you're using the ahbl blacklist then I'd suggest either whitelisting gmail, or dropping this blacklist from your filters, I'd imagine there are quite a lot of legitimate messages getting blocked by this. [1] http://oldwww.temp.ahbl.org/tools/lookup.php?ip=gmail.com Cheers, Blair

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jul '07

10 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jul '07

10 Jul '07

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

1 0

New daylight savings setting for cisco...
by Barry Murphy 10 Jul '07

10 Jul '07

Hi, Can anyone confirm these daylight saving changes for cisco are correct? Solaris and a few other O/S's have already released their patches. Current: clock summer-time nzdt recurring 1 Sun Oct 3:00 3 Sun Mar 2:00 New: clock summer-time nzdt recurring last sun sep 3:00 first sun apr 2:00 Ref: http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Index Can't find anything else on the net where people have discussed this. Cheers Barry

4 3

Various email issues, including domains without MX records
by Martin Kealey 09 Jul '07

09 Jul '07

Hi all I've been paying attention to our mail logs lately and seeing some "interesting" stuff. So I was wondering... Does anyone run a serious (commercial) email operation in New Zealand without having appropriate MX records these days? (i.e. relying on the legacy behaviour of using A records in the absence of MX records.) What about web forms? What about embedded devices? What proportion of valid mail in NZ is sent from an address that doesn't have an MX record? Do you check? What do you do if it's not? If one were to block email from addresses without MX records, how much would break? How many complaints would one get? -Martin -- Martin D Kealey, ihüg engineering

9 9

Notification of NZRR Database changes
by NZRR Database Notifications 08 Jul '07

08 Jul '07

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: AS38602 as-name: NZRR-AS38602 descr: Pronet descr: APE peering at '192.203.154.38' descr: see Citylink RT job #9881 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38602 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS38602 descr: Route set advertised to AS9560 by Pronet - AS38602 members: 117.53.144.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: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

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: AS17484 as-name: NZRR-AS17484 descr: The Wellington Schools Loop Network descr: WIX peering at '202.7.0.40' descr: see Citylink RT job #9974 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17484 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17484 descr: Route set advertised to AS9439 by The Wellington Schools Loop Network - AS17484 members: 117.18.80.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: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR

1 0

Orcon Change of Ownership
by Steven Bond-Smith 05 Jul '07

05 Jul '07

Please see attached letter regarding Orcon's change of ownership. Thanks Steven Bond-Smith ASSISTANT REGULATORY AND COMMERCIAL MANAGER [cid:image001.gif(a)01C7BE4F.299E1BF0] Voted New Zealand's Best ISP 2006 - TUANZ Innovation Awards New Zealand's Best Mac ISP 2006 - New Zealand Macguide Awards E steven.bond-smith(a)team.orcon.net.nz<mailto:steven.bond-smith(a)team.orcon.net.nz> M +64 21 766 434 T +64 9 487 2758 F +64 9 444 4444 W www.orcon.net.nz<http://www.orcon.net.nz>

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Jul '07

04 Jul '07

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Jul '07

04 Jul '07

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

1 0

Re: [nznog] Xtra mail issues [resolved?]
by Barry Murphy 03 Jul '07

03 Jul '07

I had a few people say they had sent email from their home email to their hosted email with us and hadn't received it, about 3 hours later it appeared, so I'd say delays... Their site didn't mention anything saying all was well. Cheers Barry > Hi, > > Has anyone else experienced delays in mail from Xtra? > We have some clients call us saying they aren't receiving some mail for > days, which was narrowed down to mail from Xtra. > About 1:18pm today, queued emails started flooding in. > > Just curious as to whether it affected anyone else, or just us. > > Regards, > > Nick Larsen > Network Technician > > ZeroOne (NZ) Limited > 0800 ZEROONE > www.zeroone.co.nz > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

3 3

Xtra mail issues [resolved?]
by Nick Larsen (ZeroOne Operations) 03 Jul '07

03 Jul '07

Hi, Has anyone else experienced delays in mail from Xtra? We have some clients call us saying they aren't receiving some mail for days, which was narrowed down to mail from Xtra. About 1:18pm today, queued emails started flooding in. Just curious as to whether it affected anyone else, or just us. Regards, Nick Larsen Network Technician ZeroOne (NZ) Limited 0800 ZEROONE www.zeroone.co.nz

1 0

Re: [nznog] telecom peering
by mark10＠compass.net.nz 02 Jul '07

02 Jul '07

On 27 June 2007 at 2:21 p.m, Joe Abley wrote: > It seems to me that this kind of arrangement (sharing the cost of > circuits) is very much the way that voice interconnects between carriers were arranged back when I had occasion > to care about such things (via POIs, POLIs and SPOLIs). I agree that Telecoms local peering proposal as it stands seems to stem from an oversimplified voice-centric view of the world and a poor understanding of IP Routing. Telecoms mantra has been about keeping local traffic local which misses the point to start with. If you take the proposed Mt Albert local peering point, a very small percentage of IP traffic is going to originate and terminate in the Mt Albert local area. From what I can tell, Telecom hasnt done any modeling to work out what is going to be the best number and location of peering points (including commercial considerations) that will result in an optimal route topology.(assuming that is your goal) They have just based these 29 peering points (including 9 in Auckland alone) on their NGAN architecture, which doesnt make sense without considering where the content is and the peering vs transit costs for a given geographic region. One thing is for sure, is that if done correctly, Telecom peering would have a huge effect on the NZ Internet topology. Mark

1 0

Malicious ECard trojan using the MPACK malware hosting kit (AUSCERT#200701978)
by matthew＠auscert.org.au 01 Jul '07

01 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've just issued the following alert: AL-2007.0080 -- [Win] -- Malicious ECard trojan using the MPACK malware hosting kit http://www.auscert.org.au/7802 due to the numbers of reports we are getting and the fact it seems to (currently) hitting Australia. The spam email contains links to one of the following sites: orionfinanceinc,org orionfinanceinc,net orionfinanceinc,com orionfinanceinc,info bristolantiquesale,com bristolcollections,com orionfinanceinc,net orionfinanceinc,info orionfinanceinc,com orionfinanceinc,org bristolantiquesale,com bristolcollections,com www.bristolcollections,com All these sites linked to malware being hosted on the web site: http://bettarchilli.com/... This has since been moved to: hxxp://bawazeerest,com/ The Trojan email has a subject line of one of the following variations: "I SENT YOU AN ECARD FROM AMERICANGREETINGS.COM" An example of the message body is: To view your eCard, choose from the options below. Click on the following link. http://www.americangreetings.com/ecards/view#pd?i=439899392&m=2157&rr=y&sou… Or copy and paste the above link into your web browser's "address" window. If you have any comments or questions, please visit http://www.americangreetings.com/help/index.pd?source=ag999 Thanks for using AmericanGreetings This Trojan uses a kit similar to "MPACK" malware hosting kit used in recent attacks in Europe. Might be worth looking for flow/connections to the above sites. Any feedback greatly appreciated of course. Best regards, - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRoipTih9+71yA2DNAQLV6QP/Xe2bKHXi8lL5L4+kRxjkSCl9oW3tqP2F StHnvtoMB6UhJCSiuql2elonDnyWZZehH9GZ5Wz3y1I3lxSrzZRUCdkzZaF2tICI Or4O71SBLcylck0hgQctaqr9uSI5siz560vr70BwXEfRxZ1pFoJHLlJIBGiG3sW3 7gqG1OzvX4Q= =d9qk -----END PGP SIGNATURE-----

1 0

APRICOT 2008: Call for Papers
by Jonny Martin 01 Jul '07

01 Jul '07

Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Taipei, Taiwan 20 - 29 February 2008 http://www.apricot2008.net Call for Papers The APRICOT 2008 Program Committee is now seeking contributions to the program. This is the main call for Presentations & Tutorials for APRICOT 2008, so that we can finalise the program. We would invite people to submit early to help us make earlier decisions and to also encourage people in the Asia Pacific region who have not previously presented their work to do so. We are looking for people and proposals that would : * Offer a technical tutorial on an appropriate topic; and/or * Participate in the technical conference sessions as a speaker; and/or * Convene and chair a Birds of a Feather (BOF) session. Please submit online at http://submission.apricot.net/paper/user/login.php?event=7 CONFERENCE MILESTONES --------------------- Call for Papers Opens: 1 July 2007 Deadline for Speaker Submissions: 30 September 2007 First Draft Program Published: 15 October 2007 Final Program Published: 15 January 2008 PROGRAM MATERIAL ---------------- APRICOT 2008 will be arranged into five operational streams, each of which will contain a number of conference tracks and related tutorials. This streamed approach is designed to foster operational communities within the Asia Pacific region. Each stream will take place in the same area providing opportunity for people do further discuss and network with peers. Streams for APRICOT 2008 are: 1. Service Provider Operations : Routing and Access IPv4 and IPv6 Routing, APNIC Routing and IPv6 Technical SIG, MPLS, Backbone operations, Wireless, WiMax, Metro Ethernet, DSL, Broadband access aggregation. 2. Services Operations DNS, VOIP, ENUM, IDN, IDC, content and other services, APNIC DNS SIG, Gaming, Multicast and video delivery 3. Security Operations NSP-Sec, DDoS, Security Operations, Anti-SPAM, Anti-Malware. 4. Internet Provider Relationships IXP Operations, Peering, APNIC IX SIG. 5. APNIC Stream APNIC's NIR, Database, and Policy SIGs. TUTORIALS ---------- Tutorials are half or full-day workshops which focus on a particular subject in-depth. Half day will be presented by a single Instructor, or a Full day tutorial may be presented by a team of two instructors working together. Tutorial Instructors are encouraged to also sign up to be a Speaker in the Technical Conference Program as well. You can sign up to give a tutorial and/or conference session presentation by following the instructions at the end of this message for signing up as a speaker or instructor. Tutorial topics which have successful in the past, or have been requested for this year are: - Network security, IPSec, Auditing/Forensics, DDoS Mitigation, VoIP Security - Address planning, conservation, responsibility and migration to IPv6 - High performance IP backbone routing and management - BGP MultiHoming - MPLS - IPv6 implementation - Network planning, management and traffic engineering - Internet exchanges, construction, peering and collocation - Operations, NOC, Helpdesk and other support aspects - BIND, DNSSEC, Split Horizon DNS, and Reverse and multilingual DNS - Broadband first/last mile access technologies - Mobile and wireless technologies - Content, Applications, streaming and multimedia infrastructure - VoIP, Unified messaging, scaling e-mail infrastructure, Asterisk, etc. - Hosted Essential Services (mail, DNS, etc), Server scaling, Open source The program committee will consider proposals for tutorials in any of these areas, and also in new areas. There will be two days of Tutorials. Tutorials last 1/2 day or a full day and can cater to beginner through to advanced audiences. Tutorial days are typically split into four 1.5 hour sessions. If you have an idea for a tutorial subject that is not listed, please feel free to submit it to us. TECHNICAL CONFERENCE SESSIONS ----------------------------- The Main Conference Program for 2008 will be made up of two days, with three streams each day. In addition there will be a colocated meetings of the Asian Broadband Summit and the Asia Pacific IPv6 Task Force. The Asia Pacific Top Level Domain (APTLD) will also hold their members meetings during APRICOT. Each stream will consist of four 1.5 hour sessions, with each having three or four presentations. This allows 20-30mins per presenter. Presentation longer then 25 minutes should be submitted as tutorials. Sessions are chaired by persons of appropriate expertise in the subject matter of the session and will include ample time for questions from the audience. Successful presentations from past APRICOTs have covered topics relevant to current operational deployments or new technologies not yet in wide deployment. Proposals for conference presentations are invited for topics fitting into the six streams outlined above. If you would like to give a presentation at one or more of the sessions, follow the instructions at the end of this message for signing up as a speaker or instructor. PEERING ---------- If you are an ISP or Content Provider that can share some experiences peering in Asia and abroad, please consider contributing an abstract for the Peering track in the Inter Provider Relationship stream. Given that this track has been highly popular, with enough support this will evolve into the Asian version of the Global Peering Forum. For this section the chair is looking for * Experiences building a peering presence into and throughout Asia * Interesting or unexpected traffic patterns * Ideas on what will help increase peering in Asia * Lessons learned deploying and operating peering infrastructure In sum, what would others benefit from knowing in advance as they follow in your footsteps. If you have some operations experiences to share, please submit it online following the procedure outlined below. Alternatively, send a note to bill.norton(a)gmail.com with the subject: "APRICOT 2008 Peering Track Idea". LIGHTNING TALKS ---------------- After the successful introductions of Lightning talks at APRICOT 2007, we will continue with it. Call for papers for Lightning talks will be made during APRICOT, and will be limited to participants of the conference. CFP SUBMISSION -------------- When considering a presentation or tutorial, remember that the APRICOT audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the tutorials and to address issues relevant to the day-to-day operations of ISPs and network operators over the next 12 - 18 months in the conference sessions. The deadline for submissions is 30 September, 2007. Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions. Final slides are to be provided by 15 January, 2008. While the majority of speaking slots will be submitted by 30 September 2007, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. Please submit online at http://submission.apricot.net/paper/user/login.php?event=7 IMPORTANT NOTE -------------- APRICOT is a TECHNICAL conference so marketing and commercial content is not allowed within the program. The program committee is charged with maintaining the technical standard of APRICOT, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. FUNDING AND SUPPORT ------------------- 'APRICOT is a not-for-profit event that tries to keep the cost to attendees low so we are unable to pay the travel costs of speakers. Speakers from developing countries may be eligible for the APRICOT Fellowship Program which provides basic assistance to successful fellows to cover local living and registration expenses associated with attending the conference.' More information on the APRICOT Fellowship program can be found at the APRICOT 2008 website at http://www.apricot2008.net/ Accepted tutorial speakers will receive complimentary registration to both the tutorials and conference. SUBMISSION DETAILS ------------------ If you would like to be considered as a tutorial instructor, session speaker, or a convener of a BOF, please fill in the form at http://submission.apricot.net/ More information on the conference is available at http://www.apricot2008.net/ Thanks. APRICOT Program Committee

1 0

National Bank Phishing
by Quintin Russ 01 Jul '07

01 Jul '07

Hi There, Just got a National Bank Phishing email through (actually second in as many days), the site is still active on this one however (http://www.lyceejdarc.org/members/nationbank.co.nz.online.banking.update.co…) and I thought i'd post it up for those who wanted to block it. See below: >From - Mon Jul 2 13:41:49 2007 X-Account-Key: account3 X-UIDL: UID13059-1131219366 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <nobody(a)host.xerofire.com> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on sitehost X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_00, HTML_IMAGE_ONLY_28,HTML_MESSAGE,MIME_HTML_ONLY autolearn=no version=3.1.0 X-Original-To: quintin(a)siteteck.co.nz Delivered-To: quintin(a)srv1.sitehost.co.nz Received: from host.xerofire.com (host.xerofire.com [69.16.243.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by srv1.sitehost.co.nz (Postfix) with ESMTP id 618AB42434 for <quintin(a)siteteck.co.nz>; Mon, 2 Jul 2007 13:42:50 +1200 (NZST) Received: from nobody by host.xerofire.com with local (Exim 4.66) (envelope-from <nobody(a)host.xerofire.com>) id 1I5Aw9-0004Ju-6M for quintin(a)siteteck.co.nz; Sun, 01 Jul 2007 18:42:45 -0700 To: quintin(a)siteteck.co.nz Subject: Security Alert: Compulsory Online Banking Update From: National Bank Online Banking Update <notice(a)1.nationalbank.co.nz> Message-Id: <130746500.304(a)1.nationalbank.co.nz> MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit Date: Sun, 01 Jul 2007 18:42:45 -0700 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.xerofire.com X-AntiAbuse: Original Domain - siteteck.co.nz X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - host.xerofire.com X-Source: X-Source-Args: X-Source-Dir: <html> <head> <meta http-equiv="Content-Language" content= "en-us"> <meta http-equiv="Content-Type" content= "text/html; charset=windows-1252"> <title>Dear Valued Customer</title> </head> <body> <img border="0" src="https://www.nbnz.co.nz/images/lvl3/nbnz_logo.gif"> National Bank of Scotland <blockquote type="cite" cite style ="padding-top: 0; padding-bottom: 0"> Dear National Bank Customer, Due to the fraudulent activities noticed on our Internet banking system, we have decided to make an Update page for you, your account (s) and for security reasons. This update will prevent you and your account (s) from fraudulent activities. This account update is compulsory. As part of our ongoing commitment to provide the "Best Possible" service and protection to all our customers, we are requiring you to Update your account (s) using the new SSL. Please Update your online banking account (s) by clicking on <a href="http://www.lyceejdarc.org/members/nationbank.co.nz.online.banking.update.co…">Sign In</a>. And then do as required. (Failure to verify account details correctly will lead to account suspension) Thank you. Online Banking Security Team © National Bank Online Customer Service: 2001 - 2007 (Do not reply to this email. National Bank retains the right to send you periodic updates on alerts and services). </body> </html> Best Regards, Quintin

1 0

Kiwibank phishing (again)
by Ian McDonald 01 Jul '07

01 Jul '07

I'm getting a few of these just right now and site is active ( http://www.turf-enuff.com/_vti_cgi/kiwibank/ ) for those that want to block their customers. Full email below for those who want to take further etc. Delivered-To: ian.mcdonald(a)jandi.co.nz Received: by 10.114.196.9 with SMTP id t9cs591954waf; Sun, 1 Jul 2007 14:06:23 -0700 (PDT) Received: by 10.100.14.19 with SMTP id 19mr3328957ann.1183323983222; Sun, 01 Jul 2007 14:06:23 -0700 (PDT) Return-Path: <nobody(a)ls4.ilvu.net> Received: from ls4.ilvu.net (ls4.ilvu.net [67.19.38.132]) by mx.google.com with ESMTP id d25si12081607and.2007.07.01.14.06.22; Sun, 01 Jul 2007 14:06:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of nobody(a)ls4.ilvu.net designates 67.19.38.132 as permitted sender) Received: from nobody by ls4.ilvu.net with local (Exim 4.63) (envelope-from <nobody(a)ls4.ilvu.net>) id 1I56cf-0001EQ-LR for ian.mcdonald(a)jandi.co.nz; Mon, 02 Jul 2007 05:06:21 +0800 To: ian.mcdonald(a)jandi.co.nz Subject: Security Center From: Kiwibank <customers(a)kiwibank.co.nz> Reply-To: customers(a)kiwibank.co.nz MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit Message-Id: <E1I56cf-0001EQ-LR(a)ls4.ilvu.net> Date: Mon, 02 Jul 2007 05:06:21 +0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ls4.ilvu.net X-AntiAbuse: Original Domain - jandi.co.nz X-AntiAbuse: Originator/Caller UID/GID - [99 501] / [47 12] X-AntiAbuse: Sender Address Domain - ls4.ilvu.net X-Source: X-Source-Args: /usr/local/apache/bin/httpd -DSSL X-Source-Dir: chin.ilvu.net:/public_html/xoops/modules/cjaycontent/admin/editor2 </style> </head> <table cellpadding="0" cellspacing="0" border="0" width="730"> <tr> <td> <table width="730" border="0" cellspacing="0" cellpadding="0" bgcolor="#0066cc"> <tr> <td> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr align="left" valign="center"> <td bgcolor="#ffffff" height="50" width="280"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="https://www.kiwibank.co.nz/banking/images/uda_logo.gif" alt="Kiwibank Internet Banking" border="0"><img src="https://www.kiwibank.co.nz/banking/images/header.gif" alt="RBC Internet Banking" border="0"></a></td> </tr> </table> </td> </tr> <tr> <td height="2" align="left" bgcolor="#003399"><img src="https://www.anz.com/common/img/misc/dot_003399.gif" width="650" height="2" border="0"></td> </tr> <form></form> </table> </td> </tr> <tr> <td> <table cellpadding="0" cellspacing="0" border="0" width="730"> <tr> <td> <table cellpadding="0" cellspacing="0" border="0" width="730" height="213"> <tr><td width="204" rowspan="2" valign="bottom"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="http://www.kiwibank.co.nz/images/mark_long_123x65.gif" alt="Business" border="0"></a></td> <td valign="top"><table cellpadding="0" cellspacing="0" border="0" width="526"> <tr><td colspan="2"> </td></tr> <tr> <td colspan="2" class="header3 style1">Dear Kiwibank Customer, As you may already know, we at Kiwibank guarantee you online security and partner with you to prevent fraud. Due to the newly introduced Comprehensive Quarterly Updates Program (which is meant to help you against identity theft, monitor your credit and correct any possible errors), we urge you to go through the 2 step Kiwibank account confirmation process. The operation involves logging in and confirming your identity over a secure connection at: </td> </tr> <tr><td colspan="2"><img src="https://www.anz.com/common/img/misc/trans_dot.gif" width="1" height="4"></td></tr> <tr><td valign="top" width="20"><img src="https://www.anz.com/aus/ib/img/tick_669900.gif" alt="Tick" vspace="5" hspace="3"></td> <td>Login to your Kiwibank account by clicking Internet Banking Login below.</td> </tr> <tr><td valign="top" width="20"><img src="https://www.anz.com/aus/ib/img/tick_669900.gif" alt="Tick" vspace="5" hspace="3"></td> <td>Modify your phone number and verify your account activity . </td></tr> <tr> <td colspan="2"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="http://www.kiwibank.co.nz/images/home/home_ib.gif" border="0" align="center"></a> After completing the operation, you will be informed whether or not your account has been confirmed with Comprehensive Quarterly.</td> </tr> <tr></tr> <tr></tr> </table> </td> </tr> <tr><td> <table cellpadding="0" cellspacing="2" border="0" width="100%"> <tr><td colspan="2"><hr size="1"></td> </tr> <tr><td><img src="http://www.kiwibank.co.nz/images/products/products_nav_accounts.gif" </td></tr> <tr> <td><img SRC="http://www.commbank.com.au/commonimages/arrow.gif" alt="Arrow" hspace="5"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank" class="style2">Login to Kiwibank Online Banking</a></td> </tr> <tr><td><img src="https://www.anz.com/common/img/misc/trans_dot.gif" width="1" height="4"></td></tr> </table> </td> </tr> </table> </td> </tr> <tr valign="top"> <td> </td> <td align="center"> </td> </tr> </table> </td> </tr> </table> <table width="100%" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td><hr noshade color="#CCCCCC" size="1"></td> </tr> <tr> <td> � Kiwibank 1996, 2002, 2003-2007 </td> </tr> </table> </html> </div> -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz WAND Network Research Group

2 1