- NZNOG - lists.nznog.org

Re: [nznog] Waiuku/ glen brook area wireless access
by Richard Naylor 29 Sep '05

29 Sep '05

At 10:36 AM 9/30/2005 +1200, Webmaster wrote: >and more beer..... > > >>> Richard Naylor <richard.naylor(a)citylink.co.nz> 30/09/2005 10:30 > >>> >of course using both birds would be nice....but so would lower latency, > >higher bandwidth, cheaper access, no rain, more money, air >conditioning in >the van, cheaper diesel, better hotels, better food, <sigh> it must be friday - is it 4:30 yet ? Are you bringing your thirst down here ? (easier than bringing our fridge up)

1 0

Re: [nznog] Waiuku/ glen brook area wireless access
by Webmaster 29 Sep '05

29 Sep '05

and more beer..... >>> Richard Naylor <richard.naylor(a)citylink.co.nz> 30/09/2005 10:30 >>> of course using both birds would be nice....but so would lower latency, higher bandwidth, cheaper access, no rain, more money, air conditioning in the van, cheaper diesel, better hotels, better food, <sigh>

1 0

Waiuku/ glen brook area wireless access
by Garrett Stoupe 29 Sep '05

29 Sep '05

Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe

5 4

Re: [nznog] Bankdirect phish - perl script
by Webmaster 29 Sep '05

29 Sep '05

I'd suggest that the loop have a longish sleep - say 10 seconds or so - so that it does not look like a denial of service attack. R >>> Liz Q <liz(a)debian.co.nz> 30/09/2005 09:49 >>> If a few of you were to run this in a loop it may screw things up for them #!/usr/bin/perl -w my $url = "http://www.bankdlrect.co.nz/Logon.html"; use WWW::Mechanize; use String::Random; $randstuff = new String::Random; my $fakeuser = $randstuff->randregex('\d\d\d\d\d\d\d\d'); # Prints random digits my $fakepass = $randstuff->randpattern("........"); # Prints random printable characters my $mech = WWW::Mechanize->new(); $mech->get( $url ); #$mech->follow_link( n => 3 ); #$mech->follow_link( text_regex => qr/download this/i ); #$mech->follow_link( url => 'http://host.com/index.html' ); $mech->submit_form( form_number => 1, fields => { username => '$fakeuser', password => 'fakepass', } ); print "Logging into $url with $fakeuser and $fakepass\n"; Liz On Fri, 30 Sep 2005 08:55, James Clark wrote: > Craig Box wrote: > > Just got a phish for BankDirect. The telling part: "<a > > href="http://www.bankdlrect.co.nz/index_secure.asp" >" > > I've seen this phish aswell. > > Cheers, > James. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog -- It's a poor sort of memory that only works backwards. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Re: [nznog] Bankdirect phish
by Webmaster 29 Sep '05

29 Sep '05

It has just occured to me that a good way to 'deal' with phishing sites prior to them being shut down might be to have a script that submits random usernames and passwords. Thousands of them. It would certainly make it much harder for the phisher. cheers, Richard >>> "Craig Box" <Craig(a)itpartners.co.nz> 30/09/2005 08:52 >>> Just got a phish for BankDirect. The telling part: "<a href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. The domain is registered with DiscountDomains.co.nz to a RODNEY GUISTWITE. admin_contact_name: RODNEY GUISTWITE admin_contact_address1: 9740 CONIFER LANE admin_contact_city: MURRELLS INLET admin_contact_country: US (UNITED STATES) admin_contact_phone: +84 3 6501641 admin_contact_email: directmain(a)yahoo.com The email headers: Received: from firewall.itpartners.co.nz ([10.7.0.254]) by penfold.itpartners.co.nz with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Sep 2005 08:46:23 +1200 Received: from [218.233.125.18] (helo=-1208382648) by firewall.itpartners.co.nz with smtp (Exim 4.34) id 1EL5Iv-0007GJ-5u for craig(a)itpartners.co.nz; Fri, 30 Sep 2005 08:47:04 +1200 Received: from bankdirect.co.nz (-1208528168 [-1208791160]) by google.com (Qmailv1) with ESMTP id 554E5D0054 for <craig(a)itpartners.co.nz>; Thu, 29 Sep 2005 13:13:12 -0700 Date: Thu, 29 Sep 2005 13:13:12 -0700 From: Bankdirect Accounts <accounts(a)bankdirect.co.nz> X-Mailer: The Bat! (v2.00.8) Personal X-Priority: 3 Message-ID: <5432025998.20050929131312(a)bankdirect.co.nz> To: Craig <craig(a)itpartners.co.nz> Subject: New Fraud-Prevention system. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------C0723C19AFB5862" X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: -5.8 {-----} X-Spam-Report: No, hits=-5.8 required=5.0 tests=ALL_TRUSTED,BAYES_00,HTML_MESSAGE,HTML_TAG_EXIST_TBODY autolearn=ham version=3.0.2 Return-Path: accounts(a)bankdirect.co.nz X-OriginalArrivalTime: 29 Sep 2005 20:46:23.0798 (UTC) FILETIME=[DAB2BD60:01C5C536] Craig Box Phone 07 957 2653 IT Partners Ltd Fax 07 957 2659 PO Box 9361 Mobile 021 475 869 Hamilton, New Zealand _________________________________________________________________ #include <standard-disclaimer.h> _________________________________________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 9

Re: [nznog] Bankdirect phish
by Craig Box 29 Sep '05

29 Sep '05

> Anyone want to donate a large chunk of bandwidth to the cause? I'm sure a well placed phone call could probably achieve a better end result. :) > Well, the phish website is still up and running, and it is *very* well > done. I didn't get any certificate warning when going to the https site, > and it looks exactly like the real one. They even promote the NetCODE > security system, and all of the links on the page point to the real site. That's because the site is actually only http:// - go to the https:// site and you get an expired cert for localhost.localdomain. Craig

1 0

Re: [nznog] Bankdirect phish
by Kerry Thompson 29 Sep '05

29 Sep '05

Craig Box said: > Just got a phish for BankDirect. The telling part: "<a > href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. Well, the phish website is still up and running, and it is *very* well done. I didn't get any certificate warning when going to the https site, and it looks exactly like the real one. They even promote the NetCODE security system, and all of the links on the page point to the real site. -- Kerry Thompson IT Security Consultant http://www.crypt.gen.nz

1 0

Re: [nznog] Bankdirect phish
by Craig Box 29 Sep '05

29 Sep '05

> The email headers: The offending message can be found in full at http://www.hs.net.nz/~crb/New_Fraud_Prevention_system_.msg. Craig

1 0

CFP: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 28 Sep '05

28 Sep '05

Call for Presentations Systems Administration Miniconf, linux.conf.au 2006. This is a call for presentations for a 2 day Linux Systems Administration mini conference that will be held as part of the linux.conf.au conference in January 2006. The conference will be held in Dunedin, New Zealand. Miniconferences are held on the first two days, prior to the main programme. Please see our website at http://sysadmin.miniconf.org/ for details. The organisers of the Systems Administration Miniconf would like to invite proposals for presentations to be delivered at the Miniconf. Topics for presentations could include (but are not limited to) Samba, Databases, Backups, Firewalls, AAA, Troubleshooting, Buying Decisions, VPN, Virtual machines (Xen, UML, VMware), Monitoring Software, Web/Mail/LDAP/etc Server software, Wikis, PHP, Spam and Virus Filtering, VOIP, Trouble Ticket System, Best Practices, New Developments, Clustering/High Availability , Automated Installs, Automated configuration, Packaging Local Software. Speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ----------------------- Presentations of between 30 and 120 minutes (including questions) are currently being sought. We will also be holding a lightning talks session, with a list of 5-10 minutes short presentations.. Submitting talks ---------------- Please note that in order to give a presentation you must be register to attend the main linux.conf.au conference. In order to submit a talk please see our Call for Presentations webpage at: http://sysadmin.miniconf.org/cfp.html Submissions (or any questions) should be sent to: contact @ sysadmin.miniconf.org. Dates and Deadlines ------------------- To encourage early submissions around half the programme will be filled from presentations submitted before the 31st of October. 31 Oct 2005 - Deadline for early submissions 18 Nov 2005 - Deadline for late submissions Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Re: [nznog] Waiuku/ glen brook area wireless access
by Paul Norton 28 Sep '05

28 Sep '05

you could give satellite a go.. http://www.stuff.co.nz/stuff/0,2106,3423872a28,00.html ________________________________ From: Jeremy Strachan [mailto:JeremyS(a)cclnz.co.nz] Sent: Thursday, 29 September 2005 14:20 To: Garrett Stoupe Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Waiuku/ glen brook area wireless access Iridium Satellite phone?!! and you thought we lived in a developed country... ________________________________ From: Garrett Stoupe [mailto:garretts(a)te.co.nz] Sent: Thursday, 29 September 2005 2:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Waiuku/ glen brook area wireless access Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe "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] Waiuku/ glen brook area wireless access
by Jeremy Strachan 28 Sep '05

28 Sep '05

Iridium Satellite phone?!! and you thought we lived in a developed country... ________________________________ From: Garrett Stoupe [mailto:garretts(a)te.co.nz] Sent: Thursday, 29 September 2005 2:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Waiuku/ glen brook area wireless access Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe

1 0

Audio Streaming
by Webmaster 28 Sep '05

28 Sep '05

Radio NZ is nearing the end of the testing phase of the live audio streams of National Radio and Concert FM. As a result of feedback from the tests we have removed the 16 kbs cap from our US server. This means that the streams can go up to 48 kbs stereo (National Radio) and 64 kbs (Concert FM) for ALL end users regardless of their location. At present about 40% of the traffic from this server is NZ bound. The streams are also available via NZ exchange points should operators wish to avoid the more expensive international route. regards, Richard Hulse

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Sep '05

25 Sep '05

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Sep '05

25 Sep '05

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

1 0

What would the NZ numbers be?
by Juha Saarinen 22 Sep '05

22 Sep '05

http://computerworld.co.nz/news.nsf/netw/40778CA910E0E6B4CC25707D007A6977 Anyone know? -- Juha

1 0

Orcon support email - auto reply. Anyone from orcon listening??
by Gavin Legge 22 Sep '05

22 Sep '05

Yeah it's still coming through - if anyone at orcon is on here - they may want to unsub there support address so it does not auto reply all the time to the poster. The following came from support(a)orcon.net.nz in reply to my post... <include message> Thankyou for emailing Orcon customer support. Your email has been received and will be processed as quickly as possible, however we are experiencing some delays at present due to high customer demand so it may take up to 96 hours to get an initial response. We've just implemented a new ticketing system to allow better tracking of customer enquiries and orders - and your email has been assigned the identifier: FZT-83853-666. Please ensure you keep this ticket ID in the subject line of any related replies. Warm regards, Orcon Customer Support. Auckland: (09) 444-4414 Freephone: (0508) 4ORCON 8am - 8pm Monday-Friday 11am - 8pm Saturday/Sunday and public holidays -------------------------------------------------------------- In the interim, please check out the following items which may allow you solve your problem on your own: GENERAL: * Basic configuration settings http://www.orcon.net.nz/help/settings/nz/ DIALUP * Current pricing plans and signup http://www.orcon.net.nz/products/dialup/ DSL * Want to upgrade to Orcon's new BitStream 256k service ($49.95/month) http://www.orcon.net.nz/shortcut/getbitstream * Current pricing plans http://www.orcon.net.nz/products/jetstream/ * Experiencing high ping times/latency? See the following link for information http://www.orcon.net.nz/help/kb/ADSL/latency BILLING * Frequently asked questions about your billing http://www.orcon.net.nz/help/billing/ If any of the above links help answer the query you just emailed us, if possible please do us the courtesy of emailing us saying the problem is "resolved" so we can attend to other customer's queries. --- Kind Regards Gavin Legge Security Officer [Linux Systems Administrator] g.legge(a)irl.cri.nz 04 931 3131 (ext 4131) 021 905 461 This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

Re: [nznog] Vodafone dial pattern - another change ?
by Gavin Legge 22 Sep '05

22 Sep '05

I used to work for a telco and on many occasions observed overlap sending on ISDN's working fine. This while watching test instruments across live lines. - so yeah - it's used out there for sure... Go for it. -----Original Message----- From: Ian Batterbee [mailto:ian.batterbee(a)aut.ac.nz] Sent: Friday, 23 September 2005 1:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Vodafone dial pattern - another change ? >Surely the delay thing is why most VoIP type systems accept something >such as "#" as an "I've finished inputting my number, please dial it" >indicator ? > > Although we do operate a VoIP system, that's largely irrelevant, because our previous PBX (Ericsson MD110) had all the patterns configured into it as well, so we would have been in the same situation. Users don't expect to have to dial a # at the end of their number, and we shouldn't expect them to have to do so. >Is the 5 seconds tuneable ? "wait 5 seconds till the 5th digit has been >entered then change this to 3 seconds till the 7th digit then change >this to 1 second" > The 5-second delay is coming from TelstraClear.. so no, we can't tune it. They're waiting for another digit, and when I posted about last month, it was because TCL's pattern was actually incorrect, and was waiting for extra digits that would never come, resulting in an unncessary 5 second setup delay to a large number of 021 numbers. This has since been corrected. A number of PBX systems validate the numbers so that they can match and therefore route them down the most appropriate route. Our (Cisco) PBX comes with patterns for most countries, which simplifies the task of setting up a new system. While I agree NZ's plan is relatively simple, other countries are not, and that's probably the reason they do it that way. There is the possibilty that we could enable overlap sending.. which I believe means that you send each digit as it is dialled, rather than all at once in an ISDN SETUP message - as it gives the telco the option to send back 'more needed', or 'that's enough digits'.. but.. I'm reluctant to turn it on without some proper testing first. Thanks to Barry who found the info I needed, and finally, to those of you who do validate the numbers locally, and who were forced into silence before posting anything by Steve's helpful comments, here are the new patterns: 021 0221 XXXX 021 0222 XXXX I believe there may be more coming. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

2 1

Re: [nznog] Vodafone dial pattern - another change ?
by Ian Batterbee 22 Sep '05

22 Sep '05

>Surely the delay thing is why most VoIP type systems accept something >such as "#" as an "I've finished inputting my number, please dial it" >indicator ? > > Although we do operate a VoIP system, that's largely irrelevant, because our previous PBX (Ericsson MD110) had all the patterns configured into it as well, so we would have been in the same situation. Users don't expect to have to dial a # at the end of their number, and we shouldn't expect them to have to do so. >Is the 5 seconds tuneable ? "wait 5 seconds till the 5th digit has been >entered then change this to 3 seconds till the 7th digit then change >this to 1 second" > The 5-second delay is coming from TelstraClear.. so no, we can't tune it. They're waiting for another digit, and when I posted about last month, it was because TCL's pattern was actually incorrect, and was waiting for extra digits that would never come, resulting in an unncessary 5 second setup delay to a large number of 021 numbers. This has since been corrected. A number of PBX systems validate the numbers so that they can match and therefore route them down the most appropriate route. Our (Cisco) PBX comes with patterns for most countries, which simplifies the task of setting up a new system. While I agree NZ's plan is relatively simple, other countries are not, and that's probably the reason they do it that way. There is the possibilty that we could enable overlap sending.. which I believe means that you send each digit as it is dialled, rather than all at once in an ISDN SETUP message - as it gives the telco the option to send back 'more needed', or 'that's enough digits'.. but.. I'm reluctant to turn it on without some proper testing first. Thanks to Barry who found the info I needed, and finally, to those of you who do validate the numbers locally, and who were forced into silence before posting anything by Steve's helpful comments, here are the new patterns: 021 0221 XXXX 021 0222 XXXX I believe there may be more coming.

1 0

Vodafone dial pattern - another change ?
by Ian Batterbee 22 Sep '05

22 Sep '05

In the last 24 hours I've heard from multiple sources that Vodafone is now using 8 digit prepay numbers - the numbers I was given that were reported 'not working' (because our PBX didn't match all the digits) were both 021-0222xxxx, ie, 8 digits after the 021. I know I asked about this only one month ago, but back then 021[012] only appeared to require 6 further digits, and not 7. I've just tried calling both 0222xxxx numbers from my vodafone mobile, and they they both rang. I tried leaving the last digit off, and they both failed, so it does suggest that things have changed. Does anyone know what's going on, and/or what the correct prefix for this number pattern is ? If I change my end to match 0210 plus 7, it will introduce a 5 second delay into any numbers that only have 6 digits after the 0210 -- Ian Batterbee, CCNP Senior Network/Comms Technician Auckland University of Technology

6 8

Want to sell the syntax S648 motherboard
by Kevn Wong 21 Sep '05

21 Sep '05

Dear sir, Now we have some syntax Syntax S648 motherboard in stock, they are all new original retail box unopen products. our offer is US$25.00/Pcs, if you are interesting in them, please feel free to contact me, thanks. Have a nice day Best Regards Kevin http://www.syntaxusa.com/catalog/product_info.php?cPath=44_46&products_id=68 Description ・ Intel Motherboard S648 Special Features ・ Socket 478 board that supports Intel Pentium 4 processor up to 533Mhz FSB ・ Integrated with the most advanced technologies - SiS MuTIOL media I/O Magic Setting, USB 2.0 (SiS 963) ・ USB 2.0 ・ Supports Ultra DMA 133/100 Specifications - Processors ・ Socket 478 for Intel Pentium 4 processor ・ FSB 533/400 MHz ・ Supports Hyper-Threading Technology - Chipset ・ North Bridge: SiS 648 ・ South Bridge: SiS 963 - Memory ・ 3 DDR DIMM sockets Support ・ 3 x 2.5V DDR SDRAMs (DDR266/DDR200) or ・ 2 x 2.5V DDR SDRAMs (DDR333) ・ Max. 3GB (2GB only for DDR333) - Graphics ・ 8X AGP - Sound ・ Compliant with AC97 2.2 specification - LAN ・ RealTek RTL8100/B 10/100 Mbps Fast Ethernet Controller - IDE ・ 2 UltraDMA 133/100/66/33 - USB ・ 6 USB 2.0 - Expansion Slots ・ 1 AGP 8X ・ 5 PCI ・ 1 CNR - Back Panel I/O Ports ・ 1 PS/2 Mouse ・ 1 PS/2 Keyboard ・ 1 Parallel ・ 2 Seria ・ Game port ・ 1 LAN ・ 2 USB ・ 1 Line-in ・ 1 Line-out ・ 1 Mic-in - Internal I/O Connectors ・ 2 USB 2.0 headers support additional 4 USB ports ・ Front Panel MIC/Line out header ・ SIR header ・ HDD LED, Reset switch, Power switch headers ・ ATX power connector ・ CPU/Power/Case fan Connectors - BIOS ・ Award 2MB flash EEPROM ・ Supports Plug and Play 1.0A, AMP 1.2, multi boot, DMI ・ Support ACPI V1.0 specification - Form Factor ・ ATX - Board Size ・ 12" x 9.6" (305mm x 244mm) - RTC & Battery ・ SiS 963 built-in 256 bytes of CMOS SRAM ・ With CMOS hardware clear jumper

1 0

Re: [nznog] Further Analysis of Election Night
by Regan Murphy 21 Sep '05

21 Sep '05

I'm with xtra for DSL at home. I don't seem to transit via the US to get content from the r2 servers. -----Original Message----- From: Dan Clark [mailto:dan(a)synaptic.net.nz] Sent: Thursday, 22 September 2005 6:59 p.m. To: Richard Naylor Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Further Analysis of Election Night mostly Xtra customers connecting to the US server no doubt? Dan

4 3

Further Analysis of Election Night
by Richard Naylor 21 Sep '05

21 Sep '05

Further analysis of the Election period webcast ----------------------------------------------- We have now had some time to analyse log files from the election period. The following observations are made. It should be understood that there were 4 servers, USA - 1 AKL - 2 (CityLink and TVNZ) WLG - 1 We have not had access to the TVNZ log files and so the following comments are based on analysis of 3 servers only. These servers were carrying 62% of the load (by traffic) It also needs to be understood that these servers were not set up solely for the election event and carried on handling day to day 24x7 streaming. So in looking at log files, there are many streams and services (such as on demand video or audio files) which were operating regardless of the election. Equally many of the stations which we stream had no particular coverage of the election and carried on their usual Saturday night programmes. As a result some analysis requires a little local knowledge to make sense. In addition, R2 was providing on-demand services to 3 political parties involved in the election. Several parties had closing video clips or focussed their multi-media assets for the closing stages of the campaign. This produced extra traffic on election day. In some cases a surprising number of hits. We also carried a number of election related events such as The Labour Party Election Campaign launch The InternetNZ ICT Candidates debate Election Fiscal Update (access via Scooop.co.nz) Several Press Briefings by the PM (access via Scoop.co.nz) Candidate debates (access via RadioNZ.co.nz) As a result a very rough estimate is that the last month has seen server traffic double. On election night, over 40 countries accessed the 3 CityLink servers. They were NZ 36% Australia 12% US 8% UK 2.5% France 1.5% Canada Japan Netherlands Singapore Switzerland Germany Czech Republic Italy Brazil Thailand Poland Malaysia Austria Saudi Arabia Israel India Hungary Taiwan Turkey Spain Slovakia Belgium Sweden Denmark Norway Fiji Azerbaijan United Arab Emirates Russia Philippines The top 15 countries all accessed over 1GBytes of data Of great interest to us is the access to the USA server as its usage is designed to handle international interest under a strategy of locating servers as close to the clients as possible, so that over time, higher quality material (audio or video) can be delivered. The USA server received connections from NZ 30% Australia 20% USA 10% UK 3.7% Japan 1.5% Singapore 1.3% With 3 servers located in NZ, there was no need for traffic from the US server to NZ. This is caused solely by poor peering by NZ ISPs. It represents some 10Mbps of traffic.

3 3

Useful BGP tool
by Gordon Smith 21 Sep '05

21 Sep '05

A little something that's quite useful for looking at route advertisement trends over time. It complements the use of route-servers quite well when looking at BGP path changes internationally. Found the link on NANOG http://bgpinspect.merit.edu/

2 1

Re: [nznog] [afnog] ARIN to allocate from 74/8 & 75/8
by Rob Thomas 20 Sep '05

20 Sep '05

Hi, Randy. ] but, as you seem to understand, that's only half the story. luckily, ] the other, more useful, half is easily testable if arin/cymru would ] just follow the long-discussed path. We couldn't agree more! That's why we stood up the following three pingable IP addresses prior to announcing the test prefixes. 74.63.1.2 75.127.1.2 76.191.1.2 Sorry those weren't announced sooner! Thanks, Rob, for Team Cymru. -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999.

1 0

Woosh prefix update
by Nathan Ward 20 Sep '05

20 Sep '05

We are now advertising an additional prefix to our APE and WIX connected peers, including the route servers for these exchanges. I also ask that anyone not currently accepting up to 24 bit long prefixes in our advertisements, to please do so. We have no need to advertise these now, but we'd like to have the option available if needed, yadda yadda. The new prefix is 203.211.64.0/20. So, in the end it should look something like: ip prefix-list woosh-in seq 5 permit 202.74.192.0/19 le 24 ip prefix-list woosh-in seq 10 permit 203.211.64.0/20 le 24 Other potentially useful details follow: ASN 17412 APE IP 192.203.154.49 WIX IP 202.7.0.50 For those of you who are not currently peering with us and would like to arrange direct peering sessions, please contact me offlist, or on +64-9-522-3699, ext 618. -- Nathan Ward

2 1

Election Night Statistics
by Richard Naylor 20 Sep '05

20 Sep '05

Election Night Webcasting Statistics On Election night, 2005, CityLink/R2 was involved in assisting a number of broadcasters with their streaming requirements. This was in addition to the normal webcasting activites being carried out with other TV and radio stations. Particular focus was placed on TV-One (TVNZ) TV-3 NewstalkZB National Radio The streaming was carried out using servers located in Auckland, Wellington and Palo Alto (USA). Encoding was carried out by TVNZ and CityLink/R2. In terms of number of viewers, the 2003 Lord of the Rings premiere has been regarded as the biggest event webcast to date. The election night figures passed that by approximately 50%. On election night, some servers used anycast routing to spread traffic between servers, so that viewers connected to the server closest to them by Internet topology. Because not all servers used anycasting, we experienced congestion on the link feeding the US based server. As a result, some viewers used the link to NZ servers, further overloading the International capacity. In hindsight, we should have fed the US server via an alternate route to ensure the quality of its streams. In terms of traffic, the average bandwidth being consumed was Auckland (2 servers) = 110 Mbps Wellington (1 server) = 50 Mbps USA (1 server) = 50 Mbps Total average bandwidth = 210 Mbps Peaks were of course much higher. Estimates are that approximately 450Gbytes of data was transferred during the event of 6 hours. 98% of this data was carried by the anycast routing architecture. At 10 cents per megabyte this data represents approximately $45,000. CityLink delivered this event for free as a public service. Lessons Learned Our experience suggests that for large events, anycast routing delivers high performance. However, the source feed to the US servers needs to be isolated from any other traffic into or out of NZ. We could have done this using our satellite capacity or by strictly enforcing anycast routing. This would have meant that NZ ISPs not peering at NZ Internet exchanges would have to bring significant traffic into NZ on their International circuits.

1 0

Re: [nznog] New phish - Westpac
by Nic Wise 20 Sep '05

20 Sep '05

> BNZ tried using certs in 2000 for IB for public - was a > nightmare - far too early for browser compatibility usual > portability of certs etc. Ah, I might have had my banks mixed up. > And of course, and this will come > as a surprise to some, certs aren't very good for > authentication remember - their power in is in persistently > marking transactions/data or whatever That BNZ system was > tried to get round key loggers but as you say anything that > needs specific machine setups/configs will fail for retail > banking. And there are screen grabbers now anyway. Oh, I found that even without the threat of phishers etc, the pain of using it (Even after I installed Java) was just too high. > 2-factor also does not solve the problem and can introduce > more. Netcode relies on a now-defunct, unsupported product > from RSA - it was dropped from the RSA product line due to > the issues with SMS delivery and security - ask yourself how > secure the SMS network is, would you know, do you know ? I Well, personally, I'd find it more secure that not having it at all. Without something like it, anyone can get in with my username + pwd. With it, atleast if they ALSO intercept my cell transmission, they can get it for what, 10 mins (assuming they have my UN+PW as well). That's a fairly small window, and better than the current situation. > would be more concerned about that than anything. Also, the > banks cannot control SMS delivery nor guarantee anything and > therefore don't like it. 2 factor is relatively complex to > manage in big deployments, expensive (relatively compared to > a password) and probably overkill for retail but spot on for > business - which of course you'll know has been used in for a > number of years now by most banks.... I think ASB got around that by having something in there saying "if you don't get the text within X mins, call us on 0800 WHATEVER, quote ID 123456 and we'll check your details like we normally do". > Remember though - you can use a computer - most people who > use retail Internet Banking can't - IB is the pinnacle of > their PC knowledge VERY good point. Smartcards + reader look interesting, but there again - hardware compatability. Does it works on a Mac? Does it work on my mothers old P166 without USB? Etc. > And anyway banks don;t make any money from retail banking so > until phishing and e-banking scams become sufficiently common > they still pale in comparison to manual frauds. The real > answer is to remove some functionality but of course we'd all > moan...Free beers for life for the person that cracks the > portability vs security conundrum ! Very true. As long as they keep refunding people when they get all their money nicked, it's not THAT huge a long-term problem. Short term, and for the person who's cash is (for a while) gone, it's a bit of a stresser. :) Good discussion to have, me thinks, especially given the types of people on this list. :) Now, lunch and Beer :) Is it Friday yet? N

1 0

Re: [nznog] New phish - Westpac
by Nic Wise 20 Sep '05

20 Sep '05

> I'm not a application Security expert, but why can the banks > issue a authentication Certificate, and only allow > connections to those who are authenticated? > Certs would help, but they are a PITA to get working reliably. I know of one place that does use them (www.vir.co.nz - only for dealers) - but Banks are very much mass-market, and mom-and-pop would have a lot of troulbe working it out. I think one of the banks (ANZ??) tried it a while back. Not sure what they use now tho. The worst I have used was BNZ - they had a Java applet, and you had to CLICK on your password, on a keyboard on the screen. Wow, how secure, if someone is shoulder surfing, or capturing mouse clicks. And, it was just crap to use, especially if you didn't have Java (you just couldn't get in without Java!) 2-factor authentication is one of the few ways they could tighten up on security. ASB already does this, to some extent, with NetCode (ditto BankDirect - same company tho). They send you a text to confirm (you have to enter the code in the text) if the amount is over a specific value ($2500 per day). Works great. Why not do it on ALL transactions under a certain value (eg, $50)? Want to log in and check accounts? Fine. Usename + password. Want to move money? You then MUST use 2-factor authentication. I'd say that 99% of people with computers, also have cellphones, so text messages is a good way. Going overseas? Get one of those fancy SecureID cards on loan. I'm SURE that a load of people on this list know those cards - credit card sized "random" number generators on their keyrings. Same idea could be implemented for LESS cost than the banks usually loose.... Of course, the banks have to be motivated to do it.... And they are not, really, at the moment. It might still give the phishermen entry, but only within a VERY small window (60 seconds to 5 mins, usually), which would solve most of the problems. Of course, you'd need to sync it up with the Beer Tap at the pub somehow..... Maybe give the "keys" away free with every pint sold? Righto. Back to work :) Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

4 4

Re: [nznog] New phish - Westpac
by David Robb 20 Sep '05

20 Sep '05

On Mon, 19 Sep 2005, Jeremy Strachan wrote: > > Given the alternative is our users bank accounts being cleaned out - I'm > all for Telco and/or ISP's blocking access to the site. So you say it's ok for bank phishing. What about ebay/trademe/other auction/sales sites? What if it were for Live Journal? --David

15 20

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

19 Sep '05

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

1 0

Price list from kevin
by Kevn Wong 18 Sep '05

18 Sep '05

Dear sir, How is your weekend? I'm kevin from Pcarcher data Technology Ltd. We are a manufacturer and Exporter from china, we make and sell the VGA Card and networking products. We have our own factory, the factory are with 4 STM product line, and all products go out the door of factory after double QA and QC, so we can deliever the goods to our client within 4 working day after we get client's payment, and we can supply 13 months warranty to our client, hope that we can do the business with you, I believe we will become your good supplier, and supply the best products and service to you. Enclosed is our price list of these products, please check it, hope that you can find some you products which you like, looking forward to hearing from you again, anyways thanks for your support. My msn is w_qifan(a)hotmail.com. Cisco 1721 US$300.00/Pcs WS-C2950-24 US$310.00/Pcs WS-C2950T-24 US$450.00/Pcs 2610XM US$700.00/Pcs 2620XM US$710.00/Pcs 2621XM US$710.00.Pcs BTW now we have the DI-524 and DI-624 in stock, they are original products, and our offer are follows, please check it. DI-524 US$29.0/Pcs 54Mbps http://www.dlink.com/products/?pid=316 DI-624 US$40.5/Pcs 108Mbps http://www.dlink.com/products/?pid=6 Have a nice day Best Regards Kevin Pcarcher Data Tehcnology Ltd Room 2106, BaoAn Plaza, ShenNan Road,Shen Zhen City,China Tel: +86 755 82818860 Fax: +86 755 82818640

2 1

Re: [nznog] New phish - Westpac
by Simon Allard 18 Sep '05

18 Sep '05

> > Phising is no different to putting a skimmer and camera onto an ATM > machine and stealing the card details and pin numbers. Infact, how many of you check for skimmers and cameras before putting your card into an ATM or make sure the clerk behind the desk doesn't skim your credit card before giving it back? I would say not many people would. How is that any different from an average internet person and a phising website?

1 0

Re: [nznog] New phish - Westpac
by Simon Allard 18 Sep '05

18 Sep '05

> > You will need to come into the branch and do it there. > > > > If you do follow links and get stung then we'll treat it along the same > lines > > as "so you met this guy in a pub and he said 'can I borrow your ATM card > and > > pin number for ten minutes'.....". You can't compare a Phising site to that. The user doesn't know they are entering details into a trojaned website. Phising is no different to putting a skimmer and camera onto an ATM machine and stealing the card details and pin numbers.

1 0

Re: [nznog] New phish - Westpac
by Joel Van Velden 18 Sep '05

18 Sep '05

> >> >> Wait until the phishers catchup with the normal spammers and make the > IP >> of their websites move every 10 minutes. Personally I'm surprised it >> hasn't happened already, certainly it will happen if people get > efficient >> at blocking single IPs. > > That's why it's better done at the ISP level. > > If they have web caches which transparently proxy everything. (dunno how > many isp's still do this). But the URL itself can be blocked rather than > the IP. > > Carriers shouldn't block IP's IMHO. Can't ISP's just intercept http traffic destined for phishers' sites (based on url matching, not ip) and display a nice html message to the user how their bank account would have been cleaned out if it hadn't been for their nice friendly isp? :) Certainly blatantly blocking ip's at carrier level is rather nasty. what happens if that IP is a large virtual host server? Replacing content (as above) at least allows you to make it obvious to all users whats happening. -Joel > > Simon Allard > ihug Limited > > P +64 9 962 9827 > M +64 21 456 412 > E simon.allard(a)staff.ihug.co.nz > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

2 1

Re: [nznog] New phish - Westpac
by Simon Allard 18 Sep '05

18 Sep '05

> I don't buy this line of reasoning any more. Don't open attachments > from people you don't know. Don't open attachments from people you do > know. Don't open attachments that have innocent looking icons like a > text file. Don't preview emails that have attachments. Now we're in an > arms race where trying to send any email attachments around the internet > is a sure fire way of getting someone to blackhole your entire email for > "malicious content"[1]. Even experienced users running around with all > the latest antivirus and ad zappers and everything can *still* > occasionally get infected with spyware.[2] How do you expect users to > keep up? I agree with this comment. If user education worked, ISP's wouldn't be hit with high call volumes when the big viruses hits. ISP's wouldn't need to have big virus/spam servers in front of their mail farms. Too many stupid users, and when those stupid users become educated, there are new stupid users who take their place. It's a never ending cycle. Every time a user rings the helpdesk, it hits the ISP's bottom line, hence why a lot of ISP's are in favour of blocking phising/virus ports etc. But I don't understand why carriers block stuff. Simon Allard ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] New phish - Westpac
by Gordon Smith 18 Sep '05

18 Sep '05

It's a typical spammer setup that's using zombies to provide DNS. Makes it more difficult to shut them down. The web server is located in India. We've already notified them of the compromised host, and also asked joker.com to pull the domains. Both this domain, and the domains that the nameservers respond to, are bogus. I'm not going to hold my breath waiting for joker to act though :-) Cheers, Gordon

5 5

Re: [nznog] New phish - Westpac
by Gavin Legge 18 Sep '05

18 Sep '05

<start drivvel> well well we have come full circle.. So who's going to gauge what will and wont get through ay. I'm all for letting people choose themselves. If they don't like what they see - they can unplug. It's a big scary world out there ay... It's like the isp's/transport providers are the highways. If people wanna walk out in front of a car on your highway (even though it's obviously a big truck that's gonna run them down badly disguised as a phishing scam.. - well - they have been warned. They had to learn to walk in real life- maybe they should learn to 'walk' in 'our virtual world' ie fall over some of the pitfalls - just like we all have done at some time.. You cant protect everyone all the time. So many standards of wrong and right and possibly no right answer. </end drivvel> This is the bit where I go quiet again - after all I don't even work for an ISP any more! Shudder... -----Original Message----- From: David Robb [mailto:ender(a)paradise.gen.nz] Sent: Monday, 19 September 2005 4:28 p.m. To: Russell Sharpe Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] New phish - Westpac On Mon, 19 Sep 2005, Russell Sharpe wrote: > I guess from a morality point of view... > Is it in an ISP's best interest to protect its customers interests? If you want to involve morality... many people don't like pornography. There's lots of it out there. Should we block it? --David _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

Re: [nznog] New phish - Westpac
by neil gardner 18 Sep '05

18 Sep '05

>>>> Andy Linton <asjl(a)citylink.co.nz> 19/09/2005 4:15 p.m. >>> >> So you say it's ok for bank phishing. What about ebay/trademe/other >> auction/sales sites? > >Perhaps the correct response is some (more) user education and then allow >evolution to take over - those people who are too stupid to work this out lose >all their money and then they can't use the Internet any more. While ISPs will >lose revenue from them they're probably the ones who cause 90% of the help >desk calls and so profitability goes up and we all get more time for beer. On a more general level it's a simple economic problem and we shouldn't be expending that much energy into finding a technical solution. The current level of bank fraud is _obviously_ acceptable to the banking institutions (1)... When it becomes unacceptable then we'll see more secure (yes, less convenient) methods of conducting e-banking. We'll probably also see the banks seriously publicise the issues and most importantly, we'll see the banks start shying away from accepting financial responsibility for these phished transactions - currently they wear most of the losses. Regards Neil Gardner (1) They are obviously acceptable because we haven't seen the banks go ballistic to close this down from their end - don't think they don't know how, or can't afford it... It's just more trouble than it's currently worth. If we keep trying to solve the problem from a technical perspective, the attacks just get better, and the banks get to sit (relatively) idly by and not have to solve the root problems. Neil Gardner Product Manager - Product Line Management Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) 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] New phish - Westpac
by Simon Allard 18 Sep '05

18 Sep '05

> > Wait until the phishers catchup with the normal spammers and make the IP > of their websites move every 10 minutes. Personally I'm surprised it > hasn't happened already, certainly it will happen if people get efficient > at blocking single IPs. That's why it's better done at the ISP level. If they have web caches which transparently proxy everything. (dunno how many isp's still do this). But the URL itself can be blocked rather than the IP. Carriers shouldn't block IP's IMHO. Simon Allard ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz

1 0

Re: [nznog] New phish - Westpac
by Simon Allard 18 Sep '05

18 Sep '05

> > > traceroute secwestpac.com > traceroute to secwestpac.com (210.212.134.2), 64 hops max, 44 byte packets > 1 drew.router.bw (10.4.6.254) 0.709 ms 0.474 ms 0.533 ms > 2 dsl.bw (10.10.69.254) 1.703 ms 1.554 ms 1.505 ms > 3 219-88-160-1.jetstream.xtra.co.nz (219.88.160.1) 139.575 ms 73.358 > ms 143.285 ms > 4 203.96.122.59 (203.96.122.59) 77.224 ms 184.149 ms 105.514 ms > 5 fid-int.tkbr4.global-gateway.net.nz (202.50.245.198) 60.790 ms > 65.843 ms 59.394 ms > 6 vlan-283.tkbr4.global-gateway.net.nz (202.50.245.197) 59.068 ms > 58.437 ms 59.557 ms > 7 210.55.202.65 (210.55.202.65) 59.215 ms !H * 59.743 ms We have also killed the routes to the sites on our borders. Simon Allard - CCNA Senior Systems Programmer ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz

1 0

Sponsorship - packages or tiers?
by Lin Nah 18 Sep '05

18 Sep '05

I do admit that I don't know much about this and some of my conclusions are based on observations of what other conferences / events have done. So feel free to shoot parts or any of this down if need be. Tiers of sponsors: The reason why I say we are too small to have tiers of sponsors is because essentially the number of sponsors we can have in a small event such as this is small. To me tiers of sponsor implies the sort you see at the ballet etc where it says if you pay a certain amount you are listed as a sponsor at that level. This however doesn't specify what they are sponsoring. ie we'd be out there each of us asking ppl to sponsor $x for Tier1 and sponsor y for tier 2. With those sorts of sponsorships (form what I have seen) there is a list of perks they get with it. eg tier 1 = 3delegates, logo on bag and shirt, etc. Tier 2 = 2 delegates and logo on notepad To have this we'd have to have ability to work towards obtaining enough sponsors, and figure out what to do if we don't get enough. I know that's like normal sponsorship. Howver it is a bigger risk if some or many of our potential big sponsors decide to go for a lower tier. So instead of tiers, we have a shopping list of stuff we want and find sponsors for a combination of them. The reason why we would package them is because some stuff is more "sexy" and so more easy to find a sponsor. The idea with the package is to ensure at the end of the day we aren't left with a list of the stuff that is hard to find a sponsor for and yet is important for the conference. It is also harder perhaps to find sponsors for an overseas speaker as the $ amounts are higher For example it won't be hard to sell the idea of sponsoring a bar tab but you may find it harder to get someone to sponsor stuff like the AV gear (mics, laser pointers etc). It will be like tiers of sponsors in the fact they are sponsoring $x means we give them certain benefits. With each item in the shopping list we should perhaps add a certain markup to cover costs of some of the other non sponsorable stuff. or make sure they sponsor more than one thing. eg speaker + AV hire. Bandwidth + bags The thing with the big ticket items is we should try to give them something in return. Something that their management can understand as a return. Some of those speakers can speak on more than one topic. So we could perhaps ask them to also do a public lecture (perhaps at a uni campus somewhere) and an interview with idg or herald technology. Thus the sponsor has a bigger exposure for that amount given. List of items that are sponsorable Overseas Speaker(s) - Travel & Accommodation Local Speaker(s) - Travel & Accommodation Venue costs (room hire) Main Dinner Bar Tab Bag (generic term - could be backpack/satchel/folder etc) Lunch Bandwidth Networking (wireless hubs) Streaming AV Gear (mics, data projectors, laser pointers) Coke Fridge. Fridge hire & filling it with drinks (we perhaps get stickers for each can with the sponsor's logo? or just a poster on the fridge door, say size of door with sponsor's logo) First night dinner (usually not part of nznog) Costs So far all I have is what has been posted to this list I have no idea what other sutff cost in the past but things like t-shirt and bag, I could easily ring round for quotesi f need be. Bandwidth: 2005: The conference network carried just over 32GB of traffic, including the video streaming, but not traffic to www.nznog.org. Coke: 2005: 495 cans of soft drink (incl 275 coke and 100 diet coke), 2004: 420 cans soft drink (there was fridge filled with coke, diet coke, sprite, fanta, and other soft drinks. No V or red bull) Tea, Coffee, OJ, Biscuits 2005: over 60L of juice and nearly 4kg of ground coffee. 2004: 80 ltrs OJ (morning tea/coffee and lunch) Food bill: 2004: $5800 (I am not sure what that included. Tony - did this include dinner or just lunch, morning tea&coffee) Bar Tab 2005: $1500 ($1000 by 2day and $500 by WAND) 2004: $1000 2002: $1000 Anyway I am sure there are ppl in here who are more experienced than I about these sorts of things. Do we want tiers of sponsors as in look for people to contribute certain sums of money? eg $10000, $5000, $1000. OR do we want sponsors to sponsor specific items. ie all stuff we need is listed as sponsorable items? regards lin

1 1

Subject: Changes to registration of .govt.nz domains
by keith.mclean＠ssc.govt.nz 18 Sep '05

18 Sep '05

Hello NZNOG, As part of the moderation of the .govt.nz domain, the State Services Commission (SSC) has become a .nz registrar. On October 3rd any new .govt.nz domains will need to be created through the SSC registrar at <http://www.dns.govt.nz/>. Over the next few months, the existing .govt.nz domains will be transferred to the new registrar. We will make contact with existing registrars and registrants of .govt.nz names before any transfer occurs. No delegation will change during the transfer. If you are providing name-service for a .govt.nz name this should continue, as should any billing for this service. The SSC Registrar will not complete with other .nz registrars in non-government namespaces. Further details are available on the website at <http://www.dns.govt.nz/terms_and_conditions.php> If you have any concerns about the upcoming transfers, please contact transfers(a)dns.govt.nz or call 0508 GOVTNZ (468869) Unfortunately moderation rules prohibit the registration of beer.govt.nz, but consumption is acceptable. Regards Keith McLean Keith McLean, State Services Commission. DDI (04) 495 2861.Mobile (027) 6096779 Caution: If you have received this message in error please notify the sender immediately and then delete this message.

1 0

linux.jetstreamgames.co.nz
by Matthew Poole 18 Sep '05

18 Sep '05

Does anyone on here know the status of this server? Is it down for good, or just for protracted maintenance? Thanks -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

New phish - Westpac
by Alastair Johnson 18 Sep '05

18 Sep '05

Morning If anyone from Westpac Security monitors NZNOG, and for those that want to update their mail rulesets appropriately, there appears to be a new phish this morning for Westpac. I've received 6 in the last 10 minutes. All originate from 219.128.152.213, a Chinanet host or 82.229.209.178. The body refers people to http://secwestpac.com/IOLB/newSession . The hostname is similar to their correct "sec.westpac.co.nz". The domain hasn't yet been pushed into WHOIS, but is in the GTLD servers. The body of the message is HTML, with Westpac graphics. The text is: Processing error We were unable to process your recent transactions on your account. To ensure that your account is not suspended, please update your information Headers below. aj From - Mon Sep 19 10:28:31 2005 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <update(a)westpac.co.nz> X-Original-To: aj(a)sonic.sneep.net Delivered-To: aj(a)sonic.sneep.net Received: by sonic.sneep.net (Postfix, from userid 668) id 8E13A21CFB; Mon, 19 Sep 2005 10:19:50 +1200 (NZST) Received: from smtp01.maxnet.net.nz (smtp01.maxnet.net.nz [202.89.32.6]) by sonic.sneep.net (Postfix) with ESMTP id B9D3E21CEE for <aj(a)sneep.net>; Mon, 19 Sep 2005 10:19:39 +1200 (NZST) Received: from mailfilter01.maxnet.net.nz (mailfilter01.maxnet.net.nz [202.89.32.8]) by smtp01.maxnet.net.nz (Postfix) with ESMTP id 323D2406A2E for <aj(a)sneep.net>; Mon, 19 Sep 2005 10:21:14 +1200 (NZST) Received: from stolichnaya.maxnet.net.nz (stolichnaya.maxnet.net.nz [209.123.221.169]) by mailfilter01.maxnet.net.nz (Postfix) with ESMTP id CF02384E40 for <aj(a)win.co.nz>; Mon, 19 Sep 2005 10:21:55 +1200 (NZST) Received: from -1211395320 (cha92-7-82-229-209-178.fbx.proxad.net [82.229.209.178]) by stolichnaya.maxnet.net.nz (Postfix) with SMTP id DA3B65325E0 for <aj(a)win.co.nz>; Mon, 19 Sep 2005 10:19:37 +1200 (NZST) Received: from westpac.co.nz (142870456 [137878400]) by cha92-7-82-229-209-178.fbx.proxad.net (Qmailv1) with ESMTP id A18855DD6F for <aj(a)win.co.nz>; Sun, 18 Sep 2005 14:46:52 -0700 Date: Sun, 18 Sep 2005 14:46:52 -0700 From: Update <update(a)westpac.co.nz> X-Mailer: The Bat! (v2.00.6) Personal X-Priority: 3 Message-ID: <4793089069.20050918144652(a)westpac.co.nz> To: Aj <aj(a)win.co.nz> Subject: Anti-fraud notification MIME-Version: 1.0 Content-Type: multipart/related; boundary="----------572BB2C4F688976"

2 1

Inaugural Cisco User Group Meeting
by Philip D'Ath 16 Sep '05

16 Sep '05

I'm establishing a Cisco User Group in Auckland. The inaugural meeting is taking place Wednesday 12th October. Further details can be found at: http://www.nzcug.org.nz/ I could really do with a mailing list. Any volunteers to host this? Off course, offlist replies.

1 0

[removal of service on OLD ip address for "B"]
by bmanning＠vacation.karoshi.com 15 Sep '05

15 Sep '05

good afternoon, back on 14 january 2004, we provided notification that the "B" root server address was being renumbered. this renumbering occured 28 january 2004. we have continued to run root service on the old address since then to ease transition for those who might have needed more time to make the change. please ensure that you have a current "root.hints" or "cache.db" file. The Current version may be downloaded from: http://www.internic.net/zones/named.root we have requested and received permission to terminate root service on the old IP address for the "B" root server and plan to do so on 01 january 2006. if there are concerns or questions, please let us know. --bill manning for <hostmaster(a)b.root-servers.net>

1 0

Global Gateway issue today
by Barry Murphy 15 Sep '05

15 Sep '05

Hi, I was aware of an issue on orcons Global-gateway issue today where both national and international was basically unusable for about 3 hours. I'm trying to find out if anyone else was effected as my flat mate who who manages a banks network (which I prefer not to mention) but they were told for 3 hours that the problem was within their network. I'm aware of 1 other company that connects direct to global-gateway that was effected. Please reply off list and if people are interested I'll send a summary. Thanks Barry

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Sep '05

13 Sep '05

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Sep '05

13 Sep '05

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

1 0

NZNOG 06 update
by Simon Lyall 12 Sep '05

12 Sep '05

Just a quick update, it has been 3 weeks since the call for papers. 1. Wednesday SIG Day So far we have not had any interest/offers/plans for the Wednesday which we've previously given over to streamed sessions. If you wish to do something that day please contact us fairly soon. Possibly we might end up having the conference over all 3 days (or perhaps streaming the Wednesday morning only). 2. Sponsorship. We are currently preparing a list of sponsorship options for perspective sponsors. If you are interested in sponsoring NZNOG 2006 ( via Money, Speakers, Goods, Money, Services or Money ) then please contact sponsorship(a)nznog.org. 3. Talks We have had several good talk proposals already and are in process or arranging others. Please make sure you submit proposals before the deadline to have a good chance of getting in. Don't forget you can do a lightning talk if you don't want to do a full one. Or you can do like WAND did this year and split a 1 hour talk slot across several talks by members of your team. Or something else perhaps. Email talks(a)nznog.org . 4. Website We have a initial website up ( http://www.nznog.org ) with some information on 2006 (Thanks Mark) . This site will be expanded/replaced in a few weeks/months but it is there to give the 2006 conference an initial presence. 5. Feedback/Questions. Email any feedback or questions to info(a)nznog.org , or email me directly if you're shy. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Upcoming Live Webcasts
by Richard Naylor 12 Sep '05

12 Sep '05

14 September - Maori Language Week Awards - http://www.r2.co.nz/20050914 25 September - World Mountain Running Championships - http://www.r2.co.nz/20050925 A few challenges with getting connectivity, but otherwise nothing too major happening.

1 0

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

12 Sep '05

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

1 0

Fast UpLink ( OT)
by bigalownz 10 Sep '05

10 Sep '05

Due to my normal ihug bliink only being 128k up I'm looking for a ISP etc that can help me with a fast up link so I can send data (5GB) to San Diego - California one time a week for the next year I worked it out if would take me 60 - 70 hours to send it on my ihug bliink Thanks

7 6

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

08 Sep '05

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

1 0

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

08 Sep '05

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

1 0

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

08 Sep '05

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

1 0

Live Audio Streams
by Webmaster 06 Sep '05

06 Sep '05

Radio NZ has commenced a public test of our live streams from our current web site. This is being done so that we can fine tune the system prior to the launch of the new web site. Here is a list of what is available: Service Max. Data Rate Mode National Radio 48 kbs Stereo Concert FM 64 kbs Stereo RNZ International 48 kbs Mono www.radionz.co.nz/audio/ We have also posted on demand audio of the Radio NZ Election debates. There has been considerable interest in the programmes posted to date. www.radionz.co.nz/election2005/ regards, Richard Hulse

3 2

128k beer?
by Blair Harrison 05 Sep '05

05 Sep '05

Slow day.. Gotta be on topic, surely.. It's a mock Tui Ad :) http://jedi.net.nz/128kbroadband.jpg Cheers, Blair

1 0

ISPs offering transit service via the APE
by Andy Linton 04 Sep '05

04 Sep '05

A good number of ISPs use the APE for transit between each other either by using the APE route servers to exchange routes on a multilateral basis and/or direct bilateral arrangements. A smaller number offer transit services directly to customers using our fabric in Auckland. In Wellington, we have a list of those who offer services (ahttp://www.citylink.co.nz/community/isps.html) and I'd like to build a similar one for Auckland. Contact me off list if you want to be included. I'll owe a beer to the first person to respond. (:-)

1 0

Jetstreamgames FreeBSD distfiles
by Barry Murphy 04 Sep '05

04 Sep '05

Hey there, I can't recall who looks after jetstreamgames, but I recall the person being on this list. It would seem since the weekend that the distfiles have disappeared for FreeBSD, any chance of these re-appearing? ftp://linux.jetstreamgames.co.nz/dist/freebsd/ports/distfiles/ Thanks Barry

2 1

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

04 Sep '05

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

1 0

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

04 Sep '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS7696 as-name: NZRR-AS7696 descr: OneSquared descr: WIX peering at '202.7.0.137' descr: see Citylink RT job #3156 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS7696 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: aut-num: AS7696 as-name: NZRR-AS7696 descr: OneSquared descr: WIX peering at '202.7.0.137' descr: see Citylink RT job #3156 descr: APE peering at '192.203.154.25' descr: see Citylink RT job #3088 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS7696 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS7696 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS7696 descr: Route set advertised to AS9560 by OneSquared - AS7696 members: 202.160.112.0/21^21-29, 203.163.98.32/28^28-29, 203.163.98.48/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR

1 0

OT - Smart Start 5.50
by Geraint Jones 04 Sep '05

04 Sep '05

would anyone happen to have the SmartStart 5.5 ISO (available off HP.com) and be willing to put it on a WIX/APE connected server for me ? *let the arse kicking begin* GJ 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 04 Sep '05

04 Sep '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS7696 as-name: NZRR-AS7696 descr: OneSquared descr: WIX peering at '202.7.0.137' descr: see Citylink RT job #3156 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS7696 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS7696 descr: Route set advertised to AS9439 by OneSquared - AS7696 members: 202.160.112.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR

1 0

Fast UpLink ( OT)
by bigalownz 04 Sep '05

04 Sep '05

Thanks for the help but I forgot to say I'm based in Wellington (Porirua Area) and my price range is $100 - $200 a month and sending a DVD by post to the USA is not an option as I have to upload data to a number of web sites

2 1

kaimai/mamaku
by Steve Wright 01 Sep '05

01 Sep '05

Greetings I need power and possibly minimal shelter (tower space even?) on the Kaimai/Mamaku Ranges near or about the metereological installation (above swaps quarry). Any and all suggestions welcomed off-list please. Steve

1 0

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

31 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050830 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050901 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050830 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050901 source: NZRR

1 0

Fwd: Important Event - ICT Leaders Debate, this Thursday evening
by Richard Naylor 30 Aug '05

30 Aug '05

In case some of you don't get this. >From: "Colin Jackson" <president(a)internetnz.net.nz> >To: "INZ Members Announce" <members-announce(a)internetnz.net.nz> >Date: Tue, 30 Aug 2005 14:54:33 +1200 > >InternetNZ ICT Leaders Election Forum 2005 > >This Thursday evening InternetNZ is convening an Election Forum, for >political parties to present and defend their policies relating to >information and communications technology policy. > >David Cunliffe MP (Labour Party), Maurice Williamson MP (National Party) >and Mikaere Curtis (Green Party) will face questions from a panel of >journalists (Paul Brislen, IDG / Computerworld; and Kate McLaughlin, >National Business Review) on where they see the future of this industry, >where they want to take it, and why. > >Date: Thursday 1 September 2005 > >Time: 7.00pm - 9.00pm > >Physical Venues: University of Auckland - Access Grid Suite (Main Venue) >and Wellington - Media Lab Conference Room, L2, 205-207 Victoria St. > >Webcast/Chatlink : Link page will be available at 6pm this afternoon at >www.internetnz.net.nz/forum, with links to actual webcast and chat posted >on Thursday. > >Moderated by barrister Peter Dengate Thrush, the debate will commence with >an hour-long session where the speakers respond to pre-prepared questions >covering the wide range of issues relating to ICT and telecommunications >policy. > >In the second hour with the politicians will take questions from the >audience, channelled through the journalist panel, and live questions from >the Wellington audience. Online participants will be able to participate >in the debate through submitting questions via a web based chat channel. > >Communications between Auckland and Wellington will be by means of an >Access Grid. The Access Grid technology provides realtime audio and video >links between the two sites, making it an effective way to let audiences >in different geographic locations interact in real time. > >The only attendees in the Auckland venue will be the Moderator, the >journalists, and of course, the politicians. Outside the room will be the >technical providers, the feedback co-ordinators and the politicians >advisory teams. There will not be any general audience at this venue. > >There is a limited amount of space in the physical venue in Wellington for >InternetNZ members to attend the event. Obviously we want to have a >capacity audience at the venue. If you would like to attend, please advise >office(a)Internetnz.net.nz as soon as possible. Physical attendance will be >allocated on a first-come, first-served basis. For members outside of >Wellington, we would value your on-line attendance and questions. > >This InternetNZ Election Forum provides a unique opportunity for you to >put questions to the politicians who will be making critical decisions >about the future regulatory environment for communications and information >technology in New Zealand. We welcome your involvement. We feel that this >"proof of concept" of the technologies may lead to a whole new method of >engagement in political discussions for special interest groups wishing to >engage in detailed debates in specialised areas of policy. Please help us >make this event a success. > >Colin Jackson >President - InternetNZ

6 7

Notification of NZRR Database changes
by NZRR Database Notifications 29 Aug '05

29 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050526 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050830 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 29 Aug '05

29 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050526 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050830 source: NZRR

1 0

HEADSUP - Upcoming Webcast
by Richard Naylor 28 Aug '05

28 Aug '05

Upcoming Webcast on www.R2.co.nz This is a premature warning of what could be a webcast of interest to Network Operators. The organiser will hopefully announce it very soon (was due out by now <sigh>). The event is 7pm to 9pm on Thursday 1 September 2005 and will be carried by R2 using anycast routing. This means that ISPs not peering at APE, WIX or PNIX will receive the traffic from our US server. If you require assistance with peering, please contact Andy Linton at CityLink. The event will be webcast in video at our usual bit rates of 56kbps, 128kbps and 384kbps, and audio at 28kbps and 56kbps. There will be a separate stream at 2Mbps, for those who would like to experience near standard definition video. A recent webcast had 25% of viewers watching the 2Mbps stream, so ISPs may experience an increase of traffic. (that was out of 100 viewers) Help Desks should also be advised that this event is happening, as there may be an increase of requests for assistance. This will be an interactive webcast, as will become apparent, when it finally gets properly announced. As well as links to client mediaplayers, the event will use a custom web page with embedded player and the interactive stuff. Thanks for your co-operation. Rich (wearing my R2 hat)

1 0

Trade Me phishing scam??
by Paul Adshead 26 Aug '05

26 Aug '05

Has anyone else seen any other phishing attempts on Trade Me before? Are there many of these coming through at the moment?? Cheers, Paul. ---------- *From:* mailer(a)trademe.co.nz[SMTP:MAILER(a)TRADEME.CO.NZ] *Sent:* Friday, August 26, 2005 11:24:06 AM *To:* Help Desk *Subject:* Your Trade Me Bid was Cancelled !!! *Auto forwarded by a Rule* ** ** * Dear Customer,* ** *The bid that has been entered in error was cancelled, **Click Here *<http://004c256.netsolhost.com/> * to view the reason provided for the cancellation.* ** *Happy Trading! Trade Me Customer Support Team **http://www.trademe.co.nz* <http://www.trademe.co.nz/>

11 16

Trademe phishing
by Jeremy Brake 25 Aug '05

25 Aug '05

5 4

Re: [nznog] Colo in wellington/AKL
by Joshua Brady 25 Aug '05

25 Aug '05

To quickly answer all the replies I have gotten about summarizing the replies. I'll post general colo costs in the same fashion paul vixie has done his personal colo registry on www.vix.com I will say right off the top, my requirements are much much more than those of someone who is colocating 1 - 2 servers. Also, I need a contact number for iconz, as the 0800 freefone doesn't work internationally, reply off list would be great. And just to stay on topic . beer

2 2

RE: [nznog] Trade Me phishing scam??
by James Butler 25 Aug '05

25 Aug '05

Ok, Originating IP: 66.206.6.48.. Must remember to check what I'm mailing :P James Butler

1 0

Colo in wellington/AKL
by Joshua Brady 24 Aug '05

24 Aug '05

This is probably extremely off topic, but if people could shoot me back a list of colo providers (Carrier neutral prefered) with a general run down on the service, rankings and all. Auckland could do the same. In repayment to the list, the next round is on me. I am flying into Auckland and driving to Wellington in October. -Josh

1 0

RE: [nznog] Ihug UBS to Global Gateway trip to Australia?
by Gordon Smith 24 Aug '05

24 Aug '05

> > Is > > this a side effect of the Depeering/Peering policies of Telecom? > > Yup, we used to peer with GG, Xtra over APE but yea you know > the rest of the story. > > > Simon Allard > ihug Limited > Don't Ihug peer with Orcon at the APE anyway? Looking at it from our side, it would appear to be an Ihug internal routing issue. Currently, a trace to ihug from a UBS test circuit shows a route loop between 203.109.156.140,148,147,155 Too much beer maybe?? :-)

1 0

RE: [nznog] Ihug UBS to Global Gateway trip to Australia?
by Simon Allard 23 Aug '05

23 Aug '05

That's very odd and no, not normal AFAIK. We don't buy domestic transit from Global Gateway (don't want to pay Telecom anymore money than we have to), but we do buy domestic transit from TelstraClear. GG should be preferring/learning ihug routes from TelstraClear. I will try and sort it out for you. Hopefully it's a mistake and not some new unknown GG policy. > Is > this a side effect of the Depeering/Peering policies of Telecom? Yup, we used to peer with GG, Xtra over APE but yea you know the rest of the story. Simon Allard ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz > -----Original Message----- > From: Jon Dean [mailto:jon.dean(a)simplicity.net.nz] > Sent: Wednesday, 24 August 2005 5:44 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Ihug UBS to Global Gateway trip to Australia? > > Hi all. > > For the last few weeks, at least three Ihug 256K UBS accounts in > Invercargill > have been suffering from the following problem. Their round trip times to > Global Gateway customers (ie. DSL customers) and been running at around > 350ms. Traceroutes indicate that data is traversing via australia (which > might account for the latency - but even that still seems to high). > > A response from Ihug Business indicated that this was normal and advised > that > they would talk to Telstra. > > Now these Ihug customers do not have any relationship with either Telstra > or > Telecom - and I accept that this could be some screwed up config with > either > party. However, I can't accept this is normal. Talking to your neighbour > via > DSL shouldn't go via Australia or at least shouldn't take 350ms. > > All other traffic goes correctly (ie. Ihug UBS to pop3.xtra.co.nz etc...) > it > is only GG end users that seem to be screwed up. > > My question for NZNOGers. Can anyone confirm that this is normal? Is GG > not > peering at all with Ihug UBS. Is there any beer at the end of the tunnel? > Is > this a side effect of the Depeering/Peering policies of Telecom? > > This is Ihug UBS to Orcon (Telecom) DSL > 2 203-109-156-252.ihug.net (203.109.156.252) 93.694 ms > 3 Vl117-tig-nz-core-1.ihug.net (203.109.156.209) 88.690 ms > 4 203-109-156-138.ihug.net (203.109.156.138) 83.481 ms > 5 g1-0-1642.u12.telstraclear.net (203.98.18.161) 87.422 ms > 6 * * * > 7 210.55.202.49 (210.55.202.49) 299.341 ms > 8 car17-dom.akcr8.global-gateway.net.nz (202.50.119.154) 336.779 ms > 9 * * * > 10 port-x-x-x-x.fastadsl.net.nz (x.x.x.x) [open] 339.033 ms > > This is the reverse Orcon DSL - Ihug UBS > 2 210-55-67-32.adsl.netgate.net.nz (210.55.67.32) 56.362 ms > 3 192.168.253.1 (192.168.253.1) 62.454 ms > 4 p-c1.akbr1.global-gateway.net.nz (202.50.245.237) 73.997 ms > 5 210.55.202.97 (210.55.202.97) 103.640 ms > p1-1.tkbr3.global-gateway.net.nz (202.50.116.162) 77.407 ms > 7 210.55.202.67 (210.55.202.67) 68.395 ms > 8 ATM9-0-0-50.sn1.optus.net.au (202.139.128.97) 341.822 ms > 9 AsiaNetcom.sn1.optus.net.au (202.139.18.2) 289.700 ms > 10 po0-2.gw1.akl1.asianetcom.net (202.147.55.90) 376.026 ms > 11 ip-202-147-45-74.asianetcom.net (202.147.45.74) 337.066 ms > 12 203-109-156-140.ihug.net (203.109.156.140) 360.544 ms > 13 203-109-156-213.ihug.net (203.109.156.213) 340.953 ms > 14 203-173-161-x.bliink.ihug.co.nz (203.173.161.x) 471.486 ms > > Kind Regards, > > jon > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

OT, but a beer in it!
by Russell Sharpe 23 Aug '05

23 Aug '05

Does anyone have any experience with... Nomadix Hotspot Gateway... to be used for billing Fortigate 60... Antivirus/Firewall I have an electrician(!) who has asked me to install these + easy stuff, but I can only find sales PDF's! No diagramms or config details supplied... go figure! Please email me off line Cheers and a beer! Russell Sharpe rsharpe(a)paradise.net.nz Ph +64 4 9717665, +64 21 742 773 Fax +64 4 9717635, +64 21 342 776

1 0

Re: [nznog] Ihug UBS to Global Gateway trip to Australia?
by Webmaster 23 Aug '05

23 Aug '05

>>> Jon Dean <jon.dean(a)simplicity.net.nz> 08/24/05 5:44 PM >>> > Is there any beer at the end of the tunnel? Hops are good for beer but not for the internet.

1 0

Microsoft Opposes NZ Anti-Spam Bill/Who are these NZ Spammers..
by Craig Whitmore 23 Aug '05

23 Aug '05

See: http://www.stuff.co.nz/stuff/0,2106,3384447a28,00.html The Article Quotes: "Mr Hamlin says his understanding is that there are just three big spammers operating in New Zealand, responsible for producing about 5 per cent of the spam that arrives in New Zealanders' inboxes." The question is.. who are these NZ spammers? Where does he get this information from? Thanks Craig

8 13

Ihug UBS to Global Gateway trip to Australia?
by Jon Dean 23 Aug '05

23 Aug '05

Hi all. For the last few weeks, at least three Ihug 256K UBS accounts in Invercargill have been suffering from the following problem. Their round trip times to Global Gateway customers (ie. DSL customers) and been running at around 350ms. Traceroutes indicate that data is traversing via australia (which might account for the latency - but even that still seems to high). A response from Ihug Business indicated that this was normal and advised that they would talk to Telstra. Now these Ihug customers do not have any relationship with either Telstra or Telecom - and I accept that this could be some screwed up config with either party. However, I can't accept this is normal. Talking to your neighbour via DSL shouldn't go via Australia or at least shouldn't take 350ms. All other traffic goes correctly (ie. Ihug UBS to pop3.xtra.co.nz etc...) it is only GG end users that seem to be screwed up. My question for NZNOGers. Can anyone confirm that this is normal? Is GG not peering at all with Ihug UBS. Is there any beer at the end of the tunnel? Is this a side effect of the Depeering/Peering policies of Telecom? This is Ihug UBS to Orcon (Telecom) DSL 2 203-109-156-252.ihug.net (203.109.156.252) 93.694 ms 3 Vl117-tig-nz-core-1.ihug.net (203.109.156.209) 88.690 ms 4 203-109-156-138.ihug.net (203.109.156.138) 83.481 ms 5 g1-0-1642.u12.telstraclear.net (203.98.18.161) 87.422 ms 6 * * * 7 210.55.202.49 (210.55.202.49) 299.341 ms 8 car17-dom.akcr8.global-gateway.net.nz (202.50.119.154) 336.779 ms 9 * * * 10 port-x-x-x-x.fastadsl.net.nz (x.x.x.x) [open] 339.033 ms This is the reverse Orcon DSL - Ihug UBS 2 210-55-67-32.adsl.netgate.net.nz (210.55.67.32) 56.362 ms 3 192.168.253.1 (192.168.253.1) 62.454 ms 4 p-c1.akbr1.global-gateway.net.nz (202.50.245.237) 73.997 ms 5 210.55.202.97 (210.55.202.97) 103.640 ms p1-1.tkbr3.global-gateway.net.nz (202.50.116.162) 77.407 ms 7 210.55.202.67 (210.55.202.67) 68.395 ms 8 ATM9-0-0-50.sn1.optus.net.au (202.139.128.97) 341.822 ms 9 AsiaNetcom.sn1.optus.net.au (202.139.18.2) 289.700 ms 10 po0-2.gw1.akl1.asianetcom.net (202.147.55.90) 376.026 ms 11 ip-202-147-45-74.asianetcom.net (202.147.45.74) 337.066 ms 12 203-109-156-140.ihug.net (203.109.156.140) 360.544 ms 13 203-109-156-213.ihug.net (203.109.156.213) 340.953 ms 14 203-173-161-x.bliink.ihug.co.nz (203.173.161.x) 471.486 ms Kind Regards, jon

1 0

OT - Network stuff ...
by Tim John 23 Aug '05

23 Aug '05

Hi all, Sorry for the off topic post, but I've just been through the garage and made a list of network stuff that I brought over from the UK with me a couple of years ago. I'm about to put some/all of it on TradeMe, but wondered if anyone on this list would like first refusal. Some items include brand new analogue modems, new ISDN modems, thin client terminals etc. If anyone is interest, please contact me off list for more information. Cheers, Tim

1 0

OT - Last week end
by Richard Naylor 23 Aug '05

23 Aug '05

Sorry for being OT, but after promising everyone some webcasting action, not all of it worked. The wedding webcast on Saturday wasn't the best. Our wireless link didn't come up and after loosing time with a faulty video DA, we didn't have enough time to find out why. Theres no T3G coverage in Tawa (or the whole Tawa/Porirua valley) so there was nothing we could do. A 2 person crew can only do so much. So we shot the wedding to disk....... Thats the first time in about 5 years that we've failed to get the signal out. In comparison, Sunday in AKL, was a dream. 2 hours to set up the van and 4 cameras. Jeff and ? (forgot his name) from NZ Wireless just turned up, ran a long cable from their car to my van. Pings worked straight away - and I had 15Mbps to APE. It all ran perfectly and we uploaded a 750MB file afterwards, straight to the server. Nice and easy. So sorry that this is a shameless plug for Chris and the team at NZ Wireless, but it was a very short notice job, and they delivered the goods. It shows the power of NZNOG as a group, when you can fire off an email asking for help and get such a great response in 15 minutes. And they did a brilliant job as well. I was so pleased I had 2 beers that night (just to get on topic). To make life easier, I guess I should start using ISPs who can deliver to my van, rather than having to do that part myself as well as the production side of things (and the encoding). Next scheduled job is 7 Sept - it will be an opportunity for all Operators........more later. Rich

1 0

Cisco memory
by Nathan Ward 23 Aug '05

23 Aug '05

I'm trying to get hold of some Cisco RAM, specifically 512Mbit sticks for 7401s. The Cisco PN is MEM-7400ASR-512MB=. Does anyone know where I can find some locally? Either Cisco brand or Kingston, or maybe something else..

2 1

NZNOG 06 - Bits and pieces
by Simon Lyall 22 Aug '05

22 Aug '05

Hosts ----- The School of Mathematics, Statistics and Computer Science at Victoria University will be hosting us this year. They are in the process of getting the website ready and working out other details. Dates ----- Talk proposals are due in November to allow us to publish the schedule before people go on Xmas break so they can organise expenses and time of with their company. The idea is that the schedule will be 80+ percent ready by then. We know a few talks will be late but to ensure that the schedule is filled early a big priority will be given to those in on time. Even if you talk/abstract is not 100% flushed out by the close date please contact us by then to ensure that we pencil you in. Lightning talks --------------- Just a note that we don't expect a full abstract for lighting talks or even (possibly) a topic/title at this point. People who get in early will have a better chance however. Please feel free to discuss with talks(a)nznog.org More information on the lightning talks will be published in a few weeks. Costs ----- We anticipate that costs for 2006 will be similar to 2005. If you you are on a budget you might want to start saving now. Accommodation ------------- Since NZNOG will be held during term time accommodation costs will be higher since student halls will not be available as in previous years. We are looking at options for a large booking but feedback as to what people are after ( Backpackers, 2 star, etc ) would be appreciated. Transport --------- Please have a look at the airline sites to estimate your costs. If there are a number of people who can't afford to fly then we may try to arrange bus or car sharing. We will ask closer to the date. Sponsorship ----------- There are opportunities available for companies to sponsor various aspects of this meeting. For more information, contact sponsorship(a)nznog.org.

1 0

NZNOG 06 - Call for Participation and Papers
by Simon Lyall 22 Aug '05

22 Aug '05

NZNOG 06 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Wellington between 22-24 March 2006. Our hosts are The School of Mathematics, Statistics and Computer Science at Victoria University. The conference will take place the week before the Wellington ICANN meeting in order enable people to attend both events. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. The planned format is one day of streamed Special Interest Group ( SIG ) Meetings followed by 2 days of the conference proper. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information SIG Meetings ------------ The first day of the conference is arranged as parallel tracks to cover subject material which is of interest to particular groups of attendees. Proposals are requested for workshops, tutorials and other appropriate special-interest meetings of interest to Network Operators. Presentations ------------- NZNOG invites presentations on relevant topics. Suitable topics include, but are not limited to Network Monitoring, Peering , Network Design Philosophy, Security and Encryption, IPV6, DDOS, WAN Solutions / VPNs, BGP and other routing protocols, ENUM, Fibre Optics, Wireless, Spam, Mail Servers, Virtual Servers (eg Xen, UML, VMware). Presentations from researchers and from practitioners are welcomed. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. The survey of mailing list members was conducted in early 2005 to determine areas of interest, the results are available here: http://list.waikato.ac.nz/pipermail/nznog/2005-May/010020.html If you are interested in submitting a talk please fill out the questions at then end of this document and email them to talks(a)nznog.org . Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG'06 it is planned that there will be at least one hour long lightning talk session. Advice on giving Lightning Talks: http://www.justanotherperlhacker.org/lightning/ http://www.perl.com/pub/a/2004/07/30/lightningtalk.html http://perl.plover.com/lt/lightning-talks.html http://www.metaart.org/maca/perl/lightning/lightning_what.html Proposals for lightning talks should be submitted they same way as other talks. Dates ----- Dates (other than that of the conference itself) may be subject to change. 1 Nov: Proposals and Abstracts due Early Nov: Notification to Authors Early Nov: Schedule Published. Mid Nov: Registrations open 28 Feb: Draft of presentation slides due. 22 Mar: Conference begins. 27 Mar: ICANN meeting begins Contact ------- Website * www.nznog.org General Enquiries * info(a)nznog.org Talks and Papers * talks(a)nznog.org Talk Proposals -------------- Please send all talk proposals (including lightning talks) to talks(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. The deadline for proposals is November 1st, 2005. While the majority of speaking slots will be filled by November 1st, a limited number of slots may be available after that date for topics that are timely, important, or otherwise exceptional. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Title of Talk: Abstract: Length of talk: Author's short biography: Whether travel and accommodation assistance will be required:

1 0

APNIC 20 update - IPv6 workshop and pre-meeting routing workshop
by Miwa Fujii 21 Aug '05

21 Aug '05

[Apologies for duplicates] APNIC 20 update #8 ______________________________ 20th APNIC Open Policy Meeting 6-9 September 2005 Hanoi, Vietnam ______________________________ Dear APNIC members and friends, There are now only three weeks to go until the APNIC 20 meeting in Hanoi. This is an update announcement with important information on two of the workshops being conducted in conjunction with APNIC 20. Contents -------- 1. IPv6 workshop 2. Pre-conference routing workshop 1. IPv6 workshop ---------------- Places are still available for the full-day IPv6 workshop presented by Jordi Palet (Consulintel). Date: Tuesday 6 September 2005 IPv6, the new Internet protocol is currently being deployed around the world, and it is important for ISPs and upstream providers to start considering IPv6 deployment in their own networks if they are to meet the expected growth in customer demand. This workshop offers a brief, practical introduction to the basics of IPv6. Participants will learn how to activate IPv6 on their own laptops, and be given practical instruction on: * Installing IPv6 on different platforms (XP/W2003, Linux, BSD) * Basic stateless/stateful configuration, including privacy setup * Transition mechanisms * Examples of applications During the workshop the attendees will also learn to do some basic monitoring and troubleshooting of the IPv6 network. Details are available at: http://www.apnic.net/meetings/20/programme/ipv6-ws.html 2. Pre-conference routing workshop ---------------------------------- Places are still available for the six-day routing workshop (including the 3-day Routing essentials workshop and the 3-day Routing and multihoming workshop) Routing essentials workshop by Amante Alvaran (APNIC Training team) Date: Tuesday 30 August - Thursday 1 September 2005 (no sessions on the national holiday, Friday 2 September) This routing essentials workshop covers basic network infrastructure design principles that will allow participants to understand and configure interior and exterior gateway routing protocols. The workshop will begin by introducing participants to OSPF and BGP, and will cover the principles of routing policy, including router configuration under both protocols. Routing and multihoming workshop by Philip Smith (Cisco) Date: Saturday 3 September - Monday 5 September 2005 This workshop is designed to provide an empowering learning environment. This is a technical workshop and attendees should be technical staff who are operating a wide area TCP/IP base Internet Service Provider (ISP) network or Internet eXchange Point (IXP), likely with international and/or multi-provider connectivity. You will learn following in this workshop: * Techniques for design, set-up, and operation of a metropolitan, regional, or national ISP backbone network. This includes advanced BGP4 and complex network configurations. * IOS Essentials every ISP should be doing. The hidden secrets that all key NSPs have been using for years, but not telling anyone. * Techniques for multiple connections to the Internet (multihoming), including connections to IXPs, NSP, and transoceanic Internet links. Participants are expected to bring their own PC to all sessions of the pre-conference routing workshop. Details are available at: http://www.apnic.net/meetings/20/programme/routing-ws.html If you have any questions or suggestions about APNIC 20, please email the APNIC Secretariat at <meetings(a)apnic.net> We look forward to seeing you in Hanoi. Best 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 ---------------------------------------------------------------------- See you at APNIC 20! Hanoi, Vietnam, 6-9 September 2005 www.apnic.net/meetings ______________________________________________________________________ _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce

1 0

Can someone from Clear please contact me off list ASAP
by Mark Karena 18 Aug '05

18 Aug '05

Can someone from Clear please contact me off list ASAP, one of our sales staff has been trying to get the below corrected for 3 days now. > www.capitaltyres.co.nz Server: dns1.clear.net.nz Address: 203.97.33.1 www.capitaltyres.co.nz canonical name = webserver2.enlightenhosting.com.or capitaltyres.co.nz nameserver = dns1.clear.net.nz capitaltyres.co.nz nameserver = dns2.clear.net.nz dns1.clear.net.nz internet address = 203.97.33.1 dns2.clear.net.nz internet address = 203.97.37.1 Thanks, -------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING +64 7 853 6060 http://www.enlightenhosting.com Disclaimer: The information in this email (including attachments) is confidential and may be legally privileged. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email and destroy the message. If you are not the intended recipient, any use, disclosure, copying or distribution is prohibited and may be unlawful.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Aug '05

17 Aug '05

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Aug '05

17 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS18400 as-name: NZRR-AS18400 descr: 203.167.235.0/24 descr: WIX peering at '202.7.0.148' descr: see Citylink RT job #3031 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18400 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: aut-num: AS18400 as-name: NZRR-AS18400 descr: 203.167.235.0/24 descr: WIX peering at '202.7.0.148' descr: see Citylink RT job #3031 descr: WIX peering at '202.7.0.148' descr: see Citylink RT job #3031 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18400 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18400 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18400 descr: Route set advertised to AS9439 by 203.167.235.0/24 - AS18400 members: 218.101.2.0/23^23-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: Route set advertised to AS9439 by Xtreme - AS18400 members: 218.101.2.0/23^23-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Aug '05

17 Aug '05

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

1 0

RE: [nznog] Tiger on Intel Laptop (via vmware)
by Tim Hoffman 17 Aug '05

17 Aug '05

try http://img145.imageshack.us/img145/1157/dscf13204bh.jpg -----Original Message----- From: Matt Mariu <Matt.Mariu(a)nz.logicalcsi.com> To: 'Tim Hoffman' <tim(a)hoffman.net.nz> Date: Thu, 18 Aug 2005 08:50:42 +1200 Subject: RE: [nznog] Tiger on Intel Laptop (via vmware) > Link no worky worky... > > -----Original Message----- > From: Tim Hoffman [mailto:tim(a)hoffman.net.nz] > Sent: Wednesday, 17 August 2005 23:29 > To: NZNOG(a)list.waikato.ac.nz > Subject: [nznog] Tiger on Intel Laptop (via vmware) > > > This might interest some of you. > > http://img145.imageshack.us/my.php?image=dscf13204bh.jpg > <http://img145.imageshack.us/my.php?image=dscf13204bh.jpg> > OS X Tiger on Intel via vmware (fiddled vmware to do the jobbie) > > Share and enjoy > -Exparrot and Tim > >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Aug '05

17 Aug '05

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

1 0

Tiger on Intel Laptop (via vmware)
by Tim Hoffman 16 Aug '05

16 Aug '05

This might interest some of you. http://img145.imageshack.us/my.php?image=dscf13204bh.jpg OS X Tiger on Intel via vmware (fiddled vmware to do the jobbie) Share and enjoy -Exparrot and Tim

1 0

InternetNZ releases ENUM Personal User Agent Prototype software u nder Open Source BSD Licence.
by Michael Sutton 16 Aug '05

16 Aug '05

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

5 4

maxnet DC staff
by Tom 16 Aug '05

16 Aug '05

It would seem maxnet have changed their phone numbers and I am unable to contact emergency DC staff :(( help..........

1 0

HEADSUP - more webcasts
by Webmaster 16 Aug '05

16 Aug '05

I can now confirm that Radio New Zealand will be simulcasting the David Lange memorial service on the internet. This will be from 11am this Saturday. We expect enormous interest. The simulcast will use an anycast address, with servers based at NZ exchanges and in the US. http://www.radionz.co.nz/lange/ regards, Richard Hulse

1 0

HEADSUP - Webcasting in the next few days
by Richard Naylor 16 Aug '05

16 Aug '05

After last nights bandwidth panic, we now have approvals to carry out the following webcasts over the next few days. 1. Thursday 18 August - Electoral Fiscal Update - 1100Hrs This will be "on-demand" video that will come available after the embargo is lifted at 1100. Probably quite popular. Main URL is www.scoop.co.nz - backup URL is www.r2.co.nz/20050818 2. Saturday 20 August - 1430 Hrs - Wedding of Clare Hinkley and Matthew Short Unlikely to cause much network disturbance. URL is www.r2.co.nz/20050820 3. Sunday 21 August - 1400Hrs to 1600 - Labour Party Election Campaign Launch Main URL is www.labour.org.nz back up URL is www.r2.co.nz/20050821 This will be a multi-bit rate event, probably including a 2Mbps stream - FYI - not sure who is carrying the Lange Service on Saturday, we may have an update on that later in the week. Rich

1 0

Last minute bandwidth need - AKL
by Richard Naylor 15 Aug '05

15 Aug '05

Evening All, We have been asked to handle a "last minute" webcast request and my usual bandwidth suppliers aren't answering the phone (its 5:15pm). Anyone with 1-5Mbps bandwidth available at AKL Town Hall on Sunday 21 August please contact me off list or on 021 897 089. There is a budget. I only need bandwidth back to APE, so anyone with a wireless link to the Sky Tower will be fine. 1 Mbps will be fine also, but more is also nice :-) Rich

1 0

VPN over Australian Telecom TG3 network and Cisco PIX IOS 6.3(1)
by Tushar Panchal (DSLWN) 15 Aug '05

15 Aug '05

Hi all, Just wanted everyone to be aware that when a user connecting via a Cisco Secure VPN client from Australian TG3 wireless network to a Cisco PIX running the code 6.3(1) it will cause the PIX to reload. Therefore, please upgrade to 6.3(4) if you are experiencing this problem. Not exactly sure why this happens but we are currently looking into it. The error on the PIX will be point to the ISAMKP receiver service. Cheers, Tushar

1 0

Xtra Telecom
by Dream Net Sales 15 Aug '05

15 Aug '05

Hello, Could someone from Xtra/Telecom please reply off list regarding some Xtra broadband customers who can not access some websites due to IP blocking We have called Xtra to no avail. Thank you. Regards Adam Fenech www.dreamnet.co.nz 0800 484 393 WARNING This email contains information which is CONFIDENTIAL and may be subject to LEGAL PRIVILEGE. If you are not the intended recipient you must not peruse, use, disseminate, distribute or copy this email or attachments. If you have received this in error please notify us immediately by return email, 0800484393 and delete this email. Thank you.

2 1

InternetNZ - M-co ENUM Report - Consultation response due date 19 th August 2005
by Michael Sutton 15 Aug '05

15 Aug '05

InternetNZ kindly reminds those responding to the ENUM Consultation Report that submissions are due by the 19th of August 2005 (close-of-business). Alternatively please advise us by that date should you require additional time. We invite comments and submissions by individuals, organizations and companies. InternetNZ members are also encouraged to respond to this Report. On-topic comments from NZNOG List members are very much welcomed. Given the time constraints present, we encourage and welcome interested persons to provide their comments in as succinct manner as they are able. Should you wish to state general support for this work and have no detailed comment we also would appreciate such a contribution. Please email your submission to <mailto:enum-tf(a)internetnz.net.nz> mailto:enum-tf(a)internetnz.net.nz The complete Report is available at: <http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete .pdf> http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf InternetNZ's public ENUM information web-site is available at: <http://www.internetnz.net.nz/public/enum/> http://www.internetnz.net.nz/public/enum/ Sincerely Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chairman - InternetNZ Enum Task Force Telephone: +64 4 475 9235 Mobile: +64 21 305500 Facsimile: +64 21 305002 ENUM = Enabling (existing) telephone numbers to be registered as Internet Addresses [ Apologies to those who receive duplicate messages ] [ Sent as HTML to avoid broken web addresses ]

1 0

Off Topic: Corporate Connection
by Gavin Palmer 15 Aug '05

15 Aug '05

Hiya All, Please forgive the off topic post. Could I ask please for someone to contact me off list if your organisation is able to provide a corporate level internet connection for our company in Albany on the Shore. We currently have a flat rate 10Mb fibre link for our whole building (multiple businesses) and we are looking to separate ourselves from that with a similar high speed link, this is an info gathering exercise at this point, after gathering the various offers and proposals we will make a final decision. Many thanx in advance for your help. Cheers Gav

1 0

TCL NOC?
by Simon Garner 15 Aug '05

15 Aug '05

Hi, If there is anyone from the TelstraClear NOC on this list, could they contact me off list? TIA -Simon

1 0

RE: [nznog] Vodafone's spanky new 3G network.
by Donald Neal 15 Aug '05

15 Aug '05

This would be a good time for this thread to stop. Some days ago would have been better, but now would be good. - Donald Neal NZNOG List Administrator Donald Neal |"Do you think some people work Support Engineer |harder to be stupider than others?" NGN Operations |- Det. Pembleton 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

Vodafone's spanky new 3G network.
by Jonny Martin 14 Aug '05

14 Aug '05

As we all know, porn has been a significant technology enabler for some time... >From Paul Brislen's article on the Vodafone 3G network: - Unlike TelstraClear, which recently pulled its adult entertainment channel, Vodafone 3G will be offering a range of adult choices, including enough video clips, tips and games. Vodafone's brochure promises to "keep your hands full for a whole 24 hours". - None of the TCL moral stand in there! Cheers, Jonny.

7 6

Thanks all for the numbering plan info
by Ian Batterbee 10 Aug '05

10 Aug '05

Thanks to all those who replied, especially those who pointed me at very relevant URLS, such as this one http://www.numberingplans.com/index.php?goto=plans&by=E.164&s=NZ&action=show

1 0

Vodafone numbering plan
by Ian Batterbee 10 Aug '05

10 Aug '05

Can someone who has good and accurate knowledge of the current Vodafone NZ telephone number numbering plan (ie, valid patterns and dial string length after the 021 bit) please contact me off-list. Thanks.

1 0

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

10 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS9433 as-name: NZRR-AS9433 descr: Massey University descr: WIX peering at '202.7.0.44' descr: see Citylink RT job #2963 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9433 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: G.Eustace(a)massey.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050805 source: NZRR REPLACED BY: aut-num: AS9433 as-name: NZRR-AS9433 descr: Massey University descr: WIX peering at '202.7.0.44' descr: see Citylink RT job #2963 descr: PNIX peering at '218.100.21.11' descr: see Citylink RT job #2984 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9433 import: from AS9281 accept ANY AND NOT fltr-bogons export: to AS9281 announce AS9433 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: G.Eustace(a)massey.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050811 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9281:RS-ROUTES:AS9433 descr: Route set advertised to AS9281 by Massey - AS9433 members: 130.123.0.0/16^16-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: G.Eustace(a)massey.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050811 source: NZRR

1 0

Cisco 5000 switch PSU
by John S Russell 09 Aug '05

09 Aug '05

This is a personal request, not one made on behalf of my corporate masters. If anyone out there has a PSU for an old Cisco 5000 series modular switch (or better, two such PSUs) that they would be willing to exchange for money and/or beer and/or being owed a favour, can they drop me an e-mail please? Thanks in advance! JSR

1 0

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

07 Aug '05

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

1 0

Are Telecom Micro Outages still an issue?
by Gary T. Benner 07 Aug '05

07 Aug '05

HI all, Have been racking my brains trying to solve a problem, and I suddenly remembered an issue that Telecom had regarding "micro-outages". Does this problem still exist? Our problem comes up with a customer using chat rooms in the Moodle Learning Management System, for students in remote locations. The chat room relies upon a persistent socket connection for the duration of the "chat". Perhaps for 30+ mins or so at a time. However students and teachers are regularly dropped. The Chat daemon is basically a socket server, and the only way I can see this happening is if the socket connection is broken. We do not see this effect in LAN trials. kind regards Gary Benner Ref#: 41006

2 1

RE: [nznog] Are Telecom Micro Outages still an issue?
by Regan Murphy 07 Aug '05

07 Aug '05

I'd suggest looking at your firewall. Many firewalls have a configurable timeout for connections. The Sonicwall firewalls for example have a default "Inactivity Timeout in Minutes" of 5 minutes but it is configurable per port/protocol. -- Regan ________________________________ From: Gary T. Benner [mailto:gary(a)123.co.nz] Sent: Monday, 8 August 2005 12:19 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] Are Telecom Micro Outages still an issue? HI all, Have been racking my brains trying to solve a problem, and I suddenly remembered an issue that Telecom had regarding "micro-outages". Does this problem still exist? Our problem comes up with a customer using chat rooms in the Moodle Learning Management System, for students in remote locations. The chat room relies upon a persistent socket connection for the duration of the "chat". Perhaps for 30+ mins or so at a time. However students and teachers are regularly dropped. The Chat daemon is basically a socket server, and the only way I can see this happening is if the socket connection is broken. We do not see this effect in LAN trials. kind regards Gary Benner

1 0

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

04 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS9433 as-name: NZRR-AS9433 descr: Massey University descr: WIX peering at '202.7.0.44' descr: see Citylink RT job #2963 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9433 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: G.Eustace(a)massey.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050805 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9433 descr: Route set advertised to AS9439 by Massey University - AS9433 members: 130.123.0.0/16^16-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: G.Eustace(a)massey.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050805 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Aug '05

02 Aug '05

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

1 0

RIPE NCC to begin allocating from new IPv4 range
by leo vegoda 01 Aug '05

01 Aug '05

Dear Colleagues, This announcement is being sent to multiple lists. I apologise for duplicates. The RIPE NCC received the IPv4 address range 89.0.0.0 - 91.255.255.255 (89.0.0.0/8 and 90.0.0.0/7) from the IANA in June 2005. We expect to start making allocations from this range in the near future. We have started announcing two prefixes from each /8, which originate in AS12654. They are: 89.192.0.0/16 89.255.248.0/21 90.192.0.0/16 90.255.248.0/21 91.192.0.0/16 91.255.248.0/21 Details of target names and addresses, reachability tools and other information are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html You may want to update any filters you have in place. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

APNIC20 - IPv6 workshop and Pre-meeting routing workshop
by Miwa Fujii 01 Aug '05

01 Aug '05

Hi All, Apologies for duplicate copies. Dear APNIC members and friends, There are only six weeks to go before APNIC 20 commences in Hanoi, Vietnam. In this announcement: --------------------- 1. IPv6 workshop 2. Pre-conference routing workshop 3. Early bird registration extended 1. IPv6 workshop ---------------- Places are still available for the full day IPv6 workshop run by Jordi Palet (Consulintel). Date: Tuesday 6 September 2005 Participants will have hands-on experience of installing IPv6 on different platforms, basic stateless/statefull configuration, transition mechanisms, and more. More details are available at: http://www.apnic.net/meetings/20/programme/ipv6-ws.html 2. Pre-conference routing workshop ---------------------------------- We are pleased to announce the following pre-conference technical workshop, added to the programme since the last meeting announcement was sent: Six-day routing workshop run by Philip Smith (Cisco) and Amante Alvaran (APNIC) Date: Tuesday 30 August - Monday 5 September 2005 (no sessions on the national holiday, Friday 2 September) This workshop will cover basic aspects of OSPF and BGP and also provide hands-on router configuration workshop. More details are available at: http://www.apnic.net/meetings/20/programme/routing-ws.html 3. Early bird registration extended ----------------------------------- Early bird registration has been extended to Friday 5 August 2005. If you have not yet registered please do so quickly to take advantage of the significant saving. The online registration form is available at: http://www.apnic.net/cgi-bin/registration.pl?event_id=73 Terms and conditions of registration are available at: http://www.apnic.net/meetings/20/rego/conditions.html If you have any questions or suggestions about APNIC 20, please email us at <meetings(a)apnic.net> We look forward to seeing you in Hanoi. Best 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 ---------------------------------------------------------------------- See you at APNIC 20! Hanoi, Vietnam, 6-9 September 2005 www.apnic.net/meetings ______________________________________________________________________

1 0

Congratulations
by Matthew Poole 31 Jul '05

31 Jul '05

to Mark, who's been a father for nearly 24 hours now. Which Mark? I'll leave that as an exercise for you, dear reader :P -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

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

31 Jul '05

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

1 0

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

31 Jul '05

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

1 0

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

31 Jul '05

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

1 0

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

31 Jul '05

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

1 0

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

30 Jul '05

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

1 0

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

29 Jul '05

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

2 1

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

29 Jul '05

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

1 0

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

29 Jul '05

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

3 3

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

28 Jul '05

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

2 1

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

28 Jul '05

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

1 0

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

28 Jul '05

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

1 0

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

28 Jul '05

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

1 0

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

28 Jul '05

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

3 2

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

28 Jul '05

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

1 0

Webcasting Heads up
by Richard Naylor 27 Jul '05

27 Jul '05

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

1 0

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

27 Jul '05

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

11 15

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

27 Jul '05

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

1 0

Interesting articles from Beehive
by Ian McDonald 27 Jul '05

27 Jul '05

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

1 0

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

27 Jul '05

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

1 0

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

27 Jul '05

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

1 0

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

26 Jul '05

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

1 0

Victoria SCS Mail Admin
by Jonathan Brewer 26 Jul '05

26 Jul '05

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

3 4

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

25 Jul '05

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

1 0

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

25 Jul '05

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

5 4

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

20 Jul '05

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

1 0

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

20 Jul '05

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

1 0

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

20 Jul '05

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

1 0

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

20 Jul '05

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

1 0

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

19 Jul '05

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

1 0

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

18 Jul '05

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

3 3

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

18 Jul '05

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

1 0

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

18 Jul '05

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

1 0

DPE and 3CIX
by Andy Linton 18 Jul '05

18 Jul '05

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

3 2

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

18 Jul '05

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

4 3

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

18 Jul '05

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

2 1

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

18 Jul '05

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

8 12

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

18 Jul '05

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

1 0

Frame Relay services
by Andy Linton 16 Jul '05

16 Jul '05

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

1 0

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

14 Jul '05

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

1 0

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

14 Jul '05

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

4 3

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

14 Jul '05

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

9 11

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

14 Jul '05

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

1 0

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

14 Jul '05

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

1 0

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

13 Jul '05

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

2 1

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

13 Jul '05

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

4 6

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

13 Jul '05

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

1 0

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

13 Jul '05

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

3 3

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

13 Jul '05

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

1 0

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

13 Jul '05

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

1 0

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

13 Jul '05

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

1 0

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

13 Jul '05

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

2 2

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

12 Jul '05

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

1 0

Not quite 255
by Juha Saarinen 10 Jul '05

10 Jul '05

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

1 0

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

10 Jul '05

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

1 0

Noc Contact list.
by Simon Lyall 09 Jul '05

09 Jul '05

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

1 0

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

07 Jul '05

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

1 0

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

07 Jul '05

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

1 0

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

07 Jul '05

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

1 0

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

07 Jul '05

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

2 1

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

05 Jul '05

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

1 0

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

03 Jul '05

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

1 0

Another Technical Announcement
by Richard Naylor 03 Jul '05

03 Jul '05

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

1 1

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

03 Jul '05

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

1 0

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

03 Jul '05

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

2 2

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

03 Jul '05

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

1 0

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

03 Jul '05

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

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

2 1

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

DSL Tails in NZ
by Sam Sarkis 30 Jun '05

30 Jun '05

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

2 1

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

29 Jun '05

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

3 2

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

29 Jun '05

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

4 4

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

29 Jun '05

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

2 1

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

29 Jun '05

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

1 0

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

29 Jun '05

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

9 10

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

29 Jun '05

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

1 0