- NZNOG - lists.nznog.org

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

15 Nov '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 13:43:36 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161337240.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: Route set advertised to AS9560 by ihug - AS7657 members: 203.109.128.0/17^17-24, 203.173.128.0/17^17-24, 203.118.128.0/18^18-24, 203.96.192.0/19^19-24, 210.55.248.0/21^21-24, 202.49.240.0/22^22-24, 202.50.188.0/22^22-24, 202.21.136.0/23^23-24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.49.46.0/23^23-24, 202.49.88.0/23^23-24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.180.0/23^23-24, 192.107.113.0/24, 202.21.130.0/24, 202.36.44.0/24, 202.49.33.0/24, 202.49.48.0/24, 202.49.63.0/24, 202.49.178.0/24, 202.49.186.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.255.0/24, 210.55.110.0/24, 210.55.184.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031210 changed: rpsl-admin(a)nzix.net 20040813 changed: rpsl-admin(a)nzix.net 20040920 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 192.107.113.0/24, 202.21.130.0/24, 202.21.136.0/23^23-24, 202.36.44.0/24, 202.36.94.0/23^23-24, 202.36.230.0/23^23-24, 202.37.182.0/24, 202.49.33.0/24, 202.49.46.0/23^23-24, 202.49.63.0/24, 202.49.64.0/24, 202.49.140.0/24, 202.49.148.0/23^23-24, 202.49.176.0/23^23-24, 202.49.178.0/24, 202.49.180.0/23^23-24, 202.49.186.0/24, 202.49.249.0/24, 202.50.84.0/24, 202.50.103.0/24, 202.50.188.0/22^22-24, 202.50.255.0/24, 203.96.192.0/19^19-24, 203.109.128.0/17^17-24, 203.118.128.0/18^18-24, 203.173.128.0/17^17-24, 210.55.110.0/24, 210.55.184.0/24, 210.55.202.0/23^23-24, 210.55.248.0/21^21-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 192.107.113.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.21.130.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.21.136.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.36.44.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.36.230.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.33.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.46.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.63.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.64.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.140.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.178.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 202.50.188.0/22 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 203.96.192.0/19 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR --- OBJECT BELOW CREATED: route: 210.55.110.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR

1 0

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

15 Nov '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Tue, 16 Nov 2004 13:16:45 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0411161316250.28886(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.4.72/29 descr: Route for FX Networks - AS18406 descr: WIX experimental block origin: AS18406 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR

1 0

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

11 Nov '04

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

1 0

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

11 Nov '04

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

1 0

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

11 Nov '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. --- OBJECT BELOW CREATED: aut-num: AS17705 as-name: NZRR-AS17705 descr: Inspire Net descr: initially peering at '218.100.21.10' descr: see Citylink RT job #1487 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR --- OBJECT BELOW CREATED: route: 203.114.128.0/19 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR --- OBJECT BELOW CREATED: route: 203.79.88.0/23 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR --- OBJECT BELOW CREATED: route: 203.96.157.0/24 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9281:RS-ROUTES:AS17705 descr: Route set advertised to AS9281 by Inspire Net - AS17705 members: 203.114.128.0/19^19-24, 203.79.88.0/23^23-24, 203.96.157.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041111 source: NZRR

7 7

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

11 Nov '04

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

1 0

NZNOG Conference 2005 Presenters
by Donald Neal 08 Nov '04

08 Nov '04

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

1 0

High Class Webcasting
by Richard Naylor 08 Nov '04

08 Nov '04

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

3 4

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

04 Nov '04

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

4 4

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

03 Nov '04

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

2 1

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

03 Nov '04

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

1 0

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

02 Nov '04

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

2 1

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

31 Oct '04

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

1 0

Ihug Prefix list update
by Sainesh Singh 28 Oct '04

28 Oct '04

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

3 2

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

28 Oct '04

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

1 0

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

28 Oct '04

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

1 0

WIX Peering
by Craig Spiers 28 Oct '04

28 Oct '04

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

1 0

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

28 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 12:26:49 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291218530.3561(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24, 202.7.6.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.7.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

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

28 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:47:13 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291145340.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/24^24-29, 202.7.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/24^24-29, 202.7.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route: 202.7.4.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route: 202.7.4.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- OBJECT BELOW CREATED: route: 202.7.7.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

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

28 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:27:06 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291126030.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.6.0/24 descr: Route for Citylink - AS23754 origin: AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24, 202.7.6.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

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

28 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 29 Oct 2004 11:22:53 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410291122070.3438(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.7.6.0/24 descr: Route for Citylink - AS23755 origin: AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

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

28 Oct '04

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

1 0

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

27 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1429] New objects for inclusion in NZRR (fwd) - Date: Thu, 28 Oct 2004 14:30:40 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281429180.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route: 202.135.38.0/26 descr: Route for SolNet Solutions - AS64580 origin: AS64580 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: eric.duggan(a)solnetsolutions.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR

1 0

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

27 Oct '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 28 Oct 2004 14:22:08 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0410281420390.5844(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: Route set for Citylink to APE members: 203.118.144.0/24, 198.48.0.0/22, 202.8.44.0/22^22-24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz changed: rpsl-admin(a)nzix.net 20031118 changed: rpsl-admin(a)nzix.net 20040303 changed: rpsl-admin(a)nzix.net 20040406 changed: rpsl-admin(a)nzix.net 20040629 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 203.118.144.0/24, 202.7.5.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR --- OBJECT BELOW CREATED: route: 202.7.5.0/24 descr: Route for CityLink - AS23754 origin: AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR

1 0

ADSL @ Home
by Geraint Jones 27 Oct '04

27 Oct '04

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

6 5

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