- NZNOG - lists.nznog.org

Re: [nznog] TelstraClear Cable
by Tony Wicks 03 Feb '08

03 Feb '08

Tony, Just wondering where you heard this as I am sat at home right now on a Wholesale TelstraCable connection that runs straight into our network. If they are dropping wholesale I'll have a busy week next week moving our customers. Hmm.. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited They informed me this when I asked to check for cable availability for a couple of customers. My impression is they are refusing to add new connections for wholesale customers not so much existing ones. But who knows ? You would have thought some sort of official announcement would have been appropriate not just (quote) – “we do not resale cable modems” And further clarification when asked – “We no longer wholesale cable modems” I know there has been very little interest from wholesale ISP’s in wholesaling cable (that can be expected when the wholesale price exceeds the Telco’s retail price and at lower speeds), but it does seem strange. Especially with the work being done to improve the wholesale access and redundancy to the network. This reeks of a its too hard to do the paperwork so we’ll just tell customers we don’t do it anymore if they ask. Its really quite disappointing, I wonder what they would do if Telecom came along and asked for wholesale access.

2 1

CDNs in NZ?
by Simon Lyall 02 Feb '08

02 Feb '08

Just wondering if anyone is aware of any commercial Content Delivery Networks with distributed NZ-based Internet delivery points apart from Akamai and Citylink? By "commercial" I mean ones that people can buy delivery off, not "internal only" ones such as the root servers. By "distributed" I mean a minimum of APE and WIX. Connectivity to the other half of the NZ eyeballs would be good too. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

5 5

colville fibre
by Fred Look 02 Feb '08

02 Feb '08

hello folks does anyone know where exactly telecom is up to with the fiber cable for northern coromandel we were promised "before christmas" and workers came and layed lots of fiberoptic then.......... nothing tried telecom site but no info who might i ask or better still apply some encouragement to Fred Look brees

2 1

Re: [nznog] Orcon traffic going intl to telstraclear for some ranges
by Barry Murphy 30 Jan '08

30 Jan '08

Thanks, Just as I suspected. On calling orcon they said they were un aware of the issue, even though it had been present for 2hrs 30 mins (I always give them time to fix something incase they caused it and to allow others to call in). I logged a case and it's now been an hr with no word back, so I'm not sure what the issue is, will call them now. Thanks for the input people. Cheers B > A trace from my Orcon dsl to www.telstraclear.co.nz goes via asianetcom. I > suspect Orcon may not be listening to telstraclear's domestic prefix > list.. > or their domestic Telstra circuit has gone dead.. > > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Thursday, January 31, 2008 3:14 PM > To: Joe > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Orcon traffic going intl to telstraclear for some > ranges > > Yeh as per my trace, clear was ok, telstraclear.co.nz , paradise.net.nz > and a few others were not. Just like to hear from those that see the same > issue, and I'm guessing it may be an orcon only fault. > > Cheers > B > > >> Test from 202.20.5.34 (DTS Ltd) >> Host >> Loss% Snt Last Avg Best Wrst StDev >> 1. >> 192.168.1.1 >> 0.0% 10 0.3 0.3 0.2 0.3 0.0 >> 2. >> dts-uh-gw-dmz2.dts.net.nz >> 0.0% 10 2.0 2.5 2.0 4.6 0.8 >> 3. >> dts-slx-gw.dts.net.nz >> 0.0% 10 2.5 2.3 1.8 3.1 0.4 >> 4. >> g1-0-1159b.u21.tar.telstraclear.net >> 0.0% 10 4.1 6.1 4.1 18.5 4.4 >> 5. >> ae1-844.ie4.telstraclear.net >> 0.0% 10 3.3 4.2 3.2 9.3 1.9 >> 6. >> ge-1-2-0-843.ie1.telstraclear.net >> 0.0% 10 13.3 25.4 13.3 62.5 18.5 >> 7. >> front1-clix.clear.net.nz >> 0.0% 10 13.8 14.3 13.5 16.4 1.0 >> 8. >> karma.clear.net.nz >> 0.0% 10 14.5 15.0 13.7 16.9 1.2 >> >> Looks fine from here. >> >> Regards, >> >> Joe. >> >> Barry Murphy wrote: >>> Anyone else noticed this since 12 this afternoon, traffic to some >>> telstra >>> ip ranges going international even though they appear in my national >>> routing table supplied by orcon... I've confirmed this from one other >>> host >>> (tr.meta.net.nz) on orcon, anyone else? >>> >>> Telstra DSL customers, their web hosting division and a few others are >>> going international then back into the country, however some clear >>> sites >>> are fine as per below: >>> >>> traceroute to karma.clear.net.nz (203.97.32.100), 64 hops max, 40 byte >>> packets >>> 1 primary (60.234.66.129) 0.635 ms 0.624 ms 0.586 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.523 ms 0.638 ms >>> 0.681 ms >>> 3 60.234.9.8 (60.234.9.8) 0.735 ms 1.384 ms 0.837 ms >>> 4 203.97.2.161 (203.97.2.161) 3.436 ms 3.243 ms 3.865 ms >>> 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 3.546 ms 7.114 >>> ms >>> 3.424 ms >>> 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 6.000 ms 3.777 >>> ms >>> 5.136 ms >>> 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.288 ms 15.050 >>> ms >>> 14.254 ms >>> 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 15.076 ms 42.059 >>> ms >>> 14.670 ms >>> 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.554 ms 11.333 ms >>> 11.358 ms >>> 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.270 ms >>> 12.990 >>> ms 13.572 ms >>> 11 front1-clix.clear.net.nz (203.167.243.212) 13.052 ms 13.249 ms >>> 12.983 ms >>> 12 karma.clear.net.nz (203.97.32.100) 13.143 ms 13.142 ms 13.069 ms >>> >>> >>> traceroute to 121-72-28-16.dsl.telstraclear.net (121.72.28.16), 64 hops >>> max, 40 byte packets >>> 1 primary (60.234.66.129) 0.642 ms 0.590 ms 0.557 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.549 ms 1.177 ms >>> 0.944 ms >>> 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 7.836 ms 6.838 ms >>> 5.536 ms >>> 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 5.077 ms >>> 3.406 ms 1.778 ms >>> 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 1.274 ms >>> 2.696 >>> ms 1.902 ms >>> 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.995 ms 29.158 >>> ms >>> 35.145 ms >>> 7 gi1-3.gw2.syd1.asianetcom.net (202.147.40.190) 31.912 ms 24.378 >>> ms >>> 26.212 ms >>> 8 61.88.133.205 (61.88.133.205) 27.267 ms 28.816 ms 28.926 ms >>> 9 GigabitEthernet1-4.ken12.Sydney.telstra.net (139.130.65.145) >>> 33.790 >>> ms 30.153 ms 26.487 ms >>> 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 30.889 ms >>> 28.365 ms 26.615 ms >>> 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 30.871 >>> ms >>> 28.709 ms 27.337 ms >>> 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 26.592 ms >>> 27.205 ms 28.404 ms >>> 13 unknown.net.reach.com (134.159.126.33) 27.117 ms 27.875 ms >>> 30.866 >>> ms >>> 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.229 ms 52.308 >>> ms >>> 58.073 ms >>> 15 203.167.233.14 (203.167.233.14) 52.988 ms 54.358 ms 53.908 ms >>> 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 29.688 ms 27.061 ms >>> 29.254 ms >>> 17 218.101.61.163 (218.101.61.163) 29.570 ms 29.038 ms 36.667 ms >>> 18 *^C >>> >>> >>> traceroute to www.paradise.net.nz (203.96.152.127), 64 hops max, 40 >>> byte >>> packets >>> 1 primary (60.234.66.129) 0.624 ms 0.638 ms 0.571 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.426 ms 0.446 ms >>> 0.426 ms >>> 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 2.177 ms 1.786 ms >>> 2.296 ms >>> 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 2.946 ms >>> 2.431 ms 1.834 ms >>> 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 0.990 ms >>> 2.633 >>> ms 2.567 ms >>> 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 25.366 ms 25.566 >>> ms >>> 25.068 ms >>> 7 gi1-2.gw2.syd1.asianetcom.net (202.147.40.182) 25.462 ms 24.029 >>> ms >>> 23.939 ms >>> 8 61.88.133.205 (61.88.133.205) 27.373 ms 26.260 ms 28.539 ms >>> 9 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 28.342 >>> ms >>> 31.793 ms 28.448 ms >>> 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 27.120 ms >>> 28.729 ms 34.028 ms >>> 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 34.244 >>> ms >>> 28.564 ms 29.506 ms >>> 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 197.367 ms >>> 204.040 ms 200.955 ms >>> 13 unknown.net.reach.com (134.159.126.33) 26.861 ms 31.010 ms >>> 29.032 >>> ms >>> 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.340 ms 50.991 >>> ms >>> 50.760 ms >>> 15 203.167.233.14 (203.167.233.14) 56.734 ms 51.162 ms 52.239 ms >>> 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 26.802 ms 25.833 ms >>> 27.581 ms >>> 17 218.101.61.162 (218.101.61.162) 27.050 ms 26.124 ms 31.480 ms >>> 18 218.101.61.42 (218.101.61.42) 43.502 ms 44.411 ms 46.399 ms >>> ^C >>> >>> >>> traceroute to www.clear.net.nz (203.97.33.220), 64 hops max, 40 byte >>> packets >>> 1 primary (60.234.66.129) 0.607 ms 0.610 ms 0.575 ms >>> 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.467 ms 0.833 ms >>> 0.523 ms >>> 3 60.234.9.8 (60.234.9.8) 0.537 ms 0.489 ms 0.495 ms >>> 4 203.97.2.161 (203.97.2.161) 19.630 ms 9.418 ms 6.234 ms >>> 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 11.222 ms 6.493 >>> ms >>> 3.908 ms >>> 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 4.781 ms 5.040 >>> ms >>> 3.573 ms >>> 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.362 ms 15.289 >>> ms >>> 13.767 ms >>> 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 14.173 ms 15.508 >>> ms >>> 14.625 ms >>> 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.188 ms 11.102 ms >>> 11.259 ms >>> 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.479 ms >>> 12.812 >>> ms 12.576 ms >>> 11 front1-clix.clear.net.nz (203.167.243.212) 12.714 ms 12.948 ms >>> 13.112 ms >>> ^C >>> >>> Cheers >>> Barry >>> >>> >>> _______________________________________________ >>> NZNOG mailing list >>> NZNOG(a)list.waikato.ac.nz >>> http://list.waikato.ac.nz/mailman/listinfo/nznog >>> >>> >> >> > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Orcon traffic going intl to telstraclear for some ranges
by Barry Murphy 30 Jan '08

30 Jan '08

Anyone else noticed this since 12 this afternoon, traffic to some telstra ip ranges going international even though they appear in my national routing table supplied by orcon... I've confirmed this from one other host (tr.meta.net.nz) on orcon, anyone else? Telstra DSL customers, their web hosting division and a few others are going international then back into the country, however some clear sites are fine as per below: traceroute to karma.clear.net.nz (203.97.32.100), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.635 ms 0.624 ms 0.586 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.523 ms 0.638 ms 0.681 ms 3 60.234.9.8 (60.234.9.8) 0.735 ms 1.384 ms 0.837 ms 4 203.97.2.161 (203.97.2.161) 3.436 ms 3.243 ms 3.865 ms 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 3.546 ms 7.114 ms 3.424 ms 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 6.000 ms 3.777 ms 5.136 ms 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.288 ms 15.050 ms 14.254 ms 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 15.076 ms 42.059 ms 14.670 ms 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.554 ms 11.333 ms 11.358 ms 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.270 ms 12.990 ms 13.572 ms 11 front1-clix.clear.net.nz (203.167.243.212) 13.052 ms 13.249 ms 12.983 ms 12 karma.clear.net.nz (203.97.32.100) 13.143 ms 13.142 ms 13.069 ms traceroute to 121-72-28-16.dsl.telstraclear.net (121.72.28.16), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.642 ms 0.590 ms 0.557 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.549 ms 1.177 ms 0.944 ms 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 7.836 ms 6.838 ms 5.536 ms 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 5.077 ms 3.406 ms 1.778 ms 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 1.274 ms 2.696 ms 1.902 ms 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.995 ms 29.158 ms 35.145 ms 7 gi1-3.gw2.syd1.asianetcom.net (202.147.40.190) 31.912 ms 24.378 ms 26.212 ms 8 61.88.133.205 (61.88.133.205) 27.267 ms 28.816 ms 28.926 ms 9 GigabitEthernet1-4.ken12.Sydney.telstra.net (139.130.65.145) 33.790 ms 30.153 ms 26.487 ms 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 30.889 ms 28.365 ms 26.615 ms 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 30.871 ms 28.709 ms 27.337 ms 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 26.592 ms 27.205 ms 28.404 ms 13 unknown.net.reach.com (134.159.126.33) 27.117 ms 27.875 ms 30.866 ms 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.229 ms 52.308 ms 58.073 ms 15 203.167.233.14 (203.167.233.14) 52.988 ms 54.358 ms 53.908 ms 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 29.688 ms 27.061 ms 29.254 ms 17 218.101.61.163 (218.101.61.163) 29.570 ms 29.038 ms 36.667 ms 18 *^C traceroute to www.paradise.net.nz (203.96.152.127), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.624 ms 0.638 ms 0.571 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.426 ms 0.446 ms 0.426 ms 3 ge-1-3-0-400.cr1.sky.orcon.net.nz (60.234.9.21) 2.177 ms 1.786 ms 2.296 ms 4 OrconInternet.gw1.akl1.asianetcom.net (203.192.167.153) 2.946 ms 2.431 ms 1.834 ms 5 ge-1-2-0-0.gw4.akl1.asianetcom.net (202.147.55.222) 0.990 ms 2.633 ms 2.567 ms 6 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 25.366 ms 25.566 ms 25.068 ms 7 gi1-2.gw2.syd1.asianetcom.net (202.147.40.182) 25.462 ms 24.029 ms 23.939 ms 8 61.88.133.205 (61.88.133.205) 27.373 ms 26.260 ms 28.539 ms 9 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 28.342 ms 31.793 ms 28.448 ms 10 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 27.120 ms 28.729 ms 34.028 ms 11 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 34.244 ms 28.564 ms 29.506 ms 12 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 197.367 ms 204.040 ms 200.955 ms 13 unknown.net.reach.com (134.159.126.33) 26.861 ms 31.010 ms 29.032 ms 14 i-3-0.tauc-core01.net.reach.com (202.84.142.142) 52.340 ms 50.991 ms 50.760 ms 15 203.167.233.14 (203.167.233.14) 56.734 ms 51.162 ms 52.239 ms 16 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 26.802 ms 25.833 ms 27.581 ms 17 218.101.61.162 (218.101.61.162) 27.050 ms 26.124 ms 31.480 ms 18 218.101.61.42 (218.101.61.42) 43.502 ms 44.411 ms 46.399 ms ^C traceroute to www.clear.net.nz (203.97.33.220), 64 hops max, 40 byte packets 1 primary (60.234.66.129) 0.607 ms 0.610 ms 0.575 ms 2 ge-0-3-0-200.cr1.nct.orcon.net.nz (60.234.9.1) 0.467 ms 0.833 ms 0.523 ms 3 60.234.9.8 (60.234.9.8) 0.537 ms 0.489 ms 0.495 ms 4 203.97.2.161 (203.97.2.161) 19.630 ms 9.418 ms 6.234 ms 5 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 11.222 ms 6.493 ms 3.908 ms 6 g9-0-945.u11.pnr.telstraclear.net (203.98.23.194) 4.781 ms 5.040 ms 3.573 ms 7 gi-4-0-878.u21.telstraclear.net (218.101.61.138) 14.362 ms 15.289 ms 13.767 ms 8 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 14.173 ms 15.508 ms 14.625 ms 9 ae1-844.ie4.telstraclear.net (218.101.61.117) 11.188 ms 11.102 ms 11.259 ms 10 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 12.479 ms 12.812 ms 12.576 ms 11 front1-clix.clear.net.nz (203.167.243.212) 12.714 ms 12.948 ms 13.112 ms ^C Cheers Barry

4 5

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Jan '08

30 Jan '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64546 descr: Route set for Intelligroup - AS64546 members: 210.48.106.48/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: cam(a)intelligroup.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040311 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64546 descr: advertised to AS9439 by Soltius New Zealand Limited - AS64546 members: 210.48.106.48/29, 210.48.106.160/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Paul.Trainor(a)soltius.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080131 source: NZRR ------------------------------------------------------------

1 0

Sky Tower power issues?
by Sid Jones 29 Jan '08

29 Jan '08

Anyone else got power issues at the Sky Tower..... We're getting an interesting story from an upstream about the status of the electricity. Call this me double-checking. -- cheers, Sid

2 1

Percentage of users that do peer-to-peer
by Nathan Ward 28 Jan '08

28 Jan '08

Hi guys, A short questionnaire for those of you who sell Internet services, if I may: 1) How many users (as a percentage) on your network use peer to peer? 2) Can you break that down in to: - Users that use p2p 1-3 days per month on average - Users that use p2p 1-6 days per week on average - Users that use p2p 6-7 days per week on average 3) What percentage of your network traffic is peer to peer? (by bitrate /and/ by packetrate, if possible) 4) What percentage of your users are users that do more than say, 80% of their traffic as peer to peer 5) Do you have a histogram available of % of users for various different amounts of data per month? If you reply, please do it offlist, I won't tell anyone your secrets, etc. I'm only after percentages. I don't work for any competing ISPs right now, so can't use your info competitively, this is for some Internet research work I'm doing - believe it or not in the IPv6 area. Findings will be publicly available and based on an aggregate of all ISPs who give me data, and I'll likely talk about my findings at the next NZNOG meeting. For the good of the Internet community and all that. If you have some kind of p2p shaping boxes, they tend to have these sorts of stats available. If you can only provide one or two of these stats, that's still really useful. Cheers! -- Nathan Ward

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Jan '08

28 Jan '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20080129 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Jan '08

28 Jan '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20080129 source: NZRR ------------------------------------------------------------

1 0

pdf presentations from conference
by Mark Smith 28 Jan '08

28 Jan '08

are the presentations from the conference up on the web page yet? -- Mark Smith E mark.smith(a)endace.com P +64 7 957 0540 W http://www.endace.com Endace Technologies, Limited 85 Alexandra Street Hamilton Endace delivers absolute performance for monitoring and intervention over the widest range of network types and software applications.

5 6

Mac bits left behind at NZNOG08
by Jonny Martin 28 Jan '08

28 Jan '08

A Mac mini-DIV to DVI and 3-pin to cloverleaf mains lead where behind at NZNOG last week. Let me know if they belong to you, and I'll send them off. Cheers, Jonny.

2 1

Updated .nz Domain Growth Statistics
by Blair Harrison 25 Jan '08

25 Jan '08

Hello List, I've updated my graphs once again and they are available to view at http://jedi.school.nz/nzdg.html Please let me know if you have any comments or ideas for other ways to display this information. Cheers, Blair

1 0

Perry's NZNOG'08 IP-over-something challenge!
by Nathan Ward 23 Jan '08

23 Jan '08

I hereby issue the challenge to get IP running over the dishes photographed at: http://unobtainium.braintrust.co.nz/~nward/dishes/ Normally, you'd stand at one and talk, and someone standing at the other would hear you.. you've all played with these before. Perry's challenge is to make two laptops talk to each other, using sound. Note: These photos were taken in winter, which is why those girls have lots of warm stuff on. I have a tshirt on today, but it's raining a little. -- Nathan Ward

15 20

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by yuri 22 Jan '08

22 Jan '08

On 24/01/2008, Bruce Kingsbury wrote: > > > Does one person standing at one dish speaking IP and the person at the > > other end reconstituting packets count as a solution? > > What, an IPoV solution? Hmmm.. You mean like this http://xkcd.com/257/ ? Yuri

1 0

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by Stu Fleming 22 Jan '08

22 Jan '08

> > From: Matthew Poole <matt(a)p00le.net> > Subject: Re: [nznog] Perry's NZNOG'08 IP-over-something challenge! > > > For those who don't understand the terminology, Ed's talking about pouring > roughly 15L/sec of cold, high-pressure water on said drunk students. Who, > presumably, won't stay drunk for long :P You obviously haven't been to Dunedin lately... Does one person standing at one dish speaking IP and the person at the other end reconstituting packets count as a solution?

2 1

NZNOG 2008 live stream
by Jonny Martin 22 Jan '08

22 Jan '08

Hi All. The live stream is available at http://www.r2.co.nz/20080124/ Recordings of all the sessions will also be available online after the conference, thanks to Richard Naylor and co. at R2. Cheers, Jonny.

1 0

Could someone from Compass, Orcon, DTS, Xtreme, Actrix, etc. please contact me off-list?
by Jonathan Brewer 22 Jan '08

22 Jan '08

Preferably in Dunedin. There's this conference going on, with at least 130 network admins present, and there are a couple of companies conspicuously absent. Regards...

1 1

NZNOG'08 session recording
by Cameron Kerr 22 Jan '08

22 Jan '08

Hello, due to an itinerary clash, I'll be on a bus all day Friday travelling to another conference. I understand the conference will be streamed. Will it also be available post-conference? Any details so far (perhaps this should go onto the Wiki? Many thanks. -- Cameron Kerr <ckerr(a)cs.otago.ac.nz> Telecommunications Teaching Fellow & SysAdmin Cell: 027 7175 244

1 0

Re: [nznog] Perry's NZNOG'08 IP-over-something challenge!
by Jonathan Woolley 22 Jan '08

22 Jan '08

>The main point is that soaking the aforementioned hackers (yes I >know!) with a high pressure hose won't really make them sober up in >a >pharmacological sense, but it would be great fun. > >Cheers - N Pharmocologically sober them up: no, psychologically sober them up: yes. And I think it's the behaviour of said student hackers we care about, so aside from the enjoyment factor it may prove effective as well!

1 0

Sir Ed's Live feed
by Ian Batterbee 22 Jan '08

22 Jan '08

Just out of interest, was anyone able to watch the funeral on tvnz's website ? I tried it on a host of different browsers and settings and the best I got was an "error in page" in IE, and a flash app in firefox etc that wouldn't display any video at all (but I could change the bitrate settings) Just wondering if it was just me / my connection ?

6 6

NZNOG 2008 - Call for Lightning Talks
by Jonny Martin 22 Jan '08

22 Jan '08

NZNOG 2008 - Call for Lightning Talks ===================================== The NZNOG 2008 call for lightning talks is now open! Lightning talks are scheduled for 9am sharp, this Friday 25 January. Lightning talks are short talks/presentations on relevant topics that last no more than 10 minutes. They may be as quick as one minute. This time limit is strictly enforced. Talks on topics that are timely, interesting, or a little crazy, are invited. If you've thought about presenting at a future NZNOG, a lightning talk this year is a great place to start! The use of slides is not required although most people choose to use them. Speakers typically prepare three or four slides. Ideally you will provide final slides in PDF format so we can present of a common laptop. If you have other applications or anything special you wish to use in your presentation, you are welcome to use your own laptop, but please be ready for a speedy setup. To submit a proposal for a Lightning Talk, send an email to nznog08(a)jonnynet.net *** Proposals are due by 3pm Thursday 24 January, so hurry *** You can find some useful advice on giving Lightning Talks at: http://www.justanotherperlhacker.org/lightning/ http://perl.plover.com/lt/lightning-talks.html http://www.metaart.org/maca/perl/lightning/lightning_what.html Thanks! The NZNOG 2008 team.

1 0

Re: [nznog] Sir Ed's Live feed
by Richard Hulse 22 Jan '08

22 Jan '08

>>> Ian Batterbee <ibatterb(a)gmail.com> 22/01/2008 19:42 >>> > Just wondering if it was just me / my connection ? Based on the numbers in this press release: http://www.scoop.co.nz/stories/CU0801/S00171.htm and combined with our own figures and info from the non publically owned stations, I'd estimate that NZ broadcasters were doing in excess of 1 gigabit/s. There might have been a few bottlenecks around the place.

1 0

Re: [nznog] Perry's NZNOG'08 IP-over-something challenge!
by elroy 21 Jan '08

21 Jan '08

1) Connect Laptop1 sound-card audio-in and audio-out to appropriate small speaker(s)/mic (1) ; add your favourite *nix; 'cat <pre-made signal file> > /dev/dsp' 2) Same setup Laptop2 is listening for xxx signal level on mic input - writes a 1 to a file in RAM tempfile when above predefined level, then a 0 when below - insert appropriate programming magic to monitor tempfile and interface to something useable... 3) Profit!!! (Or IP-over-Audio) Elroy. (1) Would the laptop built-in ones be sensitive/powerful enough?!? NOTES: 1) Maybe different frequencies for each units send/receive so Duplex can be achieved?!? 2) Sorry Michael! Michael Fincham wrote: > How about a couple of old analog modems with 9v batteries to simulate being connected to a line, along with a little audio amplifier / receiver? I see duplex being a problem in that situation, but it's a start... > > As an aside, we had briefly discussed the possibility of establishing an RFC 1149 IPoAC link for VPN back to the office for our man on the ground at NZNOG but the link quality was deemed unsuitable.

2 1

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 20 Jan '08

20 Jan '08

> >From TVNZ's press release: >"In addition to TVNZ's own live broadcast on TV ONE, live streaming >on tvnz.co.nz and replay on TVNZ ondemand, TVNZ has offered the >broadcast free of charge to domestic and international radio and >television broadcasters and agencies. > >"So far the following news organisations have requested access to >the TVNZ feed: >ABC Australia, Al Jazeera, APTN, BBC, Channel 9 Australia, Channel 10 >Australia, CNN, EBU (European Broadcasting Union), Reuters Australia, >SBS Australia, Sky News Australia, Prime/Sky, Radio Works, TV Works, >and Newstalk ZB." > >One would assume that this is a clean feed, since it will be used >(domestically) by the competing networks too. in theory. Practise is different. Often we have to switch out the ad breaks, so we mix our cameras, with the feed. It doesn't matter now. The plan was that we would have started at 9am this morning and gone on non-stop "as required". We were to cover inside the Cathedral where Sir Ed is lying in state. Its a good application of robotic cameras and webcasting - sort of fly on the wall stuff. I don't think TVNZ are covering that and DIA didn't want cameras in there. I suspect DIA's decision was based on respecting people's privacy when paying their respects. No one wants a camera in their face or a close up shot, when they're grieving. As robot operator, theres no way I'd have gone close up, but you'd have to trust my judgement. It was probably just all too new for DIA. Our client was TV3 and it may have been seen as a competitve move. The word I got was that clean feed or iso feeds off host broadcaster cameras were not available and we had to do it ourselves. That would have been easy in the Catherdral and then when the casket moved to the funeral we would have just switched to the host feed. The OB is probably rigging today so no feeds would be available until tomorrow. Its all too late now...... Rich

1 0

Sysadmin Miniconf programme online
by Ewen McNeill 20 Jan '08

20 Jan '08

For those that are interested, the programme for the Sysadmin Miniconf at NZNOG 2008 (in Dunedin, this Wedesday -- 23 January 2008) is now online: http://nznog.miniconf.org/programme08.html Ewen

1 0

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 19 Jan '08

19 Jan '08

At 09:09 a.m. 20/01/2008, David Robb wrote: >On Sat, 19 Jan 2008, Richard Naylor wrote: > >>Sadly DIA has advised our client (a broadcaster) that we're not >>allowed to place our cameras on site and so the job has been canned. >>Its really sad as it was a great application for webcasting. But the >>powers that be have decided "no cameras". <sigh> > >"No Cameras", yet they're having cameras to feed out to TV screens >in the neighbouring cathedral and in the Domain..? > >You can't just get a feed from those perhaps? No - the plan was for us to webcast a different part of the 2 days, not the "main event", so it would have been our cameras. Often we take an "international" or "clean" feed and mix that with our cameras. There is some discussion as to whether an international grade clean feed is available. RNZ are unable to make a clean feed available. There have been some space issues. The bottom line is we were turned down. DIA don't want cameras in the bit we were asked to cover. Sorry I'll explain later over beer - a bit of broadcaster competition was occuring. On the bright side - its 20hours driving less to do, and Jeremy doesn't have to fly to NZNOG in/out of AKL. He gets to fly out of DNN to WLG - then drive to AKL. Rich

2 1

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 19 Jan '08

19 Jan '08

Evening All, Further to my request for urgent help - I received a heap of really great offers and with some help with a Microwave link from Parnell to SKY, we had it all sorted. Sadly DIA has advised our client (a broadcaster) that we're not allowed to place our cameras on site and so the job has been canned. Its really sad as it was a great application for webcasting. But the powers that be have decided "no cameras". <sigh> So a big THANKS to everyone. There was terrific generosity - everyone really pulled in and it would have been a great project. (with lousy hours though). Next time.... Rich

2 1

URGENT - broadband connex in AKL
by Richard Naylor 16 Jan '08

16 Jan '08

Hi folks, I have an urgent need for 1-2Mbps of IP capacity from AKL to WIX for Monday-tuesday next week for the Ed Hillary funeral. I ay use satelite, but if a wireless operator can do a link to the Sky Tower for good money, I'd love to hear from them. And yes we will drive the 1-2Mbps fairly hard Cheers Richard

1 0

Spam statistics for AA
by Thomas Layzell 16 Jan '08

16 Jan '08

Here's our statistic for the last year: Total Spam Messages Dropped 9,490,810 Total Virus Messages Dropped 1,300 Total Clean Messages Processed 1,787,289 THOMAS LAYZELL | NETWORK MANAGER | INFORMATION & COMMUNICATIONS TECHNOLOGY The New Zealand Automobile Association Incorporated

1 0

ICANN: JPA midterm review - have your say
by Save Vocea 15 Jan '08

15 Jan '08

(apology for any duplicate - slightly less tech in nature but worth sharing as its about DNS admin) Dear colleagues, My first mail in 2008 - so very warm greetings all. First up I'd like to highlight this very important information from ICANN. ccTLD managers in each economy have received this as well. ICANN in the past have had its fair share of critics "for/against" the current model or it's relationship with the US Govt and transition to independence. (just have to Goggle to read this) May I request those that particularly follow ICANN work (and those new to this space) to spare some time to read through the latest announcement from ICANN website particularly the "Joint Project Agreement - ICANN response" about the Notice of Inquiry put out by the USG regarding ICANN and the USG Joint Partnership Agreement. The documents referenced will clarify why ICANN was formed and delegated the role to perform the technical coordination and management of the Internet’s domain name and addressing system (DNS). ICANN's role is now in midterm review with this Notice of Inquiry requested for by the USG. http://www.icann.org/ As you will see from ICANN's submission, among other things, it is the view of the ICANN Board that: ~ The JPA like the memorandums of understanding before it has helped ICANN to become a stable organization; ~ ICANN has executed the terms of the JPA commenced in September 2006; ~ ICANN is meeting its responsibilities under the JPA; ~ The JPA is no longer necessary. Concluding it is the next step in transition of the coordination of the Domain Name System (DNS) to the private sector; ~ This step will provide continuing confidence that the original vision laid out in the White Paper is being delivered; ~ Concluding the JPA will not affect existing accountabilities expressed in the IANA contract and the United States Government¹s participation through the Governmental Advisory Committee. I am sure that both ICANN and the US Department of Commerce would appreciate hearing the views of the Internet community on this important review. As there's a very narrow window in which to tailor and submit responses/comments I hope I can again contact some of you to discuss or please feel free to contact me at any time to clarify. It will be useful under this review term that as many responses are received from those parties interested to have a say. I encourage those interested in this list to also contribute to this process and to add to a truly global response. Now is the chance to get your voices heard. Comments close on 15 February. regards, -- Save Vocea Global Partnerships Manager, Regional Relations - Australasia/Pacific Islands http://www.icann.org ICANN is about coordination, not control

1 0

iperf/AS7108
by jamie baddeley 14 Jan '08

14 Jan '08

Hi There, Does anyone have ssh access to a well connected host that can run iperf that is either directly connected or very near AS7018 in the US? If so, can you please contact me offlist thanks? Cheers Jamie

1 0

OT - Martin Hunt
by Richard Naylor 14 Jan '08

14 Jan '08

Some of the list members who were around in the early 90's may have known Martin Hunt, a Sysadmin based in Wellington. He passed away suddenly at home last week aged 46. There was a death notice in Saturday's Dominion Post. He was a really nice guy. Martin worked at Govt Print (with Don Stokes, Larry Hall and Ian Calhaem, etc), then WCC IT Dept and latterly at Fairfax Media. While at WCC he was one of the Sysadmins who looked after WCC CityNet. He was active in DECUS in the early 90's. A service for Martin will be held in St Lukes, cnr Pitt St and Wadestown Rd, Wednesday 16 January at 1100 (sadly I have to be working elsewhere). Messages to Martin's family c/o P O Box 50-347 Porirua, or I can pass on emails via his brother. A really nice guy. He will be missed. Richard

2 1

NZRR Route Registry Update
by NZRR Database Notifications 14 Jan '08

14 Jan '08

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

1 0

Re: [nznog] Using nolisting to reduce spam
by Glen Eustace 14 Jan '08

14 Jan '08

> The primary downside initially is that any legitimate server is doing > two transactions for every email. This would delay mail slightly and > increase queue lengths and CPU usage of every legitimate mail server > sending to you. If everybody implemented this it would load mail > servers up a bit. My observation would be that a TCP reject doesn't result in a requeuing of the email. With postix, it would appear that the smtp sending process immediately tries the MX in the chain upto a max of 5 ( but this is configurable ). There is a SYN packet, an RST and then a SYN to the secondary, not IMHO a significant overhead or delay. NB: The first MX must reject the connection not just drop it, otherwise the behaviour you describe does occur. > Again it is a temporary workaround but it might be worthwhile for > knowledgable system administrators. Over time the issues of spam still > need to be sorted out but that is a longer term project and is both > technical and political. It would seem that all spam solutions are just sticking plasters but a 'defense-in-depth' approach using multiple techniques does seem to be viable for the time being. Glen.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Jan '08

10 Jan '08

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

1 0

Sysadmin Miniconf: Lightning talks
by Ewen McNeill 09 Jan '08

09 Jan '08

I would like to hold a lightning talk session during the Sysadmin Miniconf stream at NZNOG 2008 (in Dunedin very soon; register now!). If you would be willing to talk for 5-15 minutes about either: - a tool, or technique that you find useful and think others should know about; or - how your AS looks after servers, users, etc (eg, what you use for deploying servers, how you manage trouble tickets, how you handle mail, etc) I'd like to hear from you soon. Email nznog08 @ nznog.miniconf.org to register your interest in speaking with an indication of how much time you need to cover your topic (eg 5 minutes, or 15 minutes). Also if anyone is willing to talk about: - Deploying IPv6 aware applications[0]; or - A comparision of trouble ticket/helpdesk systems (RT versus OTRS versus...) I'd love to hear from you ASAP. Email nznog08 @ nznog.miniconf.org with offers to speak. Other topics are of course welcome too, but I'd need to know this week. Ewen McNeill For the Sysadmin Miniconf [0] Yes, I know there's an entire IPv6 stream on at the same time. But a shorter overview of the application aspects would still be very useful especially from a sysadmin who has "been there, done that" without necessarily having got involved in IPv6 routing.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Jan '08

08 Jan '08

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Jan '08

08 Jan '08

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

1 0

NZNOG 2008 - reminder!
by Jonny Martin 07 Jan '08

07 Jan '08

[Apologies for any duplicates...] A quick reminder that the NZNOG 2008 conference is only two weeks away now. http://conference.nznog.org We need to finalise numbers very shortly now, so go ahead and register NOW if you intend to come and haven't already. The largely-finalised programme is up on the website, there's been some great new additions over the past month so do check it out at: http://conference.nznog.org/conferenceprogramme.html Thanks, and looking forward to seeing you in Dunedin! Jonny.

2 1

Call for nominations to APNIC Executive Council
by Srinivas Chendi 03 Jan '08

03 Jan '08

_______________________________________________ CALL FOR NOMINATIONS TO APNIC EXECUTIVE COUNCIL _______________________________________________ Three positions on the APNIC Executive Council will be opened for election at the APNIC Member Meeting in Taipei on Friday, 29 February 2008. The members whose positions are up for re-election are Akinori Maemura, Che-Hoo Cheng, and Vinh Ngo, who were elected at the APNIC Member Meeting in Perth on 3 March 2006. Nominations are due by the close of business on Tuesday, 12 February 2008 at the latest (5:30pm UTC+10 Brisbane time). Only APNIC members may nominate and vote for candidates, but nominees do not have to be representatives of members. Nominations must be made using the online nomination form available at: http://www.apnic.net/meetings/25/elections/ec.html For more information on nominations received, proxy registration, current EC members, and the role of the EC, please refer to: http://www.apnic.net/meetings/25/elections/ Online voting will be available for this election via the MyAPNIC web site and will open soon after the nomination period closes. If you are not able to vote online or attend the AMM, you can still make your vote count by appointing a proxy to represent you at the meeting. Proxy forms are available at: http://www.apnic.net/meetings/proxy.html Nominees should note that positions on the APNIC Executive Council are currently voluntary and that APNIC may not be able to reimburse EC members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at secretariat(a)apnic.net. Regards, ________________________________________________________________________ APNIC Secretariat 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 25 Taipei, Taiwan, 25-29 February 2008 http://www.apnic.net/meetings/25 ------------------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 01 Jan '08

01 Jan '08

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR ------------------------------------------------------------

1 0

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

31 Dec '07

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. Meetings Our next annual conference is to be hosted by the WAND group in Hamilton on February 2nd to 4th, 2005. See http://www.nznog.org/ for more information, including the Call For Presentations. Offers to present are due in by 22nd October, and all presenters should have had their acceptance confirmed by 31st October. Also see http://auckland.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.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. See http://www.wix.net.nz/ for the Wellington Internet Exchange. About This Mailing List This list has slightly over 700 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 Donald Neal |Palmersdale: Are you in charge here? Technical Specialist |The Doctor: No, but I'm full of Operations Engineering | ideas. 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." ------------------------------------------------------------------------------

3 16

Seasons greetings message
by Elly Tawhai 20 Dec '07

20 Dec '07

Hi, Thank you for supporting APNIC this year. The APNIC Secretariat has created a short movie greeting for your enjoyment: http://www.apnic.net/flash/new-year-2008.swf We would like to wish you a safe and happy festive season and a prosperous new year. We look forward to working with you in 2008. Kind regards The staff of the APNIC Secretariat ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by KOrdia Ltd. - AS24324 members: 118.148.0.0/15^15-29, 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, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.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, 203.171.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071211 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/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, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-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, 203.171.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071128 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071128 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071221 source: NZRR ------------------------------------------------------------

1 0

Get your own strawberries email
by Dean Pemberton 19 Dec '07

19 Dec '07

Hi all. You no doubt will have all seen/heard about the latest viral (in the spreading, not the harming sense) email doing the rounds. http://www.stuff.co.nz/4330204a11.html I'm interested in what the breadth and depth of this email is, what the average branch size was etc. Could any of you who received the email (and if you got multiple copies that would be cool) forward me a copy with all the cascade still intact. I'm going to anonymise all the results, so don't worry about being identified. Dean

4 5

Updated domain stats
by Blair Harrison 19 Dec '07

19 Dec '07

Hi folks, I've re-done my domain stats spreadsheet / graphs to include the last three months. http://jedi.school.nz/nzdg.html I know the html version is ugly, Openoffice just doesn't seem to deal with it very well. Interesting to note that the net increase in domains last month was 5752, taking to a total of 311,198. Biggest jump yet, and crossed the 300,000 mark since I last looked at it all a few months ago :) Cheers, Blair

1 0

Flights to NZNOG...
by Jonny Martin 18 Dec '07

18 Dec '07

For all of you who have the impression that Dunedin is an expensive place to fly to... AirNZ currently have on offer, for 48hrs, discount flights to and from Dunedin ex Napier, Wellington, and Christchurch for $99, $89, and $59 respectively, one way. Travel valid for period 26 Dec through 31 Jan. Sounds good to me. http://airnz.co.nz/airfares_offers/hotdeals/hot_deals_fares/ new_zealand_summer_sale_19dec07.htm Oh, and did anyone remind you all to register for the conference? ;) Cheers, Jonny.

3 4

[Fwd: Re: Flights to NZNOG...]
by Dean Pemberton 17 Dec '07

17 Dec '07

Heh - nope - I can't get a refund on the $300 I paid for "Getting in Early" either =) Those prices are almost less than I paid in petrol to get to the last one in Palmie. Dean -------- Original Message -------- any way to get the refund on the USD 400 plus i have already spent to get there from AKL? :) --bill On Tue, Dec 18, 2007 at 03:07:03PM +1300, Jonny Martin wrote: > For all of you who have the impression that Dunedin is an expensive > place to fly to... > > AirNZ currently have on offer, for 48hrs, discount flights to and > from Dunedin ex Napier, Wellington, and Christchurch for $99, $89, > and $59 respectively, one way. Travel valid for period 26 Dec > through 31 Jan. Sounds good to me. > > http://airnz.co.nz/airfares_offers/hotdeals/hot_deals_fares/ > new_zealand_summer_sale_19dec07.htm > > Oh, and did anyone remind you all to register for the conference? ;) > > Cheers, > Jonny. > > _______________________________________________ > 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

2 1

NZNOG 2008 - Fellowship Program
by Jonny Martin 17 Dec '07

17 Dec '07

Hi All, The NZNOG Organising committee is trying something a little different this year and offering a small number of Fellowships to the conference. The aim of this is to provide assistance to those people that mightn't otherwise be able to come - but have a lot to offer to, or gain from, the NZNOG community. The fellowships will cover up to four nights accommodation at the NZNOG hostel and the conference registration fee. Five fellowship packages are being made available. Criteria for applicants: - They write a few paragraphs explaining why they need a fellowship to NZNOG08 and what they hope to get out of it, and otherwise convince us that they're not after a freebie for the sake of it being free. - Their employer can't or won't cover them and they're having to cover costs personally or they're a student / unemployed. - They have a history of involvement in the NZNOG community, or can demonstrate an intent to do so, or how attending an NZNOG community will benefit them. - It will help greatly if they are presenting a talk (or intend to) and wouldn't be able to without some form of fellowship assistance - They actually have to attend the NZNOG sessions, and not run off sightseeing or touring the local breweries! Submissions will be evaluated by the NZNOG 2008 organising committee. Email your submissions to prog08(a)nznog.org Closing date for applications 23:59hrs Wednesday 19th December (that's soon!) Successful applicants notified on Friday 21st December. For those of you who like something a little more than plaintext, all these details are at: http://conference.nznog.org/fellowships.html Cheers, Jonny.

2 1

<OT> Araneo is Hiring
by Jonathan Brewer 16 Dec '07

16 Dec '07

Hi Folks, We have a mid-level position at Araneo open in provisioning. Details on our website. http://www.araneo.net.nz/jobposting1207 Cheers, Jonathan Brewer -------------------------------- Araneo Limited 232A Left Bank 116 Cuba Street Wellington 6011 ph: 04 978 7350 fx: 04 978 7355 mb: 021 345 054 <http://www.araneo.net.nz/> www.araneo.net.nz --------------------------------

1 0

Re: [nznog] Xtra Mail Admin Contact Off List re White List - Reporting back
by Don Gould 15 Dec '07

15 Dec '07

This is a quick round up of my earlier post for those who are interested in these issues. It is provided for information, not to troll for a flame :) I got hold of Ted. Following a half dozen pointless emails, he confirmed today that the shared server I'm using is in the Yahoo! block list. Yahoo! run a 'voting' system that counts messages users put in to their spam folder from different locations and blocks those sites. HOW TO FIX THE PROBLEM Ted expressed that I needed to ensure that our shared service is filtering for spam, before auto forwarding, then apply to have the server block removed. http://help.yahoo.com/l/us/yahoo/mail/yahoomail/postmaster/defer.html MY CONSIDERED ISSUES Frankly I suspect that this may be pointless. I know that the shared server is used to host a number of applications that can be hacked (eg poorly written Joomla components) and used to leverage the sending of spam. I suspect that if I get it removed from the Yahoo! block list this week then I'll have to start over again next week as I do not have control over the rest of the server. I'd like to thank the person who suggested I contact Ted. I got the clear impression (and I mean 'impression') that he's as frustrated with the whole email thing as the rest of us. He referred me to many pages on the Yahoo! web site that were incomplete and did little to explain clearly how to fix these sort of problems. Frankly by the end of the week I felt very stone walled. FINAL OUTCOME / RECOMMENDATIONS You may recall the purpose of the 'auto forwarding' was to save the 27 users from having to reconfigure their client software. I have now told them that they do not have this option. They have to set up their mail client to read from the server and/or pay someone else to do it or use our web mail interface. So much for trying to same someone some hassle. We are also having ongoing problems with email messages taking time to exit Xtra's/Yahoo!'s mail system and getting delivered. I've expressed that they should change providers to a smaller firm who have a more reliable system that is not quite so subject to the load issues that a mail provider such as Yahoo! has. I'm sure it will come as no surprise that despite explaining this to the users, only 2 of the 30 users have change provider. I should have thought that 2 months free service, your own account manager and email delivered in seconds, would have been enough to entice the users to change - I was wrong. Cheers and thanks to everyone for their help, especially Ted! Merry Christmas, Don Blair Robson wrote: > I don't have a clue about whether this is true or not, but it was my > understanding that Xtra had some sort of deal with 3rd party mail > services such as http://www.smartmail.co.nz/ that exempted them from > the standard mail policies for a regular user.. (thereforn avoiding > problems like this... > > On 28/11/2007, *Brian Gibbons* <brian(a)outersite.co.nz > <mailto:brian(a)outersite.co.nz>> wrote: > > > >From: "Steve Phillips" <steve(a)focb.co.nz <mailto:steve(a)focb.co.nz>> > > I guess people have short attention spans here ;-) > > > > (Don, if you search the archives for posts from Ted Grenfell - > last one > > dated 7-12-2006, you should find his contact details) > > I think we all tried that.... > > Xtra no longer exist, they are a brand of Telecom and if you contact > Xtra(Ted) about this problem they/he will "refer" you to Yahoo who > are now > the provider of the service > > This is a bit like taking a product back to The Warehouse and being > told to > send it back to China yourself. A service company would take > ownership of > the problem. Xtra has not. > > By now I would expect an "Xtra" procedure for whitelisting a .nz server > (sorry Ted but this is a big time waster). > > Cheers > > BG > > > > ---------------------------------------------------------------------- > This e-mail message has passed virus scanning by Outersite Technology. > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz <mailto:NZNOG(a)list.waikato.ac.nz> > http://list.waikato.ac.nz/mailman/listinfo/nznog > > -- Don Gould 2/59 Peverel Street, Riccarton, Christchurch, New Zealand Phone: +64 3 348 7235 - Mobile: +64 21 114 0699 www.thinkdesignprint.co.nz

2 1

RT users in NZ
by Nathan Ward 13 Dec '07

13 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, I'm trying to convince a customer of mine that RT (Request Tracker, the ticketing system) is the way to go for ticketing for their organisation. The question has come up (as it always does for open source applications) of what the installed base in NZ is. Obviously this is hard to gauge, as there's no licensing etc. as there is for commercial solutions. So, are you using RT, or are you aware of people using RT, in anger in NZ today? (Private reply is fine) (Yep, I realise it's not hugely on topic, but an ISP list seems like it's have lots of RT users on it) - -- Nathan Ward -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.7.0 (Build 867) Charset: US-ASCII wsBVAwUBR2DSmqhXB4ariYS3AQgTPwf/QjGiQJWytZRDiN2dbVkjRn6Is9V0WMNE IpOXwnfu+1FxoFjyUIpzQKsWeALZBWbhoNBJEJgR7VNyBrmUjAdDvgW7svGFDkaI TaYm3cy4rufgxInjZpbh2Hn3nGWNzyXWtSoXA7DGaT2Xk0K3H4tqyhS6H0a+HL+T L3dfgPErxZmeoXd5vnO4rsRN61n8g0wKW24AgZYD09C8vfSM3tcSxpdRdY6KJ0dK m5vwHFXNcX3wo40r33/dYW4jwzN2ZOzOYS2qvfJuJ4Cs8tB+DePMUb//V1LyOSyV PkOKyXo5Cf9w7sVX7hd5aI8xKDoe7aqW5+vgfqkC45PkyzS2s8L5Hw== =IPrU -----END PGP SIGNATURE-----

4 3

Re: [nznog] RT users in NZ
by Ewen McNeill 12 Dec '07

12 Dec '07

In message <CE64FCF2-B49B-4A44-98B1-1DD4B81AB3BD(a)daork.net>, Nathan Ward writes: >So, are you using RT, or are you aware of people using RT, in anger in >NZ today? (Private reply is fine) I'm aware of three NZ ISPs (or ISP-like) organisations using RT for their ticketing system, at least one with moderately extensive customisations. As well as at least two other NZ organisations using RT for their internal task management.[0] My impression is that it's one of the most widely deployed open source task tracking systems outside development projects.[1] <subliminal>I'd be keen for someone to talk about ticketing systems and ticket triage/management at the Sysadmin Miniconf</subliminal> Ewen [0] I support some of these RT installs, but by no means all of them. [1] Developers tend to use Bugzilla or DebBugs or similar. Bugzilla in particular doesn't seem as nice to interact with as RT.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Dec '07

12 Dec '07

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

1 0

NZNOG 2008 - Don't forget to register!
by Jonny Martin 11 Dec '07

11 Dec '07

Hi All, The NZNOG 2008 program has been largely finalised. The PC have done a great job providing a topical program with a great line up of both international and local speakers. Highlights are our keynote speakers, Geoff Huston, Philip Smith, and Bill Manning, alongside many fresh local presenters and a number of NZNOG regulars. APNIC and Team Cymru are providing a hands-on security tutorial on the Wednesday, alongside BGP and IPv6 tutorials and the popular Sysadmin Miniconf. Some tutorials are space limited and will be filled on a first-in basis. Full program details are available at: http://conference.nznog.org/conferenceprogramme.html In addition there are several co-located meetings taking place, with REANNZ, InternetNZ, and ISPANZ all holding meetings alongside NZNOG. There are now even more good reasons for you to come on down to Dunedin for NZNOG 2008. Numbers for the conference need to be finalised soon, so please register NOW! Cheers, Jonny.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Dec '07

10 Dec '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 118.82.176.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, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.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, 203.171.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070918 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by KOrdia Ltd. - AS24324 members: 118.148.0.0/15^15-29, 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, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.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, 203.171.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071211 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] NZNOG Digest, Vol 60, Issue 6
by Tim Rowe 10 Dec '07

10 Dec '07

1 0

WLG Power Woes
by Jonathan Brewer 10 Dec '07

10 Dec '07

Hi Folks, >From the amount of up/down alerts I've seen from monitored subscriber sites in the past couple of minutes, I'd say the Wellington grid is experiencing some significant issues right now. Regards, Jonathan Brewer -------------------------------- Araneo Limited 232A Left Bank 116 Cuba Street Wellington 6011 ph: 04 978 7350 fx: 04 978 7355 mb: 021 345 054 www.araneo.net.nz <http://www.araneo.net.nz/> --------------------------------

2 1

Significant power outage in Wellington
by Simon Blake 09 Dec '07

09 Dec '07

Power to a good chunk of central Wellington went out around 3:58pm this afternoon. Seems to be between Customhouse Quay and Courtenay Place, we've seen at least these buildings down: -- Date: Mon, 10 Dec 2007 16:15:22 +1300 Subject: tentative list of power affected sites Willbank House (57 Willis St) BDO House, 99-105 Customhouse Quay Guardian Trust House (15 Willeston St) Cigna House (28-48 Mercer St) Economous Building/Hibernian House (4 Bond St) Perpetual Trust House (111-115 Customhouse Quay) Computerland House (154 Featherston St) Todd Building (95 Customhouse Quay, cnr Customhouse and Hunter) Synergy House (Queens Wharf) Optimation House (1-13 Grey St) HP Tower/Hotel Intercontinental (163-175 Featherston St) Lumley House (3-11 Hunter St) Exchange Place (5-7 Willeston St) Willeston Centre (22-28 Willeston St) NZX Centre (11 Cable St) United Building (107 Customhouse Quay) CMC Building (89 Courtenay Place) Conservation House (18-32 Manners St) Sovereign House (34 Manners Street) MSO House (19 Edward St) BNZ Trust House (50 Manners St) Axon House (1 Willeston St) NEC/Panasonic House (40 Taranaki St) Cheers Si

3 2

Re: [nznog] NZNOG '08 Talks
by Ewen McNeill 09 Dec '07

09 Dec '07

In message <eedb5d410712091222j7181d91eja34beb9c8ec64727(a)mail.gmail.com>, "Neil Fenemor" writes: >As some of you will have noticed, we're getting more of the talks confirmed >and up for NZNOG'08. However there is still a spot for you to speak. There are also still a few speaking slots at the Sysadmin Miniconf (held on the Wednesday); details here: http://nznog.miniconf.org/ (We're a little behind on the draft programme, as we're still waiting on a few speakers to provide titles/abstracts.) I'd be particularly interested in someone to speak on content distribution networks, and someone to speak on deploying IPv6-aware applications, but proposals for anything related to ISP systems administration will be gratefully received. Please email proposals and any questions to <talks08(a)nznog.miniconf.org> Ewen

1 0

NZNOG '08 Talks
by Neil Fenemor 09 Dec '07

09 Dec '07

Hi, As some of you will have noticed, we're getting more of the talks confirmed and up for NZNOG'08. However there is still a spot for you to speak. While the majority of the talks are 30 minutes, we are able to accommodate 20 minutes, or if you prefer a 5 minute lightning talk. If you're interested in talking, feel free to email myself, or the program committee on prog08(a)nznog.org For all your NZNOG'08 needs, visit http://conference.nznog.org/ Look forward to hearing from you. Cheers, neil NZNOG'08

1 0

APNIC Training - next week.
by Jonny Martin 04 Dec '07

04 Dec '07

For those of you who haven't already found out, APNIC are running training in Wellington and Auckland next week: Wellington, 11 December: http://www.apnic.net/training/registration/ 2007/register-20071211.html Auckland, 13 December: http://www.apnic.net/training/registration/ 2007/register-20071213.html Training will be the Extended Internet Resource Management Essentials (IRME), followed by a hostmaster consultation session the following morning in each location. The IRME course won't be covered at NZNOG08, so this is your chance to attend the training. This is a good course for anyone who works at an organisation that currently holds, or is looking at obtaining APNIC allocations. To those of you who think you know it all already, well I don't believe you! :). Cheers, Jonny.

1 0

New Zealand Meraki Experiences?
by Hamish MacEwan 04 Dec '07

04 Dec '07

Hi, Anyone have any experience with the Meraki wireless mesh networking system, formerly MIT's RoofNet, in the New Zealand environment that they would be prepared to share with a group interested in investigating the technology? http://meraki.com/about/ http://www.technologyreview.com/Infotech/19260/?a=f Hamish. -- http://del.icio.us/Hamish.MacEwan http://urltea.com/3jm?GoogleSharedItems

2 2

NRO Number Council election: Call for nominations
by Elly Tawhai 03 Dec '07

03 Dec '07

[Apologies for duplicates] Dear colleagues This is a call for nominations of individuals from the Asia Pacific region to serve on the NRO Number Council. As of 31 March 2008 one Asia Pacific Number Council seat will become vacant. This seat will be filled until 31 December 2009 by an individual nominated through this open call. The selection process will involve an open election to be held during the APNIC 25 Open Policy Meeting in Taipei, Taiwan on Friday 29 February 2008. The elected individual must be willing to serve an 18-month term beginning 1 April 2008. * Deadline for nominations: 24 January 2008 * Election scheduled for: 29 February 2008 There will also be an online voting facility available to APNIC members through MyAPNIC. This service will open on Wednesday 13 February 2008 and close at 09:00 UTC+8, Wednesday 27 February 2008. More information on how to cast your vote online will be available in MyAPNIC over the coming weeks. For full details on the position and how to nominate please see: http://www.apnic.net/community/nro/nc/call-nomination.html Please note that the NRO Number Council representatives now fulfil the role of ICANN's ASO Address Council. Responsibilities of NRO NC representatives are outlined in the ASO Memorandum of Understanding at: http://www.nro.net/documents/aso-mou.html With best regards APNIC Secretariat --------------------------------------------------------------------- APNIC Secretariat email: secretariat(a)apnic.net http://www.apnic.net sip: info(a)voip.apnic.net phone: +61 7 3858 3100 ---------------------------------------------------------------------

1 0

APNIC IPv6 transit exchange
by Terry Manderson 28 Nov '07

28 Nov '07

Dear NZnog Colleagues, APNIC is facilitating IPv6 adoption in the Asia Pacific region with an IPv6 Transit Exchange. This will allow APNIC to support IPv6 and at the same time expand IPv6 awareness, use, and understanding of IPv6 in the Asia Pacific region. The IPv6 Transit Exchange is a Reasearch and Development effort and will continue to run for as long the participants require the service, however a horizon may be set when commercial providers offer native IPv6 services in a commercial relationship. APNIC will additionally advertise prefixes and negotiate peers for both 2byte and 4byte Autonomous System numbers (AS) to ipv6 neighbors of this service. The preference for the IPv6 exchange is that is an MLPA style service. That is, we will re-advertise all routes presented to us. And the more routes you are willing to advertise the better! As such, any organisations willing to offer full transit will be greatly appreciated. Any organisation with an IPv6 prefix is welcome, and encouraged to join. Please see the following link for more information: [http://icons.apnic.net/index.php? option=com_content&task=view&id=3432&Itemid=94] Cheers, Terry -- Terry Manderson email: terry(a)apnic.net Network Operations Manager, APNIC sip: info(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3100

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Nov '07

28 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES: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 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.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.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, 202.146.186.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 20071129 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 28 Nov '07

28 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES: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 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.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.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, 202.146.186.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 20071129 source: NZRR ------------------------------------------------------------

1 0

Xtra Mail Admin Contact Off List re White List
by Don Gould 27 Nov '07

27 Nov '07

If any one knows how I get babyonthemove.co.nz white listed with Xtra's email system could they please contact me. At present the 25 franchises who have broadband accounts with Xtra are finding that email forwarded to their @xtra.co.nz account is going missing. We have set up their addresses so that the email is forwarded automatically to their relivant xtra account. If others have tried this sort of thing and discovered that you just can't do it this way then I'd like to know. eg. east.chch(a)babyonthemove.co.nz --> whatever(a)xtra.co.nz west.chch(a)babyonthemove.co.nz --> whoever(a)xtra.co.nz We did this because we didn't want to have to explain to each franchise holder how to set up Outlook or Thunderbird to retrieve mail from the the babyonthemove.co.nz mail server. WHY THIS LIST/NOT THIS LIST PLEASE! I've already rung level 1 support. The first person I spoke to told me "you're not with us", after she's asked me for my phone number, despite my explaining who I was and why I was calling. To her credit she did not cut me off, she put me through to a broadband helpdesk person who did not know what a 'white list' was. He also didn't cut me off, and put me though to a person who did at least know what a white list is. He referred me to http://xtra.co.nz/help/0,,4155-7793692,00.html which referred me to http://help.yahoo.com/l/us/yahoo/mail/yahoomail/postmaster/bulk.html which I filled out. It then sent me a 1200 word email about spam. That was the point I felt I'd read enough, talked to enough people who were clearly not in control of the situation and wanted to speak to a person who has actually been through this process and can tell me if I'm chasing my tail or actually in the right direction. Or, do I have to simply bite the bullet and make everyone set up mail readers? Cheers Don -- Don Gould 2/59 Peverel Street, Riccarton, Christchurch, New Zealand Phone: +64 3 348 7235 - Mobile: +64 21 114 0699 www.thinkdesignprint.co.nz

6 7

Small interruptions to APE at L48 Sky Tower over the next week
by Simon Blake 27 Nov '07

27 Nov '07

Hi all Most affected parties should already be aware, but I'll repeat it here in case the change control messages didn't get to the right people - we're replacing gear on L48 over the next week. Between 12:01 and 6:00 on Thursday 28 through Dec 5, (excluding Saturday and Sunday morning), there will likely be short interruptions to every connection to the Citylink cabinet on L48. More info at http://news.clnz.net/2007/11/16#Level-48-Sky-Tower-Project Cheers Simon

2 2

NZRR Route Registry Update
by NZRR Database Notifications 27 Nov '07

27 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.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 20071108 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, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071128 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Nov '07

27 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.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 20071108 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, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.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 20071128 source: NZRR ------------------------------------------------------------

1 0

APNIC 25 Call for Proposals
by Elly Tawhai 25 Nov '07

25 Nov '07

APNIC 25 25 February - 29 February 2008 Howard Plaza Hotel Taipei, Taiwan Dear colleagues Special Interest Groups (SIGs) will be held at the 25th APNIC Open Policy Meeting. We invite you to submit proposal presentations for these sessions. There are two types of presentations: - Policy proposal (P) A proposal which requires feedback and community consensus before it can proceed. - Informational (I) Typically a status report delivered to convey information to the audience. Informational presentations may be presented in SIG sessions. * Submitting policy proposals To submit a policy proposal before the 28 January 2008 deadline, you have two options: 1. Use the online form at: http://www.apnic.net/cgi-bin/policy_proposal.pl 2. Send your proposal in TEXT format to the appropriate SIG Chair, CCing <sig(a)apnic.net>. * Submitting informational proposals Send your proposal in TEXT format to <program(a)apnic.net>, preferably before 28 January 2008. Agenda slots will be allocated on a first-come first-served basis, so it is advisable to submit your proposal as soon as possible. More information ---------------- SIG archives and guidelines for presenters are available at: http://www.apnic.net/meetings/archive/sigs/ SIG chairs can be contacted at: * Policy SIG <sig-policy-chair(a)apnic.net> * Database SIG <sig-db-chair(a)apnic.net> * DNS operations SIG <sig-dns-chair(a)apnic.net> * IPv6 technical SIG <sig-ipv6-chair(a)apnic.net> * IX SIG <sig-ix-chair(a)apnic.net> * NIR SIG <sig-nir-chair(a)apnic.net> * Routing SIG <sig-routing-chair(a)apnic.net> We look forward to seeing you in Taipei! Kind regards, Elly ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

An explanation of what went wrong at Mayoral Drive on 4/11
by Matthew Poole 21 Nov '07

21 Nov '07

ComputerWorld article. http://s0.tx.co.nz/at/tep34n279457j138688i194855f2c4680224a4t9s4z During testing a UPS failed to start a generator, then its batteries went flat and the systems it was feeding had to be restarted. Fire and Police were hit hard because they'd only very recently consolidated to a single database from three region-based ones, and hadn't had a DR drill (one was planned) so it was the first time they'd actually done a cut-over. That sod Murphy strikes again! -- Matthew Poole "Don't use force. Get a bigger hammer."

9 14

Re: [nznog] An explanation of what went wrong at Mayoral Drive on 4/11
by Russell Sharpe 20 Nov '07

20 Nov '07

I agree with you on that as well as my comments Peter :| -----Original Message----- From: Peter Mott [mailto:peter(a)mott.co.nz] Sent: Wednesday, 21 November 2007 20:02 To: Russell Sharpe Cc: 'NZNOG' Subject: Re: [nznog] An explanation of what went wrong at Mayoral Drive on 4/11 On 21/11/2007, at 7:45 PM, Russell Sharpe wrote: > IMHO. This type of incident enforces my feeling that some providers > are only interested in profits, not customer service. :( and a gross > lack of investment More likely due to a lack of ... * personal ownership of having it stay going * basic problem solving skills * understanding of how it works * consequences for when you screw up Blame management if you want, but I would start with parents and schools. Time for a beer. regards Peter Mott -/-

1 0

Re: [nznog] An explanation of what went wrong at Mayoral Drive on
by Stewart Fleming 20 Nov '07

20 Nov '07

> -----Original Message----- > From: nznog-request(a)list.waikato.ac.nz > [mailto:nznog-request(a)list.waikato.ac.nz] > Sent: Wednesday, 21 November 2007 12:00 p.m. > Message: 2 > Date: Wed, 21 Nov 2007 09:38:51 +1300 (NZDT) > From: Matthew Poole <matt(a)p00le.net> > Subject: [nznog] An explanation of what went wrong at Mayoral Drive on > 4/11 > To: NZNOG <nznog(a)list.waikato.ac.nz> > Message-ID: <Pine.LNX.4.62.0711210935340.8793(a)maverick.blakjak.net> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > ComputerWorld article. > http://s0.tx.co.nz/at/tep34n279457j138688i194855f2c4680224a4t9s4z > > During testing a UPS failed to start a generator, then its > batteries went flat and the systems it was feeding had to be > restarted. Interesting that there was a similar power-related failure of emergency systems in the South Island a few days after this incident. And that a similar incident occurred at the Telecom Dunedin exchange about 6 months ago (UPS test, generator started, sparked, caused a fire, fire happened to be in same room as mains cutover switch...UPS ran flat.)

1 0

NZNOG 2008 registrations are up/up
by Jonny Martin 20 Nov '07

20 Nov '07

The NZNOG 2008 website is up and registrations are now open. http://conference.nznog.org Hope you can make it to Dunedin, Jan 23-25 2008! Cheers, Jonny.

3 2

Re: [nznog] An explanation of what went wrong at Mayoral Drive on 4/11
by Matthew Poole 20 Nov '07

20 Nov '07

On Wed, 21 Nov 2007, Jeremy Strachan wrote: > > "during testing" means someone must have been onsite - to check the > generator started?? > > or are the dumb enough not to do that ... because of staff cuts ... > Who know? One would HOPE that they'd have engineers on-site for testing of critical components. Still, this is far more of an explanation that I'd ever expected to be given! -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Nov '07

19 Nov '07

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

1 0

Security alert - http://www.bugmenot.com/ offering username/passwords online
by Paul England 12 Nov '07

12 Nov '07

Hi everyone, I just thought I'd share this with everyone as we recently found that some of our domains were on this website... It's the first website of it's kind that I've ever come across and personally I'm concerned that it's going to grow in popularity. There is an automated system to allow systems admins to block their domains from this website... definitely worth doing. Cheers - Paul England

9 13

NZRR Route Registry Update
by NZRR Database Notifications 12 Nov '07

12 Nov '07

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Nov '07

12 Nov '07

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Nov '07

07 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-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, 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.36.218.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 20071024 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, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.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 20071108 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Nov '07

07 Nov '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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, 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.36.218.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 20071024 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, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.218.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 20071108 source: NZRR ------------------------------------------------------------

1 0

InternetNZ launches public consultation on Internet peering
by Dean Pemberton 07 Nov '07

07 Nov '07

Hi all. InternetNZ is asking for public consultation on Internet Peering. There are a number of interesting things in this email, my apologies for its length. The first is the InternetNZ Peering Report which can be downloaded at http://peering.internetnz.net.nz/wp-content/uploads/2007/11/issues-regardin… And the second are the 8 questions which InternetNZ is asking for submissions on. People are welcome to send in their own submissions, and if the discussion is within the AUP then feel free to voice them here too. I look forward to the discussion. =) I've included the original RTF document as text below inline with the list rules. Dean -------- Original Message -------- InternetNZ launches public consultation on Internet peering For immediate release 7 November 2007 InternetNZ (the Internet Society of New Zealand Inc) today launches a public consultation on Internet peering, a subject that relates to the performance and reliability of the Internet. This follows the release of a report commissioned by the Society entitled “Issues regarding Internet peering and interconnection in New Zealand”. Some key issues identified in the report include conflicting interpretations of the term peering, cost of transit, lack of reliable internet traffic data and statistics and the challenges faced by content providers InternetNZ invites comments on any issues presented in the report and what further steps should be considered in progressing peering and data interconnection issues in New Zealand. A consultation document is attached and submissions have been invited either by email in response to that document, or at the website http://peering.internetnz.net.nz, where comments can be attached to the individual questions. The mission of InternetNZ is to protect and promote the Internet in New Zealand. InternetNZ is a public policy advocate for Internet and telecommunications issues that further an open and uncaptureable Internet. InternetNZ promotes neutral peering and neutral peering exchanges on the basis that it provides diversity for the Internet network and assists in improving network performance. For further information contact: Richard Wood Communications and Research Officer InternetNZ richard(a)internetnz.net.nz 0274 974 837 ----------Attachment------- InternetNZ Invites Comment on Peering Consultation Document - 7 November 2007 ------------------------------------------------- InternetNZ (the Internet Society of New Zealand Inc) has commissioned a report "Issues regarding Internet peering and interconnection in New Zealand", which examines the state of peering and related issues in New Zealand. The report can be found here: http://peering.internetnz.net.nz/wp-content/uploads/2007/11/issues- regarding-internet-peering-and-interconnection-in-new-zealand-099.pdf InternetNZ invites comments on any issues presented in the report and what further steps should be considered in progressing peering and data interconnection issues in New Zealand. Submissions must be received by 5pm, Friday 7 December. InternetNZ is also inviting comments and discussion online at the website http://peering.internetnz.net.nz Background --------------- The mission of InternetNZ is to protect and promote the Internet in New Zealand. InternetNZ is a public policy advocate for Internet and telecommunications issues that further an open and uncaptureable Internet. InternetNZ promotes neutral peering and neutral peering exchanges on the basis that it provides diversity for the Internet network and assists in improving network performance. In March 2008 InternetNZ commissioned an external working group chaired by Dr Murray Milner to undertake a wide ranging industry consultation on peering and related issues. The terms of reference were as follows; • To facilitate industry discussion on issues relating to Internet peering in New Zealand inclusive of all interested and affected stakeholders and in a collaborative fashion. • To establish policies and principles that will expedite an industry-wide agreement on peering and local interconnection of data. The findings and recommendations contained in "Issues regarding Internet peering and interconnection in New Zealand" do not represent InternetNZ policy but are designed to provide a framework for a wider industry debate on peering and data connection issues. Following the public consultation process, InternetNZ will publish a final report that will incorporate feedback from public submissions To assist the feedback process, outlined below are a list of specific questions based on the findings and recommendations raised in the report Questions ------------ 1. Peering: Interpretation and Definition The term peering is open to many interpretations. The report identifies the differences in what is meant by the word "peering" and says that emotive responses flowing from historical events can be overcome by defining as far as possible what peering means. Do you agree with definition of peering that is proposed in the report. If not, what would be more appropriate? 2. Cost of Transit International benchmarking suggests the cost of transit is relatively high in New Zealand. Do you agree? Specifically, is there a market failure or evidence of SMP (significant market power) with regard to the cost of transit? Should government conduct an investigation regarding the price of transit? And finally should Government regulate the price of transit? 3. The state of networking - lack of reliable data The report highlights the difficulty in having any informed debate about the state of networking in relation to local, national and international data interconnection in New Zealand, without access to reliable Internet traffic data and statistics. Do you support the need for an initiative that would collect and make available on an aggregated basis, New Zealand Internet traffic flows and volumes? If so who should collect that data? Specifically; the Telecommunication Carrier's Forum, Commerce Commission, Ministry of Economic Development, InternetNZ, or other? 4. Rich Media Content Distribution The report identifies the challenges faced by content providers, particularly the distribution of audio and video files. What initiatives with regards to peering and data interconnection would assist the growth and viability of the NZ digital content industry? 5. Consumer Pricing Strategies The report suggests consumer pricing strategies that differentiate between national and international traffic might encourage a greater take-up of New Zealand-sourced content. Do you agree? 6. Telecom Local Peering Proposal The report has noted a significant industry development with regards to Telecom's Local Peering Proposal, which has been the subject of industry discussions since April 2007. Do you support the proposals put forward in Telecom's local peering initiative? 7. Peering Code of Practice The report is neutral at this time on whether a Peering Code of Practice could be a useful mechanism to progress industry cooperation on peering and data connection issues. Do you support the need for a specific self regulatory industry initiative such as a Code of Practice to manage and develop consensus on peering and data connection issues? Failing that, should Government consider some form of regulation? 8. Other Please comment on any other issues in the report that you feel are not covered by the above questions. ------------ Please forward submissions to richard(a)internetnz.net.nz. InternetNZ will publish all submissions on its website at www.internetnz.net.nz and considers you have consented to this by filing your submission

1 0

Spam & NZ Anti Spam law issues.
by Skip Parker 05 Nov '07

05 Nov '07

Hi, I hope this email is not too far off List Topic, however i have a question that I would like some feedback for from NZ ISP's. (I believe its been raised before) A number of my customers run Email List Services which sends out various messages to a subscribed customer base (compliant with the NZ Anti Spam Laws etc). The issue we have is that while we have done ALL we can to adhere to good internet etiquette, we seem to be loosing the battle to send legitimate emails to our customers. In the last month ive been discussing these issues with many ISP's and the range of responses are "Sure heres how you can make it work" to "Go Away we dont want to deal with this". What I'm wondering is this. If we setup a whitelist service that had a set of guidelines, would ISP's look at adopting it in their Firewall/Spam filtering services. Some guidelines for such a service would be: - New Zealand Based List Servers Only - New Zealand Anti Spam law compliant - Correct DNS and Fixed IP Address configured - Agreed Email Delivery Speeds (i.e x number of messages per hour) - Agreed Email Volumes (i.e x number of bulk message sent per day) - Server/Service Administrator Details registered for contacting etc - Security Compliance etc.. Keen to hear any feedback and suggestions. I think i speak for a number of content providers when i say that we want to work with ISP's and provide a service that works for both our Customers and you guys as ISP's. Skip Parker skip(a)ignition.net.nz

9 11

BBBZZZZZTTTT: Where did all the lights go?
by Dean Pemberton 04 Nov '07

04 Nov '07

Anyone get effected by the Telecom power outage? Dean

8 9

[Apnic-announce] APNIC additional IPv4 address blocks
by Elly Tawhai 01 Nov '07

01 Nov '07

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

1 0

Re: [nznog] The day the routers died
by Scott Weeks 31 Oct '07

31 Oct '07

Once, back when I was working on a global network, myself, some folks from Europe and some folks from your part of the world were all working on a big problem together and I kept hearing the guys from your part of the world snicker every time the Europe guys said 'rooter'. Being from Hawaii, I didn't get it. Later, it was explained to me. Now every time I hear the Europe guys say 'rooter' I laugh and everyone now looks at me strangely. ;-) scott --- danclarknz(a)gmail.com wrote: haha the 'Rooter' ;-) --------------------------------- On 11/1/07, Philip D'Ath <pid(a)ifm.net.nz> wrote: > > Not on topic, I know, but this is very entertaining and will appeal to > people on this group. > > http://www.youtube.com/watch?v=_y36fG2Oba0

1 0

IPv6 tunnel appliance beta testers wanted
by Nathan Ward 31 Oct '07

31 Oct '07

Righty, As many of you know, I've been working on building some little tunnelling appliances to push IPv6 over IPv4 using well known protocols (6to4 and Teredo). Both 6to4 and Teredo benefit from having relays in as many places as possible. Cisco currently supports 6to4. I'm not sure if anyone else does. Noone supports Teredo. With both 6to4 and Teredo being built in and enabled by default on Vista (and enable-able on XP SP2), the amount of tunnelled IPv6 traffic on the Internet is increasing. I recently posted on the v6ops IETF mailing list about Azureus's support for IPv6 - when I use this client, over half of my DHT peers are IPv6 peers, and 99% of them were over tunnelled IPv6, either with 6to4 or Teredo. So, in light of this, I've put together a small FreeBSD based image for Soekris hardware. This does Teredo and 6to4, and also BGP. It does some funky tricks to hook all of these boxes together, tunnelling over IPv4. So, you get interconnection with many other networks over IPv4 best paths and existing IPv4 transit. I'm also expecting to be able to get you on to the v6IX (Citylink's IPv6 peering) as well if you (or your transit provider) are an existing IPv4 peer at APE or WIX. This software will be freely available when it's ready. Here's the best bit: Thanks to InternetNZ, I'll soon have have 6 boxes to do a live test of the code, and hopefully more down the line when it's ready to go for real. So, I'm looking for people who are running networks that fit one (or more) of the following: - Large numbers of end users - Lots of content on IPv6 (yeah, I'm dreaming) - Universities (or other large private networks) It doesn't matter if you have some IPv6 deployed, or if you only have IPv4 deployed, or if you haven't even thought about IPv6 deployment yet. What I need from you: - A shelf somewhere, and an IEC C13 (a.k.a. jug plug) cable/outlet. - An IPv4 address or two. - A 10/100 ethernet port (or two if you're keen on resiliency). - The ability to statically route a couple of IPv4 addresses at your box. - Also useful (but not necessary!) is an IPv6 allocation, and some form of transit internationally (a free IPv6 tunnel from somewhere overseas is fine- native transit isn't required) What you get: - 6to4 relay - Teredo relay - IPv6 interconnection to other people with these boxes Impacts: - If it breaks, you might end up with customer IPv6 traffic being impacted. (ie. not that much impact at all, right now) I'm working right now on some deployment pictures and all that noise, so there's more info coming. Please let me know if you're interested, or if you're interested but have some concerns, or, whatever. I'm wanting to get boxes in fairly soon - ie. before xmas brownouts. Integration is pretty minimal if you have an IPv4 network - plug in and point a route or two. It's only slightly more if you have an IPv6 network. Cheers! -- Nathan Ward Braintrust Ltd.

1 0

The day the routers died
by Philip D'Ath 31 Oct '07

31 Oct '07

Not on topic, I know, but this is very entertaining and will appeal to people on this group. http://www.youtube.com/watch?v=_y36fG2Oba0

3 2

[nznog-owner@list.waikato.ac.nz: Re: DNS lookup false positives with: com.co.nz > 208.73.212.12 > information.com]
by Richard Haakma 29 Oct '07

29 Oct '07

On Tue, Oct 30, 2007 at 09:43:32AM +1300, Paul Adshead wrote: > Are any others being affected by the fools who have registered "com.co.nz"? > > It's been setup as a 'catch all' search engine, for the 'append parent DNS > suffix' queries. So a lookup on "abcd.com" that should fail, comes back > successful from "abcd.com.co.nz"... :-( I add a line search . in /etc/resolv.conf in my mail servers to fix this sort of stuff. All email addresses should be fully qualified. Regards, RH.

1 0

DNS lookup false positives with: com.co.nz > 208.73.212.12 > information.com
by Paul Adshead 29 Oct '07

29 Oct '07

Are any others being affected by the fools who have registered "com.co.nz"? It's been setup as a 'catch all' search engine, for the 'append parent DNS suffix' queries. So a lookup on "abcd.com" that should fail, comes back successful from "abcd.com.co.nz"... :-(

4 3

114/8 and 115/8 allocated to APNIC
by Leo Vegoda 28 Oct '07

28 Oct '07

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in October 2007: 144/8 and 115/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 Manager, Number Resources - IANA

1 1

NZRR Route Registry Update
by NZRR Database Notifications 28 Oct '07

28 Oct '07

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

1 0

Youtube in NZ?
by Joel van Velden 25 Oct '07

25 Oct '07

Does anyone know anything about todays launch of a New Zealand portal on Youtube and in particular talk of a local youtube server? -Joel

3 2