- NZNOG - lists.nznog.org

Error
by Sahil Gupta - NET4U LIMITED 10 Aug '03

10 Aug '03

Apologies, the network is 202.50.167.0/24 and not 202.50.267.0/24 Regards, Sahil Gupta Senior Account Manager NET4U LIMITED Phone: 0508-263-848 Fax: 07-8582659 Mobile: 029-366-6375

1 0

Prefix-List Update for Net4U Limited (AS23746)
by Sahil Gupta - NET4U LIMITED 10 Aug '03

10 Aug '03

Hi, Could ISP's currently peering with Net4U at APE kindly add the below listed network to the net4u's current prefix-list: 202.50.267.0/24 A full prefix-list is attached. Regards, Sahil Gupta Senior Account Manager NET4U LIMITED Phone: 0508-263-848 Fax: 07-8582659 Mobile: 029-366-6375

1 0

RE: [nznog] Re:Domain Name Scams
by Paul Adshead 10 Aug '03

10 Aug '03

It is to be fair, incredibly simple to find out most of the information regarding the allocation of a domain. Just go to the main DomaiNZ page: www.domainz.net.nz and enter your (NZ) domain name into the search box on the left. After selecting OK, then a warning about not being able to use this information for any other purpose appears - and this warning automatically disappears after a few seconds anyway. After this, then all of the details for the queried domain appear! As the warning message automatically disappears, then the content of the warning is probably not legally enforceable anyway - you could have been looking away from your screen at that point! They should have a "Yes I've read the above agreement" checkbox before you can proceed... Possible ways that the scam has found out the contact info: - if you knew enough about HTML, ASP and VB, it would be simple enough to write a program that once every five seconds sent a request to the DomaiNZ webserver starting at "a.co.nz" and finishing at "zzzzzzz999.net.nz", to find out the information for the various domains - it would take a while though; - you could use an 'electronic dictionary' of words in order to cut down on the unlikely examples; - there is also probably an online listing somewhere, of all of the currently active companies in New Zealand, you could then just try "<company name>.co.nz" and "<company name>.net.nz". There are far too many ways that people could have done it. I'm not condoning what has happened and have not done so myself, I'm just trying to explain how easy it is to do so. I was hit with three renewals too... Paul Adshead Network and Systems Manager OTL Software Ltd www.otl.co.nz -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Friday, 8 August 2003 13:04 To: PhoneNet Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Re:Domain Name Scams On Fri, 8 Aug 2003, PhoneNet wrote: > I have today received 5 letters from The Domain Registry of America, > Melbourne (posted in UK) asking me to re-register some of my domains as > they are due to expire - so they are at it also. Got one here as well, and what bothers me is that although the domain in question is registered under my own name, the letter was addressed to my company, which doesn't appear in whois data anywhere. Somebody's been trawling... -- Juha Saarinen _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

5 5

FW: [nznog] Re:Domain Name Scams
by Tim John 09 Aug '03

09 Aug '03

> Just go to the main DomaiNZ page: www.domainz.net.nz and > enter your (NZ) > domain name into the search box on the left. After selecting > OK, then a > warning about not being able to use this information for any > other purpose > appears - and this warning automatically disappears after a > few seconds > anyway. After this, then all of the details for the queried > domain appear! > As the warning message automatically disappears, then the > content of the > warning is probably not legally enforceable anyway - you > could have been > looking away from your screen at that point! They should > have a "Yes I've > read the above agreement" checkbox before you can proceed... > Actually, the warning message appears on the Domainz homepage, the 'SRS is being queried' page and the results page. It only disappears when the page reloads with the results. It's only a GUI'd representation of a WhoIs query. On registration, there is a physical need to click a "I've read the terms of service" button, but at the end of the day, any information entered as part of a domain name registration is available in the public domain. Tim > Possible ways that the scam has found out the contact info: > - if you knew enough about HTML, ASP and VB, it would be > simple enough to > write a program that once every five seconds sent a request > to the DomaiNZ > webserver starting at "a.co.nz" and finishing at > "zzzzzzz999.net.nz", to > find out the information for the various domains - it would > take a while > though; > - you could use an 'electronic dictionary' of words in order > to cut down on > the unlikely examples; > - there is also probably an online listing somewhere, of all of the > currently active companies in New Zealand, you could then > just try "<company > name>.co.nz" and "<company name>.net.nz". > > There are far too many ways that people could have done it. > > I'm not condoning what has happened and have not done so > myself, I'm just > trying to explain how easy it is to do so. I was hit with > three renewals > too... > > Paul Adshead > Network and Systems Manager > OTL Software Ltd > www.otl.co.nz > > > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Friday, 8 August 2003 13:04 > To: PhoneNet > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Re:Domain Name Scams > > > On Fri, 8 Aug 2003, PhoneNet wrote: > > > I have today received 5 letters from The Domain Registry > of America, > > Melbourne (posted in UK) asking me to re-register some of > my domains as > > they are due to expire - so they are at it also. > > Got one here as well, and what bothers me is that although > the domain in > question is registered under my own name, the letter was > addressed to my > company, which doesn't appear in whois data anywhere. > > Somebody's been trawling... > > -- > Juha Saarinen > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

Info Session: Certificate In Web-based Instruction
by Abigail 08 Aug '03

08 Aug '03

On Thursday, August 14th at 1100 hrs Pacific Standard Time (GMT 08:00) there will be a Webcast featuring the instructors of the Certificate in Web-Based Instruction (CWI). Webcast participants can ask questions and interact with the instructors of this 24 week program that will be offered entirely online beginning September 15, 2003. The CWI program gives you the tools and knowledge necessary to design, develop and deliver Web-based courses or add online components to the face-to-face classroom. Please register to participate in the live Webcast by visiting http://www.sfu.ca/lidc/telestraining. If you are unable to make it to this live presentation at the above date then you can attend our next Webcast scheduled for Wednesday, September 3 at 1100 hrs PST (GMT 8:00). Abby Dy Communications Specialist Certificate in Web-Based Instruction Tel: 604-806-5156 ady(a)sfu.ca

1 0

DomainNamesNZ
by Felix Tsang 07 Aug '03

07 Aug '03

I recon their misleading letters should be taken up with the commerce commission. Felix Tsang

8 7

DomainNamesNZ
by Dominic O'Hare 07 Aug '03

07 Aug '03

The company "DomianNamesNZ" is actually "Domain Names Australia Pty Limited" a Australian based company incorporated in Victoria. They also go by "Internet Registry Pty Limited" and "NetRegister" (Not NetRegistry). The address they're using, the ASB tower in Auckland is an internet bought mail forwarding address. They have also done mail-outs and fax-outs in Australia - http://www.auda.org.au/about/news/2003061903.html One thing interesting is that they have sent letters to customers of Internet Name Group (ING) who did a similar mail-out in NZ in a while back, the letters were filled with B.S and obviously asked they register renew domains with them. Regards, Dominic

2 1

Re: [nznog] Re:Domain Name Scams
by Jamie Baddeley 07 Aug '03

07 Aug '03

got one here too. >>> Juha Saarinen <juha(a)saarinen.org> 8/8/2003 1:03:46 PM >>> On Fri, 8 Aug 2003, PhoneNet wrote: > I have today received 5 letters from The Domain Registry of America, > Melbourne (posted in UK) asking me to re-register some of my domains as > they are due to expire - so they are at it also. Got one here as well, and what bothers me is that although the domain in question is registered under my own name, the letter was addressed to my company, which doesn't appear in whois data anywhere. Somebody's been trawling... -- Juha Saarinen _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

TelstraClear Routing?
by Steve Withers 07 Aug '03

07 Aug '03

I've been using a VPN to connect to work across the WIX for over a year - via a Paradise cable modem. I was seeing about 1mbps throughput, consistent with AT&T's Wellington Office (the actual people-at-desks office) United Networks connection to the WIX. A traceroute showed roughly 5-6 hops as I recall. Today....I can't get my VPN tunnel up at all and the traceroute shows 15 hops and my traffic is going to Auckland and off to Reach in HongKong...and then into AT&T's network there and then back again via Australia to NZ. Is anyone else seeing similar routing troubles? -- Steve Withers <swithers(a)mmp.org.nz>

2 1

OT: MP3 player
by Tim John 07 Aug '03

07 Aug '03

Hi, Sorry for the off topic posting, but during the Netforum conference last month, Domainz were selling 128Mb MP3 players for $120 (including GST) to it's participants; it was just for a bit of fun. I have a number of these little devices left - which double as pen drives - so if anyone would like one, please visit the following URL and I'll organise one to be sent out. Delivery is $7.50 (within New Zealand). https://www.domainz.net.nz/mp3/order.asp Again, sorry for taking this off topic, but wanted to wanted to offer these to all. Tim DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

Re: Nznog Digest, Vol 8, Issue 4
by Paul J 07 Aug '03

07 Aug '03

maybe try http://www.lucentdocs.com/ ? >>>>>MAX4000/6000 You'll first need to 'enable' yourself with what ever max enable password you have set on the max box. ctrl + d >P=Password >00-309 Full Access <password> ctrl + d >E=Termsrv show users kill <session ID> <<<<< >>>>>MAXTNT userstat (or users | grep <string>) users -k <session ID> <<<<< ----- Original Message ----- From: "Robert Mena" <rt_mena(a)yahoo.com> To: <nznog(a)list.waikato.ac.nz> Sent: Friday, August 08, 2003 2:22 AM Subject: [nznog] Re: Nznog Digest, Vol 8, Issue 4 > Hi Simon, > > I do live in Brazil and I was not aware that this was > a problem for the list. > > The IP you mantioned is probably the cable modem > company. > > I do not know how to get in this termserv mode. When > I need to to things I telnet to MAX, login as admin. > > I've tryed that kill with no luck. Sould I read > <something> first ? > > ------------ > Message: 2 > Date: Thu, 7 Aug 2003 13:42:20 +1200 (NZST) > From: Simon Lyall <simon.lyall(a)ihug.co.nz> > Subject: Re: [nznog] disconectin users in a MAX TNT > To: <nznog(a)list.waikato.ac.nz> > Message-ID: > > <Pine.LNX.4.30.0308071332230.19531-100000(a)boggle.ihug.co.nz> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Wed, 6 Aug 2003, Robert Mena wrote: > > I was wondering how can I disconnect a user from a > MAX > > TNT ? > > 1. Why are you posting to nznog when you're in Brazil? > > 2. You apepar to have a slight spam problem: > > http://www.moensted.dk/spam/?addr=200.174.69.242 > > Maybe you'll be able to disconnect them now.. > > > 3. Are you useing a TNT or a MAX ? They are a little > different... > > 4. On a TNT run: > > > userstat ? > > On a Max go into Termsrv mode and run: > > % show users > % kill <session ID> > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > Paul Joslin Systems Administrator Network Operations Center IHUG LTD, Auckland, New Zealand www.ihug.co.nz

1 0

Re: Nznog Digest, Vol 8, Issue 4
by Robert Mena 06 Aug '03

06 Aug '03

Hi Simon, I do live in Brazil and I was not aware that this was a problem for the list. The IP you mantioned is probably the cable modem company. I do not know how to get in this termserv mode. When I need to to things I telnet to MAX, login as admin. I've tryed that kill with no luck. Sould I read <something> first ? ------------ Message: 2 Date: Thu, 7 Aug 2003 13:42:20 +1200 (NZST) From: Simon Lyall <simon.lyall(a)ihug.co.nz> Subject: Re: [nznog] disconectin users in a MAX TNT To: <nznog(a)list.waikato.ac.nz> Message-ID: <Pine.LNX.4.30.0308071332230.19531-100000(a)boggle.ihug.co.nz> Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 6 Aug 2003, Robert Mena wrote: > I was wondering how can I disconnect a user from a MAX > TNT ? 1. Why are you posting to nznog when you're in Brazil? 2. You apepar to have a slight spam problem: http://www.moensted.dk/spam/?addr=200.174.69.242 Maybe you'll be able to disconnect them now.. 3. Are you useing a TNT or a MAX ? They are a little different... 4. On a TNT run: > userstat ? On a Max go into Termsrv mode and run: % show users % kill <session ID> __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

RE: [nznog] DomainNamesNZ
by Steve Phillips 06 Aug '03

06 Aug '03

I received one of these as well requesting i register my name with a .net (not .net.nz) extension - this may produce even more issues as this would be outside the control of the DNC. the listed address is 20, 135 Albert St in Auckland - I considered wandering into town to go and LART them in person.. my domain was only registered February of this year so they have managed to get a list of .nz names after this point. -- Steve. At 14:14 7/08/2003, Tim John wrote: >This has been taken up by the DNC - check out her website for the latest >info. > >I'm not sure whether they are using an old version of the .nz zone file >(although these haven't been available for at least 18 months), or they have >some scripting engine pulling the information of the general WhoIs. This >breaches the DNC policy on use of private information for commercial gain, >yada, yada ... > >Tim

2 1

DomainNamesNZ
by Matthew G Brown 06 Aug '03

06 Aug '03

I've been getting a few good old snail mail letters from Domainnamesnz.com offering me to register domain names. Eg: I own learnbydestroying.co.nz and the "offer" is for learnbydestroying.net . How ever since these letters include; Reference #, MPID ? , Closing Date, Credit card details, and very little info to conclude that this is a Renewal many people have inadvertently paid the money ( $237 for two years ! ) thinking it's a Domainz or other registrar invoice. I'm not questioning the legality of this , as I am no expert, how ever im interested to know how so many of my clients and myself ended up with these letters? Anyone else experienced these letters or perhaps had clients pay for what they thought was a valid renewal? Best Regards Matthew G Brown Managing Director B & R Holdings LIMITED Nelson, New Zealand Ph: 027 4807731 Http://www.brh.co.nz

4 5

RE: [nznog] DomainNamesNZ
by mark.harris＠ssc.govt.nz 06 Aug '03

06 Aug '03

From: Tim John > I'm not sure whether they are using an old version of > the .nz zone file (although these haven't been available > for at least 18 months), or they have some scripting > engine pulling the information of the general WhoIs. It's not an old one and they didn't get it from Domainz. One of the domains I got a note about was only registered a few months ago via Freeparking. As an aside, this will work on some people. My wife (who is not unclueful) was opening the mail, handed me the nonvoices and said "Bills from Domainz. Do you want me to pay them online?" People will read what they think they see, no matter how much clue you throw at them. Cheers Mark Harris Senior Advisor, Portal Operations State Services Commission PO Box 329, Wellington, NZ Tel: 64 4 495 2844

1 0

RE: [nznog] DomainNamesNZ
by Paul Adshead 06 Aug '03

06 Aug '03

I have also received a .net.nz 'renewal' for each of the three .co.nz domains that I have! You have to read very carefully before you actually realise that it is a proposal rather than a renewal.. :-( Paul Adshead Network & Systems Manager OTL Software Ltd www.otl.co.nz -----Original Message----- From: Dan Clark [mailto:dan(a)scarfies.net] Sent: Thursday, 7 August 2003 14:14 To: Matthew G Brown; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] DomainNamesNZ yes, we have received around 1/2 a dozen so far, some of my clients got them directly and were just going to pay it! hrmm, in reading the small print on the back it also says something about not being able to change registrar's for a whole 60 days after 'transferring to them' Regards Dan Clark Network Manager Scarfies.Net Ltd Wickliffe Ltd ----- Original Message ----- From: "Matthew G Brown" <Matt(a)Brh.Co.Nz> To: <nznog(a)list.waikato.ac.nz> Sent: Thursday, August 07, 2003 2:09 PM Subject: [nznog] DomainNamesNZ > I've been getting a few good old snail mail letters from > Domainnamesnz.com offering me to register domain names. Eg: I own > learnbydestroying.co.nz and the "offer" is for learnbydestroying.net . > How ever since these letters include; Reference #, MPID ? , Closing > Date, Credit card details, and very little info to conclude that this is > a Renewal many people have inadvertently paid the money ( $237 for two > years ! ) thinking it's a Domainz or other registrar invoice. > > I'm not questioning the legality of this , as I am no expert, how ever > im interested to know how so many of my clients and myself ended up with > these letters? Anyone else experienced these letters or perhaps had > clients pay for what they thought was a valid renewal? > > > > Best Regards > > Matthew G Brown > Managing Director > B & R Holdings LIMITED > Nelson, New Zealand > Ph: 027 4807731 > Http://www.brh.co.nz > > > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

disconectin users in a MAX TNT
by Robert Mena 06 Aug '03

06 Aug '03

Hi, I was wondering how can I disconnect a user from a MAX TNT ? With other RAS I could reset SXX where XX would be the session it is attached to. Unfortunately under MAX I could not find the proper command, reset, kill, drop, disconnect etc... __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

Orcon Internet Prefix List Update (2003-08-07)
by Craig Whitmore 06 Aug '03

06 Aug '03

For all those peering with Orcon Internet (AS17746) please update your Prefix Lists/BGP to allow the Following Network (202.50.176.0/24) ip prefix-list orcon-national permit 202.50.176.0/24 Thanks Craig Whitmore Systems Administrator Orcon Internet http://www.orcon.net.nz

1 0

2500 PS
by Jon Leeman 05 Aug '03

05 Aug '03

Thanks to all that responded to Andy's plea, on my behalf, for a 2500 series power supply. I've managed to find a supplier in NZ - a list member - and it should be here in a couple of weeks. In the meantime we got the box running per the solution at http://www.hardstaff.com/Computer/Cisco/index.html and it's been working for about a week now with no apparent problems. Cheers, Jon

1 0

RE: IP to PSTN/Public network gateway.
by Gavin Legge [Invincible Technologies Limited NZ] 05 Aug '03

05 Aug '03

Thank you everyone for your comments. After a call to chch (thank's Matt) and a look at fx.net.nz i think i have all i need for now - at least a damn good start and all the right contacts. so thanks again to all. Now - how to get the normal PSTN voice calls routed back to the IP pbx/phone... hmm - time to jump into bed with a telco i think or at least connect to one .. IP/CCS7 POI/interface anyone?? lol cheers Gavin

1 0

IP to PSTN/Public network gateway.
by Gavin Legge [Invincible Technologies Limited NZ] 05 Aug '03

05 Aug '03

First question from a new list member (probably go straight to FAQ no?).... Does anyone know of a (preferably) New Zealand based provider that provides an 'IP' to 'public network' and back again gateway service (at a charge or otherwise)? Somewhere we can fire IP voice calls at, that will take the IP voice call and poke it out to the local number, local number being a normal everyday phone connected to the PSTN ? Thanks for any advice Regards Gavin Legge

1 0

Cisco 2500 power supply
by Andy Linton 04 Aug '03

04 Aug '03

Anybody got a spare 2500 power supply that Jon Leeman in Nauru can have for his 2509 dial in box? If there's a box that can be cannibalised that's fine. Include Jon on any replies if you can help. andy

1 0

Newbie with MAX : how to set up aditional pools
by Robert Mena 04 Aug '03

04 Aug '03

Hi, I am trying to configure an already running MAX TNT with TAOS 8.0.2. I need to change the current pool and add a new pool. Does anybody have a howto for that ? I've searched and downloaded the PDFs but no luck so far... Regards. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

RE: [nznog] 411 Scam
by Carl Black 04 Aug '03

04 Aug '03

Yes, actually - in the last month I've noticed about 4 to 5 times the amount of 411 spam I would normally expect hitting my organisation. > -----Original Message----- > From: Barry Murphy [mailto:barry(a)unix.co.nz] > Sent: Monday, August 04, 2003 10:54 PM > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] 411 Scam > > > Hi, > > Just wondering if anyone else is being bombarded with 411 > scams of late. > Until a week ago I had only received maybe 6 over the year, > but over the > last 2 weeks I have received about 2-5 a day. > > Cheers > Barry > > > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

411 Scam
by Barry Murphy 04 Aug '03

04 Aug '03

Hi, Just wondering if anyone else is being bombarded with 411 scams of late. Until a week ago I had only received maybe 6 over the year, but over the last 2 weeks I have received about 2-5 a day. Cheers Barry

2 1

Looking for Cisco VIP4
by Craig Whitmore 29 Jul '03

29 Jul '03

Hi folks.. I'm urgently looking for a few VIP2's or a VIP4 or above for a Cisco 7500. If anyone can help please let me know. Also if anyone has any type of IO Controller for a 7200 it would be great as well. Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

1 1

RE: [nznog] Uniforum Meeting and Various Belated Thank-Yous
by Tim John 29 Jul '03

29 Jul '03

Hi Joe, It was a pleasure for Domainz to be able to bring you to the Conference and I'm sure your presence was appreciated by everyone. However, the least you could have done was bought an MP3 player off me ... :) Tim -----Original Message----- From: Joe Abley [mailto:jabley(a)isc.org] Sent: Tuesday, 29 July 2003 7:44 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Uniforum Meeting and Various Belated Thank-Yous (warning! non-operational content. Press "d" now.) This is going to sound a little bit like a delayed reaction, but I've been travelling wildly since the meeting and hence have something of a mental meme backlog. It was very pleasant to be back putting names to faces and waving my hands in front of a whiteboard. Many thanks to Roger & Co for organising the meeting, and for inviting me to come down and speak. My travel to Auckland was paid for by Domainz -- without their funding I likely would not have been able to visit to talk at the meeting, nor turn up the F root server instance in Auckland in July (if your traceroute to f.root-servers.net currently leaves the country, feel free to contact peering(a)isc.org to set up a peering session with us in Auckland, or encourage your ISP to do the same). Direct assistance and ongoing donations of time, network, colo and equipment for the F root server were provided by Juniper, TelstraClear, Citylink, FX Networks and 2day.com, all of whom should hereby consider themselves heartily thanked. http://www.isc.org/ISC/news/pr-07232003.html Joe _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

UseNet's Looking Glass...
by Dan Clark 29 Jul '03

29 Jul '03

Hi Guys, The UseNet Looking Glass http://www.usenet.net.nz/lg.cgi web server, appears to not be parsing cgi scripts? Does anyone have a traceroute looking glass, close to the APE, I could use for a minute or two please? Regards Dan Clark Network Manager Wickliffe Ltd Scarfies.Net Ltd

7 9

Uniforum Meeting and Various Belated Thank-Yous
by Joe Abley 28 Jul '03

28 Jul '03

(warning! non-operational content. Press "d" now.) This is going to sound a little bit like a delayed reaction, but I've been travelling wildly since the meeting and hence have something of a mental meme backlog. It was very pleasant to be back putting names to faces and waving my hands in front of a whiteboard. Many thanks to Roger & Co for organising the meeting, and for inviting me to come down and speak. My travel to Auckland was paid for by Domainz -- without their funding I likely would not have been able to visit to talk at the meeting, nor turn up the F root server instance in Auckland in July (if your traceroute to f.root-servers.net currently leaves the country, feel free to contact peering(a)isc.org to set up a peering session with us in Auckland, or encourage your ISP to do the same). Direct assistance and ongoing donations of time, network, colo and equipment for the F root server were provided by Juniper, TelstraClear, Citylink, FX Networks and 2day.com, all of whom should hereby consider themselves heartily thanked. http://www.isc.org/ISC/news/pr-07232003.html Joe

1 0

RE: [nznog] Staff remote access
by barry＠unix.co.nz 27 Jul '03

27 Jul '03

Sorry about that, should have been offlist. Barry ------------------------------------------------------------- This mail sent through UnixCo Webmail: http://www.unix.co.nz/

1 0

Staff remote access
by nward＠esphion.com 27 Jul '03

27 Jul '03

I currently have an IPExpress circuit from TelstraClear providing Internet access. I'd like to be able to have staff use some kind of fast IP service (ie ADSL), to connect in to the office to do thier work, I don't want Internet access over these links, just some form of nationally accessable 'VPN'. It only needs to be 1-2Mbit speed, but can't complain if its more. Is this kind of thing being done? I tried to contact Telecom about it only to have some customer support monkey tell me that ADSL is an Internet thing, and as much as I love dealing with support people... I assume many replies to this will be deemed commercial and OT, so please contact me off-list. Nathan Ward

2 1

Linux beginners training
by Jonathon Horsman 27 Jul '03

27 Jul '03

Hi all Sorry for this rather blatant advertisement, but I believe this may be of interest to some. I am running a one day Linux beginners training in Auckland this Saturday (2nd of August). Details can be found here: http://www.59uptime.com/training.html Please email me if you're interested in attending. Thanks very much Jonathon

1 0

Notification: Disable Seconday Public (Stratum 2) NTP Service
by Kim Shepherd 24 Jul '03

24 Jul '03

The University of Waikato will cease to provide public stratum 2 NTP service as of 31st July, 2003. A list of alternative stratum 2 servers is available at the URL below: http://www.eecis.udel.edu/~mills/ntp/clock2a.html Regards, Kim. -- Kim Shepherd Systems Operator/Administrator ITS Systems & Development The University of Waikato, Hamilton, New Zealand DDI: +64-7-838-4681 Mob: +64-25-240-8682 Mail: kims(a)waikato.ac.nz

1 0

Fwd: 100,000 Reasons ...
by barry＠unix.co.nz 23 Jul '03

23 Jul '03

Anyone else receiving spam which "is not part of a mass mailout" ? They even fail to refer to which domain I should keep with domainz, as far as I know I have moved my domains over to orcon almost a month ago. Barry ----- Forwarded message from Domainz(a)domainz.net.nz ----- Date: Mon, 21 Jul 2003 11:39:53 +1200 From: Domainz(a)domainz.net.nz Reply-To: Domainz(a)domainz.net.nz Subject: 100,000 Reasons ... To: blacklabel(a)orcon.net.nz This email has been sent directly to 'blacklabel(a)orcon.net.nz' and is not part of a mass mailout. ----- <http://www.domainz.net.nz> <http://www.domainz.net.nz> <http://www.domainz.net.nz/> <http://www.domainz.net.nz> You now have a choice of registrars to manage your domain name requirements. At Domainz, we've registered more than 100,000 .nz domain names over the past six years, making us the specialists. So while you now have a choice, we think it's best exercised by doing nothing! That way you can ensure Domainz remains your registrar. Why stay with Domainz? Because your domain name is a valuable asset that needs to be properly protected and managed. We're New Zealand's most experienced and expert domain name registrar - and that makes us the people you should rely on for top service and best value for money. Domain names are our speciality! What else do I get by doing nothing? We are now able to offer you other services alongside your domain name registration. Right now, you can have: * Domain name parking - domain name reservation *FREE* * Website redirection - redirection of your website traffic so you can have it managed wherever you want *FREE* * Email forwarding - we can redirect your email to wherever you want *FREE* * Email hosting - we'll manage your whole email system using our facilities * Web hosting - we'll do the same with your website Domainz offers all of our services in a range of packages designed to fit the differing requirements of our customers. What will I miss if I act now? Remember, there's no need to do anything - and we strongly advise that you don't! Very soon we'll be offering a range of new products and services, including: * More billing and payment options - including variable registration periods for domain names * Registration of international domain names - such as .com, .net and .ws But if I need to know more! If you would simply like to discuss your domain name needs or find out more information, then email us by clicking here <mailto:4service(a)domainz.net.nz?subject=Information Please> . You can also ring us on 0800 366 2469 or visit our website, www.domainz.net.nz <http://www.domainz.net.nz/> . We'd like to join you in doing nothing... but we're busy. Because we value your business, doing nothing isn't an option for us. We're busy working on new and better ways to make managing your domain name easier and more cost effective! Thanks for registering your domain name with us. We intend to keep making it worth your while - to do nothing at all. Derek Locke and the team at Domainz To unsubscribe from future emails of this nature from Domainz, click here <mailto:noemail(a)domainz.net.nz?subject=Email Unsubscribe - '61717200'> . ----- End forwarded message ----- ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

10 9

Re: [nznog] Mae-West Looking Glass
by Jamie Baddeley 21 Jul '03

21 Jul '03

MIA. Last seen in action september 2002. http://web.archive.org/web/*/http://nitrous.digex.net probably assimilated by the borg. jamie >>> "Mark Frater" <mfrater(a)quicksilver.co.nz> 07/21 12:37 PM >>> What ever happened to nitrous.digex.net? Mark _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Mae-West Looking Glass
by Mark Frater 20 Jul '03

20 Jul '03

What ever happened to nitrous.digex.net? Mark

2 1

Performance issues on Citylink yesterday (Saturday Jul 19)
by Simon Blake 19 Jul '03

19 Jul '03

Our apologies to the folks who suffered from performance problems on Citylink yesterday (Saturday). They were caused by an ISP under apparent SYN attack - not in itself a particularly unusual occurence, what was interesting was that in changes on Saturday morning (about 3am) said ISP managed to make the IP address under attack an unfiltered broadcast address on Citylink, so we all got to share the pain of a kind of combo SYN/smurf attack. The attacks manifested as 8-10Mb/s streams coming from the ISP onto Citylink for 1-4 minutes, about twice every two hours, which in turn caused some 10Mb customers on Citylink some disruption of service - 100Mb/1Gb customers seemed to be largely unaffected. The short duration and occasional nature of the problem did cause a few issues with tracking it and getting a resolution (about 9pm last night) - again, our apologies for not getting it sorted faster. Cheers Si

1 0

exploits logged in Auckland
by Joe Abley 17 Jul '03

17 Jul '03

I have seen attempts to exploit the recently-announced cisco vuln on a router of my acquaintance in Auckland, starting early this morning NZST. This confirms the notes on nanog (and in the updated cisco advisory) about functional exploits being published and used in the wild. The source addresses appear spoofed, and so far all of the hits have been received from outside NZ. The address "x.x.x.114" (see below) isn't in use on a router or anywhere else. Presumably the k1dd13z will realise at some point that there is more dead air on the Internet than ciscos, and will start harvesting victim addresses from traceroute instead of choosing them randomly. Is anybody contemplating customer-facing filters which block protocols 53, 54, 77 and 103? Jul 19 01:26:52 router 3587: Jul 19 01:22:37 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 54 216.191.222.139 (FastEthernet0/1.500 0002.xxxx.xxxx) -> x.x.x.164, 1 packet Jul 19 01:38:27 router 5320: Jul 19 01:34:12 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 53 245.128.83.9 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:38:27 router 5321: Jul 19 01:34:13 NZST: %SEC-6-IPACCESSLOGRP: list 127 denied pim 216.225.202.10 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:41:38 router 5327: .Jul 19 01:37:23 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 77 157.160.104.37 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:42:02 router 5331: .Jul 19 01:37:47 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 55 222.21.158.112 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:46:06 router 5343: .Jul 19 01:41:51 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 55 221.44.200.77 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:46:06 router 5344: .Jul 19 01:41:51 NZST: %SEC-6-IPACCESSLOGRP: list 127 denied pim 148.246.222.60 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:48:25 router 5347: .Jul 19 01:44:10 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 55 159.136.236.96 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:48:25 router 5348: .Jul 19 01:44:10 NZST: %SEC-6-IPACCESSLOGRP: list 127 denied pim 151.142.170.98 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:51:02 router 5353: Jul 19 01:46:48 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 53 172.75.88.52 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:51:02 router 5354: Jul 19 01:46:48 NZST: %SEC-6-IPACCESSLOGRP: list 127 denied pim 146.95.71.5 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:52:17 router 5359: Jul 19 01:48:02 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 53 252.40.243.114 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:52:17 router 5360: Jul 19 01:48:02 NZST: %SEC-6-IPACCESSLOGRP: list 127 denied pim 151.94.44.88 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet Jul 19 01:52:35 router 5362: Jul 19 01:48:20 NZST: %SEC-6-IPACCESSLOGNP: list 127 denied 53 24.17.251.39 (Serial2/2.1 DLCI xxx) -> x.x.x.114, 1 packet

1 0

Cisco Security Advisory: Cisco IOS Interface Blocked by IPv4 Packet
by Rob Thomas 17 Jul '03

17 Jul '03

FYI. -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty); -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: Cisco IOS Interface Blocked by IPv4 Packet Revision 1.3 ============ Last Updated 2003 July 17 at 23:00 UTC (GMT) For Public Release 2003 July 17 at 6:10 UTC (GMT) ================= - ---------------------------------------------------------------------- Please provide your feedback on this document. - ---------------------------------------------------------------------- Contents ======== Summary Affected Products Details Impact Software Versions and Fixes Obtaining Fixed Software Workarounds Exploitation and Public Announcements Status of This Notice: INTERIM Distribution Revision History Cisco Security Procedures - ---------------------------------------------------------------------- Summary ======= Cisco routers and switches running Cisco IOS� software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets with specific protocol fields sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available. Cisco has made software available, free of charge, to correct the problem. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml. Affected Products ================= This issue affects all Cisco devices running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets. Cisco devices which do not run Cisco IOS software are not affected. Devices which run only Internet Protocol version 6 (IPv6) are not affected. Details ======= Cisco routers are configured to process and accept Internet Protocol version 4 (IPv4) packets by default. A rare, specially crafted sequence of IPv4 packets with protocol type 53 (SWIPE), 55 (IP Mobility), 77 (Sun ND), or 103 (Protocol Independent Multicast - PIM) which is handled by the processor on a Cisco IOS device may force the device to incorrectly flag the input queue on an interface as full, which will cause the router to stop processing inbound traffic on that interface. This can cause routing protocols to drop due to dead timers. Interfaces which are explicitly configured to run PIM will not be affected by traffic with protocol type 103. An interface with PIM enabled will have one of the following three commands in the interface configuration: ip pim dense-mode, ip pim sparse-mode, or ip pim sparse-dense-mode. On Ethernet interfaces, Address Resolution Protocol (ARP) times out after a default time of four hours, and no traffic can be processed. The device must be rebooted to clear the input queue on the interface, and will not reload without user intervention. The attack may be repeated on all interfaces causing the router to be remotely inaccessible. A workaround is available, and is documented in the Workarounds section. The following two Cisco vulnerabilities are documented in DDTS: CSCea02355 ( registered customers only) affects all Cisco routers running Cisco IOS software. This documents the flaw with protocols 53, 55, and 77. CSCdz71127 ( registered customers only) was introduced by an earlier code revision, and documents an input queue vulnerability to protocol 103 with a device which is not configured for PIM. Any version of software which has the fix for CSCdx02283 ( registered customers only) is vulnerable. Registered customers can find more details using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl ( registered customers only) . To identify a blocked input interface, use the show interfaces command and look for the Input Queue line. If the current size (in this case, 76) is larger than the maximum size (75), the input queue is blocked. Use the show buffers command and look for the prot field. Below are two examples: Router#show interface ethernet 0/0 Ethernet0/0 is up, line protocol is up Hardware is AmdP2, address is 0050.500e.f1e0 (bia 0050.500e.f1e0) Internet address is 172.16.1.9/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:41, output 00:00:07, output hang never Last clearing of "show interface" counters 00:07:18 Input queue: 76/75/1091/0 (size/max/drops/flushes); Total output drops: 0 !--- The 76/75 shows that this is blocked Router#show buffers input-interface serial 0/0 Buffer information for Small buffer at 0x612EAF3C data_area 0x7896E84, refcount 1, next 0x0, flags 0x0 linktype 7 (IP), enctype 0 (None), encsize 46, rxtype 0 if_input 0x6159D340 (FastEthernet3/2), if_output 0x0 (None) inputtime 0x0, outputtime 0x0, oqnumber 65535 datagramstart 0x7896ED8, datagramsize 728, maximum size 65436 mac_start 0x7896ED8, addr_start 0x7896ED8, info_start 0x0 network_start 0x7896ED8, transport_start 0x0 source: 212.176.72.138, destination: 212.111.64.174, id: 0xAAB8, ttl: 41, prot: 103 !--- prot: 103 is proof that this is one of the attack packets Impact ====== A device receiving these specifically crafted IPv4 packets will force the inbound interface to stop processing traffic. The device may stop processing packets destined to the router, including routing protocol packets and ARP packets. No alarms will be triggered, nor will the router reload to correct itself. This issue can affect all Cisco devices running Cisco IOS software. This vulnerability may be exercised repeatedly resulting in loss of availability until a workaround has been applied or the device has been upgraded to a fixed version of code. Software Versions and Fixes =========================== Each row of the table describes a release train and the platforms or products for which it is intended. If a given release train is vulnerable, then the earliest possible releases that contain the fix and the anticipated date of availability for each are listed in the Rebuild, Interim, and Maintenance columns. In some cases, no rebuild of a particular release is planned; this is marked with the label "Not scheduled." A device running any release in the given train that is earlier than the release in a specific column (less than the earliest fixed release) is known to be vulnerable, and it should be upgraded at least to the indicated release or a later version (greater than the earliest fixed release label). When selecting a release, keep in mind the following definitions: * Maintenance Most heavily tested and highly recommended release of any label in a given row of the table. * Rebuild Constructed from the previous maintenance or major release in the same train, it contains the fix for a specific vulnerability. Although it receives less testing, it contains only the minimal changes necessary to effect the repair. Cisco has made available several rebuilds of mainline trains to address this vulnerability, but strongly recommends running only the latest maintenance release on mainline trains. * Interim Built at regular intervals between maintenance releases and receives less testing. Interims should be selected only if there is no other suitable release that addresses the vulnerability, and interim images should be upgraded to the next available maintenance release as soon as possible. Interim releases are not available through manufacturing, and usually they are not available for customer download from CCO without prior arrangement with the Cisco Technical Assistance Center (TAC). In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco TAC for assistance, as shown in the section following this table. +--------------------------------------------------------------------+ |Train |Description of |Availability of Fixed Releases | | |Image or Platform | | |--------------------------+-----------------------------------------+ | 11.x based releases | Rebuild |Interim| Maintenance | |--------------------------+-----------+-------+---------------------+ |11.1CA| |11.1(36)CA4| | | | | |** | | | |------+-------------------+-----------+-------+---------------------+ |11.2 | |11.2(26e)**| | | |------+-------------------+-----------+-------+---------------------+ |11.2P | |11.2(26)P5*| | | | | |* | | | |------+-------------------+-----------------------------------------+ |11.3 | |Not scheduled | |------+-------------------+-----------------------------------------+ |11.3T | |Not scheduled | |--------------------------+-----------------------------------------+ |12.0 based releases |Rebuild |Interim|Maintenance | |--------------------------+-----------+-------+---------------------+ | |General Deployment | | | | |12.0 |release for all | | |12.0(26) | | |platforms | | | | |------+-------------------+-----------------------------------------+ |12.0DA|xDSL support: 6100,|Migrate to 12.2DA; 12.2(10)DA2 - | | |6200 |Aug-15-2003, 12.2(12)DA3 - Aug-22-2003: | | | |Engineering Specials available on | | | |request. | |------+-------------------+-----------------------------------------+ |12.0DB|Early Deployment |Migrate to 12.3(1a) | | |6400 UAC for NSP | | |------+-------------------+-----------------------------------------+ |12.0DC|Early Deployment |Migrate to 12.3(1a) | | |6400 UAC for NRP | | |------+-------------------+-----------------------------------------+ | | |12.0(24)S2 | | | | | |12.0(23)S3 | | | | | |12.0(22)S5 | | | | | |12.0(21)S7 | | | | | |12.0(19)S4 | | | | |Core/ISP support: |12.0(18)S7 | | | |12.0S |GSR, RSP, c7200, |12.0(17)S7 | |12.0(25)S | | |c10k |12.0(16)S10| | | | | |12.0(15)S7 | | | | | |12.0(14)S8 | | | | | |12.0(13)S8 | | | | | |12.0(12)S4 | | | | | |12.0(10)S8 | | | |------+-------------------+-----------------------------------------+ |12.0SC|Cable/broadband |Migrate to 12.1(19)EC | | |ISP: ubr7200 | | |------+-------------------+-----------------------------------------+ |12.0SL|100000 ESR:c10k |Migrate to 12.0(23)S3, **12.0(17)SL9 - | | | |Jul-15-2003 | |------+-------------------+-----------------------------------------+ |12.0SP|Early Deployment |Migrate to 12.0(22)S5 | |------+-------------------+-----------------------------------------+ | |Early Deployment |12.0(21)ST7| | | |12.0ST|release for Core/ |12.0(20)ST6| | | | |ISP support: GSR, |12.0(19)ST6| | | | |RSP, c7200 |12.0(17)ST8| | | |------+-------------------+-----------------------------------------+ |12.0SX|Early Deployment |Migrate to 12.0(22)S5 | |------+-------------------+-----------------------------------------+ |12.0SY|Early Deployment |Migrate to 12.0(23)S3 | |------+-------------------+-----------------------------------------+ |12.0SZ|Early Deployment |Migrate to 12.0(23)S3 | |------+-------------------+-----------------------------------------+ |12.0T |Early Deployment |12.0(7)T3**| | | |------+-------------------+-----------+-------+---------------------+ | |8510c, ls1010, | | |12.0(26)W5(28) | | |cat8540c,cat8540m, | | | | | |ls1010 | | | | | |-------------------+-----------+-------+---------------------+ | |c5atm |12.0(26)W5 | | | | | |(28a) | | | | |-------------------+-----------+-------+---------------------+ | |Cat4232 and |12.0(25)W5 | | | |12.0W5|Cat2948G-L3 |(27) | | | | |-------------------+-----------+-------+---------------------+ | |C6MSM |Engineering| | | | | |Special | | | | | |available | | | | | |on request | | | | |-------------------+-----------+-------+---------------------+ | |c5rsfc,c5rsm,C3620,| | |12.1(20) | | |C3640, C4500, | | | | | |C7200, RSP | | | | |------+-------------------+-----------+-------+---------------------+ |12.0WC|Early deployment |12.0(05)WC8| | | | |2900XL-LRE,2900XL/ | | | | | |3500XL; 2950 | | | | | |release | | | | |------+-------------------+-----------+-------+---------------------+ |12.0WT|Early deployment |Engineering| | | | |Catalyst switches: |Special | | | | |cat4840g, |Available | | | | | |upon | | | | | |request | | | |------+-------------------+-----------------------------------------+ |12.0X |Shortlived Early |All 12.0X(any letter) releases have | |(l) |Deployment Releases|migrated to either 12.0T or 12.1 unless | | | |otherwise documented in the X release | | | |technical notes pertaining to the | | | |specific release. Please check migration | | | |paths for all 12.0X releases. | |--------------------------+-----------------------------------------+ |12.1 based releases |Rebuild |Interim|Maintenance | |--------------------------+-----------+-------+---------------------+ | |General Deployment | |12.1 | | |12.1 |release for all | |(18.4) |12.1(19) | | |platforms | | | | |------+-------------------+-----------------------------------------+ |12.1AA| |Migrate to 12.2 | |------+-------------------+-----------------------------------------+ |12.1AX|Catalyst 3750 |12.1(14)EA1| | | | | |- | | | | | |Engineering| | | | | |special | | | | | |available | | | | | |upon | | | | | |request | | | |------+-------------------+-----------+-------+---------------------+ |12.1AY|Catalyst 2940 | | |12.1(13)AY | |------+-------------------+-----------------------------------------+ |12.1DA|6160 platform |Migrate to 12.2DA | |------+-------------------+-----------------------------------------+ |12.1DB|6400 UAC |Migrate to 12.3(1a) | |------+-------------------+-----------------------------------------+ |12.1DC|6400 UAC |Migrate to 12.3(1a) | |------+-------------------+-----------------------------------------+ |12.1E |Core Enterprise |12.1(8b)E14| |12.1(19)E | | |support - c7200, |12.1(13)E7 | | | | |Catalyst 6000, RSP |12.1(14)E4 | | | | | |**12.1(12c)| | | | | |E7 | | | | | |12.1(11b) | | | | | |E12- | | | | | |Aug-4-2003 | | | | | |12.1(6)E12 | | | |------+-------------------+-----------------------------------------+ |12.1EA|12.1(4)EA |Migrate to 12.1(13)EA1c | | |12.1(6)EA | | | |12.1(8)EA | | | |12.1(9)EA | | | |12.1(11)EA | | | |-------------------+-----------------------------------------+ | |12.1(12c)EA |12.1(13) | | | | |12.1(13)EA |EA1c | | | |------+-------------------+-----------+-------+---------------------+ |12.1EB|LS1010 | | |12.1(14)EB | |------+-------------------+-----------+-------+---------------------+ |12.1EC|Early Deployment | | |12.1(19)EC (scheduled| | | | | |last week of July) | |------+-------------------+-----------+-------+---------------------+ |12.1EV|Early Deployment | | |12.1(12c)EV | |------+-------------------+-----------+-------+---------------------+ |12.1EW|Early Deployment | | |12.1(13)EW,12.1(19)EW| | |Cat4000 L3 | | | | |------+-------------------+-----------+-------+---------------------+ |12.1EX|Early deployment |12.1(13)EX2| | | |------+-------------------+-----------+-------+---------------------+ |12.1EY| | |12.1(14)E4 | | | |------+---------+---------+-----------+-------+---------------------+ | | | |12.1(14)EA1| | | |12.1YJ| | |- | | | | | | |Jul-28-2003| | | |------+-------------------+-----------+-------+---------------------+ |12.1T |Early deployment |12.1(5)T15*| | | | | |* | | | |------+-------------------------------------------------------------+ |12.1X |12.1X releases generally migrate to 12.1T, 12.2 or 12.2T as | |(l) |specified below. Please refer to specific train Technical | | |notes for documented migration path. | |------+-------------------------------------------------------------+ |12.1XA|Short lived Early |Migrate to 12.1(5)T15 | | |Deployment Release | | |------+-------------------+-----------------------------------------+ |12.1XC|Short lived Early |Migrate to12.2(17) | |12.1XD|Deployment Releases| | |12.1XH| | | |12.1XI| | | |------+-------------------+-----------------------------------------+ |12.1XB|Short lived Early |Migrate to 12.2(15)T5 | |12.1XF|Deployment Releases| | |12.1XG| | | |12.1XJ| | | |12.1XL| | | |12.1XP| | | |12.1XR| | | |12.1XT| | | |12.1YB| | | |12.1YC| | | |12.1YD| | | |12.1YH| | | |------+-------------------+-----------------------------------------+ |12.1XM|Short lived Early |Migrate to 12.2(2)XB11 | |12.1XQ|Deployment Releases| | |12.1XV| | | |------+-------------------+-----------------------------------------+ |12.1XU|Short lived Early |Migrate to 12.2(4)T6 | | |Deployment Release | | |------+-------------------+-----------------------------------------+ |12.1YE|Short lived Early |Migrate to 12.2(2)YC | |12.1YF|Deployment Release | | |12.1YI| | | |--------------------------+-----------------------------------------+ |12.2 based releases |Rebuild |Interim|Maintenance | |--------------------------+-----------+-------+---------------------+ | |General Deployment |12.2(16a) | | | |12.2 |(GD) candidate for |12.2(12e) | |12.2(17) | | |all platforms |12.2(10d) | | | |------+-------------------+-----------+-------+---------------------+ |12.2B |12.2(2)B-12.2(4)B7 |12.3(1a) | | | | |-------------------+-----------+-------+---------------------+ | |12.2(4)B8-12.2(16)B|12.2(16)B1 | | | |------+-------------------+-----------+-------+---------------------+ |12.2BC|Early Deployment |12.2(15)BC1| | | | |Release |(Scheduled | | | | | |end of | | | | | |July) | | | |------+-------------------+-----------+-------+---------------------+ |12.2BW|Early Deployment |Migrate to | | | | |for use with 7200, |12.3(1a) | | | | |7400, and 7411 | | | | | |platforms | | | | |------+-------------------+-----------+-------+---------------------+ |12.2BX|Broadband/Leased | | |12.2(16)BX | | |line | | | | |------+-------------------+-----------+-------+---------------------+ |12.2BZ|Early Deployment |12.2(15)BZ1| | | | |Release | | | | |------+-------------------+-----------------------------------------+ |12.2CX|Early Deployment |Migrate to 12.1(15)BC1 | | |Release | | |------+-------------------+-----------------------------------------+ |12.2CY|Early Deployment |Migrate to 12.1(15)BC1 | | |Release | | |------+-------------------+-----------------------------------------+ |12.2DA|Early Deployment |12.2(10)DA2| | | | |Release |- | | | | | |Jul-15-2003| | | | | |12.2(12)DA3| | | | | |- | | | | | |Aug-22-2003| | | | | |Enginering | | | | | |Special | | | | | |available | | | | | |on request | | | |------+-------------------+-----------------------------------------+ |12.2DD|Early Deployment |Migrate to 12.3(1a) | | |Release | | |------+-------------------+-----------------------------------------+ |12.2DX|Early Deployment |Migrate to 12.3(1a) | | |Release | | |------+-------------------+-----------------------------------------+ |12.2JA|Cisco Aironet | | |12.2(11)JA | | |hardware platforms:| | | | | |Introduction of | | | | | |Access Point | | | | | |feature in IOS, | | | | | |Cisco 1100 Series | | | | | |Access Point | | | | | |(802.11b) | | | | |------+-------------------+-----------+-------+---------------------+ |12.2MB|Specific Technology|12.2(4)MB12| | | | |ED for 2600 7500 | | | | | |(GPRS/PDSN/GGSN | | | | | |2600/7200/7500) | | | | |------+-------------------+-----------+-------+---------------------+ |12.2MC|Early Deployment: |12.2(13)MC1| | | | |IP RAN |CCO: 7/24/ | | | | | |03 | | | |------+-------------------+-----------+-------+---------------------+ |12.2MX| |12.2(8)YD | | | | | | | | | |------+-------------------+-----------+-------+---------------------+ |12.2S |Core/ISP support: |12.2(14)S1 |12.2 | | | |GSR, RSP, c7200 | |(16.5)S| | |------+-------------------+-----------+-------+---------------------+ |12.2SX|IOS Support for |12.2(14)SX1| | | | |C6500 Supervisor 3 | | | | |------+-------------------+-----------+-------+---------------------+ |12.2SY|VPN feature release|12.2(14) | | | | |for c6k/76xx VPN |SY1, 12.2 | | | | |service module. |(8)YD | | | |------+-------------------+-----------+-------+---------------------+ |12.2SZ|7304 Platform |12.2(14)SZ2| | | |------+-------------------+-----------+-------+---------------------+ | | |12.2(15)T4/| |No more maintenance | | |New Technology |5,12.2(13) | |trains for 12.2T are | | |Early Deployment |T5, |12.2 |planned, please | |12.2T |(ED) release for |12.2(11) |(16.5)T|migrate to latest | | |all platforms |T9,12.2(8) | |12.3 Mainline | | | |T10, | |release. | | | |12.2(4)T6 | | | |------+-------------------+-----------------------------------------+ |12.2X |Short lived Early |Many short lived releases migrate to the | |(l) |Deployment Releases|same train; the trains below this point | |12.2Y |- |until the following section are not | |(l) | |grouped by strict alphabetical order, but| | | |are grouped by migration path. Please | | | |review documented migration paths for | | | |your trains. | |------+-------------------+-----------------------------------------+ |12.2XA|Short lived Early |Migrate to 12.2(11)T9 | | |Deployment Releases| | |------+-------------------+-----------------------------------------+ |12.2XS| |12.2(2)XB11 | |------+-------------------+-----------------------------------------+ |12.2XD|Short lived Early |Migrate to 12.2(15)T5 | |12.2XE|Deployment Releases| | |12.2XH| | | |12.2XI| | | |12.2XJ| | | |12.2XK| | | |12.2XL| | | |12.2XM| | | |12.2XQ| | | |12.2XU| | | |12.2XW| | | |12.2YA| | | |12.2YB| | | |12.2YC| | | |12.2YF| | | |12.2YG| | | |12.2YH| | | |12.2YJ| | | |12.2YT| | | |------+-------------------+-----------------------------------------+ |12.2YN|Short lived Early |Migrate to 12.2(13)ZH | | |Deployment Releases| | |------+-------------------+-----------------------------------------+ | |Short lived Early |Migrate to 12.2(14)SY1 available | |12.2YO|Deployment Releases|Aug-4-2003: Engineering Special | | | |available on request | |------+-------------------+-----------------------------------------+ | |Early Deployment | | | | |12.2XB|Release with |12.2(2)XB11| | | | |continuing support | | | | |------+-------------------+-----------------------------------------+ |12.2XC|Short lived Early |Migrate to 12.2(16)B1 | | |Deployment Releases| | |------+-------------------+-----------------------------------------+ |12.2XF|Short lived Early |Migrate to 12.2(15)BC1 | | |Deployment Release | | | |UBR10000 | | |------+-------------------+-----------------------------------------+ |12.2XG|Short lived Early |Migrate to 12.2(8)T10 | | |Deployment Release | | |------+-------------------+-----------------------------------------+ |12.2XN|Short lived Early |Migrate to 12.2(11)T9 | |12.2XT|Deployment Releases| | |------+-------------------+-----------------------------------------+ |12.2YD|Short lived Early |Migrate to 12.2(8)YY | | |Deployment Release | | |------+-------------------+-----------------------------------------+ |12.2YP|Short lived Early |**12.2(11) | | | | |Deployment Release |YP1 | | | |------+-------------------+-----------------------------------------+ |12.2YK| |Migrate to 12.2(13)ZC | |------+-------------------+-----------------------------------------+ |12.2YL|Short lived Early |Migrate to 12.2(13)ZH | |12.2YM|Deployment Releases| | |12.2YU| | | |12.2YV| | | |------+-------------------+-----------------------------------------+ |12.2YQ|Short lived Early |Migrate to 12.2(15)ZL | |12.2YR|Deployment Releases| | |------+-------------------+-----------------------------------------+ |12.2YS|Short lived Early |12.2(15)YS/| | | | |Deployment Release |1.2(1) | | | |------+-------------------+-----------+-------+---------------------+ |12.2YW|Short lived Early |12.2(8)YW2 | | | | |Deployment Releases| | | | |------+-------------------+-----------+-------+---------------------+ |12.2YX|Short lived Early |12.2(11)YX1| | | | |Deployment Release | | | | | |Crypto for 7100/ | | | | | |7200 | | | | |------+-------------------+-----------+-------+---------------------+ |12.2YY|Short lived Early |12.2(8)YY3 | | | | |Deployment Releases| | | | | |IOS support for | | | | | |General Packet | | | | | |Radio Service | | | | |------+-------------------+-----------+-------+---------------------+ |12.2YZ|Short lived Early |12.2(11)YZ2| | | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZA|Short lived Early | | |12.2(14)ZA2 | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZB|Short lived Early |12.2(8)ZB7 | | | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZC|Short lived Early | | |12.2(13)ZC | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZD|Short lived Early |Not | | | | |Deployment Release |Scheduled | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZE|Short lived Early |12.3(1a) | | | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZF|Short lived Early |Not | | | | |Deployment Release |Vulnerable | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZG|Short lived Early |Not | | | | |Deployment Release |Vulnerable | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZH|Short lived Early |Not | | | | |Deployment Release |Vulnerable | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZJ|Short lived Early |12.2(15)ZJ1| | | | |Deployment Release | | | | |------+-------------------+-----------+-------+---------------------+ |12.2ZL|Short lived Early |Not | | | | |Deployment Release |Vulnerable | | | |--------------------------+-----------------------------------------+ |12.3 based releases |NOT VULNERABLE | |--------------------------------------------------------------------+ |Notes: **Marked versions of code are not available on CCO. Please | |contact TAC and request the specific images you need posted. | +--------------------------------------------------------------------+ Notes: ** Marked versions of code are not available on CCO. Please contact the Cisco TAC and request the specific images you need posted. Obtaining Fixed Software ======================== Customers with contracts should obtain upgraded software free of charge through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on the Cisco worldwide website at http://www.cisco.com/tacpage/sw-center/sw-ios.shtml. Customers whose Cisco products are provided or maintained through prior or existing agreement with third-party support organizations such as Cisco Partners, authorized resellers, or service providers should contact that support organization for assistance with obtaining the free software upgrade(s). Customers who purchase direct from Cisco but who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows. * +1 800 553 2447 (toll free from within North America) * +1 408 526 7209 (toll call from anywhere in the world) * e-mail: tac(a)cisco.com Please have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC. Please do not contact either "psirt(a)cisco.com" or "security-alert(a)cisco.com" for software upgrades. See http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special localized telephone numbers, instructions, and e-mail addresses for use in various languages. Workarounds =========== AFTER APPLYING THE WORKAROUND the input queue depth may be raised with the hold-queue <new value> in interface command -- the default size is 75. This will allow traffic flow on the interface until the device can be reloaded. Cisco recommends that all IOS devices which process IPv4 packets be configured to block traffic directed to the router from any unauthorized source with the use of Access Control Lists (ACLs). This can be done at multiple locations, and it is recommended that you review all methods and use the combination which fits your network best. Legitimate traffic is defined as management protocols such as telnet, snmp or ssh, and configured routing protocols from explicitly allowed peers. All other traffic destined to the device should be blocked at the input interface. Traffic entering the network should also be carefully evaluated and filtered at the network edge if destined to an infrastructure device. Although network service providers must often allow unknown traffic to transit their network, it is not necessary to allow that same traffic destined to their network infrastructure. Several white papers have been written to assist in deploying these recommended security best practices. ACLs can have performance impact on certain platforms, so care should be taken when applying the recommended workarounds. Transit ACLs The following access list is specifically designed to block attack traffic. Note that the attack traffic can include spoofed source addresses. This access list should be applied to all interfaces of the device, and should include topology-specific filters. This could include filtering routing protocol traffic, management protocols, and traffic destined for the internal network. Protocol 103 is Protocol Independent Multicast (PIM), which is a commonly deployed application in multicast networks. Interfaces with PIM enabled have not been found to be vulnerable to exploit traffic with protocol 103; PIM traffic may be permitted to those select devices. access-list 101 deny 53 any any access-list 101 deny 55 any any access-list 101 deny 77 any any access-list 101 deny 103 any any !--- insert any other previously applied ACL entries here !--- you must permit other protocols through to allow normal !--- traffic -- previously defined permit lists will work !--- or you may use the permit ip any any shown here access-list 101 permit ip any any Prior to deploying ACLs that filter transit traffic, a classification ACL can be used to help identify required permit statements. A classification ACL is an ACL that permits a series of protocols. Displaying access-list entry hit counters helps determine required protocols: entries with zero packets counted are likely not required. Classification access-lists are detailed in the link below for infrastructure access-lists. Receive ACLs For distributed platforms, receive path access lists may be an option starting in Cisco IOS Software Versions 12.0(21)S2 for the c12000 and 12.0(24)S for the c7500. The receive access lists protect the device from harmful traffic before the traffic can impact the route processor. The CPU load is distributed to the line card processors and helps mitigate load on the main route processor. The white paper entitled "GSR: Receive Access Control Lists" will help you identify and allow legitimate traffic to your device and deny all unwanted packets: http://www.cisco.com/warp/customer/707/racl.html Infrastructure ACLs Although it is often difficult to block traffic transiting your network, it is possible to identify traffic which should never be allowed to target your infrastructure devices and block that traffic at the border of your network. The white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection ACLs: http://www.cisco.com/warp/customer/707/iacl.html Exploitation and Public Announcements ===================================== Since the initial posting of this document, the Cisco PSIRT has been made aware of public announcements of the vulnerabilities described in this advisory. PSIRT has chosen to resend to our standard distribution list immediately with further details to assist network administrators in mitigation. Status of This Notice: INTERIM ============================== This is an INTERIM notice. Although Cisco cannot guarantee the accuracy of all statements in this notice, all of the facts have been checked to the best of our ability. Cisco does not anticipate issuing updated versions of this advisory unless there is some material change in the facts. Should there be a significant change in the facts, Cisco will update this advisory. Distribution ============ This notice is posted on the Cisco worldwide website at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml. In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients at the public release date and time: * cust-security-announce(a)cisco.com * bugtraq(a)securityfocus.com * full-disclosure(a)lists.netsys.com * first-teams(a)first.org (includes CERT/CC) * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * nanog(a)merit.edu * sanog(a)sanog.org * comp.dcom.sys.cisco * Various internal Cisco mailing lists Future updates of this advisory, if any, will be placed on the Cisco worldwide web server. Users concerned about this problem are encouraged to check the URL given above for any updates. Revision History ================ +-------------------------------------------+ | Revision | 17-July-2003 | Initial public | | 1.0 | 0:00 GMT | release | |----------+--------------+-----------------| | | | Updated | | | | Workaround | | Revision | 17-July-2003 | section (access | | 1.1 | 6:10 GMT | lists), Updated | | | | table with | | | | information on | | | | 12.0W5 | |----------+--------------+-----------------| | | | Corrected "Last | | | | Updated" time; | | | | corrected | | Revision | 17-July-2003 | document title | | 1.2 | 10:30 GMT | of | | | | Infrastructure | | | | ACL link under | | | | Workaround | | | | section | |----------+--------------+-----------------| | | | Added "with | | | | specific | | | | protocol | | | | fields" in | | | | Summary | | | | section; | | | | updated Details | | | | section to | | | | include | | | | protocol types; | | | | added details | | Revision | 17-July-2003 | to the Cisco | | 1.3 | 23:00 GMT | vulnerabilities | | | | paragraph; | | | | added an output | | | | example to | | | | identify an | | | | attack packet; | | | | rewrote Transit | | | | ACLs section; | | | | updated | | | | Exploitation | | | | and Public | | | | Announcements | | | | paragraph | +-------------------------------------------+ Cisco Security Procedures ========================= Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on the Cisco worldwide website at http://www.cisco.com/warp/public/707/sec_incident_response.shtml. This includes instructions for press inquiries regarding Cisco security notices. All Cisco Security Advisories are available at http://www.cisco.com/go/psirt. - ---------------------------------------------------------------------- This notice is Copyright 2003 by Cisco Systems, Inc. This notice may be redistributed freely after the release date given at the top of the text, provided that redistributed copies are complete and unmodified, and include all date and version information. - ---------------------------------------------------------------------- Toolbar ======= All contents are Copyright � 1992-2003 Cisco Systems, Inc. All rights reserved. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQA/AwUBPxchOXsxqM8ytrWQEQLgzwCeMBqiamX2K/VvMhIgooz9d11K1VoAoLcF nmN6hA5ZuyDFBhW3o+FydDop =pSyP -----END PGP SIGNATURE-----

2 1

IPv6
by Antonio Broughton 17 Jul '03

17 Jul '03

Hey, I was just looking through the archives of the list, and found a post that was about IPv6 peering in New Zealand. I am currently trying to setup a website (http://www.ipv6.co.nz) but as such, I am the only one involved :P. If anyone wants to help me setup content for the site etc, or if you would like to use the domain for such things as the domain for a New Zealand IPv6 Peer... then by allmeans... you can use it, just email me... Antonio Broughton

14 32

Fwd: Critical Vulnerability discovered in Windows Servers
by barry＠unix.co.nz 17 Jul '03

17 Jul '03

Don't know how many windows admins out there, but incase you havn't yet heard about the new windows RPC sploit, read below. ----- Forwarded message from Haroon Meer <haroon(a)sensepost.com> ----- Date: Fri, 18 Jul 2003 02:48:06 +0200 (SAST) From: Haroon Meer <haroon(a)sensepost.com> Reply-To: Haroon Meer <haroon(a)sensepost.com> Subject: Critical Vulnerability discovered in Windows Servers To: icepick(a)cybernett.co.za Dear Barry Murphy, Vulnerability in Microsoft Windows Servers. Versions Affected : Windows XP, Windows NT4, Windows2000, Windows2003 Severity of Bug : CRITICAL Port / Service : Port 135 - Microsoft RPC A Polish security research group have found a remotely exploitable bug in Windows based operating systems. The bug affects almost the entire Microsoft Product range from Windows NT4, to Windows2000 and even Windows2003. The exploit uses port 135 as its attack vector with the exploitable component being Microsoft RPC. This vulnerability should be considred "Critical" since it yields "SYSTEM" privileges on the victim machine. Microsoft have issued an advisory and a patch is available from them at the following location : http://www.microsoft.com/security/security_bulletins/ms03-026.asp The possible workarounds for the problem untill the patch is applied are to : [a] Firewall off access to port 135 [b] Disable DCOM on the server (Using Dcomcnfg.exe) While no exploit code for this vulnerability is currently reported in the wild, the problem aknowledged by Microsoft to be exploitable, meaning that Proof of Concept exploits (and possibly worms) will not be a long time coming. Full details on the exploit can be found at http://lsd-pl.net/special.html. Sincerely. ======================================================= SensePost Research research(a)sensepost.com http://www.sensepost.com (tel) +27 12 667 4737 ======================================================= ----- End forwarded message ----- ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

Peering at the APE and WIX
by Andy Linton 16 Jul '03

16 Jul '03

At the nznog meeting in Auckland last week I said I'd give details of how to apply for a connection once the new web pages were available and so here they are: http://www.citylink.co.nz/cgi-bin/wixape.pl?tmpl=ape.tmpl http://www.citylink.co.nz/cgi-bin/wixape.pl?tmpl=wix.tmpl You may also find the two Looking Glass pages, that give a view of what is happening on the APE and WIX route servers, useful: http://www.wix.net.nz/cgi-bin/mrlg-ape.cgi http://www.wix.net.nz/cgi-bin/mrlg-wix.cgi

1 0

IOS Vulnerability
by Arron Scott 16 Jul '03

16 Jul '03

As mentioned by Joe, Cisco has just announced a vulnerability that affects all versions of IOS, on any device, switches and routers. In the first instance, it is important to note that there are currently NO known exploitations of this vulnerability, and we are announcing it after building and preparing the appropriate fixes for all current platforms. Fixes have been made available regardless of whether your routers are under a maintentance support contract or not. The following URL also defines how to build Access-lists that can protect you from this vulnerability. http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml Do not panic, if you need more detail, feel free to give me a ring. If you can find an opportunity we would recommend an upgrade, but this is out of caution rather than need. Hope this helps to clarify the situation Arron Scott Cisco NZ *********************************************************************** Arron Scott (CCIE #4099) Phone: +64-9-3551951 Systems Engineer Mobile: +64-21-883163 Cisco New Zealand mailto:ascott(a)cisco.com http://www.cisco.com ***********************************************************************

1 0

upgrade your routers
by Joe Abley 16 Jul '03

16 Jul '03

forwarded from cisco, not from any other source Begin forwarded message: > From: Scott McGrath <mcgrath(a)fas.harvard.edu> > Date: Wed Jul 16, 2003 23:02:37 Canada/Eastern > To: nanog(a)merit.edu > Subject: IOS Vulnerability > > > > For full details about the vulnerability see > > http://www.cisco.com/en/US/products/hw/routers/ps341/ > products_security_advisory09186a00801a34c2.shtml > > Scott C. McGrath >

1 1

Cisco Security Advisory: Cisco IOS Interface Blocked by IPv4 Packet
by Cisco Systems Product Security Incident Response Team 16 Jul '03

16 Jul '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cisco Security Advisory: Cisco IOS Interface Blocked by IPv4 Packet Revision 1.0 ============ For Public Release 2003 July 17 at 0:00 UTC (GMT) - -------------------------------------------------------------------------- Please provide your feedback on this document. - -------------------------------------------------------------------------- Contents ======== Summary Affected Products Details Impact Software Versions and Fixes Obtaining Fixed Software Workarounds Exploitation and Public Announcements Status of This Notice: INTERIM Distribution Revision History Cisco Security Procedures - -------------------------------------------------------------------------- Summary ======= Cisco routers and switches running Cisco IOS® software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available. Cisco has made software available, free of charge, to correct the problem. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml. Affected Products ================= This issue affects all Cisco devices running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets. Cisco devices which do not run Cisco IOS software are not affected. Devices which run only Internet Protocol version 6 (IPv6) are not affected. Details ======= Cisco routers are configured to process and accept Internet Protocol version 4 (IPv4) packets by default. A rare, specially crafted sequence of IPv4 packets which is handled by the processor on a Cisco IOS device may force the device to incorrectly flag the input queue on an interface as full, which will cause the router to stop processing inbound traffic on that interface. This can cause routing protocols to drop due to dead timers. On Ethernet interfaces, Address Resolution Protocol (ARP) times out after a default time of four hours, and no traffic can be processed. The device must be rebooted to clear the input queue on the interface, and will not reload without user intervention. The attack may be repeated on all interfaces causing the router to be remotely inaccessible. A workaround is available, and is documented in the Workarounds section. The following two Cisco vulnerabilities are documented in DDTS. CSCea02355 ( registered customers only) affects all Cisco routers running Cisco IOS software. CSCdz71127 ( registered customers only) was introduced by an earlier code revision. Any version of software which has the fix for CSCdx02283 ( registered customers only) is vulnerable. Registered customers can find more details using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl ( registered customers only) . To identify a blocked input interface, use the show interfaces command and look for the Input Queue line. If the current size (in this case, 76) is larger than the maximum size (75), the input queue is blocked. Router#show interface ethernet 0/0 Ethernet0/0 is up, line protocol is up Hardware is AmdP2, address is 0050.500e.f1e0 (bia 0050.500e.f1e0) Internet address is 172.16.1.9/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:41, output 00:00:07, output hang never Last clearing of "show interface" counters 00:07:18 Input queue: 76/75/1091/0 (size/max/drops/flushes); Total output drops: 0 ^^^^^^^^^^^^^^ ---> blocked Impact ====== A device receiving these specifically crafted IPv4 packets will force the inbound interface to stop processing traffic. The device may stop processing packets destined to the router, including routing protocol packets and ARP packets. No alarms will be triggered, nor will the router reload to correct itself. This issue can affect all Cisco devices running Cisco IOS software. This vulnerability may be exercised repeatedly resulting in loss of availability until a workaround has been applied or the device has been upgraded to a fixed version of code. Software Versions and Fixes =========================== Each row of the table describes a release train and the platforms or products for which it is intended. If a given release train is vulnerable, then the earliest possible releases that contain the fix and the anticipated date of availability for each are listed in the Rebuild, Interim, and Maintenance columns. In some cases, no rebuild of a particular release is planned; this is marked with the label "Not scheduled." A device running any release in the given train that is earlier than the release in a specific column (less than the earliest fixed release) is known to be vulnerable, and it should be upgraded at least to the indicated release or a later version (greater than the earliest fixed release label). When selecting a release, keep in mind the following definitions: * Maintenance Most heavily tested and highly recommended release of any label in a given row of the table. * Rebuild Constructed from the previous maintenance or major release in the same train, it contains the fix for a specific vulnerability. Although it receives less testing, it contains only the minimal changes necessary to effect the repair. Cisco has made available several rebuilds of mainline trains to address this vulnerability, but strongly recommends running only the latest maintenance release on mainline trains. * Interim Built at regular intervals between maintenance releases and receives less testing. Interims should be selected only if there is no other suitable release that addresses the vulnerability, and interim images should be upgraded to the next available maintenance release as soon as possible. Interim releases are not available through manufacturing, and usually they are not available for customer download from CCO without prior arrangement with the Cisco Technical Assistance Center (TAC). In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco TAC for assistance, as shown in the section following this table. +------------------------------------------------------------------------+ |Train |Description of |Availability of Fixed Releases | | |Image or Platform| | |------------------------+-----------------------------------------------+ | 11.x based releases | Rebuild |Interim| Maintenance | |------------------------+-------------+-------+-------------------------+ |11.1CA| |11.1(36)CA4**| | | |------+-----------------+-------------+-------+-------------------------+ |11.2 | |11.2(26e)** | | | |------+-----------------+-------------+-------+-------------------------+ |11.2P | |11.2(26)P5** | | | |------+-----------------+-----------------------------------------------+ |11.3 | |Not scheduled | |------+-----------------+-----------------------------------------------+ |11.3T | |Not scheduled | |------------------------+-----------------------------------------------+ |12.0 based releases |Rebuild |Interim|Maintenance | |------------------------+-------------+-------+-------------------------+ | |General | | | | |12.0 |Deployment | | |12.0(26) | | |release for all | | | | | |platforms | | | | |------+-----------------+-----------------------------------------------+ |12.0DA|xDSL support: |Migrate to 12.2DA; 12.2(10)DA2 - Aug-15-2003, | | |6100, 6200 |12.2(12)DA3 - Aug-22-2003: Engineering | | | |Specials available on request. | |------+-----------------+-----------------------------------------------+ |12.0DB|Early Deployment |Migrate to 12.3(1a) | | |6400 UAC for NSP | | |------+-----------------+-----------------------------------------------+ |12.0DC|Early Deployment |Migrate to 12.3(1a) | | |6400 UAC for NRP | | |------+-----------------+-----------------------------------------------+ | | |12.0(24)S2 | | | | | |12.0(23)S3 | | | | | |12.0(22)S5 | | | | | |12.0(21)S7 | | | | | |12.0(19)S4 | | | | |Core/ISP support:|12.0(18)S7 | | | |12.0S |GSR, RSP, c7200, |12.0(17)S7 | |12.0(25)S | | |c10k |12.0(16)S10 | | | | | |12.0(15)S7 | | | | | |12.0(14)S8 | | | | | |12.0(13)S8 | | | | | |12.0(12)S4 | | | | | |12.0(10)S8 | | | |------+-----------------+-----------------------------------------------+ |12.0SC|Cable/broadband |Migrate to 12.1(19)EC | | |ISP: ubr7200 | | |------+-----------------+-----------------------------------------------+ |12.0SL|100000 ESR:c10k |Migrate to 12.0(23)S3, **12.0(17)SL9 - | | | |Jul-15-2003 | |------+-----------------+-----------------------------------------------+ |12.0SP|Early Deployment |Migrate to 12.0(22)S5 | |------+-----------------+-----------------------------------------------+ | |Early Deployment |12.0(21)ST7 | | | |12.0ST|release for Core/|12.0(20)ST6 | | | | |ISP support: GSR,|12.0(19)ST6 | | | | |RSP, c7200 |12.0(17)ST8 | | | |------+-----------------+-----------------------------------------------+ |12.0SX|Early Deployment |Migrate to 12.0(22)S5 | |------+-----------------+-----------------------------------------------+ |12.0SY|Early Deployment |Migrate to 12.0(23)S3 | |------+-----------------+-----------------------------------------------+ |12.0SZ|Early Deployment |Migrate to 12.0(23)S3 | |------+-----------------+-----------------------------------------------+ |12.0T |Early Deployment |12.0(7)T3** | | | |------+-----------------+-------------+-------+-------------------------+ | |85xx ls1010 | | |12.0(26)W5(28) | | |-----------------+-------------+-------+-------------------------+ | |c5atm |12.0(24)W5 | | | | | |(26a) | | | | |-----------------+-------------+-------+-------------------------+ | |Cat4232 and |12.0(25)W5 | | | | |Cat2948G-L3 |(27) | | | |12.0W5|-----------------+-------------+-------+-------------------------+ | |C6MSM,C5rsfc, |Engineering | | | | |C5rsm, |Special | | | | | |available on | | | | | |request | | | | |-----------------+-------------+-------+-------------------------+ | |C3620, C3640, | | | | | |C4500, C7200, RSP| | | | |------+-----------------+-------------+-------+-------------------------+ |12.0WC|Early deployment |12.0(05)WC8 | | | | |2900XL-LRE,2900XL| | | | | |/3500XL; 2950 | | | | | |release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.0WT|Early deployment |Engineering | | | | |Catalyst |Special | | | | |switches: |Available | | | | |cat4840g, |upon request | | | |------+-----------------+-----------------------------------------------+ |12.0X |Shortlived Early |All 12.0X(any letter) releases have migrated to| |(l) |Deployment |either 12.0T or 12.1 unless otherwise | | |Releases |documented in the X release technical notes | | | |pertaining to the specific release. Please | | | |check migration paths for all 12.0X releases. | |------------------------+-----------------------------------------------+ |12.1 based releases |Rebuild |Interim|Maintenance | |------------------------+-------------+-------+-------------------------+ | |General | | | | |12.1 |Deployment | |12.1 |12.1(19) | | |release for all | |(18.4) | | | |platforms | | | | |------+-----------------+-----------------------------------------------+ |12.1AA| |Migrate to 12.2 | |------+-----------------+-----------------------------------------------+ |12.1AX|Catalyst 3750 |12.1(14)EA1 -| | | | | |Engineering | | | | | |special | | | | | |available | | | | | |upon request | | | |------+-----------------+-------------+-------+-------------------------+ |12.1AY|Catalyst 2940 | | |12.1(13)AY | |------+-----------------+-----------------------------------------------+ |12.1DA|6160 platform |Migrate to 12.2DA | |------+-----------------+-----------------------------------------------+ |12.1DB|6400 UAC |Migrate to 12.3(1a) | |------+-----------------+-----------------------------------------------+ |12.1DC|6400 UAC |Migrate to 12.3(1a) | |------+-----------------+-----------------------------------------------+ |12.1E |Core Enterprise |12.1(8b)E14 | |12.1(19)E | | |support - c7200, |12.1(13)E7 | | | | |Catalyst 6000, |12.1(14)E4 | | | | |RSP |**12.1(12c)E7| | | | | |12.1(11b)E12-| | | | | |Aug-4-2003 | | | | | |12.1(6)E12 | | | |------+-----------------+-----------------------------------------------+ |12.1EA|12.1(4)EA |Migrate to 12.1(13)EA1c | | |12.1(6)EA | | | |12.1(8)EA | | | |12.1(9)EA | | | |12.1(11)EA | | | |-----------------+-----------------------------------------------+ | |12.1(12c)EA |12.1(13)EA1c | | | | |12.1(13)EA | | | | |------+-----------------+-------------+-------+-------------------------+ |12.1EB|LS1010 | | |12.1(14)EB | |------+-----------------+-------------+-------+-------------------------+ |12.1EC|Early Deployment | | |12.1(19)EC (scheduled | | | | | |last week of July) | |------+-----------------+-------------+-------+-------------------------+ |12.1EV|Early Deployment | | |12.1(12c)EV | |------+-----------------+-------------+-------+-------------------------+ |12.1EW|Early Deployment | | |12.1(13)EW,12.1(19)EW | | |Cat4000 L3 | | | | |------+-----------------+-------------+-------+-------------------------+ |12.1EX|Early deployment |12.1(13)EX2 | | | |------+-----------------+-------------+-------+-------------------------+ |12.1EY| | |12.1(14)E4 | | | |------+--+--------------+-------------+-------+-------------------------+ |12.1YJ| | |12.1(14)EA1 -| | | | | | |Jul-28-2003 | | | |------+-----------------+-------------+-------+-------------------------+ |12.1T |Early deployment |12.1(5)T15** | | | |------+-----------------------------------------------------------------+ |12.1X |12.1X releases generally migrate to 12.1T, 12.2 or 12.2T as | |(l) |specified below. Please refer to specific train Technical notes | | |for documented migration path. | |------+-----------------------------------------------------------------+ |12.1XA|Short lived Early|Migrate to 12.1(5)T15 | | |Deployment | | | |Release | | |------+-----------------+-----------------------------------------------+ |12.1XC|Short lived Early|Migrate to12.2(17) | |12.1XD|Deployment | | |12.1XH|Releases | | |12.1XI| | | |------+-----------------+-----------------------------------------------+ |12.1XB|Short lived Early|Migrate to 12.2(15)T5 | |12.1XF|Deployment | | |12.1XG|Releases | | |12.1XJ| | | |12.1XL| | | |12.1XP| | | |12.1XR| | | |12.1XT| | | |12.1YB| | | |12.1YC| | | |12.1YD| | | |12.1YH| | | |------+-----------------+-----------------------------------------------+ |12.1XM|Short lived Early|Migrate to 12.2(2)XB11 | |12.1XQ|Deployment | | |12.1XV|Releases | | |------+-----------------+-----------------------------------------------+ |12.1XU|Short lived Early|Migrate to 12.2(4)T6 | | |Deployment | | | |Release | | |------+-----------------+-----------------------------------------------+ |12.1YE|Short lived Early|Migrate to 12.2(2)YC | |12.1YF|Deployment | | |12.1YI|Release | | |------------------------+-----------------------------------------------+ |12.2 based releases |Rebuild |Interim|Maintenance | |------------------------+-------------+-------+-------------------------+ | |General |12.2(16a) | | | |12.2 |Deployment (GD) |12.2(12e) | |12.2(17) | | |candidate for all|12.2(10d) | | | | |platforms | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2B |12.2(2)B-12.2(4) |12.3(1a) | | | | |B7 | | | | | |-----------------+-------------+-------+-------------------------+ | |12.2(4)B8-12.2 |12.2(16)B1 | | | | |(16)B | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2BC|Early Deployment |12.2(15)BC1 | | | | |Release |(Scheduled | | | | | |end of July) | | | |------+-----------------+-------------+-------+-------------------------+ |12.2BW|Early Deployment |Migrate to | | | | |for use with |12.3(1a) | | | | |7200, 7400, and | | | | | |7411 platforms | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2BX|Broadband/Leased | | |12.2(16)BX | | |line | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2BZ|Early Deployment |12.2(15)BZ1 | | | | |Release | | | | |------+-----------------+-----------------------------------------------+ |12.2CX|Early Deployment |Migrate to 12.1(15)BC1 | | |Release | | |------+-----------------+-----------------------------------------------+ |12.2CY|Early Deployment |Migrate to 12.1(15)BC1 | | |Release | | |------+-----------------+-----------------------------------------------+ |12.2DA|Early Deployment |12.2(10)DA2 -| | | | |Release |Jul-15-2003 | | | | | |12.2(12)DA3 -| | | | | |Aug-22-2003 | | | | | |Enginering | | | | | |Special | | | | | |available on | | | | | |request | | | |------+-----------------+-----------------------------------------------+ |12.2DD|Early Deployment |Migrate to 12.3(1a) | | |Release | | |------+-----------------+-----------------------------------------------+ |12.2DX|Early Deployment |Migrate to 12.3(1a) | | |Release | | |------+-----------------+-----------------------------------------------+ |12.2JA|Cisco Aironet | | |12.2(11)JA | | |hardware | | | | | |platforms: | | | | | |Introduction of | | | | | |Access Point | | | | | |feature in IOS, | | | | | |Cisco 1100 Series| | | | | |Access Point | | | | | |(802.11b) | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2MB|Specific |12.2(4)MB12 | | | | |Technology ED for| | | | | |2600 7500 (GPRS/ | | | | | |PDSN/GGSN | | | | | |2600/7200/7500) | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2MC|Early Deployment:|12.2(13)MC1 | | | | |IP RAN |CCO: 7/24/03 | | | |------+-----------------+-------------+-------+-------------------------+ |12.2MX| |12.2(8)YD | | | | | | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2S |Core/ISP support:|12.2(14)S1 |12.2 | | | |GSR, RSP, c7200 | |(16.5)S| | |------+-----------------+-------------+-------+-------------------------+ |12.2SX|IOS Support for |12.2(14)SX1 | | | | |C6500 Supervisor | | | | | |3 | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2SY|VPN feature |12.2(14)SY1, | | | | |release for c6k/ |12.2(8)YD | | | | |76xx VPN service | | | | | |module. | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2SZ|7304 Platform |12.2(14)SZ2 | | | |------+-----------------+-------------+-------+-------------------------+ | | |12.2(15)T4/ | |No more maintenance | | |New Technology |5,12.2(13)T5,| |trains for 12.2T are | |12.2T |Early Deployment |12.2(11) |12.2 |planned, please migrate | | |(ED) release for |T9,12.2(8) |(16.5)T|to latest 12.3 Mainline | | |all platforms |T10, | |release. | | | |12.2(4)T6 | | | |------+-----------------+-----------------------------------------------+ |12.2X |Short lived Early|Many short lived releases migrate to the same | |(l) |Deployment |train; the trains below this point until the | |12.2Y |Releases - |following section are not grouped by strict | |(l) | |alphabetical order, but are grouped by | | | |migration path. Please review documented | | | |migration paths for your trains. | |------+-----------------+-----------------------------------------------+ |12.2XA|Short lived Early|Migrate to 12.2(11)T9 | | |Deployment | | | |Releases | | |------+-----------------+-----------------------------------------------+ |12.2XS| |12.2(2)XB11 | |------+-----------------+-----------------------------------------------+ |12.2XD|Short lived Early|Migrate to 12.2(15)T5 | |12.2XE|Deployment | | |12.2XH|Releases | | |12.2XI| | | |12.2XJ| | | |12.2XK| | | |12.2XL| | | |12.2XM| | | |12.2XQ| | | |12.2XU| | | |12.2XW| | | |12.2YA| | | |12.2YB| | | |12.2YC| | | |12.2YF| | | |12.2YG| | | |12.2YH| | | |12.2YJ| | | |12.2YT| | | |------+-----------------+-----------------------------------------------+ | |Short lived Early| | |12.2YN|Deployment |Migrate to 12.2(13)ZH | | |Releases | | |------+-----------------+-----------------------------------------------+ | |Short lived Early|Migrate to 12.2(14)SY1 available Aug-4-2003: | |12.2YO|Deployment |Engineering Special available on request | | |Releases | | |------+-----------------+-----------------------------------------------+ | |Early Deployment | | | | |12.2XB|Release with |12.2(2)XB11 | | | | |continuing | | | | | |support | | | | |------+-----------------+-----------------------------------------------+ |12.2XC|Short lived Early|Migrate to 12.2(16)B1 | | |Deployment | | | |Releases | | |------+-----------------+-----------------------------------------------+ |12.2XF|Short lived Early|Migrate to 12.2(15)BC1 | | |Deployment | | | |Release UBR10000 | | |------+-----------------+-----------------------------------------------+ |12.2XG|Short lived Early|Migrate to 12.2(8)T10 | | |Deployment | | | |Release | | |------+-----------------+-----------------------------------------------+ |12.2XN|Short lived Early|Migrate to 12.2(11)T9 | |12.2XT|Deployment | | | |Releases | | |------+-----------------+-----------------------------------------------+ |12.2YD|Short lived Early|Migrate to 12.2(8)YY | | |Deployment | | | |Release | | |------+-----------------+-----------------------------------------------+ | |Short lived Early| | | | |12.2YP|Deployment |**12.2(11)YP1| | | | |Release | | | | |------+-----------------+-----------------------------------------------+ |12.2YK| |Migrate to 12.2(13)ZC | |------+-----------------+-----------------------------------------------+ |12.2YL|Short lived Early|Migrate to 12.2(13)ZH | |12.2YM|Deployment | | |12.2YU|Releases | | |12.2YV| | | |------+-----------------+-----------------------------------------------+ |12.2YQ|Short lived Early|Migrate to 12.2(15)ZL | |12.2YR|Deployment | | | |Releases | | |------+-----------------+-----------------------------------------------+ |12.2YS|Short lived Early|12.2(15)YS/ | | | | |Deployment |1.2(1) | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2YW|Short lived Early|12.2(8)YW2 | | | | |Deployment | | | | | |Releases | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2YX|Short lived Early|12.2(11)YX1 | | | | |Deployment | | | | | |Release | | | | | |Crypto for 7100/ | | | | | |7200 | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2YY|Short lived Early|12.2(8)YY3 | | | | |Deployment | | | | | |Releases | | | | | |IOS support for | | | | | |General Packet | | | | | |Radio Service | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2YZ|Short lived Early|12.2(11)YZ2 | | | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZA|Short lived Early| | |12.2(14)ZA2 | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZB|Short lived Early|12.2(8)ZB7 | | | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZC|Short lived Early| | |12.2(13)ZC | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZD|Short lived Early|Not Scheduled| | | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZE|Short lived Early|12.3(1a) | | | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZF|Short lived Early|Not | | | | |Deployment |Vulnerable | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZG|Short lived Early|Not | | | | |Deployment |Vulnerable | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZH|Short lived Early|Not | | | | |Deployment |Vulnerable | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZJ|Short lived Early|12.2(15)ZJ1 | | | | |Deployment | | | | | |Release | | | | |------+-----------------+-------------+-------+-------------------------+ |12.2ZL|Short lived Early|Not | | | | |Deployment |Vulnerable | | | | |Release | | | | |------------------------+-----------------------------------------------+ |12.3 based releases |NOT VULNERABLE | |------------------------------------------------------------------------+ |Notes: **Marked versions of code are not available on CCO. Please | |contact TAC and request the specific images you need posted. | +------------------------------------------------------------------------+ Notes: ** Marked versions of code are not available on CCO. Please contact the Cisco TAC and request the specific images you need posted. Obtaining Fixed Software ======================== Customers with contracts should obtain upgraded software free of charge through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on the Cisco worldwide website at http://www.cisco.com/tacpage/sw-center/sw-ios.html. Customers whose Cisco products are provided or maintained through prior or existing agreement with third-party support organizations such as Cisco Partners, authorized resellers, or service providers should contact that support organization for assistance with obtaining the free software upgrade(s). Customers who purchase direct from Cisco but who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows. * +1 800 553 2447 (toll free from within North America) * +1 408 526 7209 (toll call from anywhere in the world) * e-mail: tac(a)cisco.com Please have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC. Please do not contact either "psirt(a)cisco.com" or "security-alert(a)cisco.com" for software upgrades. See http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special localized telephone numbers, instructions, and e-mail addresses for use in various languages. Workarounds =========== AFTER APPLYING THE WORKAROUND the input queue depth may be raised with the hold-queue <new value> in interface command -- the default size is 75. This will allow traffic flow on the interface until the device can be reloaded. Cisco recommends that all IOS devices which process IPv4 packets be configured to block traffic directed to the router from any unauthorized source with the use of Access Control Lists (ACLs). This can be done at multiple locations, and it is recommended that you review all methods and use the combination which fits your network best. Legitimate traffic is defined as management protocols such as telnet, snmp or ssh, and configured routing protocols from explicitly allowed peers. All other traffic destined to the device should be blocked at the input interface. Traffic entering the network should also be carefully evaluated and filtered at the network edge if destined to an infrastructure device. Although network service providers must often allow unknown traffic to transit their network, it is not necessary to allow that same traffic destined to their network infrastructure. Several white papers have been written to assist in deploying these recommended security best practices. ACLs can have performance impact on certain platforms, so care should be taken when applying the recommended workarounds. Receive ACLs For distributed platforms, receive path access lists may be an option starting in Cisco IOS software versions 12.0(21)S2 for the c12000 and 12.0 (24)S for the c7500. The receive access lists protect the device from harmful traffic before the traffic can impact the route processor. The CPU load is distributed to the line card processors and helps mitigate load on the main route processor. The white paper entitled "GSR: Receive Access Control Lists" will help you identify and allow legitimate traffic to your device and deny all unwanted packets: http://www.cisco.com/warp/customer/707/racl.html Infrastructure ACLs Although it is often difficult to block traffic transiting your network, it is possible to identify traffic which should never be allowed to target your infrastructure devices and block that traffic at the border of your network. The white paper entitled "GSR: Receive Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection ACLs: http://www.cisco.com/warp/customer/707/iacl.html Transit ACLs The two techniques described above protect infrastructure devices. This IP protocol ACL can also be used to filter transit traffic passing through a network. The ACL will need to permit all protocols used by end users, not just those destined to routers. Since end users can run a wide array of protocols, often unexpected or uncommon protocols, these protocol requirements must be well understood prior to deploying this ACL. The provided list is not a complete list of permissible protocols. This access-list is applied inbound on edge facing interfaces. For complete protection this access-list needs to be implemented on the edge router. For basic TCP,UDP and ICMP, the following ACL will provide protection: access-list 101 permit tcp any any access-list 101 permit udp any any !! GRE tunnel if required access-list 101 permit gre any any !! IPSec ESP if required access-list 101 permit esp any any !! IPSec AH if required access-list 101 permit ah any any access-list 101 permit icmp any any access-list 101 deny ip any any The last statement of the Transit ACL should be a deny any any for IP traffic. Prior to deploying ACLs that filter transit traffic, a classification ACL can be used to help identify required permit statements. A classification ACL is an ACL that permits a series of protocols. Displaying access-list entry hit counters helps determine required protocols: entries with zero packets counted are likely not required. Classification access-lists are detailed in the above link for infrastructure access-lists. Exploitation and Public Announcements ===================================== The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerabilities described in this advisory. If PSIRT becomes aware of any sign of public announcement of the crafted packet, or there is any sign of exploitation of this vulnerability, a follow-up announcement will be sent to our standard distribution list immediately with further details to assist network administrators in mitigation. Status of This Notice: INTERIM ====================== This is an INTERIM notice. Although Cisco cannot guarantee the accuracy of all statements in this notice, all of the facts have been checked to the best of our ability. Cisco does not anticipate issuing updated versions of this advisory unless there is some material change in the facts. Should there be a significant change in the facts, Cisco will update this advisory. Distribution ============ This notice will be posted on the Cisco worldwide website at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml at 21:00 GMT on July 17th, 2003. In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and will be posted to the following e-mail and Usenet news recipients at the public release date and time: * cust-security-announce(a)cisco.com * bugtraq(a)securityfocus.com * full-disclosure(a)lists.netsys.com * first-teams(a)first.org (includes CERT/CC) * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * nanog(a)merit.edu * sanog(a)sanog.org * comp.dcom.sys.cisco * Various internal Cisco mailing lists Future updates of this advisory, if any, will be placed on the Cisco worldwide web server. Users concerned about this problem are encouraged to check the URL given above for any updates. Revision History ================ +-------------------------------------------+ | Revision | 17-July-2003 | Initial public | | 1.0 | 0:00 GMT | release | +-------------------------------------------+ Cisco Security Procedures ========================= Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on the Cisco worldwide website at http://www.cisco.com/warp/public/707/sec_incident_response.shtml. This includes instructions for press inquiries regarding Cisco security notices. All Cisco Security Advisories are available at http://www.cisco.com/go/psirt. - -------------------------------------------------------------------------- This notice is Copyright 2003 by Cisco Systems, Inc. This notice may be redistributed freely after the release date given at the top of the text, provided that redistributed copies are complete and unmodified, and include all date and version information. - -------------------------------------------------------------------------- All contents are Copyright © 1992-2003 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQA/AwUBPxYP5XsxqM8ytrWQEQJOfwCg04JnuUYEIYQZyfHAeClX5p2SpngAoNMn t2zHq5JVCmsChl0DrSN9jMFq =6bis -----END PGP SIGNATURE-----

1 0

NetForum 2003
by Geoff Cant 16 Jul '03

16 Jul '03

Hi there, I'd like to thank the organisers and all the nznog people who attended NetForum2003 for being really interesting and friendly - I had a great time. Despite being one of the few students there (I was from Massey PN) everyone was amiable and great to talk to. I'd especially like to thank Joe Abbley for his immensely interesting and funny BGP presentations, and Barry Greene and Evi Nemeth for their informative (and scary - 98% rubbish at root-servers) sessions. Thanks very much guys, much looking forward to NetForum 2004 -- Geoff Cant <geoffrey.cant.1(a)uni.massey.ac.nz> (I hope the above didn't sound too gushy, but I really did have a great time :)

5 4

Apologies for 'Test' email
by Tim John 16 Jul '03

16 Jul '03

Hi people, I sent a test message to a customers account yesterday (which had nothing to do with NZNOG), but unfortunately it ended up here. Not sure what the problem was, but putting it down to chubby fingers .... For those who didn't ignore it, please do :) Tim DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

RE: [nznog] IPv6
by Chris Hellberg 15 Jul '03

15 Jul '03

when I was running the v6ix in Wellington I was running EBGP sessions with most people who had connections; seemed to work well when I had a bunch of open-souce software mirrors which were v6-accessible and people had routes that went straight to the IX. There was also tunnel to the 6bone at Merit, for those who wanted to have a nosey at the 6bone routing table, although there were some 2000::/24 prefixes on the 6bone. I've talked to Si at Citylink about getting a PI peering block for WIX and APE, but it wasn't a huge priority. I used addresses from a freenet allocation and carved up a /64 in to a bunch of /126s and used them as point-to-point links. Not the best solution in the world, but worked for the purpose. -----Original Message----- From: perry(a)deeper.co.nz [mailto:perry(a)deeper.co.nz] Sent: Wednesday, 16 July 2003 21:43 To: Joe Abley Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv6 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > You can't plumb tunnels right now, today? Or is the problem that > there's just no local place to plumb a tunnel to? > > (see http://ipv6tb.he.net/ for a tunnel broker run by clueful people in > the US). ahh, but tunnels to the US mean that you have the irritating problem that pinging someone on the same ISP as you can give you up to 3,000ms of latency as it transits from here to the US and back again. You have issues when they are overloaded, or down. You have issues if the internet between here and there decides that packets should be routed via darkest peru. IPv6 was designed to work in the situation where you have to bridge large IPv4 clouds. A much better solution for people in New Zealand is to use 6to4 addressing, especially if you're on the end of ADSL or similar and don't have native transport. 6to4 addressing means that whatever device(s) have non-RFC1918 IPv4 addresses can have a /48 assigned to them. 2003:<high two octets of IPv4 address>:<low two octets of IPv4 address>::/48. To route to another 2002::/16 address over IPv4 you just take the packet, encapsulate it in IPv4, and send it to the embedded IPv4 address. Linux and FreeBSD both support this. Latency to other 6to4 addresses is about the same as IPv4, avoiding the entire US round trip. To talk from a 6to4 address to a non-6to4 IPv6 address you route via ::192.88.99.1 which is an AnyCast address. Unfortunately, last time I looked the nearest 192.88.99.1 AnyCast announcement appeared to be in Germany. Is there any chance of someone putting forward 6to4 anycast gateway in the APE and/or the WIX? Of course the problem here is that probably 50% of it's traffic will be international. In an unrelated note, the MetaNet has been used by several people in NZ who are interested in playing around with more interesting networks without breaking things that people pay to use. We use it for peering IPv6 without having to go via the US and we'd be interested in organising IPv6 tunnels with like minded people (either using wand, gre, or 6in4 tunnels) Unfortunately the MetaNet wouldn't handle multicast very well (or we'd be having a good tinker with it) Resources: * http://www.wlug.org.nz/DancingPenguin (A IPv6 enabled website in New Zealand which is useful for testing with) * http://www.wlug.org.nz/IPv6LessonsLearnt (For some random things we've discovered about IPv6 the hard way, so you don't have to) * http://www.wlug.org.nz/6to4 (Information about 6to4 under Linux) * http://www.wlug.org.nz/IPv6 (Information about IPv6 on the wiki) * http://www.nevada.net.nz/~pmurray/6to4.html (6to4 under FreeBSD) If you want to chat about it, we're usually hanging around in #wlug on Undernet. irc://undernet/%23wlug - -- <f00Dave> Look, rejects, this is #OpenGL, not #GEEKSEX. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Only when you are sure they have you, can you stop being paranoid iD8DBQE/FQ0TcAgRpy8z8UQRAhadAJ4gAGn+YRABqt6A7X58K73hBQPNugCgy3ie 05qO9xRxAXyaG1K5EElVfAY= =+lkH -----END PGP SIGNATURE----- _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you." ------------------------------------------------------------------------------

1 0

dns and routing slides
by Joe Abley 15 Jul '03

15 Jul '03

The DNS slides I used to talk about DNS, TSIG, DNSSEC and reverse DNS can be found here: http://www.isc.org/misc/nznog/01-Introduction.ppt http://www.isc.org/misc/nznog/06-Reverse.ppt http://www.isc.org/misc/nznog/07-dnssec.ppt The cisco slides I occasionally referred to whilst waving my hands about BGP can be found here: ftp://ftp-eng.cisco.com/pfs/isp-workshops/studentcd-2003a/ Workshop_Materials The whiteboard scribblings and frequent rambling tangents were fortunately not recorded for posterity, but an air ticket and a nominal amount of beer can easily secure a repeat performance :) Joe

1 0

Test
by Tim John 15 Jul '03

15 Jul '03

This is a test. Please ignore .... Tim DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

Live Webcast - Meet instructors of Certificate In Web-based Instruction offered by Simon Fraser University
by Abigail 15 Jul '03

15 Jul '03

On July 30th at 1100 hrs Pacific Time (GMT 08:00) there will be a Webcast featuring the instructors of the Certificate in Web-Based Instruction (CWI). Participants of the Webcast can interact with the instructors and ask questions about this program. The CWI program gives you the tools and knowledge necessary to design, develop and deliver web-based courses or add online components to classroom teachings. If you are unable to make it to this live presentation at the above date then you can attend one of the following alternative dates: Wednesday, August 20 at 1100 hrs Pacific Time (GMT 8:00) or Wednesday, September 3 at 1100 hrs Pacific Time (GMT 8:00). Please register to participate in the live Webcast by visiting http://www.sfu.ca/lidc/telestraining. Abby Dy Communications Specialist Certificate in Web-Based Instruction Tel: 604-806-5156 ady(a)sfu.ca

1 0

RE: [nznog] Anyone thinking about WiMAX?
by Matthew G Brown 12 Jul '03

12 Jul '03

New Zealand regulatory bodies are trying to put us more in line with the US FCC standards. So I should not see to much of a problem,. 5.8 & 5.3ghz are virtually self managed by users as it is. I have several cases at the moment of other people using the Uncertified and darn right HORRIBLE! 2.4/5.8 Up.Down converters in areas turning the spectrum in to "Flip the coin for a channel" . But it's a matter if people been sensible and maybe we can take some more control over our own spectrum. Some where I have papers outlinig this, Off list of anyone wants Helen Clarkes peoples dribble on the matter. Best Regards Matthew G Brown Managing Director B & R Holdings LIMITED Nelson, New Zealand Ph: 027 4807731 Http://www.brh.co.nz -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Friday, 11 July 2003 9:38 a.m. To: Matthew G Brown Subject: RE: [nznog] Anyone thinking about WiMAX? On Thu, 10 Jul 2003, Matthew G Brown wrote: > We had a meeting on this at CeBit Sydney. I was not aware that the > IEEE had ratified the standard at the time. There is plenty of talk > about it in isp-wireless news groups over the last few months. Proxim > and Alvarion are defiantly working on 802.16 at the moment. > > The issue lies with me that if your not after the QOS and control > features then why not just go buy Redline off the shelf, $20,000 for > 55mb over 40 miles is cheap buying. > > Im going to keep following this standard for the fact it can be > developed over a combination of frequencies. Ideally 3.5ghz .... FYI > people considering 3.5ghz should keep in Mind that Alvarion ( Formally > Breezecom ) have been producing 3.5ghz equipment for there local > market for 10 years. Infact the BAII & BreezeAcess series are all > avail at 3.5ghz. Good news for Rural Broadband people > > </rant, less coffee> More coffee... it's morning. Although the 802.16a stuff is pricey at the moment (they're talking US$1,000 for customer "modems") it could be very interesting for providers looking to bypass the local loop stranglehold. Not just for the rurals, in other words. Here's hoping someone else than Walkers will try to deploy in Auckland. I wonder if there are any radio frequency spectrum issues here though? Redline's AN-50 looks like it delivers the same performance -- 72Mbps, up to 80km range... only 49Mbps "at the Ethernet level" though. -- Juha Saarinen

1 0

NetForum 2003
by Tim John 12 Jul '03

12 Jul '03

Hi Roger, Just a quick word of thanks for a most enjoyable couple of days in Auckland during the NetForum conference. Please pass on my thanks to Sue and all the others who worked hard to make it happen this year. I would also like to thank all those who contributed their time by giving presentations during the Thursday and Friday I was there. I didn't catch all the presentations, but the ones I did see were great. BTW, on the flight back to Wellington, I attempted to get into the cockpit and show the pilot what I had learned from the Flight Sim. presentation, but was promptly refused :) Thanks again, Tim DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

1 0

ISC F root nameserver node live at APE
by Joe Abley 11 Jul '03

11 Jul '03

APE Peering People, Internet Software Consortium has a node of the F root nameserver at the APE in Auckland. Networks connected to the APE can gain access to this node by peering with it across the exchange, as follows: APE addresses: 192.203.154.98, 192.203.154.99 AS number: 23710 NOC phone: +1 650 423 1310 INOC DBA: 3557 NOC e-mail: noc(a)isc.org The APE path to F will also be available through the APE route servers. Networks peering locally with F gain lower transport latency and increased path diversity to the F root nameserver, which helps make the DNS as a whole more reliable. ISC operates an open peering policy. To set up a session please send e-mail to peering(a)isc.org. The F root nameserver node in Auckland advertises the single prefix 192.5.5.0/24 to peers which covers the address of f.root-servers.net. For further details of the general routing policy for F, together with a summary of remote F-root nodes deployed at other exchange points, see: http://www.isc.org/peering/ A representation of the policy for the F-Root node in Auckland is present in the IRR. The Auckland F root nameserver node was made possible by Juniper Networks, TelstraClear, FX Networks and 2day.com. Joe

2 1

usenet.net.nz offline.
by Simon Lyall 10 Jul '03

10 Jul '03

Just a quick FYI but usenet.net.nz is currently offline due to dodgy hardware, this means that the noc contact list, ape website and my looking glass (onlong with random other stuff) is offline. I'll kick the box tomorrow and I have a replacement machine ready, hopefully I'll have a chance to config it up in the next couple of days. -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | Postmaster | Home: simon(a)darkmere.gen.nz Ihug Ltd, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz

1 0

Anyone thinking about WiMAX?
by Juha Saarinen 09 Jul '03

09 Jul '03

www.wimaxforum.org Roundabout 50km reach, with 70Mbps max rate. -- Juha Saarinen

2 1

legal threats from DE Technologies re web commerce
by Robert Hunt 09 Jul '03

09 Jul '03

James & Wells NZ Barristers and Solicitors (http://www.jaws.co.nz) are acting for DE Technologies ( http://www.detechnologies.com ) DE Technologies are described at http://www.globetechnology.com/servlet/GAMArticleHTMLTemplate?tf=globetechn… as "a tiny company in Montreal" and the patent as "a computer implemented process for carrying out an international commercial transaction." I hope this is not seen as off topic. I am at a loss to say whether this is an absurdity or a significant worry, but my firm has recently received a legal fax from James & Wells claiming we are infringing DE Technologies recently acquired NZ Patent. In what looks like a mass produced demand they appear to require that we "discuss" obtaining a license for three years for US $25,000 plus 1.15% of our and our customers' transactions, if we wish to continue hosting web sites that take international orders. The NZ version of the patent was obtained earlier this year. Curiously the target of their attention happens to be a website of ours that does not do actual orders itself but is just a portal, hence my guess that this is part of an broad initial salvo in an attempt to create the "pay up and avoid litigation" response. I want to make contact with other operations who have received a license and royalty demand under NZ Patent 505284 for large sums of money if they wish to continue using basic international web shopping practices. We can probably deflect the particular letter we have received, however if the barristers involved are keen to search out sites that do have some chance of coming under the patent then they should find a virtual cornucopia, as they traverse the sites of your customers and ours. Supposing they succeed in upholding their patent then their requirements would claim a significant percentage of overheads of net traders looking to continue having international ordering/transaction capabilities. Obviously I am sorely disappointed that the NZ Patent Office is granting patents of this kind, and am reviewing both political and legal options for raising this issue in the public eye. Alongside Microsoft's moves to patent .Net APIs we are of course, seeing some serious challenges to developer freedoms, and end user's integration choices, if the arena of intellectual patents is not balanced with concern for open standards in at least some of the world. Well that is off topic now I am sure... I am happy to set up a list for discussing this issue if anyone else is interested, let me know or point me to a pre-existing nz list on this matter. Oh and I'll let you know when I have a patent on the process of running an online charity auction to save ISPs sued by patent attorney's.. :) regards Robert -- Robert Hunt phone +64-3-3645888 Managing Director fax +64-3-3645828 Plain Communications roberth(a)plain.co.nz

7 9

Effective RBL's
by Matthew G Brown 09 Jul '03

09 Jul '03

Does anyone have experience with good RBL's . A client is running Mdaemon and looking to increase the level of SPAM protection. By Default its running relays.osirussoft.com, relays.ordb.com & bl.spamcop.net Anyone have any others that function well ? Best Regards Matthew G Brown Managing Director B & R Holdings LIMITED Nelson, New Zealand Ph: 027 4807731 Http://www.brh.co.nz

5 5

Re: [nznog] Xtra supporting Address harvesting and prompting customers to embed HTML in their e-mail ?
by Malcolm Lockyer 08 Jul '03

08 Jul '03

>From: Steve Phillips <steve(a)focb.co.nz> >To: nznog(a)list.waikato.ac.nz >Subject: [nznog] Xtra supporting Address harvesting and prompting customers >to embed HTML in their e-mail ? >Date: Wed, 09 Jul 2003 14:33:39 +1200 >MIME-Version: 1.0 > >*sigh* <quote> To turn on HTML in your Outlook/Outlook Express On the Tools menu, click Options, and then click the Mail Format tab if on Outlook or the Send tab if on Outlook Express. </quote> (read: turn on the vulnerabilities) Its disturbing to see big companies trying to undo all our customer educating (read: using a cluestick) - it doesn't even meantion why us big government/IT Department/whatever types (read: those of us with a cluestick) don't like HTML mail..! I'd like to see anybody that can figure out how to apply the new crimes bill to spammers - to also use it against companies with pages like this to sort it out - <quote>Start getting everyone's email address now - in every way you can. </quote> *sigh* back to reality. // gets out the flameproof jacket ;) m > >http://xtramsn.co.nz/business/0,,10271-2468719,00.html > >No wonder we have such problems with spam and e-mail worms... > >-- >Steve. > >_______________________________________________ >Nznog mailing list >Nznog(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog _________________________________________________________________ Check out the Xtra gaming servers at http://xtramsn.co.nz/gaming !

1 0

Re: [nznog] Multicast status in New Zealand
by Ewen McNeill 08 Jul '03

08 Jul '03

In message <5.2.0.9.0.20030709102145.00b81700(a)pele.citylink.co.nz>, Richard Nayl or writes: >Don't get me wrong, I'm not anti-multicast. I agree its the most efficient >way of distributing a synchronous event. Its just I don't see a lot of >synchronous events...... Which brings me back to where I started -- with a bit of relaxation of the "I must see it NOW" requirement (in the order of a few seconds/minutes) and good client software/hardware, you can turn a bunch of not-quite-synchronous viewings into synchronous events. And thus snatch a multicast win, out of the jaws of a watch-now unicast defeat. This is both with "live" things -- which I agree aren't that common -- and also "near release time" viewings of things which aren't live (where you can expect that something which is recently released, and popular, is most likely to be wanted nearer the release time than later, in some sort of half-bell-curve type model). >Its just as the size of "live" viewer base gets smaller, and bandwidth >higher, multicasting doesn't seem worth the effort. Well I've seen approximately three orders of magnitude (powers of 10) drop in the cost of bandwidth/traffic over the last 10 years or so, and it's still at least two to three orders of magnitude away from the point where I'd be willing to say the "cost" of getting multicasting going isn't worth the value of the saved bandwidth. Generally like RAM space, harddrive space, etc, the uses will expand to fill all the available bandwidth, so using it inefficiently isn't exactly desireable. >If I stream an event for say 10 viewers, why should the rest of the >NZ net get it sent to them without asking for it. Umm, that's not how multicasting works (indeed it's the key difference between multicasting and broadcasting). But I think you know that already. Ewen

4 3

Xtra supporting Address harvesting and prompting customers to embed HTML in their e-mail ?
by Steve Phillips 08 Jul '03

08 Jul '03

*sigh* http://xtramsn.co.nz/business/0,,10271-2468719,00.html No wonder we have such problems with spam and e-mail worms... -- Steve.

1 0

Re: [nznog] legal threats from DE Technologies re web commerce
by David Farrar 08 Jul '03

08 Jul '03

Robert Hunt wrote: > Obviously I am sorely disappointed that the NZ Patent > Office is granting patents of this kind, and am reviewing > both political and legal options for raising this issue in > the public eye. Alongside Microsoft's moves to patent > .Net APIs we are of course, seeing some serious challenges > to developer freedoms, and end user's integration choices, > if the arena of intellectual patents is not balanced with > concern for open standards in at least some of the world. > > Well that is off topic now I am sure... I am happy to > set up a list for discussing this issue if anyone else is > interested, let me know or point me to a pre-existing nz > list on this matter. The issue came up yesterday on InternetNZ's public-discuss list. Archives at http://listserver.internetnz.net.nz/pipermail/public-discuss/2003-July/thre… and list at http://listserver.internetnz.net.nz/mailman/listinfo/public-discuss InternetNZ is considering engaging a QC who is an expert in the intellectual property arena to provide some initial advice on the situation which has arisen. No decision has been taken yet, but InternetNZ would be interested in hearing from anyone else who may be affected by this. At a minimum I am sure we will be happy to help co-ordinate information sharing. DPF (VP and Chair of Legal & Regulatory, InternetNZ)

1 0

Re: [nznog] Netsites Domain Name Changes page offline?
by Ewen McNeill 08 Jul '03

08 Jul '03

In message <Pine.LNX.4.44.0307081250150.6688-100000(a)blue.darkmere.gen.nz>, Lin N ah writes: >On Mon, 7 Jul 2003, Mark Davies wrote: >> [Mark's netsite changes list] >> I got asked on 1 July by Nick Griffin to not publish the changes list until >> some review I wasn't aware of that is apparently currently happening was >> completed. >> >Perhaps the DNC should explain to us why there is a problem with >Mark's excellent netsites page. The explanation I was given was that apparently some spammers had been trawling through the list of new domains to figure out what to look up to pick up a new collection of registrar/registrant/admin/technical contact addresses to spam. Apparently at least one spammer actually claimed to have used Mark's changes list as a source, which is presumably why the interium action was to ask for it to be taken down. As Steven Heath noted, there is a mention in the June Registrar newsletter; and it will be in the minutes from the June NZOC meeting which should be up RSN I'm told (apparently they were overlooked for a while in amongst everything else going on and now just need to be reviewed by NZOC for accuracy). And there should be some sort of call-for-comments coming out relatively soon (sometime in July?). >Is it doing any harm or is it because it isn't published by DNC and so >not sanctioned? Actually as I remember it Mark's site was one of the few that made it onto the original blessed list of those who could still do zone transfers when restrictions were put in place (a couple of years back). AFAICT it's merely the "source of addresses for spam" problem which makes it an issue, rather than "not run by the DNC". Ewen

2 1

RE: [nznog] Effective RBL's
by Michael Bordignon 08 Jul '03

08 Jul '03

> Does anyone have experience with good RBL's . A client is > running Mdaemon and looking to increase the level of SPAM > protection. By Default its running relays.osirussoft.com, > relays.ordb.com & bl.spamcop.net Anyone have any others that > function well ? I use these with exim: rbl_domains = relays.ordb.org/reject:list.dsbl.org/reject:relays.osirusoft.com/warn:blackh oles.easynet.nl\ /reject:bl.spamcop.net/reject:blackholes.five-ten-sg.com/warn Michael

1 0

RE: [nznog] Crimes Amendment Bill No 6 Now Law
by Donald Neal 08 Jul '03

08 Jul '03

> From: Gordon Smith [mailto:gordon(a)morenet.net.nz] > Sent: Wednesday, 9 July 2003 07:47 > To: Donald Neal; nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Crimes Amendment Bill No 6 Now Law > > > Even when its particularly relevant to network operations? > Like it or not, this is something that does affect our operations. Discussion of operational effects of a new law, based on knowledge of contents of that law - in. Discussion of what might be in that law - generally out. Sysadmins and network engineers seeking to give their opinions of interpretation of an Act - especially bad idea. - Donald Neal List Administrator > > -----Original Message----- > > From: Donald Neal [mailto:Donald.Neal(a)telecom.co.nz] > > Sent: Tuesday, 8 July 2003 3:42 PM > > To: nznog(a)list.waikato.ac.nz > > Subject: RE: [nznog] Crimes Amendment Bill No 6 Now Law > > > > > > Let's just bear in mind that postings of a legal nature are > > discouraged on this list. > > > > - Donald Neal > > List Administrator > ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

1 0

RE: [nznog] Multicast status in New Zealand
by Michael Sutton 08 Jul '03

08 Jul '03

Point of Technical peturbance Multicast is much more efficient. The data does not flood to every router in New Zealand. Actual data, just like unicast, only routes to those branches of the network where there is actual demand at that instance in time. If there is no downstream client application (player) requesting the data feed, no data will be sent to that location. The only data held by routers is information about the identity of the upstream multicast source, if there is client request. If the demand was only in Wellington the multicast data would not leave Wellington. When someone joins in Auckland then the data would flow to Auckland and no-where-else... When the Auckland users ceases the session data transfer would be pruned back to Wellington while the multicast session continues. Regards Michael Sutton http://www.internetnz.co.nz/members/by-elections/030619byelection.html http://www.internetnz.co.nz/biographies/bio03-msutton.html -----Original Message----- From: Richard Naylor [mailto:richard.naylor(a)citylink.co.nz] Sent: Wednesday, July 09, 2003 10:40 To: Ewen McNeill; Hamish MacEwan Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Multicast status in New Zealand Its just as the size of "live" viewer base gets smaller, and bandwidth higher, multicasting doesn't seem worth the effort. If I stream an event for say 10 viewers, why should the rest of the NZ net get it sent to them without asking for it. rich _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] Multicast status in New Zealand
by Michael Sutton 08 Jul '03

08 Jul '03

I agree with your take on the issue, Ewen... Further, it is surely in the "National Interest" that multicast be in active operational capability today for the "Public Internet" so that in the event of a future national crisis such as a SARS, Foot and Mouth, Small Pox or when a similar situation occurs the facility can be used to its best technical advantage. It is then important to: communicate, instruct & train, professionals and the public - while reducing close personnel contact. Multicast can be used to provide "low cost" high quality content injection which of itself does not cause degradation of New Zealand network performance at any location during a strategic performance window. Alternatives such as Consumer Digital Satellite TV would cost, at list prices, significant dollars to open up spot channels for a period of days || weeks || months, and in such circumstances the Ministries available discretionary funds would be under severe pressure, and therefore may be excluded as a viable option. However, multicast would help, as the cost of 48hours digital satellite television broadcast might equate to the cost of one years multicast distribution @ 300kbs. During the SARs containment emergency, Beijing and other locations in China closed schools and other education institutions and made children stay home. Their schools used telephones and the Public Internet to conduct distance learning. What would happen in New Zealand if all schools in Auckland and other city locations closed. Multicast was also used to connect SARS support hubs in Asia. Therefore prior to such an emergency, operational multicast services today would enable strategic content provider organisations to distribute current operational materials for capture and/or real-time display and be prepared and confident that such a system can be relied on as a front-line communication capability. So... reliable operation today ensures access when Noah needs an Ark... Nobody will try to implement it the day a Balloon goes UP... Hope you are all having a great conference... Is Joe warbling now... Best Regards Michael Sutton InternetNZ By-election Candidate - Councillor Vote now :) (disgraceful lobby) http://www.internetnz.co.nz/members/by-elections/030619byelection.html http://www.internetnz.co.nz/biographies/bio03-msutton.html -----Original Message----- From: Ewen McNeill [mailto:ewen(a)naos.co.nz] Sent: Tuesday, July 08, 2003 10:06 To: Hamish MacEwan Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Multicast status in New Zealand <snip> It does, however, seem to me rather counter productive to insist that they must use unicast, must use the bandwidth inefficiently, in order to some how deter this. At best all that's likely to achieve is that there's even less bandwidth available for other things. (Witness allocations of the frequency spectrum to radio, TV, etc, and what's left for ham radio operators.) And to make it even harder for "small operators" to join in -- so bang goes your online equivilent of public access TV (it's just too expensive to get a pipe big enough to unicast it to a reasoanble audience). <snip>.... Indeed. And that survives partly because many people "need" to be at work at the same time, which is largely true because of network effects (eg, you'd like the cafe to be open when you want to get morning tea, and people need to be in the same place at the same time for meetings, etc). And in the same way when something "interesting" happens lots of people are going to "need" to see it at once, if only to keep up with the Jones and be able to talk about it at morning tea the next day. To use your earlier analogy providing more buses/trains/etc can help to reduce this congestion. And in the same way multicasting can help reduce the congestion. But apparently buses/trains/etc are good, and multicasting is bad, for reasons I don't follow.

1 0

Re: [nznog] Multicast status in New Zealand
by Ewen McNeill 08 Jul '03

08 Jul '03

In message <20030708092651.GM4808(a)stuckist.macewan.gen.nz>, Hamish MacEwan writes: >On Sat, Jun 28, 2003 at 13:05 +1200, Ewen McNeill wrote: >> In message <5.2.0.9.0.20030627160856.02023200(a)pele.citylink.co.nz>, Richard Naylor writes: >> >ah - its that word "channel" that I don't see in the future. Such a >> >dated concept. >> >> Ah. Channels are double-plus-ungood. Call it a stream if it makes >> you feel happier. Or VDC or whatever. > >I think Rich's point is broader than "channels," it goes to the notion >of "broadcast," which, while like most things is not going to go away >anytime soon, but the option of obtaining material from P2P or other >sources (Tivo as so aptly observed by Joe) and assembling your own >experience is becoming more feasible, Except that a Tivo listens to (a bunch of) broadcast channels (there, two horrible words in a row!) and caches the "interesting" stuff that it sees for later viewing. The problem, IMHO, is not the broadcasting, or the channels, themselves. It's how people make use of them. Broadcasting is a fairly efficient technique to get information to a whole bunch of people in one go (for them to use now or later). Channels are an efficient way to know which broadcast to listen to for what things. I simply don't buy the argument that says that because the "must watch it when it screens, must watch what they want to show" model of broadcast channels is bad (which I definitely agree with -- I haven't even had a TV for 5+ years), that means that all the components of it (broadcasting, channels, etc) are totally without merit. To get, vaguely, back on topic -- multicasting is just "broadcasting with focus" -- if you like it's a more efficient form of broadcasting for a medium which can handle sending only to interested parties (eg, a packet switched network like the Internet, as opposed to a frequency division "network" like radio waves). >[Spoonfeeding, etc] >This is what makes me leery of attempts to make the Internet a better >broadcast medium than it already isn't. It may make non-broadcast use >more difficult. Unintended consequences, increased core complexity, et al. I'm not especially convinced by this argument either. There's a whole lot of money behind turning the Internet into a "content provision" network -- and I suspect they'll succeed in doing what they want to do irrespective of whether we try to make it more difficult. It does, however, seem to me rather counter productive to insist that they must use unicast, must use the bandwidth inefficiently, in order to some how deter this. At best all that's likely to achieve is that there's even less bandwidth available for other things. (Witness allocations of the frequency spectrum to radio, TV, etc, and what's left for ham radio operators.) And to make it even harder for "small operators" to join in -- so bang goes your online equivilent of public access TV (it's just too expensive to get a pipe big enough to unicast it to a reasoanble audience). [Choose to watch something, join VDC starting it soon] >Yes, like video rental already provides, without the drive there and >back, and PPV on Sky Digital. Yes, like a video rental. Without having to leave the house in the cold of winter. And without having to deal with the fact that some other bastard has taken out the thing you wanted to watch. And, if done properly, without having to watch it all at once so you can return it in time. (I've never seen how PPV on Sky Digital works, so I couldn't say how it compares.) >PS. Road congestion, like unicast broadcast congestion, seems to arise >from the continued belief that we all have to use the road at the same >times (morning and night, Monday-Friday) Indeed. And that survives partly because many people "need" to be at work at the same time, which is largely true because of network effects (eg, you'd like the cafe to be open when you want to get morning tea, and people need to be in the same place at the same time for meetings, etc). And in the same way when something "interesting" happens lots of people are going to "need" to see it at once, if only to keep up with the Jones and be able to talk about it at morning tea the next day. To use your earlier analogy providing more buses/trains/etc can help to reduce this congestion. And in the same way multicasting can help reduce the congestion. But apparently buses/trains/etc are good, and multicasting is bad, for reasons I don't follow. Ewen

2 1

RE: [nznog] Crimes Amendment Bill No 6 Now Law
by Donald Neal 08 Jul '03

08 Jul '03

Let's just bear in mind that postings of a legal nature are discouraged on this list. - Donald Neal List Administrator Donald Neal | Doctor: Did you see what I didn't see? Technical Specialist | Romana: No. Operations Engineering| Doctor: Nor did I. Alcatel NZ Ltd | - Douglas Adams, Shada ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

5 5

Re: [nznog] Multicast status in New Zealand
by Ewen McNeill 07 Jul '03

07 Jul '03

In message <5.2.0.9.0.20030627160856.02023200(a)pele.citylink.co.nz>, Richard Nayl or writes: >At 03:54 p.m. 27/06/2003 +1200, Ewen McNeill wrote: >>In message <5.2.0.9.0.20030627141054.038683c0(a)pele.citylink.co.nz>, >>Richard Naylor writes: >> >>[Multicast] >> >Well the biggest part of the business is video on demand and that can >> >really only be unicast as getting viewers to agree on what they watch is >> >like agreeing on a TV Channel in a huge flat - hopeless. >> >>[... "on demand" doesn't necessarily mean "instantly" ...] >>Which means that for popular stuff that is "on demand" it might not be >>enough to have one channel with it, where the wait time is, say, 15 >>minutes for it to cycle around -- but it might be fine to have 10-20 >>channels, suitably staggered, where the wait time was 1-2 minutes. > >ah - its that word "channel" that I don't see in the future. Such a dated >concept. Ah. Channels are double-plus-ungood. Call it a stream if it makes you feel happier. Or VDC or whatever. >Instead, you're interested in Alastair Cook. Why should you wait til Monday >at 8:45 every week and then miss it because you were on the phone. I don't recall suggesting that you should. >Hey you have 10 minutes now and would like to catch up with what he said last >Monday (when you were on the phone, remember). So why can't you click in >now and view it ? Your argument seems to be "viewers must be able to view it __NOW__(tm)" and hence we must use unicast for everything in order that everyone can have their whim satisifed at an instants notice (and provide all the bandwidth from source to (multiple) sink(s) to make this possible). My argument is that there's a fair chunk of evidence that says that people would be willing to wait 1, 2, 5, 10, 30, or even 60 seconds for something to start (maybe even longer if it's a sizeable time investment to watch it all and the waiting time can be used productively -- eg, getting that beer out of the fridge before settling down to watch the game), especially given a proper cost/benefit tradeoff ("would you pay 5 times as much to be able to have it start within half a second instead of within 5 seconds"?). And that by adding that relaxing condition it's both quite feasible, and quite benefical, to use multicast at least for the more popular things, especially where the multicast VDCs is set up "on demand" with just a short "setup time" to pull in other potential viewers. Think of it as the difference between everyone just crossing the road when they feel like it, and traffic lights (or at very least waiting for the same gap in the traffic). The big reason that it's beneficial in the popular-to-(re)view situation is that there're more people wanting to view something than there are 5-second, 10-second, 30-second, 60-second, whatever start periods. So you can achieve an N:M reduction in the number of VDC you need originating from the source, for only the price of a bit of management infrastructure (request-a-start-soon), and a slightly slip from the "I wanna watch it now! Now! Now! Mommy, make it go!" instant satisfaction. >Multicast is great for synchronous events like TRADITIONAL tv. I just don't >see that continuing. It's good for things other than traditional TV too. Especially where there's (significantly) more than one person wanting to watch something at the "same" time. Which is a surprisingly common case for "current" events. (Speech replays, sports replays, recent movie releases, etc.) Oh, and I quite agree with Joe's comment that caching at the edge can achieve quite remarkable things in turning "watch now or miss it" into "watch when you feel like it". (And even better, if those with suitable broadcast channels would actually get a clue and use the "down" time to spool out things people might want to watch during the week (eg, "this week's hot new movies"). But "video recorders are bad, we must do everything to defeat the use of video recorders". Furrfu.) Ewen

8 7

RE: [nznog] Crimes Amendment Bill No 6 Now Law
by Stephen Andrew 07 Jul '03

07 Jul '03

----Original Message---- From: Tony McGregor [mailto:tonym(a)cs.waikato.ac.nz] Sent: Tuesday, 8 July 2003 2:46 PM To: Stephen Andrew Subject: RE: [nznog] Crimes Amendment Bill No 6 Now Law > Since access means "make use of any of the resources of the computer > system" and "access without authorisation" includes "directly or > indirectly" didn't the internet just become illegal? > > I have no authorisation to access most of the routers and SNMP > gateways my packets went through to get to you. You can probably get around it using the argument that subsection (2) makes any access at all legal as long as you were given permission to do something first; "(1) Every one is liable to imprisonment for a term not exceeding 2 years who intentionally accesses, directly or indirectly, any computer system without authorisation, knowing that he or she is not authorised to access that computer system, or being reckless as to whether or not he or she is authorised to access that computer system. "(2) To avoid doubt, subsection (1) does not apply if a person who is authorised to access a computer system accesses that computer system for a purpose other than the one for which that person was given access. Presumably this means privelege escalation is legal. By putting up a public web/mail/router service you are implying authorised access for some purpose (viewing a web page, sending an email, making packets go from A to B) thus /any/ use is now legal (as long as it it not dishonest by the terms of the act). -- Andrew This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please reply immediately, destroy it and do not copy, disclose or use it in any way.

10 16

Crimes Amendment Bill No 6 Now Law
by David Farrar 07 Jul '03

07 Jul '03

For those interested. INZ will also put a copy of the Act on its website once this is available. DPF "The Crimes Amendment Bill No 6 has now come into force as The Crimes Amendment Act 2003. This Act, amending the 1961 Crimes Act, may potentially affect many internet users and providers. It has been commonly known as the anti-hacking bill. InternetNZ has done a brief paper on aspects of the Act which may affect internet users and providers. The paper is at http://www.internetnz.net.nz/public/committee-reports/ctte-legal-and-regula… or http://tinyurl.com/g9vj ISPs may wish to get professional legal advice on their obligations under the Act. If enough ISPs thought it would be useful, InternetNZ could consider getting generic advice for the industry generally."

4 3

Re: [nznog] Netsites Domain Name Changes page offline?
by Ewen McNeill 07 Jul '03

07 Jul '03

In message <3F095736.9020504(a)paradise.net.nz>, Steven Heath writes: >http://www.netlink.co.nz/~mark/netsites-growth.html [still updated] > >DNC has said since last year 'we are planning to offer .nz stats soon'. >I even offered to do them for free. There are stats in, eg, the DNC Newsletters which are linked from: http://www.dnc.org.nz/index.php?clsid=1&catid=34 ("Newsletters" on the DNC site -- I'm not sure how stable the URL above is.) According to the summaries the stats seem to go back to the start of the year. Alas, they're buried in tables in PDF files and so harder to extract. And in a two-for-one-special: In message <200307071157.XAA0000429877(a)bats.mcs.vuw.ac.nz>, Mark Davies writes: >> [netsite changes suspended pending zone tranfer policy review] > >I got asked on 1 July by Nick Griffin to not publish the changes list until >some review I wasn't aware of that is apparently currently happening was >completed. Interesting. Neither Keith Davidson nor I was able to find an online reference to this review on either the DNC site or the InternetNZ site. Keith Davidson thinks it must have been mentioned only in hard copy form. I've already suggested it'd be nice if such reviews were notified a bit more publically so affected people could comment on them. >Well the growth stats are the primary reason I'm still doing it. The >other pages merely fall out from doing that. Sure. The other pages are the more useful though at least to any non-maths analysis. Especially the search page since the current whois doesn't support any wildcarding. Ewen

2 1

Re: [nznog] Netsites Domain Name Changes page offline?
by David Farrar 07 Jul '03

07 Jul '03

Ewen wrote: > There are stats in, eg, the DNC Newsletters which are > linked from: > > http://www.dnc.org.nz/index.php?clsid=1&catid=34 > According to the summaries the stats seem to go back to > the start of the year. Alas, they're buried in tables in > PDF files and so harder to extract. I have in Excel the stats from 1993 onwards. Mark's stats I have used up until the launch of the SRS. From then on I have gone off the (public) NZRS stats. As under the SRS one can now register a name but not have it in the zone file, the NZRS stats are a couple of hundred higher. They exclude those in the "pending release" category though. If anyone wants a copy, I'm happy to pass over my spreadsheet - even the nice blue graphs for each 2LD :-) > Sure. The other pages are the more useful though at least > to any non-maths analysis. Especially the search page > since the current whois doesn't support any wildcarding. The problem with the changes page is that spammers had started to use them as a source of domain names and e-mail addresses. There were several complaints about a spammer, who said he had got the info off Mark's pages. Hopefully there are ways to minimise or prevent the pages from being of use to spammers, but allow their continued legitimate use. I refer to Mark's pages often and find them a good resource, but as always spammers stuff things up! DPF

1 0

RE: [nznog] Multicast and InternetNZ By-Election - I stand forpro moting mult icast on the Public Network
by Michael Sutton 07 Jul '03

07 Jul '03

Chris The setup of the Multicast Network Border Peering is not hard. The content provider who injects the multicast is protected from unicast server cost overruns, while client customers pay for all their bandwidth and data received. If the tariff is based on bytes then multicast would generate ISP revenue for the network that delivers it to the client. In so far as content providers using multicast: As someone who has concurrently delivered live Radio New Zealand BBC World, XtraMsn Music Channels as well as Compaq || Hewlett Packard and Ministry of Health Live events, all of these content streams, where possible, used dial-in multicast for the Xtra network and would have used multicast via adsl for all events if possible. Michael Auspices & pretence - we will find out :) -----Original Message----- From: Chris Hellberg [mailto:Chris.Hellberg(a)telecom.co.nz] Sent: Monday, July 07, 2003 07:55 To: Joe Abley; Michael Sutton Cc: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Multicast and InternetNZ By-Election - I stand forpromoting mult icast on the Public Network And with what pretence or auspices would multicast peering be set up between peers? I'm a bit dubious that that apart from the tinker factor, there's nothing to really justify the effort that goes in to setting up MSDP, MOSPF, PIM, etc, so unless someone comes up with a content goldmine and charging regime, most customers of multicast-enabled networks aren't going to care that their traffic has a wierd 224.12.3.4 DA and their ISP gets bandwidth savings from such traffic. All very much my own opinions. Chris -----Original Message----- From: Joe Abley [mailto:jabley(a)automagic.org] Sent: Mon 7/7/2003 4:51 PM To: Michael Sutton Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Multicast and InternetNZ By-Election - I stand forpromoting mult icast on the Public Network On Monday, Jul 7, 2003, at 00:08 Canada/Eastern, Michael Sutton wrote: > I am standing as a Candidate for Councillor on a platform to encourage > IP4 multicast peering and service to users of the public Internet in > New Zealand. There is significant effort within InternetNZ to > encourage NGI and IP6, however, this can not provide immediate public > access to multicast services. I'm interested to know what influence you think the InternetNZ council has over network operators, and how they might dictate what protocols operators decide to deploy in their networks. Joe _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ---------------------------------------------------------------------------- -- "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you." ---------------------------------------------------------------------------- --

2 1

Abuse desk responses
by Steve Phillips 07 Jul '03

07 Jul '03

Has anyone else here had problems with NZ ISP abuse complaint responses ? mainly in response to SPAM reports where they refuse to do anything until they get blacklisted but also covering network abuse (DOS type scenario's and the like) ? It appears that abuse complains are more and more regularly falling on deaf ears where the person/team handling the abuse desk seems more concerned with pointing out how it is not their problem than actually trying to educate their end users as to correct practices. This does not appear to be restricted to smaller ISP's either as the main offender (though not limited to) in this case appears to be paradise. -- Steve.

18 22

Multicast and InternetNZ By-Election - I stand for promoting mult icast on the Public Network
by Michael Sutton 07 Jul '03

07 Jul '03

Remembering our postings on multicast over the several past weeks... I have been motivated to act.. Please excuse my partly OT posting with a multicast bias... Many of you are extremely busy this week with the Conference and it may pass attention of those who are also members of InternetNZ that a By-election is occurring for Secretary and Councillor. Voting closes on the 14th July. I am standing as a Candidate for Councillor on a platform to encourage IP4 multicast peering and service to users of the public Internet in New Zealand. There is significant effort within InternetNZ to encourage NGI and IP6, however, this can not provide immediate public access to multicast services. If elected I will make every effort to encourage implementation of multicast services via public networks. I encourage those of you who are InternetNZ members to review the candidates and cast your vote. Please e-mail off-line or call directly if you want to speak with me on this matter. I enclose links to my bio etc... Best Regards... Michael Sutton http://www.awacs.co.nz http://www.internetnz.co.nz/biographies/bio03-msutton.html http://www.internetnz.co.nz/members/by-elections/030619byelection.html

3 2

Netsites Domain Name Changes page offline?
by Bruce Fitzsimons 06 Jul '03

06 Jul '03

Hi everyone, Can anyone shed any light on why the useful, but not-that-well-known page at: http://webpages.netlink.co.nz/~mark/netsites-changes.html is off line? Who is the NZOC? I guess lots of people doing the same thing would be bad, but this page has been around for yonks. Its very interesting to review from time to time, even if its just for a giggle about the weird domain names people choose (and later release back to the world, my my we're lucky). Thanks /Bruce

3 2

Re: [nznog] Netsites Domain Name Changes page offline?
by Ewen McNeill 06 Jul '03

06 Jul '03

In message <05a801c3446e$cb07c040$0a21970a(a)norris>, "Bruce Fitzsimons" writes: >Can anyone shed any light on why the useful, but not-that-well-known page at: > >http://webpages.netlink.co.nz/~mark/netsites-changes.html > >is off line? Who is the NZOC? NZOC == New Zealand (DNS) Oversight Committee, which is the committee in InternetNZ which "oversees" the Domain Name Commissioner's office. I wasn't aware that they were (still) conducting a review (again), and Mark's "changes" list seems (at first glance) to be consistent with the existing zone transfer policies. I know that Mark updated those scripts recently ('cause I prompted him to do so, since some links were out of date including the ones for whois) -- maybe it just picked up a copy of a "in progress" version of the script generating the changes file? >I guess lots of people doing the same thing would be bad, but this page has >been around for yonks. As I understand it, that was the main reason (in an earlier interation of setting zone transfer restrictions) for allowing Mark's scripts to keep going -- it was one point where people could look for changes, rather than everyone doing their own zone transfers. Ewen

1 0

Conference Attendance
by Simon Lyall 06 Jul '03

06 Jul '03

A quick question but are the sessions being recorded and available for later download? I've noticed a couple of sessions I'm interested in opposite each other and also had queries from people at ihug not attending (who said they like watching nanog recorded sessions). I got feedback from a couple of people (one attending, one not) after my requested on Thursday. Both said that the conference is "mainly being a chance to sit in a room with other engineers and sort out new fun stuff." The one who wasn't going said there wern't enough sessions they were interested in (or more directly related to their work) to convince their boss to let them have time off and/or pay for them. "So what would work consider worthwhile? More bleeding edge technology stuff, new product things, more seriously detailed technology discussions (eg a panel about QoS and the various algorithms used and why, might be something that'd attract the Telco types). " -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | Postmaster | Home: simon(a)darkmere.gen.nz Ihug Ltd, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz

1 0

Re: Hackers Challenge started at 1500 NZ time
by Dominic O'Hare 06 Jul '03

06 Jul '03

The owner of the site is in Ft Lauderdale, Florida. ----- Original Message ----- From: <nznog-request(a)list.waikato.ac.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Monday, July 07, 2003 7:13 AM Subject: Nznog Digest, Vol 7, Issue 13 > Send Nznog mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.waikato.ac.nz/mailman/listinfo/nznog > or, via email, send a message with subject or body 'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Nznog digest..." > > > Today's Topics: > > 1. Re: Conference Attendance (Andy Gardner) > 2. Hackers Challenge started at 1500 NZ time (Peter Macaulay) > 3. RE: Abuse desk responses (Neil Gardner) > 4. Re: Abuse desk responses (Michael Hallager) > 5. Re: Abuse desk responses (Edward Yardley) > 6. Re: Hackers Challenge started at 1500 NZ time (Dan Clark) > 7. Re: Hackers Challenge started at 1500 NZ time (Keith Davidson) > 8. Re: Hackers Challenge started at 1500 NZ time (Peter Macaulay) > 9. Re: Hackers Challenge started at 1500 NZ time (Mark Thompson) > 10. Re: Abuse desk responses (Russell Fulton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 6 Jul 2003 00:28:38 -0500 > From: Andy Gardner <andy(a)navigator.co.nz> > Subject: Re: [nznog] Conference Attendance > To: <nznog(a)list.waikato.ac.nz> > Message-ID: <B273F2FC-AF72-11D7-93B2-000393ABF064(a)navigator.co.nz> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > > On Friday, July 4, 2003, at 05:07 AM, Keith Davidson wrote: > > > I'll also be at Unforum for a couple of days, just to rub noses with > > the > > penguin huggers :-) Look forward to putting some names to faces, > > and to > > heckling Joe Abley at every opportunity ... > > > Gee, and here I was thinking you were doing a talk on how to destroy > nz.general through incessant punning. > > > > ------------------------------ > > Message: 2 > Date: Sun, 06 Jul 2003 17:59:02 +1200 > From: Peter Macaulay <exe.dir(a)internetnz.net.nz> > Subject: [nznog] Hackers Challenge started at 1500 NZ time > To: "members-discuss >> InternetNZ Members Discussion List" > <members-discuss(a)internetnz.net.nz>, nznog <nznog(a)list.waikato.ac.nz> > Message-ID: <3F07BAA6.2030505(a)internetnz.net.nz> > Content-Type: text/plain; charset=us-ascii; format=flowed > > > -- > Peter Macaulay > Executive Director > InternetNZ > Direct +64 4 495 2113 > > > ------------------------------ > > Message: 3 > Date: Fri, 4 Jul 2003 16:08:46 +1200 > From: "Neil Gardner" <neil(a)neilnz.com> > Subject: RE: [nznog] Abuse desk responses > To: <nznog(a)list.waikato.ac.nz> > Message-ID: <000001c341e1$f7806620$6b63a8c0(a)delta> > Content-Type: text/plain; charset="us-ascii" > > >-----Original Message----- > >From: Steve Phillips [mailto:steve(a)focb.co.nz] > >Has anyone else here had problems with NZ ISP abuse complaint responses > ? > >mainly in response to SPAM reports where they refuse to do anything > until > >they get blacklisted but also covering network abuse (DOS type > scenario's > >and the like) ? > > Yep, although in most cases it appears to be from a lack of organisation > in getting the complaints to the right person rather than a systemic > neglect of the issue. Recently I tried for 2 weeks through proper > channels to get an obviously infected ADSL customer disabled and > informed of their problem, to no avail, and culminating in the Helpdesk > telling me that the Abuse people only worked form midnight to 8am a > couple of days a week!!!! > > Obviously what he meant was that the person that dealt with it in the > NOC was next rostered on for a midnight to 8am shift, but it's NOT what > he said. > > Anyway, I posted the details on this list and someone from the > appropriate ISP saw it and had the issue resolved in 30 minutes. > > But there should be some sort of internally monitored helpdesk with > escalation for complaints like that - I know of a number of (admittedly > corporate and not cheap - HEAT and Magic spring to mind) that do this > sort of thing very well). > > Out of interest, are any ISP reps here prepared to admit how they track > issues, specifically something like complaints to abuse(a)isp.co.nz where > there could be a lot of incoming jobs? > > Cheers - Neil G > > > > ------------------------------ > > Message: 4 > Date: Sun, 6 Jul 2003 21:18:51 +1200 > From: Michael Hallager <michael(a)networkstuff.co.nz> > Subject: Re: [nznog] Abuse desk responses > To: "Neil Gardner" <neil(a)neilnz.com> > Cc: nznog(a)list.waikato.ac.nz > Message-ID: <200307062118.51406.michael(a)networkstuff.co.nz> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > At Vivid Computers / Vivid Net, all abuse(a)vivid.net.nz email comes to myself > - as the Systems Administrator - for prompt action. > > Michael Hallager > Networkstuff Limited > http://www.networkstuff.co.nz > > > >-----Original Message----- > > > > From: Steve Phillips [mailto:steve(a)focb.co.nz] > > > > >Has anyone else here had problems with NZ ISP abuse complaint responses > > > > ? > > > > >mainly in response to SPAM reports where they refuse to do anything > > > > until > > > > >they get blacklisted but also covering network abuse (DOS type > > > > scenario's > > > > >and the like) ? > > > > Yep, although in most cases it appears to be from a lack of organisation > > in getting the complaints to the right person rather than a systemic > > neglect of the issue. Recently I tried for 2 weeks through proper > > channels to get an obviously infected ADSL customer disabled and > > informed of their problem, to no avail, and culminating in the Helpdesk > > telling me that the Abuse people only worked form midnight to 8am a > > couple of days a week!!!! > > > > Obviously what he meant was that the person that dealt with it in the > > NOC was next rostered on for a midnight to 8am shift, but it's NOT what > > he said. > > > > Anyway, I posted the details on this list and someone from the > > appropriate ISP saw it and had the issue resolved in 30 minutes. > > > > But there should be some sort of internally monitored helpdesk with > > escalation for complaints like that - I know of a number of (admittedly > > corporate and not cheap - HEAT and Magic spring to mind) that do this > > sort of thing very well). > > > > Out of interest, are any ISP reps here prepared to admit how they track > > issues, specifically something like complaints to abuse(a)isp.co.nz where > > there could be a lot of incoming jobs? > > > > Cheers - Neil G > > > > > > _______________________________________________ > > Nznog mailing list > > Nznog(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > -- > Michael Hallager > Managing Director > Networkstuff Limited > > http://www.networkstuff.co.nz > michael @ networkstuff.co.nz > > > ------------------------------ > > Message: 5 > Date: Sun, 6 Jul 2003 21:58:57 +1200 > From: "Edward Yardley" <edward(a)edan.co.nz> > Subject: Re: [nznog] Abuse desk responses > To: <nznog(a)list.waikato.ac.nz> > Message-ID: <011501c343a5$37e58780$3d00000a(a)sebastian> > Content-Type: text/plain; charset="iso-8859-1" > > I've found the same thing with Paradise/Telstra Clear's responses. > > Edward. > ----- Original Message ----- > From: <nznog(a)neilnz.com> > To: <nznog(a)list.waikato.ac.nz> > Sent: Friday, July 04, 2003 4:15 PM > Subject: RE: [nznog] Abuse desk responses > > > > >-----Original Message----- > > >From: Steve Phillips [mailto:steve(a)focb.co.nz] > > >Has anyone else here had problems with NZ ISP abuse complaint responses > > ? > > >mainly in response to SPAM reports where they refuse to do anything > > until > > >they get blacklisted but also covering network abuse (DOS type > > scenario's > > >and the like) ? > > > > Yep, although in most cases it appears to be from a lack of organisation > > in getting the complaints to the right person rather than a systemic > > neglect of the issue. Recently I tried for 2 weeks through proper > > channels to get an obviously infected ADSL customer disabled and > > informed of their problem, to no avail, and culminating in the Helpdesk > > telling me that the Abuse people only worked form midnight to 8am a > > couple of days a week!!!! > > > > Obviously what he meant was that the person that dealt with it in the > > NOC was next rostered on for a midnight to 8am shift, but it's NOT what > > he said. > > > > Anyway, I posted the details on this list and someone from the > > appropriate ISP saw it and had the issue resolved in 30 minutes. > > > > But there should be some sort of internally monitored helpdesk with > > escalation for complaints like that - I know of a number of (admittedly > > corporate and not cheap - HEAT and Magic spring to mind) that do this > > sort of thing very well). > > > > Out of interest, are any ISP reps here prepared to admit how they track > > issues, specifically something like complaints to abuse(a)isp.co.nz where > > there could be a lot of incoming jobs? > > > > Cheers - Neil G > > > > > > _______________________________________________ > > Nznog mailing list > > Nznog(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > ------------------------------ > > Message: 6 > Date: Sun, 6 Jul 2003 22:17:22 +1200 > From: "Dan Clark" <dan(a)scarfies.net> > Subject: Re: [nznog] Hackers Challenge started at 1500 NZ time > To: "Peter Macaulay" <exe.dir(a)internetnz.net.nz>, "members-discuss >> > InternetNZ Members Discussion List" > <members-discuss(a)internetnz.net.nz>, "nznog" > <nznog(a)list.waikato.ac.nz> > Message-ID: <00be01c343a7$d49611b0$150210ac(a)morpheus> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all, > Any examples of defaced sites??? > > Regards > Dan > > > ----- Original Message ----- > From: "Peter Macaulay" <exe.dir(a)internetnz.net.nz> > To: "members-discuss >> InternetNZ Members Discussion List" > <members-discuss(a)internetnz.net.nz>; "nznog" <nznog(a)list.waikato.ac.nz> > Sent: Sunday, July 06, 2003 5:59 PM > Subject: [nznog] Hackers Challenge started at 1500 NZ time > > > > > > -- > > Peter Macaulay > > Executive Director > > InternetNZ > > Direct +64 4 495 2113 > > > > _______________________________________________ > > Nznog mailing list > > Nznog(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > ------------------------------ > > Message: 7 > Date: Sun, 6 Jul 2003 22:39:28 +1200 > From: "Keith Davidson" <keith(a)wise.net.nz> > Subject: Re: [nznog] Hackers Challenge started at 1500 NZ time > To: "nznog" <nznog(a)list.waikato.ac.nz> > Message-ID: <00d901c343aa$e0970200$4db724ca(a)wise.net.nz> > Content-Type: text/plain; charset="iso-8859-1" > > > Hi all, > > Any examples of defaced sites??? > > www.scarfies.net :-) > > I still can't get through to www.defacers-challenge.com, which was supposed > to be listing the hacked sites... > > Keith Davidson > > > > ------------------------------ > > Message: 8 > Date: Sun, 06 Jul 2003 23:00:10 +1200 > From: Peter Macaulay <exe.dir(a)internetnz.net.nz> > Subject: Re: [nznog] Hackers Challenge started at 1500 NZ time > Cc: nznog <nznog(a)list.waikato.ac.nz> > Message-ID: <3F08013A.8070405(a)internetnz.net.nz> > Content-Type: text/plain; charset="us-ascii" > > Haven't seen any yet and zone-h showed only a slight increase before the > DNOS attack clogged their 100mb totally. The originator runs a > 'brazilian' site based out of the US, and his/her email is from > somewhere in France. The Estonian link is for the time of the challenge > and the time is according to zone-h which is estonian (Tallin) > ;-) Just showing I have done my homework before putting on the makeup > and getting demolished by Hoskin and Hawkesbury. > > Keith Davidson wrote: > > >>Hi all, > >> Any examples of defaced sites??? > >> > >> > > > >www.scarfies.net :-) > > > >I still can't get through to www.defacers-challenge.com, which was supposed > >to be listing the hacked sites... > > > >Keith Davidson > > > > > >_______________________________________________ > >Nznog mailing list > >Nznog(a)list.waikato.ac.nz > >http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > > -- > Peter Macaulay > Executive Director > InternetNZ > Direct +64 4 495 2113 > >

1 0

Hackers Challenge started at 1500 NZ time
by Peter Macaulay 06 Jul '03

06 Jul '03

-- Peter Macaulay Executive Director InternetNZ Direct +64 4 495 2113

5 5

Conference Attendance
by Tony McGregor 05 Jul '03

05 Jul '03

There will be a bunch of people there from the WAND group. The speaker discounts made it possible for us. Can someone confirm that there will be connectivity (inc wireless) at the conference? Tony ---------------------------------------------------------------------------- Tony McGregor Mail: T.McGregor(a)cs.waikato.ac.nz Department of Computer Science Phone: +64 7 838 4651 Waikato University Fax: +64 7 858 5095(w) +64 7 825 5047(h) Private Bag 3105 Home: +64 7 825 5040 mobile: (021)313004 Hamilton, New Zealand www: http://www.cs.waikato.ac.nz/~tonym ----------------------------------------------------------------------------

6 6

Net4U Thread
by Donald Neal 03 Jul '03

03 Jul '03

The current (or immediately past?) thread dealing with Net4U contains some postings which are clearly within this list's acceptable use policy, and some which are not. In brief, postings which discuss operational or technical issues - and an ISP using spam to advertise does look to me like one of those - are in. Postings containing "character assassination or lack of respect for other participants" are out. Whether they cause deformation or not. For myself, I'd like to see no further additions to the thread unless they come from people who have something new and relevant to say. - Donald Neal ex cathedra, or something Donald Neal | Doctor: Did you see what I didn't see? Technical Specialist | Romana: No. Operations Engineering| Doctor: Nor did I. Alcatel NZ Ltd | - Douglas Adams, Shada ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

2 1

WTB: APE bandwidth
by Michael Hallager 03 Jul '03

03 Jul '03

Hello all, Could ISP's that have connections to the APE please contact me with their prices for bandwidth to equipment located at APE. Kind regards, Michael Hallager Managing Director Networkstuff Limited http://www.networkstuff.co.nz michael @ networkstuff.co.nz

1 0

Re: [nznog] APE Peering
by - 03 Jul '03

03 Jul '03

Sahil said to me, as well as publically on the site that the "auditor's" report would be made available publically on the website. After a number of months I saw him again, and casually asked, whats up with that auditor's report, and he shrugged it off, as if to say "that was a joke". Secondly Sahil obviously did know about it, so shrugging it off as his staff's fault is amusing in the least

9 11

RE: [nznog] APE Peering
by Chris O'Donoghue 03 Jul '03

03 Jul '03

Well perhaps you should work on your management a bit more. It took all of about 5 seconds to convince me that this was worthwhile for my sysadmins to attend. But then again maybe I'm biased, cos I went last year. Chris Chris O'Donoghue Technology Manager Online & Digital TVNZ -----Original Message----- From: Jeremy Brooking [mailto:jeremy(a)morenet.net.nz] Sent: Friday, 4 July 2003 1:01 p.m. To: Simon Lyall Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] APE Peering Simon Lyall wrote: ><grump> >By which I assume you make less than $20,000 per year and live in central >Auckland. Seriously it's $250 per day, if you go on two days thats $500 >bucks. $20/per weeek if you started saving at the start of the year when >this was first mentioned (and I think I told people to start saving). > >If you present you get that day free. If you talk your work into a 5% >training budget then it'll cover it. > >Exactly what sort of pricing could you afford? I remmeber the little ISP >forum that Internetnz had a couple of years back, that was $50 per day and >nobody much attended. ></grump> > > Perhaps my _insane_ comment was a bit of an overstatement. First post I saw regarding it was 9th of 3rd. So that would make it about $50 a week. And of course, we all have $50 spare a week dont we? _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ================================================================ CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on nzoom.com, visit us online at http://www.nzoom.com ================================================================

1 0

Netforum - I'm in !
by Tim John 03 Jul '03

03 Jul '03

> On another note, Whos going to Netforum? > A quick survey of Auckland Thursday Night Curry attendees didn't look too > promising.. Chris and I from Domainz are coming up for the Thursday and Friday. We'll be the ones hiding in the shadows :) We're looking forward to Joe's presentation ... and of course the curry on Thursday ! Tim DISCLAIMER: The content of this email is confidential and may contain legally privileged information intended only for the individual or entity named above. Access to this message by anyone else is unauthorised. If you are not the intended recipient, please be advised that the use, distribution and publication of the above information is prohibited. If you have received this email in error, please contact Domainz by returning the email and destroying the original. Thank you.

2 1

19" Cases.....
by Roger De Salis 03 Jul '03

03 Jul '03

I have built two self assembly 19" cases, simply designed to be a simple as possible, and extremely low cost. Unit One, 2.5RU (ie the same height as a standard PCI card.) 450mm deep. Accepts standard power supply, any ATX board (full, mini, micro). Combos are Std CDROM + Floppy + 6 drives OR up to 10 disk drives without CDROM/Floppy Assembly. No risers. One case fan (included). Unit Two, Same Height as standard ATX power supply 90mm, 2RU, 275mm deep. Accepts micro ATX board only. Accepts Standard ATX power supply. Accepts laptop 1/3high floppy and CDROM (which I can supply if required) $169 for CD, $79 for floppy. Accepts 1/2 high PCI Cards only. No risers Unit Two currently supports 1 x 3.5" DD and 3 x 2.5"DD. Production version will likely be modded to accept 2 x 3.5"DD and 2 x 2.5" DD ========================================================== Removable 19" Rack wings on both. Mounting combinations are: Flush front, recess 50mm, centre pillar mount, or reverse mount, and 50mm recessed reversed. The intention is to place a full shelf underneath the base unit, then I would not have any qualms about 4-5 racked up on top of each other. There is currently no provision for slides, but if someone was desperate..... Henry Ford Colour scheme. NZ$260+GST complete with PSU, wiring assembly pwr/hdd assy, screws. Netforum Special NZ$230+GST. I'll have three units on show at the Waipuna next week if someone wants to look/dicuss. The second small unit was intended to complement Cisco 2600 in a rack, but also be the right size for home stereo with silent PSU and 2.5"DDs, so if you want to buy your own power supply, knock $35 off the price. Further discounts for quantity (ie 4up.) If you want to buy just the metalwork, and make up your own, happy to oblige... Basically I run them as telephone controllers, log servers etc etc, with a Duron 1300, MSI 6787 board with LAN on-board, single drive and CD for approx $700, rack mounted with a 2 year warranty on everything. About 14 day delivery. I'll include a couple of JPEG's later this morning. Rgds Roger De Salis -- \_ Roger De Salis rdesalis(a)fx.net.nz </' FX Networks +64 25 481 452 /) Wellington, New Zealand roger(a)desalis.gen.nz (/ ` Bentley win Le Mans! - What next, English win cricket in Aus?

1 0

Net4U's earlier actions
by Sahil Gupta - NET4U LIMITED 02 Jul '03

02 Jul '03

Hi, Firstly, I'd like to apologise for actions made earlier during the day with respect to a mailout to a certain group of ISP's. I wasnt thinking clearly when I thought to add a few more addresses to the mailout to existing contacts. My bad, wont be repeated. As Richard has suggested, if anyone has any concerns or issues that need addressing, please contact us off-list. Just for those that were concerned, issues with abuse(a)net4u.co.nz have now been resolved. Once again, my apologies for the drama here in NZNOG. Regards, Sahil Gupta Senior Account Manager NET4U LIMITED Phone: 0508-263-848 Fax: 07-8582659 Mobile: 029-366-6375

1 0

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

You have some valid points here. The whole thing is quite disappointing, and for many, quite frustrating. This abuse(a)net4u is also becoming a sore point, and clearly there has been an issue with this address. I can only chase up as much as was passed on to me. There are a number of other recommended tasks which were to be carried out but have not :( Please contact me off-list with more details, and I will be happy to deal with things. As I said, I'm sill helping Net4U (Unpaid I might add) here and there when I am not involved with my regular clients. If anyone else is reading this and has ANY issues with Net4U that have been ignored, please feel free to contact me off-list or directly on 021409987, and I will to my best to deal with things. This is not the place for this nonsense, so lets get all this off-list, contact me, and lets get everyone happy. If no one has any other abuse they want to throw this way, perhaps we can move back to other interesting threads such as Multicast which I enjoyed following? How about why ISP's should/shouldn't be able to control assignment of IP addresses on ADSL Starter? Anyone have any views on this? Cheers, Richard. -----Original Message----- From: Dave Howes [mailto:mish(a)doomx.net] Sent: Thursday, 3 July 2003 6:49 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] APE Peering I think we should all take a good look at ourselves, and the motivation behind the pettiness that from time to time, makes me wonder just how many children play on this list, and how many people are here to get work/business done. Lets just get on with our work please everyone. Each time the topic of Net4u has come up I've resisted posting as previously the entire situation was already at boiling point, but suggesting people are here to play when they're obviously just frustrated by actions that they see as detremental and disrespectful to other New Zealand Network Operators really rubs me the wrong way. Net4u does seem to be operating in a more legal fashion than before but they're still not admin friendly by any stretch of the imagination. I've received spam from net4u customers to domains I previously managed, I contacted Net4u to advise them of this ( abuse(a)net4u.co.nz) but have never received any response. I was also informed of a 'hole' in their security through which anyone can log into the net4u network and gain free ADSL service by use of an 'admin' account, I emailed the administrator of net4u to advise of this but despite sending two emails I never received a response and (I just tested) the hole still seems to be wide open. I'm glad you see the spam from Net4u as a bad thing as even though the operators of Net4u are (reasonably) new to the game, in this 'net enabled' age even the newest player has no excuse for thinking that unsolicited commercial email to a soa address is a good idea, the same goes for their previous dubious actions. You can feel free to view comments like these as 'pettiness' but I for one am glad to be informed of the actions (or inaction) of New Zealand ISPs even if the observations are at times coloured by external factors. -- Regards, Dave Howes.

1 0

LOL - Tis so odd.....
by Michael Hallager 02 Jul '03

02 Jul '03

Richard's entire post looks clearly like a Sahil marketing effort: COPY We have made a brief report which is not for public viewing, but which has identified a small number of issues on the Net4U network (which were quickly rectified) that were as a result of previous employees. We found nothing that was causing deliberate loss of bandwidth to any other party. We did not fully complete the work due to budget restraints, however we did cover most of the important aspects. Some of our recommendations have been implemented, and sadly others have not been done, but Net4U are operating somewhat better than they were. /COPY YEAH RIGHT. We all have the MP3 of Sahil BOASTING about taking bandwidth. How do you reconcile that with your above claim? I think we would all like the answer. Sahil also ropes his friends into fronting for him, including doing the following actions, both people have admitted that Sahil got them to contact me: 1) Sending me an abusive email 2) Contacting me to rent several thousand dollars worth of equipment that I would never loan to Sahil. COPY > I can assure you the bandwidth offered by Net4U in that "distributed" > email is legitimate, and I should warn you that continued accusations > and alligations are a direct attack against me and my company, which > left Net4U operating legally and above board, and there is no > justification for this blatant deformation. /COPY Don't like the heat, get out of the fire. You knew full well what you were getting into when you associated yourself with Net4u by doing this contracting job. COPY It doesn't take much for everyone to see that some of you are making an issue simply because it's Sahil and Net4U, and because you were a reject at school who was picked on and bullied, and now have a psychological disorder resulting in you playing out the role of your boyhood deamon from school, dishing out what you received. /COPY OK, whatever. I have a small **** or a demon or whatever (This is starting to sound like whacky religious stuff). How did you KNOW??? Michael Hallager Managing Director Networkstuff / Comsolve

1 0

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

Thanks Dan. There are one or two ISP's and their administrators out there that have been VERY generous, sympathetic and helpful towards Sahil & Net4U and yet more who have been giving Net4U advise, and telling him off when needed :). As I say, Net4U are "growing up" slowly, but like me, are bound to make mistakes along the way. I enjoy helping others where help is needed, but sometimes this pisses other people off, especially those that don't think that particular person or business deserves to be helped or to get ahead, and I'm not just talking about Net4U. Anyway, rest assured, he has just had a verbal assault from me for yet again, not thinking carefully and using common sense before acting. ie sending Spam etc Thanks for your patience and understanding everyone. He wont be doing that again. :) Cheers, Richard. -----Original Message----- From: Dan Clark [mailto:dan(a)scarfies.net] Sent: Thursday, 3 July 2003 4:04 p.m. To: Richard Parkinson; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] APE Peering I have to agree with Richard here, the problem is the young man who set this particular ISP up has historicly been ignorant as to some of the ethical rules and unwritten policy's of the internet community. We all make mistakes and maybe he just needs a little guidance and support from fellow ISP's who, will no doubt have started from penny's in the early days themselves. Regards Dan Clark Network Manager Scarfies.Net Ltd ----- Original Message ----- From: Richard <mailto:Richard(a)sigel.co.nz> Parkinson To: nznog(a)list.waikato.ac.nz Sent: Thursday, July 03, 2003 3:35 PM Subject: RE: [nznog] APE Peering We have made a brief report which is not for public viewing, but which has identified a small number of issues on the Net4U network (which were quickly rectified) that were as a result of previous employees. We found nothing that was causing deliberate loss of bandwidth to any other party. We did not fully complete the work due to budget restraints, however we did cover most of the important aspects. Some of our recommendations have been implemented, and sadly others have not been done, but Net4U are operating somewhat better than they were. We no longer oversee the operation of Net4U, but have kept in touch with them, and assist with other matters both business related and technical, and feel Net4U & Sahil are slowly "growing up" so to speak, but I expect mystiques will still be made from time to time. None of us are perfect. I can assure you the bandwidth offered by Net4U in that "distributed" email is legitimate, and I should warn you that continued accusations and alligations are a direct attack against me and my company, which left Net4U operating legally and above board, and there is no justification for this blatant deformation. I must say that I also disagree with the method of advertising chosen. Had I been consulted I would have recommended against it, but in saying that, I welcome email in my inbox that relates directly to my line of business and would rather receive such email as opposed to the ones about increasing the size of certain body parts or some other "amazing offer" which we see all to often of late, depending on how good your mail filters are. It doesn't take much for everyone to see that some of you are making an issue simply because it's Sahil and Net4U, and because you were a reject at school who was picked on and bullied, and now have a psychological disorder resulting in you playing out the role of your boyhood deamon from school, dishing out what you received. Without naming anyone, I would also like to point out that there are those of you on this list making such accusations who are the last people to do so, or should we raise the matter of a VAST amount of bandwidth stolen from Telecom for a number of months, by a much larger ISP than Net4U, who even taught another ISP's network administrator how to do it only days before Telecom figured it all out... or perhaps I could send the list a copy of some forged court documents? To these few people I say, I suggest you stop stirring the pot and leave the past alone, or you will get more than just a little of it on you. I think we should all take a good look at ourselves, and the motivation behind the pettiness that from time to time, makes me wonder just how many children play on this list, and how many people are here to get work/business done. Lets just get on with our work please everyone. Cheers, Richard Parkinson (Director) Sigel Data Systems Ltd. -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Thursday, 3 July 2003 2:13 p.m. To: nznog(a)list.waikato.ac.nz; Steve Phillips Subject: Re: [nznog] APE Peering If anyone had forgotten, where is the "Report" from Sigel Systems about Net4u's runnings over the last 3 months. I believe the impartial 3rd party was hired as one of net4u's staff a very short while after (so couldn't be impartial) Thanks Craig > >> >[snippage] > > > We can deliver using several methods as I've outlined above and can also > > > take care of transporting your existing I.P. Address ranges supplied to > > > you by your current provider to us. > > That would be a neat trick. Almost worth taking him up on that just to > watch him fail dismally. _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _____ _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

APE Peering
by Sahil Gupta - NET4U LIMITED 02 Jul '03

02 Jul '03

Hi, This announcement is more centered towards Network Administrators at ISP's that are connected to the APE. Net4U (www.net4u.co.nz) connected to the APE since May 2003 and since then have been peering with a number of ISP's around the country. We are currently looking for more ISP's to peer with and so if you feel that we could have a domestic peering arrangement between your ISP and Net4U, please get back to me off-list as we would be more than happy to do so. Regards, Sahil Gupta Senior Account Manager NET4U LIMITED Phone: 0508-263-848 Fax: 07-8582659 Mobile: 029-366-6375

7 6

APE Peering
by Richard Patterson 02 Jul '03

02 Jul '03

1 0

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

We have made a brief report which is not for public viewing, but which has identified a small number of issues on the Net4U network (which were quickly rectified) that were as a result of previous employees. We found nothing that was causing deliberate loss of bandwidth to any other party. We did not fully complete the work due to budget restraints, however we did cover most of the important aspects. Some of our recommendations have been implemented, and sadly others have not been done, but Net4U are operating somewhat better than they were. We no longer oversee the operation of Net4U, but have kept in touch with them, and assist with other matters both business related and technical, and feel Net4U & Sahil are slowly "growing up" so to speak, but I expect mystiques will still be made from time to time. None of us are perfect. I can assure you the bandwidth offered by Net4U in that "distributed" email is legitimate, and I should warn you that continued accusations and alligations are a direct attack against me and my company, which left Net4U operating legally and above board, and there is no justification for this blatant deformation. I must say that I also disagree with the method of advertising chosen. Had I been consulted I would have recommended against it, but in saying that, I welcome email in my inbox that relates directly to my line of business and would rather receive such email as opposed to the ones about increasing the size of certain body parts or some other "amazing offer" which we see all to often of late, depending on how good your mail filters are. It doesn't take much for everyone to see that some of you are making an issue simply because it's Sahil and Net4U, and because you were a reject at school who was picked on and bullied, and now have a psychological disorder resulting in you playing out the role of your boyhood deamon from school, dishing out what you received. Without naming anyone, I would also like to point out that there are those of you on this list making such accusations who are the last people to do so, or should we raise the matter of a VAST amount of bandwidth stolen from Telecom for a number of months, by a much larger ISP than Net4U, who even taught another ISP's network administrator how to do it only days before Telecom figured it all out... or perhaps I could send the list a copy of some forged court documents? To these few people I say, I suggest you stop stirring the pot and leave the past alone, or you will get more than just a little of it on you. I think we should all take a good look at ourselves, and the motivation behind the pettiness that from time to time, makes me wonder just how many children play on this list, and how many people are here to get work/business done. Lets just get on with our work please everyone. Cheers, Richard Parkinson (Director) Sigel Data Systems Ltd. -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Thursday, 3 July 2003 2:13 p.m. To: nznog(a)list.waikato.ac.nz; Steve Phillips Subject: Re: [nznog] APE Peering If anyone had forgotten, where is the "Report" from Sigel Systems about Net4u's runnings over the last 3 months. I believe the impartial 3rd party was hired as one of net4u's staff a very short while after (so couldn't be impartial) Thanks Craig > >> >[snippage] > > > We can deliver using several methods as I've outlined above and can also > > > take care of transporting your existing I.P. Address ranges supplied to > > > you by your current provider to us. > > That would be a neat trick. Almost worth taking him up on that just to > watch him fail dismally. _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 5

RE: [nznog] APE Peering
by Simon Byrnand 02 Jul '03

02 Jul '03

At 15:35 3/07/03 +1200, Richard Parkinson wrote: >I must say that I also disagree with the method of advertising chosen. Had >I been consulted I would have recommended against it, but in saying that, >I welcome email in my inbox that relates directly to my line of business >and would rather receive such email as opposed to the ones about >increasing the size of certain body parts or some other "amazing offer" >which we see all to often of late, depending on how good your mail filters >are. > Sorry, but that doesn't wash with me, or I suspect most members of the list. Spam is Spam whether its trying to sell me Viagra or Bandwidth. Anybody that received that mailout (fortunately I didn't) who had no previous business dealings with Net4U could be legitimately annoyed by it. The sample "message" appeared to be addressed to soa@ which suggests it might have been taken from domain or APNIC contact details. >It doesn't take much for everyone to see that some of you are making an >issue simply because it's Sahil and Net4U, and because you were a reject >at school who was picked on and bullied, and now have a psychological >disorder resulting in you playing out the role of your boyhood deamon from >school, dishing out what you received. > Pot, Kettle, Black ? Regards, Simon

2 1

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

I did say disagree with the "spam" method used. I agree this thread is a waste of time and should die. -----Original Message----- From: Gordon Smith [mailto:gordon(a)morenet.net.nz] Sent: Thursday, 3 July 2003 3:47 p.m. To: Richard Parkinson; nznog(a)list.waikato.ac.nz Subject: RE: [nznog] APE Peering Richard, Was there any point to that message at all? Firstly, spam is spam, not "distributed" email. It is unsolicited commercial email, which this was. Secondly, I think you'll find that ANY provider that has previously behaved as poorly would attract a similar response. I really don't care if they are mystical or deformed, this is a breach of what is generally accepted as "acceptable conduct". Perhaps this thread should die - it has very little to do with network operations. Gordon Smith CCNA Network Operations Manager MoreNet Ltd PGP Fingerprint: 4B12 FBE4 784A 3294 6637 4587 AB6F C893 AB2C 952C

1 0

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

And I knew this as soon as I saw it hit the list. Cheers -----Original Message----- From: Matthew Poole [mailto:lists(a)p00le.net] Sent: Thursday, 3 July 2003 3:45 p.m. To: Richard Parkinson Cc: NZNOG Subject: RE: [nznog] APE Peering Getting very OT here, but that word is EXCEPT! On Thu, 3 Jul 2003, Richard Parkinson wrote: > Accept for a spelling error or two. :) > > -----Original Message----- > From: Juha Saarinen [ mailto:juha(a)saarinen.org] > Sent: Thursday, 3 July 2003 3:44 p.m. > Cc: NZNOG > Subject: RE: [nznog] APE Peering > > > > On Thu, 3 Jul 2003, Richard Parkinson wrote: > > > I can assure you the bandwidth offered by Net4U in that "distributed" > > email is legitimate, and I should warn you that continued accusations > > and alligations are a direct attack against me and my company, which > > left Net4U operating legally and above board, and there is no > > justification for this blatant deformation. > > Priceless. > > > -- > Juha Saarinen > _______________________________________________ > Nznog mailing list > Nznog(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >

1 0

RE: [nznog] APE Peering
by Richard Parkinson 02 Jul '03

02 Jul '03

Accept for a spelling error or two. :) -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 3 July 2003 3:44 p.m. Cc: NZNOG Subject: RE: [nznog] APE Peering On Thu, 3 Jul 2003, Richard Parkinson wrote: > I can assure you the bandwidth offered by Net4U in that "distributed" > email is legitimate, and I should warn you that continued accusations > and alligations are a direct attack against me and my company, which > left Net4U operating legally and above board, and there is no > justification for this blatant deformation. Priceless. -- Juha Saarinen _______________________________________________ Nznog mailing list Nznog(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1