- NZNOG - lists.nznog.org

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

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS7657 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

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

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink descr: SMARTLINX3 peering at '218.100.26.3' descr: see Citylink RT job #1927 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050331 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Jul '05

31 Jul '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference We're in the early stages of planning our next conference, which is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 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 31 Jul '05

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

NASA TV Query...
by Clint Jeffrey 30 Jul '05

30 Jul '05

Thanks to all whom responded.Wally has been in contact.. Ta Thanks. Clint - VK3CSJ.

1 0

NASA TV Feed on OPTUS B1...query
by Clint Jeffrey 29 Jul '05

29 Jul '05

Hello to anyone that maybe still using this forum.I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

2 1

RE: [nznog] NASA TV Feed on OPTUS B1...query
by Jeremy Strachan 29 Jul '05

29 Jul '05

Done. ________________________________ From: Clint Jeffrey [mailto:vk3csj(a)netspace.net.au] Sent: Saturday, 30 July 2005 8:51 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NASA TV Feed on OPTUS B1...query Hello to anyone that maybe still using this forum...I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

1 0

Anti Spam Legislation vs Spam realities and ISP staffing
by Mark Foster 29 Jul '05

29 Jul '05

http://www.nzherald.co.nz/index.cfm?c_id=5&ObjectID=10338203 My review of this article noted this paragraph: --8<-- Internet users will complain in the first instance to their internet provider about spam email, and the Department of Internal Affairs will act as an internet watchdog if the matter is taken further. --8<-- Now did I get the wrong end of the stick here, or is this saying that the onus of the ISP that provides connectivity to the Spam Receiver to act on complaints - or the DIA will be hounding them? Shouldn't the source ISP, and not the destination, be the people responsible for dealing with their own spam sources? I wrote a bit of a commentary of my own: http://www.blakjak.net/node/view/261 However wonder if this has come to the attention of anyone else yet... The first thing that jumps into my head is that ISPs are going to wind up having to do all the investigative legwork on the complaints they receive - and not many ISPS I know of are staffed to support this. Antispam costs for all providers going up - and probably going up in relation to the size of their customer base. Hmmm.... Mark.

3 3

RE: [nznog] Multi-point VPN around NZ to a central location ( Wellington)
by Kerry Milestone 28 Jul '05

28 Jul '05

Mmmmm....... Chrome bits...... Yes. Realistically though... Nissan350z. ________________________________ From: Drew Broadley [mailto:drew(a)corrupt.co.nz] Sent: Friday, 29 July 2005 2:19 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Multi-point VPN around NZ to a central location ( Wellington) Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

2 1

Multi-point VPN around NZ to a central location (Wellington)
by Drew Broadley 28 Jul '05

28 Jul '05

Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

1 0

Reminder Notice: ENUM Consultation extended until 19th August
by Michael Sutton 28 Jul '05

28 Jul '05

ENUM ANNOUNCEMENT: Those interested are reminded, that InternetNZ is receiving feed back & submissions on the "New Zealand ENUM Trial Framework - Consultation Report" by M-co for InternetNZ: The Report is available on the web site at http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf (1.2MB) Originally we had advised 21 July, however there is now additional time available in our schedule. Best Regards Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chair - Enum Task Force InternetNZ Project Manager - UCI PUA Enum Prototype Member Audit & Technical Committee Telephone: +64 4 475 9235 Mobile: +64 21 305500 Facsimile: +64 21 305002 WWW: http://www.internetnz.net.nz/public/enum/ E-mail: mailto:michael.sutton(a)awacs.co.nz mailto:michael.sutton(a)internetnz.net.nz> ----------------------------------------------------------------------- CAUTION: This email and any attachments may contain information that is confidential and subject to legal privilege. If you are not the intended recipient, you must not read, use, disseminate,distribute or copy this email or any attachments. DISCLAIMER: To the maximum extent permitted by law, Michael Sutton is not liable (including in respect of negligence) for viruses or other defects or for the changes made to this email or to any attachments. Before opening or using attachments, check them for viruses and other defects. -----------------------------------------------------------------------

1 0

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

28 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050729 source: NZRR

1 0

RE: [nznog] [FW] Re: Interesting articles from Beehive
by Jeremy Strachan 28 Jul '05

28 Jul '05

We'd like an increase from 128K to a whole 256K! Greedy I know ... But 128K is horribly limited for any remote users trying to access a site over a vpn, webmail, you name it. Things we do in the modern age. Jeremy -----Original Message----- From: Blair Harrison [mailto:nznog(a)jedi.school.nz] Sent: Thursday, 28 July 2005 9:09 p.m. To: Richard Dingwall Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] [FW] Re: Interesting articles from Beehive Richard Dingwall wrote: > > I would imagine that the low upstream limit could (partly) have been > an effort to curb NZ P2P network traffic. > > National P2P networks (DC, particularly) became very popular a few > years ago, when unlimited 128KBit/128KBit DSL was available (i.e, > download as fast as your connection goes - woohoo!). > > More recently, as the downstream rate has significantly exceeded the > upstream, your slow upload becomes someone else's slow download. > Imagine the thrill of leeching at 16KByte/s on a 2MBit connection..! > > - Richard > Quite a possibility. I did have one of our high speed customers leave Kazaa on over a few days.. managed to eat up about 75GB of traffic in those couple of days. They were uploading at a rate of about 1.8 gig an hour. I can see the merits of limiting upstream speed in the interests of conserving network capacity, but I don't see why regular non-p2p-using customers should be held back from experiencing true broadband speeds because of the actions of the leechers out there. There are methods available to limit the impact of such P2P applications and I believe at least one large ISP in NZ has implemented a layer 7 filtering system that can limit speeds at the application level. So the technology to limit the impact of P2P users to the network is available, should Telecom choose to use it. Why slow down the rest of the users who want to do really cool things like full screen multi-user videoconferencing and sending media files across town for processing because of the actions of the pesky leechers? Maybe because that would start to eat into their other more traditional 'higher value' revenue streams such as Frame Relay, Metro Ethernet and ATM? (which, incidentally, I can't even find on their website today) P2P may be a big reason and the most obvious, but I doubt it's the only reason. Cheers, Blair _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

NZ General Election - On The Night Results
by Andrew McMillan 28 Jul '05

28 Jul '05

Hi, As you will know by now this years general election will be on the 17th of September. The Chief Electoral Office have contracted Catalyst IT Ltd to host a public website with the election-night results, as we have done for the previous two elections. Counting of votes will begin when the polls close at 7:00pm, and will continue through to the small hours of the morning of the 18th. Historically, peak interest has been from around 8:30pm through to 10:30pm. If any ISPs or other websites would like to mirror this information for your own customers I will be happy to arrange rsync access to the changing website. In addition to the HTML formatted web pages there are a series of data files which are intended for post-processing and a specification of these data formats is available. Updates to the website are applied approximately every minute during the counting process. Please contact me off list if you are interested in any of this. Thanks, Andrew McMillan. ------------------------------------------------------------------------- Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Planning an election? Call us! -------------------------------------------------------------------------

1 0

Webcasting Heads up
by Richard Naylor 27 Jul '05

27 Jul '05

Tomorrow Internet NZ is having their AGM and using 2 Access Grid nodes to link participants in AKL and WLG. Its at 6pm from memory. I think I've managed enough parts to make another Access Grid node and so am going to attempt to webcast a grid session in action, using multiple simultaneous webcast streams . It may fail horribly. I will drink beer whatever happens (got back on topic). The link to the webcast is http://www.r2.co.nz/20050523 There is TV playing on the streams now if you want to see what it may look like, if it all works. Operators may get calls from clients requesting help. May see a bit of traffic (its about a meg per client) or may just like to watch and laugh as it all crashes. Drink beer, it all looks better then. Feedback will be appreciated. Anyone still got dial-up and willing to try it ? Rich

1 0

[FW] Re: Interesting articles from Beehive
by Juha Saarinen 27 Jul '05

27 Jul '05

---------------------------------------------------------------------------- Paul Brislen wrote: > I'm sorry but has the Minister read his own Commissioner's rulings? > > snip: > I am aware of an very strong opinion in the industry that 128k upstream is > a constraint. Like the Commissioner I do not regard the proposed regulated > 128k service as an upper limit. On the contrary, it should be seen as a > baseline and I expect commercial offerings in the market above that level. > snip I'm sorry but the regulation has 128 as the MAXIMUM upload speed, not some kind of regulated minimum. He can expect all he likes, without some new regulation that says otherwise, 128 is all the incumbent has to deliver and 128 is all it will deliver. I must now drink a lot of beer a: to stay on topic and b: to drown my narrowband sorrows. I bid you good day. - Paul ---------------------------------------------------------------------------

11 15

<<<Amendment>>> InternetNZ releases ENUM Personal User Agent Prot otype software under Open Source BSD Licence.
by Michael Sutton 27 Jul '05

27 Jul '05

============ July 28th 2005. Greetings: I am resending a modified version of this information bulletin highlighting the contribution of the European Telecommunications Standards Institute (ETSI) to this work: This PUA software was designed and developed in New Zealand by CatalystIT and utilised ETSI Guides available at http://www.etsi.org/services_products/freestandard/home.htm [1] ETSI EG 202 067: "Universal Communications Identifier (UCI); System framework". [2] ETSI EG 202 249: "Universal Communications Identifier (UCI); Guidelines on the usability of UCI based systems". We thank Mike Pluke and others at ETSI. Best Regards Michael Sutton Chair ENUM Task Force. ============ InternetNZ releases ENUM Personal User Agent Prototype software under Open Source BSD Licence. http://www.internetnz.net.nz/public/enum/pua/2005-07-pua-media-release.html InternetNZ announced today the release of its ENUM "Personal User Agent" prototype source code under an Open Source BSD Licence. The release hopes to encourage developer support of an ENUM initiative in New Zealand. The code is available from http://www.internetnz.net.nz/public/enum, as well as Reports prepared by the Task Force and a limited quantity of CDs. The PUA release does not include the "Universal Communications Identifier" Registry modules. Subscribe to a public information list at http://farsight.internetnz.net.nz/mailman/listinfo/enum. ENUM is a set of Internet protocols, mapping telephone numbers onto the Internet naming system. Existing email addresses, web sites and alternate telephone contact addresses can be attached to this ENUM record. This record can be used by suitable handsets or (pabx type) computer programs to contact the number holder. ENUM is in government approved trial or production in approximately 30 countries. "Personal User Agents" (PUA) are software programs which act like firewalls; automatically filtering requests for ENUM contact information and deciding what information to release and how incoming calls will be directed based on rules that look at the inbound identity of the caller. This protects the consumer from address harvesting or privacy breaches. In theory every existing and future telephone number in the world could be ENUM provisioned. This provides a massive legacy base on which commercial PUA software can be built. The ENUM PUA is based on our research and Guides by Europe's Telecommunications Standards Institute, ETSI (EG 202 067 & EG 202 249). http://www.etsi.org/services_products/freestandard/home.htm. In a complimentary note ETSI also referred InternetNZ's work to the European Commission. InternetNZ looks forward to continuing close and contructive dialogue with ETSI. Following completion of an ENUM PUA UCI Feasibility Study at the beginning of 2005 the prototype was developed by Catalyst IT (http://www.catalyst.net.nz) of Wellington, for InternetNZ. The PUA prototype was linked to another module known as the "Universal Communications Identifier" (UCI) which can bind an individual's name and service requirements to ENUM records and then be accessed by other PUAs. Future ENUM PUA software will enable users to opt-in to security services that will restrict publication of contact (email etc) information to anonymous callers and will permit intelligent routing of calls based on the relationship of the receiver to the caller and possible cost optimization of call termination and also increasing the rate of successful call completion for the networks. There are significant international opportunities for software developers to incorporate ENUM with PUA features into their existing communications software and directory services. InternetNZ anticipate that a number of software companies will work co-operatively to develop compatible systems that will compliment each other on different niche markets such as PUAs in the Telco-network, ISP, corporate business, SoHo and individual markets. Co-operating with the Government, Telecommunication Carriers Forum and applications developers, InternetNZ will participate and facilitate a New Zealand ENUM Trial over the next year that will provide a platform to test, demonstrate, commercialize applications and integrate ENUM to deliver economic advantage to the New Zealand community. InternetNZ welcomes enquiry from anyone interested in undertaking ENUM development work and participating in the Trial. "One Number To Hold Them All" Michael Sutton Chairman - InternetNZ ENUM Task Force Councillor InternetNZ Member Technical and Audit Committee Phone: +64 4 4721600 Ext 730 mailto:michael.sutton(a)internetnz.net.nz

1 0

Interesting articles from Beehive
by Ian McDonald 27 Jul '05

27 Jul '05

Folks, You might be interested in two postings today: http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=23810 which is the Anti Spam bill and includes a (badly) scanned version of the bill. Also: http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=23811 where the government seems to be rattling the sabres a little in broadband particularly around wholesale and the 128 k upload. Regards, Ian

1 0

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

27 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR

1 0

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

27 Jul '05

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

1 0

OT 1U or 2U servers
by Barry Murphy 26 Jul '05

26 Jul '05

Hey guys, Please reply offlist if you have some second hand 1U's or 2U's you're looking at getting rid of. Thanks Barry

1 0

Victoria SCS Mail Admin
by Jonathan Brewer 26 Jul '05

26 Jul '05

Hello, Looking for a mail admin at VUW to contact me off list fairly urgently re: an exploding mailing list running on terror.vuw.ac.nz. Quick response will save many headaches. Cheers, Jon

3 4

Iconz/esurf please contact
by Daniel Cross 25 Jul '05

25 Jul '05

Could somebody from esurf please contact me off-list. I've been trying to get hold of someone through the helpdesk (the only number I seem to be able to find), but am only getting an answering machine with no call backs thus far. This is in regards to one of our legacy customers with certain ports blocked. I can be reached on 021492917, or 5223680 Thanx, Daniel Cross Network Surveillance Engineer Woosh Wireless Limited Tel: +64 (9) 522 3680 Fax: +64 (9) 520 3447 0800 4 WOOSH www.woosh.com <http://www.woosh.com>

1 0

http://www.wlug.org.nz/NewZealandInternetHistory license details
by Matt Brown 25 Jul '05

25 Jul '05

Hi, Many of you will be familiar with the New Zealand Internet History page created on the WLUG Wiki after this years NZNOG conference. WLUG is currently in the process of clarifying the license situation for all of the wiki content, and we are endeavouring to bring all content under the a Creative Commons Wiki License (see http://www.wlug.org.nz/WlugWikiLicense for details). Due to the huge volume of edits and additions to this page we unfortunately don't have details of all of the original contributors and authors to it. My recollection is that this page was created by Ian McDonald based on notes from Joe's talk. Given that the content is all a historical record that has been collaboratively compiled, I don't imagine we're going to run into any copyright problems, but just to be sure, we would like to check. Does anyone on this list, who has contributed significantly to the page object to it being placed under the aforementioned license? If you do, please contact me so we can discuss it. Assuming we don't have problems I intend to relicense this page near the end of the week. Kind Regards PS. You're still welcome to add to/improve the page :) -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

5 4

OT: Jobs in Christchurch
by Bill Walker 20 Jul '05

20 Jul '05

Hi, Just a quick note to see if anyone knows of any jobs / job agencies in Christchurch? Please Reply off list. Thanks, Bill

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS23655 as-name: NZRR-AS23655 descr: Snap Internet descr: WIX peering at '202.7.1.240' descr: see Citylink RT job #2857 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23655 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 20050721 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23655 descr: Route set advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/20^20-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.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.50.117.0/24^24-29, 202.50.169.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 20050721 source: NZRR

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- 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, 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, 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.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.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, 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 20050526 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, 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, 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.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.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, 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 20050721 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050517 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050517 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR --- 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, 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, 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.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.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, 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 20050526 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, 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, 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.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.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, 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 20050721 source: NZRR

1 0

ICONZ prefix update 2005-07-20
by John Johnston 19 Jul '05

19 Jul '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer direct with ICONZ there is an update. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

1 0

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

18 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.148.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR

3 3

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

18 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route: 210.55.248.0/21 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.248.0/21 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 202.49.176.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 202.49.176.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 210.55.202.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.202.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR

1 0

Re: [nznog] DPE and 3CIX
by Webmaster 18 Jul '05

18 Jul '05

For those who want to peer there, our content will be available at 3CIX when we launch. If you already peer with the 3CIX route servers then you need do nothing. regards, Richard Hulse Radio NZ >>> Andy Linton <asjl(a)citylink.co.nz> 19/07/2005 14:50 >>> CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DPE and 3CIX
by Andy Linton 18 Jul '05

18 Jul '05

CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/

3 2

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Donald Neal 18 Jul '05

18 Jul '05

On Tue, 19 Jul 2005, Barry Murphy wrote: [...] >> I'm guessing customers connect directly to the erx's, thus if the erxcrash's >> and goes down, customer falling off that node will be effected. >> >> The idea is a pretty map with colors indicating packet loss. >> Let's just see what happens when the next big network fault happens. >It is highly unlikely anyone will give you this information (and in some >cases this is 100% unlikely) as this would tend to be considered >"commercially sensitive" data to many large organisations. >Any information gathered through probing networks will most certainly be >inaccurate and could lead (as pointed out earlier) to increased >frustration in helpdesks when some clueless customer rings up to report an >ERX crash because they saw it on your intarwebnet page. There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

4 3

Re: NZNOG Digest, Vol 31, Issue 14 (Out of Office)
by Lance Edwards 18 Jul '05

18 Jul '05

I will be out of the office starting noon Monday 18 July and will return Friday 22 July. I will be checking email once per day during this period. Regards, Lance ______________________________________________________________________________________________________ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info(a)linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. ______________________________________________________________________________________________________

2 1

[OT]Ispmap / isp locations / core routers
by Barry Murphy 18 Jul '05

18 Jul '05

Hey guys, I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz . 1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice. To gather this info, simply fire up http://status.fast.co.nz/metric.html , zoom in to the closest location to your office/router as possible, center it in the screen and mail me the details of latitude and longitude. http://status.fast.co.nz will soon become apart of ispmap, if you go directly to this URL you will see what my aim is, to have a country map (with the ability to filter by ISP) with the status of each ISP's network. Please mail back (Off list) in the following format: ISP: Contact: Logitude: Latitude: IP Address: Services effected: (optional, but would be nice to see what parts of the country and what services would be effected) Equipment: (optional, but eg cisco, I may add logos to the map later) Thanks. Barry

8 12

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Gordon Smith 18 Jul '05

18 Jul '05

I agree 100% with Steve on this. I doubt that there are many providers that wish to publicise their internal network structure. A pretty map has very little relevance to a modern MPLS-based network without a view of the underlying signalling. All you'll see is the switched paths, not the physical infrastructure. There is such a thing as too much information - I see little point in letting an end user try to diagnose a network fault when said user has little or no understanding of network topologies and protocols, even at layer 3. Cheers, Gordon

1 0

Frame Relay services
by Andy Linton 16 Jul '05

16 Jul '05

I'd appreciate hearing from ISPs who provide connectivity using Frame Relay. Replies off list and please no diatribes about how crap Frame Relay is and how I should use technology X instead.

1 0

RE: [nznog] [Fwd: Buzz.ThePeople]
by Scott Walsh 14 Jul '05

14 Jul '05

Interesting (and un-surprisingly), the privacy statement on their website (http://www.buzzchannel.co.nz/v1.1/research/surveys/privacy.asp?cid=42&sid=1 ) contradicts the statement below. -----Original Message----- From: Richard Patterson [mailto:richard(a)helix.net.nz] Sent: Friday, 15 July 2005 14:01 To: nznog(a)list.waikato.ac.nz Subject: [nznog] [Fwd: Buzz.ThePeople] <snip> IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople.

1 0

[Fwd: Buzz.ThePeople]
by Richard Patterson 14 Jul '05

14 Jul '05

Sorry to disrupt everybody from their ever so important SPF ranting. but, has anybody heard of this NZ spamm0r? registrant_contact_name: Buzz Channel Limited registrant_contact_address1: P.O. Box 68-953 registrant_contact_address2: Newton registrant_contact_city: Auckland registrant_contact_postalcode: 1003 registrant_contact_country: NZ (NEW ZEALAND) registrant_contact_phone: +64 9 5284883 registrant_contact_email: nick.macdonald(a)buzzconsult.com Registered Office 43 Bright St Eden Terrace Auckland Directors VANCE, Mary MACDONALD, Nicholas -------- Original Message -------- From: - Fri Jul 15 13:09:22 2005 X-Account-Key: account3 X-UIDL: 1121390459.30535.skywarp,S=1631 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <buzz(a)buzzchannel.co.nz> Delivered-To: detonate(a)helix.net.nz Received: (qmail 30533 invoked by uid 89); 15 Jul 2005 01:20:58 -0000 Received: from unknown (HELO 216-55-168-48.dedicated.abac.net) (216.55.168.48) by skyfire.helix.net.nz with SMTP; 15 Jul 2005 01:20:58 -0000 Received: from BuzzServer1001.buzzone.buzzchannel.net (unverified [216.55.168.48]) by 216-55-168-48.dedicated.abac.net (SurgeMail 3.0c2) with ESMTP id 73137 for <detonate(a)helix.net.nz>; Thu, 14 Jul 2005 18:08:13 -0700 Return-Path: <buzz(a)buzzchannel.co.nz> From: Buzz.ThePeople <buzz(a)buzzchannel.co.nz> To: detonate(a)helix.net.nz Subject: Buzz.ThePeople Date: Thu, 14 Jul 2005 18:08:13 -0700 Message-ID: <20050714-18081356-cdc(a)BuzzServer1001.buzzone.buzzchannel.net> MIME-Version: 1.0 X-Server: High Performance Mail Server - http://surgemail.com Dear Richard Patterson, Help shape your future PLUS have the chance to win! Buzz.ThePeople is a new online way for you to have your say on lots of different topics. Many people are joining Buzz.ThePeople because they want their views considered by NZ decision makers (e.g. political pollsters, the media, marketers and market researchers). Others are joining because there are going to be great prizes and even opportunities to earn cash. If you are interested and want to know more (plus your chance to go into the draw for a new Dell Inspiron 6000 notebook computer) click on the following link: http://www.buzzthepeople.co.nz?c=43401 IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople. Kind Regards, The Buzz Team.

4 3

SPF Uptake in New Zealand
by Craig Whitmore 14 Jul '05

14 Jul '05

So you ask what is SPF? SPF (Sender Permitted From) is an anti-forgery method used with SMTP which stops people trying to send from your domain. Not designed for stopping spam, but helps reduce the amount of spam as well (stops people sending from other peoples domains). Spammers can add SPF records to their domains yes, (repeat: SPF doesn't stop spam but does a good job of it) but in the future may be improved to include trust factors (ie domain and SPF has been only around for 2 days and its sending 1000 emails to me... strange) There are quite a number of anti-forgery systems around at the moment, and the main ones are SPF, Sender-ID (Microsoft) and DomainKeys (Yahoo), SPF at the moment is the largest used worldwide. (over a million domain names having SPF records) The uptake in New Zealand is pretty small at the moment, but ISP's are starting to add SPF records for their domains. Xtra have added SPF rules for the xtra.co.nz Domain: v=spf1 ip4:210.86.15.0/24 ?all (host -t TXT xtra.co.nz) IHUG have added a SPF rule for ihug hosted domains to include: eg v=spf1 include:_spf.ihug.co.nz -all (host -t TXT _spf.ihug.co.nz) And a lot of Domains (see http://spam.co.nz/spf/working/) have started to add SPF Rules . This list is no where complete at the moment for .NZ (or other domainnames). Also quite a number of NZ domains have broken SPF records for various reasons which (if an ISP is testing for SPF will reject and cause bounces), so its quite important to make your rules correct (see http://www.spam.co.nz/spf/broken - This list is also quite imcomplete) I'm not saying SPF doesn't have its problems, but the major problem (at the moment) is forwarding emails . Ie user(a)ispa.com sends email to user(a)ispb.com and it gets forwarded to user(a)ispc.com. . If user(a)ispc.com checks for SPF it will fail as the user(a)ispa.com email address is coming from ISP B's email server. BUT mechanisms like SRS fix this problem. Mostly importantant is before SPF records are set up for a domain you must know how you users are using your domain. So maybe you think SPF is just something kids play around with and it will never be used for anything important and no one cares about it which is not so as its gaining momentum like just recently the IANA just gave SPF its own DNS RR (SPF) (see http://www.iana.org/assignments/dns-parameters) which will be used instead of the TXT records in the future to SPF records (maybe SPF v3 will use it only) More information can be read at: http://www.openspf.net/ and the mailing list and other information can be read at http://www.openspf.org/ Thanks Craig Whitmore www.spam.co.nz

9 11

RE: [nznog] SPF Uptake in New Zealand
by Nic Wise 14 Jul '05

14 Jul '05

> I'm guessing that this is a precursor to enforcing it for all > Microsoft controlled domains. Though presumably they will > have trouble enforcing it for Microsoft.com, unless they're > already prepping the next version of Exchange to include > spf/senderid support :) > I'm not 100% sure, but I think I read that this is going to be in Exchange 2003 SP2 - I think it's part of the "edge services" thing that's in SP2. Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited. t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

1 0

RE: [nznog] SPF Uptake in New Zealand
by Drew Broadley 14 Jul '05

14 Jul '05

> Just my 2c..... Nothing like a Friday morning rant... I need a V.... s/V/Beer/ ;) Cheers for that summary, it's helped me get my head around SPF, which I've flogged researching for the fear of adding False-Negatives possibilities on-top of my current SA setup (which, incidentally, has been flawless for a few months now). - Drew

1 0

RE: [nznog] SPF Uptake in New Zealand
by Simon Allard 13 Jul '05

13 Jul '05

> > If they set "v=spf1 ip4:210.86.15.0/24 -all" then some mail (for example > > that trademe.co.nz sends out) would get rejected as it would be coming > > from the wrong place > > > > This was a little unclear what I said . trademe.co.nz sends out emails > sometimes from the email address of the trademe user. If a user has email > address of customer(a)xtra.co.nz it will send from that address from trademe > mail server. and if tested for SPF with a -all will fail and get rejected. I can see SPF being a big learning curve to the NZ ISP customer base, once ISP's start enforcing SPF. We still see lots of email from customers who have an ispa email set as their email address but are using our email server because they moved ISP's but didn't want to change email address. I would be surprised if any ISP's don't see this. SPF seems like a very good idea, and will work perfectly for personal domains, but for big ISP's, xtra/clear/ihug etc. It's going to cause a huge influx of unhappy customers if it ever gets implemented. - Simon

2 1

RE: [nznog] SPF Uptake in New Zealand
by Nic Wise 13 Jul '05

13 Jul '05

Hey folks, Noone has mentioned building the SPF strings :) I found this a while back: http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx It's a nice little (online) wizard from MS, which allows you to build the string without having to work out a geekcode-look-alike. AFAIK, they don't store info - just show you the SPF for what you enter. No comment on how effective SPF might be, but the wizard is handy if you don't wanna work out the syntax :) Cheers. Nic, off to add the TXT record to his domains. -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited. t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

4 6

RE: [nznog] SPF Uptake in New Zealand
by Drew Broadley 13 Jul '05

13 Jul '05

> Noone has mentioned building the SPF strings :) I found this a while > back: > > http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx > There is wizard on one of the one links posted by Craig. http://spf.pobox.com/ , http://www.openspf.net/ (some thing) The wizard is on the top left, where it says to enter your domain. - Drew

1 0

nz.pool.ntp.org??
by Simon 13 Jul '05

13 Jul '05

Hi There, Anyone know whats happened to this ntp server(s)? Im getting a connection timeout from a few days ago... # rdate -s nz.pool.ntp.org rdate: connect: Connection timed out Simon

3 3

RE: [nznog] nz.pool.ntp.org??
by Gavin Legge 13 Jul '05

13 Jul '05

Incidentally I tried nslookup on nz.pool.ntp.org a few minutes ago and it timed out. After the third or fourth attempt I got an answer with multiple IP's as expected. Hope that helps. -----Original Message----- From: Drew Broadley [mailto:drew(a)iws.co.nz] Sent: Thursday, 14 July 2005 9:12 a.m. To: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] nz.pool.ntp.org?? > Hi There, Anyone know whats happened to this ntp server(s)? > Im getting a > connection timeout from a few days ago... > > # rdate -s nz.pool.ntp.org > rdate: connect: Connection timed out > > Simon I'm guessing you've tried multiple attempts ? Try a different nameserver in /etc/resolv.conf incase the one you're using has nutted out (for some unkonw reason) on the multiple A records ? - Drew _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

RE: [nznog] nz.pool.ntp.org??
by Drew Broadley 13 Jul '05

13 Jul '05

> Hi There, Anyone know whats happened to this ntp server(s)? > Im getting a > connection timeout from a few days ago... > > # rdate -s nz.pool.ntp.org > rdate: connect: Connection timed out > > Simon I'm guessing you've tried multiple attempts ? Try a different nameserver in /etc/resolv.conf incase the one you're using has nutted out (for some unkonw reason) on the multiple A records ? - Drew

1 0

RE: [nznog] nz.pool.ntp.org??
by Gavin Legge 13 Jul '05

13 Jul '05

Nope - but there is one at IRL - in fact the(one of many?) main reference for NZ. Msltime.irl.cri.nz enjoy -----Original Message----- From: Simon [mailto:dev(a)networker.co.nz] Sent: Thursday, 14 July 2005 9:00 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] nz.pool.ntp.org?? Hi There, Anyone know whats happened to this ntp server(s)? Im getting a connection timeout from a few days ago... # rdate -s nz.pool.ntp.org rdate: connect: Connection timed out Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

Hostile takeover of Indonesia's .it registrar
by Mark Derricutt 13 Jul '05

13 Jul '05

Just saw a discussion of a hostile takeover of the .it domain management on IRC (#joiito @ freenode ) and thought it might be of interest to you NZNOGers: http://lists.apdip.net/pipermail/igovap/Week-of-Mon-20050711/000374.html Mark

2 2

ENUM Consultation Report by M-co for InternetNZ
by Michael Sutton 12 Jul '05

12 Jul '05

Members of NZNOG. On behalf of InternetNZ's ENUM Task Force we are pleased to provide you with a link to the full M-co report, "The staging of the first ENUM trial in New Zealand" (~100pages) <http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete .pdf> http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf This report was commissioned to provide advice to InternetNZ including recommendations and questions to be addressed in respect of ENUM's implementation in New Zealand. In parallel to the preparation and release of this report InternetNZ has agreed with the Telecommunication Carriers Forum (TCF) to form a joint Industry ENUM Steering Group as part of our initiative to provide a platform to plan and implement ENUM for New Zealand. We look forward to receiving feedback with a nominal close off date of July 21st 2005. If you require an extended period please let us know by that date. All comments should be sent to <mailto:enum-tf(a)internetnz.net.nz> mailto:enum-tf(a)internetnz.net.nz. Written submissions can also sent to our Office at: ENUM Task Force, InternetNZ, P.O.Box 11-881, Wellington, New Zealand, or can be faxed to the Task Force at +64 4 495 2115. The Consultation Report is also to being printed and to receive a physical copy please send a request and mailing address to Jordan Carter at <mailto:jordan(a)internetnz.net.nz> mailto:jordan(a)internetnz.net.nz. The Report in subsections (PDF format), are also available on the InternetNZ web site <http://www.internetnz.net.nz/public/enum/> http://www.internetnz.net.nz/public/enum/. You will also find links to the ENUM workshop and initiatives at this URL. You are welcome to distribute this Report to anyone this would be of interest too. Best Regards Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chairman - Enum Task Force InternetNZ Project Manager - UCI PUA Enum Prototype Telephone: +64 4 475 9235 Mobile: +64 21 305500 InternetNZ: +64 4 4721600 ext 730 <mailto:michael.sutton(a)internetnz.net.nz> mailto:michael.sutton(a)internetnz.net.nz> [ Please note this email is in HTML format to prevent long URL links being broken - my apologies to those who prefer plain text]

1 0

Not quite 255
by Juha Saarinen 10 Jul '05

10 Jul '05

Intelenet-Communications-Intelenet-Communications.so-6-0-0.ar3.LAX1.gblx.net -- Juha

1 0

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

10 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.118.128.0/18^18-29, 203.173.192.0/18^18-29, 203.96.192.0/19^19-29, 202.46.160.0/20^20-29, 202.126.80.0/20^20-29, 203.109.144.0/20^20-29, 203.173.144.0/20^20-29, 203.109.192.0/21^21-29, 203.173.136.0/21^21-29, 203.173.168.0/21^21-29, 202.50.188.0/22^22-29, 203.109.132.0/22^22-29, 203.109.252.0/22^22-29, 203.173.164.0/22^22-29, 203.173.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 203.173.160.0/23^23-29, 203.173.186.0/23^23-29, 192.107.113.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.109.163.0/24^24-29, 203.109.230.0/24^24-29, 203.109.233.0/24^24-29, 203.173.162.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050518 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.109.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 203.109.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.173.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 203.173.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 202.49.140.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 202.49.140.0/24 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR

1 0

Noc Contact list.
by Simon Lyall 09 Jul '05

09 Jul '05

Okay first up a big apology for getting behind with updates to this list, I've just gone though mail box and grabbed all the old ones so I have should have all the updates. Which means if they page isn't correct then please send me a new update. http://www.usenet.net.nz/noc/ Note that I'm not just including ISPs on the list but hosting companies and other large Internet connected organisations. Basically people who might need to be connected in a hurry. PS: I believe APNIC lets you do role based owners of IPs and AS numbers now, so there isn't really an excuse to not have your details updated 8 months after somebody leaves.. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 203.97.231.224/28^28-29, 203.79.85.80/29, 203.109.195.72/29, 210.48.103.0/29, 210.48.103.112/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050621 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 203.97.231.224/28^28-29, 203.79.85.80/29, 203.109.195.72/29, 210.48.103.0/29, 210.48.103.112/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9343 descr: Route set advertised to AS9439 by DTS - AS9343 members: 192.100.53.0/24, 192.173.17.0/24, 202.68.80.0/20^20-24, 202.20.0.0/21^21-24, 202.49.158.0/23^23-24, 202.36.173.0/24, 202.36.204.0/23^23-24, 202.37.197.0/24, 202.46.190.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: technical(a)dts.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040114 changed: rpsl-admin(a)nzix.net 20040624 changed: rpsl-admin(a)nzix.net 20041006 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9343 descr: advertised to AS9439 by DTS - AS9343 members: 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.36.204.0/23^23-29, 202.49.158.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64522 descr: advertised to AS9439 by Change Training Consultants Ltd - AS64522 members: 202.49.158.112/28^28-29, 202.20.7.160/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: hamish(a)change.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050201 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64522 descr: advertised to AS9439 by Change Training Consultants Ltd - AS64522 members: 202.20.5.224/27^27-29, 202.20.7.160/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: hamish(a)change.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

[ot] nz opensource websites
by Barry Murphy 07 Jul '05

07 Jul '05

Hey guys, Bit off topic but it's Friday and the weeks been slow, just a few more hours now before beer time. Anyways, if you run an opensource website or an ISP and you'd like to offer downloads to save on your precious international bandwidth, then you might want to take a look at this, the catch, you need to be wix or ape connected as it's an anycast range. http://www.isp.fast.co.nz/mirror.htm The above link will give instructions to showing your name on the page, i.e. http://www.linuxnet.isp.fast.co.nz (Single word name) http://www.kiwi-online.isp.fast.co.nz (2 word name) This may save you quite a bit of traffic on your international connectivity if you have links from your homepage. If anything is out of date or you'd like to request other mirrors, please don't hesitate to contact me. Cheers Regards Barry

2 1

[nznog] IANA IPv4 allocations and bogon updates: 89/8, 90/8 and 91/8
by Rob Thomas 05 Jul '05

05 Jul '05

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those of you who receive this note in multiple forums. ] Hi, team. The numerous Team Cymru bogon projects have been updated as of 30 JUN 2005 to reflect the following IANA allocation made on 30 JUN 2005: 089/8 Jun 05 RIPE NCC (whois.ripe.net) 090/8 Jun 05 RIPE NCC (whois.ripe.net) 091/8 Jun 05 RIPE NCC (whois.ripe.net) IANA allocations change over time, so please check regularly to ensure you have the latest filters if you are not using the bogon BGP feed(s). We do announce updates to the bogon projects to sundry lists, such as the bogon-announce list. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the Team Cymru master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/> A quick summary of the documents and projects that have been updated include the following: HTTP The Bogon List - <http://www.cymru.com/Documents/bogon-list.html> The Text Bogon Lists - <http://www.cymru.com/Documents/bogon-bn-nonagg.txt> - <http://www.cymru.com/Documents/bogon-bn-agg.txt> Secure BIND Template - <http://www.cymru.com/Documents/secure-bind-template.html> Secure IOS Template (Cisco) - <http://www.cymru.com/Documents/secure-ios-template.html> Secure BGP Template (Cisco) - <http://www.cymru.com/Documents/secure-bgp-template.html> Secure JUNOS Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-template.htm> Secure JUNOS BGP Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-bgp-template.htm> Ingress Prefix Filter Templates, Loose and Strict (Cisco) - <ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix- Filter-Templates/> Ingress Prefix Filter Template, Loose (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix-filter-loose.htm> Ingress Prefix Filter Template, Strict (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix-filter-strict.htm> BGP Bogon route-server for AUTOMATED updates of bogon filters - All bogon route-server peers have already received the appropriate BGP prefix updates. - <http://www.cymru.com/BGP/bogon-rs.html> RADb fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#radb> RIPE NCC fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#ripe> DNS Bogon (bogons.cymru.com) zone - <http://www.cymru.com/Bogons/index.html#dns> Monitoring Bogon prefix monitoring - <http://www.cymru.com/BGP/robbgp-bogon.html> Bogus ASN monitoring - <http://www.cymru.com/BGP/asnbogusrep.html> Please feel free to contact Team Cymru <team-cymru(a)cymru.com> with any comments, questions, or concerns. Thank you for your continued support. Thanks! Rob. - -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQswL+1kX3QAo5sgJAQHcQgP/RDehEvRBiaN0nFApyeQroJzb6NfOmd88 VScVbNj08xn7jkovVjXndQ8roQzDEVhLZyhHa0+dp8cLEETnjVYXNd6Ir9/bajRj 3mybhQefzaPlKJjLOhjWmoU3maUMN8oTrWGkE5YQOe+6Ef8HDrI0inT+mhhyqdhF V/I5kb6mNBw= =qVJI -----END PGP SIGNATURE-----

1 0

Transfer of management now complete
by Elly Tawhai 03 Jul '05

03 Jul '05

Hi, Transfer of historical IP address ranges ---------------------------------------- The following address ranges were transferred from NZTelecom to APNIC's management on 1 July 2005: 202.27/16 202.37/16 202.36/16 202.49/16 202.50/16 For more information about how to update your resources, please refer to section 4 of "Historical resource policies" at: http://www.apnic.net/docs/policy/historical-resource-policies.html#4 If you have further queries, please feel free to contact APNIC at: <helpdesk(a)apnic.net> Regards, APNIC Secretariat

1 0

Another Technical Announcement
by Richard Naylor 03 Jul '05

03 Jul '05

Wearing my R2 hat.... R2 has recently installed a streaming media server at the Palmerston North (PNIX) internet exchange in addition to servers already at WIX and APE. We also have a server located in California, USA to serve content to New Zealanders overseas. These have been tested during the current Lions Rugby tour and are now fully operational. They will shortly be carrying the previously announced RNZ service. This announcement is to advise that all the streams carried by R2 on behalf of Rhema Broadcasting Group (RBG) are now available on all servers. These streams are Radio Rhema www.rhema.co.nz Southern Star www.sstar.co.nz LifeFM www.lifefm.co.nz ShineTV www.shinetv.co.nz The audio streams are available in bit rates up to 64kbps and TV up to 384kbps. We expect to make a 2Mbps TV stream available by the end of the month. Details of the streams is available via the station websites listed above. RBG content is both live streams and on-demand content. We have chosen to deploy a multi-homed architecture for the following reasons: 1. Greater diversity and redundancy than a single site/provider architecture. 2. Reduced network latency for improved streaming performance. 3. Shortest path for broadband consumers (reducing network congestion for Operators). 4. Scalability, allowing us to add servers at new exchanges in the future. 5. To minimise national transit costs for the ISP's of customers using the content. 6. Lowest cost to serve content. 7. Ability to better serve international viewers and listeners of NZ stations. The servers have a globally consistent anycast IP address which is advertised at each exchange to ensure that the content is delivered from the nearest server to the consumer. In order to get the best performance we recommend that you peer directly with the anycast routers at all the exchanges where you have connectivity. Any peering questions should be directed to me at richard.naylor(a)r2.co.nz Thanks Richard

1 1

Re: [nznog] Archived stream of this morning's Nat Radio programme(s)
by Webmaster 03 Jul '05

03 Jul '05

There is a long standing caching (as I understand it) problem. If you press reload/refresh a couple of time it clears the error. cheers, Richard Hulse >>> Dan Clark <dan(a)synaptic.net.nz> 4/07/2005 11:35 >>> used to be http://www.radionz.co.nz/audio I think, for some reason it go's to some broken Telecom Xtra link. Dan Juha Saarinen wrote: > Is there one somewhere? RadioNZ? R2? > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Archived stream of this morning's Nat Radio programme(s)
by Juha Saarinen 03 Jul '05

03 Jul '05

Is there one somewhere? RadioNZ? R2? -- Juha

2 2

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

03 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

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

03 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Jun '05

30 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: Smartlinx3 descr: WIX peering at '202.7.1.20' descr: see Citylink RT job #2729 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24385 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Jun '05

30 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW DELETED: route-set: AS9439:RS-ROUTES:AS24385 descr: Route set advertised to AS9439 by Smartlinx3 - AS24385 members: 218.100.26.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Jun '05

30 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24385 descr: Route set advertised to AS9439 by Smartlinx3 - AS24385 members: 218.100.26.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

Re: [nznog] Technical Announcement
by Richard Naylor 30 Jun '05

30 Jun '05

At 10:14 PM 6/29/2005 +1200, Simon Lyall wrote: >On Wed, 29 Jun 2005, Jamie Baddeley wrote: > > Have you considered multicast as an option, and if so, what stopped you > > from deploying it? Client support or Network support? > >Does anyone have full end to end support of multicast? I would guess with >bitstream and people having layer-2 all the way it might be possible to >do it these days. In a pure L2 network multicast is a dangerous technology. Think of what happens to a 10meg user when a 100meg user kicks off a 25meg multicast stream. The trend seems to be to use multicast inside tunnels in this environment. Thats the way the Access Grid folks are going. It also allows user groups within a network to opt in and out of multicast sessions. Theres quite a few tunnels tools around. >Not sure what it would be any practical use for though. Lots of chickens >and eggs here. yes. A few "broken network" days ahead. Multicast is good for synchronous events - like TV watching or LOTR Premieres etc. But for asynchronous events - like day to day watching of video, which is tending towards "on-demand", then multicast has almost no value. With the usual availability of bandwidth, I feel multicast is going to be of declining importance but will be implemented more for niche applications, which will become more important in themselves. The "tv" world is fascinated by "video on demand" and the radio (Audio) world is fascinated by Podcasting (aka on-demand listening - mobile). Neither of these is aided by multicast and in themselves they don't impose huge demands on both servers and networks. What we do know is 50x 2meg streams doesn't require 100Mbps. The technology certainly doesn't work that way - the playout buffer is your friend. So unicast streams are not overly heavy on the network or the server. Having said all that, we will be playing with multicast and probably making it available. The other thing we'll be playing with is better quality and alternate compressions. We're very close to be able to originate those nice HD streams we demo'd last year. So maybe NZNOG-06 will be in 10Mbps HD streams....... Rich

2 1

RE: [nznog] Technical Announcement
by Richard Naylor 30 Jun '05

30 Jun '05

At 02:26 PM 7/1/2005 +1200, Simon Allard wrote: > > > > In a pure L2 network multicast is a dangerous technology. Think of >what > > happens to a 10meg user when a 100meg user kicks off a 25meg multicast > > stream. > >But doesn't that depend on how your switches are setup?. My >understanding is the use of IGMP fixes this problem. The switch will >only sent that multicast packets to switch ports which want it. > >(of course the switch has to support IGMP) Having a bad day. THat was teh 2nd attempt to send....think I may just go for a quiet walk and see if I can find whats left of my brain......

1 0

RE: [nznog] Technical Announcement
by Simon Allard 30 Jun '05

30 Jun '05

> > In a pure L2 network multicast is a dangerous technology. Think of what > happens to a 10meg user when a 100meg user kicks off a 25meg multicast > stream. But doesn't that depend on how your switches are setup?. My understanding is the use of IGMP fixes this problem. The switch will only sent that multicast packets to switch ports which want it. (of course the switch has to support IGMP)

1 0

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

30 Jun '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference We're in the early stages of planning our next conference, which is to be held in Wellington. We're now working towards dates of 22-24 March, 2006. That's the week before the scheduled ICANN meeting. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of the Auckland, Palmerston North and Wellington exchanges, and some information on others under construction. About This Mailing List This list has around 850 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

Re: NZ IP-Range (nzip.meta.net.nz)
by Drew Broadley 30 Jun '05

30 Jun '05

Sorry to hijack the topic slightly, Could the person from the origination IPs please stop sucking the xml subnet file every 5 minutes, it only gets updated ONCE a day! 202.27.251.36 - - [01/Jul/2005:08:49:38 +1200] "GET /files/nzip/nzsubnets.xml HTTP/1.0" 200 17498 "-" "-" 202.27.251.34 - - [01/Jul/2005:08:51:08 +1200] "GET /files/nzip/nzsubnets.xml HTTP/1.0" 200 17498 "-" "-" I have blocked you until further notice. If you would like to contact me offlist to discuss this bandwidth rapage, that would be appreciated :) That will be all. - Drew P.S TGIF

1 0

DSL Tails in NZ
by Sam Sarkis 30 Jun '05

30 Jun '05

Hey All, We are looking for around 50 - 60 DSL tails in NZ for our customers. Is there a way we can resell DSL in NZ or a way we can get a Layer 2 Hand off for DSL Tails ? These connections are required all over NZ. Regards Sam Sarkis United IP Director Ph 61 2 8825 5586 Fax 61 2 8825 5577 ======================================================================== This message has been scanned for spam & viruses by Mail Sleuth. To report SPAM forward the message to: spam(a)mailsleuth.com.au Mail Sleuth www.mailsleuth.com.au ========================================================================

2 1

RE: [nznog] NZ IP-Range
by Kerry Milestone 30 Jun '05

30 Jun '05

Hi there, but from the top of that file it grabs it states: # # Note that this is *not* an definitive guide, and does not cover all of the # APNIC ranges. (see whois.apnic.net) is there a definitive guide? Kerry. ________________________________ From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Thursday, 30 June 2005 9:30 a.m. To: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range I got this script from Paul of linuxsystems, grabs the APNIC IP database and compiles a list of NZ ip ranges: #!/usr/local/bin/php <?php $in_file = "ftp://ftp.apnic.net/pub/apnic/dbase/data/country-ipv4.lst"; // $in_file = "country-ipv4.lst"; $out_file = "nzipranges.txt"; $handle_input = @fopen($in_file,"r") or die("Unable to open $in_file\n\n"); $handle_output = fopen($out_file, "w"); $now = date ("r"); fwrite ($handle_output,"# Generated: $now\n\n"); while (!feof($handle_input)) { $buffer = fgets($handle_input); if ( ereg ( "nz", $buffer) ) { // echo $buffer; $this_range = trim(preg_replace ( "#([\d\.]+) \- [\d\.]+ : [\d\.]+(\/\d+) .+#","$1$2", $buffer )); fwrite ($handle_output,"\n" . $this_range); } } fclose($handle_input); fwrite ($handle_output,"\n"); fclose($handle_output); ?> ----- Original Message ----- From: James J. Guidera <mailto:james(a)miracle.co.nz> To: NZNOG(a)list.waikato.ac.nz Sent: Thursday, June 30, 2005 9:00 AM Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614 ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

RE: [nznog] NZ IP-Range
by Kerry Milestone 29 Jun '05

29 Jun '05

I know what I asked, 'tis why I did. I have often wondered about the fact that the internet can _be_ definitive only for the moment its queried. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 30 June 2005 4:27 p.m. To: Steve Phillips Cc: Kerry Milestone Subject: Re: [nznog] NZ IP-Range Steve Phillips wrote: > Think of what you ask. The simple answer is "no" Oh gowon... I know you've got it. Let Kerry have your definitive NZIP guide now, and don't be so mean.

4 4

police mail tech
by jamie.baddeley＠vpc.co.nz 29 Jun '05

29 Jun '05

Can someone from NZ Police please contact me offlist. thanks jamie

2 1

RE: [nznog] NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Cheers for the warning, -----Original Message----- From: Russell Fulton [mailto:r.fulton(a)auckland.ac.nz] Sent: Thursday, 30 June 2005 11:40 a.m. Cc: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range Steve Phillips wrote: > > Just be aware that these solutions will give you a list of "NZ IP > Ranges" but may not be New Zealand based netwise. > > If you are looking for traffic originating in NZ and not traversing any > international links then thats an entirely different story and only your > ISP can provide you with this. > > If this is a bill saving exercise then it may pay to be a little prudent. > I echo Steve's warning. It really depends how relaible you need the data to be. Back in the days when everything went throug NZGate at Waikato they kept lists of NZ addresses based upon the BGP tables. These contain quite a few small blocks of non NZ addresses -- mainly belonging to large multination companies and Telcos. I imagine it has got worse not better. If accuracy is crucial then you really need something based on the routing tables that gets updated frequently. Russell

1 0

NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614

9 10

Re: [nznog] Technical Announcement
by Webmaster 29 Jun '05

29 Jun '05

> Have you considered multicast as an option, and if so, what stopped you > from deploying it? Client support or Network support? Multicast is only usefull for live streams (which we are still working on rights issues for). I remember hearing a lot about Multicast at the NAB coference in 1997. The website is still there (http://www.ipmulticast.com/) For ISPs who peer with us in NZ, we'd certainly look at enabling it (subject to some solid testing being done of course). cheers, Richard

1 0

RE: [nznog] NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Thanks for the script Paul, might have look into the software and IP2location for the windows based machines, and script for linux. James ________________________________ From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Thursday, 30 June 2005 9:30 a.m. To: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range I got this script from Paul of linuxsystems, grabs the APNIC IP database and compiles a list of NZ ip ranges: #!/usr/local/bin/php <?php $in_file = "ftp://ftp.apnic.net/pub/apnic/dbase/data/country-ipv4.lst"; // $in_file = "country-ipv4.lst"; $out_file = "nzipranges.txt"; $handle_input = @fopen($in_file,"r") or die("Unable to open $in_file\n\n"); $handle_output = fopen($out_file, "w"); $now = date ("r"); fwrite ($handle_output,"# Generated: $now\n\n"); while (!feof($handle_input)) { $buffer = fgets($handle_input); if ( ereg ( "nz", $buffer) ) { // echo $buffer; $this_range = trim(preg_replace ( "#([\d\.]+) \- [\d\.]+ : [\d\.]+(\/\d+) .+#","$1$2", $buffer )); fwrite ($handle_output,"\n" . $this_range); } } fclose($handle_input); fwrite ($handle_output,"\n"); fclose($handle_output); ?> ----- Original Message ----- From: James J. Guidera <mailto:james(a)miracle.co.nz> To: NZNOG(a)list.waikato.ac.nz Sent: Thursday, June 30, 2005 9:00 AM Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614 ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] NZ IP-Range
by Mark Karena 29 Jun '05

29 Jun '05

Not sure if there is a single list within the community but there are places that sell IP<-> location software that pulls info from APNIC, ARIN etc. Here is one place. http://www.ip2location.com/?AfID=23224 HTH, ------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING (07) 853 6060 (021) 141 3792 _____ From: James J. Guidera [mailto:james(a)miracle.co.nz] Sent: Thursday, 30 June 2005 9:00 a.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614

1 0

Re: [nznog] Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

>>> Barry Murphy <barry(a)unix.co.nz> 06/29/05 2:38 PM >>> > For providers not connected to the peering exchanges > will the content be delivered from the USA? Yes, at the 'standard' rate of 16 or 24 kbs. This rate is on a par with other Public Broadcasters. Peering ISPs get higher rates from the local servers. > This would mean those providers will only get the USA > content and wont be allowed to hear the copyright audio? NZ Restricted audio, actually. We use the exchange infrastructure to limit the distribution of some content. At the start there won't be any NZ restricted content (apart from Enzology). We expect demand for the service to be quite high, and don't want to have to sort between help desk calls from consumers who's ISPs do not peer and people who have a genuine problem. R.

3 2

RE: [nznog] Technical Announcement
by Regan Murphy 28 Jun '05

28 Jun '05

>>For providers not connected to the peering exchanges such as telecom and telstra The way I see it is that while these two providers are connected to the one or more exchanges, its just that they don't openly peer with everybody at the exchanges. Therefore they may choose to peer directly with radionz at one of these exchanges thus enabling the content to be provided to their subscribers. -- Regan -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Wednesday, 29 June 2005 2:38 p.m. To: Webmaster; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Technical Announcement Hi, For providers not connected to the peering exchanges such as telecom and telstra, will the content be delivered from the USA? I'm guessing this is the case so you don't have to purchase domestic links from those providers. This would mean those providers will only get the USA content and wont be allowed to hear the copyright audio? Thanks Barry P.S. www.ispmap.co.nz is backup and running people, sorry the hardware died and took a while to replace. ----- Original Message ----- From: "Webmaster" <Webmaster(a)radionz.co.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Wednesday, June 29, 2005 2:24 PM Subject: [nznog] Technical Announcement > Hi, > > Radio New Zealand has recently installed content servers at the > Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet > exchanges. We also have a server located in California, USA to serve > content to New Zealanders overseas. > > These servers have been deployed within the R2 infrastructure and will > be used for the soon-to-be-launched on-demand and simulcast audio > service. > There will be a range of on-demand content from programmes broadcast > on both networks, and we are hoping to provide live streams of > National Radio and Concert FM (subject to resolving some outstanding > copyright issues). When the service commences we expect about 60 hours > of new content to be available each week. The servers will also be > used by Radio NZ International for their on-demand and simulcast audio. > > All streams will initially be 16 kbs maximum, and this may increase to > 24 kbs once we have a handle on traffic flows. Everyone will be able > to access content at this rate. > > We have chosen to deploy a multi-homed architecture for the following > reasons: > 1. Greater diversity and redundancy than a single site/provider > architecture. > 2. Reduced network latency for improved streaming performance. > 3. Shortest path for broadband consumers (reducing network congestion > for Operators). > 4. Scalability, allowing us to add servers at new exchanges in the > future. > 5. To minimise national transit costs for the ISP's of customers using > the content. > 6. Lowest cost to serve content. > > The servers have a globally consistent anycast IP address which will > be advertised at each exchange to ensure that the content is delivered > from the nearest server to the consumer. > > As new exchanges are installed throughout the country we intend to > deploy content servers at them, subject to certain minimum criteria > being met. This also includes MUSH style networks outlined in the NZ > Government's Digital Strategy. > > In order to get the best performance we recommend that you peer > directly with the anycast routers at all the exchanges where you have > connectivity. > > For those who wish to peer locally an enhanced service is available > from the NZ exchange-based content servers. Maximum data rates will > increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for > live streams. The live simulcasts (when available) will be available > in stereo at these rates. > > Where content is limited to NZ for copyright reasons there will be no > international route, meaning customers of non-peering ISPs will not be > able to access the content. This is currently the case with the > Enzology series (www.radionz.co.nz/enzology/) > > Please contact our peering coordinator at peering(a)radionz.co.nz if you > need to establish a peering session with our content servers. > > We will be maintaining a list of peers and a help page on our new > website so that consumers can be informed about how to access the > enhanced service. > > Operators may expect increased help desk activity due to their > customers not being able to access NZ restricted content, or asking > for access to the enhanced service. > > We are publishing our intentions to this list in advance of the launch > so that Operators can prepare for what we expect will be a very > popular service with the 686,000 people who listen each week to > National Radio and Concert FM. > > We expect to go live in 2-3 weeks. > > > regards, > > > Richard Hulse > New Media Manager > Radio New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

Hi, Radio New Zealand has recently installed content servers at the Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet exchanges. We also have a server located in California, USA to serve content to New Zealanders overseas. These servers have been deployed within the R2 infrastructure and will be used for the soon-to-be-launched on-demand and simulcast audio service. There will be a range of on-demand content from programmes broadcast on both networks, and we are hoping to provide live streams of National Radio and Concert FM (subject to resolving some outstanding copyright issues). When the service commences we expect about 60 hours of new content to be available each week. The servers will also be used by Radio NZ International for their on-demand and simulcast audio. All streams will initially be 16 kbs maximum, and this may increase to 24 kbs once we have a handle on traffic flows. Everyone will be able to access content at this rate. We have chosen to deploy a multi-homed architecture for the following reasons: 1. Greater diversity and redundancy than a single site/provider architecture. 2. Reduced network latency for improved streaming performance. 3. Shortest path for broadband consumers (reducing network congestion for Operators). 4. Scalability, allowing us to add servers at new exchanges in the future. 5. To minimise national transit costs for the ISP's of customers using the content. 6. Lowest cost to serve content. The servers have a globally consistent anycast IP address which will be advertised at each exchange to ensure that the content is delivered from the nearest server to the consumer. As new exchanges are installed throughout the country we intend to deploy content servers at them, subject to certain minimum criteria being met. This also includes MUSH style networks outlined in the NZ Government's Digital Strategy. In order to get the best performance we recommend that you peer directly with the anycast routers at all the exchanges where you have connectivity. For those who wish to peer locally an enhanced service is available from the NZ exchange-based content servers. Maximum data rates will increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for live streams. The live simulcasts (when available) will be available in stereo at these rates. Where content is limited to NZ for copyright reasons there will be no international route, meaning customers of non-peering ISPs will not be able to access the content. This is currently the case with the Enzology series (www.radionz.co.nz/enzology/) Please contact our peering coordinator at peering(a)radionz.co.nz if you need to establish a peering session with our content servers. We will be maintaining a list of peers and a help page on our new website so that consumers can be informed about how to access the enhanced service. Operators may expect increased help desk activity due to their customers not being able to access NZ restricted content, or asking for access to the enhanced service. We are publishing our intentions to this list in advance of the launch so that Operators can prepare for what we expect will be a very popular service with the 686,000 people who listen each week to National Radio and Concert FM. We expect to go live in 2-3 weeks. regards, Richard Hulse New Media Manager Radio New Zealand

2 1

Telstra Problems
by Lyndon 27 Jun '05

27 Jun '05

I took a traceroute this morning as Telstra were fixing the issue, it was indeed interesting. First 3 hops are removed (my firewall, local router and next hop). I am connected by Cable Modem. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * 20 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 153 ms 153 ms 154 ms so.jb.wils.telstraclear.net [203.98.42.66] 9 155 ms 156 ms 154 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 148 ms 147 ms 147 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 156 ms 157 ms 154 ms 0.so-1-1-0.XL1.LAX7.ALTER.NET [152.63.57.78] 12 154 ms 153 ms 155 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41] 13 148 ms 148 ms 146 ms so-2-0-0.gar1.LosAngeles1.Level3.net [209.0.227.37] 14 148 ms 149 ms 146 ms so-0-1-0.bbr2.LosAngeles1.Level3.net [4.68.96.89] 15 167 ms 169 ms 168 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157] 16 167 ms 168 ms 168 ms ae-23-54.car3.SanJose1.Level3.net [4.68.123.109] 17 217 ms 213 ms 213 ms unknown.Level3.net [64.152.102.58] 18 205 ms 207 ms 205 ms po3-0.gw1.akl1.asianetcom.net [202.147.55.213] 19 206 ms 204 ms 204 ms ip-202-147-45-74.asianetcom.net [202.147.45.74] 20 206 ms 205 ms 206 ms 203-109-156-100.ihug.net [203.109.156.100] 21 206 ms 204 ms 205 ms oldresolver3.ihug.co.nz [202.36.94.1] Cheers L

1 0

RE: [nznog] TelstraClear/ICONZ Fault (IHUG as well?)
by Simon Allard 27 Jun '05

27 Jun '05

There was earlier, we had to shut down our BGP session to TCL because of some weirdness in the BGP advertisements from TCL. It has been resolved now and the BGP session was brought back up. > -----Original Message----- > From: Tony Wicks [mailto:nzog(a)road.gen.nz] > Sent: Tuesday, 28 June 2005 9:55 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] TelstraClear/ICONZ Fault (IHUG as well?) > > No issues to Ihug via TCL Auckland. > > > [root(a)fire root]# traceroute ihug.co.nz > traceroute to ihug.co.nz (203.109.252.75), 30 hops max, 38 byte packets > 1 router2 (203.97.9.132) 0.982 ms 1.136 ms 0.993 ms > 2 203.97.85.221 (203.97.85.221) 25.973 ms 27.754 ms 25.487 ms > 3 ge9-0-954.u11.pnr.telstraclear.net (218.101.61.41) 25.982 ms > 30.724 ms 30.487 ms > 4 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 27.482 ms > 30.195 ms 29.486 ms > 5 g1-926.u12.brh.telstraclear.net (218.101.61.35) 26.982 ms 27.230 > ms 26.486 ms > 6 lnk1-ihug-ge-1-0-1642.u12.telstraclear.net (203.98.18.162) 28.482 > ms 30.234 ms 25.486 ms > 7 203-109-156-97.ihug.net (203.109.156.97) 35.982 ms 36.202 ms > 45.986 ms > 8 ihug.co.nz (203.109.252.75) 26.974 ms 28.200 ms 25.985 ms > [root(a)fire root]# > Simon wrote: > > Michael Bordignon wrote: > > > >>> Since then we have about 55% packet loss, with ICONZ as at 12:05 > >> > >> > >> saying that they have not been given an ETA by TelstraClear. > >> > >>> 12 hours of substandard performance with no ETA seems a bit poor to > >> > >> > >> me. > >> > >>> If anyone has any updates on this please feel free to let me know. > >> > >> > >> > >> Same here - unusable. > > > > > > I am possibly seeing the same problem here? we are on tesltraclear DSL > > and cant get to any of IHUG's network... Anyone seeing this same issue > > this morning? Other major ISP's are fine. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] TelstraClear/ICONZ Fault
by Michael Bordignon 27 Jun '05

27 Jun '05

> Since then we have about 55% packet loss, with ICONZ as at 12:05 saying that they have not been given an ETA by TelstraClear. > 12 hours of substandard performance with no ETA seems a bit poor to me. > If anyone has any updates on this please feel free to let me know. Same here - unusable. Michael

5 5

RE: [nznog] Trademe problems ?
by Jay Rama 27 Jun '05

27 Jun '05

Hi Simon, Telstra/Paradise are currently having some DNS issues, there is a quickfix in place, but I believe problems still persist... Regards, Jay ________________________________ From: Simon Byrnand [mailto:simon(a)igrin.co.nz] Sent: Tue 28/06/2005 9:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Trademe problems ? Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trademe problems ?
by Simon Byrnand 27 Jun '05

27 Jun '05

Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon

3 2

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

26 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: Route set advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/24^24-29, 202.49.135.0/24^24-29, 202.49.133.0/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 20050610 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 202.49.128.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050627 source: NZRR

1 0

APNIC Updates @ Telstra
by Jonathan Brewer 26 Jun '05

26 Jun '05

Hi Folks, Would someone at Telstra capable of performing updates to Telstra-managed AS9436 please contact me off-list? Thanks, Jonathan Brewer

1 0

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

23 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.4.0/24^24-29, 202.7.6.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: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050228 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 202.7.6.0/24^24-29, 203.118.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: noc(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050621 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR

1 0

TelstraClear/ICONZ Fault
by Chris Woodrow 22 Jun '05

22 Jun '05

Apparently TelstraClear made some 'changes' to the primary ICONZ WGTN-AUCK circuit around midnight last night. Since then we have about 55% packet loss, with ICONZ as at 12:05 saying that they have not been given an ETA by TelstraClear. 12 hours of substandard performance with no ETA seems a bit poor to me. If anyone has any updates on this please feel free to let me know. Regards Chris Woodrow BDT

1 0

Re: [nznog] Anyone awake at Ihug NOC/Security?
by Mark Foster 21 Jun '05

21 Jun '05

Glen Wilson wrote: *snip* > I enquired about your email today and was told that you had lodged a fault > regarding smtp relay attempts in which the offending ip was not an Ihug > ip and the issue was dropped. It was also brought to my attention > that in a follow up email from you to the abuse mailbox stated the > following,... > > "If I don't get some sort of acknowledgement of my reports soon I will > start dropping ihug IP ranges at the highest supernet I can see... " Unfortunately you're taking my frustration and desire-to-get-SOME-sort-of-response out of context, and its a shame you did this on NZNOG. I don't make a habit of misreporting complaints, and i'm wary of the fact that as an end user (at least in the capacity I was reporting this particular abuse case in) I don't exactly have any 'clout'. So I was simply reporting a fact - that my frustration level was such that i'd rather add all of ihug to my RBL than deal with the ongoing virus payload that was (apparently) being ignored. I have sent another response offlist but I felt the need to make it clear that I am not a cry-wolf type and am familiar with the concepts of dns lookup and whois. ;-) Good luck to those at ihug with the thankless task of clearing that backlog! Mark.

5 4

RE: [nznog] Anyone awake at Ihug NOC/Security?
by Blair Robson 21 Jun '05

21 Jun '05

It was just a suggestion, that email was a few days old and none of you guys had responded (obviously cos it was sorted) - I was just trying to help. >> All your comments are just rumour and speculation. Yeah, absolutely I don't _know_ anything and I said that. Again just a suggestion. _b -----Original Message----- From: Simon Allard [mailto:simona(a)staff.iinet.net.au] Sent: Wednesday, 22 June 2005 9:23 a.m. To: Blair Robson; nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? Blair. Please don't comment on ihug matters which you know nothing about. All your comments are just rumour and speculation. None of the senior type jobs have gone. Yes some have left for other jobs, but they have all been replaced with new staff. abuse(a)iinet.net.au has no visibility into the ihug NZ network, so they will be no help to you. abuse(a)ihug.co.nz is the correct email to use. For the record, Mark was contacted minutes after his email and his problem was sorted. Cheers Simon Allard IHUG Security Monkey > -----Original Message----- > From: Blair Robson [mailto:blair.robson(a)ihug.co.nz] > Sent: Wednesday, 22 June 2005 2:52 a.m. > To: jon.brewer(a)att.net; 'Mark Foster'; nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > Seriously - try abuse(a)iinet.net.au , explain that you have tried > contacting > abuse(a)ihug.co.nz (I assume you have?) > I don't know weather that will work or not, but I do know that nearly all > the senior people at Ihug in NZ are gone..And I think you will find Simon > no > longer works for Ihug. > As far as I can gather everything is being run or in the process of being > run from Perth now. > > Blair > > -----Original Message----- > From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] > Sent: Tuesday, 21 June 2005 3:25 p.m. > To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > We too need a reply from Ihug security, and have unanswered mail in to > noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a > better address? > > To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated > 30 GB of http traffic in the past month for one of our customers - > repeatedly downloading one file. (2400 times at last count) Our customer > would rather like it to stop. > > JB > > -------------- Original message from "Blair Robson" > <blair.robson(a)ihug.co.nz>: -------------- > > > > abuse(a)iinet ? > > > > > > > > -----Original Message----- > > From: Mark Foster [mailto:blakjak(a)blakjak.net] > > Sent: Wednesday, 15 June 2005 5:05 p.m. > > To: nznog(a)list.waikato.ac.nz > > Subject: [nznog] Anyone awake at Ihug NOC/Security? > > > > Repeat emails over the last week or two to abuse@ and noc@ havn't had > any > > sort of response or acknowledgement - can someone from Ihug NOC or > > security please contact me offlist. > > > > Thanks > > Mark. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Anyone awake at Ihug NOC/Security?
by Glen Wilson 21 Jun '05

21 Jun '05

Glen Wilson Network Operations Manager Ihug Ltd, Auckland, New Zealand www.ihug.co.nz On Wed, 22 Jun 2005, Glen Wilson wrote: > > Again I clarify that noc(a)ihug and abuse(a)ihug remain the appropriate > channels. The mailbox is currently backlogged by several weeks, for the > benefit of the list if there are any urgent issues please feel free to > raise them with me directly (off list) for adequate responce. > > Your points are valid, but as the abuse autoresponder states, not all > emails warrent a reply. > > I can assure you that the matter was looked into and recommendations > were made to the responsible parties to improve the process. > > Abuse emails are treated seriously, however genuine cases of abuse are > dealt with faster than complaints of portscans, relay attempts and > blackice alarm logs. > > I enquired about your email today and was told that you had lodged a fault > regarding smtp relay attempts in which the offending ip was not an Ihug > ip and the issue was dropped. It was also brought to my attention > that in a follow up email from you to the abuse mailbox stated the > following,... > > "If I don't get some sort of acknowledgement of my reports soon I will > start dropping ihug IP ranges at the highest supernet I can see... " > > I recognise that current response times to abuse emails is somewhat > lacking but may I presume to recommend a more professional approach in > future Mark. > > Further comments should be off list. > > Regards > > Glen Wilson > Network Operations Manager > Ihug Ltd, Auckland, New Zealand > www.ihug.co.nz > > On Wed, 22 Jun 2005, Mark Foster wrote: > > > Glen - > > I dare say that instead of 'habitual abuse emailer' you might call me > > 'someone who's not willing to simply ignore situations for which ISPs > > and end users should actually be responsible'. > > > > And in case you missed what I stated in my original email, I had tried > > both addresses. Repeatedly. Over WEEKS. > > > > Further I suggest that the 'I'm having the same problem too' format of > > responses to my post to NZNOG might imply that maybe you need to examine > > your own internal processes before you decide to get snarky on a public > > mailing list. > > > > If Ihug abuse team actually acknowledged complaints and committed to > > actioning them within a specific timeframe - as many ISPs do - I would > > not have felt the need to post to NZNOG - which was an act of desparation. > > > > I've been responsible for the abuse@ mailboxes for 3 different ISPs in > > the past and funnily enough, each of those ISPs took abuse reports > > seriously. Nomatter how much they might have wanted to killfile reports > > from particularly frequent reporters. :-) > > > > So I hope you have a great day, Glen. :-) > > > > Mark. > > > > PS: In case anyone hasn't registered it, Simon Lyall's NOC Contact List > > at http://www.usenet.net.nz/noc is pretty damn useful. Most of the time. > > :) [And isn't related to Simons past employment with Ihug.] > > > > Glen Wilson wrote: > > > > > noc(a)ihug.co.nz or abuse(a)ihug.co.nz. > > > > > > As a habitual abuse emailer, Mark Foster knows the appropriate channels. > > > > > > > > > Glen Wilson > > > Network Operations Manager > > > Ihug Ltd, Auckland, New Zealand > > > www.ihug.co.nz > > > > > > On Wed, 22 Jun 2005, Blair Robson wrote: > > > > > > > > >>Seriously - try abuse(a)iinet.net.au , explain that you have tried contacting > > >>abuse(a)ihug.co.nz (I assume you have?) > > >>I don't know weather that will work or not, but I do know that nearly all > > >>the senior people at Ihug in NZ are gone..And I think you will find Simon no > > >>longer works for Ihug. > > >>As far as I can gather everything is being run or in the process of being > > >>run from Perth now. > > >> > > >>Blair > > >> > > >>-----Original Message----- > > >>From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] > > >>Sent: Tuesday, 21 June 2005 3:25 p.m. > > >>To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz > > >>Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > >> > > >>We too need a reply from Ihug security, and have unanswered mail in to > > >>noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a > > >>better address? > > >> > > >>To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated > > >>30 GB of http traffic in the past month for one of our customers - > > >>repeatedly downloading one file. (2400 times at last count) Our customer > > >>would rather like it to stop. > > >

2 1

RE: [nznog] Anyone awake at Ihug NOC/Security?
by Blair Robson 21 Jun '05

21 Jun '05

Seriously - try abuse(a)iinet.net.au , explain that you have tried contacting abuse(a)ihug.co.nz (I assume you have?) I don't know weather that will work or not, but I do know that nearly all the senior people at Ihug in NZ are gone..And I think you will find Simon no longer works for Ihug. As far as I can gather everything is being run or in the process of being run from Perth now. Blair -----Original Message----- From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] Sent: Tuesday, 21 June 2005 3:25 p.m. To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? We too need a reply from Ihug security, and have unanswered mail in to noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a better address? To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated 30 GB of http traffic in the past month for one of our customers - repeatedly downloading one file. (2400 times at last count) Our customer would rather like it to stop. JB -------------- Original message from "Blair Robson" <blair.robson(a)ihug.co.nz>: -------------- > abuse(a)iinet ? > > > > -----Original Message----- > From: Mark Foster [mailto:blakjak(a)blakjak.net] > Sent: Wednesday, 15 June 2005 5:05 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Anyone awake at Ihug NOC/Security? > > Repeat emails over the last week or two to abuse@ and noc@ havn't had any > sort of response or acknowledgement - can someone from Ihug NOC or > security please contact me offlist. > > Thanks > Mark. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

7 6

RE: [nznog] Help with configuring router
by Lesley Walker 21 Jun '05

21 Jun '05

As you were. I found out what my problem was. Sorry for the distraction, I no longer need help. > I need some help with setting up a borrowed Network iQ 1000 series > router. (Also labelled securicor 3net if that helps) Lesley

1 0