- 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: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

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:01:56 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281401420.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: route: 210.48.101.64/27 descr: Route for Araneo - AS64598 origin: AS64598 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 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 13:59:44 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281356090.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: route: 202.53.189.128/29 descr: Route for Araneo - AS64598 origin: AS64598 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR --- OBJECT BELOW DELETED: route: 202.174.161.0/24 descr: Route for Araneo - AS64598 origin: AS64598 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR --- OBJECT BELOW DELETED: route: 210.48.109.224/27 descr: Route for Araneo - AS64598 origin: AS64598 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR

1 0

RE: [nznog] ADSL @ Home
by Geraint Jones 27 Oct '04

27 Oct '04

/me brushes the sand off his ears ;-P Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240 -----Original Message----- From: Drew Broadley [mailto:drew(a)corrupt.co.nz] Sent: Thursday, October 28, 2004 1:24 PM To: Geraint Jones Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] ADSL @ Home Geraint Jones wrote: > 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. Is this really on-topic ? Answer: yes, your head is in the sand, http://www.telecom-media.co.nz/releases_detail.asp?id=3096 :) - Drew 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.

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 #1422] Changes to AS64598 (fwd) - Date: Thu, 28 Oct 2004 12:28:34 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281227470.5286(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64598 descr: Route set advertised to AS9439 by Araneo - AS64598 members: 202.53.189.128/29, 202.174.161.0/24^24-29, 210.48.109.224/27^27-29, 210.48.101.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64598 descr: advertised to AS9439 by Araneo - AS64598 members: 210.48.109.104/29, 210.48.109.112/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 210.48.109.104/29 descr: Route for Araneo - AS64598 origin: AS64598 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.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: [CityLink #1421] Changes to AS64597 (fwd) - Date: Thu, 28 Oct 2004 12:27:23 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281226020.5286(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: Route set advertised to AS9439 by Araneo at RNZ - AS64597 members: 210.48.109.224/27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: jon.brewer(a)att.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040801 changed: rpsl-admin(a)nzix.net 20040908 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 202.53.189.128/29 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 210.48.101.64/27 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 210.48.109.224/27 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 202.174.161.0/24 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR

1 0

Re: [nznog] ADSL Rate Limiting on the line.
by neil gardner 23 Oct '04

23 Oct '04

Well, I've never met Bruce, and I do read Aardvark most days, but I think it would be good to get someone that really _knows_ what the impact of reducing the line speed on latency will be. We have a few dslams here for testing but they're been used for real work right now. Anyone _know_ what the effect will be? Cheers - Neil G >>> Richard Nelson <richardn(a)cs.waikato.ac.nz> 22/10/2004 12:44:56 p.m. >>> Maybe you misread it, there is a 'but' in the sentance: "This will likely increase latency for all but those on the full-speed JetStream plans ..." Richard. Craig Spiers wrote: > Hi guys, > > > > Reading todays article on http://www.aardvark.co.nz/ he raves on about > 'increased latency' > > > > Would I be right in saying the latency would only increase on lower speed > jetstream plans - as it takes longer for the packets to pass over a smaller > pipe. > > > > Why is he talking about it increasing latency on full rate jetstream plans? > > > > Cheers > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

4 4

Weekend reading on Exchanges
by Andy Linton 21 Oct '04

21 Oct '04

Here's a paper on IXes you might like to read: Prescriptive Policy Guide for Developing Nations Wishing to Encourage the Formation of a Domestic Internet Industry http://www.pch.net/resources/papers/policy-guide/policy-guide.html

1 0

FW: Westpac: SERVICE MESSAGE
by Barry Murphy 21 Oct '04

21 Oct '04

Just received: Return-Path: <www(a)forcartex.com.tw> Delivered-To: unix.co.nz-barry(a)unix.co.nz Received: (qmail 57023 invoked from network); 22 Oct 2004 00:25:24 -0000 Received: from www(a)forcartex.com.tw by firewall.unix.co.nz by uid 82 with qmail-scanner-1.22 (uvscan: v4.3.20/v4396. Clear:RC:0(219.88.242.3):. Processed in 0.334605 secs); 22 Oct 2004 00:25:24 -0000 X-Qmail-Scanner-Mail-From: www(a)forcartex.com.tw via firewall.unix.co.nz X-Qmail-Scanner: 1.22 (Clear:RC:0(219.88.242.3):. Processed in 0.334605 secs) Received: from unknown (HELO dbmail-mx3.orcon.net.nz) (219.88.242.3) by smtp.unix.co.nz with SMTP; 22 Oct 2004 00:25:24 -0000 Received: from mail.unix.co.nz (firewall.unix.co.nz [219.88.241.242]) by dbmail-mx3.orcon.net.nz (8.13.1/8.13.1/Debian-14) with SMTP id i9M0PONQ030574 for <blacklabel(a)orcon.net.nz>; Fri, 22 Oct 2004 13:25:25 +1300 Received: (qmail 57013 invoked by uid 89); 22 Oct 2004 00:25:23 -0000 Delivered-To: barry(a)southafrica.co.nz Received: (qmail 57007 invoked from network); 22 Oct 2004 00:25:22 -0000 Received: from www(a)forcartex.com.tw by firewall.unix.co.nz by uid 82 with qmail-scanner-1.22 (uvscan: v4.3.20/v4396. Clear:RC:0(211.22.18.59):. Processed in 0.985909 secs); 22 Oct 2004 00:25:22 -0000 X-Qmail-Scanner-Mail-From: www(a)forcartex.com.tw via firewall.unix.co.nz X-Qmail-Scanner: 1.22 (Clear:RC:0(211.22.18.59):. Processed in 0.985909 secs) Received: from unknown (HELO mail.forcartex.com.tw) (211.22.18.59) by smtp.unix.co.nz with SMTP; 22 Oct 2004 00:25:21 -0000 Received: from localhost (localhost.forcartex.com.tw [127.0.0.1]) by mail.forcartex.com.tw (Postfix) with ESMTP id B207F12BC24 for <barry(a)southafrica.co.nz>; Fri, 22 Oct 2004 08:25:18 +0800 (CST) Received: from mail.forcartex.com.tw ([127.0.0.1]) by localhost (www.forcartex.com.tw [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10715-03 for <barry(a)southafrica.co.nz>; Fri, 22 Oct 2004 08:25:18 +0800 (CST) Received: by mail.forcartex.com.tw (Postfix, from userid 80) id 4D67012BCA8; Fri, 22 Oct 2004 08:24:21 +0800 (CST) To: barry(a)southafrica.co.nz Subject: Westpac: SERVICE MESSAGE MIME-Version: 1.0 Content-type: text/html; charset=iso-8859-1 From: Westpac New Zealand <service(a)westpac.co.nz> Reply-To: service(a)westpac.co.nz X-Mailer: PHP/4.3.8 Message-Id: <20041022002421.4D67012BCA8(a)mail.forcartex.com.tw> Date: Fri, 22 Oct 2004 08:24:21 +0800 (CST) X-Virus-Scanned: clamd / ClamAV version 0.75-1, clamav-milter version 0.75c on dbmail-mx3 X-Virus-Scanned: by amavisd-new at forcartex.com.tw X-Amavis-Alert: BAD HEADER Improper use of control character (char 0D hex) in message header 'MIME-Version': MIME-Version: 1.0\r\n Received-SPF: none (dbmail-mx3.orcon.net.nz: 219.88.241.242 is neither permitted nor denied by domain of forcartex.com.tw) receiver=dbmail-mx3.orcon.net.nz; client-ip=219.88.241.242; helo=mail.unix.co.nz; envelope-from=www(a)forcartex.com.tw; x-software=spfmilter 0.93 http://www.acme.com/software/spfmilter/; X-Virus-Status: Clean X-Spam-DCC: : X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on firewall.unix.co.nz X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=BAYES_50,HTML_MESSAGE, HTML_TITLE_UNTITLED,MIME_HTML_ONLY autolearn=no version=2.64 _____ From: Westpac New Zealand [mailto:service(a)westpac.co.nz] Sent: Friday, 22 October 2004 1:24 p.m. To: barry(a)southafrica.co.nz Subject: Westpac: SERVICE MESSAGE <http://www.westpac.co.nz/w_nz.gif> Dear Westpac customer, Recently there has been a large number of identity theft attempts targeting Westpac customers. In order to safeguard your account, we require that you confirm your banking details. This process is mandatory, and if not completed within the nearest time your account may be subject to temporary suspension. To securely confirm your Westpac account details, please fill in the form that will follow after signing in at: http://www.westpac.co.nz/personal/Checking/OnlineBanking/Internet_Banking/in dex.cfm <http://www.saracie.org/secure/online/adtrack/IOLB/newSession/nz.htm> Thank you for your prompt attention to this matter and for using Westpac! Westpac Banking Corporation ABN 33 007 457 141, incorporated in Australia (New Zealand division). CopyrightC1999-2004 Westpac Banking Corporation

3 2

ADSL Rate Limiting on the line.
by Craig Spiers 21 Oct '04

21 Oct '04

Hi guys, Reading todays article on http://www.aardvark.co.nz/ he raves on about 'increased latency' Would I be right in saying the latency would only increase on lower speed jetstream plans - as it takes longer for the packets to pass over a smaller pipe. Why is he talking about it increasing latency on full rate jetstream plans? Cheers

2 2

Unsubscription from NZNOG
by Donald Neal 20 Oct '04

20 Oct '04

After repeatedly making postings to this list which were not compatible with the list's acseptable use policy, Michael Hallager has been unsubscribed from the NZNOG list. I have received a number of complaints about his behaviour. My thanks to those subscribers for not sending their complaints to the list. - Donald Neal NZNOG Mailing 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

Re: [nznog] FYI: Telecom changes the ADSL playing field again...
by neil gardner 20 Oct '04

20 Oct '04

>>> Stephen Ridley <stephen.ridley(a)k.co.nz> 21/10/2004 11:00:01 a.m. >>> >And the latency is somewhat better than what we used to get from the jetstream >link: >traceroute to xtra.co.nz (202.27.184.102), 30 hops max, 38 byte packets > 1 a.a.a.a (a.a.a.a) 0.926 ms 0.864 ms 0.922 ms > 2 b.b.b.b (b.b.b.b) 8.465 ms 8.123 ms 12.425 ms > 3 cs2-e4-7-acld.auckland.clix.net.nz (203.97.9.98) 8.771 ms 9.305 ms 9.286 ms > 4 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 11.422 ms 10.660 ms 10.282 ms > 5 xtra.ape.net.nz (192.203.154.60) 14.338 ms 10.610 ms 10.278 ms > 6 v512.XTRAK2-B1.xtra.co.nz (202.27.176.226) 11.048 ms 10.160 ms 10.023 ms We don't need no Interleaving We don't need no surf control No dark deals screwing VOIP Telcos, leave them bits alone Hey, Telcos! Leave them bits alone! All in all it's just another service to fall All in all, you're just a consumer that's going to get screwed by corporate greed and can't do a damn thing about it at all! (Apologies to Pink Floyd and for the number of syllables in the last line :-) N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

5 4

RE: [nznog] FYI: Telecom changes the ADSL playing field again...
by Steve Schmidt 20 Oct '04

20 Oct '04

The question will be "Free" for how much longer? I have heard rumors that Citylink may have some new tricks up their sleeve (free to comment, open for blasting) to try and maintain free peering exchanges but it will ultimately come down to all the "other" isp's ensuring that they continue to peer at the exchanges. (note: MCI/Voyager just completing their own peering hub and peering arrangements are now being "reviewed") TCNZ are reviewing. TCL have already made their intentions clear. (pardon the pun :-) -----Original Message----- From: Richard Patterson [mailto:richard(a)helix.net.nz] Sent: Thursday, 21 October 2004 10:28 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] FYI: Telecom changes the ADSL playing field again... J S Russell wrote: > >Doesn't this kinda defeat the whole point of having a seperate realm for >JSG, then? That full-speed business was the only thing that made it >interesting. If your connectivity to it is the same as your connectivity >to any other normally-peered (Hi TelstraClear!) New Zealand game server, >why bother maintaining it as a seperate realm you need to re-login to >access? It was worth the bother to re-login when it got you decent speeds, >but without them it's just a pain in the ass. You may as well just lift >the access lists and put allow access to these machines from the general >internet. Or is that what's happening anyway? I remember hearing something >recently about JSG going away. > > > > > Well it won't count to your usage cap. Your 10Gb Usage cap. Including NATIONAL Traffic National traffic thats delivered over the public peering exchanges. Thats ~free anyway. </rant> _______________________________________________ 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.

9 19

RE: [nznog] FYI: Telecom changes the ADSL playing field again...
by Donald Neal 20 Oct '04

20 Oct '04

Subscribers to this list should by now be well aware that the Acceptable Use Policy begins "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." This does include, for example, discussion of the way QoS features are used in carrier-class networks. But ADSL-related threads on this list have a record of quickly becoming irrelevant to the list's purpose. Let's try and keep this on topic, please. - 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

FYI: Telecom changes the ADSL playing field again...
by Craig Humphrey 20 Oct '04

20 Oct '04

This just came up in the NZ ADSL list: http://www.telecom.co.nz/content/0,3900,204368-201502,00.html Many of you (who work for ISPs) are probably already aware of this, but here's a quick summary: 1. Telecom moving the rate-limiting to the DSLAM and implementing new backend QoS. 2. Telecom apparently (pointed out by an NZ ADSL user) introducing a further 30ms of latency to ADSL connections (presumably due to new QoS). 3. JetStream Games realm and Remote.Office connections will now be limited to connection plan speed (due to the limiting being done at the DSLAM). Yes, this will impact the usage of the jetstreamgames.co.nz and ftp.paradise.net.nz(?) game/linux/bsd mirrors. Note: this is just a mixture of my interpretation and info garnered from NZ ADSL. I/we could be completely wrong :) Later'ish Craig

9 8

Re: [nznog] FYI: Telecom changes the ADSL playing field again...
by neil gardner 20 Oct '04

20 Oct '04

>>> Barry Murphy <barry(a)unix.co.nz> 21/10/2004 10:23:04 a.m. >>> >Telstra Clear already do this with their tempest service, if you purchase a >256k connection, check your router status and you'll see you are connected at >288k. They at least give 32k leaway. Not really - that 288k is 288k of ATM bandwidth... It translates (as best I can figure) to 31.32Kb/sec or 250.56kbits of real world transfer... So you're actually getting more than 256kbits of raw traffic, it's the TCP overheads that bring the number below 256. Cheers - Neil G (Reference : http://www.broadbandreports.com/information/kb/maximum+DSL+speeds/ATM) quoted below maximum DSL speeds Maximum DSL speed is a function of distance, the gauge (thinness) of the phone wire used in your locale, and the DSL technology employed. The fastest DSL now commonly available is ADSL, and it offers maximum download speeds of up to 7.1mbps and around 1.1m upload. Most residential ADSL is limited to 90-680k for download, depending on the Telco. SDSL currently has a max of 1.5mbps, but that is both up and down (symmetric). Other common rates are (in k bits per second) 640k/90k, 1600k/90k, 680k/680k for ADSL. Rule of thumb for converting speeds to something easier to understand: take the k bps, and divide by 10. This is the maximum transfer K per second you are ever likely to see in a browser download window. More accurately, divide by 8 and take off 13%, which is overhead from tcp/ip and, more importantly, ATM overhead. (DSL lines use ATM as an underlying data-transport protocol). Modems range from 2-5k a second, DSL lines from 10-500k a second, office computer interconnections are usually either (best case) 800k a second (10mbit) or 8000k a second (100mbit switched). NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

Re: [nznog] FYI: Telecom changes the ADSL playing field again...
by Michael Hallager 20 Oct '04

20 Oct '04

> This makes a lot of sense, though, technically. Why connect the user at > 8Mbits/sec down and churn out a boatload of RF bollocks from the copper, > when they're only buying a 256Kbits/sec "broadband" connection? May as > well make it 256Kbits/sec right at the start. This will probably enhance > overall network stability somewhat. It does lead automatically to point 3, > however... Good point. Here I have to use two micro filters in series to have a useable phone. (On the ADSL line). Anyone else have this experience? Michael Hallager

1 0

RE: [nznog] FYI: Telecom changes the ADSL playing field again...
by Regan Murphy 20 Oct '04

20 Oct '04

>From: Juha Saarinen [mailto:juha(a)saarinen.org] >Sent: Thursday, 21 October 2004 9:39 a.m. > >What's so badly b0rk3d about DSLAM rate-limiting >and the new QoS implementation that causes latency >to jump like that? Anyone know? "QoS also provides mechanisms for the network to control the delay characteristics (both latency and jitter) of high-priority traffic. Together, prioritization and delay control enable the transmission of real-time voice and video streams." The key word there is "control" (not "reduce" or "limit"). Maybe the latency is applied by design rather than being a fault of the DSLAMs. -- Regan

1 0

Re: Re: [nznog] FYI: Telecom changes the ADSL playing field again...
by Jonny Martin 20 Oct '04

20 Oct '04

> What's so badly b0rk3d about DSLAM rate-limiting and the new QoS > implementation that causes latency to jump like that? Anyone know? If they're dropping the DSL line rate down to plan speed then your bits will take longer to wander to the exchange. It makes quite a significant difference when moving from 8 odd Mbit/s down to 256kbit/s downstream. Can't really take jibes at Telecom for this. If they are taking this approach, then the slower line rates will also mean less RF inteference in the cable binders, which means more robust [albeit slow and piddly] DSL connections. This is how most, if not all, providers work in Australia. Cheers, Jonny.

1 0

RE: Voyager changing AS number
by Booker, Chris 19 Oct '04

19 Oct '04

Hi, Notification that AS4740 Voyager will change to AS703 (MCI Asia Pac) on Thursday 21/10/2004 at 05.30. I am writing to you as the contact point for peering between your AS and our legacy AS 4740 (Voyager) at the Auckland Peering Exchange. If you are not the best contact for peering in your organisation I would appreciate it if you could pass this e-mail on to the right person. MCI acquired Voyager some time ago and we have recently built a new hub in Auckland. We are migrating our peering links to the new site. As part of the move we would like to change the AS on our side to AS703. Our routing policy with respect to your AS will remain the same - we will treat you as a national peer. We will advertise our New Zealand prefixes to you and we will advertise your prefixes to our New Zealand customers. Our peering committee is currently reviewing our peering arrangements in New Zealand and you may hear from a member of our engineering team in the future with regards to that review. Our proposed date time for migration is this Thursday at 0500 New Zealand time. The only change required at your end should be for you to change the remote AS from 4740 to 703. Our IP address will remain the same. I'd appreciate it if you could contact me to let me know if this works for you. Thanks for your time. Regards Christopher Booker Implementation Engineering MCI Australia Email <mailto:chris.booker(a)au.mci.com> chris.booker(a)au.mci.com Tel: + 61 2 9434 5967 Fax: + 61 2 9434 5970

1 0

Invitation to Cisco ISP Update Seminar
by Arron Scott 19 Oct '04

19 Oct '04

Hi all I have asked the List owner for his opinion on whether this may be construed as sales content, so I hope this does not find dis-favour with anyone. Cisco has our primary ISP Consulting Engineer for Australia/New Zealand in Auckland next week, and would be please to invite any ISP staff to attend the following Product Update and Technology Seminar. Attendance is at no cost, and morning tea is included. Please RSVP to browns(a)cisco.com if you would like to attend. ISP's Technology Update Dear All Cisco systems is pleased to invite you a ISP Technology Update Date: Wednesday 27th October Time: 9am to 12.00 Location: Level 16, ASB Building , 135 Albert Street, Auckland During this update we will cover; . IOS software enhancements . 7301 and 7206 NPE-G1. . 10K with PRE-2. . BRAS and LNS Platform update . New RADIUS functionality . Policy management and integration . SSG enhancements . Netflow developments . Core routing update . CRS-1 and IOS-XR . 12000 update RSVP: browns(a)cisco.com We look forward to your participation Arron Scott (CCIE #4099) Phone: +64(9)3551951 Systems Engineer Mobile: +64(21)883163 Cisco Systems New Zealand Ltd. Fax: +64(9)3584442 Level 25, 135 Albert St, Auckland eMail: ascott(a)cisco.com

1 0

SPF Records
by Craig Whitmore 18 Oct '04

18 Oct '04

Hi folks. We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all" This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number) We (Orcon) have started to use SPF (for testing inbound email) and found it helps with identifying spam. _ALOT_ of people have published valid SPF records. Thanks Craig Whitmore Orcon Internet

11 14

Re: [nznog] SPF Records
by Ewen McNeill 18 Oct '04

18 Oct '04

In message <200410190425.i9J4PvGX007457(a)mailserv.waikato.ac.nz>, "Barry Murphy" writes: >I've wanted to setup SPF in the past but have always wondered what happens >when you have a roaming user sending via paradise for example. The best solution for roaming users is (SASL authenticated) relaying via a central mail server that is listed with SPF. Most commonly used mail clients (and some mail servers) will do SASL authentication these days, and many MTAs can be configured to do SALS authenticated mail relaying. Pushing mail through a central mail server like this is also useful if you are doing other processing on that mail server (eg, statistics, storing copies of messages, etc). >Would one need to know every internet facing ip for all ISP's mailservers? SPF also allows for "include" options, so that you can include (by reference) the SPF records published by the ISPs that are being used. You could, eg, "include" the SPF records of all ISPs used by roaming users. It'd be looser than ideal, but still much better than nothing. If that still isn't sufficient (eg, you have roaming users doing direct-to-remote-server SMTP), you could perhaps list all those ISP dialup subnets (in CIDR fashion). Again this is not ideal, but narrowing it down to a few /22s or even /20s compared with "the whole internet" is still an improvement. With some combination of these it should be possible to list a "much better than nothing" SPF record and then focus on tidying things up so it can be tighter (perhaps eventually down to just "v=spf1 mx -all"). More details at the SPF wizard: http://spf.pobox.com/wizard.html?mydomain=example.com Ewen

1 0

RE: [nznog] Mailwasher and its Forged Bounces
by neil gardner 18 Oct '04

18 Oct '04

Longtime listener, first time poster (on this topic anyway) _IF_ it's possible to reliably (and easily) identify the MailWasher bounces, why not just use that to identify customers using it, and block them from your mail server for a while (Hell, even disable their account perhaps) BUT, and this is the important bit, Send an email to the MW developers telling them that as an ISP you are blocking customers that use their software in this way. Suggest that users of their software will find their Intarwebthingy disabled. Sure the developers may not like taking out neat features, but they probably won't like fielding calls from users who get their net killed because of their product either. Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

3 2

Mailwasher and its Forged Bounces
by Lennon - Orcon 18 Oct '04

18 Oct '04

I've been looking lately and a "large" number of double bounces to postermaster are caused by people who use "MailWashers" to Bounce Spam. I rmember the days when I could read every message to postmaster(a)isp.co.nz They are quite easy to spot as they all have the format of: mail.local: unknown name: username 550 username(a)domain.co.nz ... User unknown Coming from MAILER-DAEMON(a)domain.co.nz (usually the ISP's one) (and forging the email (which I presume is against all ISP's T&C) In mailwashers FAQ it says: ------- Do the spammers know I am bouncing email? No, spammers do not know you are bouncing messages. Bounced messages look just like a returned mail message you would receive if you sent an email to an incorrect address. --------- If I can tell if someone if using mailwasher.. why cannot the spammers? Even so I would think 99.9% of all emails bounced via this program don't get back to the spammers anyway (they don't use proper from addresses or use someone else's domain to send from (anyone in NZ using/looking at using SPF? to stop this type of thing) What I am trying to say (if not very well). What do people think of this feature of mailwasher. I've emailed the writer a few times for comments over the last few years and heard nothing from him. Have ISP's complained to uses using it? stopped people using it? or what? Thanks Craig Whitmore

12 19

Ihug Prefix list update
by Sainesh Singh 17 Oct '04

17 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-18 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.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.170.0/23 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

1 0

ACCC (Aus): Draft report on Internet Interconnection
by Simon Lyall 17 Oct '04

17 Oct '04

I havn't read it all yet but people may find it interesting. http://www.accc.gov.au/content/index.phtml/itemId/543536/ "The Australian Competition and Consumer Commission has issued a draft report seeking comment on whether internet interconnection arrangements should be subject to a two year period of monitoring..... " -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

Updated monitoring pages from Team Cymru
by Rob Thomas 13 Oct '04

13 Oct '04

[ Apologies to those of you who receive this note in multiple forums. ] Hi, team. We are pleased to announce some updated monitoring, as well as some new monitoring, on our web site. This includes aesthetic fixes as well as increased visibility. Our DNS monitoring now has increased visibility as well as a new look and feel. Gone are the multiple pages for each zone, replaced with a single page that will have additional zones soon. You'll find it at the following URL. <http://www.cymru.com/DNS/dns.html> The times are DNS query response times, and the query responses are checked for correctness. Clicking on the query response time will bring you to a more detailed, graphical view of the query responses for the given pod and name server combination. We've updated our network monitoring to include several new components. This includes pod to pod ICMP, TCP, and UDP monitoring. It also includes traffic graphs for a select few Darknet pods, and our new Internet Garbage Meter. :) <http://www.cymru.com/Reach/index.html> For more on Darknets, from which our Darknet monitoring and Internet Garbage Meter are generated, please see our Darknet Project page at the following URL. <http://www.cymru.com/Darknet/> We hope you find this of use. Comments and suggestions are always welcome! Thanks! Rob, for Team Cymru. -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty);

1 0

Re: [nznog] ICONZ
by Michael Hallager 12 Oct '04

12 Oct '04

Their helpdesk has told me it is a BGP4 fault and it is at Orcon's end, which it appears is news to Orcon. > Call the helpdesk? Call the noc? Paths look fine to me in a traceroute from > both providers. Michael Hallager (SNIP)

2 1

Re: Re: [nznog] linux.jetstreamgames.co.nz
by Jonny Martin 12 Oct '04

12 Oct '04

> "WIX peers only" mirror, much like ftp.nz.debian.org? I notice the "your ISP > is broken" message is still broken: > Looks like peering with the APE route servers wont > actually fix it. "...MAY be able to fix this problem for you... at the APE OR the WIX" - doesn't seem to me that it's broken. Seems quite reasonable as a generic sorry-no-peering-at-the-appropriate-place-and-we're-not-paying-for-the-traffic message. Cheers, Jonny.

18 23

RE: [nznog] Windows Update Server Selection
by Craig Humphrey 12 Oct '04

12 Oct '04

We've worked with Akamai and the best I can ascertain is that it directs you to the "best" location, where best isn't always the physically nearest server, since it may not have the content you're after. I think it uses similar ideas to what some of the distributed p2p clients do. Get enough requests from a "region" and you move the content (or a copy of the content) closer to that region. But that's just my understanding. > -----Original Message----- > From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] > Sent: Wednesday, October 13, 2004 1:24 PM > To: jon.brewer(a)araneo.net.nz > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Windows Update Server Selection > > It is based on Akamai (where download.microsoft.com is > pointing). But for > some reason.. they seem to move it around ALL the time. Anyone from > Microsoft/Akamai comment/can find out WHY its switching > around all the time > (with us it changes every 20-30 mins.. NZ..Australia.. US.. > Australia....) > Instead of just going to the Akamai Servers in NZ > > Thanks > Craig Whitmore > Orcon Internet

1 0

An idea for discussion
by Michael Hallager 12 Oct '04

12 Oct '04

Hello all. Ever so often on NZNOG somebody posts a wanted or for sale message. I have just thought - would there be any interest in a seperate "marketplace" mailing list, to buy, sell, trade equipment specifically related to ISP's and networks? MTCW - Comments please. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

4 4

ICONZ
by Michael Hallager 11 Oct '04

11 Oct '04

Hello all. Is anyone aware of any funkiness between Iconz and Orcon, somewhere around APE? Non APE paths work. APE paths don't. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

4 3

Re: [nznog] Networkstuff promotion
by Michael Hallager 11 Oct '04

11 Oct '04

Repeat: NO ONE who got emailed today was added to any mailing list !! (Without requesting it). It was ONLY AN INVITATION to a small group of targetted people, who's email addresses were in my address book. Please people, with p-pills, mortgage applications, pirated MS software yada yada, why the need to take out your frustrations on a local known specialised e-commerce business? Despite having my email address all over the place, I receive maybe once a month only an unsolicited professional email offering me something relevant and I find many of these useful or I simply delete. I have publically apologised several times and still I get emails suggesting that I should "apologise". Could it be that this is way out of proportion? I am still sorry and disapointed that some people have taken this in an unintended way. Michael Hallager > Rather remove everyone you manually added to the mailing list and let them > find your website on their own, if they want to be added they will opt in. > > Barry > > -----Original Message----- > From: Michael Hallager [mailto:michael(a)networkstuff.co.nz] > Sent: Sunday, 10 October 2004 9:05 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Networkstuff promotion > > Hello all. > > I have just gone through and added a few names to the no-contact list > although > only about 50% of the people posting so far in this subject so far were > ever > > emailed in the first place. At last count, about 5 or 6. > > The actions of some in threatening mail blocks and in continuing this on > NZNOG > has made it rather hard for me to asertain who would like to be added. > I have already discussed it with others, some who would rather keep > the pot boiling... for no obvious reason.... I have tried to sort this out > with as many people as possible. > > So I repeat - contact me directly with your details and it will happen. > > I sincerely apologise again to all who were offended. > > // Michael Hallager > Director || Head geek || Making IT work. > > URL: http://www.networkstuff.co.nz > networkStuff, NZ's leading online supplier of high quality new and used > networking equipment. > > Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) > Fax: (09) 837-8100 0800 329-788 (Freefax) > Mobile: 029 638-7883 (SMS, MMS and PXT supported) > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog -- // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

7 12

Lucent Ascend & Telecom PR2
by Craig Spiers 11 Oct '04

11 Oct '04

Anyone know how to configure a telecom PR2 PRI on a lucent ascend ? Settings etc? Any funky things I should know? Cheers

1 0

RE: [nznog] Ameritrade.com smtp server issue
by Gordon Smith 11 Oct '04

11 Oct '04

Yeah, poor choice of terminology on my part perhaps. I was referring to the fact that a tier 1 provider was reachable via another tier 1 provider i.e. peered, so from the point of view of the endpoint traffic transits the first tier 1 to reach the second :-) Cheers, Gordon > -----Original Message----- > From: Hamish MacEwan [mailto:hamish.macewan(a)gmail.com] > Sent: Tuesday, 12 October 2004 11:45 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: Re: [nznog] Ameritrade.com smtp server issue > > And because they don't need transit, they are top tier. It > is after all a self-fulfilling and self-referring definition. > > Hamish. > > On Mon, 11 Oct 2004 18:42:04 -0400, Joe Abley <jabley(a)isc.org> wrote: > > > > They are peers. It's because the top-tier operators peer that they > > don't need transit. > > > > > > Joe >

1 0

RE: [nznog] Sprintlink outage yesterday
by Tom Hibbert 11 Oct '04

11 Oct '04

By contrast 3 of our clients on Virtual ISP couldn't send a single packet past core2a.iconz.net.nz until at least 3pm... Oh well, there was nothing anyone could have done about a crashed router. Noone at ICONZ could have got things back on track any faster unless they teleported to the endpoint and hit reset themselves. Kudos to John J and Iconz NOC for their failover setup, its more than most ISPs I know can/will do. -----Original Message----- From: Jonathan Brewer [mailto:jon.brewer(a)worldnet.att.net] Sent: Tuesday, 12 October 2004 9:43 a.m. To: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Sprintlink outage yesterday Folks, We were very impressed with the way ICONZ failed over from SprintLink to Global Gateway without significant disruption. We did receive a number of calls from our customers on ICONZ upstream, but all were to do with a lack of performance rather than a lack of connectivity. Cheers, Jonathan Brewer -----Original Message----- From: Tom Hibbert [mailto:tom(a)nsp.co.nz] Sent: Tuesday, 12 October 2004 9:01 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Sprintlink outage yesterday Hi all Seems like some of us were stung by a major outage affecting at least Iconz' upstream yesterday, but probably others were affected also. One of our largest customers - a power line service contractor covering 3/5 of the country - was severely stung by the routing issue yesterday as Contact Energy deliver their job notices through a mail sanitization house in the United States, who were attempting to route back through to New Zealand but were unable to do so. Fortunately Contact were contacted (pun unintentional) by their provider in the states who arranged a resolution by bouncing the mail off one of our boxes here. Thanks to them the outage as far as it affected Joe Public at his home and business was only about 2 hours... So what the hell happened? Obviously the problem was with the endpoint in the USA and therefore outside of anyone in NZ's responsibility... Tom Hibbert Technical Specialist Phone: +64-9-306-0230 Technical Helpdesk: +64-9-306-0234 Mobile: +64-274-307-784 Email: tom(a)nsp.co.nz Website: http://www.nsp.co.nz The information in this email and any attachments is confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Sprintlink outage yesterday
by Tom Hibbert 11 Oct '04

11 Oct '04

Hi all Seems like some of us were stung by a major outage affecting at least Iconz' upstream yesterday, but probably others were affected also. One of our largest customers - a power line service contractor covering 3/5 of the country - was severely stung by the routing issue yesterday as Contact Energy deliver their job notices through a mail sanitization house in the United States, who were attempting to route back through to New Zealand but were unable to do so. Fortunately Contact were contacted (pun unintentional) by their provider in the states who arranged a resolution by bouncing the mail off one of our boxes here. Thanks to them the outage as far as it affected Joe Public at his home and business was only about 2 hours... So what the hell happened? Obviously the problem was with the endpoint in the USA and therefore outside of anyone in NZ's responsibility... Tom Hibbert Technical Specialist Phone: +64-9-306-0230 Technical Helpdesk: +64-9-306-0234 Mobile: +64-274-307-784 Email: tom(a)nsp.co.nz Website: http://www.nsp.co.nz The information in this email and any attachments is confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

5 5

RE: [nznog] Ameritrade.com smtp server issue
by Gordon Smith 11 Oct '04

11 Oct '04

> Beither Sprint or UUNET have any transit arrangements. They > don't need them. > > > Joe > > Hmm... They're definitely passing some of each others routes, according to our intl route tables... e.g. AS 3707 (MCI) is known via AS 1239 (SPRN). Both Telecom (AS 4648) and Sprint here (AS 3643), carry them... I see 4 AS hops: 3643 1239 701 3707 - Sprint -> Sprint -> UUNET -> UUNET (MCI) Cheers, Gordon

3 2

RE: [nznog] Ameritrade.com smtp server issue
by Gordon Smith 10 Oct '04

10 Oct '04

Depends on their transit agreements. That's how BGP works..... If a route is known via several different paths, it is possible to route traffic around devices that are having problems. When setting up a partial mesh though, it is also extremely easy to introdue routing "blackholes" inadvertently. > -----Original Message----- > From: Alastair Johnson [mailto:alastair.johnson(a)maxnet.co.nz] > Sent: Friday, 8 October 2004 2:29 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Ameritrade.com smtp server issue > > That doesn't make sense. Savvis should not be routing > between Sprintlink and UUNET. That would be a major filter > failure, and cause massive issues. >

2 1

WTB: ISDN emulator
by Michael Hallager 10 Oct '04

10 Oct '04

Hello all. We would like to purchase an ISDN-BRI emulator. If anyone has one for sale, please contact me offlist. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

2 1

Re: [nznog] Re: Networkstuff promotion
by Michael Hallager 10 Oct '04

10 Oct '04

You were not supposed to be on that list. I wouldn't deal with you on the basis of your degree of involvement with Net4u. Mr Net4u 2IC giving me a lecture? Don't throw stones in glass houses. Michael Hallager > > A few NZNOGers have received an email. Out of these few, even fewer have > > complained. I have just received some complaints from people whom in in > > all likelyhood have a short memory for names/people they have had contact > > with. > > Hell, if we have to all individually complain to get the point across that > spam sucks (I even have to get the point across?), then treat this as an > individual complaint. > > If you're going to try and say I have a short memory for names/people I > have had contact with, you're wrong. About the only reason you'd have my > email address is because I was once employed by a company who provided you > with connectivity to the vast network that is the interweb. But wait, if > you'd emailed me with respect to that, you would have used my work email > address. Whoops, guess you got my address from NZNOG. > > > However 50% of those who have complained never received anything in the > > first place because I check their names and NOTHING..... comes up. > > I assure you I received a copy of your spam. I'll forward it back to you > with headers if you don't believe me. > > > Also some people are starting to post myths and fake stories up here now. > > > > There is no spamming, no email harvesting, no nonsense, no conspiracy. > > ?! The only myth I've seen so far is that "there is no spamming". > > > As much as it might suit some peoples egos to continue on with this > > tirade, I have done everything I can and apologised several times. > > Wrong. Doing everything you can would have involved not sending the spam in > the first place. > > > I really don't deserve the crap that I receive from some people - I hope > > they never make an error of judgement in case they are on the receiving > > end of their own bad attitude. Complain to me, yes - abuse/threaten me, > > no. > > You, are a spammer. Spammers deserve what they get. > > As an aside, if you've never dealt with Richard and/or Helix, how come he > received a copy of your spam? Whoops, NZNOG harvesting again. > > In case you haven't got the message, remove me from your list. > > Michael. -- // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

7 8

Again
by Michael Hallager 10 Oct '04

10 Oct '04

I notice that there is some more noise on the subject: I have heard what the NZNOG has to say. The message was not intended to be spam, it was intended to be a few targeted emails to appropriate people offering them the opportunity to get included on the newsletter or get a login to the website. Unfortunitly, poor wording of the email has left some people with the wrong impression. 1. No one was ever added to the newsletter mailing list unless they asked. Therefore it was always OPT IN. 2. A negative reply or no reply is considered to be 'un interested'. As of now I have written to everyone who has received the email and complained. (If I have left you out, that was an oversight) and I have apologised. For the odd person who has threatened a mail block, that is up to you, but I hope that you will consider it again - counter productive for your clients as well as mine. You know who I am and you know that I won't be doing it again, therefore negating the purpose. The mailout was small, but ill-conceived. I accept responsibility for this and I will not be making a repeat of this mistake. I will shortly be adding a 'add me to your newsletter mailing list' DOUBLE OPT IN option to my website to allow people to join. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

1 0

Re: [nznog] Networkstuff promotion
by Michael Hallager 10 Oct '04

10 Oct '04

> A few months ago I was approached by Whitebox Express (Colin Brown - ex > PC Company) about going on their mailing list, but they didn't just > start sending me mail without asking, I got an email saying would I like > to be added, and if I DID want to be added then I could reply saying so. > They didn't just add me and then expect me to unsubscribe if I didn't > want to hear from them. What you describe is exactly what I did. It was always an OPT IN mailing list. All people received was a relevant, targetted and professional ONE OFF INVITATION. However some people, including many who never actually received the email, have jumped on the "spam" bandwagon. The few who have contacted me - I have done the right thing for them. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

9 9

Re: [nznog] Networkstuff promotion
by Keith Davidson 10 Oct '04

10 Oct '04

Neil G wrote: > >From: Keith Davidson >>For my part, I will inform as many people as I can that they should >>never deal with networkstuff or Michael Hallager on the basis that >>he is a spammer. > > Well, I'm not sorry I called Michael on this but I have one thing to > say... > > Sheee-it! If I ever make a stupid public mistake on this list, please let > me > have the good sense to publically and promptly apologise. Indeed. Instead, I got the following charming personal "apology" from Michael Hallager the spammer: --<cut>-- And I will likewise about yourself. grow up. your name is now on the blacklist. you will not be contacted again. > For my part, I will inform as many people as I can that they should never > deal with networkstuff or Michael Hallager on the basis that he is a > spammer. --<paste> Keith Davidson <who thought he was fully grown up>

8 9

RE: [nznog] Spam from local sources?
by Donald Neal 09 Oct '04

09 Oct '04

As Ewen McNeill put it, > From: Ewen McNeill [mailto:ewen(a)naos.co.nz] > Sent: Sunday, 10 October 2004 9:02 p.m. > To: Mark Foster > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Spam from local sources? [...] > Meanwhile the reaction is hopefully a sufficient demonstration that > sending advertising (spam) to "individuals who we have found > on the New > Zealand internet" is fairly counter productive if your aim is > to attract > new customers. Particularly when the spam goes to those involved in > running the networks. > > So hopefully there will not be a repeat. The same could usefully be said of much of this thread's content. This thread has long since ceased to have any operational relevance it may just possibly once have possessed. I also see too little of the respect for other subscribers which the AUP requires. Repeat contributors who don't stop now can expect to see warnings as described in paragraph ten of the AUP. There are lots of high-volume forums on the interweb which aren't expecially focussed on a particular subject. This isn't one of them. - Donald Neal Donald Neal |Palmerdale: 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

Spam from local sources?
by NZNOG＠neilnz.com 09 Oct '04

09 Oct '04

Anyone else received any spam today from a local, un-named company? I'm trying to track down where he got my email address from... And yes, he is a member of this list. I thought people on here should know better than this!!! N.

15 28

Re: Re: [nznog] Re: Networkstuff promotion
by Jonny Martin 09 Oct '04

09 Oct '04

> crap > more crap So how about that Telstra outage then... Jonny.

1 0

Networkstuff promotion
by Michael Hallager 09 Oct '04

09 Oct '04

Hello all. I have just gone through and added a few names to the no-contact list although only about 50% of the people posting so far in this subject so far were ever emailed in the first place. At last count, about 5 or 6. The actions of some in threatening mail blocks and in continuing this on NZNOG has made it rather hard for me to asertain who would like to be added. I have already discussed it with others, some who would rather keep the pot boiling... for no obvious reason.... I have tried to sort this out with as many people as possible. So I repeat - contact me directly with your details and it will happen. I sincerely apologise again to all who were offended. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

4 3

Re: [nznog] Spam from local sources?
by Ewen McNeill 09 Oct '04

09 Oct '04

In message <Pine.LNX.4.56.0410102013390.12121(a)babylon.blakjak.net>, Mark Foster writes: >>[Regarding an apparently fairly widespread email to people "involved >> in the local internet / computer industry."] > >Speaking of which; any representatives of Michael's upstream present on >the list? If so you can colour this as an official complaint about the UCE >from Michael Hallager as he obviously doesn't see the reason that NZNOG >have such a low opinion of him. I sent a report to abuse@$UPSTREAMISP around 17:30 with full details. I assume someone at $UPSTREAMISP will deal with it tomorrow. Meanwhile the reaction is hopefully a sufficient demonstration that sending advertising (spam) to "individuals who we have found on the New Zealand internet" is fairly counter productive if your aim is to attract new customers. Particularly when the spam goes to those involved in running the networks. So hopefully there will not be a repeat. Ewen

1 0

RE: [nznog] Spam from local sources?
by NZNOG＠neilnz.com 09 Oct '04

09 Oct '04

Michael, after sending spam (presumably to a bunch of people on this list) you shouldn't be throwing stones. I sent the email to the list at 5:14pm although Paradise didn't pass it on until just after 6pm... In any case, I sent the email to the list before I heard from you - and to be honest I don't give spammers the courtesy of assuming they'll reply intelligently or in a timely fashion (Which you did, however). Cheers - Neil G -----Original Message----- From: Michael Hallager [mailto:michael(a)networkstuff.co.nz] Sent: Sunday, 10 October 2004 7:03 p.m. To: Neil(a)neilnz.com Subject: Re: [nznog] Spam from local sources? We have had this discussion and I thought that we settled the matter. Why are you trying to stir? Michael > Anyone else received any spam today from a local, un-named company? > I'm trying to track down where he got my email address from... And > yes, he is a member of this list. > > I thought people on here should know better than this!!! > > N. > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog -- // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freefax) Mobile: 029 638-7883 (SMS, MMS and PXT supported)

1 0

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

07 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: FAILED: (fwd) - Date: Fri, 8 Oct 2004 16:52:09 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410081642280.1327(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS9889 as-name: NZRR-AS9889 descr: Maxnet descr: initially peering at '202.7.0.116' descr: see Citylink RT job #1320 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9889 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20041008 source: NZRR REPLACED BY: aut-num: AS9889 as-name: NZRR-AS9889 descr: Maxnet admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9889 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9889 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20041008 source: NZRR

1 0

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

07 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. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9889 descr: Route set advertised to AS9439 by Maxnet - AS9889 members: 202.14.217.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.50.167.0/24^24-29, 202.89.32.0/19^19-29, 210.55.29.0/24^24-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 210.55.110.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20041008 source: NZRR

1 0

RE: [nznog] Ameritrade.com smtp server issue
by Gordon Smith 07 Oct '04

07 Oct '04

Looks like a Sprint routing issue. Ameritrade are a customer of alter.net & they should be reachable via Savvis when going across Sprint: 8 sl-bb24-ana-10-2.sprintlink.net (144.232.1.205) 133.225 ms 132.062 ms 132.340 ms 9 sl-st21-la-13-0.sprintlink.net (144.232.20.69) 134.608 ms 135.151 ms 134.132 ms 10 bpr2-so-3-0-0.LosAngelesEquinix.savvis.net (208.174.196.73) 132.760 ms 132.626 ms 133.118 ms 11 bpr1-ae0.LosAngelesEquinix.savvis.net (208.172.35.49) 134.405 ms 134.300 ms 134.417 ms 12 bpr1-so-5-0-0.LosAngeles.savvis.net (208.173.57.61) 140.357 ms 135.033 ms 134.136 ms 13 dcr1-ae1-0.LosAngeles.savvis.net (208.172.47.1) 136.275 ms 134.696 ms dcr2-ae1-0.LosAngeles.savvis.net (208.172.47.13) 133.501 ms 14 dcr2-loopback.SanFranciscosfo.savvis.net (206.24.210.100) 139.084 ms 137.953 ms 140.427 ms 15 bpr2-so-4-0-0.SanJoseEquinix.savvis.net (206.24.211.78) 137.337 ms 136.382 ms 136.519 ms 16 POS3-3.BR1.SJC7.ALTER.NET (208.173.55.2) 137.376 ms 137.765 ms * Alter.net's backbone is reachable, but not all their routes are.... Cheers, Gordon > -----Original Message----- > From: jfp [mailto:jfp(a)clearfield.com] > Sent: Friday, 8 October 2004 12:36 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Ameritrade.com smtp server issue > > > Hi people, we are having issues sending mail to Ameritrade.com. > > It looks like their firewall is dropping the smtp connection > to smtp.ameritrade.com (199.200.9.140) from us. > > I can connect to it from our US server and they claim that > they have lots of NZ customers with no issues. > > So I think they are blocking the 210 block of addresses (we show up as > 210.48.112) because we share that with Korea. > (This is not a mail server block, we don't get a connection > to the mail server, so it must be the firewall in front) > > Could get some of you to try to telnet to smtp.ameritrade.com on port > 25 and let me know the result and the block it's coming from? > > I need some concrete evidence. > > Thanks. > > > jfp. > > -------------------------------------------------------------- > ---------- > Jean-Francois Pirus <jfp(a)clearfield.com> Senior > Software Engineer > Phone (+64-9) 358 2081 Clearfield > Software Ltd > Fax (+64-9) 358 2083 4th Floor 8-10 > Whitaker Place > Mob (+64-21) 640 779 P O Box 2348 Auckland, > New Zealand > -------------------------------------------------------------- > ---------- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Ameritrade.com smtp server issue
by Jean-Francois Pirus 07 Oct '04

07 Oct '04

Thanks for the data guys. I am getting a vast majority of failures so it's a bit more widespread than expected. I will collate it and ask them to review their response :-) Thanks again. jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Clearfield Software Ltd Phone (+64-9) 358 2081 4th Floor 8-10 Whitaker Place Fax (+64-9) 358 2083 P O Box 2348 Auckland, New Zealand ------------------------------------------------------------------------

2 1

RE: [nznog] Ameritrade.com smtp server issue
by Michael Bordignon 07 Oct '04

07 Oct '04

> It looks like their firewall is dropping the smtp connection to > smtp.ameritrade.com (199.200.9.140) from us. timing out for me too - seems as though they're firewalling everything, as even tcptraceroute fails 8 sl-bb21-sj-3-2.sprintlink.net (144.232.8.130) 188.567 ms 189.587 ms 188.584 ms 9 sl-bb24-sj-13-0.sprintlink.net (144.232.3.214) 188.096 ms 185.861 ms 190.153 ms 10 sl-bb21-stk-12-0.sprintlink.net (144.232.20.180) 278.218 ms 196.284 ms 201.601 ms 11 sl-bb22-kc-2-0.sprintlink.net (144.232.20.168) 230.531 ms 231.154 ms 233.457 ms 12 sl-gw10-kc-6-0.sprintlink.net (144.232.23.82) 234.645 ms 233.974 ms 232.707 ms 13 sl-think1-6-0.sprintlink.net (144.224.22.6) 234.018 ms 233.321 ms 234.457 ms 14 * * Michael

1 0

RE: [nznog] Ameritrade.com smtp server issue
by Craig Humphrey 07 Oct '04

07 Oct '04

Looks like a connectivity issue between Sprint and UUNet/Alternet. Here's a couple of traces, one from London, one from Virginia. Please excuse the excessive layout. [Virginia] Report for smtp.ameritrade.com [199.200.9.140] Analysis: Connections to SMTP port 25 on host 'smtp.ameritrade.com' are working, but ICMP packets are being blocked past network "UUNET Technologies, Inc. UUNETCUSTB40" at hop 10. It is a SMTP server (ESMTP Server ready). ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------- | Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------- | 0 | | 161.58.180.113 | WIN10115.visualware.com | Dulles, VA, USA | -05:00 | | | Verio, Inc. VRIO-161-058 | | 1 | | 161.58.176.129 | - | ?Englewood, CO | | 0 | x | Verio, Inc. VRIO-161-058 | | 2 | | 161.58.156.140 | - | ?Englewood, CO | | 0 | x | Verio, Inc. VRIO-161-058 | | 3 | | 129.250.28.206 | xe-1-2-0-3.r20.asbnva01.us.bb.verio.net | Ashburn, VA, USA | -05:00 | 0 | x | Verio, Inc. VRIO-129-250 | | 4 | | 129.250.9.70 | p16-0.uunet.asbnva01.us.bb.verio.net | Ashburn, VA, USA | -05:00 | 0 | x | Verio, Inc. VRIO-129-250 | | 5 | | 152.63.43.182 | 0.so-2-2-0.XL1.DCA5.ALTER.NET | Washington, DC, USA | -05:00 | 0 | x | UUNET Technologies, Inc. UUNET-BACKBONE | | 6 | | 152.63.25.37 | 0.so-2-0-0.TL1.DCA8.ALTER.NET | Washington, DC, USA | -05:00 | 0 | x | UUNET Technologies, Inc. UUNET-BACKBONE | | 7 | | 152.63.0.126 | 0.so-1-2-0.TL1.STL3.ALTER.NET | St. Louis, MO, USA | -06:00 | 15 | x | UUNET Technologies, Inc. UUNET-BACKBONE | | 8 | | 152.63.88.58 | 0.so-7-0-0.CL1.KCY4.ALTER.NET | Kansas City, MO, USA | -06:00 | 31 | x | UUNET Technologies, Inc. UUNET-BACKBONE | | 9 | | 152.63.93.185 | 179.ATM6-0.GW3.KCY4.ALTER.NET | Kansas City, MO, USA | -06:00 | 31 | x | UUNET Technologies, Inc. UUNET-BACKBONE | | 10 | | 157.130.165.126 | ameritrade-gw.customer.alter.net | ?Ashburn, VA, USA | -05:00 | 31 | x- | UUNET Technologies, Inc. UUNETCUSTB40 | | ... | | | | | | | | | | ? | | 199.200.9.140 | smtp.ameritrade.com | | | | | AccuTrade, Inc. ACTRADE | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------- [London] Report for smtp.ameritrade.com [199.200.9.140] Analysis: IP packets are being lost past network "Sprint SPRINT-INNET1" at hop 19. VisualRoute cannot determine the next network at hop 20. Connections to SMTP port 25 are not working. ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------- | Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------- | 0 | | 192.168.101.239 | visualroute.visualware.co.uk | ... | | | | (private use) | | 1 | | 192.168.101.254 | - | ... | | 0 | x | (private use) | | 2 | | 195.167.164.1 | - | ?London, UK | * | 0 | x | Richmond Software | | 3 | | 195.167.252.170 | s12-1-7.access2.lon1.uk.vital-group.net | ?London, UK | * | 21 | x------ | IPCENTA Ltd | | 4 | | 195.167.248.1 | - | ?London, UK | * | 0 | x | Vital International | | 5 | | 134.222.109.173 | ldn-s2-rou-1002.UK.eurorings.net | ?Amsterdam, Netherlands | +01:00 | 0 | x | RIPE Network Coordination Centre RIPE-ERX-134-219-0-0 | | 6 | | 134.222.231.61 | ldn-s2-rou-1001.UK.eurorings.net | ?Amsterdam, Netherlands | +01:00 | 0 | x | RIPE Network Coordination Centre RIPE-ERX-134-219-0-0 | | 7 | | 134.222.230.145 | obl-rou-1003.NL.eurorings.net | ?Amsterdam, Netherlands | +01:00 | 0 | x | RIPE Network Coordination Centre RIPE-ERX-134-219-0-0 | | 8 | | 134.222.229.237 | ledn-rou-1001.NL.eurorings.net | ?Amsterdam, Netherlands | +01:00 | 2 | x | RIPE Network Coordination Centre RIPE-ERX-134-219-0-0 | | 9 | | 134.222.254.2 | ewr-brdr-02.inet.qwest.net | Newark, NJ, USA | -05:00 | 78 | x | RIPE Network Coordination Centre RIPE-ERX-134-219-0-0 | | 10 | | 205.171.17.125 | ewr-core-01.inet.qwest.net | Newark, NJ, USA | -05:00 | 79 | x | Colorado SuperNet, Inc. CSN-BLOCK-7 | | 11 | | 205.171.17.62 | nyc-brdr-01.inet.qwest.net | New York, NY, USA | -05:00 | 78 | x | Colorado SuperNet, Inc. CSN-BLOCK-7 | | 12 | | 205.171.1.134 | - | Denver, CO, USA | -07:00 | 90 | x---- | Colorado SuperNet, Inc. CSN-BLOCK-7 | | 13 | | 144.232.13.1 | sl-bb25-nyc-11-0.sprintlink.net | New York, NY, USA | -05:00 | 159 | --x-- | Sprint SPRINT-INNET9 | | 14 | | 144.232.9.156 | sl-bb24-chi-2-0.sprintlink.net | Chicago, IL, USA | -06:00 | 121 | x---- | Sprint SPRINT-INNET9 | | 15 | | 144.232.26.110 | sl-bb22-chi-9-0.sprintlink.net | Chicago, IL, USA | -06:00 | 134 | -x----- | Sprint SPRINT-INNET9 | | 16 | | 144.232.19.202 | sl-bb20-kc-14-2.sprintlink.net | Kansas City, MO, USA | -06:00 | 133 | -x----- | Sprint SPRINT-INNET9 | | 17 | | 144.232.2.118 | sl-bb21-kc-15-0.sprintlink.net | Kansas City, MO, USA | -06:00 | 109 | x | Sprint SPRINT-INNET9 | | 18 | | 144.232.23.74 | sl-gw10-kc-5-0.sprintlink.net | Kansas City, MO, USA | -06:00 | 109 | x | Sprint SPRINT-INNET9 | | 19 | | 144.224.22.6 | sl-think1-6-0.sprintlink.net | - | | 110 | x- | Sprint SPRINT-INNET1 | | ... | | | | | | | | | | ? | | 199.200.9.140 | smtp.ameritrade.com | Omaha, NE, USA | | | | AccuTrade, Inc. ACTRADE | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------- > -----Original Message----- > From: jfp [mailto:jfp(a)clearfield.com] > Sent: Friday, October 08, 2004 12:36 PM > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Ameritrade.com smtp server issue > > > Hi people, we are having issues sending mail to Ameritrade.com. > > It looks like their firewall is dropping the smtp connection to > smtp.ameritrade.com (199.200.9.140) from us. > > I can connect to it from our US server and they claim that they have > lots of NZ customers with no issues. > > So I think they are blocking the 210 block of addresses (we show up as > 210.48.112) because we share that with Korea. > (This is not a mail server block, we don't get a connection > to the mail > server, so it must be the firewall in front) > > Could get some of you to try to telnet to smtp.ameritrade.com on port > 25 and let me know the result and the block it's coming from? > > I need some concrete evidence. > > Thanks. > > > jfp. > > -------------------------------------------------------------- > ---------- > Jean-Francois Pirus <jfp(a)clearfield.com> Senior > Software Engineer > Phone (+64-9) 358 2081 Clearfield > Software Ltd > Fax (+64-9) 358 2083 4th Floor 8-10 > Whitaker Place > Mob (+64-21) 640 779 P O Box 2348 Auckland, > New Zealand > -------------------------------------------------------------- > ---------- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Ameritrade.com smtp server issue
by jfp 07 Oct '04

07 Oct '04

Hi people, we are having issues sending mail to Ameritrade.com. It looks like their firewall is dropping the smtp connection to smtp.ameritrade.com (199.200.9.140) from us. I can connect to it from our US server and they claim that they have lots of NZ customers with no issues. So I think they are blocking the 210 block of addresses (we show up as 210.48.112) because we share that with Korea. (This is not a mail server block, we don't get a connection to the mail server, so it must be the firewall in front) Could get some of you to try to telnet to smtp.ameritrade.com on port 25 and let me know the result and the block it's coming from? I need some concrete evidence. Thanks. jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 2348 Auckland, New Zealand ------------------------------------------------------------------------

3 2

RE: [nznog] Ameritrade.com smtp server issue
by Craig Humphrey 07 Oct '04

07 Oct '04

We're blocked at 210.86.19.x and 210.55.180.x > -----Original Message----- > From: jfp [mailto:jfp(a)clearfield.com] > Sent: Friday, October 08, 2004 12:36 PM > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Ameritrade.com smtp server issue > > > Hi people, we are having issues sending mail to Ameritrade.com. > > It looks like their firewall is dropping the smtp connection to > smtp.ameritrade.com (199.200.9.140) from us. > > I can connect to it from our US server and they claim that they have > lots of NZ customers with no issues. > > So I think they are blocking the 210 block of addresses (we show up as > 210.48.112) because we share that with Korea. > (This is not a mail server block, we don't get a connection > to the mail > server, so it must be the firewall in front) > > Could get some of you to try to telnet to smtp.ameritrade.com on port > 25 and let me know the result and the block it's coming from? > > I need some concrete evidence. > > Thanks. > > > jfp. > > -------------------------------------------------------------- > ---------- > Jean-Francois Pirus <jfp(a)clearfield.com> Senior > Software Engineer > Phone (+64-9) 358 2081 Clearfield > Software Ltd > Fax (+64-9) 358 2083 4th Floor 8-10 > Whitaker Place > Mob (+64-21) 640 779 P O Box 2348 Auckland, > New Zealand > -------------------------------------------------------------- > ---------- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

RE: [nznog] NZ Linux mirrors
by Craig Humphrey 07 Oct '04

07 Oct '04

I've also updated the WLUG Wiki page: http://www.wlug.org.nz/NewZealandLinuxMirrors Thanks to "Aristotle Pagaltzis" for editing my first attempt at Wiki layout. > -----Original Message----- > From: Mark Foster [mailto:blakjak(a)blakjak.net] > Sent: Thursday, October 07, 2004 5:43 PM > To: nznog(a)list.waikato.ac.nz > Cc: nzlug(a)linux.net.nz > Subject: Re: [nznog] NZ Linux mirrors [snip snip] > At the risk of responding to myself - its now online: > > http://www.linux.net.nz/node/view/75 > > > NZLUG: A list of currently known Linux mirrors is now > published on the LUG > site as per above. :) > Apologies for the crosspost. > > Cheers > Mark.

2 1

NZ Linux mirrors
by Craig Humphrey 06 Oct '04

06 Oct '04

Hi people, Ok, was bored an inquisitive today, so did a little Google and came up with the following Linux mirror sites in NZ, there's even a few FreeBSD ones tagged on the end. If anyone's aware of any others, please let me know and I'll maintain an informal list (and notify linux.net.nz and WLUG). If my boss lets me, I'll stick it on a website too... Later'ish Craig Linux Kernel www.nz.kernel.org ftp.ihug.co.nz/Linux/kernels/kernel/ ftp://linux.jetstreamgames.co.nz/dist/kernel/ Caos ftp://linux.jetstreamgames.co.nz/dist/caos Debian ftp.ihug.co.nz/Linux/CD-images/Debian-3.0/ ftp://debian.ihug.co.nz/debian/ ftp://debian.ihug.co.nz/debian-non-US/ ftp://debian.paradise.net.nz/ ftp://debian.co.nz/Debian/ ftp://linux.jetstreamgames.co.nz/dist/debian/ ftp://linux.jetstreamgames.co.nz/dist/debian-cd/ ftp://linux.jetstreamgames.co.nz/dist/debian-non-US/ ftp://linux.jetstreamgames.co.nz/dist/debian-security/ ftp.jetstreamgames.co.nz/debian/ ftp.jetstreamgames.co.nz/debian-non-US/ ftp.jetstreamgames.co.nz/debian-security/ ftp://ftp.tranzpeer.net/debian/ ftp://ftp.tranzpeer.net/debian-backports/ ftp://ftp.tranzpeer.net/debian-cd/ ftp://ftp.tranzpeer.net/debian-non-US/ ftp://ftp.tranzpeer.net/debian-security/ ftp.nz.debian.org/debian/ (ftp.citylink.co.nz) WIX only (there may be other distros on here) ftp://mirror.inspire.net.nz/debian/ ftp://mirror.inspire.net.nz/debian-backports/ ftp://mirror.inspire.net.nz/debian-cd/ ftp://mirror.inspire.net.nz/debian-non-US/ ftp://mirror.inspire.net.nz/debian-security/ Fedora ftp.wicks.co.nz/pub/linux/dist/fedora/ ftp.ihug.co.nz/Linux/CD-images/Fedora/ ftp://debian.co.nz/Fedora linux.jetstreamgames.co.nz/fedora/ Gentoo ftp.ihug.co.nz/Linux/CD-images/Gentoo-1.2/ ftp://debian.co.nz/Gentoo/ ftp://linux.jetstreamgames.co.nz/dist/gentoo/ ftp://linux.jetstreamgames.co.nz/dist/gentoo-portage/ ftp://linux.jetstreamgames.co.nz/dist/gentoo-x86-portage/ Knoppix ftp.ihug.co.nz/Linux/CD-images/Knoppix-3.3/ ftp://debian.co.nz/Knoppix/ ftp://linux.jetstreamgames.co.nz/dist/knoppix/ ftp://mirror.inspire.net.nz/knoppix/ Mandrake ftp.ihug.co.nz/Linux/CD-images/Mandrake-9.2/ ftp://debian.co.nz/Mandrake/ ftp://linux.jetstreamgames.co.nz/dist/mandrake/ ftp://ftp.tranzpeer.net/mandrake/ ftp://mirror.inspire.net.nz/mandrake/ RedHat ftp.ihug.co.nz/Linux/CD-images/RedHat-9.0/ ftp.redhat.co.nz/pub/linux/dist/redhat/ (ftp.wicks.co.nz) ftp://ftp.tranzpeer.net/redhat/ ftp://mirror.inspire.net.nz/Redhat 9.0/ ftp://mirror.inspire.net.nz/Redhat%208.0/ ftp://mirror.inspire.net.nz/Redhat%207.3/ Slackware ftp.ihug.co.nz/Linux/CD-images/Slackware-9.1/ ftp://debian.co.nz/Slackware/ Suse ftp://linux.jetstreamgames.co.nz/dist/suse/ Xandros ftp://debian.co.nz/Xandros/ Yoper ftp://linux.jetstreamgames.co.nz/dist/yoper/ ftp://nz1.yoper.com/pub/ Other ftp.ihug.co.nz/Linux/CD-images/Floppyfw-2.04-FloppyFirewall/ ftp.ihug.co.nz/Linux/CD-images/Freesco-0.27-FloppyDistro/ FreeBSD ftp://debian.co.nz/FreeBSD/ ftp://linux.jetstreamgames.co.nz/dist/freebsd/ ftp://ftp.nz.freebsd.org/pub/FreeBSD/ (ftp.tranzpeer.net) ftp://mirror.inspire.net.nz/FreeBSD/

3 3

RE: [nznog] NZ Linux mirrors
by Craig Humphrey 06 Oct '04

06 Oct '04

If I get the go-ahead to set up a site/page with this, I'll set up something to check for "up-to-date-ness". Still, at least these ones exist, unlike many I tried. (unless they're all hiding behind WIX only routes) > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Thursday, October 07, 2004 5:03 PM > To: Craig Humphrey; nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] NZ Linux mirrors > > Hi, > > A number of the links you have shown, i.e. debian.paradise.net.nz are > generally out of date thus of no use. But good work anyways. > > Barry

1 0

RE: [nznog] Modem Pool's
by Wayne Kampjes 06 Oct '04

06 Oct '04

Telecom do a Remote Private Office Network http://www.telecom.co.nz/content/0,3900,201876-201214,00.html Cheers Wayne -----Original Message----- From: Craig Humphrey [mailto:Craig.Humphrey(a)chapmantripp.com] Sent: Thursday, 7 October 2004 11:43 To: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Modem Pool's If you're going to make it that complex, VPN'ing, etc. Why not VPN over the internet? > -----Original Message----- > From: Geraint Jones [mailto:g.jones(a)french-maid.co.nz] > Sent: Thursday, October 07, 2004 11:34 AM > To: Matthew Poole > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Modem Pool's > > To our head office, so I would be looking to maybe have a box > in a rack > with a pool attached so I can then VPN the traffic back to > head office, > as pictured below. > > Sales Reps > | > Modem Pool > | > My Colo'd Server > | > |---VPN Over the net > | > Server at head office > > > > Geraint Jones > Systems Administrator > French Maid Foods Limited > www.french-maid.net > > Tel: +64 (0)4 568 2687 > Fax: +64 (0)4 568 2345 > Mob: +64 (0)21 739 240 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

2 1

RE: [nznog] Modem Pool's
by Craig Humphrey 06 Oct '04

06 Oct '04

If you're going to make it that complex, VPN'ing, etc. Why not VPN over the internet? > -----Original Message----- > From: Geraint Jones [mailto:g.jones(a)french-maid.co.nz] > Sent: Thursday, October 07, 2004 11:34 AM > To: Matthew Poole > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Modem Pool's > > To our head office, so I would be looking to maybe have a box > in a rack > with a pool attached so I can then VPN the traffic back to > head office, > as pictured below. > > Sales Reps > | > Modem Pool > | > My Colo'd Server > | > |---VPN Over the net > | > Server at head office > > > > Geraint Jones > Systems Administrator > French Maid Foods Limited > www.french-maid.net > > Tel: +64 (0)4 568 2687 > Fax: +64 (0)4 568 2345 > Mob: +64 (0)21 739 240

2 1

RE: [nznog] Modem Pool's
by Geraint Jones 06 Oct '04

06 Oct '04

To our head office, so I would be looking to maybe have a box in a rack with a pool attached so I can then VPN the traffic back to head office, as pictured below. Sales Reps | Modem Pool | My Colo'd Server | |---VPN Over the net | Server at head office Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240 -----Original Message----- From: Matthew Poole [mailto:matt(a)p00le.net] Sent: Thursday, October 07, 2004 11:23 AM To: Geraint Jones Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Modem Pool's On Thu, 7 Oct 2004, Geraint Jones wrote: > Completely off topic but I cant really think of anywhere better to post > it. > Does anyone know of an ISP/Telco that will rent a modem pool ? > > I am looking at providing our sales reps with dial in access, and > thought there may be someone on the list that's used this kind of > service. > Do you mean dialup access to the 'net, or dialup access to your network? 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.

2 1

Modem Pool's
by Geraint Jones 06 Oct '04

06 Oct '04

Completely off topic but I cant really think of anywhere better to post it. Does anyone know of an ISP/Telco that will rent a modem pool ? I am looking at providing our sales reps with dial in access, and thought there may be someone on the list that's used this kind of service. 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.

2 1

[Fwd: Warning: spammer seeking services]
by Nic Bellamy 04 Oct '04

04 Oct '04

Hi all, it was suggested to me that this warning might also be NZNOG-worthy. His message to me triggered my spammer-o-meter, so I did some digging: -----Forwarded Message----- From: Nic Bellamy <nic(a)bellamy.co.nz> To: nzlug(a)linux.net.nz Subject: [nzlug] Warning: spammer seeking services Date: Tue, 05 Oct 2004 11:56:31 +1300 Just in case anyone here gets an enquiry from this chap regarding setup of mail servers: Ralph Juliano/Raphael Giuliani <r.juliano(a)verizon.net> Atlas Sales Suite 515, 2700 Market Street (aka. Crestview Apartments) Wilmington Delaware 19802 USA Phone +1-302-762-2828 Fax +1-302-762-5232 He's a spammer. He also seems to lack a sense of humour, as he didn't appear to find my sending him a picture of his apartment funny in the slightest, nor the advice to get a real job. Be vigilant. Cheers, Nic. -- Nic Bellamy <nic(a)bellamy.co.nz> Bellamy Consulting -- Software & Security -- http://www.bellamy.co.nz/ Phone: +64-6-377-4957 Fax: +64-6-377-0505 Mobile: +64-21-251-8954

1 0

Something a bit more on-topic: UK firm recons it's got the busiest interchange!
by Craig Humphrey 04 Oct '04

04 Oct '04

http://news.bbc.co.uk/2/hi/technology/3700290.stm I'm surprised it's bigger than any in the USA or say Germany.

9 10

RE: [nznog] so ... what is the real reason there is whois anyway?
by Frank March 30 Sep '04

30 Sep '04

-----Original Message----- From: Robert Gray [mailto:bob(a)brockhurst.co.nz] Sent: Friday, 1 October 2004 7:30 a.m. Keith Davidson wrote: > InternetNZ has already agreed to implement DNSSEC. Waiting for the > resolution of the issue of "walking the zone" appears prudent. The debate about "walking the zone" has centered on whether this is actually an issue, luminaries such as Joe Abley and Bill Manning have suggested that it is not. Others, well DPF, has suggested that it is. ----------------------------------- The debate is much wider than this. It amounts to whether or not a technical standard circumvents a wider policy issue relating to access to the zone file and WHOIS data. It is an international debate - although as far as .nz is concerned it is an issue of local Internet community concern. There is a tension between those concerned with the technical issues relating to the DNSSEC standard and those concerned with public policy issues - the problem plainly arises from a failure on the part of the standards setters to take the wider policy issues into account... Unfortunate, but certainly understandable. Whether .geek.nz should have a difference policy set from the other unmoderated .nz 2LDs was debated at the time it was established... The outcome has been well canvassed on this list and I will not repeat it. The policy relating to release of the .nz zone file has been recently reviewed and all received views taken into account. The zone file will be released at the discretion of the NZOC and (ultimately) InternetNZ Council provided that there is a clear public interest and the party concerned is prepared to sign up to strict usage criteria. Timing (not the principle) of DNSSEC implementation is also under constant review. All of these matters have been debated in public, there are no hidden agendas, the only concerns have been the best stewardship of .nz in the interests of all Internet users and, especially, those reliant on the .nz DN space According to Robert Gray: <quote>That the society wishes to ignore the views, however well informed, of a "handful of NZNOGers" speaks volumes about the need for industry membership of InternetNZ. Why pay money to be ignored when you can be ignored for free.</quote> To which the only response I can make is that democracy does have its downside for those who find themselves in the minority. ---- Frank March Chair, .nz Oversight committee _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog http://www.govt.nz - connecting you to New Zealand central & local government services Any opinions expressed in this message are not necessarily those of the Ministry of Economic Development. This message and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivery to the intended recipient, be advised that you have received this message in error and that any use is strictly prohibited. Please contact the sender and delete the message and any attachment from your computer.

2 1

ns1,2,3,5.dns.net.nz hot being helpful
by Tim Nicholas 30 Sep '04

30 Sep '04

Hi all, Anyone know why ns1 ns2 ns3 and ns5.dns.net.nz aren't giving out useful information? That's 4 of 7 primary servers for all of .nz and seems to be affecting all of the second level domains. 22:35:04 tim(a)stella ~$ for i in 1 2 3 4 5 6 7; do host -t ns dnc.net.nz ns$i.dns.net.nz;echo; done dnc.net.nz NS record currently not present at ns1.dns.net.nz dnc.net.nz NS record currently not present at ns2.dns.net.nz dnc.net.nz NS record currently not present at ns3.dns.net.nz dnc.net.nz NS ns2.actrix.co.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS record currently not present at ns5.dns.net.nz dnc.net.nz NS ns2.actrix.co.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS ns2.actrix.co.nz 22:37:40 tim(a)stella ~$ Cheers, Tim -- Tim Nicholas || Cilix Email: tim(a)nicholas.net.nz || Wellington, New Zealand http://tim.nicholas.net.nz/ || Cell/SMS: +64 21 337 204

17 42

Notification of NZRR Database changes
by NZRR Database Notifications 29 Sep '04

29 Sep '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, 30 Sep 2004 12:42:53 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409301238310.22181(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040930 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040930 source: NZRR

1 0

ICONZ Prefix update 20040930
by John Johnston 29 Sep '04

29 Sep '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, another prefix list update. Prefix list is attached or can be pulled from http://www.iconz.co.nz/prefix Cheers -- John Johnston Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: +64 21 277-5692 Email:john.johnston(a)iconz.net 0800 THE NET www.iconz.co.nz

1 0

Whois Server Policy Review
by Peter Macaulay 28 Sep '04

28 Sep '04

InternetNZ, through the Office of the Domain Name Commissioner, is reviewing the Whois Server Policy. All aspects of the policy are subject to this review. For more information, including a consultation paper, feedback form, and details about the review working group, please see: http://dnc.org.nz/whois-review Feedback is due by 5pm on Monday 1 November 2004, and comments will be published on the DNC website as they are received. -- Peter Macaulay Executive Director InternetNZ Direct +64 4 495 2113

1 0

Re: [nznog] so ... what is the real reason there is whois anyway?
by Ewen McNeill 28 Sep '04

28 Sep '04

NOTE: operational content here is marginal; replies in email may be best In message <20040929014242.GD5188(a)stateless>, Nicholas Lee writes: >How about restricting access to whois information via a >registration-required web interface, rate limit access dependant on >GeoIP location, and make it difficult for scripts. The New Zealand whois interface is already rate limited (as David mentioned). Taking away the traditional whois interface again (Domainz didn't provide it for a long time) and replacing it with a web interface will reduce the ability for legitimate users to use the traditional tools to look up information (which may be integrated into their workflow). But it won't make it any more difficult for someone who is determined to extract the information from the whois database; HTTP libraries are just as available as TCP/IP connection libraries these days. If you put in a registration step, then again you make it more difficult for someone who is legitimately trying to look up information without really making it more difficult for a scripted solution. If you add a "type in the text from this distorted image" step (eg, a captcha), then there is a proven workaround for such things -- you offer free pr0n to anyone that decodes one of those images, then feed the result back into the system. It's unlikely there'll ever be a short supply of people wanting free pr0n. If you "randomize" the output of the whois information, then you make the service more difficult for legitmate users to use, but again nothing that's particularly hard for a scraping script to work around (if the output is programatically generated then it's almost always programatically parsable, particularly if you only want a subset of the information and aren't too concerned about false parsing). Besides which only one scammer (or enterprising supplier of scammers) needs to extract this information; it can be sold or reused for quite a while after it's extracted. The "useful lifetime" of the information is probably in the order of 6-12 months, and if you get a few "good" scams through in that time, the effort to extract it easily pays off. Since most of the scams that have been effective have been paper-based, and since the main operational need is for an email contact or a phone number contact, possibly the most productive thing to do is review whether the physical address information is made available (by default). But ultimately I think that so long as there's money to be made (and gullible people available to be scammed), such things will continue to happen almost irrespective of how difficult one tries to make it to obtain the information -- at least up to the point where legitimate users have long since given up trying to use the service. And it's not always a good idea to substantially interfere with legitimate use just because of a small amount of illegitimate use. Ewen

1 0

OT: Laptop repairs.
by barry＠unix.co.nz 27 Sep '04

27 Sep '04

Hey guys, sorry to post off topic, just wanted to get a general idea on whats going on here. I bought a laptop 2months ago from Noel Lemmings, top of the range of the NEC model, shortly after getting it I had issues with software freezing etc and then the sound just stopped functioning. I tried installing other OSs on the laptop thinking it was just windows being its self, however the problem occurred on both FreeBSD and Debian linux. I sent the laptop in for repair (Theyve now had it close on 2 weeks) where they said they couldnt find a fault (typical) so I told them to keep it for a few more days. They then did find a fault and said it looked to be hardware related as per what I told them. They sent it in for repair where some other doofis tried to reinstall windows and then 2 days later said it was hardware related and it would take 5 days for a new MB to be sent from Malaysia. Well this morning I was called and asked if it would be alright if they could reinstall my laptop and did I want anything backed up; obviously no notes have been left with the laptop saying that its been reinstalled 11 times in the last 2 weeks and nothing is on the laptop. I call up this afternoon and ask when I can pickup the machine, they tell me that Malaysia dont have stock of my MB and Ill have to wait another 2 weeks before I might get my laptop back. When I asked if this was normal, they said yes, no laptop vendors keep stock in the country, only for desktops. So my questions are 1./ Should they be replacing the laptop with a new one 2./ Do hardware vendors never keep stock of parts in NZ (specially for a new range of equipment) 3./ How long should a laptop be in for repairs if its a P1 (Priority 1) job? Please reply directly. Thanks Barry ------------------------------------------------------------- This mail sent through UnixCo Webmail: http://www.unix.co.nz/

1 1

OT: A bit of a rash
by David Zanetti 27 Sep '04

27 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I know this is off-topic, so please excuse my stupidity in thinking anyone cares about this anyway. I recently partook of some "services", and now I've developed a bit of a rash. At first, I denied it existed, because that would make me unclean, but now it's ruined my life, and I'm losing my hair, and also my dog has developed a bit of an interest in the neighbours. Anyway, I thought I ask here, of all places, if: 1. How long does it normally take for rashes of a random and unspecified nature to go away? 2. What's the going rate for "services"? 3. Just how many people are going to use this list to air completely irrelevent issues ranging from end users with ADSL problems thru to completely offtopic posts about the service you get from random big name retail chains. [Aside: BTW, in case it's not obvious, I am of course joking about the rash. No really.] - -- David Zanetti | (__) #include <geek/unix.h> | ( oo Mooooooo http://hairy.geek.nz/ | /(_O ./ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFBWNqYT21+qRy4P+QRAveOAKCprXgFaYq2C3ZwAC5eMoPPmCx//gCfQgeE vuelU3xnDdmdscfLTDiFHgk= =r8aX -----END PGP SIGNATURE-----

1 0

RE: [nznog] Acceptable levels of Latency, Jitter and Packet loss on national links
by Craig Humphrey 27 Sep '04

27 Sep '04

That's all well and good, but since it's also the only "performance metrics" given in the contract, it's all I have to go on (hence soliciting references from existing customers). It would be nice to get an indication of what performance we can expect, not just "oh, it'll never get worse than this..." I've got a load of questions for the provider around these (and other) issues, so I'll just have to see what they come up with. Later'ish Craig > -----Original Message----- > From: Joe Abley [mailto:jabley(a)isc.org] > Sent: Tuesday, September 28, 2004 2:54 AM [snip snip] > It may actually be that the performance guarantee is a paper-dwelling > construct, and has little or no form in the actual network. > > I have certainly come across providers in my past for whom > performance > guarantees were necessary in order to be able to bid for > projects, but > the cost of deploying infrastructure to support the > guarantees was much > higher than just giving a few refunds now and then. As such the > guarantees didn't really exist outside the billing department. > > > Joe

1 0

RE: [nznog] Acceptable levels of Latency, Jitter and Packet loss on national links
by Donald Neal 26 Sep '04

26 Sep '04

> -----Original Message----- > From: Joe Abley [mailto:jabley(a)isc.org] > Sent: Monday, 27 September 2004 4:09 p.m. > To: Craig Humphrey > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Acceptable levels of Latency, Jitter and > Packet loss on national links > > > On 26 Sep 2004, at 22:25, Craig Humphrey wrote: > > > Latency Jitter IP Packet Loss > > "Realtime" <50ms <12.5ms <0.1% > > "Interactive" <75ms <50ms <0.1% > > "Business" <200ms <100ms <1.0% > > > > And yes, we're chasing references who are already using > this service. > > > > The reason for my dissatisfaction... Based on crude testing > with ping, > > we already get an average of 25ms latency over the 2Mbit/s fibre > > (during > > normal background load), and that's a round trip! So I'm > not sure how > > the above is really an improvement... > > What is the actual RTT over the ethernet service? Normal performance > and guaranteed performance seem very unlikely to be similar (or even > comparable within an order of magnitude). Among other reasons this is because normal performance is seen when things are normal. A provider's performance guarantee is presumably going to have a more demanding specification than just "you'll see numbers like this most of the time". - Donald Neal [All opinions mine only.] Donald Neal |World Domination is Technical Specialist |proceeding according to Operations Engineering |plan. - Andrew Tridgell 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." ------------------------------------------------------------------------------

2 1

Acceptable levels of Latency, Jitter and Packet loss on national links
by Craig Humphrey 26 Sep '04

26 Sep '04

Hi People, We're about to upgrade our site to site 2Mbit/s frame relay WAN links (Akl, Wgn & Chc) to 10Mbit/s fibre into a central cloud, but I'm not entirely happy with the performance levels our provider is offering us. Below I've listed what's on offer, but I wanted to see what other providers consider to be deliverable levels for National links. All thoughts and comments welcome, probably off-list (to keep the noise down), and I can post a summary if people are interested. Latency Jitter IP Packet Loss "Realtime" <50ms <12.5ms <0.1% "Interactive" <75ms <50ms <0.1% "Business" <200ms <100ms <1.0% And yes, we're chasing references who are already using this service. The reason for my dissatisfaction... Based on crude testing with ping, we already get an average of 25ms latency over the 2Mbit/s fibre (during normal background load), and that's a round trip! So I'm not sure how the above is really an improvement... Soon'ish Craig

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 26 Sep '04

26 Sep '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. --- PREVIOUS OBJECT: aut-num: AS24111 as-name: NZRR-AS24111 descr: NZwireless descr: initially peering at '202.7.1.69' descr: see Citylink RT job #929 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR REPLACED BY: aut-num: AS24111 as-name: NZRR-AS24111 descr: nzWireless descr: initially peering at '192.203.154.14' descr: see Citylink RT job #1236 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24111 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040927 source: NZRR --- PREVIOUS OBJECT: route: 203.110.28.0/23 descr: Route for NZwireless - AS24111 origin: AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR REPLACED BY: route: 203.110.28.0/23 descr: Route for nzWireless - AS24111 origin: AS24111 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040927 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS24111 descr: Route set advertised to AS9560 by nzWireless - AS24111 members: 203.110.28.0/23^23-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040927 source: NZRR

1 0

RE: [nznog] nznog research group for NGI?
by Donald Neal 26 Sep '04

26 Sep '04

> -----Original Message----- > From: Daniel Lawson [mailto:daniel(a)wand.net.nz] > Sent: Thursday, 23 September 2004 9:41 a.m. > To: jon.brewer(a)worldnet.att.net; nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] nznog research group for NGI? [...] > The NZ Advanced Network is not about reading webpages. It's not about > downloading mp3s or using Kazaa. It's about shipping multi-gigabyte > volumes of data between research organisations. It's about developing > the next generation of network apps that will rely on this > capacity of > transit. > > As for 15 c/MB charges at Victoria, we face similar charges > at Waikato. > It's one of the reasons we (as a network research group) want this > network - not because we care overly about paying to read > Slashdot every > morning, but because 15 or 10 even 1 c/MB is far too much > when you want > to send 600 GB of network traces to Auckland. And it'll take > too long > across a 10Mbit TC ethernet connection. You know, talking about what specific users plan to do with a research network might actually be operational content, and so on topic for this list. - Donald Neal Donald Neal |World Domination is Technical Specialist |proceeding according to Operations Engineering |plan. - Andrew Tridgell 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." ------------------------------------------------------------------------------

2 1

Sprintlink- Planned Outage Notification
by Jonathan Brewer 25 Sep '04

25 Sep '04

Folks, This came from one of our providers, and I hadn't seen mention of it on the list. Not that 5min is any big deal, but it's nice to know why the pager is going off in the middle of the night. Cheers, JB Dear Valued Customer, Sprintlink, our upstream provider has notified us of an upcoming outage caused by Telecom NZ Ltd performing scheduled maintenance work. Details are as follows: Start date: 3 Oct 04, Sunday Time: 00:01 hrs End date:3 Oct 04, Sunday Time: 01:01 hrs Duration: One 5 minute outage during this window. Reason: Maintenance work by TNZ

1 0

APNIC records to be marked as 'private' for end user delegations
by Mark Foster 23 Sep '04

23 Sep '04

http://www.apnic.net/docs/policy/proposals/prop-007-v001.html http://www.apnic.net/info/faq/privacy-faq.htm As at 30 September client-side delegation information will be hidden from whois - the only info provided will be the ISP involved. Suprised there hasnt been any discussion of this on here so thought id pass it through. (original information sourced via NANOG, where theyre now busy 'discussing' the merits of making life easier for spammers, etc.) Cheers Mark. [posts are imho, as usual]

1 0

new BIND releases today
by Joe Abley 23 Sep '04

23 Sep '04

Fresh out of the oven: BIND 9.3.0 BIND 9.2.4 BIND 8.4.5 For more information, see: http://www.isc.org/sw/bind/ http://www.isc.org/sw/bind/bind9.3.php Joe

5 7

International routing issues yesterday
by Tom Hibbert 23 Sep '04

23 Sep '04

Hi guys, We were stung by a routing issue yesterday affecting us and many of our customers unable to reach most international hosts. Our clients are with lots of different ISPs, and so far we have had confirmation from Orcon (thanks Craig) that there was an issue with the Global Gateway. I'd appreciate if someone from VISP or Iconz could confirm that they were affected too. I know getting an official report from Telecom or GG will be next to impossible, but it would be great if someone from there could tell me which endpoint was affected. Thanks in advance :) Tom Hibbert Technical Specialist Phone: +64-9-306-0230 Technical Helpdesk: +64-9-306-0234 Mobile: +64-274-307-784 Email: tom(a)nsp.co.nz Website: http://www.nsp.co.nz The information in this email and any attachments is confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

1 0

TelstraClear WIX/APE de-peering and national/international cost split
by Bruce Fitzsimons 22 Sep '04

22 Sep '04

Hello list. As a TC Cable customer I'm curious about what the impact of the TC de-peering is going to be on my monthly bill. They've previously announced (and I believe its still on their FAQsite) that they may revisit the current 1:10 cost differential between international and national traffic at some time in the future. I'd hazard a guess that the de-peering may provide some impetus for this, since national traffic sources who don't pay to peer with them may cost them more money. It'd be nice of course if that meant they reconsidered their peering policy, but I won't hold my breath. Anyone heard anything? Have I got the peering cost equation the wrong way around? /Bruce

1 0

nznog research group for NGI?
by Lin Nah 22 Sep '04

22 Sep '04

Looks like the NGI proposal will shut out private or commercial users unless they comply with the Network use policy. All points to setting up a nznog related research group in order to be able to play in it. Unfortunately nothing states the fee required to be a Partner. Anyway they are looking for feedback by 1 Oct "Private Sector shut out of Advanced Network" http://computerworld.co.nz/news.nsf/UNID/35095BD5DF6B4AABCC256F160019E134 http://www.morst.govt.nz/?CHANNEL=IT+INFRASTRUCTURE&PAGE=IT+Infrastructure all a big yawn? lin

8 10

RE: [nznog] nznog research group for NGI?
by Craig Humphrey 21 Sep '04

21 Sep '04

Hi Daniel, This isn't a dig at you... > -----Original Message----- > From: Daniel Lawson [mailto:daniel(a)wand.net.nz] > Sent: Wednesday, September 22, 2004 5:10 PM > To: Simon Lyall; nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] nznog research group for NGI? [snip snip] > I2 won't give us free or cheap gigabit access at home. It will give > universities, other research organisations and similarly minded > businesses a high speed collaborative platform. That's what > it's there for. So an "under subscription" scheme rather than the commercial "over subscription" scheme... Ahhh... That's right, it's better and faster, because almost no one is using it! If bandwidth and technology is cheap enough that the Government can set up something like this and presumably have it economically viable (while excluding fee paying commercial customers), then why can't our existing infrastructure be upgraded to similar or even better capabilities since there would be lots of $$ involved? Maybe I'm just naive... And have over simplified things. Just my 2c. Later'ish Craig

1 0

RE: [nznog] nznog research group for NGI?
by Craig Humphrey 21 Sep '04

21 Sep '04

To quote from Page 28 of the Advanced Network Architecture document: http://www.morst.govt.nz/uploadedfiles/Documents/Current%20work/An%20Adv anced%20Network%20Architecture%20for%20New%20Zealand%20V1.11.pdf "...Beyond the current use of the Internet for email, web-browsing and web-oriented applications, some of the current R+E+I use is to support applications that require peer-to-peer connection between institutions, both nationally and overseas, simply because there is no other economic alternative. For this last important group of applications the overall Internet performance is particularly bad - latency, jitter, low bandwidth and packet loss are aggravated by the volume-oriented cost structures. ..." Is it just me, or is that a nice little dig at the current Internet situation and it's duopoly on International bandwidth (OK, so the likes of IHUG and others have their "own" International links, but they probably pale in comparison to the big two.) Oh and I see that it's primarily IPv4 based, with IPv6 being offered as a service over the top. So much for next generation... Shouldn't this be IPv6 based from the start, with perhaps IPv4 gateways at the fringe? Maybe I just need to read more... But it's home time... Later'ish Craig

1 0

RE: [nznog] nznog research group for NGI?
by Craig Humphrey 21 Sep '04

21 Sep '04

Sheesh... Heaven forbid that someone should set up a network that might compete with Telco's.... Don't you think that if someone can do it better/cheaper, then that's a Good Thing(tm) for competition in NZ. I know the network is supposed to be for "research", but then you could argue that the original NZ backbone (linking the Universities, etc) was too and look where it is now... Then again, maybe you don't want to look... :) Just my 2c. Later'ish Craig > -----Original Message----- > From: Lin Nah [mailto:lin(a)darkmere.gen.nz] > Sent: Wednesday, September 22, 2004 4:35 PM > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] nznog research group for NGI? > > Looks like the NGI proposal will shut out private or commercial users > unless they comply with the Network use policy. > > All points to setting up a nznog related research group in order to > be able to play in it. Unfortunately nothing states the fee required > to be a Partner. > > Anyway they are looking for feedback by 1 Oct > > "Private Sector shut out of Advanced Network" > http://computerworld.co.nz/news.nsf/UNID/35095BD5DF6B4AABCC256 > F160019E134 > > http://www.morst.govt.nz/?CHANNEL=IT+INFRASTRUCTURE&PAGE=IT+In > frastructure > > all a big yawn? > > lin > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

3 2

NZ Network Providers List?
by Evan Taylor 21 Sep '04

21 Sep '04

Hello from Australia, This is my first post to this list, just subscribed - looks interesting! Figured this was the most obvious place to start asking questions ... The organisation I work for has just made some aquisitions in NZ. We have taken over (or about to) an existing network running on the Telecom PON service. I was wondering - is there a global register of network providers in NZ? Currently we are sticking with Telecom as its already implemented, but I would like to research further out and see what other options there are. We have a guide for AUS, http://www.whirlpool.net.au/ Though not completely concise its an excellent start. I'm finding already the Telecom PON service - even the upgraded POM - quite restrictive. I cannot SNMP query any routers (we do all our own stats) nor, can I manage these myself (we also managed all our own gear). DSL in NZ seems quite interesting - up to 8Mbit/s according to the Xtra website? I take it this is not gaureenteed and on distance basis as well. I notice that you utilise full GDMT here - not GDMT.Lite as we do. Without moving off the Telstra DSLAMs I am lucky if I can get 1.5Mbit/s downstream and 256k up. Very interested to know more about providers, carriers, etc. over there in NZ - hopefully might be able to head over in the near future too! Cheers, Ev-

4 5

Telecoms "deadline"
by Richard Patterson 21 Sep '04

21 Sep '04

I was told yesterday by a Telecom employee that the 250,000 goal for Broadband residential users was an ultimatum from the comcom to Telecom saying "reach this otherwise we will unbundle the local loop" Are any ISP's thinking of boycotting UBS or iUBS for the greater good so to speak? or is everyone just going to jump on the bandwagon for slightly faster intarwebnet? -Richard

1 0

OT, Archiving Email
by Gavin Palmer 20 Sep '04

20 Sep '04

Hiya All, Please forgive the OT post. Can anyone shed some light on how long the law requires us to archive/retain email for legal purposes, and is this covered in the new amendment act? Please reply off list if this is too OT. Thanx Gav

1 0

OT: Motorola S1936 (voice/data) interface wanted
by Michael Hallager 19 Sep '04

19 Sep '04

Hi all. Anyone got a Motorola S1936 interface unit? This connects a Motorola carphone to a (RJ11?) standard telecommunications device (phone, fax, dialup modem etc). // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freecall) Mobile: 029 638-7883

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Sep '04

19 Sep '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: Mon, 20 Sep 2004 15:18:43 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409201518200.5722(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.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)wix.net.nz notify: noc(a)ihug.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20031210 changed: rpsl-admin(a)ape.net.nz 20040813 source: NZRR REPLACED BY: 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)wix.net.nz notify: noc(a)ihug.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20031210 changed: rpsl-admin(a)ape.net.nz 20040813 changed: rpsl-admin(a)ape.net.nz 20040920 source: NZRR

1 0

domestic vs. international
by Joe Abley 16 Sep '04

16 Sep '04

Would any access providers who measure such things care to share the ratio of domestic:international traffic, inbound to and outbound from their networks? Back when I was crashing routers in AS 4768 the feeling was that about 20% of traffic stayed local, within New Zealand. That was pre-Southern Cross, though, and it's perfectly possible that the ratio was inflated due to unsatisfied demand. The prices for transit in other countries are much, much cheaper now, and the cost of reaching those countries directly (if you buy your own transmission capacity there) has also gone down substantially, so maybe that would also act to make the ratio lower. On the other hand, as people become more used to doing things over the Internet, you'd expect local content to grow. On yet another hand (four, now?) since so many people are still inexplicably cursed with dialup, maybe that growth would be lower than in other, more enlightened markets. Seems like an interesting question, anyway. I guess this would be easiest to measure at an ISP that used separate domestic and international uplinks (like Telecom used to provision, and may still do for all I know, and like TCL have started to do). If anybody would like to share some numbers, feel free to mail me directly and I can summarise back to the list. Joe

1 0

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

15 Sep '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: Notification of NZRR Database changes (fwd) - Date: Thu, 16 Sep 2004 18:07:06 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409161806400.14082(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16^16-24, 192.107.113.0/24, 192.173.16.0/21^21-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21^21-24, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.32.0/24, 202.36.36.0/22^22-24, 202.36.44.0/23^23-24, 202.36.76.0/23^23-24, 202.36.155.0/24, 202.36.157.0/24, 202.37.76.0/24, 202.37.85.0/24, 202.37.136.0/24, 202.37.140.0/22^22-24, 202.37.144.0/21^21-24, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22^22-24, 202.37.224.0/21^21-24, 202.37.232.0/24, 202.37.252.0/23^23-24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20^20-24, 202.74.224.0/21^21-24, 203.9.179.0/24, 203.9.180.0/24, 210.48.0.0/17^17-24, 210.54.136.0/22^22-24, 210.54.140.0/24, 210.54.160.0/19^19-24, 210.55.24.0/22^22-24, 210.55.182.0/23^23-24, 210.55.253.0/24, 210.56.32.0/20^20-24, 210.185.0.0/18^18-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20030428 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR

1 0

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

15 Sep '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, 16 Sep 2004 18:05:55 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409161802410.14082(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16^16-24, 192.107.113.0/24, 192.173.16.0/21^21-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21^21-24, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.32.0/24, 202.36.36.0/22^22-24, 202.36.44.0/23^23-24, 202.36.76.0/23^23-24, 202.36.155.0/24, 202.36.157.0/24, 202.37.76.0/24, 202.37.85.0/24, 202.37.136.0/24, 202.37.140.0/22^22-24, 202.37.144.0/21^21-24, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22^22-24, 202.37.224.0/21^21-24, 202.37.232.0/24, 202.37.252.0/23^23-24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20^20-24, 202.74.224.0/21^21-24, 203.9.179.0/24, 203.9.180.0/24, 210.48.0.0/17^17-24, 210.54.136.0/22^22-24, 210.54.140.0/24, 210.54.160.0/19^19-24, 210.55.24.0/22^22-24, 210.55.182.0/23^23-24, 210.55.253.0/24, 210.56.32.0/20^20-24, 210.185.0.0/18^18-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR

1 0

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

15 Sep '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, 16 Sep 2004 13:51:53 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409161349450.12852(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.79.85.80/29, 203.109.195.72/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 changed: rpsl-admin(a)wix.net.nz 20040909 changed: rpsl-admin(a)wix.net.nz 20040913 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/29, 210.48.103.112/29, 203.79.85.80/29, 203.109.195.72/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 changed: rpsl-admin(a)wix.net.nz 20040909 changed: rpsl-admin(a)wix.net.nz 20040913 changed: rpsl-admin(a)wix.net.nz 20040916 source: NZRR

1 0

RE: [nznog] PPPOE Performance testing question
by Beatty Lane-Davis 14 Sep '04

14 Sep '04

Hi Neil, > PPPOE Access Concentrator that can easily keep up with > 100Mbit of PPPOE throughput at large sizes, and preferably > all sizes. Any and all brands or thoughts considered. Best bet is an ERX, for so many reasons. You could probably get away with a 7200 with an NPE-400 as a bare minimum, but you'd be happier with a NPE-G1 and almost certainly happiest with the ERX. > In addition, who would be the best people to validate a bit > of equipment for this requirement (assuming we don't end up > buying calibrated and certified test gear). Validate? People? Certification of the smartbits\ixia or of the router you'll be using? I don't recall ever having our test beds validated at the vendor I used to work for, course we never sold any routers either, so that's neither here nor there... ;-) Cheers, b

2 1

PPPOE Performance testing question
by neil gardner 14 Sep '04

14 Sep '04

Sorry if this is offtopic but I think it's close enough :-) We'll be needing to do some performance testing of a product shortly and while we have most of the bits we need (Ixias, smartbits etc) I was wondering if someone could point me to a PPPOE Access Concentrator that can easily keep up with 100Mbit of PPPOE throughput at large sizes, and preferably all sizes. Any and all brands or thoughts considered. In addition, who would be the best people to validate a bit of equipment for this requirement (assuming we don't end up buying calibrated and certified test gear). Cheers - Neil G NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

ICONZ Prefix list update 2004-09-15
by John Johnston 14 Sep '04

14 Sep '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, another prefix list update. Prefix list is attached or can be pulled from http://www.iconz.co.nz/prefix Additions are as follows ip prefix-list ICONZ-national permit 199.212.90.0/23 ip prefix-list ICONZ-national permit 199.212.92.0/23 ip prefix-list ICONZ-national permit 205.233.128.0/21 ip prefix-list ICONZ-national permit 205.233.136.0/23 ip prefix-list ICONZ-national permit 205.233.243.0/24 Cheers -- Regards John Johnston Engineering Manager ICONZ New Zealand Limited DDI: 64 9 977 3500 FAX: 64 9 977 3535 Mob: +64 21 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET http://www.iconz.net

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Sep '04

12 Sep '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: Mon, 13 Sep 2004 17:18:49 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409131717300.2671(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.79.85.80/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.79.85.80/29, 203.109.195.72/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 changed: rpsl-admin(a)wix.net.nz 20040909 changed: rpsl-admin(a)wix.net.nz 20040913 source: NZRR

1 0

Looking Glass and BGP routing tables archive and script available for use
by Adrian Smith 12 Sep '04

12 Sep '04

we are now providing a router Looking Glass service for general use. http://ampz-natlib.natlib.govt.nz/cgi-bin/mrlg-natlib.cgi With ping, trace, and BGP routing table data available, from a Wellington router connected to, and peering with WIX/CityLink and Telecom. Also provided are a few scripts which will pull the same BGP routing table data, diff the tables and store the files in an archive every hour, and then create and update hourly, daily, weekly and monthly reports. These routing table data files are available to view individually, or are down-loadable as a month or year to date tar.gz and tar.bz2 files and may be of use to network research organisations. Only data from 09/09/2004 is available right now, but four weeks worth will be added from a test server over the next week. The idea is to build up some N.Z. Domestic BGP routing tables data history, before the rumored de-peering changes mentioned previously on nznog to WIX and APE, which are due to happen on November 1st 2004 ? These scripts are free to download and use, but are only any use if you run BGP routers. You will then be able to collect your BGP routing table data, before it disappears?; and maybe share it with others on nznog. You can look at the various diff reports to see how your network(s) are being advertised, and see any changes that are taking place, and this may help with diagnosing routing problems. full details at http://ampz-natlib.natlib.govt.nz Adrian Smith National Library of New Zealand t

1 0

Sales Position
by Dream Net-Sales 12 Sep '04

12 Sep '04

Hello, Currently Dream Net Internet www.dreamnet.co.nz are in need of several sales people to work on a commission basis. This can be part or full time. You would sign up customers to Dream Net and earn a commission for doing so. Also we will soon have wireless access available. When this is operating you will be encouraged to contact businesses and the rural community to sell this product. As well as internet access we also supply webdesign and hosting services, which are also available to you to sell. Anyone interested please reply to sales(a)dreamnet.co.nz Regards Adam Fenech Director Dream Net Internet Services LTD www.dreamnet.co.nz

10 9

OT : Squid and http://xtramai.xtra.co.nz
by Geraint Jones 12 Sep '04

12 Sep '04

Anyone know of any issues with xtramail and Squid, we can access the rest of xtra's site, but as soon as you point at xtramail their webserver throws a 500 java.lang.IllegalArgumentException: http://xtramail.xtra.co.nz/: must start with / I can find nothing on squid's site about it Any ides welcome Ta 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 763 378 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.

1 0

Domestic Gentoo Mirror for Global Gateway?
by Dan Clark 12 Sep '04

12 Sep '04

Hi Guys, Does anyone know of a domestic mirror for Gentoo Linux that is available from a Global Gateway connected customer? Kind Regards Dan Clark Technical Director Synaptic Ltd

1 0

Small Internet Service Providers
by Grant Forest 11 Sep '04

11 Sep '04

Good Morning, If there are any Small Internet Service providers looking at selling (vISP or not) or if there is anyone who knows of one/any for Sale, Could you please contact me Off list. Cheers, Grant. -- Grant Forest grantforest(a)eml.cc

1 0

RE: [nznog] Crimes Amendment Act #6
by Scott Walsh 09 Sep '04

09 Sep '04

> > Does any one know where I can get a copy of the Crimes Amendment Act > > #6 I need to know what the story is about sending bulk e-mail from the > > server as I have a client wanting to do so however need to know how > > they can legally do it. (ie by placing opt out at the bottom is that > > sufficient) also is e-mail covered under this act as an offence. > > Check out www.legislation.govt.nz perhaps? I've found the section by section nature of legislation.govt.nz not the greatest if you want to refer back and forth. At the end of this email, I copied the parts of the Act relating Crimes involving computers (which I guessing is the main part you want to look at). As part of the GSEC certification, I wrote a an essay with an overview of the Crimes Amendment Act (http://www.giac.org/practical/GSEC/Scott_Walsh_GSEC.pdf) not directly related to spam, but some of it may be useful (it's all personal option, so don't take it as legal advise). (I'll apology now for the typos in it.) Thanks Scott Walsh Service Implementation Specialist Integrated Technology Services (ITS) - Passionate about Winning IBM New Zealand Limited Level 2, 48 Greys Ave, P.O Box 6840, Wellesley Street, Auckland, New Zealand DDI: +64 9 359 4104 Fax: +64 9 309 3242 Mob: +64 21 307 763 LSC: 0800 802 729 Office: 0800 801 800 http://www.ibm.com/nz This email communication does not create or vary any contractual relationship between IBM and you. Internet communications are not secure and accordingly IBM does not accept any legal liability for the contents of this message. The contents of this email are confidential to the intended recipient at the email address to which it has been addressed. It may not be disclosed to or used by anyone other than this addressee, nor may it be copied in any way. If received in error, please contact IBM on the above switchboard number quoting the name of the sender and the addressee and then delete it from your system. Please note that neither IBM nor the sender accepts any responsibility for viruses. Crimes Amendment Act 2003, Sections 248-253 ``Crimes involving computers ``248. Interpretation- ``For the purposes of this section and sections 249 and 250,- ```access', in relation to any computer system, means instruct, communicate with, store data in, receive data from, or otherwise make use of any of the resources of the computer system ```computer system' - ``(a) means- ``(i) a computer; or ``(ii) 2 or more interconnected computers; or ``(iii) any communication links between computers or to remote terminals or another device; or ``(iv) 2 or more interconnected computers combined with any communication links between computers or to remote terminals or any other device; and ``(b) includes any part of the items described in paragraph (a) and all related input, output, processing, storage, software, or communication facilities, and stored data. ``249. Accessing computer system for dishonest purpose- ``(1) Every one is liable to imprisonment for a term not exceeding 7 years who, directly or indirectly, accesses any computer system and thereby, dishonestly or by deception, and without claim of right,- ``(a) obtains any property, privilege, service, pecuniary advantage, benefit, or valuable consideration; or ``(b) causes loss to any other person. ``(2) Every one is liable to imprisonment for a term not exceeding 5 years who, directly or indirectly, accesses any computer system with intent, dishonestly or by deception, and without claim of right,- ``(a) to obtain any property, privilege, service, pecuniary advantage, benefit, or valuable consideration; or ``(b) to cause loss to any other person. ``(3) In this section, `deception' has the same meaning as in section 240(2). ``250. Damaging or interfering with computer system- ``(1) Every one is liable to imprisonment for a term not exceeding 10 years who intentionally or recklessly destroys, damages, or alters any computer system if he or she knows or ought to know that danger to life is likely to result. ``(2) Every one is liable to imprisonment for a term not exceeding 7 years who intentionally or recklessly, and without authorisation, knowing that he or she is not authorised, or being reckless as to whether or not he or she is authorised,- ``(a) damages, deletes, modifies, or otherwise interferes with or impairs any data or software in any computer system; or ``(b) causes any data or software in any computer system to be damaged, deleted, modified, or otherwise interfered with or impaired; or ``(c) causes any computer system to- ``(i) fail; or ``(ii) deny service to any authorised users. ``251. Making, selling, or distributing or possessing software for committing crime- ``(1) Every one is liable to imprisonment for a term not exceeding 2 years who invites any other person to acquire from him or her, or offers or exposes for sale or supply to any other person, or agrees to sell or supply or sells or supplies to any other person, or has in his or her possession for the purpose of sale or supply to any other person, any software or other information that would enable another person to access a computer system without authorisation- ``(a) the sole or principal use of which he or she knows to be the commission of a crime; or ``(b) that he or she promotes as being useful for the commission of a crime (whether or not he or she also promotes it as being useful for any other purpose), knowing or being reckless as to whether it will be used for the commission of a crime. ``(2) Every one is liable to imprisonment for a term not exceeding 2 years who- ``(a) has in his or her possession any software or other information that would enable him or her to access a computer system without authorisation; and ``(b) intends to use that software or other information to commit a crime. Cf 1961 No 43 ss 216D(1), 229, 244 ``252. Accessing computer system without authorisation- ``(1) Every one is liable to imprisonment for a term not exceeding 2 years who intentionally accesses, directly or indirectly, any computer system without authorisation, knowing that he or she is not authorised to access that computer system, or being reckless as to whether or not he or she is authorised to access that computer system. ``(2) To avoid doubt, subsection (1) does not apply if a person who is authorised to access a computer system accesses that computer system for a purpose other than the one for which that person was given access. ``(3) To avoid doubt, subsection (1) does not apply if access to a computer system is gained by a law enforcement agency- ``(a) under the execution of an interception warrantor search warrant; or ``(b) under the authority of any Act or rule of the common law. ``253. Qualified exemption to access without authorisation offence for New Zealand Security Intelligence Service- ``Section 252 does not apply if- ``(a) the person accessing a computer system is- ``(i) the person specified in an interception warrant issued under the New Zealand Security Intelligence Service Act 1969; or ``(ii) a person, or member of a class of persons, requested to give any assistance that is specified in that warrant; and ``(b) the person accessing a computer system is doing so for the purpose of intercepting or seizing any communication, document, or thing of the kind specified in that warrant. ``254. Qualified exemption to access without authorisation offence for Government Communications Security Bureau- ``Section 252 does not apply if the person that accesses a computer system- ``(a) is authorised to access that computer system under the Government Communications Security Bureau Act 2003; and ``(b) accesses that computer system in accordance with that authorisation.

1 0

RE: [nznog] Crimes Amendment Act #6
by Gordon Smith 09 Sep '04

09 Sep '04

> Does any one know where I can get a copy of the Crimes > Amendment Act #6 I need to know what the story is about > sending bulk e-mail from the server as I have a client > wanting to do so however need to know how they can legally do > it. (ie by placing opt out at the bottom is that > sufficient) also is e-mail covered under this act as an offence. > > Thanks in advance. > Don't know that Amendment 6 addresses email abuse; from memory, I don't think it does. However, spamming in the manner that you're suggesting will do wonders for your connectivity - you'll be creating your own intranet. More than a few providers don't believe in exchanging data with spammers or the networks that host them.....

1 0

Crimes Amendment Act #6
by Cheaphost 09 Sep '04

09 Sep '04

Does any one know where I can get a copy of the Crimes Amendment Act #6 I need to know what the story is about sending bulk e-mail from the server as I have a client wanting to do so however need to know how they can legally do it. (ie by placing opt out at the bottom is that sufficient) also is e-mail covered under this act as an offence. Thanks in advance.

4 4

Notification of NZRR Database changes
by NZRR Database Notifications 08 Sep '04

08 Sep '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, 9 Sep 2004 19:24:24 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409091924070.9670(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20030428 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16^16-24, 192.107.113.0/24, 192.173.16.0/21^21-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21^21-24, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.32.0/24, 202.36.36.0/22^22-24, 202.36.44.0/23^23-24, 202.36.76.0/23^23-24, 202.36.155.0/24, 202.36.157.0/24, 202.37.76.0/24, 202.37.85.0/24, 202.37.136.0/24, 202.37.140.0/22^22-24, 202.37.144.0/21^21-24, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22^22-24, 202.37.224.0/21^21-24, 202.37.232.0/24, 202.37.252.0/23^23-24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20^20-24, 202.74.224.0/21^21-24, 203.9.179.0/24, 203.9.180.0/24, 210.48.0.0/17^17-24, 210.54.136.0/22^22-24, 210.54.140.0/24, 210.54.160.0/19^19-24, 210.55.24.0/22^22-24, 210.55.182.0/23^23-24, 210.55.253.0/24, 210.56.32.0/20^20-24, 210.185.0.0/18^18-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20030428 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16^16-24, 192.107.113.0/24, 192.173.16.0/21^21-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21^21-24, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.32.0/24, 202.36.36.0/22^22-24, 202.36.44.0/23^23-24, 202.36.76.0/23^23-24, 202.36.155.0/24, 202.36.157.0/24, 202.37.76.0/24, 202.37.85.0/24, 202.37.136.0/24, 202.37.140.0/22^22-24, 202.37.144.0/21^21-24, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22^22-24, 202.37.224.0/21^21-24, 202.37.232.0/24, 202.37.252.0/23^23-24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20^20-24, 202.74.224.0/21^21-24, 203.9.179.0/24, 203.9.180.0/24, 210.48.0.0/17^17-24, 210.54.136.0/22^22-24, 210.54.140.0/24, 210.54.160.0/19^19-24, 210.55.24.0/22^22-24, 210.55.182.0/23^23-24, 210.55.253.0/24, 210.56.32.0/20^20-24, 210.185.0.0/18^18-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.109.148.24/29, 203.79.85.80/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.79.85.80/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 changed: rpsl-admin(a)wix.net.nz 20040909 source: NZRR

1 0

Traceroute?
by Craig Spiers 08 Sep '04

08 Sep '04

Anyone got a web based traceroute on a connection to wix? Cheers

1 0

NOC peering pages
by Drew Broadley 07 Sep '04

07 Sep '04

Hi, I was just curious to see what ISPs/companies have their peering lists available online via a URL? I am trying to gather as many resources together as possible for a central repository. Cheers, Drew Broadley

4 3

ICONZ Prefix list update 2004-09-08
by John Johnston 07 Sep '04

07 Sep '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, Yet again, another prefix list update. File attached or grab list from http://www.iconz.co.nz/prefix or have included change below. ip prefix-list ICONZ-national permit 202.12.248.0/21 le 24 -- Regards John Johnston Engineering Manager ICONZ New Zealand Limited DDI: 64 9 977 3500 FAX: 64 9 977 3535 Mob: +64 21 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET http://www.iconz.net

1 0

Douglas Bagnall's Film Making Robot - live on the net
by Richard Naylor 07 Sep '04

07 Sep '04

Douglas Bagnall's Film Making Robot..... is now live on the Internet. You can find its web page here -> http://www.r2.co.nz/20040908/ or look on the live tv page -> http://www.r2.co.nz/live-tv.htm The robot is free to watch on CafeNet -> http://www.r2.co.nz/cn-live-tv.htm The robot produces video for about 12 hours a day and during the "sleep" period processes files for the next day. The webpage for the robot can be found here -> http://halo.gen.nz/robot/ Comments, feedback etc appreciated. rich

1 0

Updates to WIX
by Jonathan Brewer 07 Sep '04

07 Sep '04

Hi Folks, We've got two routers on the WIX, and were happy establishing them via the form here: http://www.citylink.co.nz/cgi-bin/wixape.pl?tmpl=wix.tmpl We'd like to update the networks we're advertising, but seem to be hitting a brick wall as to how to do it. Is there another form online somewhere for making changes? TIA, Jon Brewer

4 4

Notification of NZRR Database changes
by NZRR Database Notifications 07 Sep '04

07 Sep '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: Notification of NZRR Database changes (fwd) - Date: Wed, 8 Sep 2004 13:45:06 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409081342450.5590(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS17474 as-name: NZRR-AS17474 descr: ConceptNET descr: initially peering at '202.7.0.63' descr: see Citylink RT job #1104 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17474 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR REPLACED BY: aut-num: AS17474 as-name: NZRR-AS17474 descr: ConceptNET descr: WIX peering at '202.7.0.63' descr: APE peering at '192.203.154.91' descr: see Citylink RT job #1104 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17474 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS17474 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 07 Sep '04

07 Sep '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. --- OBJECT BELOW CREATED: route: 202.150.96.0/20 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.250.0/24 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR --- OBJECT BELOW CREATED: route: 202.50.176.0/24 descr: Route for ConceptNET - AS17474 origin: AS17474 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17474 descr: Route set advertised to AS9439 by ConceptNET - AS17474 members: 202.150.96.0/20^20-29, 203.97.44.0/24^24-29, 202.49.250.0/24^24-29, 202.50.176.0/24^24-29, 202.127.8.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: craig(a)concept.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040908 source: NZRR

1 0

RE: [nznog] NOC peering pages
by Donald Neal 07 Sep '04

07 Sep '04

Drew, I take it you've seen http://www.wix.net.nz/cgi-bin/ShowRoutes.cgi and http://www.wix.net.nz/cgi-bin/mrlg-wix.cgi and their equivalents at http://www.ape.net.nz/ ? - Donald Neal Donald Neal |World Domination is Technical Specialist |proceeding according to Operations Engineering |plan. - Andrew Tridgell Integration & Services Division +----------------------- Alcatel NZ Ltd - Telecom's network operations manager > -----Original Message----- > From: Drew Broadley [mailto:drew(a)corrupt.co.nz] > Sent: Wednesday, 8 September 2004 10:30 a.m. > To: NZNOG(a)list.waikato.ac.nz > Subject: [nznog] NOC peering pages > > Hi, > > I was just curious to see what ISPs/companies have their peering lists > available online via a URL? > > I am trying to gather as many resources together as possible for a > central repository. > > Cheers, > Drew Broadley > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

2 1

RE: [nznog] WTB: Co-location
by Geraint Jones 06 Sep '04

06 Sep '04

I would also be interested in similar but not for a tower machine looking for either pricing by rack u's or for a full rack preferably in Wellington. As an aside anyone know of any Telco/ISP that do 2Mbit+ in the Petone/Lower Hutt area Ta Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 763 378 -----Original Message----- From: Michael Hallager [mailto:michael(a)networkstuff.co.nz] Sent: Tuesday, September 07, 2004 2:18 PM To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] WTB: Co-location Hello. I would like to purchase co-location for one medium tower computer. Virtual ISP's, dubious companies and resellers need not apply. Immediate need. Kind regards, // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freecall) Mobile: 029 638-7883 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog 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.

5 4

Comparing Inernet access in NZ and other 'western civilisations'
by Paul Adshead 06 Sep '04

06 Sep '04

How does the page linked to below, compare with the current situation/future trends, of internet access in NZ? Where do we see NZ, when comparing against other 'western civilisations' regarding Internet access now and in the future? http://xtramsn.co.nz/technology/0,,7939-3671425,00.html Paul Adshead OTL Software www.otl.co.nz

3 2

WTB: Co-location
by Michael Hallager 06 Sep '04

06 Sep '04

Hello. I would like to purchase co-location for one medium tower computer. Virtual ISP's, dubious companies and resellers need not apply. Immediate need. Kind regards, // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freecall) Mobile: 029 638-7883

2 1

WTB: Cisco x.21 lead for 805.
by Michael Hallager 06 Sep '04

06 Sep '04

Hello all. I would like to buy an x.21 lead to suit a Cisco 805 router. This has an identical connection to a WIC2T. Please contact me off-list. // Michael Hallager Director || Head geek || Making IT work. URL: http://www.networkstuff.co.nz networkStuff, NZ's leading online supplier of high quality new and used networking equipment. Phone: (09) 839-1000 (DDI) 0800 638-788 (Freecall) Fax: (09) 837-8100 0800 329-788 (Freecall) Mobile: 029 638-7883

2 1

ICONZ Prefix list update
by John Johnston 05 Sep '04

05 Sep '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, another prefix list update. Prefix list is attached or can be pulled from http://www.iconz.co.nz/prefix Cheers -- Regards John Johnston Engineering Manager ICONZ Phone: 64 9 977 3500 Fax: 64 9 977 3535 Mob: +64 21 277 5692 http://www.iconz.net

2 1

Telecom Jetstream Out
by David H 02 Sep '04

02 Sep '04

FYI Jetstream in Wellington seems to have been out from 9am this morning - Xtra help(?)desk message says the problem is nationwide and gives no time to resolution. Cheers David

4 3

World-net administrator
by Drew Broadley 01 Sep '04

01 Sep '04

If there are any administrators of World-Net on this list, can someone please contact me off list. Cheers, Drew Broadley

2 1

(no subject)
by Drew.Collins＠apn.co.nz 31 Aug '04

31 Aug '04

We are having issue with the Telecom Frame Relay / ATM network at the moment on all our regional sites connecting back to our main site (ATM connected) in Auckland. This issue is around traffic to and from the sites (i.e. FTP "PUT" from the regional provides us with appox 260Kbs a FTP "GET" gives us 1.2m). This issue started mid last week, and TNZ are still looking at the issue. Drew Collins Group Communications Manager Group IT Services NZ APN Holdings NZ Ltd DDI: +64 9 373 9573 Mobile +64 21 823268 Fax: +64 9 373 6411 Ph: +64 9 379 5050 eMail: drew.collins(a)apn.co.nz Website: www.apn.co.nz ******************************************************************************** NOTICE This email and any attachments are confidential. They may contain privileged information or copyright material. If you are not an intended recipient, you should not read, copy, use or disclose the contents without authorisation as we request you contact us as once by return email. Please then delete the email and any attachments from your system. We do not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company. ********************************************************************************

3 3

Failed checksums on international transfers
by Mark Piper 31 Aug '04

31 Aug '04

Afternoon all, Over the last 24 - 48 hours we have been noticing some strange behaviour with larger international downloads. All national downloads appear to be fine at this stage. Somewhere in transit corruption is occuring causing checksums to fail (3/4 downloads of the same file from the same site will fail cksum & md5sum checks). We have tested http & ftp transfers from serveral sites including sunsite.dk, planetmirror.com & sun.com to several seperate networks here in NZ. We have also tried several machines, running several different OS's including Slackware, Debian/sparc64 and Windows 2000 sp4. Each time the behaviour is the same. Is anyone else experiencing this behaviour with larger transfers? Does anyone have ideas on how we may determine the cause of these checksum / CRC failures? Cheers, Mark

1 0

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

31 Aug '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. 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. 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 ihug Ltd. 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/archives/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 |Diplomacy - Look what Technical Specialist |the university gave me. 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

Notification of NZRR Database changes
by NZRR Database Notifications 30 Aug '04

30 Aug '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 31 Aug 2004 13:29:53 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408311323190.26563(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20030428 changed: rpsl-admin(a)wix.net.nz 20040629 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.173.16.0/21, 202.6.84.0/24, 202.12.70.0/24, 202.14.100.0/24, 202.21.130.0/24, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.45.0/24, 202.36.76.0/23, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20030428 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR

1 0

ICONZ Prefix list update
by John Johnston 29 Aug '04

29 Aug '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, For all that peer with ICONZ, we have an prefix update that needs to be applied. Prefix list is attached or can be pulled from http://www.iconz.co.nz/prefix Cheers -- Regards John Johnston Engineering Manager ICONZ Phone: 64 9 977 3500 Fax: 64 9 977 3535 Mob: +64 21 277 5692 http://www.iconz.net

1 0

RE: [nznog] Xtra's MTA's
by Geraint Jones 26 Aug '04

26 Aug '04

They all have identical Message ID's Ill mail them to xtra Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 763 378 -----Original Message----- From: Ted Grenfell [mailto:ted.grenfell(a)team.xtra.co.nz] Sent: Friday, August 27, 2004 4:30 PM To: Geraint Jones Subject: Re: [nznog] Xtra's MTA's Do they all have the same message ID? I'd suggest grabbing the headers of a couple of the duplicates and emailing them through to abuse(a)xtra.co.nz At 03:44 p.m. 27/08/2004, you wrote: >Anyone have any issues with Xtra's MTA's repeatedly delivering the same >email over and over in an endless loop > > > >I run spam marshal (www.spammarshal.com <http://www.spammarshal.com/> ) >on my external interface, which passes the mail onto my exchange 2003 >server that's inside the firewall, I from time to time get the same mail >coming in over and over, I have looked at spam marshal's logs and it is >actually receiving the email repeatedly. > > > >Anyone else have this issue ? > > > >Geraint Jones >Systems Administrator >French Maid Foods Limited >www.french-maid.net > > >Tel: +64 (0)4 568 2687 >Fax: +64 (0)4 568 2345 >Mob: +64 (0)21 763 378 > >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. > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog Regards, -- Ted Grenfell, ISP Performance Manager, IS CAP - Bus Assure, NZ Business IT, Telecom NZ Limited Mob: +64 274 435 455; DDI: +64 9359 5854; Fax: +64 9377 0781 ICQ: 191891; MSN Messenger: cameleon@ xtra.co.nz Level 2 The Plaza, 2 Hereford St, Private Bag 92028, Auckland CBD This email is for the person(s) identified above, and is confidential to the sender and the person(s). No one else is authorised to use or disseminate this email or its contents. The email or its contents do not necessarily represent the views of Xtra Limited or Telecom. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. 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.

1 0

RE: [nznog] Xtra's MTA's
by Geraint Jones 26 Aug '04

26 Aug '04

They are inbound not outbound ;-) 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 763 378 ________________________________ From: Mike Cooper [mailto:m.cooper(a)actrix.co.nz] Sent: Friday, August 27, 2004 3:50 PM To: Geraint Jones Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Xtra's MTA's It's actually a fault with SBS 2003 - see here: http://support.microsoft.com/default.aspx?scid=kb;en-us;835734 <http://www.actrix.co.nz> Geraint Jones wrote: Anyone have any issues with Xtra's MTA's repeatedly delivering the same email over and over in an endless loop I run spam marshal (www.spammarshal.com <http://www.spammarshal.com/> <http://www.spammarshal.com/> ) on my external interface, which passes the mail onto my exchange 2003 server that's inside the firewall, I from time to time get the same mail coming in over and over, I have looked at spam marshal's logs and it is actually receiving the email repeatedly. Anyone else have this issue ? Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 763 378 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. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog 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.

2 1

Xtra's MTA's
by Geraint Jones 26 Aug '04

26 Aug '04

Anyone have any issues with Xtra's MTA's repeatedly delivering the same email over and over in an endless loop I run spam marshal (www.spammarshal.com <http://www.spammarshal.com/> ) on my external interface, which passes the mail onto my exchange 2003 server that's inside the firewall, I from time to time get the same mail coming in over and over, I have looked at spam marshal's logs and it is actually receiving the email repeatedly. Anyone else have this issue ? Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 763 378 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.

2 1

ADSL PPPOA / PPPOE question
by neil gardner 26 Aug '04

26 Aug '04

Hi guys - quick query... Does anyone know of any PPPOE / PPPOA implementations where the user is required to enter IP/mask and gateway into their CPE? ie. any providers (anywhere in the world) that don't provision this automatically? While I'm here, same Q for RFC1483 Bridged and routed, but I know less about them. Cheers - Neil G NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

ConceptNET Peering/Prefix List Update
by Craig Spiers 25 Aug '04

25 Aug '04

For all those peering with conceptnet, either on ape, or directly - Please update your prefix lists to permit the following below. Changes - Added: ip prefix-list conceptnet-domestic seq 30 permit 203.110.28.0/23 ip prefix-list conceptnet-domestic seq 35 permit 210.54.151.0/24 Full Prefix List: ip prefix-list conceptnet-domestic description ConceptNET Domestic Routes <craig(a)concept.net.nz> ip prefix-list conceptnet-domestic seq 5 permit 202.150.96.0/20 ip prefix-list conceptnet-domestic seq 10 permit 202.127.8.0/22 ip prefix-list conceptnet-domestic seq 15 permit 203.97.44.0/24 ip prefix-list conceptnet-domestic seq 20 permit 202.49.250.0/24 ip prefix-list conceptnet-domestic seq 25 permit 202.50.176.0/24 ip prefix-list conceptnet-domestic seq 30 permit 203.110.28.0/23 ip prefix-list conceptnet-domestic seq 35 permit 210.54.151.0/24 Regards, Craig - ConceptNET

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Aug '04

24 Aug '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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17914 descr: Route set advertised to AS9560 by 2day - AS17914 members: 202.41.136.0/22^22-24, 202.37.240.0/23^23-24, 198.32.66.0/24, 199.212.93.0/24, 202.41.140.0/24 admin-c: JA39-NZRR tech-c: JA39-NZRR notify: rpsl-admin(a)wix.net.nz notify: jabley(a)automagic.org notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040825 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17914 descr: Route set advertised to AS9560 by 2day - AS17914 members: 202.74.224.0/21^21-24, 202.41.136.0/22^22-24, 202.37.240.0/23^23-24, 198.32.66.0/24, 199.212.93.0/24, 202.41.140.0/24 admin-c: JA39-NZRR tech-c: JA39-NZRR notify: rpsl-admin(a)wix.net.nz notify: jabley(a)automagic.org notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040825 source: NZRR

1 0

Wireless ISP
by Stuart 23 Aug '04

23 Aug '04

Hi. This might be sligtly off topic. I have a customer down in Rotorua, and is looking for a good wireless isp. Is there any in Rotorua other than Telstra Clear? Thanks STuart -- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Aug '04

22 Aug '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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64521 descr: Route set for AS64521 members: 202.180.78.0/24, 203.96.31.0/24, 203.96.60.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: siddharth.parekh(a)outwide.co.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040823 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64521 descr: Route set announced to A9439 by Outwide - AS64521 members: 203.96.31.0/24, 203.96.60.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: siddharth.parekh(a)outwide.co.nz mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040823 source: NZRR

1 0

Webcast - PICISOC Conference Vanuatu
by Richard Naylor 22 Aug '04

22 Aug '04

R2 with the support of ISOCNZ and CityLink, are attempting to webcast the PICISOC Meeting being held this week in Vanuatu. The webcast material is (hopefully) being relayed by videoconference tool to Wellington NZ, where the webcast encoding will take place. Details of the Conference can be found at <http://www.picisoc.org>http://www.picisoc.org - Basically it is a 5 day conference from Monday to Friday. The webcast is set to automatically startup on connection from Vanuatu and will run with limited supervision and monitoring from NZ. http://www.r2.co.nz/20040823/ rich

1 0

thanks
by Richard Naylor 17 Aug '04

17 Aug '04

Thanks to all those who did the little audio codec test earlier. Feedback so far is about what I expected, but other opinions are appreciated especially from folks using modems in rural places. I had to simulate that using a GPRS card. As a little thank you http://www.r2.co.nz/20040719/ Please note I put approximate costs for traffic alongside each link - you *have* been warned. rich

1 0

Hello All
by Dream Net-Sales 17 Aug '04

17 Aug '04

Hello, I would like to introduce myself and my company. My name is Adam Fenech and I am the founder/director of Dream Net Internet Services Limited. We are an ISP based in Taranaki with customers New Zealand wide our website is www.dreamnet.co.nz Any comments are welcome. Regards Adam Fenech www.dreamnet.co.nz

4 4

a favour please
by Richard Naylor 17 Aug '04

17 Aug '04

Hi there, I'm testing some audio codecs for suitability in places with very slow links - such as pacific Island, Asia and Rural NZ. Unfortunately I only have high speed net access and get a distorted result. If you have a little time I'd appreciate you listening to the clips and letting me know what you thought of the quality and how MP3 and windows media compare at low speeds (7, 8 or 16 kHz sampling). Would you listen to this sort of programme content ? (ie is it good enough that you would listen). The samples have some voice programmes and some music. I appologise for the taste in music - it was at hand. The test page is at http://www.r2.co.nz/20040812/ Thanks - Rich

1 0

Paradise Issues Today
by Tristram Cheer 16 Aug '04

16 Aug '04

Hey All, Can anyone here give me a stright answer as to what has happened to paradise today, both work and our clients in wellington have had issues twice today for peroids of upto 1 hour each time. Work is on Citylink Connection to Paradise and our clients on DSL and Cable. The first time this morning the paradise helpdesk number was overloaded and we couldnt get an answer, the 2nd time we talked and they said they knew about it and refursed to say anything. Does anyone know anything or do i have to wait a week for them to release a statement? Cheers

9 9

Re: [nznog] Paradise Issues Today
by neil gardner 16 Aug '04

16 Aug '04

>>> Juha Saarinen <juha(a)saarinen.org> 17/08/2004 8:54:27 a.m. >>> >No, no, no... it was leaves on the tracks where the fibre-optic cable >runs. Caused major packet derailment. Seventeen minutes late, water seeping through the cables at Effingham Junction there was a lot of Effingham and a good deal of Blindingham! Twenty-two minutes late, badger ate a juniper at New Malden. Twenty-two minutes late, escaped character, Chessington North. Twenty-two minutes late, fed up by ADSL delays, came by fibre. Slow contractors at Peckham. Apologies to Mr Perrin. Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

Call for Presentations - NZNOG '05
by Donald Neal 15 Aug '04

15 Aug '04

Call for Presentations NZNOG '05 The next conference of the New Zealand Network Operators' Group is to be held in Hamilton between February 2nd and 4th 2005. Our hosts are the University of Waikato's WAND Network research group. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation of network services, with particular emphasis on New Zealand. NZNOG invites presentations on relevant topics. Suitable topics include, but are not limited to: Carrier IP network architecures; Internet exchange activities; VoIP deployment; IP Routing theory or practice; Peering policy; Access technologies including mobile and other wireless; Network and service management tools and practices; Other software relevant to network operation. Presentations from researchers and from practitioners are welcomed. Presentations don't need to fit any particular fixed length. Possible formats range from day-long tutorials to very short presentations floating an idea or reporting on a discovery in a less formal manner. Suggestions for topics for presentations or discussions are also welcome. Prospective presenters should in the first case send email to talks(a)nznog.org describing their intended presentation topic, and giving some idea of the level of detail and length of presentation which would suit them. We'd prefer to receive offers to present sooner rather than later, but there is a timetable: By 22 October 2004: All offers to present received By 31 October 2004: All acceptances of presentations notified. By 24 December 2004: Draft presentation slides received By 9 January 2005: Final presentation slides received A limited number of presentation slots may be available after the closing date for topics of unusual timeliness or importance. Further information, as it becomes available, will be posted at http:// www.nznog.org/ . ------------------------------------------------------------------------------ "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 15 Aug '04

15 Aug '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Mon, 16 Aug 2004 13:38:51 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408161337520.14428(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.109.148.24/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.109.148.24/29, 203.79.85.80/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR

1 0

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

15 Aug '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. --- OBJECT BELOW CREATED: aut-num: AS4831 as-name: NZRR-AS4831 descr: BDT Ltd descr: initially peering at '202.7.1.3' descr: see Citylink RT job #956 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS4831 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: matt(a)nzcity.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR --- OBJECT BELOW CREATED: route: 202.36.76.0/23 descr: Route for BDT Ltd - AS4831 origin: AS4831 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: matt(a)nzcity.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR --- OBJECT BELOW CREATED: route: 210.48.127.0/24 descr: Route for BDT Ltd - AS4831 origin: AS4831 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: matt(a)nzcity.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS4831 descr: Route set advertised to AS9439 by BDT Ltd - AS4831 members: 202.36.76.0/23^23-29, 210.48.127.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: matt(a)nzcity.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040816 source: NZRR

1 0

Telecom UBS "not the service recommended by the Commission"
by Juha Saarinen 13 Aug '04

13 Aug '04

No, not unlimited beer service, but the wholesale DSL thing. In case you've missed it, have a read of these two: http://computerworld.co.nz/news.nsf/UNID/16FA6ACE360C15CACC256EEF003360DD http://www.nzherald.co.nz/storydisplay.cfm?storyID=3584222 I received a media release late yesterday as well, which isn't up on the ComCom Web site yet. Here's a snippet from it: 'Current UBS not the service recommended by the Commission The Commerce Commission is advising businesses that the Unbundled Bitstream Service (UBS) currently being offered commercially by Telecom New Zealand differs significantly from the regulated bitstream service, recommended by the Commission in its unbundling report to the Minister of Communications, and due to come into force shortly. The Commission has become aware that the service being currently offered by Telecom has more limited characteristics than the bitstream service recommended by the Commission. "I would be concerned if telecommunications industry participants signed up to the current Telecom commercial offer under the impression that it was a proxy for the regulated service." said Telecommunications Commissioner Douglas Webb. ' The Commission's bitstream service isn't modelled on the Jetsurf 1GB plan or any Telecom retail plan. Looking at the service description, the commission requires a max upstream of 128Kbit/s and must "have an average of not less than 256Kbit/s" for the downstream, with a throughput rate for end users that mustn't be less than 32Kbit/s. -- Juha

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Aug '04

12 Aug '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 13 Aug 2004 15:23:25 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408131522270.3688(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.109.148.24/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set for Citylink to WIX members: 203.118.144.0/24, 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.97.231.224/28, 210.48.103.0/28, 210.48.103.144/28, 210.48.103.136/29, 203.109.148.24/29, 202.7.4.32/28 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)wix.net.nz 20040112 changed: rpsl-admin(a)wix.net.nz 20040303 changed: rpsl-admin(a)wix.net.nz 20040322 changed: rpsl-admin(a)wix.net.nz 20040407 changed: rpsl-admin(a)wix.net.nz 20040525 changed: rpsl-admin(a)wix.net.nz 20040617 changed: rpsl-admin(a)wix.net.nz 20040622 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040813 source: NZRR

1 0

Re: [nznog] Unbudled Bitstream
by J S Russell 12 Aug '04

12 Aug '04

On Thu, 12 Aug 2004, Dave - Dave.net.nz wrote: > not really wanting to say this but... thats assuming that you use it > 24hrs a day, the average user(not my average use, or probably yours > but...) doesnt use their net connection 24hrs a day, assuming the > average user does 8 hrs a day(a fairly high average I'd have throught), > thats 12kbytes a second, which is just about fine. I'd have throught the > average user would be somewhere nearer to 4 or maybe 6 hours a day, but > anyway. Well, see now, my home machines actually tend to keep doing things via the internet, even when I'm not physically sitting in front of them and looking at stuff in a browser. In fact, I (and most of the people reading this list) tend to be use _less_ traffic at home than "power users" - because all our personal high-bandwidth p2p apps and audio/video streams and suchlike live on servers which tend to be connected to ISP core networks, or live in ISP co-location space. 12K/sec is "fine"? Great! I think I'd like to listen to Twisted Radio's high-quality web stream, and also .... oh, wait, I was going to talk about some other common internet stuff there, but I've pretty much already used up most of 12K/sec. Well, perhaps I'll turn all that stuff off, plunk myself down on the couch, fire up the xbox and pull up one of r2's high-quality video streams to watch on ... oh, no, I guess I sure as hell won't be doing that. And neither will anyone else at 256Kbits/sec, flat rate or not-flat rate. Because 256Kbits/sec is obscenely slow. A key point here is not to think about what most people currently do with their internet connection, it's to think about what they _could_ be doing if they had _real_ broadband. The lost opportunities from this lack of connectivity is the thing that people ought to really be mad about. A 256Kbits/sec bit rate, of which you will be allowed to sustain a fraction thereof, on a service which can do _8Mbits/sec_ is frankly, a load of ass. There are test residential FTTP installations in prodution elsewhere_right now_. True optical to the home - not science fiction, if you live in the right place you can just Go Buy One. I can see that from Telecom if it gets here - 10GBits/sec to the home, and you get a full 10Gbits/sec if you connect to Telecoms content server domains or gaming realms, and if you go anywhere else ... well, as you've pointed out, 12K/sec is "fine" isn't it? Speaking of which, I must point out yet again, The Telecom ADSL product somehow can do a full 8Mbits/sec speed flat-rate _FREE_ connection to one national platform (Jetstreamgames) yet somehow is "not provisioned" to do more than 10GB/month to another national platform (Any Non-Telecom ISP). Hell, TCNZ, I'll just run some optical cable over to wherever your JSG servers are, and .. oh, no, can't do that either. Why? "Policy", last time I asked. As I said in an earlier post to NZNOG, it's just Business As Usual. And you can't blame Telecom for it, they're just trying to protect their stock price and dividend, it's what they're legally obliged to do! It is, however, the job of the government to point at corporate interests and say "Oi! You're in a monopolistic position with regards to this resource, and we're _ordering_ you to do something that you naturally wouldn't do and open it up to others!" That didn't happen, though, did it? I am beginning to agree with other users on this thread. Let's put some alternate infrastructre in place and get some competition going. Woosh wireless manage to offer a flat-rate 256Kbits/sec connection over _cellular_ equipment for chrissakes! No cables AND it's portable! ICONZ Wireless on Waiheke offers 2Mbits/sec symmetical wireless connections, the largest of which offer 10GB of _international_ access for less than $99/month and throws in free totally unmetered line-speed flat-rate domestic access and that's _RETAIL_, not a pretend wholesale product. Sod this ADSL thing - it's damage - route around it. JSR -- John S Russell | Big Geek | Doing geek stuff.

2 1

Telecom a Joke
by Terence 12 Aug '04

12 Aug '04

Three weeks ago I put an order in for Jetstream, for our Richmond Office. Just thought I would call to find out what was happening with the connection. Xtra said that they have run out of ports at the exchange and that I am in a waiting queue for one to come available. They will give no time or date, or if they are going to upgrade the exchange. How much profit did they make last year ?. What about some re investment. Disclaimer : These figures could be wrong 795 mil profit 4 mil people. Annoyed Terence Blyth Managing Director Computer Technologies Ltd 19 Alma Street Box 584, Nelson New Zealand Phone ++ 643 545 9001 Fax ++ 643 545 9002 www.ctec.co.nz PRIVILEGED - PRIVATE AND CONFIDENTIAL This email and any files transmitted with it are intended solely for the use of the addressee(s) and may contain information, which is confidential or privileged. If you receive this email and you are not the addressee (or responsible for delivery of the email to the addressee), please disregard the contents of the email, delete the email and notify the author immediately.

1 0

Re: [nznog] Unbudled Bitstream
by Hamish MacEwan 12 Aug '04

12 Aug '04

Hurrah JSR! > A key point here is not to think about what most people currently do > with their internet connection, it's to think about what they _could_ > be doing if they had _real_ broadband. The lost opportunities from > this lack of connectivity is the thing that people ought to really be > mad about. Exactly. I've met a number of people who deny they have even a Claytons broadband connection in ADSL, since they are unable to use it for fear of exceeding their capacity to enrich Telecom. The 10GB cap on the leisurely 256K we are to be doled out amounts to about a 14% duty-cycle. And I'm bemused as to the location of the "unbundling" in UBS? It looks more and more like it it well and truly bundled to avoid the inconvenience of competition for Telecom. > I am beginning to agree with other users on this thread. Let's put some > alternate infrastructre in place and get some competition going. You ever disagreed with that? Hope truly springs eternal... > Sod this ADSL thing - it's damage - route around it. <grin>, a line from a Digital Strategy response I'm working on: "The Internet was designed for resilience and its ability to route around damage is legend. This ability has often been interpreted to indicate that whatever the Internet routes around is damage, as in the classic, "The Internet interprets censorship as damage and routes around it." The Internet may provide a way to route around the legacy "Last mile," and the closed proprietary Central Office." > JSR Hamish. -- The world isn't worse. It's just that the news coverage is so much better.

1 0

Unbudled Bitstream
by Steve Schmidt 11 Aug '04

11 Aug '04

I heard that TCNZ have changed the details of the UBS service and that now it will be a capped 10gb service. Anyone else know anything about this. Regards Steven Schmidt. 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.

9 8

RE: [nznog] Unbudled Bitstream
by Seeby Woodhouse 11 Aug '04

11 Aug '04

Although the 'new' UBS DSL deal is not as good as the original deal, nor as flexible, I should point out that the traffic limit of 10GB that Telecom has imposed is an AGGREGATE traffic limit across all the users, not a 10GB limit PER user. Currently our JetStream Starter customer base does not use anywhere near 10GB of traffic on average, so hopefully this isn't something that we'll have to worry about. (crosses my fingers that we don't ever go over our limit, and that the overage fees don't get set at 20c/meg) Cheers Seeby -----Original Message----- From: Keith Davidson [mailto:keith(a)wise.net.nz] Sent: Thursday, August 12, 2004 2:32 PM To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Unbudled Bitstream Certainly appears to be the case. See www.orcon.co.nz/company/press/54318/ text follows below. Keith Davidson ________________ "11th August 2004 - New Bitstream plans to remain unchanged On the 27th of July 2004, Orcon released a new, truly affordable 256k Flat rate residential broadband service for $49.95/mth based on the released 'Bitstream' wholesale DSL specification from Telecom. Two week's after Orcon's product release, Telecom have decided to change the specification by imposing a 10GB average traffic limit per user, and an agreement not to promote static IP addresses with the service. Orcon will honor the initial plans offered to customers at our cost, despite the changes that have been made. Orcon is currently the second largest provider of JetStream DSL in NZ, and was the first company to negotiate a Wholesale Services Agreement (WSA) with Telecom for a broad range of services. Orcon has been eagerly awaiting the wholesale DSL portion of the WSA to be finalised, as we believe that we can offer the consumer significantly better deals than are currently available. The moment Telecom told us of their planned Wholesale DSL (UBS) product in early July, we created pricing plans for our own DSL product (based on the Wholesale DSL components we would purchase from Telecom) and set about launching an advertising campaign based on these initial figures - taking a bet that Telecom's final wholesale pricing to us would either be the same or better than the initial figures. The supposed 'final' UBS specification was released by Telecom on 26th July, and as we had guessed, was slightly better than their initial proposal. Our ads for flat rate 256k DSL with a static IP address at the all-inclusive price of $49.95 started to come out a day later. As far as we were concerned, Telecom had finalised the wholesale deal for DSL that they would offer to us, and we had successfully launched our product. After a couple of weeks, with many thousands of advertising dollars already spent, and several hundred new DSL customer signed up, Telecom told us that the UBS specification they had come up with was going to be changed. Specifically, the 'flat-rate' nature of the product and the ability to advertise static IP addresses. We don't know whether the fact that Orcon came out with our flat-rate and static IP address product had anything to do with Telecom changing the specification to withdraw these capabilities, however no other ISPs had come out with any other offering, and therefore our product was seen as a 'reference' product in the market. However - As a champion for affordable broadband, Orcon has decided to wear the 10GB excess traffic charges at our cost so that we can continue to offer a flat rate product, and we will also honor the static IP address for users who have already signed up from an existing promotion wherever possible. We believe that it should the ISPs choice whether to offer Static IP addresses or provide a truly flat-rate service. Seeby Woodhouse MD Orcon Internet Limited" ----- Original Message ----- From: "Steve Schmidt" <sschmidt(a)compass.net.nz> To: "nznog" <nznog(a)list.waikato.ac.nz> Sent: Thursday, August 12, 2004 11:58 AM Subject: [nznog] Unbudled Bitstream > > I heard that TCNZ have changed the details of the UBS service and that > now it will be a capped 10gb service. Anyone else know anything about > this. > > Regards > Steven Schmidt. > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Orcon Internet Prefix List Updaet (2004-08-11)
by Craig Whitmore 10 Aug '04

10 Aug '04

For all those peering with Orcon Internet (AS17746) nationally, please update your prefix lists with the following networks (also in attached file). Added: ip prefix-list orcon-national permit 60.234.0.0/16 le 24 Regards, Craig Whitmore Orcon Internet Network Operations

2 1

6509 Chassis
by J S Russell 09 Aug '04

09 Aug '04

Does anyone on this list have access to a bare Cisco 6509 chassis (preferably also with at least one 240V PSU module installed if possible, but it's not necessary) which they'd be willing to part with in exchange for some combination of dollars and/or a populated Cisco 5513 chassis (Sup2, three 24x10/100 planes, spare Sup1) and/or a lot of beer? If you have one, or could help me at all, please do let me know. JSR -- John S Russell | Big Geek | Doing geek stuff.

1 0

nzWireless peering update
by Andrew Tipton 09 Aug '04

09 Aug '04

For those peering with us on WIX, we have added a new prefix (203.110.28.0/23). Full list: ip prefix-list nzwireless description nzWireless WIX prefixes <andrew.tipton(a)nzwireless.co.nz> ip prefix-list nzwireless seq 10 permit 210.54.151.0/24 le 29 ip prefix-list nzwireless seq 20 permit 203.110.28.0/23 le 29 -- Andrew Tipton Network Engineer nzWireless Ltd (04) 471-0905 (0211) 595-561

1 0

RE: [nznog] APE Funnys - ISC Peering
by Craig Spiers 09 Aug '04

09 Aug '04

Yep, we do.. They requested we configure it about two months ago.. Actually, That about fits the picture.. Don't think it happened before the passwords were configured.. -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: Tuesday, 10 August 2004 1:08 p.m. To: Craig Spiers Subject: Re: [nznog] APE Funnys - ISC Peering Do you have md5 passwords setup? or perhaps they think you do? On Tue, 10 Aug 2004, Craig Spiers wrote: > Anyone else seeing these errors? Happens every few minutes. Has been for a > couple of months now.. (ISC is the only peer I see these with - both > connections) > > > .Aug 10 12:42:51.304 +1200: %BGP-5-ADJCHANGE: neighbor 192.203.154.99 Down > BGP Notification sent > .Aug 10 12:42:51.304 +1200: %BGP-3-NOTIFICATION: sent to neighbor > 192.203.154.99 4/0 (hold time expired) 0 bytes > .Aug 10 12:43:23.328 +1200: %BGP-5-ADJCHANGE: neighbor 192.203.154.99 Up > > Cheers > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > -- Simon J. Lyall. | Very Busy | Mail: simon(a)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 09 Aug '04

09 Aug '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. --- OBJECT BELOW CREATED: aut-num: AS24111 as-name: NZRR-AS24111 descr: NZwireless descr: initially peering at '202.7.1.69' descr: see Citylink RT job #929 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route: 203.110.28.0/23 descr: Route for NZwireless - AS24111 origin: AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route: 210.54.151.0/24 descr: Route for NZwireless - AS24111 origin: AS24111 notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24111 descr: Route set advertised to AS9439 by NZwireless - AS24111 members: 203.110.28.0/23^23-29, 210.54.151.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)wix.net.nz notify: nznog(a)list.waikato.ac.nz notify: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)wix.net.nz 20040810 source: NZRR

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 09 Aug '04

09 Aug '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 10 Aug 2004 10:56:55 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408101055140.13273(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.27.48.0/21^21-24, 202.49.152.0/21^21-24, 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 changed: rpsl-admin(a)ape.net.nz 20040810 source: NZRR

1 0

TEST - PLEASE IGNORE
by J S Russell 08 Aug '04

08 Aug '04

I've suddenly realised that I haven't seen any NZNOG posts for some time. So this is a test. Please ignore. JSR -- John S Russell | Big Geek | Doing geek stuff.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '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. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.27.48.0/21^21-24, 202.49.152.0/21^21-24, 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Mon, 9 Aug 2004 14:08:39 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0408091401400.8879(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW DELETED: aut-num: AS4768 as-name: NZRR-AS4768 descr: University of Auckland descr: initially peering at '192.203.154.114' descr: see Citylink RT job #752 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS4768 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR --- OBJECT BELOW DELETED: route-set: AS9560:RS-ROUTES:AS4768 descr: Route set advertised to AS9560 by University of Auckland - AS4768 members: 130.216.0.0/16^16-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR --- OBJECT BELOW DELETED: route: 130.216.0.0/16 descr: Route for University of Auckland - AS4768 origin: AS4768 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040731 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '04

08 Aug '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. --- OBJECT BELOW CREATED: aut-num: AS9431 as-name: NZRR-AS9431 descr: University of Auckland descr: initially peering at '192.203.154.114' descr: see Citylink RT job #752 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9431 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR --- OBJECT BELOW CREATED: route: 130.216.0.0/16 descr: Route for University of Auckland - AS9431 origin: AS9431 notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9431 descr: Route set advertised to AS9560 by University of Auckland - AS9431 members: 130.216.0.0/16^16-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: c.ashwal(a)auckland.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)ape.net.nz 20040809 source: NZRR

1 0

Accessing www.symantec.com
by Paul Adshead 04 Aug '04

04 Aug '04

Is anyone else having access problems accessing www.symantec.com? Does anyone know if there is any DOS in progress? Thanks, Paul Adshead.

4 3

The New Zealand Network Operators' Group
by Donald Neal 04 Aug '04

04 Aug '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 We're now working towards our next annual conference, to be hosted by The WAND group in Hamilton on February 2nd to 4th, 2005. See http://www.nznog.org/ for details of this year's conference, which drew something over 120 participants. 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 around 690 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. 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 ihug Ltd. 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/archives/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 |Diplomacy - Look what Technical Specialist |the university gave me. 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." ------------------------------------------------------------------------------

2 1

IANA IPv4 allocations and bogon update: 71/8, 72/8
by Rob Thomas 03 Aug '04

03 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hi, team. [ Apologies to those of you who receive this note in multiple forums. ] The numerous Team Cymru bogon projects have been updated as of 02 AUG 2004 to reflect the following IANA allocation made on 02 AUG 2004: 71/8 Aug 04 ARIN 72/8 Aug 04 ARIN 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. Thanks! Rob, for Team Cymru. - -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQQ/hFlkX3QAo5sgJAQEV6gP+PRRJozjAEJ180JTE9KQD+kFsd0n2tQOX TNpOiE4BtjaTfwsZhzgKNYtzRsYdAwL1/zLpWOyjK3J+tllUasxQ+lsDKqGjTVii wATUj+2/JV9VGb14AVkkMz4mSEiNw1rNJxDvy+P40yyECPegWS93Em75DQjrUm3X o5SD7dgJPbI= =2ydr -----END PGP SIGNATURE-----

1 0

RE: [nznog] NTP weirdness
by Eustace, Glen 02 Aug '04

02 Aug '04

Just an FYI, I seem to have fixed our problem. I have added restrict 0.0.0.0 mask 0.0.0.0 nopeer nomodify notrust notrap Which probably should have been there all the time. Win 2k3 is announcing itself in such a way that before the 'restrict' we tried peering with it. Not sure why this wasn't an issue with 4.1.1 Now we simply reply and take no further action. 16:13:30.023910 202.50.245.234.2823 > 130.123.2.99.ntp: v3 sym_act strat 0 poll 17 prec -6 16:13:30.023960 130.123.2.99.ntp > 202.50.245.234.2823: v3 sym_pas strat 2 poll 17 prec -17 (DF) [tos 0x10] -- .*. | Glen Eustace, Infrastructure Development Engineer /V\ | Information Technology Services PN460, Turitea, (/ \) | Massey University, Palmerston North, New Zealand. ( ) | Ph: +64 6 356 9099 x 81005, Fax: +64 6 350 5607, Mob: +64 27 450 0321 ^^-^^ |------------------------------------------------------------

1 0

NTP weirdness
by Glen Eustace 02 Aug '04

02 Aug '04

Hi all, I am need of some help with our public ntp setup. We upgraded our servers from RH7.3 ->FC1 (ntp4.1.1->4.1.2) last week and I have now had several reports of people who are seeing our servers apparently port scanning them :-( I didn't change the config for ntp but can confirm that after their server first asks for the time, we start sending them packets on high UDP ports. The complaints that I have been investigating are Windows servers but that may be a red-herring. I have previously treated ntp as a black-box but am obviously going to have to understand things better. Any help would be appreciated. Glen -- .*. | Glen Eustace, Infrastructure Development Engineer /V\ | Information Technology Services PN460, Turitea, (/ \) | Massey University, Palmerston North, New Zealand. ( ) | Ph: +64 6 356 9099 x 81005, Fax: +64 6 350 5607, ^^_^^ | Mob: +64 27 4 500 321 ------+-----------------------------------------------------

1 0

Fw: ISP Details for inclusion inside DSE ADSL Manuals
by Dan Clark 01 Aug '04

01 Aug '04

This may be of interest to some ADSL operators on here. Kind Regards Dan Clark ----- Original Message ----- From: "Chris Day" <chris.day(a)dse.co.nz> To: <adsl(a)lists.unixathome.org> Sent: Monday, August 02, 2004 5:10 PM Subject: ISP Details for inclusion inside DSE ADSL Manuals > Hi all. > > We are in the process of updating the user manuals and quick start guides for our DSE branded ADSL products. If you are an ISP reselling Telecom's (PPPoA) ADSL services and you would like details to be published in our manuals, please respond to chris.day(a)dse.co.nz with the following information: > > Sales Email: > Sales Phone: > Support Email: > Support Phone: > Weblink: > Company Name: > Primary DNS: > Secondary DNS: > Incoming Mail Server: > Outgoing Mail Server: > > As this this data will eventually be reprinted in all DSE branded ADSL Modems, Routers and Filters, we will also need authorization to redistribute it to consumer market. > > Kind Regards, > > > > Chris Day > Senior Buyer - DSE(NZ)Ltd > email: chris.dau(a)dse.co.nz > Physical: 221 Bush Rd, Albany, Auckland, New Zealand > Postal: Private Bag 102-903, N.S.M.C., Auckland, NZ. > Phone: +64-9-414-2844 - Fax: +64-9-414-2801 - Cell: +64-21-745-411 > > -- > This message is part of the NZ ADSL mailing list. > see http://unixathome.org/adsl/ for archives, FAQ, > and various documents. > To unsubscribe: send mail to majordomo(a)lists.unixathome.org > with "unsubscribe adsl" in the body of the message > >

2 1

ConceptNET Limited Peering Update
by Craig Spiers 01 Aug '04

01 Aug '04

To all those peering with ConceptNET Nationally over APE - we have updated our prefix list. Changes: Added 203.21.31.0/24 Full Prefix List: ip prefix-list conceptnet description ConceptNET Domestic Routes <craig(a)concept.net.nz> ip prefix-list conceptnet seq 5 permit 202.150.96.0/20 ip prefix-list conceptnet seq 10 permit 202.127.8.0/22 ip prefix-list conceptnet seq 15 permit 203.97.44.0/24 ip prefix-list conceptnet seq 20 permit 202.49.250.0/24 ip prefix-list conceptnet seq 25 permit 202.50.176.0/24 ip prefix-list conceptnet seq 30 permit 203.21.31.0/24 Regards, Craig Spiers ConceptNET Limited

1 0

[nzlug] Problems connecting to Telstra Broadband service in
by Jo 30 Jul '04

30 Jul '04

Matthew could you reply back to me re your post in nz.general. Have something to same which cant be done publicly. Real knowledge is to know the extent of one's ignorance. ---Confucius

1 0

Update to ihug prefix list.
by Simon Lyall 28 Jul '04

28 Jul '04

Ihug has updated the list of networks we are advertising across APE and elsewhere. We have added several new networks today. The complete prefix list and the changes are below, they are also available from: http://www.ihug.net/ihug-prefix-list Current Prefix list is: ip prefix-list ihug-networks description ihug peering prefix-list contact: noc(a)ihug.co.nz : Updated 2004-07-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.37.136.0/24 ip prefix-list ihug-networks permit 202.37.182.0/24 ip prefix-list ihug-networks permit 202.37.187.0/24 ip prefix-list ihug-networks permit 202.46.160.0/20 le 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.48.0/24 ip prefix-list ihug-networks permit 202.49.59.0/24 ip prefix-list ihug-networks permit 202.49.63.0/24 ip prefix-list ihug-networks permit 202.49.88.0/23 le 24 ip prefix-list ihug-networks permit 202.49.144.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.240.0/22 le 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 22 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.118.128.0/18 le 24 ip prefix-list ihug-networks permit 203.173.128.0/17 le 24 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 The following networks were added on 2004-07-29: 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.48.0/24 ip prefix-list ihug-networks permit 202.49.63.0/24 ip prefix-list ihug-networks permit 202.49.178.0/24 ip prefix-list ihug-networks permit 202.50.188.0/22 le 22 ip prefix-list ihug-networks permit 203.96.192.0/19 le 24 ip prefix-list ihug-networks permit 210.55.110.0/24 -- Simon Lyall <simon.lyall(a)ihug.co.nz> Senior Engineer, Ihug Ltd, Auckland, NZ

1 0

[nzlug] Problems connecting to Telstra Broadband service in Wellington via a DSE XH1151 Broadband Router? (fwd)
by Matthew Poole 22 Jul '04

22 Jul '04

This is fairly OT, but I figure that the likelihood of someone on here being able to help him is higher than the other lists he posted to. ---------- Forwarded message ---------- Date: Fri, 23 Jul 2004 17:13:00 +1200 From: Chris Day <chris.day(a)dse.co.nz> Reply-To: nzlug(a)linux.net.nz To: adsl(a)lists.unixathome.org, broadband(a)lists.unixathome.org, nzlug(a)linux.net.nz Subject: [nzlug] Problems connecting to Telstra Broadband service in Wellington via a DSE XH1151 Broadband Router? Over the last couple of weeks we have seen an increase in customer calls regarding the use of the DSE XH1151 Broadband Router with the Telstra Wellington Broadband service. For some unknown reason some routers are suddenly dropping the connection. In almost all cases the customer indicates the router has been working fine. It seems to us the properties of the service has somehow changed and we are trying to contact Telstra to resolve the issue but have been unsuccessful in making any meaningful contact. If you work for Telstra or know of anyone in a position of authority that can help us, it would be most appreciated if you could contact ross.hamblin(a)dse.co.nz We are eager to work with Telstra and our manufacturers to resolve this issue. Kind regards, Chris Day Senior Buyer DSE(NZ)Ltd ------------------------------------------------------------------- To remove yourself from this list, email nzlug-request(a)linux.net.nz with "unsubscribe" in the body of the message.

1 0

RE: [nznog] Jetstreamgames Realm Ips?
by NZNOG＠neilnz.com 21 Jul '04

21 Jul '04

Thanks for the prompt replies guys... To summarise: - Yes, there is more than one IP and I now have them so my original idea should work. - I could use DNAT on one or both routers to fix it all at my end. - I wasn't wanting to do transfers between the 2 routers, only between each router and the JSG realm. - I was planning a multithread (2-3 threads per router) FTP DL of a large file, simultaneously from both routers, while measuring speed, error rates, retrains etc from both, then switching ADSL lines and repeating to see if one line is better than the other. A couple of iterations should allow me to factor out line differences. Thanks to all respondents for ideas. Cheers - Neil G

1 0