- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 15 Nov '04

15 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 13:43:36 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161337240.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: Route set advertised to AS9560 by ihug - AS7657 members: 203.109.128.0/17^17-24, 203.173.128.0/17^17-24, 203.118.128.0/18^18-24, 203.96.192.0/19^19-24, 210.55.248.0/21^21-24, 202.49.240.0/22^22-24, 202.50.188.0/22^22-24, 202.21.136.0/23^23-24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.49.46.0/23^23-24, 202.49.88.0/23^23-24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.180.0/23^23-24, 192.107.113.0/24, 202.21.130.0/24, 202.36.44.0/24, 202.49.33.0/24, 202.49.48.0/24, 202.49.63.0/24, 202.49.178.0/24, 202.49.186.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.255.0/24, 210.55.110.0/24, 210.55.184.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031210 changed: rpsl-admin(a)nzix.net 20040813 changed: rpsl-admin(a)nzix.net 20040920 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 192.107.113.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.44.0/24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.37.182.0/24, 202.49.33.0/24, 202.49.46.0/23^23-24, 202.49.63.0/24, 202.49.64.0/24, 202.49.140.0/24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.178.0/24, 202.49.180.0/23^23-24, 202.49.186.0/24, 202.49.249.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.188.0/22^22-24, 202.50.255.0/24, 203.96.192.0/19^19-24, 203.109.128.0/17^17-24, 203.118.128.0/18^18-24, 203.173.128.0/17^17-24, 210.55.110.0/24, 210.55.184.0/24, 210.55.202.0/23^23-24, 210.55.248.0/21^21-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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 192.107.113.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 --- OBJECT BELOW CREATED: route: 202.21.130.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 --- OBJECT BELOW CREATED: route: 202.21.136.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 --- OBJECT BELOW CREATED: route: 202.36.44.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 --- OBJECT BELOW CREATED: route: 202.36.230.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 --- OBJECT BELOW CREATED: route: 202.49.33.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 --- OBJECT BELOW CREATED: route: 202.49.46.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 --- OBJECT BELOW CREATED: route: 202.49.63.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 --- OBJECT BELOW CREATED: route: 202.49.64.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 --- OBJECT BELOW CREATED: 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 --- OBJECT BELOW CREATED: route: 202.49.178.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 --- OBJECT BELOW CREATED: route: 202.50.188.0/22 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 --- OBJECT BELOW CREATED: route: 203.96.192.0/19 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 --- OBJECT BELOW CREATED: route: 210.55.110.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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Nov '04

15 Nov '04

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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 13:16:45 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161316250.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.4.72/29 descr: Route for FX Networks - AS18406 descr: WIX experimental block origin: AS18406 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR

1 0

RE: [nznog] Notification of NZRR Database changes
by nznog＠asterisk.co.nz 11 Nov '04

11 Nov '04

> This would be a good place for this thread to stop. > > _Before_ we get to the Asterix jokes. And we lurq here too, so we'd notice. :p And yes, we've tried to buy asterix.co.nz. I havn't asked the store called "Obelisk" in Christchurch if they have the same problem. Regards, Adam ----------------------------------- Adam Boileau <adamb(a)asterisk.co.nz> HOD Engineering Asterisk - www.asterisk.co.nz Office: +64-9-3021777

1 0

Re: [nznog] Notification of NZRR Database changes
by phonenet＠phonenet.in-newzealand.com 11 Nov '04

11 Nov '04

If its that quiet then maybe someone at Citylink can add my MAC address to their list so I can usae the Cafenet system properly and get back to sending email (as requested by nzwireless crew earlier this week) Ian Cousins >Oh man *groan* - it must be a quiet day in the citylink office .... > > > On Fri, 2004-11-12 at 10:55, Andy Linton wrote: > Juha Saarinen wrote: > > Alastair Johnson wrote: > > > >> Should we be alarmed by this new IX, which can only be pronounced > >> "PENIX"? Did anyone think this through? :) > >> > >> (nb. This appears to be a new Palmerston North based IX, dubbed > >> the PNIX) > > > > > > Please forgive teh Ju\/3n1l3Z for they do not know how to keep a > > straight face... > > > > Oh Alastair, you big APE, sometimes you get on our WIX. When the time comes I > bet you'll knock the CHIX for SIX. >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Nov '04

11 Nov '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. --- OBJECT BELOW CREATED: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: initially peering at '218.100.21.10' descr: see Citylink RT job #1487 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce 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 20041111 source: NZRR --- OBJECT BELOW CREATED: route: 203.114.128.0/19 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 20041111 source: NZRR --- OBJECT BELOW CREATED: 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 20041111 source: NZRR --- OBJECT BELOW CREATED: route: 203.96.157.0/24 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 20041111 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9281:RS-ROUTES:AS17705 descr: Route set advertised to AS9281 by Inspire Net - AS17705 members: 203.114.128.0/19^19-24, 203.79.88.0/23^23-24, 203.96.157.0/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 20041111 source: NZRR

7 7

RE: [nznog] Notification of NZRR Database changes
by Donald Neal 11 Nov '04

11 Nov '04

> -----Original Message----- > From: Gavin Legge [mailto:gavin(a)dts.net.nz] > Sent: Friday, 12 November 2004 11:04 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Notification of NZRR Database changes > > Oh man *groan* - it must be a quiet day in the citylink office .... This would be a good place for this thread to stop. _Before_ we get to the Asterix jokes. - Donald Neal NZNOG List Administrator Donald Neal |Presbyopia - inability to see what Technical Specialist | bishops are for. Operations Engineering | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

NZNOG Conference 2005 Presenters
by Donald Neal 08 Nov '04

08 Nov '04

NZNOG People, Everyone who made an offer to present by the end of October should by now have received a response from the organising committee. We're still working our way through one or two later proposals. If we've overlooked anyone, could you please contact me off list as soon as possible. Presenter and programme details should begin to appear on the conference web site in the next few days. Thank you for your attention. - Donald Neal Donald Neal |Presbyopia - inability to see what Technical Specialist | bishops are for. Operations Engineering | Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

High Class Webcasting
by Richard Naylor 08 Nov '04

08 Nov '04

If you want to see some high class webcasting check out http://202.8.44.37/mediasitelive30/liveviewer/FrontEnd/Front.aspx?cid=1f5f9… Look at how it does the ppt and video together. Very impressive. Network impact minimal Slides are jpegs and video is 128k MS stuff. (keeps it on topic) price is eye-watering rich

3 4

Fwd: UBS - Message From Hon Paul Swain Minister of Communications
by Chris Hodgetts 04 Nov '04

04 Nov '04

This was sent to an acquaintance of mine and forwarded to me for laughter value. This message had no confidential statement attached, so one assumes that it's open and can be distributed to the recipient wanted to. I hear actually on the Radio this morning that TelstraClear is off to the Commerce Commission. It will be good to track the outcome of that.. -------- Forwarded Message -------- From: Phillippa Fox <Phillippa.Fox(a)parliament.govt.nz> To: jo(a)archnetnz.com Subject: UBS Date: Thu, 4 Nov 2004 09:37:53 +1300 COM04-05/66 Jo Smith jo(a)archnetnz.com Dear Jo Smith Thank you for your email of 17 September 2004 regarding the roll-out of Telecom's unbundled bitstream service (UBS). In particular, your concerns relate to the delay of the provision of this service to the market. In addressing this issue it is important to distinguish between the regulated UBS and the Telecom's commercial UBS. Access to a regulated UBS and corresponding backhaul service to be provided by Telecom was passed into law on 2 September 2004. Under the Telecommunications Act 2001, an Internet Service Provider (ISP) is entitled to apply to the Commerce Commission for a determination of the price and terms and conditions of an Internet grade UBS (with a minimum downstream speed of 256 Kbps) where the applicant is unable to commercially negotiate a satisfactory arrangement. As of today no ISP has applied to the Commission for such a determination. Alongside the regulated UBS, Telecom has on its own initiative offered a commercial UBS to market. The delays to which you refer are in relation to this voluntarily-provided service. The terms of Telecom's commercial UBS are available from Telecom. I understand that Telecom's commercial UBS promised by September has been delayed. Telecom says this is due to a "technical problem" which may take six months to resolve. Given ISPs have invested in marketing products dependent on this service, in the expectation that Telecom would deliver to its announced timeframe, I am concerned about the very short notice Telecom provided to these ISPs of the delay. However, I reiterate, this relates to Telecom's commercial UBS and not the regulated UBS. If an ISP cannot satisfactorily negotiate a commercial UBS, they should apply to the Commission for a determination to provide access to the regulated UBS. You also expressed concern that Telecom is able to advertise its commercial products while Telecom is not providing the service "it has been ordered" to provide and that Telecom is forcing customers into six month contracts preventing them from moving to other cheaper providers. As I explain above, Telecom is not under a legal obligation to provide the service that has been delayed. However, I encourage ISPs to apply for the regulated service if they are not satisfied with the commercial UBS offer. In regard to fixed term offers it is recommended consumers consider the range of offerings in the marketplace before committing to a specific fixed term. Given experiences to date under the Telecommunications Act 2001, I consider that there is potential to make improvements for the more timely achievement of the Act's objective ? the promotion of competition for the long term benefit of end users of telecommunications services. On October 11 2004 I announced a review of the Telecommunications Act 2001. Amongst other things, the review will look at improving the speed of resolution of key terms and conditions for supply of regulated services, including monitoring and enforcement issues, and improving the certainty and speed of processes for adding or altering regulated services. I intend to release a discussion paper in November for comment from interested parties. Yours sincerely Hon Paul Swain Minister of Communications -- Chris Hodgetts <chris(a)archnetnz.com>

4 4

use of open proxies and the Crimes Act
by Stephen Judd 03 Nov '04

03 Nov '04

Suppose a Bad Person (living in NZ) were to use an open proxy (located in NZ) belonging to a Silly Person (also living in NZ) to do Bad Things (eg leeching international bandwidth, posting nastygrams, etc). Am I right in thinking this would fall under recent amendments to the Crimes Act? If so, I might be making a few calls tomorrow. Stephen

2 1

RE: [nznog] High Class Webcasting
by Steve Schmidt 03 Nov '04

03 Nov '04

Now that is very cool. A complete presentation including PP slides sync'ed to the speaker. -----Original Message----- From: Richard Naylor [mailto:richard.naylor(a)citylink.co.nz] Sent: Thursday, 4 November 2004 10:50 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] High Class Webcasting If you want to see some high class webcasting check out http://202.8.44.37/mediasitelive30/liveviewer/FrontEnd/Front.aspx?cid=1f 5f9f9c-be0d-4848-864c-4da9e5172639 Look at how it does the ppt and video together. Very impressive. Network impact minimal Slides are jpegs and video is 128k MS stuff. (keeps it on topic) price is eye-watering rich _______________________________________________ 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. CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it.

1 0

ping TCL; received 64 bytes from TCL
by Richard Patterson 02 Nov '04

02 Nov '04

Hey TCL, weren't you supposed to be breaking the intarwebnet today? -Richard

2 1

The New Zealand Network Operators' Group
by Donald Neal 31 Oct '04

31 Oct '04

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

1 0

Ihug Prefix list update
by Sainesh Singh 28 Oct '04

28 Oct '04

Please update domestic filters for Ihug. APE details: AS7657 192.203.154.36 192.203.154.37 Updated list can be found at: http://www.ihug.net/ihug-prefix-list and is included below. Cheers, Sainesh Singh Ihug Engineering ip prefix-list ihug-networks permit ip prefix-list ihug-networks description ihug peering prefix-list contact: noc(a)ihug.co.nz : Updated 2004-10-29 ip prefix-list ihug-networks permit 192.107.113.0/24 ip prefix-list ihug-networks permit 202.21.130.0/24 ip prefix-list ihug-networks permit 202.21.136.0/23 le 24 ip prefix-list ihug-networks permit 202.36.44.0/24 ip prefix-list ihug-networks permit 202.36.94.0/23 le 24 ip prefix-list ihug-networks permit 202.36.230.0/24 ip prefix-list ihug-networks permit 202.36.231.0/24 ip prefix-list ihug-networks permit 202.37.182.0/24 ip prefix-list ihug-networks permit 202.49.33.0/24 ip prefix-list ihug-networks permit 202.49.46.0/23 le 24 ip prefix-list ihug-networks permit 202.49.63.0/24 ip prefix-list ihug-networks permit 202.49.64.0/24 ip prefix-list ihug-networks permit 202.49.140.0/24 ip prefix-list ihug-networks permit 202.49.148.0/23 le 24 ip prefix-list ihug-networks permit 202.49.176.0/23 le 24 ip prefix-list ihug-networks permit 202.49.178.0/24 ip prefix-list ihug-networks permit 202.49.180.0/23 le 24 ip prefix-list ihug-networks permit 202.49.186.0/24 ip prefix-list ihug-networks permit 202.49.249.0/24 ip prefix-list ihug-networks permit 202.50.84.0/24 ip prefix-list ihug-networks permit 202.50.103.0/24 ip prefix-list ihug-networks permit 202.50.188.0/22 le 24 ip prefix-list ihug-networks permit 202.50.255.0/24 ip prefix-list ihug-networks permit 203.96.192.0/19 le 24 ip prefix-list ihug-networks permit 203.109.128.0/17 le 24 ip prefix-list ihug-networks permit 203.109.130.0/24 ip prefix-list ihug-networks permit 203.109.132.0/22 ip prefix-list ihug-networks permit 203.109.133.0/24 ip prefix-list ihug-networks permit 203.109.134.0/24 ip prefix-list ihug-networks permit 203.109.135.0/24 ip prefix-list ihug-networks permit 203.109.144.0/20 ip prefix-list ihug-networks permit 203.109.157.0/24 ip prefix-list ihug-networks permit 203.109.192.0/21 ip prefix-list ihug-networks permit 203.109.198.0/24 ip prefix-list ihug-networks permit 203.109.199.0/24 ip prefix-list ihug-networks permit 203.109.230.0/24 ip prefix-list ihug-networks permit 203.118.128.0/18 le 24 ip prefix-list ihug-networks permit 203.118.144.0/20 ip prefix-list ihug-networks permit 203.118.160.0/20 ip prefix-list ihug-networks permit 203.118.164.0/22 ip prefix-list ihug-networks permit 203.118.168.0/21 ip prefix-list ihug-networks permit 203.173.128.0/17 le 24 ip prefix-list ihug-networks permit 203.173.164.0/22 ip prefix-list ihug-networks permit 203.173.168.0/23 ip prefix-list ihug-networks permit 203.173.170.0/23 ip prefix-list ihug-networks permit 203.173.172.0/22 ip prefix-list ihug-networks permit 203.173.192.0/19 ip prefix-list ihug-networks permit 203.173.224.0/20 ip prefix-list ihug-networks permit 203.173.240.0/21 ip prefix-list ihug-networks permit 210.55.110.0/24 ip prefix-list ihug-networks permit 210.55.184.0/24 ip prefix-list ihug-networks permit 210.55.202.0/23 le 24 ip prefix-list ihug-networks permit 210.55.248.0/21 le 24

3 2

FW: [Apnic-announce] Final Stage: Early Registration Transfer Project(ERX)
by Nurani Nimpuno 28 Oct '04

28 Oct '04

Message forwarded from the APNIC-announce mailing list. Kind regards, Nurani Nimpuno APNIC -----Original Message----- From: apnic-announce-bounces(a)lists.apnic.net [mailto:apnic-announce-bounces(a)lists.apnic.net] On Behalf Of APNIC Secretariat Sent: 29 October 2004 14:43 To: apnic-announce(a)apnic.net Subject: [Apnic-announce] Final Stage: Early Registration Transfer Project(ERX) Dear Colleagues The four Regional Internet Registries (RIRs) are about to enter the final stage of the Early Registration Transfer (ERX) project. This project is a coordinated effort to move whois records for address space registered before the advent of the RIRs to the whois database of the RIR in whose region the registrant is based. In this final stage of the project, whois records for registrations within 192.0.0.0/8 are being moved from the ARIN database. If you operate a network in 192.0.0.0/8 and have: - registration information in more than one RIR database, or - have a postal address that lies outside the RIR's service region you will receive a mail regarding its registration. The mail explains in which database we believe the registration is meant to reside. The message also explains how to indicate which contact information should be recorded. You can find out more about the ERX project at the following URLs: http://www.apnic.net/db/erx/ http://www.arin.net/registration/erx/ http://www.lacnic.net/en/erx.html http://www.ripe.net/projects/erx/ Kind regards ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 ---------------------------------------------------------------------- _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce

1 0

Contact Details for ATT NZ
by Craig Whitmore 28 Oct '04

28 Oct '04

Hi there I am looking for the NZ Technical Contact for AT&T in NZ (regards to Internet). Can anyone help me (please reply off list). It doesn't seem to be on http://www.usenet.net.nz/noc/index.html Regards, Craig Whitmore

1 0

WIX Peering
by Craig Spiers 28 Oct '04

28 Oct '04

Anyone out there on wix, who isn't currently peering at the route server's for some reason, and would like to setup direct peering, chuck me an email :-) Cheers Regards, Craig - ConceptNET

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Oct '04

28 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 12:26:49 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291218530.3561(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24, 202.7.6.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.7.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Oct '04

28 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:47:13 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291145340.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 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 20041029 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/24^24-29, 202.7.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 mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route: 202.7.4.0/24 descr: Route for Citylink - AS23755 origin: AS23755 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 20041029 source: NZRR REPLACED BY: route: 202.7.4.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 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 20041029 source: NZRR REPLACED BY: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- OBJECT BELOW CREATED: route: 202.7.7.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Oct '04

28 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:27:06 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291126030.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.6.0/24 descr: Route for Citylink - AS23754 origin: AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24, 202.7.6.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Oct '04

28 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:22:53 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291122070.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 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 20041029 source: NZRR

1 0

MCI/Voyager offer free global transit from APE
by Andy Linton 28 Oct '04

28 Oct '04

I'm trying to get hold of someone at MCI/Voyager to get them to stop advertising the APE block, 192.203.154.0/24, globally. It's generating a whole heap of extraneous noise on the APE and we want it to stop. For details see: http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&query=1&arg=+192.20…

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '04

27 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1429] New objects for inclusion in NZRR (fwd) - Date: Thu, 28 Oct 2004 14:30:40 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281429180.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.135.38.0/26 descr: Route for SolNet Solutions - AS64580 origin: AS64580 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: eric.duggan(a)solnetsolutions.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '04

27 Oct '04

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 APE and/or WIX route servers 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, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 28 Oct 2004 14:22:08 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281420390.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: Route set for Citylink to APE members: 203.118.144.0/24, 198.48.0.0/22, 202.8.44.0/22^22-24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)nzix.net 20031118 changed: rpsl-admin(a)nzix.net 20040303 changed: rpsl-admin(a)nzix.net 20040406 changed: rpsl-admin(a)nzix.net 20040629 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 202.7.5.0/24 descr: Route for CityLink - AS23754 origin: AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR

1 0

ADSL @ Home
by Geraint Jones 27 Oct '04

27 Oct '04

I got a charming email from extra informing me that their flat rate customers charged @ 69.95 will be going from 256kbit to 2mbit in the next month, the first I heard of it was the email. Was anyone aware this was going to happen and it was just me having my head in the sand or is this as unexpected as I find it. Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net <http://www.french-maid.net/> Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

6 5