- NZNOG - lists.nznog.org

Fibre Optic / Laser Safety with Single Mode Fibre
by Mark Foster 25 Jul '06

25 Jul '06

G'day guys, Have been doing a bit of research in the area of Laser Safety, we're looking at buying some new continuity-type testers for fibre (Model is OVF-1 Visible Fault Locator, as I gather it - A google gave me http://www.butlertech.ie/products/pdfs/ovf1.pdf) and one issue that was raised was that of safety when looking down a fibre line. Especially given that some of our newer technicians particularly, are OK with networking hardware but have relatively low levels of experience with Fibre. So in the interests of safety and best practise i'm looking at what kit we should have to safely troubleshoot fibre runs at a basic level (eg, validate continuity of a fibre run / clearly identify what goes where. Not talking full fibre loss analysis or anything at this stage - initial solution is for our computer techs, not our cabling specialists.). Multimode stuff is less of an issue, being LED driven, but Single Mode is a different can of worms, especially given that its often outside the visible spectrum. What do the players on here use? Laser filter goggles or somesuch I presume? Any brands or types reccomended / preferred? Of course due care should be taken to make sure theres no active laser emmitters on the other end of the feed, but beyond that, nice to be protected. Recommendations from the floor? Cheers Mark. (All thoughts/comments are in my personal opinion, this is largely a personal enquiry i'm making off my own bat, out of interest...)

6 6

Xtra filter email with blank From, To or Subject
by Dave Green 25 Jul '06

25 Jul '06

I started having problems some weeks back with Xtra mailboxes not receiving mail from a number of lists that we send. After a bit of troubleshooting our end, a query to Xtra helpdesk revealed that they now filter emails that have a blank Mail From, To or Subject field (our lists have never had a from address and our email server appears to not have the facility to add one, which kinda makes it my problem but ...). Xtra said: "We have implemented a rule on our Xtra Email Servers requiring at a minimum of a From email address, To email address, and a subject to be displayed to prevent this form of Spam. If all of these are enterred into the email this will ensure continued delivery of the automated emails. The Anti-Spam filter works by checking the content and style of email content. These blank emails have hidden content in the body that appears legitimate to the Anti-Spam filter and are passed." Not sure if this is news or not, but I hadn't seen anything publicised re this change. My understanding was that blank "from" fields are valid, so filtering this type of email may break other things such as read receipts. Has this been a problem for anyone else out there? Dave

4 4

Re: [nznog] Telecom FaxRight
by Ian Batterbee 25 Jul '06

25 Jul '06

> Date: Wed, 26 Jul 2006 08:55:56 +1200 > From: Kenneth Wells <Kenneth.Wells(a)equinox.co.nz> > Subject: Re: [nznog] Telecom FaxRight > To: nznog(a)list.waikato.ac.nz > Message-ID: <E1F0BFE34657D211AF41006094B978960133AD49(a)MOON> > Content-Type: text/plain > > TelstraClear's "FaxCheck" was still operational last time I checked - > 0508500499 - give that a go. > > Regards, > Kenneth Wells Thanks :) Much appreciated.

1 0

Re: [nznog] Telecom FaxRight
by Kenneth Wells 25 Jul '06

25 Jul '06

TelstraClear's "FaxCheck" was still operational last time I checked - 0508500499 - give that a go. Regards, Kenneth Wells -----Original Message----- From: Antonio Broughton [mailto:anacarda(a)flerwin.net] Sent: Tuesday, 25 July 2006 8:29 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Telecom FaxRight Ian Batterbee wrote: > Does anyone know what happened to Telecom's Faxright service which I'm > pretty sure used to be 0800 108 208 ?. It gives number disconnected at > the moment.. I'm not sure if I have the number wrong or if it has been > shut down. > > yea, it was shutdown i think last month? or something this month... they had a heading about the closure for a cpl months before hand... we are thinking of making a similar one in asterisk for ourselves :P -- Antonio Broughton _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Telecom FaxRight
by Ian Batterbee 24 Jul '06

24 Jul '06

Does anyone know what happened to Telecom's Faxright service which I'm pretty sure used to be 0800 108 208 ?. It gives number disconnected at the moment.. I'm not sure if I have the number wrong or if it has been shut down.

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060629 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060725 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060629 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060725 source: NZRR

1 0

Re: [nznog] SMTP Server Callbacks, the Devil or a Godsend?
by Ewen McNeill 24 Jul '06

24 Jul '06

In message <040c01c6af00$812193c0$de0dea3c(a)office.orcon.net.nz>, "Craig Whitmore" writes: >I have been looking into callbacks lately for SMTP (to reduce spam) and have >noticed a few things with a number of large nz sites who send out email. This is the scheme where upon receiving an inbound MAIL FROM:/RCPT TO: the mail server then connects back to the MX for the claimed domain and issues a MAIL FROM:/RCPT TO: as if it were going to send a reply? I'm pretty wary of such schemes because of the potential for looping (eg, A connects to B, B connects to A to verify, A connects to B to verify, ...), and because the "callback" action looks pretty much like an address verification probe for, eg, a spam list. (Once upon a time SMTP had a VRFY action which could be used to confirm addresses, but pretty much everyone turns that off due to abuse.) Aside from that some way of being sure the originator is a "real" address, preferably without requiring a separate connection, is a nice idea. One scheme I've seen a fairly large mail source (Yahoo? AOL? I forget) was to test for postmaster(a)domain instead, on the basis that the address should exist and at least they'd have somewhere to send reports of problems. That seems marginally less bad than trying the originator of the message. >A number of sites send from email addresses which don't exist. Including some newsletter mailouts that I'm aware of. Your (Craig's) list is by no means complete. Personally I'd be reasonable keen to see such mail refused as a general industry policy. Because they inevitably seem to send out (regularly) to large numbers of addresses which ceased to exist a long time ago, or never existed (hotmale.com, anyone?). The ones with valid sender addresses which have, eg, full mailboxse are only marginally less annoying. Especially given that automatic bounce processing systems have existed for a long time. I think using some sort of sender address verification scheme and then papering over it with a whitelist to allow those that fail to still send mail rather misses the point. But then I also think that email is virtually a lost cause these days, at least in the "anyone can forge anything" SMTP form. Ewen

2 1

Spectrum Allocations for Broadband Wireless Access Discussion (with refreshments!)
by Jonathan Brewer 24 Jul '06

24 Jul '06

Hi Folks, InternetNZ have kindly arranged for a neutral venue, webcasting, and refreshments to be provided for a discussion of Spectrum Allocations for Broadband Wireless Access. This discussion is to take place ***Thursday, 27 July*** at InternetNZ, 10th floor meeting room, 5-6:30PM. It will be an informal but structured discussion that will cover the main points of the paper. I think all of our responses will benefit by talking things through over a liquid refreshment or two. Important links: The discussion paper: http://www.rsm.govt.nz/spp/bwa/discussion/index.html InternetNZ location: http://www.internetnz.net.nz/about/contact/ Thursday Night Curry: http://wellington.thursdaynightcurry.com/ (discussion will continue here) Please feel free to contact me or Nick Wallingford of InternetNZ [nickw(a)internetnz.net.nz] if you have any questions. Best Regards, Jonathan Brewer ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS38178 as-name: NZRR-AS38178 descr: e-cast descr: APE peering at '192.203.154.31' descr: see Citylink RT job #6482 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38178 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: brian(a)e-cast.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS38178 descr: Route set advertised to AS9560 by e-cast - AS38178 members: 202.36.36.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(a)e-cast.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR

1 0

SPF record Errors
by Craig Whitmore 23 Jul '06

23 Jul '06

I have compiled a list of Domains which have "Broken SPF Records". These are domains which have SPF records which are invalid due to a number of reasons (explained on the website). This is not a complete record, but a large number of them. The RFC (RFC 4408) says if a SPF record is invalid (and a Mail Server is properly checking for them) then it is valid to reject email from that Domain completely (something which most people won't want on a Domain) Please note there is a LOT of domains listed which have "v=spf2.0 ... etc" which isn't a SPF nor Sender-ID record, and people should fix them up or delete them as they do nothing. Please See: http://spam.co.nz/spf/broken/. There is a number of .nz and NZ related Domains on this list so if you have any relationship with them, you might want to get them fixed. More and More large companies in NZ have correct SPF records (Xtra,Trademe,ICONZ,Datacom) Thanks Craig Whitmore http://www.spam.co.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Jul '06

23 Jul '06

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

1 0

WDANZ and Brendan Battles
by Justin Cook 20 Jul '06

20 Jul '06

Hello everyone. Apologies for interrupting your usual off-topic banter, but I'd like to take a moment to talk about something I experienced today. I've promised Dennis from the WDANZ that I would share this experience with other people in the industry. Today the noted spammer Brendan Battles called, despite being asked in the past not to contact me. Brendan was trying to solicit membership to the WDANZ. Again. This is the fourth call I've had from them about it, and it's getting old. After explaining to Brendan that since finding out it was a for-profit organisation rather than a community that I wasn't interested, he proceeded to tell me in an obnoxious tone that he "didn't like my attitude". I told him what I thought of his sales approach and rung off. A few minutes later he called again to blow me a torrent of abuse and I was forced to reiterate my desire not to be contacted. Boy Brendan, your cold-calling is pretty hot. Although I can't confirm the veracity of what the WDANZ is trying to provide to our industry I can only start to guess how ineffective this marketing campaign will be with the rest of you. Unfortunately I've been unable to finger a single service I want from the WDANZ as their offerings seem quite slim, it would appear that their approach is one where the marketing effort outstrips the services delivered. Very disappointing. Also if anyone else has experienced out-of-the-blue abusive phone calls from Brendan Battles please feel free to email me and let off some steam. God knows we can probably have a good laugh. Cheers Justin -- *Justin Cook* Developer http://www.skull.co.nz/ *Skype* justincookskull <skype:justincookskull?call> My status <skype:justincookskull?call>

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 20 Jul '06

20 Jul '06

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

1 0

Telstraclear funkiness
by neil gardner 20 Jul '06

20 Jul '06

Sorry guys, I couldn't resist this... http://networkstatus.telstraclear.co.nz Throws up an error... For a split second I see the real screen behind it with stuff in yellw (not so good), but yes, the Telstraclear status website is borked... Borked in a funny way too... Since I'm sure their phone lines will be clogged (They "experience heavy call volumes" even when nothing's wrong) can anyone here shed some lilght on the issue please? Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesis Labs Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesis Labs.

2 1

121.72.0.0/15 - outdated bogon lists
by David Robb 20 Jul '06

20 Jul '06

TelstraClear has recently been allocated 121.72.0.0/15 by APNIC. I'm aware that this range used to be covered by some bogon filters, so can I ask that people please check their bogon lists are up to date, or better yet make use of the BGP fed bogon list from the nice folks at cymru. Thanks, David

4 3

UCE from Catmail Auckland.
by Mark Karena 19 Jul '06

19 Jul '06

F.Y.I Thanks, -------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING +64 7 853 6060 http://www.enlightenhosting.com <http://www.enlightenhosting.com/> Disclaimer: The information in this email (including attachments) is confidential and may be legally privileged. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email and destroy the message. If you are not the intended recipient, any use, disclosure, copying or distribution is prohibited and may be unlawful. _____ Received: from fep05.xtra.co.nz by mail.enlightenhosting.com (mail.enlightenhosting.com v5.5) with SMTP id HRQ38575 for <admin(a)enlightenhosting.com>; Thu, 20 Jul 2006 15:10:52 +1200 Received: from catserver ([219.89.206.1]) by fep05.xtra.co.nz with ESMTP id <20060720031047.FNTQ19334.fep05.xtra.co.nz(a)catserver> for <admin(a)enlightenhosting.com>; Thu, 20 Jul 2006 15:10:47 +1200 Reply-To: <brendon(a)catmail.co.nz> From: "CATMail - Brendon Udy" <brendon(a)catmail.co.nz> To: <admin(a)enlightenhosting.com> Subject: CATMail - Email Initiatives for Advertisers Date: Thu, 20 Jul 2006 15:11:31 +1200 Organization: CATMail Ltd Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAADOM8t4+jDZJsX/MLB34QHEBAJwBFoy83khLhWqks3sVUMkAAAAB KRAAABAAAAB9b7c91cI0T7OB31wgaXYAAQAAAAA=(a)catmail.co.nz> MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_0042_01C6AC0E.C8683530" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 thread-index: AcarqjLIVWeCIiH/R4O9//2WiwOyyg== Disposition-Notification-To: "CATMail - Brendon Udy" <brendon(a)catmail.co.nz> From: CATMail - Brendon Udy [mailto:brendon(a)catmail.co.nz] Sent: Thursday, 20 July 2006 3:12 p.m. To: admin(a)enlightenhosting.com Subject: CATMail - Email Initiatives for Advertisers Over 90% of business communication has become email and where is it all? Generally sitting in a variety of in-box's around the office which typically creates an information management system that has a lot of holes and doesn't allow for email supervision and overview. If this sounds at all familiar please take the time to read about CATMail. Established in Auckland, CATMail specialise in providing email solutions for advertisers nationwide. We see advertising as the key to any successful business and have put ourselves in a position to help the advertising industry help themselves. What does CATMail do? * It stores emails to job or customer files * It interfaces with Microsoft OUTLOOK * It shares emails across a network by job and date range * It creates email schedules by job and date range * It allows you to find any email in seconds * It automatically creates address books for each job or customer * The share file resides on the shared drive, so backups are simpler * It stores email in a readable format outside of Outlook * Email content and properties are not editable giving integrity to the content * It gives your staff tools to do their job more efficiently Why do I need CATMail? If your company is customer or job focused and use email as a traceable means of communication, it will open up new opportunities to improve team efficiency and management of email archives. Is it difficult to use CATMail? Its interface was designed to follow common Windows navigation habits, allowing a natural feel when using it. The simplistic design limits tasks to a matter of clicks. How Does CATMail Work? CATMail seamlessly integrates into Microsoft OUTLOOK. From a supplementary button embedded into the dashboard of OUTLOOK, individual users are offered a pull-down menu of active company jobs or customer files. Users simply select the relative job or customer file, click to confirm, and the email and its attachment are sent off for indexing and storage into the company's job directory and the CATMail database system. You now have the company email system working in the company's interest. All business emails (and their valuable email addresses) are now embedded into the CATMail database and can be accessed by all authorised staff. Please visit www.catmail.co.nz <http://www.catmail.co.nz/> to find out more information or ring (09) 574-5735 to organise a demo.

2 1

smartmailpro.co.nz
by Russell Fulton 17 Jul '06

17 Jul '06

Any know anything about this crowd? Their name has come up in connection with a spamming incident that we got involved with. >From the web site they could be a legit 'bulk mailer' (if that isn't an oxymoron) or bunch of ratbag spammers. I'd like to have some more information before we decide what to do next. Russell.

5 5

Re: [nznog] APE Route reflector stability
by Gordon Smith 17 Jul '06

17 Jul '06

I believe that Juniper users would be more likely to detect this issue first, since the default arp cache timeout on a Juniper is 20 minutes, as opposed to 240 minutes (4 hours) on a Cisco

1 0

Re: [nznog] APE Route reflector stability
by Thomas Salmen 16 Jul '06

16 Jul '06

> > Hi Thomas > > On Mon, Jul 17, 2006 at 06:26:25PM +1200, Thomas Salmen said: > > > As far as I know, proxy-arp is disabled under junos by default. Our > > peering at APE is done with M-series kit, and we didn't notice any > > issues. > > I wasn't suggesting that the Junipers were proxy-arping, rather that > when the Juniper gets two replies to an ARP broadcast it previously sent > (one from the legit MAC, and one from the proxy-arping MAC), it seems to > be a bit of a lottery which one the Juniper uses. I see; I didn't read your initial message properly - sorry for the mistake. If I recall correctly, some earlier versions of BSD would run into problems if a host received more than one response to an ARP who-has that it had issued. I know that FreeBSD at least was at some point vulnerable to ARP cache poisoning as well; this was a few years ago now. The fix for this particular problem utilized unicast ARP. There is possibly some link here; Junos is based on BSD. I can't find any further reference to this anywhere though. There are possibly some BSD-specific ways of tuning the ARP implementation on the Junipers, but if so it'd no doubt require low-level fiddling. All I can say is that we didn't notice any problems at the time; so I'm not going to play with my production routers too much :) If I do find out any more information I'll let you know; I'm quite interested in finding out myself, now. Cheers, Thomas

1 0

Re: [nznog] APE Route reflector stability
by Thomas Salmen 16 Jul '06

16 Jul '06

As far as I know, proxy-arp is disabled under junos by default. Our peering at APE is done with M-series kit, and we didn't notice any issues. http://www.juniper.net/techpubs/software/junos/junos75/swconfig75-networ k-interfaces/html/interfaces-ethernet-config40.html This is for 7.5 code, which is fairly newish - it's possible there are issues when using older versions. On the E-series it's enabled by default: http://www.juniper.net/techpubs/software/erx/junose72/swcmdref-a-m/html/ i-commands204.html Cheers, Thomas > > Hi all. > > On Fri, Jul 14, 2006 at 07:56:44AM +1200, Gordon Smith said: > > > Would someone like to comment on what's happening with the APE route > > reflectors? The flap statistics I'm seeing are impressive - those > > servers got wings now? :-) > > This turned out to be caused by another ISP lighting up a new router and > > a) getting the netmask wrong > b) forgetting to disable proxy-arp > > So, those setting up new routers, especially Cisco kit that defaults to > turning proxy-arp on, "no ip proxy-arp" is your friend. > > An interesting observation is that of the ~40 active peers, only two > seemed to be adversely affected by the proxy-arp, and they're both > Juniper boxes. I'm wondering if Junipers may have a more trusting > approach to handling ARP replies than other kit. > > So, if anybody has bright ideas on ways that the ARP handling of > Junipers can be made a little more cynical (ie, something more like the > Linux handling where it does unicast ARP until the other end stops > responding, and then goes back to broadcast ARP, but something less > restrictive than static ARP entries), I'm all ears. > > Cheers > Si > >

2 1

APE Route reflector stability
by Gordon Smith 16 Jul '06

16 Jul '06

Would someone like to comment on what's happening with the APE route reflectors? The flap statistics I'm seeing are impressive - those servers got wings now? :-) Cheers, Gordon

2 2

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

13 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24347 descr: Route set advertised to AS9439 by Intergen - AS24347 members: 202.126.80.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dwayne.bace(a)intergen.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24347 descr: advertised to AS9439 by Intergen Limited - AS24347 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.49.144.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: dwayne.bace(a)intergen.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060714 source: NZRR

1 0

Re: [nznog] Procedure for handling a new spammer
by Scott Weeks 12 Jul '06

12 Jul '06

----- Original Message Follows ----- From: Justin Cook <skull(a)skull.co.nz> > I don't really think they were doing superlarge volume at > this point, just your usual commercial spammer who > desperately wants to appear legitimate. One piece of UCE is one too many. It's like someone throwing wet bull crap at you. One is too many. period. scott

6 5

Spectrum Allocations for Broadband Wireless Access
by Jonathan Brewer 11 Jul '06

11 Jul '06

Hi Folks, Last week our friends at the Ministry of Economic Development released a discussion paper on spectrum for broadband wireless. http://www.rsm.govt.nz/spp/bwa/discussion/index.html We'd like to see as many comments on this paper submitted to the MED as there are members of the ISP community. Our primary agenda is getting "mandatory deployment of services" attached to any future management rights and area licenses, so we don't see large players buying up huge blocks of spectrum and sitting on them. This has damaged the environment in New Zealand in the past, and needs to be stopped. "Managed Park" and "Light Licensing" are new ideas (to New Zealand) in the paper also very worthy of our consideration. Responses to this paper are due 4th August 2006, so please have a look now. If there is interest from the community, we would be willing to host a discussion in Wellington on these issues on Thursday, 27th July. Regards, Jonathan Brewer ------------------------- Araneo Limited 230 Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

2 1

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

11 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060405 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060712 source: NZRR

1 0

Sky tower wireless providers
by Barry Murphy 11 Jul '06

11 Jul '06

Hey guys, Let me start by asking you to reply offlist. I'm moving into a flat in auckland CBD (13 floors up) and have a clear view of the entire sky tower, i'm looking for stable wireless service (APE only) so I can get to my systems on Orcons network. If you have radio gear on Level 48 pointing towards Quay street or Anzac Ave (where I am) and can offer reliable cheap ape circuit, 2-10mb unmetered (I dont expect to use that much) which I can use VoIP with, please contact me. And incase I was off topic, I'll offer beer in return. Cheers Barry

1 0

zebra/quagga bgp dumps
by Jamie Baddeley 11 Jul '06

11 Jul '06

Hi, I'd quite like to get my hands on a copy of Marco D'itri's zebra/quagga dump parser. Currently the site http://www.linux.it/~md/software/zebra-dump-parser.tgz is unreachable, does anyone have a copy locally? cheers jamie

12 13

APRICOT 2007 Call for Papers
by Jonny Martin 10 Jul '06

10 Jul '06

Hi All. The APRICOT 2007 call for papers is now open, as per the following. Historically there has been a disproportionally small number of NZ attendees at these conferences so I encourage you all to have look at submitting a proposal and/or attending. Cheers, Jonny Martin APRICOT Program Committee --- Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Bali, Indonesia 21st Feb - 2nd March 2007 http://www.2007.apricot.net Call for Papers The APRICOT 2007 Program Committee is now seeking contributors to the program. This is the main call for Presentations & Tutorials before the final program is fixed. We would like to give people the opportunity to submit their proposals early and to encourage people in the Asia Pacific region who have not previously presented their work to do so. We are looking for people who would like to: * Offer a technical tutorial on an appropriate topic; and/or * Participate in the technical conference sessions as a speaker; and/or * Convene and chair a Birds of a Feather (BOF) session. CONFERENCE MILESTONES --------------------- Call for Papers Opens: 1 July 2006 Deadline for Speaker Submissions: 30 October 2006 First Draft Program Published: 15 November 2006 Final Program Published: 15 January 2007 PROGRAM MATERIAL ---------------- APRICOT 2007 will be arranged into six operational streams, each of which will contain a number of conference tracks and related tutorials. This streamed approach is designed to foster operational communities within the Asia Pacific region. Each stream will take place in the same area providing opportunity for people do further discuss and network with peers. Streams for APRICOT 2007 are: 1. Routing Operations IPv4 and IPv6 Routing, APNIC Routing and IPv6 Technical SIG, MPLS, Backbone operations. 2. Services Operations DNS, VOIP, ENUM, IDN, IDC, content and other services, APNIC DNS SIG. 3. Security Operations NSP-Sec, DDoS, Security Operations, Anti-SPAM, Anti-Malware. 4. Internet Provider Relationships IXP Operations, Peering, APNIC IX SIG. 5. Access Technologies Wireless, WiMax, Metro Ethernet, DSL, Broadband access aggregation. 6. APNIC Stream APNIC's NIR, Database, Policy SIGs. TUTORIALS Tutorials are full-day workshops which focus on a particular subject in-depth. They may be presented by a single Instructor, or a team of instructors working together. Tutorial Instructors are encouraged to also sign up to be a Speaker in the Technical Conference Program as well. You can sign up to give a tutorial and/or conference session presentation by following the instructions at the end of this message for signing up as a speaker or instructor. Tutorial topics which have successful in the past, or have been requested for this year are: - Network security, IPSec, Auditing/Forensics, DDoS Mitigation, VoIP Security - Address planning, conservation, responsibility and migration to IPv6 - High performance IP backbone routing and management - BGP MultiHoming - MPLS - IPv6 implementation - Network planning, management and traffic engineering - Internet exchanges, construction, peering and collocation - Operations, NOC, Helpdesk and other support aspects - BIND, DNSSEC, Split Horizon DNS, and Reverse and multilingual DNS - Broadband first/last mile access technologies - Mobile and wireless technologies - Content, Applications, streaming and multimedia infrastructure - VoIP, Unified messaging, scaling e-mail infrastructure, Asterisk, etc. - Hosted Essential Services (mail, DNS, etc), Server scaling, Open source - Quantitative Analysis for Internet Public Policy The program committee will consider proposals for tutorials in any of these areas, and also in new areas. There will be two days of Tutorials. Tutorials last 1/2 day or a full day and can cater to beginner through to advanced audiences. Tutorial days are typically split into four 1.5 hour sessions. If you have an idea for a tutorial subject that is not listed, please feel free to submit it to us. TECHNICAL CONFERENCE SESSIONS The Main Conference Program for 2006 will be made up of two days, with three streams each day. In addition there will be a stream focused on local (Indonesian) internet issues. Each stream will consist of four 1.5 hour sessions, with each having three or four presentations. This allows 20-30mins per presenter. Sessions are chaired by persons of appropriate expertise in the subject matter of the session and will include ample time for questions from the audience. Successful presentations from past APRICOTs have covered topics relevant to current operational deployments or new technologies not yet in wide deployment. Proposals for conference presentations are invited for topics fitting into the six streams outlined above. If you would like to give a presentation at one or more of the sessions, follow the instructions at the end of this message for signing up as a speaker or instructor. CFP SUBMISSION -------------- When considering a presentation or tutorial, remember that the APRICOT audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the tutorials and to address issues relevant to the day-to-day operations of ISPs and network operators over the next 12 - 18 months in the conference sessions. The deadline for submissions is 30 October, 2006. Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions. Final slides are to be provided by 15 January, 2007. While the majority of speaking slots will be submitted by 30 October 2006, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. IMPORTANT NOTE -------------- APRICOT is a TECHNICAL conference so marketing and commercial content is not allowed within the program. The program committee is charged with maintaining the technical standard of APRICOT, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. FUNDING AND SUPPORT ------------------- APRICOT is a not-for-profit event that tries to keep the cost to attendees low so we are unable to pay the travel costs of speakers. Speakers from developing countries may be eligible for the APRICOT Fellowship Program which provides basic assistance to successful fellows to cover local living and registration expenses associated with attending the conference. Of course, Tutorial instructors will not have to pay any registration fee to attend the conference or tutorials, and Conference Speakers do not have to pay for registration to the Technical Conference. SIGNING UP AS A SPEAKER, INSTRUCTOR OR BOF Convener If you would like to be considered as a tutorial instructor, session speaker, or a convener of a BOF, please fillin the form at http:// submission.apricot.net/ More information on the conference is available at http:/www.2007.apricot.net Thanks, APRICOT Program Committee program(a)apricot.net

1 0

Re: [nznog] [address-policy-wg] 91.192/10 to be used for PI assignments to End Users
by leo vegoda 09 Jul '06

09 Jul '06

Hi Jeroen, Jeroen Massar wrote: > On Mon, 2006-07-10 at 13:50 +0200, leo vegoda wrote: >> Dear Colleagues, >> >> At recent RIPE Meetings, we have reported a steady rise in requests from >> our members for Provider Independent (PI) address space for End User >> networks. > > Any link to the slides which might contain the expected increase for the > coming years? Especially the estimated number of routes that will newly > be announced using BGP because of this would be something nice to see. Slides from RIPE 52 are available here: http://www.ripe.net/ripe/meetings/ripe-52/presentations/ripe52-plenary-ripe… We have not made a growth projection in these slides because we concentrate on reporting what has happened. Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

91.192/10 to be used for PI assignments to End Users
by leo vegoda 09 Jul '06

09 Jul '06

Dear Colleagues, At recent RIPE Meetings, we have reported a steady rise in requests from our members for Provider Independent (PI) address space for End User networks. We have reclaimed and recycled space from closed Local Internet Registries to meet this demand, but we are nearing the point where the available PI space will run out. In the past, we made PI assignments from former Class C space (193/8 and 194/7). Because of the increasing demand for PI space, we made sure that we would be able to use some of our most recent allocation of address space to meet future requests. We have designated 91.192/10 for PI assignments to End User networks. When the former Class C space is exhausted, we will start to make PI assignments from 91.192/10. We will let you know when this happens. We are announcing a pilot prefix using the RIS beacons, you may want to update any filters that you have in place. The RIS beacons are announcing the following networks: 91.192.0.0/24 91.192.0.0/16 You can ping 91.192.0.1. Full details of reachable IP addresses and tools are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

Fwd: 3G/T3G VoIP slowdown
by Jonny Martin 06 Jul '06

06 Jul '06

> From: "Neal Richardson" <Neal.Richardson(a)telecom.co.nz> > Date: 7 July 2006 12:13:51 PM > To: "Jonny Martin" <jonny(a)jonnynet.net>, "Steve Boyd" > <steve(a)consumer.org.nz> > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] 3G/T3G VoIP slowdown > > I can say with complete confidence that we do not have the > technology to "slow" VoIP traffic over our T3G network. > > > > > Regards, > > Neal Richardson > Mobile Data - Technology Manager > > T+64 4 382 5572 (Extn 46572) > M+64 27 654 3200 > Eneal.richardson(a)telecom.co.nz > Wwww.telecom.co.nz > > Level 4 - Unit 4, Telecom Centre, 49-55 Tory Street > P O Box 293, Wellington > > > > > "This communication, including any attachments, is confidential. If > you are not the intended recipient, you should not read it - please > contact me immediately, destroy it, and do not copy or use any part > of this communication or disclose anything about it. Thank you. > Please note that this communication does not designate an > information system for the purposes of the Electronic Transactions > Act 2002." > > > > -----Original Message----- > From: Jonny Martin [mailto:jonny(a)jonnynet.net] > Sent: Thursday, 6 July 2006 12:16 p.m. > To: Steve Boyd > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] 3G/T3G VoIP slowdown > > > Anyone know about VoIP packets being slowed on either Telecom or > > Vodafones 3G networks? > > I've always had good experiences running VoIP packets over both T3G > and Vodafone's 3G network. Of course, I don't form a very large > sample. > > Telecom have in the past spent many an engineer's time on projects to > specifically bust the VoIP, however by far their most effective > weapon to date is a largely crap (pick your metric) access network. > That said, there are some quite impressive RTP/P2P busters available > if required - verso.com, amongst others. What's it called, oh yeah, > QOS :). > > As with most providers they're simply reserving the right to block/ > jumble/charge a premium for particular traffic types. Each to their > own. > > Cheers, > Jonny. > >

1 0

3G/T3G VoIP slowdown
by Steve Boyd 05 Jul '06

05 Jul '06

Hi I'm helping one of my colleages do some research for a follow up to this article on 3G VoIP being slowed: http://www.consumer.org.nz/newsitem.asp?docid=2624&category=News&topic=I SPs%20able%20to%20slow%20down%20VoIP%20services Anyone know about VoIP packets being slowed on either Telecom or Vodafones 3G networks?

3 2

Re: [nznog] Procedure for handling a new spammer
by Justin Cook 05 Jul '06

05 Jul '06

I don't really think they were doing superlarge volume at this point, just your usual commercial spammer who desperately wants to appear legitimate. Cheers though, I'll keep it in mind. TreeNet Admin wrote: > Give iconz a day or so to handle the problem. > Then if they are still there and spamming. > You may want to check all the details you can of the outfit with the > spammer database at spamhaus.org. Like with brendan battles, they may > already have a listing and certainly have the ability to negotiate > with iconz on a large scale. > > I also have a few other channels I can push the info down depending on > the nature of the spam, to get it spread around if you want to send > some of the messages (in full) to my abuse(a)treenetnz.com box. > > Amos Jeffries > > ----- Original Message ----- From: "Justin Cook" <skull(a)skull.co.nz> > To: "NZNOG" <nznog(a)list.waikato.ac.nz> > Sent: Wednesday, July 05, 2006 11:50 AM > Subject: [nznog] Procedure for handling a new spammer > > >> There's a new outfit who seem to like bulk unsolicited email. It's >> pretty annoying as they're using Iconz as well and while I'm not totally >> clear on the specifics, this can't be good for any Iconz customers like >> me who don't want to be RBLed through someone else's behaviour. >> >> I've sent the spammer a short and sharp email as well as a note to >> abuse(a)iconz, is there anything else worth doing to help stop it in its >> tracks? >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> > > > >

1 0

Re: [nznog] 3G/T3G VoIP slowdown
by Barry Murphy 05 Jul '06

05 Jul '06

Umm to my knowledge VoIP traffic is againts their terms and conditions for data calls on the T3G and vodafone. Barry > Hi I'm helping one of my colleages do some research for a follow up to > this article on 3G VoIP being slowed: > > http://www.consumer.org.nz/newsitem.asp?docid=2624&category=News&topic=I > SPs%20able%20to%20slow%20down%20VoIP%20services > > Anyone know about VoIP packets being slowed on either Telecom or > Vodafones 3G networks? > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Procedure for handling a new spammer
by Justin Cook 04 Jul '06

04 Jul '06

There's a new outfit who seem to like bulk unsolicited email. It's pretty annoying as they're using Iconz as well and while I'm not totally clear on the specifics, this can't be good for any Iconz customers like me who don't want to be RBLed through someone else's behaviour. I've sent the spammer a short and sharp email as well as a note to abuse(a)iconz, is there anything else worth doing to help stop it in its tracks?

4 5

Statistics for domain names in the .nz space.
by Dean Pemberton 03 Jul '06

03 Jul '06

Hi all. So I was thinking. It's been about 3 years now since we all banded together and voted for .geek.nz (You did all vote FOR it right?). I figured that even though there was a large takeup initially, that there would be a pretty severe dropoff over time, leaving about 6 people who actually wanted them. I asked Debbie if she could give me some stats and she pointed me at the following page. http://dnc.org.nz/story/30221-51-1.html It has statistics for all the .nz 2lds so I decided to graph them. You can see the entire spreadsheet here. http://deanpemberton.com/domainz.xls (Yes it's excel, yes I've confirmed that it opens in OpenOffice (Although the regression lines might not), no I don't want to hear any of your wingeing =) ) As a teaser, I've attached the graph for .geek.nz. You can clearly see that every year about Aug, there is a drop off as people figure they don't want their domains anymore (just after they get a bill). This dropoff is more than covered by the increase throughout the year though. So .geek.nz looks pretty strong. Much stronger than .maori.nz or .iwi.nz. There are even some 2ld's which are slowing down in their growth. Altough on the whole, the regression lines are pretty poorly fitting. Better fit models are welcome. What is interesting is that the .co.nz, .org.nz and therefore the Total can be modeled pretty well on a power curve. While it's not that much different to the linear it is food for thought. There is a possibility that these are growing faster than linear. Anyway - it was all interesting stuff and I thought you might all like to have a gander. Dean

1 0

The New Zealand Network Operators' Group
by Donald Neal 29 Jun '06

29 Jun '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Jun '06

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 202.49.152.0/21^21-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Jun '06

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060525 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060629 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Jun '06

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060523 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.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 20060629 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Jun '06

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9872 descr: advertised to AS9439 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9872 descr: advertised to AS9439 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 202.49.152.0/21^21-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR --- PREVIOUS OBJECT: route: 202.49.152.0/21 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.49.152.0/21 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

Time to post something on topic for the list
by Juha Saarinen 28 Jun '06

28 Jun '06

http://www.theregister.co.uk/2006/06/28/beer_better_than_wine/ -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 21 Jun '06

21 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES: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.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.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, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 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, 203.163.70.0/23^23-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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Jun '06

21 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES: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.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.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, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 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, 203.163.70.0/23^23-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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR

1 0

NZ regional IPs
by Steve Boyd 20 Jun '06

20 Jun '06

Hi there - we've recentely put a fairly simple broadband speedtest online at http://www.consumerspeedtest.org.nz <http://www.consumerspeedtest.org.nz/> (hosted on a VPS on www.openhost.co.nz <outbind://2/www.openhost.co.nz> which uses www.maxnet.co.nz <outbind://2/www.maxnet.co.nz> as their ISP in case you're interested) Along with the the provider, plan, download and upload speeds we're also recording the users IP address - I'm wondering if it's possible to work out what city / region the user is from based on their IP? Cheers Steve

2 1

Re: [nznog] NZ regional IPs
by Simon Allard 20 Jun '06

20 Jun '06

Depends on the ISP and how they configure their network. In IHUG's case, no, as all users terminate in Auckland on LNS's, and given IP's out of the same pool. Simon Allard Ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz _____ From: Steve Boyd [mailto:steve(a)consumer.org.nz] Sent: Wednesday, 21 June 2006 3:07 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NZ regional IPs Hi there - we've recentely put a fairly simple broadband speedtest online at http://www.consumerspeedtest.org.nz <http://www.consumerspeedtest.org.nz/> (hosted on a VPS on www.openhost.co.nz <outbind://2/www.openhost.co.nz> which uses www.maxnet.co.nz <outbind://2/www.maxnet.co.nz> as their ISP in case you're interested) Along with the the provider, plan, download and upload speeds we're also recording the users IP address - I'm wondering if it's possible to work out what city / region the user is from based on their IP? Cheers Steve

1 0

Hardware Request
by John S Russell 20 Jun '06

20 Jun '06

All: I'm currently working (personally, not with my ICONZ hat on) on a collective community network project and I find myself in need of a cisco 6000 series chassis. I'm after a WS-C6006 or 6009 (though a 6003 would also be fine, at this stage).[1] Just the chassis required, no need for a supervisor or any other modules. If anyone has upgraded to a 6500 or higher unit and has one of the older chassis hanging around, with _or without any PSU modules_, I am more than willing to exchange some (limited) cash, or beer, or fetching of coffee, or OUTRAGEOUS flattery[2] for it. I'd be willing to pick up or arrange shipping from almost anywhere in NZ or AU. If you can help, please let me know. Thanks in advance. JSR [1] If you have a spare 6500 chassis, that's a bit overkill for this project - but don't let that stop you from contacting me! [2] For example, an elaborate posting to the mailing list/blog/web forum/newsgroup of your choice detailing how your pure transcendant geek kung fu makes it seem like jets of fire shoot from your very soul and light up the lives of all around you.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jun '06

15 Jun '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jun '06

15 Jun '06

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

1 0