January 2008 - NZNOG - lists.nznog.org

list.waikato.ac.nz Has Moved
by Donald Neal 11 Dec '24

11 Dec '24

NZNOG-People, I have just finished migrating all of the mailing lists held at The University of Waikato from one server to another. I don't have any reason to believe that anything's gone wrong, but please bear with me for today if it turns out that something has. - Donald Neal -- Donald Neal | Q: How many Aucklanders does it take to change Systems Programmer/Analyst | a light bulb? The University of Waikato | A: Pass me that candle and I'll tell you. Hamilton, New Zealand | --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

RE: Sort of OT: are there any "Internet enabled" temperature sens ors/servers for Auckland?
by Greg Clare 18 Aug '21

18 Aug '21

May not be exactly what you are after? However DSE have an Internet weather station at the Albany HQ. http://www.dse.gen.nz/public/webdata/weather.htm Regards Greg > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Wednesday, 2 January 2002 2:47 pm > To: NZNOG > Subject: Sort of OT: are there any "Internet enabled" temperature > sensors/servers for Auckland? > > > Measuring the outside temperature, with geographic location given. > > -- > Juha > Take off every sig! > > - > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Charging for IPv6
by Philip D'Ath 24 Aug '08

24 Aug '08

Initially those transit providers and ISPs that do offer IPv6 transit will be able to charge for this service as it will be a premium value add. However I can't see this business model being able to last for more than 6 years (through to 2012), and possibly only three years. After this point in time I expect IPv6 deployment will be standard, and will no longer be a premium service offering - it will be the standard offering, like IPv4 is today. Once IPv4 has become exhausted and you can't actually give a customer an IPv4 address then you definitely wont be able to charge more for IPv6 - otherwise the customer will walk. So do providers start implementing slowly now, and recoup some of their investment while they can, or wait till they are forced to do the upgrades and are not able to recoup any of their "new" investment. Rhetorical question.

23 40

.co.nz Domains
by bigalownz 29 Mar '08

29 Mar '08

can someone tell me why .co.nz domains are the most expensive domains ? where as most are about $6 - $15 but .co.nz are $30 - 60 and even $100 thanks

13 15

Using nolisting to reduce spam
by Glen Eustace 19 Feb '08

19 Feb '08

Yesterday, I came across the concept of 'nolisting' as a technique for reducing the volume of inbound spam. It wasn't something I had previously come across so have done some reading on the topic. http://nolisting.org as a starting point. For such a simple technique, I was surprised by its impact. Simply speaking, the idea is to use a primary MX that doesn't listen on port 25 but simply rejects the connection. Well behaved MTAs will all try the secondary MX(es) and delivery will occur. Many spambots only try the primary so there is an immediately benefit, less inbound to check in other ways and a consequential increase in the available resources on the mail server(s). I set it up on one domain and behavior seems to be exactly as described. My reading suggests that there is no negative impact on legitimate mail and no noticeable additional latency in delivery as the switch from the primary to secondary on a reject is almost instantaneous. I was wondering whether anyone else has had any experience with this technique and if so whether the claim that it has no negative impact is true. Also, if people haven't heard of it, it may be something people might want to look at as another weapon in the anti-spam war. Glen.

18 24

CDNs in NZ?
by Simon Lyall 03 Feb '08

03 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

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