- NZNOG - lists.nznog.org

RE: NNTP Access for APE connected machines.
by Ted Grenfell 13 May '01

13 May '01

At 11:07 14/05/2001, James Tyson wrote: >That's a fairly fine line your walking there. Careful you dont trip. Okay Mum. -- Ted Grenfell Xtra ISP Performance Manager Mob 025 435 455; DDI 09 359 5854; Fax 09 362 8100 Level 13, Telecom Tower, 16 Kingston St, Private Bag 92028, Auckland --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NNTP Access for APE connected machines.
by Mark Derricutt 13 May '01

13 May '01

Hi, I was wondering if any APE connected ISPs allow read/write NNTP access to other APE connected machines? Our connection here at work goes via Zivo, and I'm wanting to connect to a news server that carries comp.* and nz.*. Apologies if this is offtopic, but I thought this would be the best place to ask about such access. Mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

11 23

Re: Update to DNS question
by Andy Gardner 11 May '01

11 May '01

Just to lower the S/N ratio even further, I am pleased to announce that enigma.cypher.co.nz is now registered for NS use at OpenSRS/Tucows. -- Andrew P. Gardner barcelona.com stolen, stmoritz.com stays. What's uniform about the UDRP? We could ask ICANN to send WIPO a clue, but do they have any to spare? Get active: http://www.domain-owners.org http://www.tldlobby.com --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Update to DNS question
by Gavin 11 May '01

11 May '01

Hi, Thanks to all those who responded to my DNS problem -- 2 weeks of dicking about, and finally some clear answers. For those who asked the details are: NZ domain: cypher.co.nz NS: enigma.cypher.co.nz IP: 202.37.176.1 .COM domain: cypher-international.com, and cypherinternational.com I simply want to point both of these back here. They are held by domains.com, also called dns4less.com, also called tucows.com, and I cannot pry our name off them for 60 days. The issue is more that they WONT add A record(s) until the nameservers are registered with the internic, and while I am aware that other US registrars (such as Network Solutions) can do this -- they can't/wont -- the nameservers have to be registered first. After 60 days I can pry our domain name off them and transfer it to someone useful, but for now..... This is what happens when over enthusiastic co-workers decide to establish a international presence without looking first...... Sigh. PS:- I am not a DNS expert -- I can only just swim in this end of the pool. -- Regards, Gavin Melville, gavin(a)cypher.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 6

OT - sort of
by Richard Naylor 10 May '01

10 May '01

Since its Friday, here is a little snippet relayed on from another list....and to confirm rumours - I do have a GbE network at home. Actually there are 3 GbE - me and my machines 100Mbps - the family 10mbps - Jeremy (who gets punished for doing 5GB of DSL traffic to Napster) + the neighbours http://www.iec.org/tutorials/opt_ethernet/images/figure05.jpg and just so you know how REAL this is, the 10Gig crew are starting forming the 100Gig group...... richard.naylor(a)citylink.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 4

Maybe this is off-topic... maybe not...
by Juha Saarinen 10 May '01

10 May '01

... but are there problems with Asia Online again? Can't get to the Hirrold's site: # traceroute 203.99.65.227 traceroute to 203.99.65.227 (203.99.65.227), 30 hops max, 38 byte packets 1 router (192.168.1.254) 2.750 ms 1.192 ms 1.507 ms 2 203-79-82-254.adsl-wns.paradise.net.nz (203.79.82.254) 18.281 ms 14.204 ms 16.725 ms 3 192.168.253.225 (192.168.253.225) 16.452 ms 18.624 ms 19.962 ms 4 kelly.ipnet2.paradise.net.nz (203.96.155.158) 21.254 ms 19.058 ms 20.029 ms 5 fe7-0-1.bertha.paradise.net.nz (203.96.152.254) 19.570 ms 17.970 ms 19.780 ms 6 iconz1.wix.net.nz (202.7.1.1) 23.588 ms 22.142 ms 23.435 ms 7 f0-0.core1.wn.nz.asiaonline.net (210.48.3.244) 23.251 ms 21.369 ms 19.085 ms 8 f2-0.core2.ak.nz.asiaonline.net (210.48.12.1) 35.686 ms 34.319 ms 31.018 ms 9 f0-0.core3.ak.nz.asiaonline.net (202.14.100.220) 37.003 ms 64.375 ms 40.895 ms 10 * * * 11 * * * 12 * * * 13 * * f0-0.core3.ak.nz.asiaonline.net (202.14.100.220) 38.050 ms !X 14 * * * 15 * And my ssh sessions with IDG freeze and die. Some hosts (on Clear and Above.net) have no problems reaching AOL, but others (Paradise, TSNZ) can't get to AOL. -- Juha The malformed orange Fails to satisfy the eye: Segmentation fault. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: Complex DNS problem
by Ewen McNeill 09 May '01

09 May '01

In message <3AFAC212.31837.13D86B0(a)localhost>, "Gavin" writes: >We now have a .com name and wish to redirect accesses to this domain name >back to our .nz address, and to do this we have to register our nameserver(s) >with the Internic. NSI used to have forms for doing this (registering the nameservers names against a particular IP address), which you could download and submit. IIRC there was no chargge. But it did take a week or two to process. Once done you can use your .co.nz (etc) nameserver names that you've registered in your .com zone files, delegation recorsd, etc. If you don't want to wait that long, the quick hack (which I've used before) is smiply to add some extra A records into your .com zone for the nameservers (ns1.example.com, ns2.example.com pointing at the correct IP addresses), and then register the .com zone with those nameservers as the ones for the delegation. At least the NSI system, and maybe others, can then insert the necessary glue records when you do it that way. But it does mean you have two names for your nameservers. Ewen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Complex DNS problem
by Gavin 09 May '01

09 May '01

Hi, I am not sure if this is the right place to ask this, but domainz have not been able to help and suggested this list. We are a ChCh company with our own class C address, and as we were active on the net long before there were registrars or agents we do not have one -- I presume we are in effect our own registrar for the .nz namespace. We now have a .com name and wish to redirect accesses to this domain name back to our .nz address, and to do this we have to register our nameserver(s) with the Internic. The US registrar for our .com address cannot do this for us -- they say our registrar must do this for us -- but we don't have one. Domainz cannot do this either. I didn't choose the US registrar, and the particular registrar that was chosen for me in the US cannot register ccTLD's -- is this the root of the problem ?. Is anyone able to point me in the right direction ? TIA, -- Regards, Gavin Melville, gavin(a)cypher.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

What the NZ Internet looks like
by Juha Saarinen 08 May '01

08 May '01

http://www.cs.bell-labs.com/who/ches/map/gallery/tld/nz.gif I think I'm there, just below uummm.... you know, that other node. -- Juha The malformed orange Fails to satisfy the eye: Segmentation fault. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 13

Unknown IP's on APE
by Simon Blake 07 May '01

07 May '01

Hi Folks would the entities using 192.203.154.10 192.203.154.30 please get in contact with me, so that I can complete my population of the APE DNS. Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

RE: Asia On-line not?
by Richard Parry 07 May '01

07 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hey Phillip; > As one of Asia On Lines upstreams, I would like to make it clear > that TelstraSaturn do not have any current issues within our > network. Interesting. Personally I don't mind either way, just relating what we've been told. The latest is that they believe it's a possible attack on their network of some kind, but this is markedly different information than what's been flowing through until earlier today. As an aside, do you count Wellington's cable modem network as a part of your network? :) > I would suggest that AONZ themselves are probably best placed > to comment on any > problems they may be experiencing. Absolutely, however in an instance where someone (Peter) can't get to their network, it may be unlikely that they can effectively respond. Just trying to help. Richard - -- Richard Parry richard.parry(a)optimation.co.nz Phone: +64 4 470 5814 x 848 Optimation New Zealand Limited Pager: richardp.pager(a)optimation.co.nz Fax: +64 4 472 7219 PGP Fingerprint: 603F ECBD B38B 09F8 9601 F438 6131 D23F -----BEGIN PGP SIGNATURE----- Version: PGP 7.0 iQEVAwUBOvdW8vVxtQ5VlW2tAQHmZQf/WTMzdLIEddx1jKDfQAbE5ek4h2KEw34T 4dZWnnvEBHW4eD6x/eDBzfkONYoo9wseLHeb229vNxpXprQmQbn14Z6sdEcqlAID BozXGgGfSD5sv+bGW+YEEKrc/ZIH0EJOfA5sFvKVNwkvvLzvhuFxpwJSppTCB08Q JlawalZ5HqkOPJeIDfGnOo+J2Z+9AZXHegWVs5GPcK+1AP+KQtW/TnE8ZWGwVDH3 Jk7aYUmAtCx/lGv42UgZJZ13IdhgkjLrrcibJFsJDr1VfztugWRNaVB3XzIPLgDv o4qsDfvJ0fl40gLkwsAYvzh9TRQ6cHDQstLw00tUXysTq2JngI0kWg== =6uRe -----END PGP SIGNATURE----- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Asia On-line not?
by Richard Parry 07 May '01

07 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hi Peter; We're an AOL (ho ho) customer, and have been experiencing problems of various nature over the past few days. I understand that mostly, it is related to their upstream provider, and a lot of problems may have had to do with their caching engine. Probably the best bet is to contact them with your concerns. We're having some intermittent DNS issues, but mostly it's to do with ftp and http (http over ssl, and other services like email, mostly work 100%). Kind regards Richard Parry - -- Richard Parry richard.parry(a)optimation.co.nz Phone: +64 4 470 5814 x 848 Optimation New Zealand Limited Pager: richardp.pager(a)optimation.co.nz Fax: +64 4 472 7219 PGP Fingerprint: 603F ECBD B38B 09F8 9601 F438 6131 D23F > -----Original Message----- > From: Peter Mott [mailto:peter.mott(a)2day.com] > Sent: Tuesday, 8 May 2001 8:59 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Asia On-line not? > > > Does anybody here have any routing problems to iconz at this time? > > We dont appear to be seeing ns1.iconz.co.nz which may be > needed to resolve > names to numbers from time to time > > <cant get www.idg.net.nz daily fix!> > > Peter Mott > Chief Enthusiast > 2day.com > -/- > > --------- > To unsubscribe from nznog, send email to > majordomo(a)list.waikato.ac.nz where the body of your message reads: > unsubscribe nznog > -----BEGIN PGP SIGNATURE----- Version: PGP 7.0 iQEVAwUBOvcjTvVxtQ5VlW2tAQHoRgf/TIgiHRcZrB0RE+mTeK9Cec3H+uVt9zT2 NaazytIVysuajt6A25rl5ngA/qbcnl9Eh8Ev0iLDvnsW3KUj7LZsSliWRZWccb3r LMJD0a37L0sEpQlOm4+eqMZVviN0HXPD6iVVEuJfPzb+iD44idwgcL84GtE6Mvyu cKOaEnVU90Ntk/BbbnX7QKV0Qf+DGIvocoiBUJn1qEHkFk4PgCCBNJgxZoBhhZR0 K0/nyQBHgqf8+wDWMfWIfu2/IOsUUswG/JbO/7KKvANhhVpPra9yVv4NwjoRSObO 6X8Jlhr+SFKajrOa+RNmVPgJSxGnqW7beAksAuJmLy2HJ4fFOi6Bsg== =OHax -----END PGP SIGNATURE----- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

YOUR GROUND FLOOR BLAST TO 7 FIGURES B/4 CHRISTMAS!
by Reginald Tchume 07 May '01

07 May '01

=============== VERY EXCLUSIVE! =============== http://cybh.com Your exclusive invitation to earn seven figures b/4 Christmas is our urgent announcement, if you can use the money! This is NEW .. . . and GROUND FLOOR! A simple, systematic use of leverage to generate large incomes from multiple businesses is your tool at http://cybh.com This full automation on 24/7 autopilots allows you to work one hour a day referring customers and earn up to six figures monthly with the CybH. It's totally risk-free! And for a meager $39.95 of a one time start-up cost, you should blast pass every obstacle to secure your position now! Get your CybH now at http://CybH.com You can start making money with it right away. Thank you greatly! Your CybH team http://cybH.com --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Outage at APE Monday 7 May 2001
by Richard Naylor 06 May '01

06 May '01

Switch Outage at APE - Monday 7 May 2001. There MAY be a small outage of the APE core switch on Monday morning, 7 May, while the switch is replaced with one of larger capacity. We expect this to be at around 10am. The replacement will be done live so the visible outage will be only the time the switch takes to notice that MAC addresses have shifted ports. There will be other work done in the APE facility at the same time, including the addition of several new connections and at least one upgrade. Any business hours questions should be via 04-917-0200, after hours via 04-385-9003 or I can be contacted on 021 897 089. Of course email works and I will check it over the week end. On a different subject, I am close to installing an ATM interface on the APE switch. I am interested in the level of interest in the network community for users to connect to APE (or WIX) via the various ATM networks. Anyone interested in ATM access to APE or WIX, please let me know ASAP. It won't happen on Monday, but as soon as I can lay my hands on some cards. Richard richard.naylor(a)citylink.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

APE switching -- L2 topology
by Chris Wedgwood 05 May '01

05 May '01

Can people with APE connectivity (privately, off the list) give me some idea of what kind of connectivity they have, whether it is a switch belonging to CLEAR, Citylink or whatever if they don't mind? I'd like to produce some kind of L2 'map' of the topology up there and also wonder if we are at the point were spanning tree might rears it ugly head. Thanks, --cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Apologies
by Frank Tyson 05 May '01

05 May '01

I apologies concerning my query on Proxy Servers I've had a couple of people email me privately suggesting it was off topic For me it was a question more about the Operational or Technical aspects of why some ISP's disallow access this way ___ [| |=|{)__ |___| \/ ) /|\ /| / | \ | \ For all your Web Design and Photography Frank Tyson Stokes Valley New Zealand Mobile 021 134 1826 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Issues regarding Access through Proxy Servers to clients homepages via FTP
by Frank Tyson 04 May '01

04 May '01

I understand various providers restrict access to their clients homepages via FTP e.g Slingshot doesnt allow you to access your pages through a proxy server at Polytechnic or University This is a pain in the proverbial A**se because the course Im completing is Cybertech/E Commerce /Web Design and as part of my project I am required to create and maintain my own site Sure its fine when this can be done from home but in some cases I need to be able to do this from class An example would be creating the site at home then zipping it up uploading the zip to my homepages, extracting it at polytech to work on a particular section then loading the completed site back to my provider Currently the only way to load it is by having 2 email addresses and transfering stuff between them unless anyone has a different idea Ok you may suggest using an outfit like Tripod etc but I dont want my project cluttered with thier adverts popups etc When one looks at some of the public domain sites they have the faciality for transfering stuff via FTP built into the site rather than having to run a seperate program Maybe its something that could be looked at hear with NZ ISP's If one of you is running a server which allows access via FTP through Proxy Servers and of course rates and conditions are reasonable let me know I may have to consider switching providers who knows lol ___ [| |=|{)__ |___| \/ ) /|\ /| / | \ | \ For all your Web Design and Photography Frank Tyson Stokes Valley New Zealand Mobile 021 134 1826 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

��Flying Shose!!��Flying Shose!!
by t169668736＠yahoo.com 03 May '01

03 May '01

1 0

RE: Connection to APE
by Brett Telfer 01 May '01

01 May '01

We can provide you an alternative BB solution, as we also have close relationships with a number of ISP's, and have a presence at the APE. Without getting into a sales pitch, we may also be able to offer you some local benefits as well :-) Contact me off-line if you're interested. Regards Brett Telfer Development Project Manager WALKER WIRELESS LIMITED Tel: +64 (9) 522 3699 Fax: +64 (21) 559 833 Mobile: +64 (21) 434 600 0800 NO NETLAG --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Connection to APE
by Seeby Woodhouse - Orcon 01 May '01

01 May '01

Hi there People We (Orcon Internet) have been considering a connection to APE for quite some time, and it is becoming more and more important for us to get this set up. The reason is that our Global Gateway domestic connection does not connect satisfactorily to a number of NZ ISP's (e.g. Asia Online), and this is important to us because otherwise we have to pay International rates to connect to them. Additionally, we have 30 NZ ISP's that sit behind our network and some of them have been expressing a desire for us to have a connection at APE as well. Because of the amount of traffic that we foward domestically, I don't think that a 2Mbit connection will surfice - so we will probably have to put in a 10Mbit link. Obviously a 10Mbit link needs to be carried over ATM or IPExpress. we don't want to use IPExpress to connect to the sky tower as I am concerned that if the quality of the service gets bad (packet loss / latency - Clear make no QoS guarantees on IPExpress), then BGP is not going to fall over to our Global Gateway Domestic - even if that is faster. So our only other option is to use ATM. However, Telecom tell us that if we want to purchase a 10Mbit PVC up the sky tower, then we need to have an ATM to terminate it on (which is going to cost us $4k for the ATM + The PVC charge + An ATM router + telehousing - which is expensive!) Clear offer a service where if you purchase a Frame Relay, IPExpress or ATM, then you can get a connection to APE for free (they just terminate it up the sky tower on their own equipment I guess) - but Telecom does not seem to do this. Anyone know how we can get a 10Mbit connection to APE via our Telecom ATM without having to pay for all the associated access fees at the sky tower end? Cheers Seeby Orcon Internet - www.orcon.net.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

The New Zealand Network Operators' Group
by Donald Neal 30 Apr '01

30 Apr '01

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. This list has around 220 subscribers, growing by a handful each month. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations (nor the administrator) is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. Some discussion is taking place on the list at present regarding the acceptability of postings advertising for sale second-hand networking equipment. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ To search the archive, see http://list.waikato.ac.nz/archives/search.html (and remember to select nznog). Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog There are at present no restrictions on who may subscribe to the list, or even on who may post to the list. Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Other Activities NZNOG does not at present have other regular activities than this mailing list. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Off topic.... but .......
by Roger De Salis 29 Apr '01

29 Apr '01

April 27, 2001 Sony to release Linux for PS2 By STEPHEN SHANKLAND, CNET NEWS.COM Linux fans who want to run their favorite operating system on the Sony PlayStation 2 game console apparently will get what they've been hoping for. On Friday, Sony posted information on the Beta Release 1 of its PlayStation 2 Linux Kit, including a press release on its Japanese site that puts its price tag at 25,000 yen, or about $200. The kit includes a DVD with software, 40GB hard drive, keyboard and mouse. The beta, or test, version will be available in June. More than 6,000 people signed a petition earlier this year to encourage Sony to work on the project. The PlayStation 2 is powered by a MIPS chip. One of the benefits of Linux is that it's comparatively easy to get it working on different CPUs. Sony selected Linux to help game developers simulate the PlayStation 2 so they could get a jump on creating games before the actual hardware was available. Running Linux on the game console itself, though, is a different matter entirely. Rumors of the possibility have been circulating on Slashdot, a news and discussion site popular with Linux fans. The programming blueprints, or source code, for the kernel--the heart of Linux--is included on the DVD, Sony said. But the source code for a proprietary "runtime environment" that lets games play on the system is not. -- \_ Roger De Salis Cisco Systems NZ Ltd </' +64 25 481 452 L8, ASB Tower, 2 Hunter St /) +64 4 496 9003 Wellington, New Zealand (/ roger(a)desalis.gen.nz rdesalis(a)cisco.com ` 4/4/01. Mike Volpi, Cisco's chief strategy officer, announces four key markets: VOIP, wireless LANs, content networking, streaming media. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Buy & Sale of used network equipment
by Bart Kindt 26 Apr '01

26 Apr '01

I often feel the need to either put up for sale network related equipment, or parts thereof, or ask for certain gear. For example, routers, Max boxes, Cisco routers cards (we have some which we don't use anymore, and others we may need), etc. The nznog list is not to be used for 'commercial' purposes... But it is silly if the NZ network managers could all benefit of trading used equipment, but we cannot use this mailing list for it. So, I would like to suggest that either this list is ammended to allow 'trading' of used network related equipment, or that we set up a separate list for this purpose. Comments? Bart Bart Kindt Director, Network Operations The Internet Group Limited New Zealand --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 8

Max 4000 Power Supplies
by Matt Camp 25 Apr '01

25 Apr '01

Anyone know where to source some reasonably cheap Max 4000 Power Supplies? Or a good place to get some fixed? I've got a bunch here all with the same transformer-sans-MagicSmoke. --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

RE: Buy & Sale of used network equipment
by Lindsay Druett 25 Apr '01

25 Apr '01

Flyin Shose! Flyin Shose! How much ? --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: Max 4000 Power Supplies
by Bart Kindt 25 Apr '01

25 Apr '01

At 09:30 26/04/01 +1200, Matt Camp wrote: > >Anyone know where to source some reasonably cheap Max 4000 Power Supplies? > >Or a good place to get some fixed? I've got a bunch here all with the same >transformer-sans-MagicSmoke. We have some max4000-V34 for sale, $2000 a piece. Could be your solution ?? Bart Bart Kindt Director, Network Operations The Internet Group Limited New Zealand --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

How to make $500,000+ with $25
by nshasy＠sinaman.com 25 Apr '01

25 Apr '01

Dear Friends & Future Millionaires: AS SEEN ON NATIONAL TV: Making over half million dollars every 4 to 5 months from your home for an investment of only $25. Dollars expense one time. THANKS TO THE COMPUTER AGE AND THE INTERNET ! -------------------------------------------------------------------------------- BE A MILLIONAIRE LIKE THESE OTHERS WITHIN A YEAR!!! Before you say ''Bull'', please read the following. This is the letter you have been hearing about on the news lately. Due to the popularity of this letter on the Internet, a national weekly news program recently devoted an entire show to the investigation of this program described below, to see if it really can make people money. The show also investigated whether or not the program was legal. Their findings proved once and for all that there are ''absolutely NO Laws prohibiting the participation in the program and if people can -follow the simple instructions, they are sound to make some mega bucks with only $25 out of pocket cost''. DUE TO THE RECENT INCREASE OF POPULARITY & RESPECT THIS PROGRAM HAS ATTAINED, IT IS CURRENTLY WORKING BETTER THAN EVER. This is what one had to say: '' Thanks to this profitable opportunity. I was approached many times before but each time I passed on it. I am so glad I finally joined just to see what one could expect in return for the minimal effort and money required. To my astonishment, I received total $ 610,470. 00 in 21 weeks, with money still coming in''. Pam Hedland. Fort Lee, New Jersey. -------------------------------------------------------------------------------- Here is another testimonial: ''' this program has been around for a long time but I never believed in it. But one day when I received this again in the mail I decided to gamble my $25 on it. I followed the simple instructions and walaa ..... 3 weeks later the money started to come in. First month I only made $240.00 but the next 2 months after that I made a total of $290,000.00. So far, in the past 8 months by re-entering the program, I have made over $710,000.00 and I am playing it again. The key to success in this program is to follow the simple steps and NOT change anything.'' More testimonials later but first, %% PRINT THIS NOW FOR YOUR FUTURE REFERENCE $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ If you would like to make at least $500,000 every 4 to 5 months easily and comfortably, please read the following...THEN READ IT AGAIN and AGAIN !! $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR FINANCIAL DREAMS WILL COME TRUE, GUARANTEED! INSTRUCTIONS: =====Please order all 5 reports as shown on the list below ===== For each report, send $5 CASH, THE NAME & NUMBER OF THE REPORT YOU ARE ORDERING and YOUR E-MAIL ADDRESS to the person whose name appears ON THAT LIST next to the report. MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE TOP LEFT CORNER in case of any mail problems. When you place your order, make sure you order each of the 5 reports. You will need all 5 reports so that you can save them on your computer and resell them. YOUR TOTAL COST $5 X 5=$25.00. Within a few days you will receive, vie email, each of the 5 reports from these 5 different individuals. Save them on your computer so they will be accessible for you to send to the 1,000's of people who will order them from you. Also make a floppy of these reports and keep it on your desk in case something happen to your computer. IMPORTANT - DO NOT alter the names of the people who are listed next to each report, or their sequence on the list, in any way other than what is instructed below in step '' 1 through 6 '' or you will loose out on majority of your profits. Once you understand the way this works, you will also see how it does not work if you change it. Remember, this method has been tested, and if you alter, it will NOT work !!! People have tried to put their friends/relatives names on all five thinking they could get all the money. But it does not work this way. Believe us, we all have tried to be greedy and then nothing happened. So Do Not try to change anything other than what is instructed. Because if you do, it will not work for you. Remember, honesty reaps the reward!!! 1.... After you have ordered all 5 reports, take this advertisement and REMOVE the name & address of the person in REPORT # 5. This person has made it through the cycle and is no doubt counting their fortune. 2.... Move the name & address in REPORT # 4 down TO REPORT # 5 3.... Move the name & address in REPORT # 3 down TO REPORT # 4 4.... Move the name & address in REPORT # 2 down TO REPORT # 3 5.... Move the name & address in REPORT # 1 down TO REPORT # 2 6.... Insert YOUR name & address in the REPORT # 1 Position. PLEASE MAKE SURE you copy every name & address ACCURATELY! -------------------------------------------------------------------------------- **** Take this entire letter, with the modified list of names, and save it on your computer. DO NOT MAKE ANY OTHER CHANGES. Save this on a disk as well just in case if you loose any data. To assist you with marketing your business on the internet, the 5 reports you purchase will provide you with invaluable marketing information which includes how to send bulk e-mails llegally, where to find thousands of free classified ads and much more. there are 2 Primary methods to get this venture going: METHOD # 1: BY SENDING BULK E-MAIL LEGALLY -------------------------------------------------------------------------------- Let's say that you decide to start small, just to see how it goes, and we will assume You and those involved send out only 5,000 e-mails each. Let's also assume that the mailing receive only a 0.2% response (the response could be much better but lets just say it is only 0.2%. Also many people will send out hundreds of thousands e-mails instead of only 5,000 each). continuing with this example, you send out only 5,000 e-mails. With a 0.2% response, that is only 10 orders for report # 1. Those 10 people responded by sending out 5,000 e-mail each for a total of 50,000. Out of those 50,000 emails only 0.2% responded with orders. That's 100 people responded and ordered Report # 2. Those 100 people mail out 5,000 e-mails each for a total of 100,000 e-mails. The 0.2% response to that is 1000 orders for Report # 3. Those 1000 people send out 5,000 e-mails each for a total of 5 million e-mails sent out. The 0.2% response to that is 10,000 orders for Report. Those 10,000 people send out 5,000 e-mails each for a total of 50,000,000 (50 million) e-mails. The 0.2% response to that is 100,000 orders for Report # 5 THAT'S 100,000 ORDERS TIMES $5 EACH $500,000.00 (half million). Your total income in this example is: 1..... $50 + 2..... $500 + 3..... $5, 000 + =..... $50,000 + 5..... $500,000 ........ Grand Total $555,550. 00 NUMBERS DO NOT LIE. LET A PENCIL & PAPER AND FIGURE OUT THE WORST POSSIBLE RESPONSES AND NO MATTER HOW YOU CALCULATE IT, YOU WILL STILL MAKE A LOT OF MONEY ! -------------------------------------------------------------------------------- REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE ORDERING OUT OF 5,000 YOU MAILED TO. Dare to think for a moment what would happen if everyone or half or even one 4th of those people mailed 100,000 e-mails each or more? there are over 150 million people on the Internet worldwide and counting. Believe me, many people will do just that, and more! METHOD # 2 : BY PLACING FREE ADS ON THE INTERNET -------------------------------------------------------------------------------- Advertising on the net is very very inexpensive and there are hundreds of FREE places to advertise. Placing a lot of free ads on the internet will easily get a larger response. We strongly suggest you start with method # 1 and add METHOD # 2 as you go along. For every $5 you receive, all you just do is e-mail them the Report they ordered. That's it. Always provide same day service on all orders. This will guarantee that the e-mail they send out, with your name and address on it, will be prompt because they can not advertise until they receive the report. ===========AVAILABLE REPORTS ==================== ORDER EACH REPORT BY ITS NUMBER & NAME ONLY. Notes: Always send $5 cash (U.S. CURRENCY) for each Report. Checks NOT accepted. Make sure the cash is concealed by wrapping it in at least 2 sheets of paper. On one of those sheets of paper, Write the NUMBER & the NAME of the Report you are ordering, YOUR E-MAIL ADDRESS and your name and postal address. PLACE YOUR ORDER FOR THESE REPORTS NOW : -------------------------------------------------------------------------------- Report #1: The Insider's Guide To Advertising for Free On The Net. Order Report #1 from: Stephen Au Flat D, 10/F, Block 5, Locwood Court Kingswood Villas, Tin Shui Wai Yuen Long Hong Kong ___________________________________________________ REPORT #2: The Insider's Guide To Sending Bulk Email On The Net. Order report #2 from: Marc Hansen 615, Avenue Mozart F-13100 Aix-en-Provence France Europe ___________________________________________________ REPORT #3: Secret To Multilevel Marketing On The Net. Order Report #3 from : Pete Gallagher 2082 Newbury Rd. #14 Newbury Pk., CA 91320 ___________________________________________________ REPORT #4: How To Become A Millionaire Utilizing MLM & The Net. Order Report #4 from: Sonja MacKenzie RR#25 1032 Orange Rd. Roberts Creek, BC VON 2W5 CANADA ___________________________________________________ REPORT #5: How To Send Out One Million Emails For Free. Order Report #5 From: Kimik P. O. Box 175 Alta Loma, CA 91701-0175 USA ___________________________________________________ $$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$ Follow these guidelines to guarantee your success: === If you do not receive at least 10 orders for Report #1 within 2 weeks, continue sending e-mails until you do. === After you have received 10 orders, 2 to 3 weeks after that you should receive 100 orders or more for REPORT # 2. If you did not, continue advertising or sending e-mails until you do. === Once you have received 100 or more orders for report # 2, YOU CAN RELAX, because the system is already working for you, and the cash will continue to roll in ! THIS IS IMPORTANT TO REMEMBER: Every time your name is moved down on the list, you are placed in front of a Different report. You can KEEP TRACK of your PROGRESS by watching which report people are ordering from you. IF YOU WANT TO GENERATE MORE INCOME SEND ANOTHER BATCH OF E-MAILS AND START THE WHOLE PROCESS AGAIN. There is NO LIMIT to the income you can generate from this business !!! -------------------------------------------------------------------------------- FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS PROGRAM: You have just received information that can give you financial freedom for the rest of your life, with NO RISK and JUST A LITTLE BIT OF EFFORT. You can make more money in the next few weeks and months than you have ever imagined. Follow the program EXACTLY AS INSTRUCTED. Do Not change it in any way. It works exceedingly well as it is now. Remember to e-mail a copy of this exciting report after you have put your name and address in Report #1 and moved others to #2 ..........# 5 as instructed above. One of the people you send this to may send out 100,000 or more e-mails and your name will be on every one of them. Remember though, the more you send out the more potential customers you will reach. So my friend, I have given you the ideas, information, materials and opportunity to become financially independent. IT IS UP TO YOU NOW ! ============MORE TESTIMONIALS================== '' My name is Mitchell. My wife, Jody and I live in Chicago. I am an accountant with a major U.S. Corporation and I make pretty good money. When I received =his program I grumbled to Jody about receiving ''junk mail''. I made =un of the whole thing, spouting my knowledge of the population and percentages involved. I ''knew'' it wouldn't work. Jody totally ignored my supposed intelligence and few days later she jumped in with both feet. I made merciless fun of her, and was ready to lay the old ''I told you so'' on her when the thing didn't work. Well, the laugh was on me! Within 3 weeks she had received 50 responses. within the next 45 days she had received total $ 147,200.00 .......... all cash! I was shocked. I have joined Jody in her ''hobby''. Mitchell Wolf, M.D. Chicago, Illinois. =================================================== '' Not being the gambling type, it took me several weeks to wake up my mind to participate in this plan. But conservative that I am, I decided that the initial investment was so little that there was just no way that I couldn't get enough orders to at least get my money back''. '' I was surprised when I found my medium size post office box crammed with orders. I made =319,210. 00 in the first 12 weeks. The nice thing about this deal is that it does not matter where people live. There simply isn't a better investment with a faster return and so big''. Dan Sondstrom. Alberta, Canada. =================================================== '' I had received this program before. I deleted it, but later I wondered if I should have given it a try. Of course, I had no idea who do contact to get another copy, so I had to wait until I was e-mailed again by someone else.........11 months passed then it luckily came again...... I did not delete this one! I made more than $490,000 on my first try and all the money came within 22 weeks''. Susan De Suza. New York, N.Y. -------------------------------------------------------------------------------- '' It really is a great opportunity to make relatively easy money with little cost to you. I followed the simple instructions carefully and within 10 days the money started to come in. My first month I made $ 20, 560.00 and by the end of third month my total cash count was $ 362,840.00. Life is beautiful, Thanx to internet''. Fred Dellaca. Westport, New Zealand. -------------------------------------------------------------------------------- ORDER YOUR REPORTS TODAY AND GET STARTED ON YOUR ROAD TO FINANCIAL FREEDOM ! -------------------------------------------------------------------------------- FOR YOUR INFORMATION.... If you need help with starting a business, registering a business name, learning how income tax is handled, etc., contact your local office of the Small Business Administration (a Federal agency) 1-(800)827-5722 for free help and answers to questions. Also, the Internal Revenue Service offers free help via telephone and free seminars about business tax requirements. Under Bill S1618 Title III passed by the 105th US Congress this letter cannot be considered spam as long as the sender includes contact information and a method of removal. This is a one time e-mail transmission. No request for removal is necessary. If you have any questions of the legality of this program, contact the Office of Associate Director for Marketing Practices, Federal Trade Commission, Bureau of Consumer Protection, Washington, D.C. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Flying Shose!!��Flying Shose!!
by i46157184＠hotmail.com 21 Apr '01

21 Apr '01

1 0

MBGP
by James Tyson 16 Apr '01

16 Apr '01

Sorry about the cross-posting. I wanted to ask who would be willing to set up MBGP across APE or WIX (it's pretty easy, you just need to extend the capabilities of your current sessions with a new address-family). All interested say "Aye" and I will post instructions on the mbone-nz list for IOS<12.1 IOS>12.1 (they changed it) and Zebra I was really hoping that the guys at Citylink would be willing to set the route-reflectors up to do it also. Cheers. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: MBGP
by James Tyson 16 Apr '01

16 Apr '01

#include <tumbleweed.h> Cheers. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Humour
by Roger De Salis 15 Apr '01

15 Apr '01

In these possibly humour impaired times...... it is not often one gets a giggle at competitors equipment. Here is a picture of a recently announced IP phone from a Canadian vendor :-) (Hard hat-on, iron-underpants in place, Cisco product abuse shields operational.... Warp speed Mr Sulu.......) :-) -- \_ Roger De Salis Cisco Systems NZ Ltd </' +64 25 481 452 L8, ASB Tower, 2 Hunter St /) +64 4 496 9003 Wellington, New Zealand (/ roger(a)desalis.gen.nz rdesalis(a)cisco.com ` 4/4/01. Mike Volpi, Cisco's chief strategy officer, announces four key markets: VOIP, wireless LANs, content networking, streaming media.

7 10

Make your web site fun to view!
by joan343＠wilcox.org 14 Apr '01

14 Apr '01

Make your Web Site fun to visit while increasing your traffic by adding iCards Greetings. For as little as $19.95 per month you can have iCards Greetings running on your web site. Give your visitors a reason to keep coming back again and again, all while creating new first time visitor. And best of all, we do all the work. 1. All pages customized with your background, colors and logo. 2. New iCard Greetings added regularly. 3. All bandwidth is on our server. 4. Application maintenance and updates are all done by us. 5. Statistical Reports to monitor activity. Once set up, usually within 24 hours, just sit back and watch your traffic grow. Each time a visitor sends an iCard Greeting to a friend or family, you have just created a new visitor to your web site. As time goes on the 'snow ball' effect will increase your web site traffic tremendously. Best of all it requires absolutely no work of any kind on your part, everything is done automatically. No long term commitment or obligation. You have nothing to lose and everything to gain. Mention this email and receive the first month FREE. Take a look at www.SendiCards.com and see for yourself how much fun iCard Greetings can be. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

Slingshot Having Security Problems
by slingshot 11 Apr '01

11 Apr '01

As a customer I see there was major issues with security on the network Today they were down at least 12 hours from around 6am - 6pm All customers have been asked to change passwords Frank --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

RE: Cisco Field Notice: 12SP+/30VIP Phone Intl. Pwr. Cube Potenti al
by Lindsay Druett 09 Apr '01

09 Apr '01

(Hard hat-on, iron-underpants in place, Cisco product abuse shields operational.... Warp speed Mr Sulu.......) -----Original Message----- From: imnot telling [mailto:tellingimnot(a)hotmail.com] Sent: Tuesday, 10 April 2001 09:44 To: nznog(a)list.waikato.ac.nz Subject: Cisco Field Notice: 12SP+/30VIP Phone Intl. Pwr. Cube Potential "user may be exposed to live terminals at high voltage", but at least they look neater than an unamed Canadian competitors product. -----Original Message----- From: CCO Field Notice [mailto:cco-valet(a)cisco.com] Subject: Cisco Field Notice: 12SP+/30VIP Phone Intl. Pwr. Cube Potential Safety Hazard --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

Cisco Field Notice: 12SP+/30VIP Phone Intl. Pwr. Cube Potential
by imnot telling 09 Apr '01

09 Apr '01

"user may be exposed to live terminals at high voltage", but at least they look neater than an unamed Canadian competitors product. -----Original Message----- From: CCO Field Notice [mailto:cco-valet(a)cisco.com] Subject: Cisco Field Notice: 12SP+/30VIP Phone Intl. Pwr. Cube Potential Safety Hazard The product affected is currently NOT IN ANY PROFILE therefore a mass mailing to our entire mailing list is necessary. This e-mail is coming to you courtesy of the Cisco Connection Online Field Notice tool. Thank you for indicating through your interest profile that you wish to receive these alerts. For information, features or helpful hints about Cisco's Field Notices, please go to: http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice?action=he… Want to change your Alert Profile or create a new one? Please go to: http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice Title: Field Notice: 12SP+/30VIP Telephone International Power Cube Potential Safety Hazard URL: http://www.cisco.com/warp/customer/770/fn13042.shtml Posted: April 5, 2001 Summary: A potential safety hazard may occur when the 12SP+/30VIP telephone is not used with international power converter cubes and power cords provided by Cisco. Some non-Cisco-approved power cords may fit too snugly into the cube AC power supply inlet receptacle ("the receptacle"). In this situation the receptacle may be dislodged from the cube housing when attempts are made to extract the power cord plug. If the receptacle becomes dislodged, the user may be exposed to live terminals at high voltage. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZ Undernet server
by Pete 07 Apr '01

07 Apr '01

Hi all Does anyone know of a public Undernet IRC server within 'NZ' ? After receiving a HUGE bill from my isp for traffic to the SanDiego server I'm keen to find another 'local' relay. I note that auckland.nz.undernet.org is non-existant now. Thanks in advance Pete Pete Mundy - Technician Advanced Communications +64-3-546-9169 / +64-25-480-840 E-Mail: Pete(a)AdvComm.Co.NZ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

14 25

Fwd: Make a lot of money from your computer
by Leon Toh 06 Apr '01

06 Apr '01

Hi, It's good to see NZ have a Internet network list where most ISP's are subscribe to it. I still haven't locate 1 for Australia. I believe what this person did can be consider as spamming. From the mail header can anyone tell as to where this mail originated from. Are we able to do something about it. Best Regards, Leon >X-Persona: <Optus> >Return-Path: <owner-megaco(a)fore.com> >Received: from mx2.optushome.com.au ([203.164.2.11]) > by mss.rdc2.nsw.optushome.com.au > (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP > id > <20010406140639.CVBV17266.mss.rdc2.nsw.optushome.com.au(a)mx2.optushome.com.au> > for <leontoh(a)optushome.com.au>; Sat, 7 Apr 2001 00:06:39 +1000 >Received: from prserv.net (in5.prserv.net [32.97.166.41]) > by mx2.optushome.com.au (8.9.1/8.9.1) with ESMTP id AAA15381 > for <leontoh(a)optushome.com.au>; Sat, 7 Apr 2001 00:06:38 +1000 (EST) >Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) > by prserv.net (in5) with ESMTP > id <2001040614063610504kuur8e>; Fri, 6 Apr 2001 14:06:36 +0000 >Received: from mailman.pit.comms.marconi.com >(mailman.pit.comms.marconi.com [169.144.2.12]) > by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id > JAA28605; > Fri, 6 Apr 2001 09:57:35 -0400 (EDT) >Received: (from majordom(a)localhost) > by mailman.pit.comms.marconi.com (8.9.3/8.9.3) id JAA11559 > for megaco-list; Fri, 6 Apr 2001 09:55:02 -0400 (EDT) >Received: from mailgate.pit.comms.marconi.com >(mailgate.pit.comms.marconi.com [169.144.68.6]) > by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA11555 > for <megaco(a)fore.com>; Fri, 6 Apr 2001 09:55:00 -0400 (EDT) >From: quickwaynz(a)e247.com >Received: from mta6-rme.xtra.co.nz (mta6-rme.xtra.co.nz [203.96.92.19]) > by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id > JAA28233 > for <megaco(a)fore.com>; Fri, 6 Apr 2001 09:54:55 -0400 (EDT) >Received: from mail.xtra.co.nz ([210.54.103.7]) by mta6-rme.xtra.co.nz > with SMTP > id > <20010406134330.KNRK9352737.mta6-rme.xtra.co.nz(a)mail.xtra.co.nz>; > Sat, 7 Apr 2001 01:43:30 +1200 >To: Friend(a)public.com >Date: Sat, 07 Apr 01 01:28:31 EST >Subject: Make a lot of money from your computer >Message-Id: <20010406134330.KNRK9352737.mta6-rme.xtra.co.nz(a)mail.xtra.co.nz> >Sender: owner-megaco(a)pit.comms.marconi.com >Precedence: bulk > >Hi There >My name is Tim, I live in New Zealand. A few weeks ago I was sent a bulk >email and just >for a change I decided to read it. What it shows is a genuine way to make >thousands of >dollars in a very short time using the immense power of the internet. >Yes, it's a multi level marketing scheme. Yes, it's legal and YES, it >works. Rather than >bombard you with information by email, all I ask is that you click on my >site at >http://mysite.xtra.co.nz/~fastwaynz . There you will find all the >information you need . If you >have any questions WHATSOEVER, you can contact me by clicking EMAIL from >my site. >I will help make this work for you, just like it has for thousands of >people before us. >Please reserve your skepticism until after you have readhow it works. >Taking the plunge >is paying off better than I could have imagined. So thanks for reading >this far. Now check >out my site - it'll be the best ten minute read of your life. >Tim --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Fwd: RE: New hacking laws
by Mark Foster 02 Apr '01

02 Apr '01

I assume this was supposed to go to the list. >Delivered-To: blakjak-net-blakjak(a)blakjak.net >From: "David Buckingham" <david.buckingham(a)xtra.co.nz> >To: "Chris Wedgwood" <cw(a)f00f.org> >Subject: RE: New hacking laws >Date: Mon, 2 Apr 2001 19:37:34 +1200 >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) >Importance: Normal >Sender: owner-nznog(a)list.waikato.ac.nz > >Hello All, > >Aardvark (aardvark.co.nz) made a comment this morning, which touched >directly on something I put to the select committee (Law and Order) in my >submission on the new hacking laws. > >That is - that with the law proposed (which is the result of a law >commission report 54 - "computer misuse" - May 1999 see www.lawcom.govt.nz >for a copy) governing hacking, interception and so on, soon to come into >force, how is it going to be enforced? > >Enforcement of criminal law is by police prosecuting after an investigation. >Which poses one of the most important questions of all - do the police have >the resources, background and skills to make investigations into serious >computer crime?, or computer crime for that matter? > >My recommendation to the select committee was to have a special unit for >computer crime, which is adequately funded, which solely investigates these >types of offences. > >I am interested to hear some feedback. - I have copies of a number of >documents related to this issue - and if you would like for me to let you >know how to get your hands on this information please let me know. > >David Buckingham > >-----Original Message----- >From: owner-nznog(a)list.waikato.ac.nz >[mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Chris Wedgwood >Sent: Monday, 2 April 2001 5:57 p.m. >To: David Buckingham >Cc: nznog(a)list.waikato.ac.nz >Subject: Re: New hacking laws > >On Mon, Apr 02, 2001 at 04:01:20PM +1200, David Buckingham wrote: > > Would it be off topic to discuss the proposed new hacking laws? > > I am referring to the Crimes Amendment Bill (No.6) and its SOP 85. > >I see no reason why not... it's certainly more relevant than a lot of >what is discussed here. > > > > --cw >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog > >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 8

Re: Fwd: RE: New hacking laws
by Mark Foster 01 Apr '01

01 Apr '01

except that I didnt see a copy from the list.. :) At 20:07 2/04/2001 +1200, you wrote: >Fear, and respect the beauty of Bcc: > > >On Mon, 2 Apr 2001, Mark Foster wrote: > > > I assume this was supposed to go to the list. > > > > >Delivered-To: blakjak-net-blakjak(a)blakjak.net > > >From: "David Buckingham" <david.buckingham(a)xtra.co.nz> > > >To: "Chris Wedgwood" <cw(a)f00f.org> > > >Subject: RE: New hacking laws > > >Date: Mon, 2 Apr 2001 19:37:34 +1200 > > >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) > > >Importance: Normal > > >Sender: owner-nznog(a)list.waikato.ac.nz > > > > > >Hello All, > > > > > >Aardvark (aardvark.co.nz) made a comment this morning, which touched > > >directly on something I put to the select committee (Law and Order) in my > > >submission on the new hacking laws. > > > > > >That is - that with the law proposed (which is the result of a law > > >commission report 54 - "computer misuse" - May 1999 see www.lawcom.govt.nz > > >for a copy) governing hacking, interception and so on, soon to come into > > >force, how is it going to be enforced? > > > > > >Enforcement of criminal law is by police prosecuting after an > investigation. > > >Which poses one of the most important questions of all - do the police > have > > >the resources, background and skills to make investigations into serious > > >computer crime?, or computer crime for that matter? > > > > > >My recommendation to the select committee was to have a special unit for > > >computer crime, which is adequately funded, which solely investigates > these > > >types of offences. > > > > > >I am interested to hear some feedback. - I have copies of a number of > > >documents related to this issue - and if you would like for me to let you > > >know how to get your hands on this information please let me know. > > > > > >David Buckingham > > > > > >-----Original Message----- > > >From: owner-nznog(a)list.waikato.ac.nz > > >[mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Chris Wedgwood > > >Sent: Monday, 2 April 2001 5:57 p.m. > > >To: David Buckingham > > >Cc: nznog(a)list.waikato.ac.nz > > >Subject: Re: New hacking laws > > > > > >On Mon, Apr 02, 2001 at 04:01:20PM +1200, David Buckingham wrote: > > > > > > Would it be off topic to discuss the proposed new hacking laws? > > > > > > I am referring to the Crimes Amendment Bill (No.6) and its SOP 85. > > > > > >I see no reason why not... it's certainly more relevant than a lot of > > >what is discussed here. > > > > > > > > > > > > --cw > > >--------- > > >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > > >where the body of your message reads: > > >unsubscribe nznog > > > > > >--------- > > >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > > >where the body of your message reads: > > >unsubscribe nznog > > > > --------- > > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > > where the body of your message reads: > > unsubscribe nznog > > > > >Tim J. Shackleton ------------------+ +- Business http://www.netlink.co.nz/ >Networks Admin/Programmer ----------+ +- Personal http://www.netnet.net.nz/ >Netlink LTD -- DDI +64 4 922 8476 --+ +------------- Pager 64 +26 253 4356 >+64 29 650 476 -- Cellular ---------+ +------------------------------------ >----------------- " All your base are belong to us! " --------------------- > >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

New hacking laws
by David Buckingham 01 Apr '01

01 Apr '01

Afternoon, Would it be off topic to discuss the proposed new hacking laws? I am referring to the Crimes Amendment Bill (No.6) and its SOP 85. David Buckingham --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

RE: NZ Undernet server
by Steve Phillips 01 Apr '01

01 Apr '01

At 15:58 2/04/2001, Tim Shackleton wrote: >Nothing an old-fashioned lynching won't fix :) I'll donate the rope/baseball bat -- Steve. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

The New Zealand Network Operators' Group
by Donald Neal 01 Apr '01

01 Apr '01

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. This list has just under 220 subscribers, growing by a handful each month. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations (nor the administrator) is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ To search the archive, see http://list.waikato.ac.nz/archives/search.html (and remember to select nznog). Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog There are at present no restrictions on who may subscribe to the list, or even on who may post to the list. Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Other Activities NZNOG does not at present have other regular activities than this mailing list, though the administrator is on the hunt for presenters for the annual Uniforum NZ conference, to be held in the second half of the year. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Time for a change
by Andy Linton 29 Mar '01

29 Mar '01

Today's my last day at TelstraSaturn. I think it's also the end of an era for me. I've decided to take a break from being at the pointy end of IP operations - too many bellheads and not enough netheads for my liking. Of course, when the money runs out I may well be back grovelling for work. I'll still be on the list, lurking in a dark corner. So long and thanks for all the fish! andy --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Re: History of Internet in New Zealand to current date (Off Topic, but what the hell..)
by Mark Davies 29 Mar '01

29 Mar '01

From: "fwetyson" <fwetyson(a)slingshot.co.nz> Date: Wed, 28 Mar 2001 22:58:13 +1200 > Would be interested in the dates regarding VUW and Massey 1989 - about 6 months after the international link went in to Waikato having got fed up waiting for the computer centers to get something working. > Did these take place before Kawahiko and Tuia got on line > via NZGate? Yes. cheers mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 6

Re: History of Internet in New Zealand to current date (Off Topic, but what the hell..)
by Mark Davies 28 Mar '01

28 Mar '01

From: Geoff Huston <gih(a)telstra.net> Date: Wed, 28 Mar 2001 17:50:40 +1000 > Just a quick note from the other side of the Tasman - the earliest efforts > appeared to be at the Victoria University, Wellington, where the Computer > Science Department operated a modem-based trans-Tasman messaging service > through the eighties - I'm not sure whether the link used the uunet > protocols or the acsnet protocols, but I'm not sure thats all that > relevant. It linked up to a comparable Computer Science messaging network > in Australia. It was ACSnet to melbourne as well as uucp to Calgary and to uunet (actually it was initially seismo back in the pre uunet days). There was even a short period when email between here and canterbury went via calgary. > The first link was, as I recall, a 14.4Kbps analog modem > connection, installed in late 88 (or thereabouts) with NASA and NZ > funding. And the first NZ IP link out of Waikato was a slip link between here and there running over the DSIR's internal serial network with an 8086 based PCrouter at each end. That link ran at 9.6K though the DSIR constrained it to only 4.8K. That was quickly followed by a similar link from here to Massey. cheers mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re Messages from this list
by fwetyson 28 Mar '01

28 Mar '01

I checked my end and not CCing myself messages Whats the email command for checking my settings in the list Some lists allow you to change or reset your status this way Thanks in advance Frank Tyson Phone: 64211341826 Fax:+6445635927 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

www.ape.net.nz
by Simon Lyall 28 Mar '01

28 Mar '01

I've recently taken this over from Joe and it's now up on usenet.net.nz. Can people take a quick look and please email me any suggestions, updates and corrections for it. There are some errors and missing bits for participants on APE and other stuff needs fixed as well. http://www.ape.net.nz/ -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | | Home: simon(a)darkmere.gen.nz ihug, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

late DEW - 2q2001
by Bill Manning 28 Mar '01

28 Mar '01

Hi, I appologize for duplicates. Its almost time for the next quarterly walk of the inverse tree of the DNS. Since 1997, I've been walking the in-addr tree looking for numbers of delegations, accurate delegations, and types and styles of error conditions. So... this is a heads up that you will be seeing zone transfers being generated by a couple of the collecter machines here. For those of you who utilize BINDs access controls, I'd appreciate your inclusion of the collector machines in allowed transfers. The expectation is that they will be the following IP addresses: 128.9.160.57 and 198.32.4.13 If there are any questions or concerns, I'd be happy to talk about them. Past data has been presented at IEPG, Apricot and RIPE meetings. The expectation is that future data will be presented in the same and similar forums. Past data may be viewed at: http://www.isi.edu/~bmanning/in-addr-audit.html --bill 310.322.8102 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: History of Internet in New Zealand to current date (Off Topic, but what the hell..)
by Mark Davies 27 Mar '01

27 Mar '01

> > Did these take place before Kawahiko and Tuia got on line > > via NZGate? > Yes. I should have added "before any of these existed." mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: History of Internet in New Zealand to current date (Off Topic, but what the hell..)
by fwetyson 27 Mar '01

27 Mar '01

Thanks for the feed back folks Would be interested in the dates regarding VUW and Massey Did these take place before Kawahiko and Tuia got on line via NZGate? Frank Tyson Phone: 64211341826 Fax:+6445635927 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: History of Internet in New Zealand to current date (Off Topic)
by fwetyson 27 Mar '01

27 Mar '01

Thanks for the assistance some of you have given I see a note next to the thread that this subject is Off Topic Does that mean I cant raise the question here? If so thats a pity considering the major inovators of Internet here in NZ Appologies Frank Tyson Phone: 64211341826 Fax:+6445635927 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Messages from this list
by fwetyson 27 Mar '01

27 Mar '01

Could someone advise me why I get two copies of every posting to the list Thanks in advance Frank Tyson Phone: 64211341826 Fax:+6445635927 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Attica/Tranzpeer Prefix List
by James Tyson 27 Mar '01

27 Mar '01

Hi all! Attached is an updated prefix list for Tranzpeer[1], which includes Attica and Tranzpeer's customers. Tranzpeer will be moving to it's own AS number shortly, so those of you peering with us will recieve an email shortly asking you to change your peering session with us[2]. Cheers. James Tyson. Self-Deluded Governing Minority, Attica Network Operations. --- [1] Tranzpeer Limited is a wholesale bandwidth provider run by Attica [2] Does anyone know how to make a crisco router run multiple instances of BGP, because that would make it so much easier!

4 6

RE: History of Internet in New Zealand to current date
by Lindsay Druett 27 Mar '01

27 Mar '01

I would have thought the best person to ask about this subject would be John Haulker. Tim Williams seems to remember a lot about what happened... -----Original Message----- From: fwetyson [mailto:fwetyson(a)slingshot.co.nz] Sent: Wednesday, 28 March 2001 09:13 To: nznog(a)list.waikato.ac.nz Subject: History of Internet in New Zealand to current date Ive been lurking around watching the postings and discussions here for the last few months and felt this was the place to pose the following question? Where does one find accurate information regarding the History and Development of the Internet here in NZ ? Most information Ive read (with the exception of postings here) is circa 1997 In recent times there has been many courses in IT commencing in the various technical institutions and locating accurate up to date information has been a major effort The most recent I could find was at http://www.iscr.org.nz/documents/enright.pdf Most others as I said havent been updated prior to 1997 Considering the many years of experience here and the wide range of organisations maybe this needs to be reviewed Finally I appologise if this isnt the place to raise this discussion Frank Tyson Student CyberTechnology Hutt Valley Polytech --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

10 14

RE: History of Internet in New Zealand to current date
by Bart Kindt 27 Mar '01

27 Mar '01

At 09:14 28/03/01 +1200, Lindsay Druett wrote: >I would have thought the best person to ask about this subject would be John >Haulker. > >Tim Williams seems to remember a lot about what happened... > I started Efficient Software Internet in Dunedin in August 1994. Got my backbone via University of Otago, who got theirs from Waikato. John Haulker I talked a lot with in those days :) Nostalgia... Bart Bart Kindt Director The Internet Group Limited --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

History of Internet in New Zealand to current date
by fwetyson 27 Mar '01

27 Mar '01

Ive been lurking around watching the postings and discussions here for the last few months and felt this was the place to pose the following question? Where does one find accurate information regarding the History and Development of the Internet here in NZ ? Most information Ive read (with the exception of postings here) is circa 1997 In recent times there has been many courses in IT commencing in the various technical institutions and locating accurate up to date information has been a major effort The most recent I could find was at http://www.iscr.org.nz/documents/enright.pdf Most others as I said havent been updated prior to 1997 Considering the many years of experience here and the wide range of organisations maybe this needs to be reviewed Finally I appologise if this isnt the place to raise this discussion Frank Tyson Student CyberTechnology Hutt Valley Polytech --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

APE Switch
by Tony Wicks 26 Mar '01

26 Mar '01

Hi all, I note the 2912 switch that constitutes APE is full and has now been supplemented by a Dlink one. While Dick Smith may be quite happy selling these devices to their customers, I don't think it is entirely appropriate to be a central point for New Zealand's Internet traffic. Perhaps the nice people at Cisco ( or another civic minded manufacturer ) would like to donate something more appropriate for the task, like a 3548xl say ? --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

12 14

Ignore: Testing my mailfilter; sorry ;)
by Bart Kindt 25 Mar '01

25 Mar '01

To filter or not to filter, thats the question! Bart Bart Kindt Director The Internet Group Limited --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

mbone stuff
by James Tyson 24 Mar '01

24 Mar '01

Hi all. Just letting everyone know that I have set up a mailling list for NZ Network Operators that wish to discuss the nzmbone stuff without spamming this list. You can subscribe at: https://secure.samizdat.co.nz/mailman/listinfo/mbone-nz or by sending a subscribe message to mbone-nz-request(a)samizdat.co.nz Status update: IHUG & Attica are now live and streaming MP3 content, all content has been restricted to 233/8 space while formulation of a NZ mbone addressing schema. I am still waiting to hear from other ISP's wishing to become involved (hint hint). Cheers. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 8

New prefix list
by Tony Wicks 19 Mar '01

19 Mar '01

Below is a new prefix list for all of you that we are peering with. Can someone at Clear please post their current list, I get the feeling that my copy is a bit out of date. notes - added - 210.185.16.0/20 le 21,203.9.179.0/24 removed - several cheers ip prefix-list AONZ-networks description networks(a)nz.asiaonline.net ip prefix-list AONZ-networks seq 5 permit 202.14.100.0/24 ip prefix-list AONZ-networks seq 10 permit 210.48.0.0/17 le 18 ip prefix-list AONZ-networks seq 15 permit 192.173.16.0/21 ip prefix-list AONZ-networks seq 25 permit 202.6.84.0/24 ip prefix-list AONZ-networks seq 30 permit 202.12.70.0/24 ip prefix-list AONZ-networks seq 45 permit 202.36.76.0/23 ip prefix-list AONZ-networks seq 60 permit 202.37.85.0/24 ip prefix-list AONZ-networks seq 75 permit 202.37.140.0/22 ip prefix-list AONZ-networks seq 85 permit 202.37.144.0/21 ip prefix-list AONZ-networks seq 115 permit 202.37.197.0/24 ip prefix-list AONZ-networks seq 120 permit 202.37.200.0/22 ip prefix-list AONZ-networks seq 130 permit 202.37.224.0/21 ip prefix-list AONZ-networks seq 150 permit 202.49.144.0/24 ip prefix-list AONZ-networks seq 155 permit 202.50.16.0/20 ip prefix-list AONZ-networks seq 160 permit 203.99.65.0/24 ip prefix-list AONZ-networks seq 165 permit 203.99.66.0/24 ip prefix-list AONZ-networks seq 170 permit 203.99.71.0/24 ip prefix-list AONZ-networks seq 175 permit 210.54.0.0/22 ip prefix-list AONZ-networks seq 180 permit 138.235.0.0/16 ip prefix-list AONZ-networks seq 185 permit 203.9.179.0/24 ip prefix-list AONZ-networks seq 190 permit 203.9.180.0/24 ip prefix-list AONZ-networks seq 195 permit 210.185.16.0/20 le 21 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Wireless Internet Training Program Development
by Paul Ravi Kumar 15 Mar '01

15 Mar '01

Sir, I am a wireless consultant from India with about 8 years of communications experience. I am conducting research on "Anywhere anytime mobile/wireless Internet". I wish to know the details of your Wireless Internet Training Program Development. Kindly respond with necessary details as to enable me to enrol for the program. Regards Paul Ravi Kumar _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

(Fwd) The Webserver Plan
by Sue Leader 15 Mar '01

15 Mar '01

Greetings all - We have what I'm sure will be good news.... ------- Forwarded message follows ------- From: John Vorstermans <tech(a)isocnz.org.nz> Organization: Internet Society of NZ On Friday evening 16th March ISOCNZ will be moving their webserver in-house to their new premises. At this time the new "look and feel" site will come live. The changeover requires alterations to the ISOCNZ DNS which can take anywhere from several hours to several days to filter around the different ISPs etc. (depending on DNS refresh settings). This means that some people may not be able to get to the new site till later in the weekend. Cheers John -- John Vorstermans - Technical Manager ISOCNZ (Internet Society of New Zealand Inc) PO Box 11-881, Wellington ------- End of forwarded message ------- Cheers Sue Sue Leader - Executive Director Internet Society of New Zealand Inc PLEASE NOTE CHANGES: Voice: +64-4-472-1600 Fax: +64-4-472-1207 Level 4, Hibernian Building, 89 Willis Street (P.O.Box 11-881) Wellington http://www.isocnz.org.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

VOTE: .bank.nz
by Sue Leader 14 Mar '01

14 Mar '01

Greetings all I've just returned from the Melbourne ICANN meeting and have been offline because of equipment failure, so I apologise for the delay in posting this. The voting for the .bank.nz opened on Monday morning. If you wish to vote on this application please read the 'how to vote' information at: http://www.isocnz.org.nz/consult/2LD/how_to_vote.html. Please note to vote you must have an email address that ends in .nz. Voting will be open for 14 days and any questions regarding the voting can be sent to the Voting Officer at vote-help(a)isocnz.org.nz Cheers Sue Sue Leader - Executive Director ISOCNZ (Internet Society of New Zealand Inc) Exe.Dir(a)isocnz.org.nz Voice: +64-4-801-6256 http://www.isocnz.org.nz PLEASE NOTE CHANGE: P.O.Box 11-881, Wellington --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

RE: Kiwi spammer "Deco Marketing Solutions"
by Michael White 13 Mar '01

13 Mar '01

Just what the Internet needs, more bad press. Be careful the media is evil :) Mike > ---------- > From: Juha Saarinen > Sent: Wednesday, 14 March 2001 10:26 AM > To: Martin D Kealey; nznog(a)list.waikato.ac.nz > Cc: Russell_Brown(a)idg. co. nz; Paul_Brislen(a)idg. co. nz; Darren > Greenwood; Stephen Bell > Subject: RE: Kiwi spammer "Deco Marketing Solutions" > > Martin, > > I've cc'ed some IDG reporters, in the hope that they might pick up on this > and cobble together a "Scourge Of The Internet" type of expose... ;-) > > -- Juha > > :: -----Original Message----- > :: From: owner-nznog(a)list.waikato.ac.nz > :: [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Martin D Kealey > :: Sent: Wednesday, March 14, 2001 10:07 AM > :: To: nznog(a)list.waikato.ac.nz > :: Subject: Kiwi spammer "Deco Marketing Solutions" > :: > :: > :: Heads up, a local spam operation... > :: > :: Has anyone else been receiving spam from "email-prom.net" [12.42.24.22] > :: lately? The usual crap about how X million addressesee will buy > stuff... > :: > :: In this latest case the phone and fax numbers given are in > Ponsonby/Grey > :: Lynn and Orewa/Silverdale/Whangaparaoa areas respectively. > :: > :: A quick scan on call-minder for 09-3608038 reveals a mailbox > :: labelled "Deco > :: Marketing Solutions" (no information for the fax number 09-4268337). > The > :: previous message used a mailbox in North America, so I don't expect > they > :: actually live here, but on the off chance that they do, does anyone > know > :: anything about these guys? > :: > :: Normally I'd just firewall the IP, but if there's a chance of nailing > :: someone local I'll give them enough rope to hang themselves... > :: > :: And any suggestions as to what we should do with these two phone > numbers? > :: > :: -Martin > :: > :: ---------- Forwarded message ---------- > :: Received: from email-prom.net ([12.42.24.23]) > :: by smtp.sig.net.nz (8.9.3/NZSFI-20000705) with SMTP id VAA01285 > :: for <martin(a)kurahaupo.gen.nz>; Tue, 13 Mar 2001 21:01:37 +1300 > :: X-Authentication-Warning: mae.sub.net.nz: Host [12.42.24.23] > :: claimed to be > :: email-prom.net > :: Subject: FWD: Last Biz To Business Disc > :: Content-Type: text/plain; > :: charset=us-ascii > :: Content-Transfer-Encoding: 8BIT > :: X-Mailer: QI03122001MDNZ > :: Message-Id: <gcbinx81s4pg0grx.142o5n3n(a)email-prom.net> > :: Date: Tue, 13 Mar 2001 03:06:31 +0000 > :: Reply-To: md2000nz(a)email-prom.net > :: To: md2000nz(a)email-prom.net > :: > :: > :: You can now access contact data for over 8.5 Million Records. > :: All of them > :: have their own .com .org or .net domain name, making them > :: serious prospects > :: for Internet business. > :: > :: Our data base readily accessible on CD-Rom, list the Names, Contact > :: Information, Physical Address, Phone #, Fax #, SIC Industry > :: Code, URL (Domain > :: Name), and Contact Email Address which you can use to efficiently > target > :: companies worldwide. > :: > :: Over 8.5 Million Physical Addresses let you target businesses by > :: Country, > :: State, City, Province, Zip Code, Area Code or by using the SIC > :: Industry Code. > :: The data comes in a Comma-Delimited ASCII format which makes it easy to > :: manipulate and Import/Export records to your Contact-Management, > :: Spreadsheet, > :: analysis and Broadcasting Applications. > :: > :: > :: Please send me more info about: > :: > :: [ ] Master Disc 2000 8.5 Million Records, Cost US$799.00 > :: [ ] Online Updates & Download Access Cost US$199.00 (Annually) > :: [ ] Commercial Email Services & Products > :: > :: Note: Not all records contain complete data, call for breakdowns. > :: > :: For more details on Database, please call: > :: > :: #011-649-360-7038 (International) > :: > :: or fax form below to: > :: #011-649-426-8337 > :: > :: (Make Sure To Mention Reseller Id #1629 When Calling) > :: > :: > :: Company name: ___________________________________________ > :: > :: > :: Web Site Url: ___________________________________________ > :: > :: > :: Contact name: ___________________________________________ > :: > :: > :: Email: __________________________________________________ > :: > :: > :: Phone: __________________________________________________ > :: > :: > :: Fax: ___________________________________________________ > :: > :: > :: Street address: _________________________________________ > :: > :: > :: City, Zip, State: _______________________________________ > :: > :: > :: Country: ________________________________________________ > :: > :: > :: Check the following that apply: > :: > :: _____ Please Notify Me Of Online Web Site & Register Me > :: For Access Using The > :: Information Above. > :: > :: > :: Also Please, Send Additional Information on: > :: > :: _____ Online Adult & Gaming Owner/Operaters > :: _____ Online Adult Subscribers & Online Gamers Databases > :: _____ Online Billing/Credit Card Processing > :: _____ Emailing Services and Databases > :: _____ Search Engine Positioning > :: _____ International Contact Lists > :: _____ Buying / Selling Traffic > :: _____ Web Site Hosting Services > :: _____ Other:_______________________________ > :: > :: > :: ####################################################################### > :: To discontinue receipt of further notice and to be removed from our > :: database, please reply with the word "Remove" in subject. > :: > :: Any attempts to disrupt the removal email address etc., will not allow > :: us to be able to retrieve and process the remove requests. > :: ####################################################################### > :: > :: > :: .031201 > :: > :: --------- > :: To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > :: where the body of your message reads: > :: unsubscribe nznog > > > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Anybody know of a 3Ware importer in NZ?
by Simon Blake 13 Mar '01

13 Mar '01

Apologies for the non netops related, but this seems a good place to ask - does anybody know of an importer of 3Ware IDE raid cards in NZ? Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Kiwi spammer "Deco Marketing Solutions"
by Martin D Kealey 13 Mar '01

13 Mar '01

Heads up, a local spam operation... Has anyone else been receiving spam from "email-prom.net" [12.42.24.22] lately? The usual crap about how X million addressesee will buy stuff... In this latest case the phone and fax numbers given are in Ponsonby/Grey Lynn and Orewa/Silverdale/Whangaparaoa areas respectively. A quick scan on call-minder for 09-3608038 reveals a mailbox labelled "Deco Marketing Solutions" (no information for the fax number 09-4268337). The previous message used a mailbox in North America, so I don't expect they actually live here, but on the off chance that they do, does anyone know anything about these guys? Normally I'd just firewall the IP, but if there's a chance of nailing someone local I'll give them enough rope to hang themselves... And any suggestions as to what we should do with these two phone numbers? -Martin ---------- Forwarded message ---------- Received: from email-prom.net ([12.42.24.23]) by smtp.sig.net.nz (8.9.3/NZSFI-20000705) with SMTP id VAA01285 for <martin(a)kurahaupo.gen.nz>; Tue, 13 Mar 2001 21:01:37 +1300 X-Authentication-Warning: mae.sub.net.nz: Host [12.42.24.23] claimed to be email-prom.net Subject: FWD: Last Biz To Business Disc Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT X-Mailer: QI03122001MDNZ Message-Id: <gcbinx81s4pg0grx.142o5n3n(a)email-prom.net> Date: Tue, 13 Mar 2001 03:06:31 +0000 Reply-To: md2000nz(a)email-prom.net To: md2000nz(a)email-prom.net You can now access contact data for over 8.5 Million Records. All of them have their own .com .org or .net domain name, making them serious prospects for Internet business. Our data base readily accessible on CD-Rom, list the Names, Contact Information, Physical Address, Phone #, Fax #, SIC Industry Code, URL (Domain Name), and Contact Email Address which you can use to efficiently target companies worldwide. Over 8.5 Million Physical Addresses let you target businesses by Country, State, City, Province, Zip Code, Area Code or by using the SIC Industry Code. The data comes in a Comma-Delimited ASCII format which makes it easy to manipulate and Import/Export records to your Contact-Management, Spreadsheet, analysis and Broadcasting Applications. Please send me more info about: [ ] Master Disc 2000 8.5 Million Records, Cost US$799.00 [ ] Online Updates & Download Access Cost US$199.00 (Annually) [ ] Commercial Email Services & Products Note: Not all records contain complete data, call for breakdowns. For more details on Database, please call: #011-649-360-7038 (International) or fax form below to: #011-649-426-8337 (Make Sure To Mention Reseller Id #1629 When Calling) Company name: ___________________________________________ Web Site Url: ___________________________________________ Contact name: ___________________________________________ Email: __________________________________________________ Phone: __________________________________________________ Fax: ___________________________________________________ Street address: _________________________________________ City, Zip, State: _______________________________________ Country: ________________________________________________ Check the following that apply: _____ Please Notify Me Of Online Web Site & Register Me For Access Using The Information Above. Also Please, Send Additional Information on: _____ Online Adult & Gaming Owner/Operaters _____ Online Adult Subscribers & Online Gamers Databases _____ Online Billing/Credit Card Processing _____ Emailing Services and Databases _____ Search Engine Positioning _____ International Contact Lists _____ Buying / Selling Traffic _____ Web Site Hosting Services _____ Other:_______________________________ ####################################################################### To discontinue receipt of further notice and to be removed from our database, please reply with the word "Remove" in subject. Any attempts to disrupt the removal email address etc., will not allow us to be able to retrieve and process the remove requests. ####################################################################### .031201 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

PIM
by James Tyson 13 Mar '01

13 Mar '01

Can anyone who fires up a pim router on APE or WIX please email me so that I can update the website. Cheers. James Tyson. Self-Deluded Governing Minority, Attica Network Operations. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 4

Re: Telecom - Clear peering bandwidth
by Peter Mott 12 Mar '01

12 Mar '01

> -----Original Message----- > From: Alan Mitford-Taylor [mailto:Alan.Mitford-Taylor(a)telecom.co.nz] > Sent: Wednesday, 7 March 2001 11:52 a.m. > To: peter.mott(a)2day.com > > the planned improvement in the Clear peering bandwidth still awaits > clear's signature on a contract, we have link in place and ready to go > but can not proceed without legal sign off, unfortunately this has been > situation since last October so I don't know when it will be resolved, > but continue to chase it. I guess the same contract is also waiting Telecom's sig Peter Mott Chief Enthusiast 2day.com -/- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 7

traffic analysis by protocol
by Craig Anderson 12 Mar '01

12 Mar '01

Hi. I'm looking for off the shelf commercial or otherwise software for monitoring traffic. In particular, i'd like graphs showing the total traffic and the % traffic that is HTTP, SMTP, FTP, etc., and TCP, UDP, ICMP etc. splits. Of course also split by inbound/outbound, remote site location (NZ, International), and local network (i.e. by client of an ISP). Both near real-time data and historical analysis. I've found several protocol analysers that will give real-time and historical graphs by protocol, but don't seem to have any real facilities for breaking this down much further. Does anyone know of where i can find such software? Thanks, -Craig --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 9

Mbone pages
by James Tyson 12 Mar '01

12 Mar '01

I have updated: http://mbone.samizdat.co.nz/isps.html Cheers. James Tyson. Self-Deluded Governing Minority, Attica Network Operations. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

nzmbone
by James Tyson 12 Mar '01

12 Mar '01

Hey matey-peeps. Just letting you all know that I am right now listening to a multicast MP3 stream of BFM kindly casted over APE by IHUG (Thanks David). I'm still getting the greeblies out of my multicast routing, but it's getting there. So who else feels like putting up some content? (I was thinking of casting Triangle TV). Cheers. James Tyson. Self-Deluded Governing Minority, Attica Network Operations. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Spammers like Xtra?
by Keith Davidson 06 Mar '01

06 Mar '01

Is anyone else experiencing problems with Xtra failing to take meaningful action against spammers? My ISP has had complaints about an Xtra user, computerkids(a)xtra.co.nz and traditional contact with abuse(a)xtra results in nothing more than slaps over the wrist with wet bus tickets. HISTORY OF UCE FROM Mark Lancaster Nightingale Press 335 Beechey Street, Pirongia Tel/Fax: 07 871 9691 Email computerkidz(a)xtra.co.nz First UCE from him received on 13 February. Complaint lodged abuse(a)xtra. Second UCE received on 18 February. Complaint lodged abuse(a)xtra Third UCE received on 7 March. Actual copy of UCE below sig. My complainant states: "I then rang Xtra (finally got through to Customer Support desk) and advised that I wished to verbally complain about one of their customers spamming and that I had laid complaints on two occasions and seemingly no action had been taken. The person on their help desk took the email address of the spammer and then advised me that this person had had two warnings and I should email abuse(a)xtra again. I said that was not satisfactory and wondered how many warnings one of their users had to get before any action was taken by xtra. The Help Desk clerk said he would check and put me on hold for a few minutes. When he came back he advised me that quite a number of warnings had to be issued before any action was taken. He suggested I filter the perpetrator and I told him that that didn't fix the problem. He asked if there was anything abusive or rude in the email and I advised that whilst there was nothing along those lines that I personally found uce offensive. He advised me to lodge a further complaint with abuse(a)xtra.co.nz and I told him that I had warned xtra on a previous occasion that if no action was forthcoming to solve the problem that I intended to take the matter further." Does anyone in Xtra take these issues seriously? It is just nonsensical for Xtra staff to suggest filtering etc - it doesn't stop the source. Is the $25 per month so important to Xtra's revenue that they wont take real action? Or does Xtra like being known as a "spam friendly" ISP? Most ISP's seem to work on "2 strikes and you're out", mine included. Just what does it take for Xtra to kick someone? Anyone else having similar problems from this quarter? Any suggestions of a method of escalating the issue that might get a resolution? Keith Davidson ________________________________________________ Return-Path: <computerkidz(a)xtra.co.nz> Received: from mta1-rme.xtra.co.nz (mta1-rme.xtra.co.nz [203.96.92.1]) by kiwi.wise.net.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id KAA32673 for <office(a)wairarapa.school.nz>; Wed, 7 Mar 2001 10:15:02 +1300 Received: from marklanc ([210.54.202.229]) by mta1-rme.xtra.co.nz with SMTP id <20010306211551.EQOL2261674.mta1-rme.xtra.co.nz(a)marklanc>; Wed, 7 Mar 2001 10:15:51 +1300 From: "Mark Lancaster" <computerkidz(a)xtra.co.nz> To: <computerkidz(a)xtra.co.nz> Subject: PLEASE FORWARD THIS TO THE MATHS DEPT. - THANK YOU Date: Wed, 7 Mar 2001 10:10:19 +1300 Message-ID: <NCBBJGLIOPJEFADAPBMEIEANIJAA.computerkidz(a)xtra.co.nz> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C0A6EE.D1102F60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-UIDL: +lP!!HH!#!/9d!!D:("! This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C0A6EE.D1102F60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Nightingale Press 335 Beechey Street, Pirongia Tel/Fax: 07 871 9691 Hi I would just like to tell you about a new series of Blackline Masters we have just released called "MATHS OUTCOMES". The strands they cover throughout the series are - SPACE, MEASUREMENT, NUMBER and WORKING MATHEMATICALLY. There are 7 books in the series starting from Kindy (early stage 1) right through to Upper Primary levels. Each book contains 53 pages of photocopiable worksheets covering all the above topics. All the activities in this set of Blackline Masters are used to support lessons introduced by the teacher in class. The work presented on each page has been carefully designed to provide a different approach to maths by involving memory games , matching activities and it allows the child to offer reasoning for their answers and choices. It is designed to help children understand, consolidate and extend concepts and skills. The price is $29.95 per book and they are all available on approval. If you would like to order any (or all) of the books in this superb series, please just return this email stating copies required, the name and address of your school and any order numbers, or you could order by fax/phone. Many thanks for taking the time to read this email. Mark ------=_NextPart_000_0014_01C0A6EE.D1102F60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <snip endless html rubbish> --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NLX PSU's
by Matt Camp 06 Mar '01

06 Mar '01

Might be slightly off topic, but does anyone know where to source power supplies for NLX type PC cases? Insite used to have them, but since their merger with Renaissance, have obsoleted the product line. --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Telecom Peering
by Tony Wicks 05 Mar '01

05 Mar '01

Hi all, I have been chasing my Telecom account Manager for months to get some progress on this, so I thought I would throw it out here and see where every one else is with this. We currently peer with all major ISP's and backbone providors over either or both WIX and APE. The notable exception being Telecom Netgate ( we do peer directly with Xtra on WIX ). We are paying Telecom currently for a PVC to Netgate for peering with them and I am unhappy for this to continue. ( especially as we have almost twice the outgoing traffic to them as we recieve from them ! ). I have had nothing more than "I'll get back to you" when attempting to initiate peering with Telecom ( not Xtra ). It seems very strange to me that Clear, Telstra and everyone else is responsive and happy to work for the greater good of the Internet users in the country, but Telecom only seems interested if someone else is paying for it. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 7

www.apnic.net
by Tony Wicks 04 Mar '01

04 Mar '01

Can anyone get to this website at the moment ? I can't seem to make a connection ( apart from cached objects ) from NZ, AU or the US to the site. kappa:staff/tonyw 4:45pm > dig www.apnic.net ; <<>> DiG 8.3 <<>> www.apnic.net ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6 ;; QUERY SECTION: ;; www.apnic.net, type = A, class = IN ;; ANSWER SECTION: www.apnic.net. 30m36s IN A 203.37.255.97 ;; AUTHORITY SECTION: apnic.net. 30m36s IN NS ns.apnic.net. apnic.net. 30m36s IN NS svc00.apnic.net. apnic.net. 30m36s IN NS ns.ripe.net. apnic.net. 30m36s IN NS rs.arin.net. ;; ADDITIONAL SECTION: ns.apnic.net. 1h5m19s IN A 203.37.255.97 ns.apnic.net. 30m36s IN AAAA ::ffff:203.37.255.97 svc00.apnic.net. 1d18h6m27s IN A 202.12.28.131 svc00.apnic.net. 30m36s IN AAAA ::ffff:202.12.28.131 ns.ripe.net. 1d9h57m19s IN A 193.0.0.193 rs.arin.net. 1d18h6m27s IN A 192.149.252.21 ;; Total query time: 35 msec ;; FROM: kappa to SERVER: default -- 205.201.44.9 ;; WHEN: Sun Mar 4 16:45:14 2001 ;; MSG SIZE sent: 31 rcvd: 248 kappa:staff/tonyw 4:45pm > traceroute 203.37.255.97 traceroute to 203.37.255.97 (203.37.255.97), 30 hops max, 40 byte packets 1 master-gw.lm.net (205.201.1.1) 24.433 ms 19.029 ms 4.986 ms 2 263.ATM1-0.GW5.PIT1.alter.net (157.130.22.193) 516.424 ms 453.962 ms 502.864 ms 3 539.at-2-0-0.XR2.DCA1.ALTER.NET (152.63.38.178) 33.179 ms 25.498 ms 13.896 ms 4 294.at-7-1-0.XR2.DCA8.ALTER.NET (146.188.163.26) 22.794 ms 28.986 ms 25.275 ms 5 POS7-0.BR5.DCA8.ALTER.NET (152.63.37.45) 9.957 ms 10.352 ms 12.454 ms 6 137.39.52.158 (137.39.52.158) 429.94 ms 552.788 ms 521.643 ms 7 so-3-0-0.washdc3-nbr1.bbnplanet.net (4.24.4.169) 105.349 ms 188.541 ms 155.406 ms 8 so-7-0-0.washdc3-nbr2.bbnplanet.net (4.24.10.30) 134.572 ms 190.48 ms 183.578 ms 9 p9-0.phlapa1-br2.bbnplanet.net (4.24.10.186) 154.443 ms 135.832 ms 139.77 ms 10 p15-0.phlapa1-br1.bbnplanet.net (4.24.10.89) 476.805 ms 521.494 ms 458.769 ms 11 p13-0.nycmny1-nbr2.bbnplanet.net (4.24.10.178) 36.583 ms 34.301 ms 14.657 ms 12 p15-0.nycmny1-nbr1.bbnplanet.net (4.24.10.209) 492.356 ms 481.979 ms 427.66 ms 13 p4-0.snjpca1-br1.bbnplanet.net (4.24.9.157) 141.027 ms 100.905 ms 105.643 ms 14 p10-0.lsanca2-br1.bbnplanet.net (4.24.8.26) 510.23 ms 562.834 ms 580.358 ms 15 p15-0.lsanca2-br2.bbnplanet.net (4.24.5.46) 549.424 ms 535.577 ms 563.447 ms 16 p1-0.lsanca1-cr9.bbnplanet.net (4.24.5.202) 558.399 ms 468.532 ms 507.453 ms 17 p0-0.telstra4.bbnplanet.net (4.24.206.42) 137.123 ms 203.719 ms 207.281 ms 18 Pos2-3.pad-core3.Sydney.telstra.net (203.50.126.45) 749.915 ms 654.554 ms 735.379 ms 19 GigabitEthernet4-1.chw-core2.Sydney.telstra.net (203.50.6.201) 612.906 ms 660.024 ms 715.141 ms 20 Pos2-0.cha-core4.Brisbane.telstra.net (203.50.6.118) 357.183 ms 262.34 ms 264.331 ms 21 GigabitEthernet4-0.cha-core3.Brisbane.telstra.net (203.50.45.1) 307.158 ms 318.389 ms 412.24 ms 22 Fddi0-0.cha8.Brisbane.telstra.net (139.130.247.230) 349.427 ms 305.048 ms 260.397 ms 23 apnic1.lnk.telstra.net (139.130.64.98) 835.272 ms 726.571 ms 770.458 ms 24 ns.apnic.net (203.37.255.97) 711.432 ms 782.982 ms 735.846 ms kappa:staff/tonyw 4:46pm > lynx www.apnic.net Alert!: Unable to connect to remote host. lynx: Can't access startfile http://www.apnic.net/ kappa:staff/tonyw 4:48pm > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 5

The New Zealand Network Operators' Group
by Donald Neal 01 Mar '01

01 Mar '01

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. This list has just over 210 subscribers, growing by a handful each month. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations (nor the administrator) is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ To search the archive, see http://list.waikato.ac.nz/archives/search.html (and remember to select nznog). Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog There are at present no restrictions on who may subscribe to the list, or even on who may post to the list. Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Other Activities NZNOG does not at present have other regular activities than this mailing list, though the administrator is on the hunt for presenters for the annual Uniforum NZ conference, to be held in the second half of the year. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Reminder: SRS Green Paper Closes Tomorrow
by Sue Leader 01 Mar '01

01 Mar '01

Greetings Just a reminder that submissions for the SRS Green Paper close at 5pm tomorrow Friday March 2. Submissions should be sent direct to exe.dir(a)isocnz.org.nz. Cheers Sue Sue Leader - Executive Director ISOCNZ (Internet Society of New Zealand Inc) Exe.Dir(a)isocnz.org.nz Voice: +64-4-801-6256 http://www.isocnz.org.nz PLEASE NOTE CHANGE: P.O.Box 11-881, Wellington --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

NZ Network List
by Pete 01 Mar '01

01 Mar '01

Hiyas Does anyone on here keep an up-to-date list of IP networks that are considered to be 'inside NZ'. Ie some carriers charge for International traffic but not National and I was wondering if anyone had a list of what is considered 'National' ? Rgds, Pete Pete Mundy - Technician Advanced Communications +64-3-546-9169 / +64-25-480-840 E-Mail: Pete(a)AdvComm.Co.NZ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Cisco IOS Advisory
by Roger De Salis 27 Feb '01

27 Feb '01

Here is the official word... - We all agree that ATM is evil (thanks to Chris Wedgewood for those thoughts) and Arron agrees that he won't let Dean wind him up over the respective merits of the larger C and J boxes. (and they promise to conduct this meaningful dialog off-line) >Sender: nobody(a)cisco.com >From: Cisco Systems Product Security Incident Response Team <psirt(a)cisco.com> >To: internal-security-announce(a)cisco.com >Cc: psirt(a)cisco.com >Subject: Cisco Security Advisory: Cisco IOS Software SNMP Read-Write > ILMI Community String Vulnerability >Date: Tuesday, 27 Feb 2001 04:00:00 -0500 (EST) > > Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability > Revision 1.0: INTERIM > For Public Release 2001 February 27 04:00 US/Eastern (UTC+0500) > _______________________________________________________________ > >Summary > > Cisco IOS software releases based on versions 11.x and 12.0 contain > a defect that allows a limited number of SNMP objects to be viewed > and modified without authorization using a undocumented ILMI > community string. Some of the modifiable objects are confined to the > MIB-II system group, such as "sysContact", "sysLocation", and > "sysName", that do not affect the device's normal operation but that > may cause confusion if modified unexpectedly. The remaining objects > are contained in the LAN-EMULATION-CLIENT and PNNI MIBs, and > modification of those objects may affect ATM configuration. An > affected device might be vulnerable to a denial-of-service attack if > it is not protected against unauthorized use of the ILMI community > string. > > The vulnerability is only present in certain combinations of IOS > releases on Cisco routers and switches. ILMI is a necessary > component for ATM, and the vulnerability is present in every IOS > release that contains the supporting software for ATM and ILMI > without regard to the actual presence of an ATM interface or the > physical ability of the device to support an ATM connection. > > To remove this vulnerability, Cisco is offering free software > upgrades for all affected platforms. The defect is documented in > DDTS record CSCdp11863. > > In lieu of a software upgrade, a workaround can be applied to > certain IOS releases by disabling the ILMI community or "*ilmi" view > and applying an access list to prevent unauthorized access to SNMP. > Any affected system, regardless of software release, may be > protected by filtering SNMP traffic at a network perimeter or on > individual devices. > > This notice will be posted at > http://www.cisco.com/warp/public/707/ios-snmp-ilmi-vuln-pub.shtml. > >Affected Products > > The vulnerability is present only in certain releases of Cisco IOS > Software versions 11.x and 12.0 for router and switch products that > include support for Asynchronous Transfer Mode (ATM) networking and > Interim Local Management Interface (ILMI), and it is present without > regard to any physical capability for supporting an ATM interface. > > Cisco IOS Software versions based on 10.3 and earlier do not contain > the vulnerability. The defect was introduced in 11.0(0.2). All Cisco > IOS software releases of 12.1 and later have been repaired and are > not vulnerable to the defect described in this advisory. > > To determine the software running on a Cisco product, log in to the > device and issue the command "show version" to display the system > banner. Cisco IOS software will identify itself as "Internetwork > Operating System Software" or simply "IOS (tm)". The image name will > be displayed between parentheses, usually on the next line of > output, followed by "Version" and the IOS release name. Other Cisco > devices will not have the "show version" command or will give > different output. > > The following example identifies a Cisco product running IOS release > 12.0(3) with an installed image name of C2500-IS-L: > > Cisco Internetwork Operating System Software IOS (tm) > 2500 Software (C2500-IS-L), Version 12.0(3), RELEASE SOFTWARE > > The device is not vulnerable to the defect described in this > advisory since the model 2500 router is specifically excluded in the > list of unaffected products shown below. > > Cisco devices that may be running an affected IOS software release > include, but are not limited to: > > * Cisco 1400 and 1700 series. > > * Cisco 2600 (except that c2600-c-mz, c2600-d-mz, c2600-i-mz, > c2600-io3-mz, and c2600-ix-mz images are not vulnerable). > > * Catalyst 2900 ATM, 2900XL, and 2948g series. > > * Cisco 3620 (except that c3620-d-mz, c3620-i-mz, c3620-io3-mz, > and c3620-ix-mz images are not vulnerable). > > * Cisco 3640 (except that c3640-d-mz, c3640-i-mz, c3640-io3-mz, > and c3640-ix-mz images are not vulnerable). > > * Cisco 3660 (except that c3660-d-mz, c3660-i-mz, and c3660-ix-mz > images are not vulnerable). > > * Cisco MC3810 (except that mc3810-i-mz, mc3810-is-mz, > mc3810-is56i-mz, and mc3810-js-mz images are not vulnerable). > > * Catalyst 4232, 4840g, 5000 RSFC series switches. > > * Cisco 4500, 4700, and 5800 DSC series. > > * Cisco 6200, 6400 NRP, and 6400 NSP series. > > * Catalyst MSM (c6msm), 6000 Hybrid Mode (c6msfc), and 6000 Native > Mode (c6sup). > > * Cisco RSM, 7000, 7010, 7100, 7200, ubr7200, and 7500 series. > > * Catalyst 8510CSR, 8510MSR, 8540CSR, and 8540MSR series. > > * Cisco 10000 ESR and 12000 GSR series. > > * LS1010 and Cisco 6260-NI2. > > * DistributedDirector (except that igs-w3 images are not > vulnerable). > > Cisco products that are not affected by this vulnerability either > because they have no support for ATM and ILMI, or because they do > not run IOS include, but are not limited to: > > * Catalyst ATM blade (runs possibly affected code, but an SNMP > connection to the blade is not possible). > > * Cisco 800 and 805 series. > > * Cisco Universal Broadband Routers ubr900 and ubr920. > > * Cisco 1003, 1004, and 1005 series. > > * Cisco 1600, 2500, 2800, 4000 series. > > * Cisco 2500 Fixed Frad. > > * Cisco 3800 (not to be confused with MC3810). > > * Cisco 5100, 5200, and 5300 series access servers. > > * Catalyst 6000 Supervisor Module. > > * Cisco PIX Firewall. > > * Aironet and Cisco/Aironet wireless products. > > * CS11000, Cache Engine, LocalDirector, and network scaling > products (except that the Distributed Director might be > affected). > > * VPN products such as Altiga concentrators. > > * Host-based network management or access management products. > > * Cisco IP Telephony and telephony management software (except > those that are hosted on a vulnerable IOS platform). > > * Voice gateways and convergence platforms (except those that are > hosted on a vulnerable IOS platform). > > * Optical switch products such as the ONS 15000 series. > >Details > > ILMI (Interim Local Management Interface) is an independent industry > standard used for configuration of ATM (Asynchronous Transfer Mode) > interfaces. The standard specifies the use of mechanisms and formats > previously defined by SNMP (Simple Network Management Protocol). > Although it is based on SNMP, ILMI communication actually occurs > using a transport other than IP (Internet Protocol) that traverses > only the physical ATM link. ILMI is essential to functions such as > ATM auto-discovery and LANE (LAN Emulation). > > SNMP "objects" are variables that are organized into a MIB > (Management Information Base). The MIB has a tree structure and > contains both operational (read-only) data as well as configuration > (read-write) options. By specifying a community string of "ILMI" in > an SNMP request, access can be obtained to read the objects in three > specific parts of the overall management tree structure on any > device affected by this vulnerability: the MIB-II system group, the > LAN-EMULATION-CLIENT MIB, and the PNNI (Private Network-to-Network > Interface) MIB. A subset of objects in each part can be modified > using the same "ILMI" community string. > > The MIB-II system group contains basic information about the device > itself. The number of objects that can be modified is limited. > Examples include: > > * system.sysContact: The contact information for the person or > organization responsible for managing the device. > > * system.sysLocation: A description of the physical location where > the device is installed or operating. > > * system.sysName: The hostname of the device, how it identifies > itself at the console prompt. (This might not be the same name > by which the device is known to other hosts on the network.) > > Most of the objects in the system MIB are read-only and cannot be > changed via SNMP, such as the time elapsed since the previous > restart and textual descriptions of the device's hardware and > software. > > Numerous objects can be viewed in the LAN-EMULATION-CLIENT MIB and > PNNI MIB, and modification of some of the read-write objects can > have an affect on ATM operation of the device. The objects in the > LAN-EMULATION-CLIENT MIB can only be viewed or modified if LANE has > already been configured on the device. > > Access to SNMP in Cisco IOS software can be limited by applying > access control lists (ACLs), by modifying or removing the SNMP view, > by removing the community string from the running configuration, or > by disabling the SNMP service. Any SNMP query that does not meet the > criteria for access is promptly discarded when such protective > measures are in place. If a query does meet the criteria for access, > then a response is formulated and sent. > > It is possible to configure the device so that the ILMI community > string is unavailable in all IOS 11.1 and higher releases. The > particular method selected to accomplish this depends on the > specific IOS release and configuration. > > This defect is documented as CSCdp11863. The vulnerability is > repaired by imposing a test such that an SNMP request using the > "ILMI" community string will only be recognized if it has been > transported by ILMI. > > ATM functionality was added in various 10.x releases of Cisco IOS > software. However, the function containing the defect was introduced > when support for ILMI and other ATM features was added in IOS > release 11.0(0.2). Therefore, all prior releases are not vulnerable. > >Impact > > If SNMP requests can be received by an affected device, then certain > MIB objects can be viewed without proper authorization, causing a > violation of confidentiality. > > A subset of the readable MIB objects can be modified without > authorization to cause a failure of integrity. For example, the > hostname can be modified so as to confuse network adminstrators, or > the contact and location information could be changed with a goal of > disrupting operations or embarassing whoever is responsible for the > device. > > Objects in the LAN-EMULATION-CLIENT and PNNI MIBs can be viewed and > modified, thus resulting in changes to the operation of ATM > functions. If ATM is in use on the device, this may result in a > failure of availability. > > Any affected device that is not otherwise protected against the > receipt of SNMP packets is vulnerable to a denial-of-service (DoS) > attack by flooding the SNMP port with read or write requests. > >Software Versions and Fixes > > The following table summarizes the known affected Cisco IOS software > releases and the earliest estimated dates of availability for fixed > releases. All dates are tentative and subject to change. > > 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. If a device is > running an earlier release that is known to be vulnerable, it should > be upgraded to at least the indicated version. > > 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 defect. > Although it receives less testing, it contains only the > minimal changes necessary to effect the repair. > > Interim > Built at regular intervals between maintenance releases and > receive less testing. Interims should be selected only if > there is no other suitable release that addresses the > vulnerability. Interim releases are usually not available for > customer download via CCO without prior arrangement. > > 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 following > section. > > More information on IOS release names and abbreviations is available > at http://www.cisco.com/warp/public/620/1.html. > > +===========================================================================+ > | Train | Description of | Availability of Fixed Releases* | > | | Image or Platform | | > +===========================================================================+ > | 10.3-based Releases and | | | | > | Earlier | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | 10.3 and | | | > | earlier |All |Not affected | > +===========================================================================+ > | 11.0-based Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | | |11.0(22a) | | | > | 11.0 |Major GD release | | | | > | |for all platforms |2001-Mar-05 | | | > +===========================================================================+ > | 11.1-based Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | | |11.1(24a) | | | > | 11.1 |Major release for | | | | > | |all platforms |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |ED release for | | |12.1(7) | > | 11.1AA |access servers: | | | | > | |1600, 3200, and | | | | > | |5200 series. | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Platform-specific |11.1(36)CA1 | | | > | 11.1CA |support for 7500, | | | | > | |7200, 7000, and RSP|2001-Mar-02 | | | > +----------+-------------------+------------+---------------+---------------+ > | |ISP train: added | | | | > | |support for FIB, |11.1(36)CC1 | | | > | 11.1CC |CEF, and NetFlow on| | | | > | |7500, 7200, 7000, |2001-Mar-02 | | | > | |and RSP | | | | > +----------+-------------------+------------+---------------+---------------+ > | |Added support for |12.0(11)ST2 | | | > | 11.1CT |Tag Switching on | | | | > | |7500, 7200, 7000, | | | | > | |and RSP |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |11.1(28)IA1 | | | > | 11.1IA |DistributedDirector| | | | > | |only |2001-Feb-26 | | | > +===========================================================================+ > | 11.2-based Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | | |11.2(25a) | | | > | 11.2 |Major release, | | | | > | |general deployment |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Platform-specific | | | | > | |support for IBM | | |12.1(7) | > | 11.2BC |networking, CIP, | | | | > | |and TN3270 on 7500,| | |2001-Feb-26 | > | |7000, and RSP | | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early deployment |12.0(15)S1 | | | > | 11.2GS |release to support | | | | > | |12000 GSR |2001-Feb-20 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |11.2(25a)P | | | > | 11.2P |New platform | | | | > | |support |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | | | | |12.1WC | > | 11.2SA |Catalyst 2900XL | | | | > | |switch only | | |2001-Apr-12 | > +----------+-------------------+------------+---------------+---------------+ > | | | | |12.0(10)W5(18c)| > | 11.2WA3 |LS1010 ATM switch | | | | > | | | | |Available | > +----------+-------------------+------------+---------------+---------------+ > | | |11.2(25a)P | | | > |11.2(4)XA |Initial release for| | | | > | |the 1600 and 3600 |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Initial release for| | | | > | |the 5300 and |11.2(9)XA1 | | | > |11.2(9)XA |digital modem | | | | > | |support for the |Unscheduled | | | > | |3600 | | | | > +===========================================================================+ > | 11.3-based Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | | |11.3(11b) | | | > | 11.3 |Major release for | | | | > | |all platforms |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |ED for dial | | | | > | |platforms and |11.3(11a)AA | | | > | 11.3AA |access servers: | | | | > | |5800, 5200, 5300, |2001-Mar-05 | | | > | |7200 | | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early deployment |12.1(5)DA1 | | | > | 11.3DA |train for ISP DSLAM| | | | > | |6200 platform |2001-Feb-28 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early deployment | | | | > | |train for |12.1(4)DB1 | | | > | |ISP/Telco/PTT xDSL | | | | > | 11.3DB |broadband | | | | > | |concentrator | | | | > | |platform, (NRP) for|2001-Feb-26 | | | > | |6400 | | | | > +----------+-------------------+------------+---------------+---------------+ > | |Short-lived ED | | > | 11.3HA |release for ISR |Not Vulnerable | > | |3300 (SONET/SDH | | > | |router) | | > +----------+-------------------+------------+---------------+---------------+ > | | |11.3(1)MA8 | | | > | 11.3MA |MC3810 | | | | > | |functionality only |Unscheduled | | | > +----------+-------------------+------------+---------------+---------------+ > | |Voice over IP, |12.1(7) | | | > | 11.3NA |media convergence, | | | | > | |various platforms |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early deployment |11.3(11b)T1 | | | > | 11.3T |major release, | | | | > | |feature-rich for | | | | > | |early adopters |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Multilayer | | | | > | |Switching and | | |12.0(14)W5(20) | > | |Multiprotocol over | | | | > | 11.3WA4 |ATM functionality | | | | > | |for Catalyst 5000 | | | | > | |RSM, 4500, 4700, | | |2001-Feb-28 | > | |7200, 7500, LS1010 | | | | > +----------+-------------------+------------+---------------+---------------+ > | | |11.3(11b)T1 | | | > |11.3(2)XA |Introduction of | | | | > | |ubr7246 and 2600 |2001-Mar-05 | | | > +===========================================================================+ > | 12.0-based Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | |General deployment | |12.0(7.1) |12.0(16) | > | 12.0 |release for all | | | | > | |platforms | |Available |2001-Feb-20 | > +----------+-------------------+------------+---------------+---------------+ > | | | |12.0(7.1)T | | > | 12.0DA |xDSL support: 6100,| | | | > | |6200 | |Available | | > +----------+-------------------+------------+---------------+---------------+ > | |ISP/Telco/PTT xDSL |12.1(4)DB1 | | | > | 12.0DB |broadband | | | | > | |concentrator | | | | > | |platforms |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.1(4)DC2 | | | > | 12.0DC |6400 Access | | | | > | |Concentrator |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.0(15)S1 | | | > | 12.0S |Core/ISP support: | | | | > | |GSR, RSP, c7200 |2001-Feb-20 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.0(15)SC1 | | | > | 12.0SC |Cable/broadband | | | | > | |ISP: ubr7200 |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.0(14)SL1 | | | > | 12.0SL |10000 ESR: c10k | | | | > | | |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | |General deployment |12.0(11)ST2 | | | > | 12.0ST |release for all | | | | > | |platforms |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.1(5c)E8 | | | > | 12.0SX |Early Deployment | | | | > | |(ED) |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early | | | | > | |Deployment(ED): | | |12.1(7) | > | 12.0T |VPN, Distributed | | | | > | |Director, various | | |2001-Feb-26 | > | |platforms | | | | > +----------+-------------------+------------+---------------+---------------+ > | |cat8510c, cat8540c,| | | | > | |ls1010, cat8510m, | |12.0(10)W5(18c)|12.0(14)W5(20) | > | |cat8540m, c5atm, | | | | > | |c5atm, c3620, | | | | > | |c3640, c4500, | | | | > | 12.0W5 |c5rsfc, c5rsm, | |Available |2001-Feb-28 | > | |c7200, rsp, | | | | > | |cat2948g, cat4232 | | | | > | +-------------------+------------+---------------+---------------+ > | | | |12.0(10)W5(18d)|12.0(14)W5(20) | > | |c6msm | | | | > | | | |Available |2001-Feb-28 | > +----------+-------------------+------------+---------------+---------------+ > | |General deployment | | |12.0(13)WT6(1) | > | 12.0WT |release for all | | | | > | |platforms | | |2001-Feb-20 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XA |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | | | | |12.1(7) | > | 12.0XB |Short-lived early | | | | > | |deployment release | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XC |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XD |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment |12.1(5c)E8 | | | > | 12.0XE |(ED): limited | | | | > | |platforms |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XF |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XG |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment |12.0(4)XH5 | | | > | 12.0XH |(ED): limited | | | | > | |platforms |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XI |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1(7) | > | 12.0XJ |(ED): limited | | | | > | |platforms | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment |12.0(7)XK4 | | | > | 12.0XK |(ED): limited | | | | > | |platforms |Unscheduled | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment |12.0(4)XH5 | | | > | 12.0XL |(ED): limited | | | | > | |platforms |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | | | | |12.1(7) | > | 12.0XM |Short-lived early | | | | > | |deployment release | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | | | > | 12.0XN |(ED): limited | | | | > | |platforms | | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1WC | > | 12.0XP |(ED): limited | | | | > | |platforms | | |2001-Apr-12 | > +----------+-------------------+------------+---------------+---------------+ > | | | | |12.1(7) | > | 12.0XQ |Short-lived early | | | | > | |deployment release | | |2001-Feb-26 | > +----------+-------------------+------------+---------------+---------------+ > | | |12.1(5)T5 | | | > | 12.0XR |Short-lived early | | | | > | |deployment release |2001-Mar-05 | | | > +----------+-------------------+------------+---------------+---------------+ > | | |12.1(5c)E8 | | | > | 12.0XS |Short-lived early | | | | > | |deployment release |2001-Feb-26 | | | > +----------+-------------------+------------+---------------+---------------+ > | |Early Deployment | | |12.1WC | > | 12.0XU |(ED): limited | | | | > | |platforms | | |2001-Apr-12 | > +----------+-------------------+------------+---------------+---------------+ > | | |12.1(5)T5 | | | > | 12.0XV |Short-lived early | | | | > | |deployment release |2001-Mar-05 | | | > +===========================================================================+ > |12.1-based and Later Releases | Rebuild | Interim** | Maintenance | > +===========================================================================+ > | All 12.1 | | | > | Releases |Various platforms |Not Vulnerable | > +===========================================================================+ > | Notes | > +===========================================================================+ > | * All dates are estimated and Subject to change. | > | | > |** Interim releases are subjected to less rigorous testing than regular | > | maintenance releases, and may have serious bugs. | > +===========================================================================+ > >Obtaining Fixed Software > > Cisco is offering free software upgrades to remedy this > vulnerability for all affected customers. Customers with service > contracts may upgrade to any software release. Customers without > contracts may upgrade only within a single row of the table above, > except that any available fixed software release will be provided to > any customer who can use it and for whom the standard fixed software > release is not yet available. Customers may install only the feature > sets they have purchased. > > Note that not all fixed software may be available as of the release > date of this notice. > > Customers with contracts should obtain upgraded software through > their regular update channels. For most customers, this means that > upgrades should be obtained via Cisco's Software Center at > http://www.cisco.com/. > > Customers without contracts or warranty should get their upgrades by > contacting the Cisco Technical Assistance Center (TAC) as shown > below: > * (800) 553-2447 (toll-free in North America) > * +1 408 526 7209 (toll call from anywhere in the world) > * e-mail: tac(a)cisco.com > > See http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for > additional TAC contact information, including instructions and > e-mail addresses for use in various languages. > > 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; faster results will be obtained by contacting the TAC > directly. > >Workarounds > > Several workarounds are available based on customer needs, > equipment, and software features. The usefulness and practicality of > each workaround depends on the IOS release running on the device and > many variables in the customer's environment. Customers are urged to > consider each of the following alternatives carefully before > deploying. These workarounds are only needed if it is not possible > to upgrade to an unaffected release of IOS software. > > A. Default workaround for use with releases for which no other > workarounds are effective: > > 1. Applying access lists to all the interfaces of the > vulnerable device blocking SNMP from all hosts but those > authorized to manage the devices. > > 2. Blocking SNMP access at the edge of the network to prevent > undesirable SNMP traffic from entering the network > containing the vulnerable device. > > Access lists should be deployed with careful consideration of > the possible effects on network operation and performance. Also > note that authentication based on an IP source address is weak, > so the preceding method will not protect against certain types > of attacks in which the IP source address has been spoofed. > Further information can be found in the Cisco document > "Improving Security on Cisco Routers", available at > http://www.cisco.com/warp/public/707/21.html > > B. For affected releases based on IOS 11.1: > > 1. Remove the view so that the ILMI community cannot be > reached: > > no snmp-server view *ilmi > > 2. This configuration will not survive a system reload. The > command must be re-entered after every restart of the > system. > > C. For affected releases of IOS 11.2 through 11.3(8) NOT REQUIRING > ATM: > > In this affected range of releases, the ILMI community string > can be modified or deleted. However, the changes will not > persist through a reboot of the device. These instructions must > be re-applied following every system reload of the affected > device: > > 1. Expose the undocumented ILMI community string so it can be > modified: > > snmp-server community ILMI RW > > The preceding command may cause an error that can be safely > ignored. > > 2. Disable read-write capability for the same community: > > no snmp-server community ILMI RW > > If an error is displayed, then this workaround cannot be > applied to the device. Use the default workarounds > presented in the first item above. > > 3. Since this configuration will not survive a system reload, > the command must be re-entered after every restart of the > system. > > If the command in item 2 above did not generate an error and ATM > is not needed on this device, then this workaround is complete. > > D. For affected releases of IOS 11.2 through 11.3(8) THAT REQUIRE > ATM: > > This workaround will allow ILMI to continue to function for ATM > while constraining who may reconfigure the device by way of the > ILMI community string: > > 1. Create a simple ACL to deny access using the following > command. If "66" is already in use, choose a different > two-digit number: > > access-list 66 deny any > > 2. Apply it generally to the ILMI community to restrict its > view: > > snmp community ILMI view *ilmi RW 66 > > An error will be reported if the *ilmi view doesn't exist. > If that occurs, then use the following command to > explicitly restrict the ILMI view: > > snmp community ILMI RW 66 > > If the preceding command produces persistent errors, then > this workaround cannot be applied to this device. Use the > default workarounds presented in the first item above. > > E. For affected releases of IOS 11.3(9) through 12.0(2)T NOT > REQUIRING ATM: > > All versions of IOS in this range will accept this workaround, > and the change will remain in place after a system reload. > > 1. Expose the undocumented ILMI community string so it can be > modified: > > snmp-server community ILMI RW > > The preceding command may cause an error that can be safely > ignored. > > 2. Disable read-write capability for the same community: > > no snmp-server community ILMI RW > > If an error is displayed, then this workaround cannot be > applied to the device. Stop this procedure and use the > default workarounds presented in the first item above. > > F. For affected releases of IOS 11.3(9) through 12.0(2)T THAT > REQUIRE ATM: > > This workaround will allow ILMI to continue to function for ATM > while constraining who may reconfigure the device by way of the > ILMI community string: > > 1. Create a simple ACL to deny access using the following > command. If "66" is already in use, choose a different > two-digit number: > > access-list 66 deny any > > 2. Apply it generally to the ILMI community to restrict its > view: > > snmp community ILMI view *ilmi RW 66 > > An error will be reported if the *ilmi view doesn't exist. > If that occurs, then use the following command to > explicitly restrict the ILMI view: > > snmp community ILMI RW 66 > > If the preceding command produces persistent errors, then > this workaround cannot be applied to this device. Use the > default workaround presented in the first item above. > > G. For affected releases of IOS 12.0(3)T and later: > These releases of IOS include support for Simple Network > Management Protocol version 3 (SNMPv3), which is required for > this workaround. > > 1. Confirm the presence of SNMPv3 support by asking the > console CLI (command-line interpreter) for assistance with > options to complete the snmp-server command. Enter config > mode, enter the command shown below, and note the expected > response: > > snmp-server user test test ? > > remote Specify a remote SNMP entity to which the user belongs > v1 user using the v1 security model > v2c user using the v2c security model > v3 user using the v3 security model > > If the preceding command did not produce the expected > results, then SNMPv3 is not supported in the release and > this workaround cannot be applied. Stop this procedure and > consider applying the default workaround presented above in > the first item. > > Otherwise, if the device responded as expected, continue > with the following explanation and instructions. > > In these IOS releases (12.0(3)T and later), ILMI packets are > processed by the SNMP engine in the same manner as ordinary IP > SNMP packets. An access control list or a view applied to the > ILMI community string will be processed whether the transport is > ILMI or IP. However, the only types of access control lists that > can be applied to a community string are via IP access-list > statements, which when applied, block ALL non-IP packets, > including ILMI packets. Modifying or deleting the *ilmi view > will also affect the packets transported by ILMI, so workarounds > that change the view are equally ineffective at permitting ILMI > while denying SNMP. In this range of releases, it is not > possible to apply a workaround that denies IP SNMP packets that > does not also deny ILMI SNMP packets. > > H. For affected releases of IOS 12.0(3)T and later NOT REQUIRING > ATM: > > 1. Expose the undocumented ILMI community string so it can be > modified: > > snmp-server community ILMI RW > > The preceding command may cause an error that can be safely > ignored. > > 2. Disable read-write capability for the same community: > > no snmp-server community ILMI RW > > If an error is displayed, then this workaround cannot be > applied to the device. Stop this procedure and consider > using the default workaround. > > I. For affected releases of IOS 12.0(3)T and later THAT REQUIRE > ATM: > > NOTE: This section also applies to 12.0-based ATM switch > software such as for the LS1010 and the 8500 series. > > The only effective workaround for systems in this category is > the default workaround: > > 1. Applying access lists to all the interfaces of the > vulnerable device blocking SNMP from all hosts but those > authorized to manage the devices. > > 2. Blocking SNMP access at the edge of the network to prevent > undesirable SNMP traffic from entering the network > containing the vulnerable device. > > Access lists should be deployed with careful consideration of > the possible effects on network operation and performance. Also > note that authentication based on an IP source address is weak, > so the preceding method will not protect against certain types > of attacks in which the IP source address has been spoofed. > In this range of releases it is not possible to block IP SNMP > packets while permitting ILMI SNMP packets. The alternative > workarounds presented previously will almost certainly cause a > failure of ATM ILMI communications resulting in a loss of ATM > connectivity, either immediately upon configuration, or > unexpectedly at some later time. Either use the default > workaround or upgrade to fixed software. > >Exploitation and Public Announcements > > This vulnerability is known to the engineering staff of several > Cisco customers. Cisco considers it known to the public prior to the > publication of this notice. > > Cisco is aware of one recent incident involving the unauthorized > modification of a router that appears to have resulted from this > vulnerability. However, it may have been the unintended side-effect > of a test of the vulnerability. > > Cisco is not aware of any available tools specifically designed to > make use of this vulnerability. However, various off-the-shelf > network management programs could easily be used to test for this > vulnerability and to exploit it. Certain widely-available programs > known to the cracker community could be modified by any reasonably > competent programmer to automate the abuse of this vulnerability. > > Cisco is not aware of any general public discussion of this > vulnerability other than the exceptions previously noted. > >Status of This Notice: INTERIM > > This is an interim security advisory. Cisco anticipates issuing > updated versions of this notice at irregular intervals as there are > material changes in the facts, and will continue to update this > notice as necessary. The reader is warned that this notice may > contain inaccurate or incomplete information. 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 > anticipates issuing monthly updates of this notice until it reaches > FINAL status. > > A standalone copy or paraphrase of the text of this security > advisory that omits the distribution URL in the following section is > an uncontrolled copy, and may lack important information or contain > factual errors. > >Distribution > > This notice will be posted at > http://www.cisco.com/warp/public/707/ios-snmp-ilmi-vuln-pub.shtml . > > In addition to Worldwide Web posting, a text version of this notice > will be clear-signed with the Cisco PSIRT PGP key and will be posted > to the following e-mail and Usenet news recipients: > > * cust-security-announce(a)cisco.com > > * bugtraq(a)securityfocus.com > > * firewalls(a)lists.gnac.com > > * first-teams(a)first.org (including CERT/CC) > > * cisco(a)spot.colorado.edu > > * cisco-nsp(a)puck.nether.net > > * comp.dcom.sys.cisco > > * Various internal Cisco mailing lists > > Future updates of this notice, if any, will be placed on Cisco's > Worldwide Web server, but may or may not be actively announced on > mailing lists or newsgroups. Users concerned about this problem are > encouraged to check the URL given above for any updates. > >Revision History > > Revision 1.0 2001-Feb-27 First interim public version > >Cisco Product Security Incident Procedures > > Instructions for reporting product security vulnerabilities in Cisco > products, obtaining assistance with customer security incidents, and > registering to receive security information from Cisco can be found > at http://www.cisco.com/warp/public/707/sec_incident_response.shtml > , including instructions for press inquiries regarding Cisco > Security Advisories. > _______________________________________________________________ > > Copyright 2001 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. > _______________________________________________________________ > -- \_ Roger De Salis Cisco Systems NZ Ltd </' +64 25 481 452 L8, ASB Tower, 2 Hunter St /) +64 4 496 9003 Wellington, New Zealand (/ roger(a)desalis.gen.nz rdesalis(a)cisco.com ` --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Fw: Re: Warning: Cisco RW community backdoor.
by Joe Abley 27 Feb '01

27 Feb '01

More details below. -----Original Message----- From: "James A. T. Rice" <jamesr(a)rd.bbc.co.uk> Date: Tue, 27 Feb 2001 01:46:37 +0000 (GMT) Subject: Re: Warning: Cisco RW community backdoor. To: <members(a)lonap.net>, , , <ops(a)linx.net> Just a couple of things to note, I've been asked what the backdoor is, if its the community "ILMI" or if that was just an example, the answer is yes - "ILMI" is the backdoor which gives read-write access to parts of the SNMP base. Its looks like parts of my earlier email are somewhat misleading, the ILMI community appears to only allow RW access to the system object and possibly some more objects. Its not a 'standard' open RW community. hence the damage caused by this backdoor is limited. There is still some write access however, so the fix mentioned below is still highly recommended. And of course - it allows people to read what IOS/model cisco you have, which could be used to find exploitable bugs in that particular release. Oh I wonder what the chances of having a router stolen due to discovery of system.sysLocation is! :-) Warm Regards James -- James A. T. Rice | Email: jamesr(a)rd.bbc.co.uk Internet Operations Engineer | Phone: 01737 839 737 BBC Internet Services, Kingswood Warren, Tadworth, Surrey, UK. On Tue, 27 Feb 2001, it was written: > If your router responds to `snmpwalk router.isp.net.uk ILMI`, you > probabally will want to do the following to disable it: > conf t > snmp-server community ILMI RO 99 > access-list 99 deny any log > (pick another spare access-list if 99 isn't available) > > If you dont, assuming your ios/hardware combination supports it, > (most of the bigger routers do) anyone can do things like: > `snmpset router.isp.net.uk ILMI system.sysName.0 s \ > "ALL YOUR ROUTER ARE BELONG TO US."` > Thats a harmless example. You can do almost anything with RW snmp. > > Warm Regards > James > > -- > James A. T. Rice | Email: jamesr(a)rd.bbc.co.uk > Internet Operations Engineer | Phone: 01737 839 737 > BBC Internet Services, Kingswood Warren, Tadworth, Surrey, UK. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 7

FW: [nsp] Cisco Security Advisory: Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability
by Barry Raveendran Greene 27 Feb '01

27 Feb '01

-----Original Message----- From: nobody(a)cisco.com [mailto:nobody(a)cisco.com]On Behalf Of Cisco Systems Product Security Incident Response Team Sent: Tuesday, February 27, 2001 1:00 AM To: cisco-nsp(a)puck.nether.net Cc: psirt(a)cisco.com Subject: [nsp] Cisco Security Advisory: Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability -----BEGIN PGP SIGNED MESSAGE----- Cisco Security Advisory: Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability Revision 1.0: INTERIM For Public Release 2001 February 27 04:00 US/Eastern (UTC+0500) _______________________________________________________________ Summary Cisco IOS software releases based on versions 11.x and 12.0 contain a defect that allows a limited number of SNMP objects to be viewed and modified without authorization using a undocumented ILMI community string. Some of the modifiable objects are confined to the MIB-II system group, such as "sysContact", "sysLocation", and "sysName", that do not affect the device's normal operation but that may cause confusion if modified unexpectedly. The remaining objects are contained in the LAN-EMULATION-CLIENT and PNNI MIBs, and modification of those objects may affect ATM configuration. An affected device might be vulnerable to a denial-of-service attack if it is not protected against unauthorized use of the ILMI community string. The vulnerability is only present in certain combinations of IOS releases on Cisco routers and switches. ILMI is a necessary component for ATM, and the vulnerability is present in every IOS release that contains the supporting software for ATM and ILMI without regard to the actual presence of an ATM interface or the physical ability of the device to support an ATM connection. To remove this vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is documented in DDTS record CSCdp11863. In lieu of a software upgrade, a workaround can be applied to certain IOS releases by disabling the ILMI community or "*ilmi" view and applying an access list to prevent unauthorized access to SNMP. Any affected system, regardless of software release, may be protected by filtering SNMP traffic at a network perimeter or on individual devices. This notice will be posted at http://www.cisco.com/warp/public/707/ios-snmp-ilmi-vuln-pub.shtml. Affected Products The vulnerability is present only in certain releases of Cisco IOS Software versions 11.x and 12.0 for router and switch products that include support for Asynchronous Transfer Mode (ATM) networking and Interim Local Management Interface (ILMI), and it is present without regard to any physical capability for supporting an ATM interface. Cisco IOS Software versions based on 10.3 and earlier do not contain the vulnerability. The defect was introduced in 11.0(0.2). All Cisco IOS software releases of 12.1 and later have been repaired and are not vulnerable to the defect described in this advisory. To determine the software running on a Cisco product, log in to the device and issue the command "show version" to display the system banner. Cisco IOS software will identify itself as "Internetwork Operating System Software" or simply "IOS (tm)". The image name will be displayed between parentheses, usually on the next line of output, followed by "Version" and the IOS release name. Other Cisco devices will not have the "show version" command or will give different output. The following example identifies a Cisco product running IOS release 12.0(3) with an installed image name of C2500-IS-L: Cisco Internetwork Operating System Software IOS (tm) 2500 Software (C2500-IS-L), Version 12.0(3), RELEASE SOFTWARE The device is not vulnerable to the defect described in this advisory since the model 2500 router is specifically excluded in the list of unaffected products shown below. Cisco devices that may be running an affected IOS software release include, but are not limited to: * Cisco 1400 and 1700 series. * Cisco 2600 (except that c2600-c-mz, c2600-d-mz, c2600-i-mz, c2600-io3-mz, and c2600-ix-mz images are not vulnerable). * Catalyst 2900 ATM, 2900XL, and 2948g series. * Cisco 3620 (except that c3620-d-mz, c3620-i-mz, c3620-io3-mz, and c3620-ix-mz images are not vulnerable). * Cisco 3640 (except that c3640-d-mz, c3640-i-mz, c3640-io3-mz, and c3640-ix-mz images are not vulnerable). * Cisco 3660 (except that c3660-d-mz, c3660-i-mz, and c3660-ix-mz images are not vulnerable). * Cisco MC3810 (except that mc3810-i-mz, mc3810-is-mz, mc3810-is56i-mz, and mc3810-js-mz images are not vulnerable). * Catalyst 4232, 4840g, 5000 RSFC series switches. * Cisco 4500, 4700, and 5800 DSC series. * Cisco 6200, 6400 NRP, and 6400 NSP series. * Catalyst MSM (c6msm), 6000 Hybrid Mode (c6msfc), and 6000 Native Mode (c6sup). * Cisco RSM, 7000, 7010, 7100, 7200, ubr7200, and 7500 series. * Catalyst 8510CSR, 8510MSR, 8540CSR, and 8540MSR series. * Cisco 10000 ESR and 12000 GSR series. * LS1010 and Cisco 6260-NI2. * DistributedDirector (except that igs-w3 images are not vulnerable). Cisco products that are not affected by this vulnerability either because they have no support for ATM and ILMI, or because they do not run IOS include, but are not limited to: * Catalyst ATM blade (runs possibly affected code, but an SNMP connection to the blade is not possible). * Cisco 800 and 805 series. * Cisco Universal Broadband Routers ubr900 and ubr920. * Cisco 1003, 1004, and 1005 series. * Cisco 1600, 2500, 2800, 4000 series. * Cisco 2500 Fixed Frad. * Cisco 3800 (not to be confused with MC3810). * Cisco 5100, 5200, and 5300 series access servers. * Catalyst 6000 Supervisor Module. * Cisco PIX Firewall. * Aironet and Cisco/Aironet wireless products. * CS11000, Cache Engine, LocalDirector, and network scaling products (except that the Distributed Director might be affected). * VPN products such as Altiga concentrators. * Host-based network management or access management products. * Cisco IP Telephony and telephony management software (except those that are hosted on a vulnerable IOS platform). * Voice gateways and convergence platforms (except those that are hosted on a vulnerable IOS platform). * Optical switch products such as the ONS 15000 series. Details ILMI (Interim Local Management Interface) is an independent industry standard used for configuration of ATM (Asynchronous Transfer Mode) interfaces. The standard specifies the use of mechanisms and formats previously defined by SNMP (Simple Network Management Protocol). Although it is based on SNMP, ILMI communication actually occurs using a transport other than IP (Internet Protocol) that traverses only the physical ATM link. ILMI is essential to functions such as ATM auto-discovery and LANE (LAN Emulation). SNMP "objects" are variables that are organized into a MIB (Management Information Base). The MIB has a tree structure and contains both operational (read-only) data as well as configuration (read-write) options. By specifying a community string of "ILMI" in an SNMP request, access can be obtained to read the objects in three specific parts of the overall management tree structure on any device affected by this vulnerability: the MIB-II system group, the LAN-EMULATION-CLIENT MIB, and the PNNI (Private Network-to-Network Interface) MIB. A subset of objects in each part can be modified using the same "ILMI" community string. The MIB-II system group contains basic information about the device itself. The number of objects that can be modified is limited. Examples include: * system.sysContact: The contact information for the person or organization responsible for managing the device. * system.sysLocation: A description of the physical location where the device is installed or operating. * system.sysName: The hostname of the device, how it identifies itself at the console prompt. (This might not be the same name by which the device is known to other hosts on the network.) Most of the objects in the system MIB are read-only and cannot be changed via SNMP, such as the time elapsed since the previous restart and textual descriptions of the device's hardware and software. Numerous objects can be viewed in the LAN-EMULATION-CLIENT MIB and PNNI MIB, and modification of some of the read-write objects can have an affect on ATM operation of the device. The objects in the LAN-EMULATION-CLIENT MIB can only be viewed or modified if LANE has already been configured on the device. Access to SNMP in Cisco IOS software can be limited by applying access control lists (ACLs), by modifying or removing the SNMP view, by removing the community string from the running configuration, or by disabling the SNMP service. Any SNMP query that does not meet the criteria for access is promptly discarded when such protective measures are in place. If a query does meet the criteria for access, then a response is formulated and sent. It is possible to configure the device so that the ILMI community string is unavailable in all IOS 11.1 and higher releases. The particular method selected to accomplish this depends on the specific IOS release and configuration. This defect is documented as CSCdp11863. The vulnerability is repaired by imposing a test such that an SNMP request using the "ILMI" community string will only be recognized if it has been transported by ILMI. ATM functionality was added in various 10.x releases of Cisco IOS software. However, the function containing the defect was introduced when support for ILMI and other ATM features was added in IOS release 11.0(0.2). Therefore, all prior releases are not vulnerable. Impact If SNMP requests can be received by an affected device, then certain MIB objects can be viewed without proper authorization, causing a violation of confidentiality. A subset of the readable MIB objects can be modified without authorization to cause a failure of integrity. For example, the hostname can be modified so as to confuse network adminstrators, or the contact and location information could be changed with a goal of disrupting operations or embarassing whoever is responsible for the device. Objects in the LAN-EMULATION-CLIENT and PNNI MIBs can be viewed and modified, thus resulting in changes to the operation of ATM functions. If ATM is in use on the device, this may result in a failure of availability. Any affected device that is not otherwise protected against the receipt of SNMP packets is vulnerable to a denial-of-service (DoS) attack by flooding the SNMP port with read or write requests. Software Versions and Fixes The following table summarizes the known affected Cisco IOS software releases and the earliest estimated dates of availability for fixed releases. All dates are tentative and subject to change. 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. If a device is running an earlier release that is known to be vulnerable, it should be upgraded to at least the indicated version. 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 defect. Although it receives less testing, it contains only the minimal changes necessary to effect the repair. Interim Built at regular intervals between maintenance releases and receive less testing. Interims should be selected only if there is no other suitable release that addresses the vulnerability. Interim releases are usually not available for customer download via CCO without prior arrangement. 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 following section. More information on IOS release names and abbreviations is available at http://www.cisco.com/warp/public/620/1.html. +=========================================================================== + | Train | Description of | Availability of Fixed Releases* | | | Image or Platform | | +=========================================================================== + | 10.3-based Releases and | | | | | Earlier | Rebuild | Interim** | Maintenance | +=========================================================================== + | 10.3 and | | | | earlier |All |Not affected | +=========================================================================== + | 11.0-based Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | | |11.0(22a) | | | | 11.0 |Major GD release | | | | | |for all platforms |2001-Mar-05 | | | +=========================================================================== + | 11.1-based Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | | |11.1(24a) | | | | 11.1 |Major release for | | | | | |all platforms |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |ED release for | | |12.1(7) | | 11.1AA |access servers: | | | | | |1600, 3200, and | | | | | |5200 series. | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Platform-specific |11.1(36)CA1 | | | | 11.1CA |support for 7500, | | | | | |7200, 7000, and RSP|2001-Mar-02 | | | +----------+-------------------+------------+---------------+--------------- + | |ISP train: added | | | | | |support for FIB, |11.1(36)CC1 | | | | 11.1CC |CEF, and NetFlow on| | | | | |7500, 7200, 7000, |2001-Mar-02 | | | | |and RSP | | | | +----------+-------------------+------------+---------------+--------------- + | |Added support for |12.0(11)ST2 | | | | 11.1CT |Tag Switching on | | | | | |7500, 7200, 7000, | | | | | |and RSP |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | | |11.1(28)IA1 | | | | 11.1IA |DistributedDirector| | | | | |only |2001-Feb-26 | | | +=========================================================================== + | 11.2-based Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | | |11.2(25a) | | | | 11.2 |Major release, | | | | | |general deployment |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |Platform-specific | | | | | |support for IBM | | |12.1(7) | | 11.2BC |networking, CIP, | | | | | |and TN3270 on 7500,| | |2001-Feb-26 | | |7000, and RSP | | | | +----------+-------------------+------------+---------------+--------------- + | |Early deployment |12.0(15)S1 | | | | 11.2GS |release to support | | | | | |12000 GSR |2001-Feb-20 | | | +----------+-------------------+------------+---------------+--------------- + | | |11.2(25a)P | | | | 11.2P |New platform | | | | | |support |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | | | | |12.1WC | | 11.2SA |Catalyst 2900XL | | | | | |switch only | | |2001-Apr-12 | +----------+-------------------+------------+---------------+--------------- + | | | | |12.0(10)W5(18c)| | 11.2WA3 |LS1010 ATM switch | | | | | | | | |Available | +----------+-------------------+------------+---------------+--------------- + | | |11.2(25a)P | | | |11.2(4)XA |Initial release for| | | | | |the 1600 and 3600 |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |Initial release for| | | | | |the 5300 and |11.2(9)XA1 | | | |11.2(9)XA |digital modem | | | | | |support for the |Unscheduled | | | | |3600 | | | | +=========================================================================== + | 11.3-based Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | | |11.3(11b) | | | | 11.3 |Major release for | | | | | |all platforms |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |ED for dial | | | | | |platforms and |11.3(11a)AA | | | | 11.3AA |access servers: | | | | | |5800, 5200, 5300, |2001-Mar-05 | | | | |7200 | | | | +----------+-------------------+------------+---------------+--------------- + | |Early deployment |12.1(5)DA1 | | | | 11.3DA |train for ISP DSLAM| | | | | |6200 platform |2001-Feb-28 | | | +----------+-------------------+------------+---------------+--------------- + | |Early deployment | | | | | |train for |12.1(4)DB1 | | | | |ISP/Telco/PTT xDSL | | | | | 11.3DB |broadband | | | | | |concentrator | | | | | |platform, (NRP) for|2001-Feb-26 | | | | |6400 | | | | +----------+-------------------+------------+---------------+--------------- + | |Short-lived ED | | | 11.3HA |release for ISR |Not Vulnerable | | |3300 (SONET/SDH | | | |router) | | +----------+-------------------+------------+---------------+--------------- + | | |11.3(1)MA8 | | | | 11.3MA |MC3810 | | | | | |functionality only |Unscheduled | | | +----------+-------------------+------------+---------------+--------------- + | |Voice over IP, |12.1(7) | | | | 11.3NA |media convergence, | | | | | |various platforms |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |Early deployment |11.3(11b)T1 | | | | 11.3T |major release, | | | | | |feature-rich for | | | | | |early adopters |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |Multilayer | | | | | |Switching and | | |12.0(14)W5(20) | | |Multiprotocol over | | | | | 11.3WA4 |ATM functionality | | | | | |for Catalyst 5000 | | | | | |RSM, 4500, 4700, | | |2001-Feb-28 | | |7200, 7500, LS1010 | | | | +----------+-------------------+------------+---------------+--------------- + | | |11.3(11b)T1 | | | |11.3(2)XA |Introduction of | | | | | |ubr7246 and 2600 |2001-Mar-05 | | | +=========================================================================== + | 12.0-based Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | |General deployment | |12.0(7.1) |12.0(16) | | 12.0 |release for all | | | | | |platforms | |Available |2001-Feb-20 | +----------+-------------------+------------+---------------+--------------- + | | | |12.0(7.1)T | | | 12.0DA |xDSL support: 6100,| | | | | |6200 | |Available | | +----------+-------------------+------------+---------------+--------------- + | |ISP/Telco/PTT xDSL |12.1(4)DB1 | | | | 12.0DB |broadband | | | | | |concentrator | | | | | |platforms |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.1(4)DC2 | | | | 12.0DC |6400 Access | | | | | |Concentrator |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.0(15)S1 | | | | 12.0S |Core/ISP support: | | | | | |GSR, RSP, c7200 |2001-Feb-20 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.0(15)SC1 | | | | 12.0SC |Cable/broadband | | | | | |ISP: ubr7200 |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.0(14)SL1 | | | | 12.0SL |10000 ESR: c10k | | | | | | |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | |General deployment |12.0(11)ST2 | | | | 12.0ST |release for all | | | | | |platforms |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.1(5c)E8 | | | | 12.0SX |Early Deployment | | | | | |(ED) |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | |Early | | | | | |Deployment(ED): | | |12.1(7) | | 12.0T |VPN, Distributed | | | | | |Director, various | | |2001-Feb-26 | | |platforms | | | | +----------+-------------------+------------+---------------+--------------- + | |cat8510c, cat8540c,| | | | | |ls1010, cat8510m, | |12.0(10)W5(18c)|12.0(14)W5(20) | | |cat8540m, c5atm, | | | | | |c5atm, c3620, | | | | | |c3640, c4500, | | | | | 12.0W5 |c5rsfc, c5rsm, | |Available |2001-Feb-28 | | |c7200, rsp, | | | | | |cat2948g, cat4232 | | | | | +-------------------+------------+---------------+---------------+ | | | |12.0(10)W5(18d)|12.0(14)W5(20) | | |c6msm | | | | | | | |Available |2001-Feb-28 | +----------+-------------------+------------+---------------+--------------- + | |General deployment | | |12.0(13)WT6(1) | | 12.0WT |release for all | | | | | |platforms | | |2001-Feb-20 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XA |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | | | | |12.1(7) | | 12.0XB |Short-lived early | | | | | |deployment release | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XC |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XD |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment |12.1(5c)E8 | | | | 12.0XE |(ED): limited | | | | | |platforms |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XF |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XG |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment |12.0(4)XH5 | | | | 12.0XH |(ED): limited | | | | | |platforms |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XI |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1(7) | | 12.0XJ |(ED): limited | | | | | |platforms | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment |12.0(7)XK4 | | | | 12.0XK |(ED): limited | | | | | |platforms |Unscheduled | | | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment |12.0(4)XH5 | | | | 12.0XL |(ED): limited | | | | | |platforms |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | | | | |12.1(7) | | 12.0XM |Short-lived early | | | | | |deployment release | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | | | | 12.0XN |(ED): limited | | | | | |platforms | | | | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1WC | | 12.0XP |(ED): limited | | | | | |platforms | | |2001-Apr-12 | +----------+-------------------+------------+---------------+--------------- + | | | | |12.1(7) | | 12.0XQ |Short-lived early | | | | | |deployment release | | |2001-Feb-26 | +----------+-------------------+------------+---------------+--------------- + | | |12.1(5)T5 | | | | 12.0XR |Short-lived early | | | | | |deployment release |2001-Mar-05 | | | +----------+-------------------+------------+---------------+--------------- + | | |12.1(5c)E8 | | | | 12.0XS |Short-lived early | | | | | |deployment release |2001-Feb-26 | | | +----------+-------------------+------------+---------------+--------------- + | |Early Deployment | | |12.1WC | | 12.0XU |(ED): limited | | | | | |platforms | | |2001-Apr-12 | +----------+-------------------+------------+---------------+--------------- + | | |12.1(5)T5 | | | | 12.0XV |Short-lived early | | | | | |deployment release |2001-Mar-05 | | | +=========================================================================== + |12.1-based and Later Releases | Rebuild | Interim** | Maintenance | +=========================================================================== + | All 12.1 | | | | Releases |Various platforms |Not Vulnerable | +=========================================================================== + | Notes | +=========================================================================== + | * All dates are estimated and Subject to change. | | | |** Interim releases are subjected to less rigorous testing than regular | | maintenance releases, and may have serious bugs. | +=========================================================================== + Obtaining Fixed Software Cisco is offering free software upgrades to remedy this vulnerability for all affected customers. Customers with service contracts may upgrade to any software release. Customers without contracts may upgrade only within a single row of the table above, except that any available fixed software release will be provided to any customer who can use it and for whom the standard fixed software release is not yet available. Customers may install only the feature sets they have purchased. Note that not all fixed software may be available as of the release date of this notice. Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained via Cisco's Software Center at http://www.cisco.com/. Customers without contracts or warranty should get their upgrades by contacting the Cisco Technical Assistance Center (TAC) as shown below: * (800) 553-2447 (toll-free in North America) * +1 408 526 7209 (toll call from anywhere in the world) * e-mail: tac(a)cisco.com See http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including instructions and e-mail addresses for use in various languages. 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; faster results will be obtained by contacting the TAC directly. Workarounds Several workarounds are available based on customer needs, equipment, and software features. The usefulness and practicality of each workaround depends on the IOS release running on the device and many variables in the customer's environment. Customers are urged to consider each of the following alternatives carefully before deploying. These workarounds are only needed if it is not possible to upgrade to an unaffected release of IOS software. A. Default workaround for use with releases for which no other workarounds are effective: 1. Applying access lists to all the interfaces of the vulnerable device blocking SNMP from all hosts but those authorized to manage the devices. 2. Blocking SNMP access at the edge of the network to prevent undesirable SNMP traffic from entering the network containing the vulnerable device. Access lists should be deployed with careful consideration of the possible effects on network operation and performance. Also note that authentication based on an IP source address is weak, so the preceding method will not protect against certain types of attacks in which the IP source address has been spoofed. Further information can be found in the Cisco document "Improving Security on Cisco Routers", available at http://www.cisco.com/warp/public/707/21.html B. For affected releases based on IOS 11.1: 1. Remove the view so that the ILMI community cannot be reached: no snmp-server view *ilmi 2. This configuration will not survive a system reload. The command must be re-entered after every restart of the system. C. For affected releases of IOS 11.2 through 11.3(8) NOT REQUIRING ATM: In this affected range of releases, the ILMI community string can be modified or deleted. However, the changes will not persist through a reboot of the device. These instructions must be re-applied following every system reload of the affected device: 1. Expose the undocumented ILMI community string so it can be modified: snmp-server community ILMI RW The preceding command may cause an error that can be safely ignored. 2. Disable read-write capability for the same community: no snmp-server community ILMI RW If an error is displayed, then this workaround cannot be applied to the device. Use the default workarounds presented in the first item above. 3. Since this configuration will not survive a system reload, the command must be re-entered after every restart of the system. If the command in item 2 above did not generate an error and ATM is not needed on this device, then this workaround is complete. D. For affected releases of IOS 11.2 through 11.3(8) THAT REQUIRE ATM: This workaround will allow ILMI to continue to function for ATM while constraining who may reconfigure the device by way of the ILMI community string: 1. Create a simple ACL to deny access using the following command. If "66" is already in use, choose a different two-digit number: access-list 66 deny any 2. Apply it generally to the ILMI community to restrict its view: snmp community ILMI view *ilmi RW 66 An error will be reported if the *ilmi view doesn't exist. If that occurs, then use the following command to explicitly restrict the ILMI view: snmp community ILMI RW 66 If the preceding command produces persistent errors, then this workaround cannot be applied to this device. Use the default workarounds presented in the first item above. E. For affected releases of IOS 11.3(9) through 12.0(2)T NOT REQUIRING ATM: All versions of IOS in this range will accept this workaround, and the change will remain in place after a system reload. 1. Expose the undocumented ILMI community string so it can be modified: snmp-server community ILMI RW The preceding command may cause an error that can be safely ignored. 2. Disable read-write capability for the same community: no snmp-server community ILMI RW If an error is displayed, then this workaround cannot be applied to the device. Stop this procedure and use the default workarounds presented in the first item above. F. For affected releases of IOS 11.3(9) through 12.0(2)T THAT REQUIRE ATM: This workaround will allow ILMI to continue to function for ATM while constraining who may reconfigure the device by way of the ILMI community string: 1. Create a simple ACL to deny access using the following command. If "66" is already in use, choose a different two-digit number: access-list 66 deny any 2. Apply it generally to the ILMI community to restrict its view: snmp community ILMI view *ilmi RW 66 An error will be reported if the *ilmi view doesn't exist. If that occurs, then use the following command to explicitly restrict the ILMI view: snmp community ILMI RW 66 If the preceding command produces persistent errors, then this workaround cannot be applied to this device. Use the default workaround presented in the first item above. G. For affected releases of IOS 12.0(3)T and later: These releases of IOS include support for Simple Network Management Protocol version 3 (SNMPv3), which is required for this workaround. 1. Confirm the presence of SNMPv3 support by asking the console CLI (command-line interpreter) for assistance with options to complete the snmp-server command. Enter config mode, enter the command shown below, and note the expected response: snmp-server user test test ? remote Specify a remote SNMP entity to which the user belongs v1 user using the v1 security model v2c user using the v2c security model v3 user using the v3 security model If the preceding command did not produce the expected results, then SNMPv3 is not supported in the release and this workaround cannot be applied. Stop this procedure and consider applying the default workaround presented above in the first item. Otherwise, if the device responded as expected, continue with the following explanation and instructions. In these IOS releases (12.0(3)T and later), ILMI packets are processed by the SNMP engine in the same manner as ordinary IP SNMP packets. An access control list or a view applied to the ILMI community string will be processed whether the transport is ILMI or IP. However, the only types of access control lists that can be applied to a community string are via IP access-list statements, which when applied, block ALL non-IP packets, including ILMI packets. Modifying or deleting the *ilmi view will also affect the packets transported by ILMI, so workarounds that change the view are equally ineffective at permitting ILMI while denying SNMP. In this range of releases, it is not possible to apply a workaround that denies IP SNMP packets that does not also deny ILMI SNMP packets. H. For affected releases of IOS 12.0(3)T and later NOT REQUIRING ATM: 1. Expose the undocumented ILMI community string so it can be modified: snmp-server community ILMI RW The preceding command may cause an error that can be safely ignored. 2. Disable read-write capability for the same community: no snmp-server community ILMI RW If an error is displayed, then this workaround cannot be applied to the device. Stop this procedure and consider using the default workaround. I. For affected releases of IOS 12.0(3)T and later THAT REQUIRE ATM: NOTE: This section also applies to 12.0-based ATM switch software such as for the LS1010 and the 8500 series. The only effective workaround for systems in this category is the default workaround: 1. Applying access lists to all the interfaces of the vulnerable device blocking SNMP from all hosts but those authorized to manage the devices. 2. Blocking SNMP access at the edge of the network to prevent undesirable SNMP traffic from entering the network containing the vulnerable device. Access lists should be deployed with careful consideration of the possible effects on network operation and performance. Also note that authentication based on an IP source address is weak, so the preceding method will not protect against certain types of attacks in which the IP source address has been spoofed. In this range of releases it is not possible to block IP SNMP packets while permitting ILMI SNMP packets. The alternative workarounds presented previously will almost certainly cause a failure of ATM ILMI communications resulting in a loss of ATM connectivity, either immediately upon configuration, or unexpectedly at some later time. Either use the default workaround or upgrade to fixed software. Exploitation and Public Announcements This vulnerability is known to the engineering staff of several Cisco customers. Cisco considers it known to the public prior to the publication of this notice. Cisco is aware of one recent incident involving the unauthorized modification of a router that appears to have resulted from this vulnerability. However, it may have been the unintended side-effect of a test of the vulnerability. Cisco is not aware of any available tools specifically designed to make use of this vulnerability. However, various off-the-shelf network management programs could easily be used to test for this vulnerability and to exploit it. Certain widely-available programs known to the cracker community could be modified by any reasonably competent programmer to automate the abuse of this vulnerability. Cisco is not aware of any general public discussion of this vulnerability other than the exceptions previously noted. Status of This Notice: INTERIM This is an interim security advisory. Cisco anticipates issuing updated versions of this notice at irregular intervals as there are material changes in the facts, and will continue to update this notice as necessary. The reader is warned that this notice may contain inaccurate or incomplete information. 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 anticipates issuing monthly updates of this notice until it reaches FINAL status. A standalone copy or paraphrase of the text of this security advisory that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors. Distribution This notice will be posted at http://www.cisco.com/warp/public/707/ios-snmp-ilmi-vuln-pub.shtml . In addition to Worldwide Web posting, a text version of this notice will be clear-signed with the Cisco PSIRT PGP key and will be posted to the following e-mail and Usenet news recipients: * cust-security-announce(a)cisco.com * bugtraq(a)securityfocus.com * firewalls(a)lists.gnac.com * first-teams(a)first.org (including CERT/CC) * cisco(a)spot.colorado.edu * cisco-nsp(a)puck.nether.net * comp.dcom.sys.cisco * Various internal Cisco mailing lists Future updates of this notice, if any, will be placed on Cisco's Worldwide Web server, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the URL given above for any updates. Revision History Revision 1.0 2001-Feb-27 First interim public version Cisco Product Security Incident Procedures Instructions for reporting product security vulnerabilities in Cisco products, obtaining assistance with customer security incidents, and registering to receive security information from Cisco can be found at http://www.cisco.com/warp/public/707/sec_incident_response.shtml , including instructions for press inquiries regarding Cisco Security Advisories. _______________________________________________________________ Copyright 2001 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. _______________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQEVAwUBOpuPFWiN3BRdFxkbAQEmvAf+Ng5nJtzMpp2Dl/N+ZDp4/4Ul1nqMt89P IcNr/9AKa/jCMKNE8z20/tql78f0oniJ3YfR2GcoFfgfRCRKEVJ5QvzH3r+8BLA2 9YRsmxg/96aVwMP9gLoh4RiO4+qoTwSZkOBJ/DlZFzM7TG8SjKvgtjqcHWiLH9wx /YnxrVWg0jmnY9NvsRQSmS4KvKjFXZXaUBzlH8pOcrY9+vScS6ol+HwCiQOynQYn 2sG+KEapKP/ld2iDcHZPjbFfVsKm+iCtMzcroqpA+ND3ezBeNe2yjJXZG9oWUiVR zLYima8yuU5Mm18b3BoBkM2npf5QP/zRinis9A8d+mlnPemAWVoWug== =xM8n -----END PGP SIGNATURE----- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: [jamesr@rd.bbc.co.uk: Warning: Cisco RW community backdoor.]
by Andy Linton 26 Feb '01

26 Feb '01

At 14:44 27/02/2001 +1300, David Robb wrote: >On Tue, 27 Feb 2001, Chris Wedgwood wrote: > > > Unless you have IOS 11.1 where this doesn't work :) > > > > "no snmp-server" > >11.2 seems to require the same treatment. I tried the "patch" on IOS 11.2 and 11.3 boxes such as 2500s and 2924 switches. I had to leave out the "log'" option on the access list. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Cisco IOS ILMI/SNMP
by Roger De Salis 26 Feb '01

26 Feb '01

Gentlefolks, Cisco has become aware of an issue with ILMI (and there is is another advisory pending) across several versions of IOS. Please look at the PSAT pages on www.cisco.com, as info will be available very shortly with full details. Rgds Roger De Salis James A.T. Rice wrote > Its looks like parts of my earlier email are somewhat misleading, > the ILMI community appears to only allow RW access to the system > object and possibly some more objects. Its not a 'standard' open > RW community. hence the damage caused by this backdoor is limited. > There is still some write access however, so the fix mentioned > below is still highly recommended. > > And of course - it allows people to read what IOS/model cisco > you have, which could be used to find exploitable bugs in that > particular release. Oh I wonder what the chances of having a > router stolen due to discovery of system.sysLocation is! :-) > > Warm Regards > James -- \_ Roger De Salis Cisco Systems NZ Ltd </' +64 25 481 452 L8, ASB Tower, 2 Hunter St /) +64 4 496 9003 Wellington, New Zealand (/ roger(a)desalis.gen.nz rdesalis(a)cisco.com ` --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

[jamesr@rd.bbc.co.uk: Warning: Cisco RW community backdoor.]
by Joe Abley 26 Feb '01

26 Feb '01

----- Forwarded message from "James A. T. Rice" <jamesr(a)rd.bbc.co.uk> ----- Date: Tue, 27 Feb 2001 00:39:38 +0000 (GMT) From: "James A. T. Rice" <jamesr(a)rd.bbc.co.uk> X-Sender: <jamesr(a)inet15> To: <members(a)lonap.net>, <ops(a)linx.net> Subject: Warning: Cisco RW community backdoor. Precedence: bulk If your router responds to `snmpwalk router.isp.net.uk ILMI`, you probabally will want to do the following to disable it: conf t snmp-server community ILMI RO 99 access-list 99 deny any log (pick another spare access-list if 99 isn't available) If you dont, assuming your ios/hardware combination supports it, (most of the bigger routers do) anyone can do things like: `snmpset router.isp.net.uk ILMI system.sysName.0 s \ "ALL YOUR ROUTER ARE BELONG TO US."` Thats a harmless example. You can do almost anything with RW snmp. Warm Regards James -- James A. T. Rice | Email: jamesr(a)rd.bbc.co.uk Internet Operations Engineer | Phone: 01737 839 737 BBC Internet Services, Kingswood Warren, Tadworth, Surrey, UK. ----- End forwarded message ----- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

IOS & BGP
by James Tyson 26 Feb '01

26 Feb '01

Does anyone know what version of IOS the "bgp go faster you bitch" command appears in? It doesnt appear to be in 12.0(14)S. Sigh. Cheers. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

RE: ATM card in Cisco 4500
by Scott, Arron 26 Feb '01

26 Feb '01

Not speaking on behalf of any company in particular, I just wanted to say I know of a number of 4500's and 4700's running in production with the ATM card. Their throughput is limited by the CPU performance, but you can expect to get upwards of 40Mbps through it. If you want more than an OC3 I would suggest you look at something like a 7600 OSR, not speaking on behalf of any company in particular of course. Now we just need a Telco or three in NZ to support ATM at STM-4 rates. Arron Scott -----Original Message----- From: owner-nznog(a)list.waikato.ac.nz [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Dennis Su Sent: Tuesday, 20 February 2001 7:04 p.m. To: nznog(a)list.waikato.ac.nz Subject: ATM card in Cisco 4500 Hi, We would like to purchase a ATM card for a Cisco 4500. Someone has mentioned to us that its ATM card is not very stable, although I doubt it. 4500 series router has been on the market for such a long time after all. I wonder if anyone can give us some previous experience. Good or bad and what type, all welcome. Thanks, Dennis ------------------------------------------------------------------------ ---- ----------------- Dennis Su, BSc MSc Network+ MCP CCNA CCDA CCNP CCDP Team Leader, Network Admin and Development IT Infrastructure, ITS, University of Waikato Hamilton, New Zealand phone:64 7 838 4183 email:d.su(a)waikato.ac.nz http://network-services.its.waikato.ac.nz/people/dennis.html --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 11

software required -- could be urgent
by Chris Wedgwood 24 Feb '01

24 Feb '01

... but probably it's not. Serious network software required. Only the network part isn't completely true :) I _need_ RollCage or RollCage II -- if I don't get this I'm sure something serious will happen; the entire Internet will stop routing or something. I am sure it will. I can feel it. I know the former was for sale at the warehouse for 20 bucks or so, but I can't find it now... the later, no idea. They are both old games by todays standards. Someone somewhere must have either both or one of these games. ... please ... :) --cw P.S. SPAM SPAM SPAM SPAM SPAM SPAM SPAM! --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: ATM card in Cisco 4500
by Scott, Arron 23 Feb '01

23 Feb '01

ATM is FAR WORSE than that, but it helps sell stuff in New Zealand ;-) Arron Scott Not speaking for any company in particular -----Original Message----- From: Joe Abley [mailto:jabley(a)automagic.org] Sent: Friday, 23 February 2001 3:49 a.m. To: Scott, Arron Cc: Dennis Su; nznog(a)list.waikato.ac.nz Subject: Re: ATM card in Cisco 4500 On Thu, Feb 22, 2001 at 02:17:09PM +1100, Scott, Arron wrote: > Now we just need a Telco or three in NZ to support ATM at STM-4 > rates. Is anybody really waiting for that? If you're shifting an STM-4s worth of data around, it's probably a stream of packets, and it's probably IP, and you probably want to use POS. You probably don't want the additional complexity, cost, operational overhead, cell tax and SAR latency that using ATM would involve. Also, ATM is the work of Satan, which should be mentioned, for the record. Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 5

RE: ATM card in Cisco 4500
by Scott, Arron 22 Feb '01

22 Feb '01

Yeah yeah ... we're all telling the Service Providers that Broadband is critical, but that still doesn't change the fact that ATM aggregation, ADSL/FR access, legacy support, and the ability to run a fair bit of point-to-point bandwidth over an STM-4 ATM access is still quite attractive for a market like NZ. And being one who had to fight VERY hard to get POS inside a certain Telco here at all, I would love to see more widespread use of it. STM/4 ATM gives my customers what they want and need, not what I want to sell !!! Arron Scott -----Original Message----- From: dean(a)flatnet.gen.nz [mailto:dean(a)flatnet.gen.nz] Sent: Friday, 23 February 2001 4:45 p.m. To: Scott, Arron Cc: Joe Abley; nznog(a)list.waikato.ac.nz Subject: Re: ATM card in Cisco 4500 I'd rather sell something that had a future, and not cripple networking in NZ any more than it already is. No matter how much easier it made the sale. Customers listen to what vendors have to say. Vendors should be telling them the truth, not just what they think will make the sale. Long live POS =) Dean Not speaking for, or about, any company in particular On Fri, Feb 23, 2001 at 02:01:55PM +1100, Scott, Arron wrote: > ATM is FAR WORSE than that, but it helps sell stuff in New Zealand ;-) > > Arron Scott > Not speaking for any company in particular > > -----Original Message----- > From: Joe Abley [mailto:jabley(a)automagic.org] > Sent: Friday, 23 February 2001 3:49 a.m. > To: Scott, Arron > Cc: Dennis Su; nznog(a)list.waikato.ac.nz > Subject: Re: ATM card in Cisco 4500 > > > On Thu, Feb 22, 2001 at 02:17:09PM +1100, Scott, Arron wrote: > > Now we just need a Telco or three in NZ to support ATM at STM-4 > > rates. > > Is anybody really waiting for that? If you're shifting an STM-4s worth > of data around, it's probably a stream of packets, and it's probably IP, > and you probably want to use POS. You probably don't want the additional > complexity, cost, operational overhead, cell tax and SAR latency that > using ATM would involve. > > Also, ATM is the work of Satan, which should be mentioned, for the > record. > > > Joe > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: ATM card in Cisco 4500
by dean＠flatnet.gen.nz 21 Feb '01

21 Feb '01

Having a look on the Cisco Web site it seems that the fastest interface is an oc3. http://www.cisco.com/univercd/cc/td/doc/pcat/4700m.htm It might be an old website though. If it were me I would POC this to death before I bought it. The 4500 is pretty old and MAY not be able to feed an oc12 and do everything that you want it to do. Dean (Who does not speak on behalf of any employer) On Thu, Feb 22, 2001 at 11:40:17AM +1300, Lindsay Druett wrote: > OC12 > > -----Original Message----- > From: dean(a)flatnet.gen.nz [mailto:dean(a)flatnet.gen.nz] > Sent: Thursday, 22 February 2001 11:39 > To: nznog(a)list.waikato.ac.nz > Subject: Re: ATM card in Cisco 4500 > > > > On Wed, Feb 21, 2001 at 04:04:21PM +1300, Dennis Su wrote: > > > We would like to purchase a ATM card for a Cisco 4500. Someone has > > > mentioned to us that its ATM card is not very stable, although I doubt > it. > > > 4500 series router has been on the market for such a long time after > all. I > > > wonder if anyone can give us some previous experience. Good or bad and > what > > > type, all welcome. > > What speed ATM are you talking here? > > > Dean > (Who does not speak on behalf of any employer) > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

Re: ATM card in Cisco 4500
by dean＠flatnet.gen.nz 21 Feb '01

21 Feb '01

=) No Problems. I'd still POC it, But thats just me. Dean (Who does not speak on behalf of any employer) On Thu, Feb 22, 2001 at 12:06:03PM +1300, Lindsay Druett wrote: > I beg your pardon, it is an OC3 indeed (what was I thinking ?) > > -----Original Message----- > From: dean(a)flatnet.gen.nz [mailto:dean(a)flatnet.gen.nz] > Sent: Thursday, 22 February 2001 11:50 > To: Lindsay Druett; nznog(a)list.waikato.ac.nz > Subject: Re: ATM card in Cisco 4500 > > > > Having a look on the Cisco Web site it seems that the fastest interface is > an oc3. > http://www.cisco.com/univercd/cc/td/doc/pcat/4700m.htm > > It might be an old website though. > > If it were me I would POC this to death before I bought it. The 4500 is > pretty old and MAY not be able to feed an oc12 and do everything that you > want it to do. > > > Dean > (Who does not speak on behalf of any employer) > > On Thu, Feb 22, 2001 at 11:40:17AM +1300, Lindsay Druett wrote: > > OC12 > > > > -----Original Message----- > > From: dean(a)flatnet.gen.nz [mailto:dean(a)flatnet.gen.nz] > > Sent: Thursday, 22 February 2001 11:39 > > To: nznog(a)list.waikato.ac.nz > > Subject: Re: ATM card in Cisco 4500 > > > > > > > On Wed, Feb 21, 2001 at 04:04:21PM +1300, Dennis Su wrote: > > > > We would like to purchase a ATM card for a Cisco 4500. Someone has > > > > mentioned to us that its ATM card is not very stable, although I doubt > > it. > > > > 4500 series router has been on the market for such a long time after > > all. I > > > > wonder if anyone can give us some previous experience. Good or bad and > > what > > > > type, all welcome. > > > > What speed ATM are you talking here? > > > > > > Dean > > (Who does not speak on behalf of any employer) > > --------- > > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > > where the body of your message reads: > > unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

ATM card in Cisco 4500
by Dennis Su 21 Feb '01

21 Feb '01

Hi, We would like to purchase a ATM card for a Cisco 4500. Someone has mentioned to us that its ATM card is not very stable, although I doubt it. 4500 series router has been on the market for such a long time after all. I wonder if anyone can give us some previous experience. Good or bad and what type, all welcome. Thanks, Dennis ---------------------------------------------------------------------------- ----------------- Dennis Su, BSc MSc Network+ MCP CCNA CCDA CCNP CCDP Team Leader, Network Admin and Development IT Infrastructure, ITS, University of Waikato Hamilton, New Zealand phone:64 7 838 4183 email:d.su(a)waikato.ac.nz http://network-services.its.waikato.ac.nz/people/dennis.html --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

FYI: ihug DNS server ips.
by Simon Lyall 20 Feb '01

20 Feb '01

Just a note that ihug is in the process of changing it's main DNS ips (as used by customers). Previously almost all customers were using 203.29.160.4 and 203.29.160.2 but we have now switched to 203.109.252.42 and 203.109.252.43. It is likely that there are 10,000s of ihug and ex-ihug customers with the old ip's manually setup in their configurations. Since we are returning these networks to Telstra they will cease being advertised outside our network sometime next week. You may wish to warn your helpdesk to keep an eye open for this. -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | | Home: simon(a)darkmere.gen.nz ihug, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

New 2LD Voting - Feedback request
by Sue Leader 19 Feb '01

19 Feb '01

Greetings There will be a meeting of the Council of the Society this Friday the 23rd. The Council will consider the following options in regard to voting rights for new 2LD applications. Your comments are encouraged: ================= Motion 1 Abstract The Request for Votes for the .bank.nz application requires a voting electorate. After review and consideration 3 options have been presented for discussion and voting. Option 1 The electorate for the RFV shall be members of good standing of ISOCNZ as of the day before the vote is called. Reason: Known community that is easy to reach and identify which has a greater propensity to understand the issues surrounding the vote. Option 2 The electorate for the RFV shall be name holders or name holder representatives of a name in the .nz name space. A person would be only be able to vote once no matter how many names they had that qualified. Reason: The addition of a new 2LD directly affects current name holders. By having a name in the .nz spaces means they are an existing stakeholder in the .nz name space. Option 3 The electorate for the RFV shall be any person that has an email address in the .nz name space, i.e. steven.heath(a)isocnz.org.nz but not steven.heath(a)seranova.com. A person would be only be able to vote once no matter how many email addresses they had that qualified. Reason: By having an address in the .nz name space means they have an affinity with .nz and provides the widest possible community. Also does not exclude anyone based on having membership or an existing name. Preferred Motion 1 wording: That the electorate for the RFV for the .bank.nz be any person that has an email address in the .nz name space. A person would be only be able to vote once no matter how many email addresses they had that qualified. ======= Cheers Sue Sue Leader - Executive Director ISOCNZ (Internet Society of New Zealand Inc) Exe.Dir(a)isocnz.org.nz Voice: +64-4-801-6256 http://www.isocnz.org.nz PLEASE NOTE CHANGE: P.O.Box 11-881, Wellington --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Deadline Extension - Green Paper
by Sue Leader 15 Feb '01

15 Feb '01

Greetings The Society has received requests for extension of the deadline for the SRS Implementation as the notification was not received by everyone on Feb 2 when I orginally sent it out. I resent the notice on the 8th, as even though the message went to the archives and some people had received it, clearly not everyone had. On that basis the Chair has agreed to an extension until Friday March 2 - 5:00pm. Please send all Submissions to me direct for collation. Cheers Sue Sue Leader - Executive Director ISOCNZ (Internet Society of New Zealand Inc) Exe.Dir(a)isocnz.org.nz Voice: +64-4-801-6256 http://www.isocnz.org.nz Postal: Level 1, (e)-Vision Centre, 282 Wakefield St, Wellington "Error: Press any key to continue or any other key to quit..." --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

ORBS blocking Domainz servers
by Don Stokes 15 Feb '01

15 Feb '01

Hello All, A heads-up for anyone using ORBS for spam filtering: ORBS has added the following manual entries to its database: 18.160.46.202.inputs.orbs.org IN TXT "Domainz.net.nz - Attacks on ORBS and ORBS hosters." 50.160.46.202.inputs.orbs.org IN TXT "Domainz.net.nz - Attacks on ORBS and ORBS hosters." 37.16.96.203.inputs.orbs.org IN TXT "Delivery point for Domainz.net.nz - Attacks on ORBS and ORBS hosters." These represent the hosts www.domainz.net.nz, office.domainz.net.nz and mail2.actrix.gen.nz respectively. The records were added on the 9th Feb 2001, according to the ORBS database web pages. The impact of this is that if a site is using ORBS for spam blocking, it will reject mail from the Domainz automated systems, including notifications of passwords, nameserver changes, reminders of accounts due and other automatically generated DRS notifications. It will also reject mail from the Actrix list server, which includes Domainz mailing lists, ISOCNZ mailing lists and presumably others. Normal customer service email should be unaffected, as these come from other Actrix hosts. Suffice to say, none of these addresses have been used to attack the ORBS service or systems, nor do the mail servers on these addresses relay spam or block ORBS queries. Email queries to ORBS by myself and Actrix staff have not elicited a reply. Unless ORBS decides to remove these records, anyone needing to to communicate (or having customers that may need to communicate) with Domainz should ensure that ORBS is not in use by their mail exchangers, or arrangements to bypass the blocks on the Domainz addresses are in place. -- don --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

15 23

zivo.co.nz (ex clearview.co.nz)
by PhoneNet 15 Feb '01

15 Feb '01

Following on from the ORBS discusion...... Anyone else having problems getting replies from zivo.co.nz (formerly clearview.co.nz) Our main email address was used to sign up to several porn sites from one of their IPs - The originating IP for the sign up process was recorded as: 202.78.157.14 which resolves to the address: >> router-cyber.cl.clearview.co.nz. Despite three emails regarding the matter I've had no response from them...... Ian Cousins --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Xtra / WIX
by Richard Naylor 14 Feb '01

14 Feb '01

At 03:35 PM 2/15/01 +1300, Ben Martel wrote: >Tony, > >It is the same for us (CLEAR) at the mo! Their router is there (ie. BGP is >active) but we are not exchanging any prefixes. > >I'm sure someone at Xtra is looking into it - right? Yep - I gave Peter a call about 2:40 and he had someone on the way to fix it. Sounded like internal switch failure/wedge. I understand dial-up users are down also - but then I don't use modems very often...... rich richard.naylor(a)citylink.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Xtra / WIX
by Ben Martel 14 Feb '01

14 Feb '01

Tony, It is the same for us (CLEAR) at the mo! Their router is there (ie. BGP is active) but we are not exchanging any prefixes. I'm sure someone at Xtra is looking into it - right? ~benm --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Xtra / WIX
by Tony Wicks 14 Feb '01

14 Feb '01

Hi all, my peering session with Xtra on WIX has disappeared, anyone know what has happened there ? --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0