- NZNOG - lists.nznog.org

RE: xtra rejecting mail from mailing lists?
by Tech Support 25 Jul '01

25 Jul '01

>On Wed, 25 Jul 2001, Simon Blake wrote: >> I've got a mailing list on one of my servers that appears to have a >> bunch of xtra subscribers on it. Postings to the list get sent to about >> the first 10 xtra users, and then I start getting: >I had someone come up to me with this too. >Apparently when they rang up the helpdesk about it they were told >it wasn't xtra's problem. All I did was suggest they forward the >bounce to postmaster(a)xtra hoping someone does read email there. > >With the 2 examples I saw, it was bouncing emails sent to domains that >were not hosted at xtra. However emails were sent by xtra customers >using xtra's smtp server. One of them tried xtra's smtp server after >they had a problem sending from their own in-house smtp server (thus >eliminating perhaps a possible problem with their server). > >I'll try to get the actual bounce emailed to me. I think it said >something about being unable to relay email > >Lin Hmmm, perhaps Xtra subscribe to ORBS, and have blacklisted their own server..... ;) Peter Gray Telstra Saturn Tech Support E-mail: tech(a)tsnz.net Phone: 0800 949 000 Fax: 04 922 8401 Website: www.netlink.net.nz PO Box 5358, Wellington, New Zealand "Smile," they said "things could be worse!" So I smiled, and things were worse.... --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

'we should all be uncomfortable with the extent to which luck..'
by k claffy 24 Jul '01

24 Jul '01

david moore's analysis of code red: episode 0/1 is at http://www.caida.org/analysis/security/code-red/ [funded by DARPA's ITO office NGI/NMS programs, NSF ANIR, and CAIDA members, david a caida PI] definitely check out jeff brown's animation at bottom; watch carefully around 15:00 for pretty ominous elbow in infection rate (get an epidemiologist to look at it without telling them what it is...) 360,000 machines (well, IP addresses) infected in under 14 hours. from conclusion: // ..in the final analysis, we should all be uncomfortable with the extent to which luck, rather than proactive diligence, maintains the stability of the Internet infrastructure. // it goes without saying that many hosts are still vulnerable. and will likely remain so (to this or the next poison) until our luck runs out. do we expect the next version to have the two weaknesses christopher pointed out today? do we expect the next version won't clear every 3rd bit on the hard drive? almost makes me wonder if some white hat might (should?) have been behind CodeRed as some 'vaccination' attempt. "The bad news is, nobody will do anything about critical infrastructure protection until there's a global catastrophic failure," said Rasch. The good news is, there will be a global catastrophic failure." -- http://www.nando.net/technology/story/44887p-694372c.html the worse news is: protecting 'critical infrastructure' is far from enough. again from http://www.caida.org/analysis/security/code-red/ This assault also demonstrates that machines operated by home users or small businesses (hosts less likely to be maintained by a professional sysadmin) are integral to the robustness of the global Internet. As is the case with biologically active pathogens, vulnerable hosts can and do put everyone at risk, regardless of the significance of their role in the population. fwiw, caida trying to do gentle survey of patching speed, see http://worm-security-survey.caida.org/ k ps: john maddog hall (linux int'l) had a great slide a few months ago at UCSD talk; upshot something like INSTALLED BASE (EARTH) + 20 million linux systems + 450 million gates licenses ==> 4.4 - 6.6 % of the population total ... world population: ~6B ==> 5.4 billion people haven't selected an OS yet [k: maybe we can get them on OS-antioxidants before it's too late] --------- 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: anything going?
by Simon Lyall 24 Jul '01

24 Jul '01

On Wed, 25 Jul 2001, Matt Camp wrote: > Anyone know of any jobs going for experienced > IP/Cisco/Lucent/Unix/perl/php/database/networky type engineers that > don't suck? > > This ones getting kinda old, (the job, not the engineer) and the pay is > actually decreasing. You could apply at ihug Matt, someone with NT experience would be useful :) Actually does anyone know the best places to find jobs in the industry? , I notice that Telecom and I assume most of the others don't advertise a lot of their jobs online (or on their own websites). ObOperational: www.whitehouse.gov has akamai's themselves. Resume online here. | | V -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. --------- 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: anything going?
by Donald Neal 24 Jul '01

24 Jul '01

Simon Lyall: >You could apply at ihug Matt, someone with NT experience would be useful :) >Actually does anyone know the best places to find jobs in the industry? , I >notice that Telecom and I assume most of the others don't advertise a lot >of their jobs online (or on their own websites). Telecom's jobs are at http://telecomnz.hire.com/joblist.html, which is linked to from the official web site. Donald Neal (who works for Telecom but generally does not speak for them) -- Donald Neal Mobility & Calling Platforms Network Delivery Telecom New Zealand Ltd --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

anything going?
by Matt Camp 24 Jul '01

24 Jul '01

Anyone know of any jobs going for experienced IP/Cisco/Lucent/Unix/perl/php/database/networky type engineers that don't suck? This ones getting kinda old, (the job, not the engineer) and the pay is actually decreasing. --- Matt Camp Head Geek Mercury/Quicksilver --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

SuSe Linux Mirrors
by Matthew G Brown 23 Jul '01

23 Jul '01

Anyone Mirroring SuSe 7.x ? , 3.0 isn't cutting the mustard :) Matthew G Brown Tasman Solutions LTD --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Blank vendor letter
by Andrea Moran 23 Jul '01

23 Jul '01

Hi! How are you? I send you this file in order to have your advice See you later. Thanks

5 5

Fax to vendor
by Andrea Moran 23 Jul '01

23 Jul '01

Hi! How are you? I send you this file in order to have your advice See you later. Thanks

5 4

NZNOG Posting Policy
by Donald Neal 23 Jul '01

23 Jul '01

NZNOG People, At present, NZNOG accepts postings from anywhere. A previous effort to switch to accepting mail only from subscribed addresses was abandoned due to the inconveince caused. If anyone wishes another attempt made at that change, please contact me directly. Donald Neal List Administrator -- Donald Neal Mobility & Calling Platforms Network Delivery Telecom New Zealand Ltd --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Antigen found Win32.SirCam.137216 (CA(Vet)) virus
by Antigen 23 Jul '01

23 Jul '01

Antigen for Exchange found Blank vendor letter.doc~pif infected with Win32.SirCam.137216 (CA(Vet)) virus. The file is currently Removed. The message, "Blank vendor letter", was sent from Andrea Moran and was discovered in SMTP Messages\Inbound located at JUNIPER/AMERICAS/BETA. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Antigen found Win32.SirCam.137216 (CA(Vet)) virus
by Antigen 23 Jul '01

23 Jul '01

Antigen for Exchange found Fax to vendor.doc~bat infected with Win32.SirCam.137216 (CA(Vet)) virus. The file is currently Removed. The message, "Fax to vendor", was sent from Andrea Moran and was discovered in SMTP Messages\Inbound located at JUNIPER/AMERICAS/BETA. --------- 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: Fax to vendor
by Steven Perich 23 Jul '01

23 Jul '01

Guys, Anyone with half a brain who's concerned about security wouldn't open this, I know, but I thought I'ld inform the masses of this as a friendly, public service announcement :-) Scan type: Realtime Protection Scan Event: Virus Found! Virus name: W32.Sircam.Worm(a)mm File: Fax to vendor.doc.bat Location: Mail System Action taken: Clean failed : Quarantine succeeded : Date found: Tue Jul 24 09:22:26 2001 Steve > -----Original Message----- > From: owner-nznog(a)list.waikato.ac.nz > [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Andrea Moran > Sent: Tuesday, July 24, 2001 09:06 > To: nznog(a)list.waikato.ac.nz > Subject: Fax to vendor > > > Hi! How are you? > > I send you this file in order to have your advice > > See you later. Thanks > --------- 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: Fax to vendor
by Greg Clare 23 Jul '01

23 Jul '01

WARNING:- This message contained a virus (W32.Sircam.Worm(a)mm). For more details refer:- http://service1.symantec.com/SUPPORT/nav.nsf/aab56492973adccd882569450055235 5/f75929f63f73df5f882569a80022dbd0?OpenDocument Norton Virus definitions dated 17 July 2001 or later will detect this recent worm. Regards Greg > -----Original Message----- > From: Andrea Moran [mailto:andrea(a)petrinamoran.freeserve.co.uk] > Sent: Tuesday, 24 July 2001 9:06 am > To: nznog(a)list.waikato.ac.nz > Subject: Fax to vendor > > > Hi! How are you? > > I send you this file in order to have your advice > > See you later. Thanks > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

(no subject)
by AngelaMcIntee＠aol.com 22 Jul '01

22 Jul '01

Can anyone tell me the physical address of the Sprint NAP in Pennsauken, NJ? Thanks, Angela --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Julian Angelo - Conclusion
by Donald Neal 22 Jul '01

22 Jul '01

<Multimedia>If you wish this posting to be a multimedia experience, go to http://www.netspace.org/~dmacks/internet-songbook/lart-lart-lart-the-spamme… and sing the contents of that page to yourself while reading.</Multimedia> NZNOG People, Three days ago I posted to this list, saying >Just over a year ago, there was discussion on this list of spamming by >one Julian Angelo. He has now approached me, asking to have these >references removed from the NZNOG archive. It seems that prospective >employers who look up his name on the web find these archive entries, a >fact which may not be helping his career any. >If any network operator has an objection to these entries being removed >from the archive, could they please contact me directly. I had a number of reasons for doing things in this way. For one thing, I do not see myself as owner in the usual sense of that word of this list or its archive. For another, the content of email sent to me in response to such an enquiry might conceivably be actionable. I also take the view that spammers are thieves who must be shown the error of their ways and encouraged to live useful, constructive lives. I am in principle very happy with the idea of editing the names of the guilty out of publicly-readable archives a suitable period after their offending ceases. The chance to gain useful employment would then be one of the reasons why they would give up their vile activities in the first place. My request to be contacted directly was followed by close to fifty emails to the list. Some had particularly disappointing content. The acceptable use policy for this list states that character assassination is unacceptable. It also states that discussion unrelated to Internet technical and operational matters is not appropriate. Discussions of a legal nature are particularly discouraged. This has not been a good week for this list's s/n ratio, nor for constructive discussion. I am all in favour of a certain amount of humour of questionable relevance, but there was little of that here. The only such contribution was Matt Camp's, which observed "I'm sure there's a lesson there. f33r the far-reaching p0w3rz of NZNOG! [...] we shall [...] smite the career prospects of spammers and script kiddies with our flaming LARTting tool of justice!" I have doubts about his spelling of LARTing, but I too am sure there's a lesson here. As I've already said, I see publicity and its withdrawal as a useful tool in encouraging spammers into the paths of righteousness. Regrettably, the point was not taken up by others. My thanks to those who did respond directly to me. The suggestion that by altering the archive's contents on any occasion I might become responsible for all of its content was one I had not previously considered. Other opinions expressed fell into two groups. Some subscribers believed that an apology was called for before Mr Angelo's name was removed from the archive, while others felt that archives should not ever be altered. Some of this latter group observed that archiving an apology from Julian Angelo would give prospective employers a full piucture of events. I count four subscribers in the first group and thirteen in the second. Removing from the count people I believe not to be staff of network operators, and the subscriber who expressed both opinions, leaves three in the first group and eight in the second. I feel myself to be bound by this expression of the views of subscribers, and will not seek to have the archives changed. At no point has anyone even implied to me that Julian Angelo has done anything wrong since the events of July 2000. I went into this thinking that was the question. Donald Neal List Administrator/Muggins <Multimedia>You can stop singing now.</Multimedia> -- Donald Neal Mobility & Calling Platforms Network Delivery Telecom New Zealand Ltd --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

12 21

[dranch@trinnet.net: How the IIS Red Worm works..]
by Dean Pemberton 21 Jul '01

21 Jul '01

> so which ISP in Wellington was it that is reported to have lost its servers > as a result of thei worm (reported in the Herald).... and did it really > infect/affect 250000 sites? > > Ian Dunno about the first one - but there is a portion in this article that talks to your second point. Dean ----- Forwarded message ----- Interesting.. From http://www.w2knews.com/subscribe.cfm?id=W2K -- Explanation As stated earlier the .ida "Code Red" worm is spreading throughout IIS Web servers on the Internet via the .ida buffer-overflow attack that was published last month. The following are the steps that the worm takes once it has infected a vulnerable Web server: Setup initial worm environment on infected system. Setup 100 threads of the worm. Use the first 99 threads to spread the worm (infect other Web servers). � The worm spreads itself by creating a sequence of random IP addresses. However, the worm's list of IP addresses to attack is not all together random. In fact, there seems to be a static seed (a beginning IP address that is always the same) that the worm uses when generating new IP addresses. Therefore every computer infected by this worm is going to go through the same list of "random" IP addresses. Because of this feature, the worm will end up re-infecting the same systems multiple times, and traffic will cross traffic back and forth between hosts ultimately creating a denial-of-service type effect. The denial-of-service will be due to the amount of data being transferred between all of the IP addresses in the sequence of random IP addresses. The worm could have done truly random IP generation and that would have allowed it to infect many more systems much faster. We are not sure why this was not done, but a friend of ours did pose an interesting idea: If the person who wrote this worm owned an IP address that was one of the first hundred or thousand to be scanned, then they could setup a "sniffer" and anytime and IP address tried to connect to port 80 on their server they would get confirmation that the IP address that connected to them was infected with the worm. With this knowledge, they would be able to create a list of the majority of systems that were infected by this worm. The 100th thread checks to see if it is running on an English (US) Windows NT/2000 system. � If the infected system is found to be a English (US) system, the worm will proceed to deface the infected system's website. The local Web server's Web page will be changed to a message that says: "Welcome to http://www.worm.com!, Hacked By Chinese!". This hacked Web page message will stay "live" on the Web server for 10 hours and then disappear. The message will not appear again unless the system is re-infected by another computer. � If the system is not an English (US) Windows NT/2000 system, the 100th worm thread is also used to infect other systems. Each worm thread checks for c:\notworm. � If the file c:\notworm is found, the worm goes dormant. � If the file is not found, each thread will continue to attempt to infect more systems. Each worm thread checks the infected computer's system time. � If the date is past the 20th of the month (GMT), the thread will stop searching for systems to infect and will instead attack www.whitehouse.gov. The attack consists of the infected system sending 100k bytes of data (1 byte at a time + 40 bytes overheard for the actually TCP/IP packet) to port 80 of www.whitehouse.gov. This flood of data (410 megabytes of data every 4 and a half hours per instance of the worm) would potentially amount to a denial-of- service attack against www.whitehouse.gov. � If the date is between the 1st and the 19th of the month, this worm thread will not attack www.whitehouse.gov and will continue to try to find and infect new Web servers. We have calculated that the worm can attempt to infect roughly half a million IP addresses a day. This is a rough estimate generated by testing on a very slow network. At the time of writing this document (July 19th, 3:00pm), we have had reports from administrators that have been probed by over 196 thousand unique hosts. This leads us to believe that this worm has infected at least 196 thousand computers. During testing we noticed that sometimes the worm does not execute "normally" and will continue to spawn new threads until the infected machine crashes and has to be rebooted, effectively killing itself. We have not been able to isolate the cause of this behavior. ----- 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

2 1

RE: the .ida "Code Red" worm - ISP suffers?
by PhoneNet 21 Jul '01

21 Jul '01

so which ISP in Wellington was it that is reported to have lost its servers as a result of thei worm (reported in the Herald).... and did it really infect/affect 250000 sites? Ian --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

China-diesel fuel injection 7/20
by china-lutong.com 19 Jul '01

19 Jul '01

hi: My name is ChenHua, and I'm writing on behalf of the China-Lutong mechanical company. Located in the south east of China, we specialize in hydraulic heads for the VE distributor pump. We can supply standard, good quality units at a very competitive price. The following types are available: Engine model VE PUMS code NO UNIT PRICE(EX WORK) ISUZU 4JB1 NP-VE4/11F1800LNP777 146402-0920 $USD40 ISUZU 4JB1 NP-VE4/11L(DENSO) 096400-1600 $USD40 ISUZU 4JB1 NP-VE4/11R 146402-0820 $USD45 ISUZU 4JA1 NP-VE4/11R 146402-3820 $USD45 ISUZU 4JA1 NP-VE4/12R 146430-1420 $USD45 CUMMINS 6BT NP-VE6/12F1050R381-7 1 468 336 423 $USD45 IVECO 8140 NP-VE4/11FR1900R127 1 468 334 798 $USD45 We use precision forging technology to create our products and surface treat them using an imported shot-blasting machine. The constant grinding process guarantees identical clearance in each plunger. Because we have been in the field of diesel fuel injection systems for quite a few years, we are acquainted with many domestic manufacturers of, and sales agents for, parts such as injector nozzles, plungers, delivery valves and so on. If you are interested in our products, please contact me. Thank you for your interest in our company. Best regards! C.Hua Sale & purchasing department director HTTP://WWW.China-LuTong.COM C.H(a)CHINA-LUTONG.COM

1 0

Full analysis of the .ida "Code Red" worm.
by Chris Rigby 19 Jul '01

19 Jul '01

I think this is something we should all be aware of for those of you not on bugtraq (which I hope most of you are.) This attack has gone from something like 0 hits in my web logs yesterday to 11 in the last 4 hours Some people are estimating over 12,000 hosts infected already. Also to worry about are later announcements that : "A notable side effect of this.. the worm signature is wreaking havoc with Cisco 675, 677, and 678 DSL routers that have the Web Based Configuration Interface enabled." since they lock up when "?" is sent to them in a URL. And apparently has issues for some 7500 size routers. The main thing I'm concenred over is that the worm is programmed to flood www.whitehouse.gov between 20:00pm and 23:59 (local system time). I'm not looking forward to what effect this might have on the internet. Escpecially the small outbound links in NZ. Chris Rigby Senior Systems Engineer IHUG - Into the Internet ---------- Forwarded message ---------- Date: Wed, 18 Jul 2001 22:40:11 -0700 From: Marc Maiffret <marc(a)eeye.com> To: BUGTRAQ <BUGTRAQ(a)securityfocus.com> Subject: Full analysis of the .ida "Code Red" worm. The following is a detailed analysis of the "Code Red" .ida worm that we reported on July 17th 2001. This analysis was performed by Ryan Permeh and Marc Maiffret of eEye Digital Security. The disassembly (complete with comments) was done by Ryan "Shellcode Ninja" Permeh. Table of Contents ================= 1. Introduction 2. Explanation 3. Commentary 4. Deep Analysis 5. Conclusion 6. Appendix 7. Credits You can get a copy of this analysis, commented disassembly, full IDA database, and binary of worm from http://www.eeye.com/html/advisories/codered.zip Introduction ============ On Friday July 13th we received packet logs and information from 2 network administrators that were experiencing large amounts of attacks targeting the recent .ida vulnerability that eEye Digital Security discovered (http://www.eeye.com/html/Research/Advisories/AD20010618.html) on June 18, 2001. After reviewing the logs sent to us we determined that in fact someone had released a worm into the Internet that was spreading rapidly through IIS web servers. The full analysis of the .ida "Code Red" worm has provided numerous new details as to the functionality and method of propagation of this worm. For instance this worms purpose ultimately seems to be to perform a denial of service attack against www.whitehouse.gov. Also it has been found that only US English Windows NT/2000 systems will show the defaced ("Hacked by Chinese !") web page. We've designated this the .ida "Code Red" worm, because part of the worm is designed to deface web pages with the text "Hacked by Chinese" and also because code red mountain dew was the only thing that kept us awake all last night to be able to disassemble this exploit even further. Explanation =========== As stated earlier the .ida "Code Red" worm is spreading throughout IIS web servers on the Internet via the .ida buffer overflow attack that was published weeks ago. The following are the steps that the worm takes once it has infected a vulnerable web server. 1. Setup initial worm environment on infected system. 2. Setup a 100 threads of the worm 3. The first 99 threads are used to spread the worm (infect other web servers). -The worm spreads itself by creating a sequence of random IP addresses. However, the worm's randomization of IP addresses to attack is not all together random. In fact there seems to be a static seed that the worm uses when generating new IP addresses to try to attack. Therefore every computer infected by this worm is going to go through the same list of random IP addresses to try to infect. The "problem" with that is that the worm is going to end up reinfecting systems and also end up crossing traffic back and forth between hosts to end up creating a denial of service type affect because of the amount of data that will be transferred between all the IP addresses in the sequence of random IP addresses. The worm could have done truly random IP generation and that would have allowed it to infect a lot more systems a lot faster. We are not sure why that was not done but a friend of ours did pose an interesting idea... If the person who wrote this worm owned an IP address that was one of the first hundred or thousand etc... to be scanned then they could setup a sniffer and anytime and IP address tried to connect to port 80 on their IP address they would know that the IP address that connected to them was infected with the worm and they would therefore be able to create a list of the majority of systems that were infected by this worm. 4. The 100th thread checks to see if it is running on a English (US) Windows NT/2000 system. -If the infected system is found to be a English (US) system then the worm will proceed to deface the infected systems website. That means... the local web servers web page will be changed to a message that says Welcome to http://www.worm.com !, Hacked By Chinese!. This hacked web page message will stay "live" on the web server for 10 hours and then disappear and never appear again unless the infected system is re-infected by another host. -If the system is not a English (US) Windows NT/2000 system then the 100th worm thread is also used to infect other systems. 5. Each worm thread checks for c:\notworm -If the file c:\notworm is found, the worm goes dormant. -If the file is not found then each thread will continue to attempt to infect more systems. 6. Each worm thread will now check the infected computers time. -If the time is between 20:00 UTC and 23:59 UTC then the worm will proceed to use this thread to attack www.whitehouse.gov. The attack consists of the infected system sending 100k bytes of data to port 80 of www.whitehouse.gov therefore potentially performing a denial of service attack against www.whitehouse.gov. -If the time is below 20:00 UTC then this worm thread will try to find and infect new web servers. In testing we have calculated that the worm can attempt to infect roughly half a million IP addresses a day and that was a ruff estimate made from using a very slow network. As of writing this document (July 18 6:49pm) we have had reports from administrators that have been probed by over 12 thousand unique hosts. That basically means at least 12 thousand hosts have been infected by this worm. In testing we have seen that sometimes the worm does not execute correctly and will continue to spawn new threads until the infected machine crashes and has to be rebooted. We have not been able to isolate the cause of this behavior. Commentary ========== As we sat and watched this worm spread itself through the Internet we were somewhat dumbfounded as to the number of reported systems being infected. The main reason for that is that this worm is using a, what we thought to be, very well known vulnerability. A patch for this vulnerability has been available for over a month now and at the time of the release of the vulnerability many news agencies ran stories about it therefore trying to spread awareness. Even with all of that though there have still been, at the very least, 12 thousand web servers infected by this worm. So we once again encourage administrators to pay attention to security issues and patch their systems as soon as patches are available for holes. All of this research would not be available if we were not a Full Disclosure company and if the many people who helped us research this worm were against full disclosure. Although we did not release any exploit code for the .ida vulnerability, the computer underground still had no problem creating a devastating worm. In the past we have seen a much higher percentage of patched systems when example exploit code was provided. System administrators do not believe vulnerabilities exist without a public exploit, or until something like this worm happens forcing them to patch their systems. We feel that if the security community moves away from Full Disclosure more incidents like this will happen and everyone will be left in the dark as to what is going on. An example of why full disclosure is so important would be this worm itself. Chances are this worm would have not been discovered if we had not fully disclosed details about the .ida vulnerability, allowing Intrusion Detection System vendors to create signatures for the .ida buffer overflow attack. Because of the way that IIS performs logging (logging a request after processing it), servers hit with this worm will actually have no traces of information left in the IIS log files making tracking this worm (via IIS logs) virtually impossible. The first instances of _anyone_ learning anything useful about this worm was via Intrusion Detection Systems that had signatures based on our .ida vulnerability research which would not have been there if not for full disclosure. The computer underground continues to find vulnerabilities everyday. If full disclosure goes away, then the general security community is left in the dark, and therefore so are administrators. More and more we are seeing an increase in worms attacking the Internet. There have been about 2 or 3 worms in as many months. Worms force computer security to become a global issue. With the rise of the Internet, not only do you have to worry about securing your own systems, you must also be careful of your "neighbors" systems. For instance with this worm even if you have done everything right (installed the .ida patch etc...) your network connection could still be taken down because of the amount of data flooding you from all of the "other guys" who hadn't applied patches and were infected by this worm. It is important to not only maintain your own security but make sure that other people you come in contact with secure their sites. Only with global cooperation to maintain security will the threat of worms start disappear. We received information from "friends" that leads us to believe that this worm is actually a derivative of another worm which was written to exploit the first ever remote IIS buffer overflow (also discovered by eEye Digital Security), the .htr buffer overflow. From reports, the .htr worm had a much smaller infection base and seemed to go under the radar probably because the .htr vulnerability was/is very old. Deep Analysis ============= The following is a very detailed analysis of what the worm is doing at each step of its infection. Full disassembled and commented worm code is available at our website at http://www.eeye.com/html/advisories/codered.zip. It will be provided as both a assembly text dump and as a IDA (Interactive Disassembler) database file. We have chosen not distribute the worm code in this eMail as to not clog up your bandwidth anymore then we already are >:-] Note: We will use CODEREF comments in the analysis to reference where we are in the disassembled code so you can "follow along" with us. The tools that we used to perform this detailed analysis were: IDA (Interactive Disassembler) from www.datarescue.com. IDA is an advanced disassembler that made this analysis possible. MS VC++ debugging environment. We used this to monitor modified pieces of the worm as they interacted with IIS. Ryan's brain + Marc's brain + private eEye tools. No... you cant have any of those. We will be heavily referencing the disassembled worm code in the following analysis. In an attempt to make this easier to understand we have broken the functionality of the worm into 3 parts. The core worm functionality, the worm hack web page functionality and the attack www.whitehouse.gov functionality. Core worm functionality ----------------------- 1. Initial infection vector (i.e. host is vulnerable to the .ida attack and gets hit with this worm). The initial infection starts to take place when a web server, vulnerable to the .ida attack, is hit with a HTTP get request that contains the necessary code to exploit the .ida attack and uses this worm as its payload. At the time of the .ida overflow a systems stack memory will look like the following: <MORE 4E 00> 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 92 90 58 68 4E 00 4E 00 4E 00 4E 00 4E 00 4E 00 FA 00 00 00 90 90 58 68 D3 CB 01 78 90 90 58 68 D3 CB 01 78 90 90 58 68 D3 CB 01 78 90 90 90 90 90 81 C3 00 03 00 00 8B 1B 53 FF 53 78 EIP is overwritten with 0x7801CBD3 which an address within msvcrt.dll. The code at 0x7801CBD3 disassembles to: call ebx When EIP is overwritten with call ebx it then causes program flow to divert back to the stack. The code on the stack jumps into the worm code that's held in the body of the initial HTTP request. 2. Sets up some initial stack variables CODEREF: seg000:000001D6 WORM At this point we are executing the initial code of the worm. The first thing to happen is that the worm sets up a new stack for its own use. The new stack is 218h bytes, filled with CCh. The worm code then moves on to initialize its function jump table. The entire worm heavily uses an EBP stack based memory offset system. This means that all variables are referenced as EBP-X values. On our website we have a document called worm-ebp.txt that attempts to track stack usage throughout the course of the worm code. 3. Load functions (create the "jump table") CODEREF: seg000:00000203 DataSetup The first thing the worm code does is reference the data portion of the exploit code at EBP-198h. The worm then needs to setup its internal function jump table. A function jump table is a stack based table used to store function addresses. It allows the worm to generate the function addresses at run time (This makes the worm have a better chance of executing cleanly on more systems). The technique used by this worm is what is called an RVA (Relative Virtual Addresses) lookup. Basically this means that all functions, or specifically GetProcAddress, are found within IIS itself. For more details on RVA please consult any good PE (Portable Executable, the executable file format for Microsoft platforms) documentation, or read through the assembly code of this worm. In a nutshell, RVA techniques are used to get the address of GetProcAddress. GetProcAddress is then used to get the address of LoadLibraryA. Between these two functions all other functions that the worm may need can be easily found. The worm uses these two functions to load the following functions: >From kernel32.dll: GetSystemTime CreateThread CreateFileA Sleep GetSystemDefaultLangID VirtualProtect >From infocomm.dll: TcpSockSend >From WS2_32.dll: socket connect send recv closesocket Finally the worm stores the base address of w3svc.dll which it will later use to potentially deface the infected website. 4. Check the number of threads the worm has created. CODEREF: seg000:00000512 FUNC_LOAD_DONE Here the worm seems to perform a WriteClient (Part of the ISAPI Extension API), sending "GET" back to the attacking worm. This possibly could be a way of telling attacking worms that they have successfully infected a new host. Next the worm code will count the number of worm threads already in action. If the number of threads is 100 then control is shifted to the Worm hack web page functionality. If the number of threads is below 100 then the worm creates a new thread. Each new thread is an exact replica of the worm (Using the same code base). The worm now continues its path of execution. 6. Checks for the existence of c:\notworm CODEREF: seg000:0000079D DO_THE_WORK There seems to be a to be built in "lysine deficiency" (See Jurassic Park, or Caesar's paper on this at www.rootkit.com) A "lysine deficiency" is a built in check to keep malicious code from spreading further. In this case the "lysine deficiency" is a check for the existence of the file c:\notworm. If this file exists then the worm will become dormant. This means it will not attempt to make connections out to other IP addresses to try to infect. If this file does not exist then the worm continues onto the next step. 7. Check the infected systems time (computer clock) CODEREF: seg000:00000803 NOTWORM_NO The worm will now check the infected systems local time (in UTC). If the hour is greater then 20:00 UTC then the worm will proceed to goto the first step of the attack www.whitehouse.gov functionality. If the time is less than 20:00 UTC then the worm will attempt to continue to try to infect new systems. 8. Infect a new host (send .ida worm to a "random" IP address on port 80). At this point the worm will resend itself to any IP addresses which it can connect to port 80 on. It uses multiple send()'s so packet traffic may be broken up. On a successful completion of send, it closes the socket and goes to step 6... therefore repeating this loop infinitely. Worm hack webpage functionality ------------------------------- This functionality is called after a hundred threads are spawned within the worm. 1. Check if local system default language is English us then goto step 6 of core worm functionality. CODEREF: seg000:000005FE TOO_MANY_THREADS The first thing the worm does is get the local codepage. A codepage specifies the local operating system language (I.E. English (US), Chinese, German etc...). It then compares the local codepage against 0x409. 0x409 is the codepage for English (US) systems. If the infected system is an English (US) system then the worm will proceed to deface the local systems webpage. If the local codepage is not English (US) then this worm thread will goto step 6 of core worm functionality. 2. Sleep for 2 hours. CODEREF: seg000:00000636 IS_AMERICAN This worm thread now sleeps for 2 hours. We anticipate that this is to allow the other worm threads to attempt to spread the infection before making a presence known via defacing the infected systems webpage. 3. Attempt to modify infected systems webpages in memory. CODEREF: seg000:0000064F HACK_PAGE This worm uses an interesting technique called "hooking" to effectively deface (alter) an infected systems webpages. Hooking is modifying code in memory to point to code that the worm provides. In this case the worm is modifying w3svc.dll to change the normal operation of a function called TcpSockSend. TcpSockSend is what w3svc.dll (IIS core engine) uses to send information back to the client. By modifying this, the worm is able to change data being written back to clients who request web pages of an infected server. To perform hooking, first the worm makes the first 4000h bytes of w3svc.dll's memory writable. In a normal situation the memory for w3svc.dll (and basically all mapped dll's) is read-only. It uses the function VirtualProtect to change the memory of w3svc.dll to be writable, saving the old state to a stack variable. It then uses the saved codebase of w3svc.dll (from step 3 of core worm functionality) as a start point to search the import table (again see PE header documentation) for the address of TcpSockSend. Once the address for TcpSockSend is located the worm then replaces TcpSockSend's actual address with an address within the worm. The address that TcpSockSend now points to is a function within the worm that will return the "Hacked by Chinese !" webpage. The CODEREF for this function is seg000:00000C9A FAKE_TCPSOCKSEND. This thread of the worm now sleeps for 10 hours. During this 10 hours all web requests to the infected server will return the "Hacked by chinese !" webpage. After the 10 hours is up this thread will return w3svc.dll to its original state, including re-protecting memory. Execution after this proceeds to step 6 of the core worm functionality. Attack www.whitehouse.gov functionality --------------------------------------- Sooner or later every thread within the worm seems to shift its attacking focus to www.whitehouse.gov. 1. create socket and connect to www.whitehouse.gov on port 80 and send 100k byes of data CODEREF: seg000:000008AD WHITEHOUSE_SOCKET_SETUP Initially the worm will create a socket and connect to 198.137.240.91 (www.whitehouse.gov/www1.whitehouse.gov) on port 80. CODEREF: seg000:0000092F WHITEHOUSE_SOCKET_SEND If this connection is made then the worm will create a loop that performs 18000h single byte send()'s to www.whitehouse.gov. CODEREF: seg000:00000972 WHITEHOUSE_SLEEP_LOOP After 18000h send()'s the worm will sleep for about 4 and a half hours. It will then repeat the attack against www.whitehouse.gov (goto step one of Attack www.whitehouse.gov functionality). Appendix ======== This is associated information about the "Code Red" worm including how to stop the worm, commentary on the worm, and dispelling common misconceptions about this worm. How to secure your system from this .ida "Code Red" worm? --------------------------------------------------------- Microsoft patch for this .ida vulnerability http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/ bulletin/MS01-033.asp The worm spreads itself to new vulnerable systems via the .ida vulnerability. Applying this patch will keep your server from being infected. However, as stated earlier, because of the way the worm creates its list of "random" IP addresses to attack, you could still be affected by a high traffic overload denial of service. eEye Digital Security Advisory for .ida vulnerability http://www.eeye.com/html/Research/Advisories/AD20010618.html We initially discovered the .ida vulnerability which is being used by this worm as its infection vector. The above advisory details our research of that specific vulnerability. We worked with Microsoft to help them create a patch for the .ida vulnerability. SecureIIS - Application firewall, stops known and unknown IIS vulnerabilities. http://wwww.eeye.com/secureiis We do produce a product that protects IIS web servers from attack which is one of the reasons that we were so quick to research this worm. Funny enough in our initial testing we couldn't get the worm to work because we forgot we had SecureIIS enabled on the lab web server. heh. I have been infected by this worm what can I do? ------------------------------------------------ The first thing you must do is goto the Microsoft security site, as referenced above, and install the .ida patch ASAP. The worm will remain in memory until you reboot your server so make sure to reboot after installing the .ida patch. I think I am infected, how can I tell? -------------------------------------- An infected system will show an increase in load (processor/network). It will also show a number of external connections (or attempts) to port 80 of random IP addresses. You can see this by doing a "netstat -an" from a MS-DOS prompt. Either way do not take any chances... if your system is missing the .ida patch then install it ASAP and reboot. How to setup your IDS to detect this specific worm? --------------------------------------------------- The following is part of the packet data that is sent for this .ida "Code Red" worm attack: GET /default.ida?NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNN%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3% u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531b%u53ff%u0078%u0000%u00=a HTTP/1.0 Just add that to your IDS signature database. What are some common misconceptions about the "Code Red" worm? -------------------------------------------------------------- 1. It connects to worm.com. This worm only specifies www.worm.com in the initial HTTP GET request HOST: header and in the defaced page show on English (US) systems. This worm does _not_ connect to www.worm.com. This worm operates completely independent and can spread and infect systems without having a single point of failure. What that means is that this worm will be wild on the Internet until there is a _VERY_ high degree of systems that go and install the .ida patch. 2. This worm is based off of hsj's "proof of concept" .ida exploit. This worm is _NOT_ based off of hsj's "proof of concept" .ida exploit. His exploit code had no worm functionality. It was a simple exploit shell that had little to no implicit functionality. It was designed to prove to administrators the seriousness of this vulnerability so that they would install patches ASAP. Credits ======= Ken Eichman of Chemical Abstracts Service Matthew Asham of Left Coast Systems Corp and a large handful of administrators who gave us much needed data to piece this together. Signed, eEye Digital Security T.949.349.9062 F.949.349.9538 http://eEye.com/Retina - Network Security Scanner http://eEye.com/Iris - Network Traffic Analyzer http://eEye.com/SecureIIS - Stop known and unknown IIS vulnerabilities "Its not a virus! Its a worm!" - z3r0 c00l "Whats this one eat?" - l0rd n1k0n "th1s 0n3 34ts 11S s3rv3rs!" - ch4m3l30n h4ck3rs --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

17 35

Code Red --- request for logs (from NANOG)
by Chris Wedgwood 19 Jul '01

19 Jul '01

>From NANOG: From: "Steven M. Bellovin" <smb(a)research.att.com> To: nanog(a)merit.edu Cc: Balachander Krishnamurthy <bala(a)research.att.com> Subject: Re: Code Red -> Router Memory depletion? Date: Thu, 19 Jul 2001 20:39:31 -0400 Message-Id: <20010720003931.77D057B57(a)berkshire.research.att.com> X-Mailer: exmh version 2.1.1 10/15/1999 A colleague of mine, Balachander Krishnamurthy, is looking for Web server logs from sites that have been attacked by Code Red. He's working on analysis techniques to detect flash crowds, DDoS attacks, etc. Please reply directly to him (bala(a)research.att.com) if you can supply any data. (You can see the kind of stuff he's been doing by looking at some of his recent papers, at www.research.att.com/~bala/papers) --------- 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: Full analysis of the .ida "Code Red" worm.
by Greg Clare 19 Jul '01

19 Jul '01

Hits on my home connection started at 4:51am, with 17 unique source addresses logged so far. Greg > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Friday, 20 July 2001 9:50 am > To: 'Dean Pemberton'; 'Chris Rigby' > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: Full analysis of the .ida "Code Red" worm. > > > 12 hits on my home server only... many more on the IDG ones :-( > > -- > > Juha --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

RE: Full analysis of the .ida "Code Red" worm - Attacks stop
by Lindsay Druett 19 Jul '01

19 Jul '01

www.microsoft.com got hit today. I went to their site and had the message "Hacked by Chinese" in red letters. Pity, next time I logged in, I got the normal web page, a bit disappointing.... But I logged in again later, in the same web page, and got the "Hacked by Chinese", so it must be only a few of their servers. So much for "round robin" load sharing, they should be using a Cisco content switch. After 6days The attacks have stoped hitting my server in the past 10 minutes ... Who did what to whom... where is the corpse.... Michael --------- 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

Help with survey needed
by Frank March 19 Jul '01

19 Jul '01

I have been asked to assist with recruitment for an online survey of ISPs and IT companies in New Zealand. The survey is being conducted by the Information Technology Group at the Center for International Development, Harvard University in conjunction with the World Economic Forum and will be used to compile the Global Information Technology Readiness Report (GITRR). The survey for Internet Service Providers (ISPs) can be found at: http://www.cid.harvard.edu/ciditg/isp The survey for other kinds of IT companies can be found at: http://www.cid.harvard.edu/ciditg/it It is suggested that the survey should be completed by someone in a senior management position in your company or organisation. If you do not feel you 'qualify' please pass this on in your organisation to someone who does. I am distributing this to the NZNOG, InternetNZ members, and GOVIS email lists (apologies for duplications). Please feel free to further distribute to other contacts if you think it would be useful. If you want to find out more, I have appended below the unexpurgated and (largely) unedited text sent to me by Indran Ratnathicam, who is in charge of the survey. Thank you Frank March Specialist Advisor, IT Policy Group Ministry of Economic Development, PO Box 1473, Wellington, NZ Ph: (+64 4) 474 2908; Fax: (+64 4) 471 2658 <from Indran> You are invited to become a collaborator and participant in a major research project, the Global Information Technology Readiness Report (GITRR). The GITRR, a new venture between Harvard University and the World Economic Forum, aims to make an important contribution to the understanding of the New Economy and global IT usage. This report will be published in the Fall 2001, and will assess the global IT situation for nearly 100 countries, including New Zealand. The GITRR will provide: · A background for policy discussions by your government and international bodies that will influence the IT and economic development in your country, including your company's activities. · A clearly identified list of your country's relative IT strengths that may spur investment or become a source of competitive advantage in your industry or region. · A clearly identified list of your country's areas for IT development, which can be used to focus future development initiatives by both the public and private sectors. · A tool for international IT companies to increase their understanding of local markets, their opportunities and their challenges. As an IT leader of New Zealand, you are in a unique position to accurately portray where your country stands with regard to the adoption and use of IT within the global context. Your cooperation is essential in adding value to the GITRR and in guaranteeing inclusion of your country in the Report. All you need to do is fill out an online survey. The survey for Internet Service Providers (ISPs) can be found at: http://www.cid.harvard.edu/ciditg/isp The survey for other kinds of IT companies can be found at: http://www.cid.harvard.edu/ciditg/it It will take no more than 30 min of your time to complete and you will not have to necessarily stay logged on to the Internet while you are filling it out. Please fill out the survey by August 3, 2001. If you have additional comments/ queries, please do not hesitate to get in touch with me at Indran_Ratnathicam(a)ksg.harvard.edu. Please rest assured that individual questionnaires remain strictly confidential. Thank you in advance for taking the time to complete this survey. With best regards, Indran Ratnathicam Global IT Readiness Report Information Technologies Group Center for International Development at Harvard University Further details about the Global IT Readiness Report can be found at: http://www.cid.harvard.edu/ciditg/gitrr/ PS: If you are aware of other IT leaders in your country please direct them to the survey --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

None
by Ivan Walker 19 Jul '01

19 Jul '01

subscribe 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

Code Red
by Thomas Salmen 19 Jul '01

19 Jul '01

Niiiice... [root(a)proxy1 /root]# grep -c default.ida access.log 721522 [root(a)proxy2 /root]# grep -c default.ida access.log 717971 Cheers, Thomas Salmen System Administrator Radionet Ltd. 1/72 Paul Matthews Road Albany, Auckland, New Zealand Ph: +64 9 414 0300 ext 718 --------- 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: Update to "Code Red" Worm. Its a date bomb, not time.
by Greg Clare 19 Jul '01

19 Jul '01

>-----Original Message----- >From: Marc Maiffret [mailto:marc(a)eeye.com] >Sent: Friday, 20 July 2001 8:55 a.m. >To: BUGTRAQ >Subject: Update to "Code Red" Worm. Its a date bomb, not time. > > >Thanks to Eric from Symantec for tossing us a note about the >worm being Date >based and not Time based. > >We made an error in our last analysis and said the worm would start >attacking whitehouse.gov based on a certain time. In reality >its based on a >date (the 20th UTC) which is tomorrow. > >If the worm infects your system between the 1st and the 19th >it will attempt >to deface the infected servers web page or try to propogate >itself to other >systems. On the 20th all infected threads will attempt to attack >www.whitehouse.gov. This seems to continue until the worm is >removed from >the infected system. > >Any new infection that happens between the 20th and 28th will >most likely be >someone "hand infecting" your system as all other worms should >be attacking >whitehouse.gov. If for some reason you are infected between >the 20th and the >28th then the worm will begin attacking whitehouse.gov without >trying to >infect other systems. This attack will continue indefinitly. > >The following are rough numbers, but we felt that it was important to >illustrate the affects this worm can _possibly_ have. > >The worm has a timeline like this: > >day of the month: >1-19: infect other hosts using the worm >20-27: attack whitehouse.gov forever >28-end of month: eternal sleep > >Presumably, this could restart at any point in a new month again. > >Also, some stats for the attack: > >Each infection has 100 threads >Each thread is going to send about 100k, a byte at a time, >which means you >have a (40 for ip + 1 for each byte) which means you have 4.1 >megs of data >per thread >100 threads * 4.1megs = 410 Megabytes >This will be repeated again every 4.5 hours or so > >Remember, each host can be infected multiple times, meaning >that a single >host can send 410MB * # of infections. > >We have had reports between 15 thousand and 196 thousand unique hosts >infected with the "Code Red" worm. However, there has been >cross infection >and we have heard reports of at least 300+ thousand >infections/instances >(machines with multiple infections etc..) of this worm. > >If there are 300 thousand infections then that means you have >(300,000 * 410 >megabytes) that is going to be attempted to be flooded against >whitehouse.gov every 4 and a half hours. If this is true and >the worm "works >as advertised" then the fact that whitehouse.gov goes offline >is only the >begining of what _can_ possibly happen... > >---- > >I am actually writing this part of the eMail about 45 minutes after the >first part because our Internet connection here in california >has been going >up and down. We have also heard reports of internet >connectivity going down >in parts of northern california and new york. > >Signed, >eEye Digital Security >T.949.349.9062 >F.949.349.9538 >http://eEye.com/Retina - Network Security Scanner >http://eEye.com/Iris - Network Traffic Analyzer >http://eEye.com/SecureIIS - Stop known and unknown IIS vulnerabilities > --------- 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: Full analysis of the .ida "Code Red" worm.
by Tony Wicks 19 Jul '01

19 Jul '01

-----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Friday, July 20, 2001 10:12 AM To: tony.wicks(a)telstrasaturn.co.nz Subject: RE: Full analysis of the .ida "Code Red" worm. Well, Tony, to be quite frank, you annoy me even more. Who the fuck appointed you as the content-cop on NZNOG, and told you to stalk me with rude replies each time I post something? Nobody else complains about my posts, and I bet you haven't got the courage to be rude to anyone else. -- Juha :: -----Original Message----- :: From: Tony Wicks [mailto:tony.wicks(a)telstrasaturn.co.nz] :: Sent: Friday, 20 July 2001 10:07 :: To: Juha Saarinen :: Subject: RE: Full analysis of the .ida "Code Red" worm. :: :: :: Well, it's a bit rich, you posting back to the list telling :: me to cut a few :: lines out of a posting when you send so many useless posts :: there. Quite :: frankly, that annoyed me quite a bit ! :: :: -----Original Message----- :: From: Juha Saarinen [mailto:juha(a)saarinen.org] :: Sent: Friday, July 20, 2001 9:59 AM :: To: tony.wicks(a)telstrasaturn.co.nz; nznog(a)list.waikato.ac.nz :: Subject: RE: Full analysis of the .ida "Code Red" worm. :: :: :: Don't exaggerate Tony. :: :: -- :: :: Juha :: :: :: -----Original Message----- :: :: From: Tony Wicks [mailto:tony.wicks(a)telstrasaturn.co.nz] :: :: Sent: Friday, 20 July 2001 09:57 :: :: To: Juha Saarinen; nznog(a)list.waikato.ac.nz :: :: Subject: RE: Full analysis of the .ida "Code Red" worm. :: :: :: :: :: :: Ok, tell you what, I'll trim my posts if you cut your posts :: :: to just relevant :: :: stuff, not 10-20 mails a day of off topic drivel, hows that :: :: for a deal. :: :: :: --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

SPAM/SCAM alert
by Michael Newbery 19 Jul '01

19 Jul '01

This piece of ordure just showed up in my mailbox. Just a heads-up in case anyone hasn't already seen it and might decide to alert the customers. Now, where did I put that nuclear weapon? At 5:34 PM +0100 19/7/01, <webhosting(a)associate.co.uk> wrote: >Received: from moonof.saturn.co.nz > (rata.saturn.co.nz [172.20.18.220]) > by wlg-gwia-nw-01.saturn.co.nz; Fri, 20 Jul 2001 04:44:56 +1200 >Received: from cmailg6.svr.pol.co.uk (cmailg6.svr.pol.co.uk [195.92.195.176]) > by moonof.saturn.co.nz (Postfix) with ESMTP id A3A629C12 > for <michaeln(a)saturn.co.nz>; Fri, 20 Jul 2001 04:34:49 +1200 (NZST) >Received: from harrya.fsnet.co.uk ([217.134.134.196] helo=andrewal) > by cmailg6.svr.pol.co.uk with smtp (Exim 3.13 #0) > id 15NGl1-0002jE-00 > for michaeln(a)saturn.co.nz; Thu, 19 Jul 2001 17:34:35 +0100 >To: <michaeln(a)saturn.co.nz> >From: <webhosting(a)associate.co.uk> >Subject: notice from your webhost >MIME-Version: 1.0 >Content-Type: text/plain; charset=unknown-8bit >Message-Id: <E15NGl1-0002jE-00.2001-07-19-17-34-35(a)cmailg6.svr.pol.co.uk> >Date: Thu, 19 Jul 2001 17:34:35 +0100 > ><x-charset unknown-8bit> > >This email is being sent to you on behalf of your current webspace provider. >This message is not a spam or junk email, your email address was >supplied to WebHosting.com >You will not receive any more messages from WebHosting.com this is a >one time special offer notice. > >WebHosting.com is offering a selected number of webhost's member's >the following special offer. This offer is not available on our >website at www.webhosting.com or anywhere else, this is a special >offer and is valid only for a limitied time. Read on to learn more >about this amazing offer. > >For only $6.25 (one time fee) you can get: > >> 500mb webspace >> unlimited pop3 email addresses >> cgi-bin >> full ftp access >> php, ssi, my-sql, asp support >> mySQL database >> FREE DOMAIN REGISTRATION (.com .net .org) >> unlimited bandwidth >> miva merchant account >> secure server for transactions >> accept credit cards >> 24hour technical support > >You did read it right, all this will only cost you only $6.25. There >are no monthly fees or any other costs. You are probably wondering >how WebHosting.com can offer all this for the very low price of only >$6.25, the answer is that WebHosting.com will make a lot of revenue >from extra webspace charges - people wishing to have more than 500mb >can pay $10 per 10mb per month. > >If you would like to receive this excellent offer all you have to do >is send your details to the following email address and your >username and password will be emailed to you within 5 business days. >Then you will be able to login at the members area of WebHosting.com >and configure your account (add domains, setup scripts etc.). > >Please send all of the following details: > >Your Full Name >Your Full Address >Your Phone Number >Your Email Address >Your Credit Card Number >Your Credit Card Expiry Date >Your Credit Card Type (eg. visa, mastercard etc.) > >Send all of the above to webhosting(a)associate.co.uk > > > > >Thank you and I hope you enjoy this very special offer > >John Simmons >Head of Special Promotions, Webhosting.com > >------------------------------------------------------------------------------------- >WebHosting.com is a member of the CNS International Internet >Businesses Association > > ></x-charset> -- Michael Newbery Technical Specialist TelstraSaturn Limited Tel: +64-4-939 5102 Mobile: +64-29-939 5102 Fax: +64-4-922 8401 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Problems accessing sites in china
by Lin Nah 18 Jul '01

18 Jul '01

HI all I wonder if anyone here has had complains from their customers/helpdesk regarding inability to access certain chinese websites. For example the last 5 hops of a trace to www.china.com shows it disappearing after 201.176.155.238 15 hkt.ser4-0.core1.sun.cais.net (63.216.17.73) 245.372 ms 240.922 ms 237.96 0 ms 16 202.84.249.29 (202.84.249.29) 236.565 ms 235.41 ms 234.18 ms 17 207.176.97.134 (207.176.97.134) 245.263 ms 235.18 ms 238.485 ms 18 f5-1.tmh12.hkt.net (205.252.128.238) 245.80 ms 239.694 ms 243.223 ms 19 210.176.155.238 (210.176.155.238) 244.516 ms 246.827 ms 235.416 ms 20 * * * There's also been problems with some other sites ( can't remember names but perhaps one of them is cn.yahoo.com) Any ideas? regards Lin --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

RE: IPv6...Fact or Fiction?
by Gavin Cato 18 Jul '01

18 Jul '01

>> NAT is a broken idea, as are firewalls. Just because it works, >> doesn't change this. I wouldn't call it broken. A band-aid solution perhaps but not broken. It does what it intended to do quite well. Gav --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 14

This list, or an alternative? was RE: Julian Angelo - Conclusion
by Frank March 18 Jul '01

18 Jul '01

I am not a network operative, yet I lurk here (with intent, since I v occasionally post). I have always considered that off-topic posts (like, I suppose, this one) come into the permissible area, as allowed for in the mention of beer in the AUP. I have always had an excellent range of helpful responses from NZNOG subscribers when I have posed policy related questions to this list even though they are unrelated to beer. I find being on this list extremely useful. At the same time, a point made in another post in the parent thread by Matt Camp about a non-operational companion list could be considered although I dont think the noise level is that serious. Frank March Specialist Advisor, IT Policy Group Ministry of Economic Development, PO Box 1473, Wellington, NZ Ph: (+64 4) 474 2908; Fax: (+64 4) 471 2658 > -----Original Message----- > From: Dean Pemberton [SMTP:dean(a)flatnet.gen.nz] > Sent: Thursday, 19 July 2001 11:43 > To: Matt Camp > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: Julian Angelo - Conclusion > > On Thu, Jul 19, 2001 at 11:22:41AM +1200, Matt Camp wrote: > > > > > thirteen in the second. Removing from the count people I believe not > to > > > be staff of network operators, and the subscriber who expressed both > > > > Hrm... good point here. I know I don't have an official sig on this > email > > address, so might have been placed in the 'not a network op' basket > > here... yet I am. > > And I'm not - if anyone thinks that this makes me unsuitable for inclusion > by the 'network operator elite' then let me know and I'll unsubscribe. > > > Dean > --------- > 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

Could this be why your 827s are retraining?
by Juha Saarinen 18 Jul '01

18 Jul '01

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt /800/800yb/rn800yb.htm Resolved Caveats for Release 12.1(5)YB1 This section describes possibly unexpected behavior by software releases prior to Release 12.1(5)YB1 that have been resolved in Release 12.1(5)YB1 and above. CSCdt19816 A router retrains when an LOM is detected-a critical condition message is sent out, resulting in an unnecessary reboot. A LOM alone is not sufficient to require a critical condition message or router reset. This problem is fixed in Cisco IOS Software Release 12.1(5)YB1 My version is: ROM: System Bootstrap, Version 12.1(1r)XB1, RELEASE SOFTWARE (fc1) ROM: C820 Software (C820-Y6-M), Version 12.1(5)YC, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1 -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

unsubscribe nznog
by Melanie McAllister 18 Jul '01

18 Jul '01

-----Original Message----- From: James Tyson [mailto:james(a)samizdat.co.nz] Sent: Thursday, 19 July 2001 10:13 a.m. To: Juha Saarinen Cc: 'Simon Allard'; 'James Tyson'; nznog(a)list.waikato.ac.nz Subject: RE: IPv6...Fact or Fiction? > Yes, yes, but what does that mean? Details, man, details. ;-) > > I have found that with either the Nokia MW1122 and the Cisco 827 plugged > in, my Jetstream connection suffers from "micro outages", usually once a > day. It'd be interesting to discover if these outages are caused by the > adapter or by a fault/flaw in Jetstream. > > Here's what the 827 logs: > > Jul 12 03:00:16 router 23: Jul 12 03:00:16.373 NZ: %LINK-3-UPDOWN: > Interface ATM0, changed state to down > Jul 12 03:00:16 router 24: Jul 12 03:00:16.381 NZ: %LINK-3-UPDOWN: > Interface Virtual-Access1, changed state to down <snip /> Juha, Try "debug atm errors" and email me the output - I'll bet your getting the same thing as me. 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 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

DNS & email hosting
by Chris Wedgwood 18 Jul '01

18 Jul '01

I'm looking for a list of people who offer basic DNS and Email hosting. Nothing fancy, basically a service that a few people can use so that <everything>@some.domain.com will end up in their Xtra mailbox. It occurred to me there must be about fifty difference places who can do this, but I've never seen a list of services compiled list who can provide what. Right now, there is no talk of needing mailboxes, web-sites or indeed anything of the sort, but knowing that this is trivially possible is probably worth-while. Does such a list exist? --cw --------- 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: Optical Gig NICs
by Richard Naylor 17 Jul '01

17 Jul '01

At 10:35 PM 7/17/2001 +1200, Roger De Salis wrote: >Ah, the joys of my favourite and personal network provider..... > >There is one vital fact that has been missed though.... any financial >advantage accrued through the economics espoused above, is completely >negated by the scale of the PC wreckage around Simon's desk. I've >seen it... in fact it run's over two desks....., around the floor >past the aerials, over the carpet.... who needs $25 NIC cards >when you can sidle up to Si's desk and suggest humbly that >"this has been here 6 months.....would you mind if I tested it..." > >Dean can vouch for me, so this email can be seen to vendor >independenet........ Its a part of our policy of encouraging an environment of open experimentation in the area of interoperability, especially between vendors. But to set the record (and the archive) straight we did tidy up - once, when we shifted buildings. 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

3 3

Re: Optical Gig NICs
by Richard Naylor 17 Jul '01

17 Jul '01

At 10:35 PM 7/17/2001 +1200, Roger De Salis wrote: >Ah, the joys of my favourite and personal network provider..... > >There is one vital fact that has been missed though.... any financial >advantage accrued through the economics espoused above, is completely >negated by the scale of the PC wreckage around Simon's desk. I've >seen it... in fact it run's over two desks....., around the floor >past the aerials, over the carpet.... who needs $25 NIC cards >when you can sidle up to Si's desk and suggest humbly that >"this has been here 6 months.....would you mind if I tested it..." > >Dean can vouch for me, so this email can be seen to vendor >independenet........ Its a part of our policy of encouraging an environment of open experimentation in the area of interoperability, especially between vendors. But to set the record (and the archive) straight we did tidy up - once, when we shifted buildings. 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

Optical Gig NICs
by J S Russell 17 Jul '01

17 Jul '01

Possibly slightly off topic, but does anyone (Hi Richard! Hi Si!) know of a New Zealand source for gigabit nics (optical, not copper) which are (a) not priced at defence department levels, and (b) supported by linux? JSR -- John S Russell | "What the hell is he building in there... Operations Manager | he has a router...and a table saw..." Attica/Callplus NZ | - Tom Waits, Mule Variations --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 15

IPv6...Fact or Fiction?
by Craig Whitmore 17 Jul '01

17 Jul '01

Hi people.... When do people think we (the Internet) will run out of IPv4 addresses and people will be forced to move over and use IPv6? Or will people use the IPv4 addresses in a much more conservative way? Do you think it will really take off in the near future? Has there really been a standardized IPV6 Format yet? Has anyone actually used it in a production enviornment? Should I "Apply" for some IPv6 addreeses now or will there be plenty of time to implement it? Thanks Craig Whitmore Orcon Internet http://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

5 6

Julian Angelo
by Donald Neal 17 Jul '01

17 Jul '01

NZNOG People, Just over a year ago, there was discussion on this list of spamming by one Julian Angelo. He has now approached me, asking to have these references removed from the NZNOG archive. It seems that prospective employers who look up his name on the web find these archive entries, a fact which may not be helping his career any. If any network operator has an objection to these entries being removed from the archive, could they please contact me directly. Donald Neal NZNOG Mailing List Administrator --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

21 40

Re: Optical Gig NICs
by Chris Wedgwood 16 Jul '01

16 Jul '01

On Tue, Jul 17, 2001 at 11:11:21PM +1200, Chris Hellberg wrote: is that using that RAW NIC to NIC option in the linux kernel? If you mean Alexey's fastroute stuff, then no. Fast route only makes sense for a router and only works on a very limited number of cards. --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

Re: Optical Gig NICs
by Chris Hellberg 16 Jul '01

16 Jul '01

>>> "Chris Wedgwood" <cw(a)f00f.org> 07/17/01 10:41p.m. >>> On Tue, Jul 17, 2001 at 09:40:01PM +1200, Richard Naylor wrote: Dick Smith. Maybe decent was the qualifer......I think we pay $35 for D-Link. The only D-Link cards I've ever used are 530TX or something. They are not even close to what I call decent. What chipset do the ones you have use? Last time I shifted a file from the edit pc to the server (both on GbE) it took 6 minutes for 1.6 Gig. I wonder if I can get a GbE PC card for the laptop ? Ah.. this is why I say decent card. I expect a 100mbps card to run at 100mbps or very near to it. 1.6G in 6 minutes, that's 4.5 megabytes/s or so? Earlier this year I did some testing or various NICs and could sustain over 12 megabytes/s for several hours, even when this data came off a disk one one machine and onto a disk on another machine. is that using that RAW NIC to NIC option in the linux kernel? <<snipped>> --------- 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: Julian Angelo
by Lindsay Druett 16 Jul '01

16 Jul '01

Read a bit of that... you're not kidding. About 5 pages of it.... Hey ! He forgot to mention to his prayer chain about NZNOG ! :: Would it not suffice for Mr Angelo to publish an apology :: here on NZNOG, thus when prospective employers discover his :: chequered past, they will also discover his contrition. http://www.datasync.com/~mbowie/archive29.html -- read a bit of that... seems the NZNOG archives are the least of Mr Angelo's worries. -- Juha --------- 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: Julian Angelo
by david＠farrar.com 16 Jul '01

16 Jul '01

There seem to be a few lessons one can learn from this. 1) Don't spam 2) Don't spam ISPs 3) In case of 1 or 2 apologise 4) Asking for archives to be removed is a bad idea 5) Asking a group of system admins to remove archives is a *really* bad idea 6) This is because anything that can be found about you will and has been 7) Also because the discussion on your request leads to 30 times as many hits as the original thread 8) Juha does have too much time on his hands 9) Refer to 1 10) There is no 10. DPF Gordon Smith wrote: > Good grief!! > > You know Juha, you really have too much free time... :-) > > > > -----Original Message----- > > From: owner-nznog(a)list.waikato.ac.nz > > [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Juha Saarinen > > Sent: Tuesday, 17 July 2001 12:33 > > To: 'Hamish MacEwan'; nznog(a)list.waikato.ac.nz > > Subject: RE: Julian Angelo > > > > > > :: Would it not suffice for Mr Angelo to publish an apology > > :: here on NZNOG, thus when prospective employers discover his > > :: chequered past, they will also discover his contrition. > > > > http://www.datasync.com/~mbowie/archive29.html > > > > -- read a bit of that... seems the NZNOG archives are the least of Mr > > Angelo's worries. --------- 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: Julian Angelo
by Greg Clare 16 Jul '01

16 Jul '01

Just an observation... In requesting the archive purge, a whole new thread of discussion relating to this topic is currently being created... Therefore, the next request will be for the current discussion to be purged... ad infinitum! This leads to the obvious paradox that the only way to undo history is to travel back in time and not do what should not have been did in the first place! ;) Another observation... An apology post would also be recorded in the archives. Greg > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Tuesday, 17 July 2001 12:04 pm > To: 'Michael Newbery'; nznog(a)list.waikato.ac.nz > Subject: RE: Julian Angelo > > > :: An interesting point. The image of 'Memory Holes' sprang > :: instantly to mind. > :: > :: While the article below is rather extreme > :: (http://www.thefire.org/offsite/data/mcelroy042000.html) it > :: does make > :: the point that an archive is supposed to be, well, an archive. > > Good point. I think that "sanitising" archives might set an > unfortunate > precedent, but ultimately, it's up to the listadmin to decide. > > However, even if the messages referring to Mr Angelo were > expunged from > the archives, haven't they been stored elsewhere? I seem to remember > that Google spiders NZNOG... hang on... yep, so it does. > > In fact, a Google search on "Julian Angelo" reveals plenty more than > just NZNOG... see for yourself. I think he's just going to > have to live > with his fifteen seconds of Internet infamy. > > > -- > Juha > > --------- > 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 1

re: Julian Angelo
by Matthew G Brown 16 Jul '01

16 Jul '01

I have also read about this person . If he could come up with a good reason and apology he could have his sentence shortened by the ISP Justice system. Spam is Spam and from what I know he did quite the nice job of it all . Sincere apologies time. Matthew G Brown Wireless Network Specialist Tasman Solutions LTD Http://www.ts.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

Who are these at APE?
by Craig Whitmore 16 Jul '01

16 Jul '01

Anyone be able to tell me who these are at ape?? ????.ape.net.nz (192.203.154.7) dts1.ape.net.nz (192.203.154.68) dts2.ape.net.nz (192.203.154.69) ssc.ape.net.nz (192.203.154.76) They are not on the www.ape.net.nz website for contact to peer with? (if they want to is a different question) Thanks Craig Whitmore Orcon Internet http://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

4 3

Re: IP express
by David Anso 15 Jul '01

15 Jul '01

I take the last bit back. International access seems quite good again. Regards David Anso Systems Administrator - ZIP Internet Email: sysadmin(a)zip.co.nz ----- Original Message ----- From: "David Anso" <sysadmin(a)zip.co.nz> To: "Chris Wedgwood" <cw(a)f00f.org> Cc: "NZNOG Mailing List" <nznog(a)list.waikato.ac.nz> Sent: Monday, July 09, 2001 3:22 PM Subject: Re: IP express > Clint said that there was a fibre cut between Auckland and Hamilton. > Apparently it's Telecom fibre, not Clear fibre. > > It's seems CLIX and Netgate peer at Waikato, so now I'm getting 600ms ping > times to Netgate connections from CLIX :-( > > That on top of total loss of bandwidth at 13:00, which has now improved to > dog slow international access. :-( > > > Regards > > David Anso > Systems Administrator - ZIP Internet > > Email: sysadmin(a)zip.co.nz > > ----- Original Message ----- > From: "Chris Wedgwood" <cw(a)f00f.org> > To: "J S Russell" <jsr(a)jsr.com> > Cc: "David Robb" <david.robb(a)staff.ihug.co.nz>; "NZNOG Mailing List" > <nznog(a)list.waikato.ac.nz> > Sent: Monday, July 09, 2001 2:19 PM > Subject: Re: IP express > > > > On Mon, Jul 09, 2001 at 01:39:56PM +1200, J S Russell wrote: > > > > The Clear Communications operations dude just told us that "some > fibres > > have been cut, somewhere." and that "he didn't have much info at this > > time." > > > > *who* said that? > > > > > > > > --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

3 2

I'm off!
by Phill Groom 11 Jul '01

11 Jul '01

Lunch seems to have gone on a bit longer than normal today and since I am now at home and not at my desk I don't have access to all of the email addresses of the people I would like to personally say goodbye to. A general broadcast to nznog seems like the best way out of this predicament. Apologies to those that don't know me or do know me but don't care! I have left TelstraSaturn and will be returning to Telstra Corp. in Hobart next week. To all of the customers, potential customers, peers and competitors (not necessarily in that order) that I have had the pleasure of working with over the last two years I say thank you. I have learnt truck loads of stuff from all of you and will treasure the friendships I have made. This industry in New Zealand is unique. There are so many cluefull people who are prepared to put competition aside for the good of the general Internet community. I could make lots of Kiwi jokes, but I won't because I may want a job back here one day. Goodbye and good luck. Regards, Phill. --------- 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: IP express
by Seeby - Orcon Internet 09 Jul '01

09 Jul '01

Yes we are having problems with our IPExpress cct. we thought that it was just us. we have lodged a fault with Clear they haven't given us an ETA Cheers Seeby Orcon Internet - www.orcon.net.nz ----- Original Message ----- From: "Simon Lyall" <simon.lyall(a)ihug.co.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Monday, July 09, 2001 10:51 AM Subject: ip express? > Looks like it's down going off who has died on APE. Can anyone confirm? > > -- > Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz > Senior Network/System Admin | Postmaster | 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 > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 11

Australian Bill - "10 years for hacker toolkits, scanners and virus code."
by Hamish MacEwan 08 Jul '01

08 Jul '01

I've read some of the discussion at, http://slashdot.org/article.pl?sid=01/07/07/0132226 and wonder if anyone has any reassurance to offer about the NZ bill? I'm presuming the practitioners on this list will be in some kind of grey area in this legislation, unless the State wishes to introduce a form of licensing, a la Car Salesmen, Security Guards, Doctor, and Network Operator who is granted specific exemptions regarding the general provisions of the law. The other, supra-legislative, issue that might have an operational impact on the operation of the Internet in NZ is this Hague Treaty expansion, at the behest of the usual beneficiaries, to encompass content law. Is there any concern that NZ ISPs will become liable, if the law is so elsewhere in the world? Hamish. -- The only real voyage of discovery consists not in seeking new landscapes but in having new eyes. -- Marcel Proust --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 11

Re: IP express
by Donald Neal 08 Jul '01

08 Jul '01

-- Donald Neal Mobility & Calling Platforms Network Delivery Telecom New Zealand Ltd >>> "Rob Isaac" <rob(a)automagic.org> 07/09/01 12:38 >>> >*Steps up to the plate* >Seeby sends email >having problems with IP >a fault is lodged I express suprise Spare time is so extensive for operations staff - Donald Neal --------- 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: Australian Bill - "10 years for hacker toolkits, scanners and virus code."
by Frank March 08 Jul '01

08 Jul '01

The well considered (and widely consulted) InternetNZ/ISOCNZ submission on SOP 85 (the 'antihacking' provisions) put together by Ewen McNeil and others is available at http://www.isocnz.org.nz/issues/iswg010209submsm_crimes-amend-bill-6.html The SOP itself and other links are to be found under 'Legislation' at: http://www.isocnz.org.nz/issues/index.html But to save everyone from the need to search, I can summarise by noting that the issues raised by the Australian Bill are not part of any NZ legislation currently before Parliament, or contemplated. On the other hand, I do believe that Hamish is correct to draw attention to the position of ISPs should NZ be placed in a position of being required to harmonise our laws with international movements. There will be an ISP Forum organised by InternetNZ later this year and these matters should be discussed there. Frank March Specialist Advisor, IT Policy Group Ministry of Economic Development, PO Box 1473, Wellington, NZ Ph: (+64 4) 474 2908; Fax: (+64 4) 471 2658 > -----Original Message----- > From: Hamish MacEwan [SMTP:nznog(a)Hamish.MacEwan.gen.nz] > Sent: Sunday, 8 July 2001 16:21 > To: nznog(a)list.waikato.ac.nz > Subject: Australian Bill - "10 years for hacker toolkits, scanners > and virus code." > > > I've read some of the discussion at, > http://slashdot.org/article.pl?sid=01/07/07/0132226 > > and wonder if anyone has any reassurance to offer about the > NZ bill? > > I'm presuming the practitioners on this list will be in some > kind of grey area in this legislation, unless the State > wishes to introduce a form of licensing, a la Car Salesmen, > Security Guards, Doctor, and Network Operator who is granted > specific exemptions regarding the general provisions of the > law. > > The other, supra-legislative, issue that might have an > operational impact on the operation of the Internet in NZ is > this Hague Treaty expansion, at the behest of the usual > beneficiaries, to encompass content law. > > Is there any concern that NZ ISPs will become liable, if the > law is so elsewhere in the world? > > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Cache peering via WIX/APE
by David Robb 08 Jul '01

08 Jul '01

If anyone else[1] is interested in cache peering across either WIX or APE, let me know. [1] ie, anyone I'm not already peering caches with David Robb --- Senior Network Engineer DDI +64-9-359-2710 ihug (AS7657) NOC +64-9-359-2708 "The Earth is a single point of failure" --------- 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: ip express?
by Seeby - Orcon Internet 08 Jul '01

08 Jul '01

Did they lose it? ;-) or did you mean "fixing" the Clear IP express switch Cheers Seeby Orcon Internet - www.orcon.net.nz > According to someone else, The Clear tech is having problems finding the > IPexpress switch. > > -- > Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz > Senior Network/System Admin | Postmaster | 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

ip express?
by Simon Lyall 08 Jul '01

08 Jul '01

Looks like it's down going off who has died on APE. Can anyone confirm? -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | Postmaster | 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

2 1

RE: ip express?
by Lindsay Druett 08 Jul '01

08 Jul '01

Did someone say there was a dead cat in the router ? -----Original Message----- From: Simon Lyall [mailto:simon.lyall(a)ihug.co.nz] Sent: Monday, 9 July 2001 10:51 To: nznog(a)list.waikato.ac.nz Subject: ip express? Looks like it's down going off who has died on APE. Can anyone confirm? -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | Postmaster | 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

The New Zealand Network Operators' Group
by Donald Neal 08 Jul '01

08 Jul '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 a little under 250 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. The following non-working email addresses were recently removed from the list. Their owners are welcome to re-subscribe with working addresses. aleki097(a)student.otago.ac.nz brett.telfer(a)telecom.co.nz steve.hawken(a)ngtmail1.netgate.net.nz 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. 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

ORBS probes continue...
by cw＠f00f.org 05 Jul '01

05 Jul '01

I'm still seeing ORBS probe-messages... when I spoke to Alan last he told me ORBS would probably die as a result of the QSI takeover the the MIS user base. Now, these probe-messages are from one of the offshore probes, so I am left to wonder, migjt ORBS life on, are these remote probes still running waitning to be turned down? --cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 9

FW: Shared Registry System Implementation
by Peter Mott 01 Jul '01

01 Jul '01

Please bring this to the attention of folk in your organisation who may have an interest: > -----Original Message----- > From: Donna Hiser [mailto:d.hiser(a)domainz.net.nz] > Sent: Wednesday, 27 June 2001 11:22 a.m. > To: dns(a)2day.com > Subject: Shared Registry System Implementation > > SHARED REGISTRY SYSTEM IMPLEMENTATION > > As you may know ISOCNZ has appointed an SRS Implementation Manager, Rose > Percival, to manage the planning, design and rollout of the new shared > registry system. > > Rose has now drafted high level requirements for the SRS and has set up a > mailing list as a vehicle for those who wish to provide input into the > different aspects of the SRS as they are developed. > > The SRS Implementation Committee have now asked me to advise you of the > existence of this list, and to invite you on their behalf, to subscribe to > it. To do so, please go to > http://www.isocnz.org.nz/mailman/listinfo/srs-implementation. They also > invite you to consider the requirements definition document (at > http://www.isocnz.org.nz/srs ) and to provide any feedback either directly > to Rose or via the SRS Implementation list. > > If you have any concerns or queries about this, please contact the SRS > Implementation Manager (Rose Percival) directly at > rose.percival(a)isocnz.org.nz. 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

1 1

Re: Any Xtra mail admins on NZNOG?
by Ted Grenfell 25 Jun '01

25 Jun '01

That IP is in use by smtp.jabmail.net and is not an Xtra MTA. Jabmail.com NZ Ltd are apparently having some problems with their DNS server(s) at the moment. At 10:19 26/06/2001, Juha Saarinen wrote: >If so, could you please contact me? We have a problem with one MTA >(210.54.238.40) bouncing *all* mail going to it with a "550 - Relaying >prohibited". > >Other MTAs at Xtra receive mail fine. > >-- >Regards, > > >Juha > >PGP fingerprint: >B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 > > > > >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog -- 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

2 1

Any Xtra mail admins on NZNOG?
by Juha Saarinen 25 Jun '01

25 Jun '01

If so, could you please contact me? We have a problem with one MTA (210.54.238.40) bouncing *all* mail going to it with a "550 - Relaying prohibited". Other MTAs at Xtra receive mail fine. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 --------- 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 bgp stats, first puny attempt
by Joe Abley 24 Jun '01

24 Jun '01

Hello, I have a few bgp sessions up with a corresponding number of friendly people around the place, and have what I think is a reasonable view of the NZ network. I haven't amassed enough data to do anything particularly interesting yet, but I thought I'd hack one thing together quickly since I've heard a few people asking for it: see http://maggie.automagic.org/ for lists of "NZ networks" and "NZ ASNs" (there are some more precise descriptions on that page). People interested in delineating national and international traffic every month, for example, might find http://maggie.automagic.org/nzbgp/aggregates.month (or one of the specific-month snapshots) useful. Possibly even more useful when it has more than a few hours' worth of data in it. If anybody feels like donating additional views of the BGP table, so that I can try to keep this (and future) data as representative as possible, all I need is a multi-hop ebgp session terminating on 202.89.128.76 in AS65517; drop me a line if you feel like setting something up. Many thanks to those who have set one up for me already. Oh, and if you see something in the data that is clearly wrong, please let me know that too :) Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 5

Open Letter to all NZ ISPs and users of NZNOG
by T McC 18 Jun '01

18 Jun '01

Please find attached an Open Letter to all ISPs in New Zealand and all users of NZNOG. This is in no way to be treated as SPAM. It is in response to the many misconceptions and uninformed comments made by ISPs in New Zealand and users of NZNOG as a result of the email I sent to ISPs in New Zealand asking them to adjust their server settings to accept access to the .z extension. Please read it and if any one has any comments or requires any further information please contact me. Yours Trevarr McCarthy President The Wapterix Internet Group -- _______________________________________________ FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Make PC-to-Phone calls with Net2Phone. Sign-up today at: http://www.net2phone.com/cgi-bin/link.cgi?121 -- _______________________________________________ FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Make PC-to-Phone calls with Net2Phone. Sign-up today at: http://www.net2phone.com/cgi-bin/link.cgi?121

20 37

Proxy ARP on APE
by Simon Blake 17 Jun '01

17 Jun '01

Evening all simon(a)magellan:~$ nmap -sP 192.203.154.0/24 -n ... Nmap run completed -- 256 IP addresses (145 hosts up) scanned in 23 seconds simon(a)magellan:~$ sudo arp -van | grep 00:E0:34:B9:C4:45 | wc 128 896 7295 Whoever has 00:E0:34:B9:C4:45 (I'm guessing either Zivo or QSI, since it's on the Clear IP Express interconnect), please make it stop, or I *will* drop it in a MAC filter to make the problem go away. Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

(no subject)
by Adam Moore 17 Jun '01

17 Jun '01

subscribe 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

the ALT.ROOTS an introduction
by !Dr. Joe Baptista 17 Jun '01

17 Jun '01

Hi: I've recently noticed some discussion here on alt.roots. A topic of some interest to me. Don Stokes wishes they would go away, however i know they are here to stay. The ALT.ROOTS started as an experiment. The question was could the root be removed from DOC USG control (Department of Commerce, United States Government) and is it possible to expend namespace - and if so - what are the technical limitations. The experiment is now over. The ALT.ROOTS or expanded namespace works very well and the technical limitations to the growth of the root file are no different then the technical limitations seen at the .com zone file level. Now the ALT.ROOTS are experiencing a social experiment which seems to be working. They are co-ordinating the allocation of namespace in a reasonably open fashion. Some commercial ventures in fact now offer expanded root services. Certainly there have been some problems - but the expanded namespace is evolving at a rapid pace and i anticipate in excess of one million top level domains by next year. Much of this is due to various european ISP's who are activily co-ordinating local government resources to establish claims to namespace for specific and general purpose top level domains. I would actively encourage any ISP in NZ to participate. However - I advise some precautions when selecting a root provider or in listing your tlds on various root services. I speak from experience. I recently took control and shutdown about 80% of all root service traffic to the Open Root Server Confederation (ORSC). This affected organizations like znet.com - a large ISP in California, various University of California computer labs and sites, including the university president's office. Other affected parties included some ISP called Grasshoppernet, most of croatia (yes - i mean the country), and the Ministry of Education for the Grand Dutchy of Luxemburge. There were many others but these were the most interesting I found in my logs. My decision to shut down the roots was due mainly to bad planning on the part of the root operator. We enterted into an agreement with a Diebold Incorporated to provide arpa (network) infrastructure. During the period that Diebold used the arpas they made arrangements with the ORSC root operator to establish two roots on our networks. When our agreement expired we relocated our networks and examined them for traffic. We found alot of dns traffic for the old ORSC roots. As some of you may know - once a root is established it becomes a permanent fixture on the internet. Roots are pointed to using their internet protocol addresses. This put us in a sticky position. We were now in control of every answer to every question by every user attached to our infrastructure. As some of you may know a root service is a trusted service and the abuse of this trust can result in violation of a networks integrity. Our immediate concern was the what if question. What if a hacker who knew our sites once carried a root server - and understood the power of root - decided to break in and take over the root. They could essentially redirect traffic while capturing user password, names, addresses, credit card information - etc. etc. etc. This is a scary position to be left in and i'm sure you can all appreciate that. So as to avoid any potential liability we collapsed the root and redirected users attempting to access port 80 on any host to one web page which provided them with assistance on reconfiguring their computers or networks. So in picking a root I think it is very important to find one in which the infrastructure is captured by the root operator. This means that the IP numbers used to identify the root are stable and under the administrative control of the root operator - or secured by legal agreement. Many ALT.ROOT lack this. The ORSC has no legal obligation in place to provide service, they are not for profit, the ALTERNIC was established by a known felon and operate some of their infrastructure on @Home IP addresses, the OPENNIC is the same with network hardware addresses being outside their immediate control. So with roots operating on @Home infrastructure the possibility that an old but still active root can fall into the wrong hands is an uncomfortable probability. There is only one commercial root service - the largest of which is pacificroot and they have captured infrastructure. CINICS in france is building infrastructure for french governments and associations at various levels. So the push is on and the momentum unleashed. The only question is who do you trust when you don't have a report card on the players. And I include the USG root system in that question of trust. They have the same power to redirect users as I had when I made the decision to close down portions of the ORSC root infrastructure. And I find that power to be scarier in the hands of one government entity then i do in the hands of a nauty hacker. Those of you who want to explore alt roots can find more data at the Independent Root Operator's Network http://root-dns.org/ regards joe baptista The dot.GOD Registry, Limited The Executive Plaza, Suite 908 150 West 51st Street Tel: 1 (208) 330-4173 Manhattan Island NYC 10019 USA Fax: 1 (208) 293-9773 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 9

Re: Orcon's Ranges
by Simon Blake 17 Jun '01

17 Jun '01

Mmm, most likely. I need to go on a subscription drive - you'll get routes only from the these peers at the mo: Plain (192.203.154.12) 4 9559 0/0 0/0 0/0 0.01 Active Actrix (192.203.154.16) 4 9872 0/23 1/0 1/0 0.91 Established QSI (192.203.154.28) 4 9727 9/21 0/0 1/0 0.91 Established Telstra (192.203.154.32) 4 4763 0/0 0/0 0/0 0.01 Active IHUG (192.203.154.36) 4 7657 43/29 0/0 1/0 0.91 Established AOL (192.203.154.44) 4 4770 19/13 0/0 1/0 0.91 Established Zivo (192.203.154.45) 4 9495 4/19 0/0 1/0 0.91 Established Attica (192.203.154.46) 4 9790 3/20 0/0 1/0 0.91 Established WalkWire (192.203.154.49) 4 17412 1/29 0/0 1/0 0.91 Established Quest (192.203.154.64) 4 64512 0/23 0/0 1/0 0.91 Established Orcon (192.203.154.66) 4 17746 3/58 0/0 3/2 0.49 Established Some ISP's don't peer with the route servers, for a variety of reasons. I'm expecting that to change as the number of peers increase, as I put in place some more automated procedures for updating the route servers, and as I place some more pressure on the ISP's. Which is a long winded way of saying, nobody is obligated to peer with the route servers, you still may need to negotiate some bilateral arrangements. Anybody else who wants to peer with the route servers on APE, please sing out. Cheers Si On Mon, 18 Jun 2001, Craig Whitmore wrote: > I'm seeing...Is that all? > > Thanks > Craig > > * 138.235.0.0 192.203.154.44 0 9560 4770 i > * 192.173.16.0/21 192.203.154.44 0 9560 4770 i > * 202.6.84.0 192.203.154.44 0 9560 4770 i > * 202.12.70.0 192.203.154.44 0 9560 4770 i > * 202.14.100.0 192.203.154.44 0 9560 4770 i > *> 202.27.100.0/22 192.203.154.45 0 9560 9495 i > *> 202.36.45.0 192.203.154.45 0 9560 9495 i > * 202.37.85.0 192.203.154.44 0 9560 4770 i > * 202.37.140.0/22 192.203.154.44 0 9560 4770 i > * 202.37.144.0/21 192.203.154.44 0 9560 4770 i > * 202.37.197.0 192.203.154.44 0 9560 4770 i > * 202.37.200.0/22 192.203.154.44 0 9560 4770 i > * 202.37.224.0/21 192.203.154.44 0 9560 4770 i > * 202.49.144.0 192.203.154.44 0 9560 4770 i > * 202.50.16.0/20 192.203.154.44 0 9560 4770 i > *> 202.78.128.0/21 192.203.154.45 0 9560 9495 i > *> 202.89.128.0/19 192.203.154.28 0 9560 9727 i > * 202.180.64.0/19 192.203.154.46 0 9560 9790 i > * 202.180.64.0/18 192.203.154.46 0 9560 9790 i > * 202.180.96.0/19 192.203.154.46 0 9560 9790 i > *> 203.96.120.0/23 192.203.154.45 0 9560 9495 i > * 203.99.65.0 192.203.154.44 0 9560 4770 9511 > i > * 203.99.66.0 192.203.154.44 0 9560 4770 9511 > i > * 203.99.71.0 192.203.154.44 0 9560 4770 9511 > i > * 210.48.0.0/17 192.203.154.44 0 9560 4770 i > *> 210.54.0.0/22 192.203.154.44 0 9560 4770 17427 > i > * 210.55.254.0 192.203.154.46 0 9560 9727 9790 > i > > ----- Original Message ----- > From: "Simon Blake" <simon(a)citylink.co.nz> > To: "Craig Whitmore" <lennon(a)orcon.net.nz> > Sent: Monday, June 18, 2001 1:51 PM > Subject: Re: Orcon's Ranges > > > > Hokay, .1 is peering, I'm seeing this from you: > > > > magellan MRTd# sh bgp neigh 192.203.154.66 route in > > > > Peer 192.203.154.66 ip unicast 11 routes > > P Pref Time Destination Next Hop If > > B 0 00:09:22 202.27.188.128/25 192.203.154.66 eth0 > > B 0 00:09:22 210.54.13.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.54.142.0/23 192.203.154.66 eth0 > > B 0 00:09:22 210.54.148.0/22 192.203.154.66 eth0 > > B 0 00:09:22 210.55.8.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.12.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.13.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.14.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.15.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.18.0/24 192.203.154.66 eth0 > > B 0 00:09:22 210.55.199.0/24 192.203.154.66 eth0 > > > > So, looks pretty good, you should be getting assorted stuff from the other > > ISP's viz the route server now. I'll have .2 going later in the > > afternoon. > > > > Cheers > > Si > > > > On Mon, 18 Jun 2001, Craig Whitmore wrote: > > > > > Hi Simon. Here are the prefix lists for Orcon. We will also be > advertising > > > Datacom's Ranges to APE (via our AS Number) > > > > > > Do we peer with rs1.ape.net.nz and rs2.ape.net.nz with APE's (9560) > > > Number... > > > > > > Orcon: As 17746 IP : 192.203.154.6 > > > > > > ip prefix-list ORCON-networks description Orcon Internet > <noc(a)orcon.net.nz> > > > ip prefix-list ORCON-networks seq 5 permit 202.27.188.128/25 > > > ip prefix-list ORCON-networks seq 10 permit 210.54.13.0/24 > > > ip prefix-list ORCON-networks seq 15 permit 210.54.142.0/23 > > > ip prefix-list ORCON-networks seq 20 permit 210.54.148.0/23 > > > ip prefix-list ORCON-networks seq 25 permit 210.55.8.0/24 > > > ip prefix-list ORCON-networks seq 30 permit 210.55.12.0/24 > > > ip prefix-list ORCON-networks seq 35 permit 210.55.13.0/24 > > > ip prefix-list ORCON-networks seq 40 permit 210.55.14.0/24 > > > ip prefix-list ORCON-networks seq 45 permit 210.55.15.0/24 > > > ip prefix-list ORCON-networks seq 50 permit 210.55.18.0/24 > > > ip prefix-list ORCON-networks seq 55 permit 210.55.199.0/24 > > > > > > ip prefix-list DATACOM-networks description Datacom Network > > > <noc(a)orcon.net.nz> > > > ip prefix-list DATACOM-networks seq 5 permit 202.14.20.0/22 > > > ip prefix-list DATACOM-networks seq 10 permit 202.27.76.0/23 > > > ip prefix-list DATACOM-networks seq 15 permit 202.27.140.0/22 > > > ip prefix-list DATACOM-networks seq 20 permit 210.27.250.0/24 > > > > > > > > > > > > > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Peering with Orcon Internet
by Craig Whitmore 17 Jun '01

17 Jun '01

Any ISP wanting to Peer with Orcon Internet Directly @ APE please let me know to arrange it. Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz -------------------------------------------------------------------- APE IP: 192.203.154.66 AS:17746 ip prefix-list ORCON-networks description Orcon Internet <noc(a)orcon.net.nz> ip prefix-list ORCON-networks seq 5 permit 210.55.12.0/24 ip prefix-list ORCON-networks seq 10 permit 210.55.13.0/24 ip prefix-list ORCON-networks seq 15 permit 210.55.14.0/24 ip prefix-list ORCON-networks seq 20 permit 210.55.15.0/24 ip prefix-list ORCON-networks seq 25 permit 210.55.18.0/24 ip prefix-list ORCON-networks seq 30 permit 210.54.13.0/24 ip prefix-list ORCON-networks seq 35 permit 210.54.142.0/23 ip prefix-list ORCON-networks seq 40 permit 210.54.148.0/23 ip prefix-list ORCON-networks seq 45 permit 210.55.8.0/24 ip prefix-list ORCON-networks seq 50 permit 210.55.199.0/24 ip prefix-list ORCON-networks seq 55 permit 202.14.20.0/22 ip prefix-list ORCON-networks seq 60 permit 202.27.76.0/23 ip prefix-list ORCON-networks seq 65 permit 202.27.140.0/22 ip prefix-list ORCON-networks seq 70 permit 210.27.250.0/24 ip prefix-list ORCON-networks seq 75 permit 202.27.188.128/25

2 1

Public providers and ASN on WIX
by Simon Blake 17 Jun '01

17 Jun '01

Matthew Grant from Plain was asking who the WIX route servers pee with, I figured the results may be of interest to others peering or considering peering on WIX: neighbor 202.7.0.1 remote-as 9439 neighbor 202.7.0.1 description Citylink neighbor 202.7.0.49 remote-as 2687 neighbor 202.7.0.49 description AT-T ! neighbor 202.7.0.65 remote-as 7714 ! neighbor 202.7.0.65 description Netlink1 neighbor 202.7.0.76 remote-as 9736 neighbor 202.7.0.76 description Domainz neighbor 202.7.0.78 remote-as 9718 neighbor 202.7.0.78 description Chello neighbor 202.7.0.129 remote-as 9343 neighbor 202.7.0.129 description Actrix neighbor 202.7.0.130 remote-as 9872 neighbor 202.7.0.130 description Actrix-LH neighbor 202.7.0.177 remote-as 9495 neighbor 202.7.0.177 description Clearview neighbor 202.7.0.192 remote-as 4768 neighbor 202.7.0.192 description Clear neighbor 202.7.0.241 remote-as 7657 neighbor 202.7.0.241 description IHUG neighbor 202.7.1.1 remote-as 4770 neighbor 202.7.1.1 description ICONZ neighbor 202.7.1.49 remote-as 9436 neighbor 202.7.1.49 description Globe-Net neighbor 202.7.1.65 remote-as 9445 neighbor 202.7.1.65 description Saturn neighbor 202.7.1.110 remote-as 4740 neighbor 202.7.1.110 description Voyager neighbor 202.7.1.129 remote-as 9345 neighbor 202.7.1.129 description Paradise neighbor 202.7.1.176 remote-as 9503 neighbor 202.7.1.176 description Comnet neighbor 202.7.1.193 remote-as 9338 neighbor 202.7.1.193 description NLNZ neighbor 202.7.1.241 remote-as 9325 neighbor 202.7.1.241 description Xtra neighbor 202.7.1.244 remote-as 9559 neighbor 202.7.1.244 description Plain Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

XTRA, blacklisted by 'mail.com' --- WHY?
by Chris Wedgwood 17 Jun '01

17 Jun '01

At present, some of my outband email is sent through XTRA's mail-server(s) as they block outgoing SMTP access when you are inflicted with Jetstream/Jetstart through Xtra. Not that I really mind all that much, it works pretty much flawlessly and Xtra are arguably being good people by blocking nasty evil users from injecting spam into other peoples open-relays (perhaps they block other ports too --- maybe someone from Xtra can comment?). Now, this just occured, which again doesn't really bother me in this instance, but I am curious as to _why_ this was blocked. The DSN I received says this: Reporting-MTA: dns; balthamel.xtra.co.nz Arrival-Date: Sun, 17 Jun 2001 23:13:47 +1200 Received-From-MTA: dns; tapu (210.55.42.93) Final-Recipient: RFC822; <wapterix(a)mail.com> Action: failed Status: 5.1.3 Remote-MTA: dns; mail-com-bk.mr.outblaze.com (205.158.62.36) Diagnostic-Code: smtp; 553 5.3.0 Mail from 203.96.92.15 refused. Blacklisted. yet when I check the common 'blacklisting' mechanisms I find nothing: tapu:~$ rblcheck 203.96.92.15 203.96.92.15 not RBL filtered by blackholes.mail-abuse.org 203.96.92.15 not RBL filtered by dialups.mail-abuse.org 203.96.92.15 not RBL filtered by relays.mail-abuse.org 203.96.92.15 not RBL filtered by inputs.orbs.org 203.96.92.15 not RBL filtered by outputs.orbs.org 203.96.92.15 not RBL filtered by manual.orbs.org 203.96.92.15 not RBL filtered by spamsources.orbs.org 203.96.92.15 not RBL filtered by untestable-netblocks.orbs.org 203.96.92.15 not RBL filtered by spamsource-netblocks.orbs.org so I wonder what else is out there that is used to blacklist evil people? And why is Xtra in this list? --cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 5

Lots of broken mail at Xtra
by Martin D Kealey 14 Jun '01

14 Jun '01

Has anyone else noticed a recent downturn in mail deliverability for domains hosted by Xtra? In particular, in the last month I have had 3 mailing lists royally screwed by having various clients of Xtra decide to disregard the envelope addressee and send the mail back into the list injection point. The common features in all cases have been the primary MX is mta.xtra.co.nz the mail is collected from there using a POP client the mail is then fed to an Exchange Server The first one was the worst because they were on a full-time IP connection, which meant that the mail loop just went berserk; to make it worse they had changed the domain, and therefore there was *no* identifying information in the list to figure out what had gone wrong. The others since have been easier because they've been on various dial-up connections (and therefore slower) and have had useful identifying information in the report headers. Is this a problem with Xtra, or is there a new (broken) version of Exchange that is flavour of the month for installing? -Martin -- CAUTION: The information contained in this message is consequential and subject to legacy provenance. If you are the intended recipient you are hereby notified that reading this message is permitted. If you have not received this message please notarise the sender and destroy the originator. Help Microsoft stamp out software piracy: give Linux to a friend today... --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

16 29

Orcon APE connection - FIXED :-)
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

Hi there everyone Our connection to APE now works properly :-) The problem was a faulty Fibre to Ethernet tranciever at Clear's end of the link. We have been doing tests for several hours, and the link looks stable enough to start putting traffic on. We are interested in peering with as many people as possible up here - because after all - that's what APE is for. I will post our ASN, prefixes etc tomorrow 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

2 1

Re: Orcon APE connection woes
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

Hmm we have forced full-duplex and turned off auto-negotiation on our Catalyst 5000 switch - but we have also tried all the other settings possible. Clear have told us to set it to 10Mbps Full-Duplex - so that's what it is at present. Cheers Seeby Orcon Internet - www.orcon.net.nz ----- Original Message ----- From: "Ian Quinn" <iquinn(a)juniper.net> To: "Seeby Woodhouse - Orcon" <seeby(a)orcon.net.nz> Sent: Wednesday, June 13, 2001 6:42 PM Subject: RE: Orcon APE connection woes > > I had some problems recently that were marginally similar. Although I had > the speed and duplex settings configured, it didn't come right until I > turned off auto negotiation as well (eg no negotiation or something along > those lines). > > No idea if it's your problem - just seems familiar. > > Good luck :-) > > Regards / Ian > > -----Original Message----- > > From: Seeby Woodhouse - Orcon [mailto:seeby(a)orcon.net.nz] > > Sent: Wednesday, 13 June 2001 6:27 p.m. > > To: NZNOG Mailing List > > Subject: Orcon APE connection woes > > > > > > Hi there everyone > > > > Orcon has just had a 10Mbit IPExpress connection to APE > > completed, and I > > have been fighting with it all day. > > > > If we ping anyone on APE, then we get around 2/3's of the > > pings through, and > > 1/3 are dropped. > > This happens in a pattern of 1/3 drop, 2/3 get through. > > > > I talked with Clear and they said that it could be the > > IPExpress connection > > re-negotiating because of what is on our end, so we have been > > playing with > > the settings on our Catalyst 5000 switch - we have forced the > > port to our > > IPExpress connection full duplex / half duplex / 100mb / 10mb > > but they all > > seem to give the same results. > > > > Clear has advised us to set our equipment to 10Mbit full > > duplex - so that's > > what it is at present. > > > > The connection from IPExpress is then VLan'd from our > > Catalyst switch into > > our core Cisco 7505 router. > > > > A ping report of 300 pings to ihug.ape.net.nz looks like this > > > > --------------------------------------------------- > > ORCON7505#ping > > Protocol [ip]: > > Target IP address: ihug.ape.net.nz > > Repeat count [5]: 300 > > Datagram size [100]: > > Timeout in seconds [2]: > > Extended commands [n]: > > Sweep range of sizes [n]: > > Type escape sequence to abort. > > Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout > > is 2 seconds: > > ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! > > !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! > > !!..........!!!!!!!! > > Success rate is 65 percent (197/300), round-trip min/avg/max > > = 1/3/24 ms > > -------------------------------------------------- > > > > Can anyone shed any light on this? > > > > Is this related the the spanning tree problems that have been > > happening up > > at APE recently? > > Or should we be hassling Clear about the service..... > > > > 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 > > > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 6

Zfree Delibratley slowing down access to Orcon's network
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

It seems that Zfree is delibratley slowing down Internet access to some of Orcon's internal network. If we test by dialing up using a Zfree account, most of our network is blazingly fast, however access to our Mail server and FreeHost server is painfully slow. (mail.orcon.net.nz and freehost.orcon.net.nz) Last time we informed them of this problem, the issue mysteriously went away - but now it is back again a week later. I suspect that Zfree is delibratley rate-shaping the amount of traffic that can go to our mail server and our freehost server from their network to prevent people from accessing them. It is quite frustrating when it is our helpdesk that is recieving all the calls (because theirs is 0900), when it is actually their problem - especially when the customers that are calling us are not actually using us for dialup. Any system administrators for Clear got something to say about this? ;-) -- 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

2 1

Re: Orcon APE connection woes
by Seeby Woodhouse - Orcon 12 Jun '01

12 Jun '01

Hi there Tim I don't want to put any traffic over to APE until this link is working properly. As you know, BGP won't detect packet loss, so it is still better to keep sticking all our Traffic via Telecom until this issue is resolved. As soon as the link works reliably - then we will want to peer with everyone that we can. Hopefully we'll be able to get sub 10ms pings to most ISP's in the country at the end of this ;-) Cheers Seeby Orcon Internet - www.orcon.net.nz ----- Original Message ----- From: "Tim Philips" <tim.philips(a)attica.co.nz> To: "Seeby Woodhouse - Orcon" <seeby(a)orcon.net.nz> Sent: Wednesday, June 13, 2001 6:52 PM Subject: Re: Orcon APE connection woes > On Wed, 13 Jun 2001, Seeby Woodhouse - Orcon wrote: > > Seeby, > > We have had this problem before. Well are still having it with our > Tangent 100Mb. I will see what I can find. Would you like to peer with > us also once your link is up and running. > > If you do provide us with a prefix list and I or one of the other guys > will sort it all out. > > > Hi there everyone > > > > Orcon has just had a 10Mbit IPExpress connection to APE completed, and I > > have been fighting with it all day. > > > > If we ping anyone on APE, then we get around 2/3's of the pings through, and > > 1/3 are dropped. > > This happens in a pattern of 1/3 drop, 2/3 get through. > > > > I talked with Clear and they said that it could be the IPExpress connection > > re-negotiating because of what is on our end, so we have been playing with > > the settings on our Catalyst 5000 switch - we have forced the port to our > > IPExpress connection full duplex / half duplex / 100mb / 10mb but they all > > seem to give the same results. > > > > Clear has advised us to set our equipment to 10Mbit full duplex - so that's > > what it is at present. > > > > The connection from IPExpress is then VLan'd from our Catalyst switch into > > our core Cisco 7505 router. > > > > A ping report of 300 pings to ihug.ape.net.nz looks like this > > > > --------------------------------------------------- > > ORCON7505#ping > > Protocol [ip]: > > Target IP address: ihug.ape.net.nz > > Repeat count [5]: 300 > > Datagram size [100]: > > Timeout in seconds [2]: > > Extended commands [n]: > > Sweep range of sizes [n]: > > Type escape sequence to abort. > > Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout is 2 seconds: > > ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! > > !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! > > !!..........!!!!!!!! > > Success rate is 65 percent (197/300), round-trip min/avg/max = 1/3/24 ms > > -------------------------------------------------- > > > > Can anyone shed any light on this? > > > > Is this related the the spanning tree problems that have been happening up > > at APE recently? > > Or should we be hassling Clear about the service..... > > > > 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 > > > > -- > Thanks, > Tim Philips > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Orcon APE connection woes
by Seeby Woodhouse - Orcon 12 Jun '01

12 Jun '01

Hi there everyone Orcon has just had a 10Mbit IPExpress connection to APE completed, and I have been fighting with it all day. If we ping anyone on APE, then we get around 2/3's of the pings through, and 1/3 are dropped. This happens in a pattern of 1/3 drop, 2/3 get through. I talked with Clear and they said that it could be the IPExpress connection re-negotiating because of what is on our end, so we have been playing with the settings on our Catalyst 5000 switch - we have forced the port to our IPExpress connection full duplex / half duplex / 100mb / 10mb but they all seem to give the same results. Clear has advised us to set our equipment to 10Mbit full duplex - so that's what it is at present. The connection from IPExpress is then VLan'd from our Catalyst switch into our core Cisco 7505 router. A ping report of 300 pings to ihug.ape.net.nz looks like this --------------------------------------------------- ORCON7505#ping Protocol [ip]: Target IP address: ihug.ape.net.nz Repeat count [5]: 300 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout is 2 seconds: ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! !!..........!!!!!!!! Success rate is 65 percent (197/300), round-trip min/avg/max = 1/3/24 ms -------------------------------------------------- Can anyone shed any light on this? Is this related the the spanning tree problems that have been happening up at APE recently? Or should we be hassling Clear about the service..... 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

1 0

WHOIS Survey - DNSO
by Andy Linton 12 Jun '01

12 Jun '01

The DNSO is conducting a survey on ICANN's WHOIS policy. http://www.icann.org/dnso/whois-survey-en-10jun01.htm --------- 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: subscribe NZOG
by Lindsay Druett 12 Jun '01

12 Jun '01

How does the subscribe kit work ? > -----Original Message----- > From: Michael White [mailto:MWHITE(a)clear.co.nz] > Sent: Wednesday, 13 June 2001 14:40 > To: Michael White; nznog(a)list.waikato.ac.nz; 'Juha Saarinen' > Subject: RE: subscribe NZOG > > Damn, wrong kit. > > Mike > > ---------- > From: Juha Saarinen > Sent: Wednesday, 13 June 2001 2:33 PM > To: 'Michael White'; nznog(a)list.waikato.ac.nz > Subject: RE: subscribe NZOG > > Heres how to unsubscribe: > > > Errr... I think the person wants to subscribe. > > -- Juha > > --------- 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: subscribe NZOG
by Michael White 12 Jun '01

12 Jun '01

Damn, wrong kit. Mike > ---------- > From: Juha Saarinen > Sent: Wednesday, 13 June 2001 2:33 PM > To: 'Michael White'; nznog(a)list.waikato.ac.nz > Subject: RE: subscribe NZOG > > Heres how to unsubscribe: > > > Errr... I think the person wants to subscribe. > > -- Juha > >

2 1

RE: subscribe NZOG
by Michael White 12 Jun '01

12 Jun '01

> ---------- > From: Te Aroha > Sent: Wednesday, 13 June 2001 2:13 PM > To: nznog(a)list.waikato.ac.nz > Subject: subscribe NZOG > > Hi there > > Can you please subscribe me to this mailing list. > > Cheers > > > Te Aroha > Maxnet Support Team > Customer Services Supervisor > support(a)maxnet.co.nz > Ph: 0508 MAXNET > Ph: (09) 300-7555 Tech Support > Ph: (09) 300-7222 Office > > > > Heres how to unsubscribe: > > First, ask your Internet Provider to mail you an Unsubscribing Kit. > Then follow these directions. > > The kit will most likely be the standard no-fault type. Depending on > requirements, System A and/or System B can be used. When operating > System A, depress lever and a plastic dalkron unsubscriber will be > dispensed through the slot immediately underneath. When you have > fastened the adhesive lip, attach connection marked by the large "X" > outlet hose. Twist the silver- coloured ring one inch below the > connection point until you feel it lock. > > The kit is now ready for use. The Cin-Eliminator is activated by the > small switch on the lip. When securing, twist the ring back to its > initial condition, so that the two orange lines meet. Disconnect. > Place the dalkron unsubscriber in the vacuum receptacle to the rear. > Activate by pressing the blue button. > > The controls for System B are located on the opposite side. The red > release switch places the Cin-Eliminator into position; it can be > adjusted manually up or down by pressing the blue manual release > button. The opening is self- adjusting. To secure after use, press > the green button, which simultaneously activates the evaporator and > returns the Cin-Eliminator to its storage position. > > You may log off if the green exit light is on over the evaporator . > If the red light is illuminated, one of the Cin-Eliminator > requirements has not been properly implemented. Press the "List Guy" > call button on the right of the evaporator . He will secure all > facilities from his control panel. > > To use the Auto-Unsub, first undress and place all your clothes in > the clothes rack. Put on the velcro slippers located in the cabinet > immediately below. Enter the shower, taking the entire kit with you. > On the control panel to your upper right upon entering you will see a > "Shower seal" button. Press to activate. A green light will then be > illuminated immediately below. On the intensity knob, select the > desired setting. Now depress the Auto-Unsub activation lever. Bathe > normally. > > The Auto-Unsub will automatically go off after three minutes unless > you activate the "Manual off" override switch by flipping it up. When > you are ready to leave, press the blue "Shower seal" release button. > The door will open and you may leave. Please remove the velcro > slippers and place them in their container. > > If you prefer the ultrasonic log-off mode, press the indicated blue > button. When the twin panels open, pull forward by rings A & B. The > knob to the left, just below the blue light, has three settings, low, > medium or high. For normal use, the medium setting is suggested. > > After these settings have been made, you can activate the device by > switching to the "ON" position the clearly marked red switch. If > during the unsubscribing operation, you wish to change the settings, > place the "manual off" override switch in the "OFF" position. You may > now make the change and repeat the cycle. When the green exit light > goes on, you may log off and have lunch. Please close the door behind > you. > > > >

2 1

My Bad
by Te Aroha 12 Jun '01

12 Jun '01

OK ppl's My Bad I submitted to this list instead of majordomo...Cheers to Brendan Willis, Mark Little, Gavin Quayle and crew for sorting me out...I guess supervising you guys taught me nothing. :) Te Aroha Maxnet Support Team tearoha(a)maxnet.co.nz t(a)maxnet.co.nz

1 0

subscribe NZOG
by Te Aroha 12 Jun '01

12 Jun '01

Hi there Can you please subscribe me to this mailing list. Cheers Te Aroha Maxnet Support Team Customer Services Supervisor support(a)maxnet.co.nz Ph: 0508 MAXNET Ph: (09) 300-7555 Tech Support Ph: (09) 300-7222 Office

1 0

Problem at Clear???
by Craig Whitmore 12 Jun '01

12 Jun '01

Anyone notice that Clear are unreachable from the Internet?? (Overseas/Orcon/Win Internet/etc) Thanks Craig Whitmore I Talk for Myself

5 7

RE: Lots of broken mail at Xtra
by Olof Olsson 11 Jun '01

11 Jun '01

> From: Joe Abley [mailto:jabley(a)automagic.org] > Sent: Tuesday, June 12, 2001 6:59 AM > > ETRN is actually optional with mailbagging, too. Connection attempts > will begin shortly after the mailbagging user connects, and > will repeat > at regular intervals if there is mail to deliver. > > The following script may be useful: > > for n in ${things_involving_mail} > do > olof ${n} > done > Thanks for blowing my cover Joe! :-) Basically, what we do for CLEAR Net Mail is: 1) Add X-Envelope-To: headers to all inbound messages. This allows for POP3 retrieval of messages for one or more domains/users etc, without having lost the envelope recipients. (Many POP3 <=> SMTP gateways have the capabilities of performing deliveries on these kind of custom headers.) Is POP3 the right mechanism for this? Maybe not, but a lot of our customers want to do just this. And of course, the customer is always right. :-) But a nicer way is mailbagging... For mailbagging: 2a) For mailbagging customers we delivery messages into a separate mailbagging store. This store is designed so that it can efficiently queue large number of messages for each customer. It also (of course) preserves envelope information. 2b) Customers configure a "mailbagging pick-up user-id" via our self-provisioning interface. 2c) When a customers logs on using his pick-up user-id, we kick off outbound SMTP delivery. Once all the mail has been delivered, we check for new incoming mail every 60 seconds, and deliver appropriately. (For as long as the user stays logged on.) Some notes: *** We can do this for both static _and_ dynamic IP assignments. (However, we only offer customers dynamic IP addresses. Static addresses for dial-up customers are bad, for many reasons.) *** Handling dynamic IP addresses (obviously) requires us to keep track, in real-time, of who is assigned what IP address. We do this via a real-time database. Delivery via SMTP is triggered from this database when a user-id record is added that is tagged as a "mailbagging pick-up user-id". *** There are some racing conditions which makes it hard to safely use a standard MTA to implement mailbagging with dynamic IP addresses. Hence, we use a custom MTA. *** We ignore ETRNs. --Olof --------- 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: Lots of broken mail at Xtra
by Ben Martel 10 Jun '01

10 Jun '01

Don, > If you really must use POP to retrieve multiple users' mail, use > multiple mailboxes and query 'em all. Better still, use a real > transport protocol. SMTP with ETRN or dial-up triggering > strikes me as a > *much* better (if not perfect) solution. <infomercial>Take a look @ CLEARs mailbagging product. It even does it on dialup connect or dial-up triggering as you suggested :)</infomercial> ~benm --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

FW: Rootserver Change Request
by Peter Mott 06 Jun '01

06 Jun '01

Anybody got anything to say about this? Peter Mott Chief Enthusiast 2day.com -/- > ***************************************************************** > This message is being sent to 70 ISP's in New Zealand > It's a request for your company to change it's Root Server setup. > ***************************************************************** > > > To whom it may concern, > > > The Wapterix Internet Group is in the process of setting up it's online > presence. > > We are looking to offer a number of online services including hosting, > domain registration and web design to name a view. One area we > will not be > entering into is that of an ISP. We feel that there is already a good > selection and number of ISP's operating in New Zealand and for us to enter > into this sort of service would dilute our energies from the provision of > services that will be profitable for us. > > The reason for our contacting you is that we have a number of domains > relevant to our business operation that have been registered > under the ".z" > domain extension. As this extension is an alternative extension, and not > recognised by the A-Root Server, we are writing to ask that you > adjust your > name servers and resolvers to allow New Zealand internet users access to > this extension. > > The extension is controlled by ADNS.net through their site, www.adns.net, > where you will be able to find information on how, as an ISP, you > can change > your servers so that domains under this extension are visible to the > internet users of New Zealand. > > ADNS use the ORSC Root Server (www.open-rsc.org) rather than the A Root > Server given that they are an alternative extension. This Root > Server has a > large number of internet users accessing it, and offers the added > advantage > that users, while being able to access alternative extensions > covered by the > ORSC Root Server, they can also access all generic extensions - > .com, .net, > .org, .co.nz - and so on. > > We have chosen to operate domains under the ".z" extension in > support of our > belief that the internet should be not be controlled by one > governing body, > and that individuals should be free to choose any extension that > suits their > operation and/or operate their own extensions, provided those > extensions do > not legally interfere with the operation of extensions operated by other > individuals or organisations. We hope you accept our view and > will support > us in our operation by changing your servers accordingly allowing us to > operate our domains, and New Zealand internet users the ability to access > our domains. > > Should you have any querries please do not hesitate to contact me. I will > be more than willing to answer any questions you may have. > > > Yours > > Trevarr McCarthy > President > The Wapterix Internet Group --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 7

VOIP, the next big test.
by Roger De Salis 05 Jun '01

05 Jun '01

This is sufficiently thought provoking and on-topic that I thought it worthy of posting. RDS. The article disses Cisco fairly thoroughly (there are also some compliments as well). I've added some comments at the bottom. Feel free to discard my comments as appropriate. -----Original Message----- From: Peter Ecclesine [mailto:petere(a)aimnet.com] Sent: Monday, 4 June 2001 9:59 PM To: wireless Subject: Comments on Australia's VOIP nets From: Frank A. Coluccio Thursday, May 31, 2001 12:35 PM Glenn Turner, who apparently operates the Australian Academic and Research Network has some very interesting IMO things to say about running voice over the Internet. This is from the ongoing discussion on NANOG that questions: QOS or More Bandwidth? Enjoy, FAC ================snip begins: <so and so> wrote: > > > Whenever I did the cost of deploying and managing fancy QoS > > and compared it with the cost of getting and managing more > > capacity, it was always MUCH MUCH cheaper to get and manage > > more capacity than to mess with more QoS. > > We did one VoIP network deployment, and I tried each of the > different QoS services in IOS at that time (about 18 months ago) > both in the lab and in the field, and more bandwidth was the > answer then. Interesting. We have a national VoIP network which handles long-distance calls for the Australian universities. It's not a trial, it's a real VoIP rollout that interconnects the PBXs of the universities. We think that's about 300,000 handsets. More bandwidth doesn't cut it, as the voice calls then fail during DDOS attacks upon the network infrastructure. It's not too hard to fill even a 2.5Gbps link when new web servers come with gigabit interfaces and when GbE campus backbones are being rolled out. If these DDOS attacks use protocols like UDP DNS then traffic shaping the protocol is problematic and the source IP subnet from where the attack is launched needs to be filtered instead. Just finding and filtering a DDOS source can easily take more than five minutes, which pushes the availability to less than 99.999% and leads to legal issues with telecommunications regulators about access to emergency services. We found the Cisco low latency queuing to be adequate. It still has a fair amount of jitter, but not enough to matter for VoIP calls with a diameter of 4,000Km. We do have issues with Cisco's 7500: dCEF is still problematic, but needed for the LLQ feature. The QoS features are too linked to the hardware (you can't configure a service-policy that is enacted on the VIP or main CPU, depending upon the hardware). Despite QoS being most needed on cheap E1/T1 links, they expect you to upgrade to a many thousand dollar VIP4 to support QoS. We police access to QoS by source IP address, mapping non-conforming traffic to DSCP=0. As this requires an access list executed for each packet, the number of VoIP-speaking connecting sites to 50 or so, and requires H.323/SIP proxies at the edge of the sites. We don't use IntServ. When a link is down RSVP takes so long to find an alternative path that the telephone user hangs up. So what we are really waiting for is the implementation of the combined IntServ/DiffServ model so that hosts on member networks can do local authentication and bandwidth reservation and we can police the amount of QoS traffic presented at each edge interface. "Local authentication and bandwidth reservation" also hides a host of issues that are yet to be fully addressed. Most universities don't even *have* an authentication source that covers everyone that can use IP telephony. In practice, even with our deliberately simplistic implementation this whole area is a IOS version nightmare. There's no excuse for a monolithic statically-linked executable in this day and age. Hopefully Juniper's success with monolithic kernel and user-space programs will lead to Cisco looking to leapfrog the competition and adopt the on-the-fly upgradable software modules as described in Active Bridging (1997). Having dissed Cisco, I should point out that their H.323/ISDN gateway software that runs on their RAS boxes (5300, etc) was the most solid of all the manufacturers we tested and Cisco was the vendor most willing to fix the differing interpretations of ISDN we enountered when we connected the North American-developed RAS to our European-developed PABXs (Ericsson MD110, Alcatel, etc). ------------------------- As far as the "engineering staff costs" argument goes, we have found that they the real engineering time goes into hardening the existing infrastructure. When carrying voice every engineering shortcut you have taken comes back to haunt you -- clocking problems, a low percentage of CRCs, ATM links with no OAM, synchronous links with carrier nailed high. Very little of the costs were due to the configuration of the routers. Most of the cost was incurred at the edge of the network, where there is a greater variety of devices, less correct engineering, and worse configuration control. > The trans-Pacific problem is being solved. Give it another > 6-18 months and fibre between US/CA and ANZ or JP or SG should > drop significantly in price. Although the price will drop, it will never drop to the levels of trans-Atlantic prices. Even then, countries like Fiji which have landing points would find it hard to raise the millions required to buy an STM-1 from that landing point. You can make a case that North America is unique. It doesn't have 2,000Km expanses with no population centers. It isn't split off from the remainder of the world by mountain ranges so high that to do an hour's lifting can take a week. It doesn't have a population so huge that training people to lay fiber is in itself a massive undertaking. In these cases, no amount of money will buy you more bandwidth tomorrow and the engineering costs of QoS and TE are immediately worthwhile. VoIP and QoS let you use all of the long-haul optical capacity for IP, whereas the slower growth of the Internet in North America allowed the running parallel Internet and PSTN networks. -- end snip -- 'Time doesn't fool around.' 'without prejudice' U.C.C. 1-207 ======= End of Article ============================================= Comments by Rog. Please discard if you think not appropriate to this list. Cisco 7500, this was a pretty cool box 5 years ago. You all bought lots of them. We acknowledge it is now struggling to keep up, due to all the bandwidth. We'll trade it at favourable rates to help. Current thinking within Cisco is.... 7500 is a 5Gbps box. (really 4 x 1.25Gbps box). 6509/7600OSR is a 256Gbps box. Sufficient horsepower for long and complex ACL lists to counter DDOS attacks (but how do you find and load the source of the attack into the ACL swiftly?) 16 port GE cards means price of GE is slightly below US$1K/port. (7600-OSR appears to me to be 6509 with Optical Service Modules, STM-4, STM-16, GigE blades????? No we don't know why they did this either?) Fiji. The cost of an STM-1 card is about 5-10K. Double it for reliable service. So the millions referred to is really about how the Southern Cross consortium recover their investment dosh. Doing a sweet-heart deal for Fiji, and setting a price that Fiji can afford, sets a very unwelcome precedent for negotiations with other countries. So effectively Fiji misses out, and the country most in need of low-cost communications cannot have it. This is of interest to me as the same economic situation occurs in rural NZ. If rural NZ had widely available, fast communications infrastructure (10mpbs customer access minimum), then the choice of where to run a new-economy business would be much wider. The alternative is building more roads in Auckland. London built the M25 as a possible solution, but it simply created more traffic. Yeah, you have to have both, but comms networks are cheaper to build than road networks. R -- \_ 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

3 2

Number of AS's and Networks in NZ?
by Craig Whitmore 04 Jun '01

04 Jun '01

Has anyone a list of AS's in New Zealand I should see and the number of Networks associated with each AS? I want to make sure I am going Nationally for every place that is in New Zealand Thanks Craig Whitmore

9 14

Paradise Not Announcing Routes to Telecom?
by Craig Whitmore 04 Jun '01

04 Jun '01

I don't think paradise is announcing all their ranges to Global-gateway/telecom/netgate ... All I can see coming from Paradise's AS via Global-Gateway's AS is.. 202.0.32.0/21 202.0.40.0 202.49.136.0 202.49.137.0 202.50.109.0 203.96.144.0/20 Which means going to a few of there sites takes the long way around This is from 210.55.71.10 (Netgate DSL Ports) [root(a)lennon /root]# traceroute 203.79.66.5 traceroute to 203.79.66.5 (203.79.66.5), 30 hops max, 38 byte packets 1 210-55-71-254.adsl.netgate.net.nz (210.55.71.254) 46.917 ms 45.328 ms 47.723 ms 2 gateway.adsl.netgate.net.nz (192.168.253.1) 42.951 ms 45.873 ms 46.387 ms 3 202.37.247.253 (202.37.247.253) 247.152 ms 293.514 ms 228.592 ms 4 p1-1.akbr2.global-gateway.net.nz (202.50.116.161) 129.325 ms 170.006 ms 162.937 ms 5 202.50.116.170 (202.50.116.170) 168.543 ms 176.873 ms 181.526 ms 6 a4-1-0-3.sybr1.netgate.net.nz (202.50.116.82) 195.767 ms 191.548 ms 195.817 ms 7 connect.sybr1.netgate.net.nz (202.50.116.115) 200.465 ms 216.558 ms 229.336 ms 8 atm0-1-0-27.bdr1.syd.connect.com.au (210.8.219.237) 236.039 ms 233.281 ms 169.433 ms 9 Fddi1-0-0.pad13.Sydney.telstra.net (139.130.32.5) 179.480 ms 184.586 ms 197.406 ms 10 GigabitEthernet4-0.pad-core3.Sydney.telstra.net (139.130.249.240) 197.091 ms 222.966 ms 226.596 ms 11 Pos6-0-0.nzsx-core1.Auckland.net.reach.com (203.50.126.50) 251.709 ms 244.772 ms 259.497 ms 12 FE4-1-0.b2.sxb.akl.tsnz.net (203.98.4.2) 237.052 ms 247.860 ms 192.220 ms 13 bertha.lqy.tsnz.net (203.98.21.29) 219.672 ms 203.286 ms 217.687 ms 14 fe0-0-0.kelly.paradise.net.nz (203.96.152.1) 221.610 ms 243.152 ms 240.241 ms 15 ipnet.ipnet2.paradise.net.nz (203.96.155.157) 259.118 ms 244.233 ms 225.757 ms 16 * * * 17 203-79-66-5.adsl-wns.paradise.net.nz (203.79.66.5) 219.332 ms 220.679 ms 234.058 ms Paradises announced ranges works well ... traceroute to 202.49.136.1 (202.49.136.1), 30 hops max, 38 byte packets 1 210-55-71-254.adsl.netgate.net.nz (210.55.71.254) 48.527 ms 45.405 ms 49.883 ms 2 gateway.adsl.netgate.net.nz (192.168.253.1) 45.382 ms 45.137 ms 47.048 ms 3 a3-0-1.tkcr1.netgate.net.nz (202.50.245.162) 44.982 ms 47.008 ms 45.924 ms 4 paradise.akcr1.netgate.net.nz (202.37.246.74) 57.388 ms 56.106 ms 57.412 ms 5 fe7-0-1.bertha.paradise.net.nz (203.96.152.254) 55.865 ms 55.924 ms 58.631 ms 6 203-96-144-21.cable.paradise.net.nz (203.96.144.21) 67.965 ms * 66.898 ms Thanks Craig Whitmore --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 4

The New Zealand Network Operators' Group
by Donald Neal 03 Jun '01

03 Jun '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 230 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. 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

(fwd) Re: NOTICE TO ALL (fwd)
by Matt Camp 02 Jun '01

02 Jun '01

Posted to nz.net.admin: -- forwarded message -- I think that this will clear it all up. As the letter was sent to ALL MIS cutomers I will presume that it is not confidential in anyway, if it is I humbly appologise Alan. ######################################################################## The rumour mill is doing overtime, so it is time to make some announcements. 1: Manawatu Internet Services Ltd is closing down. 2: There will be no loss of service for MIS or Flatnet customers. The last 9 years of operation of Manawatu Internet Services Ltd (Dawghaus BBS up until 1994) have been enjoyable and entertaining, however the stress levels associated with operating a small ISP have been taking their toll on my health for the last 2-3 years and it really has become time to move on to different fields. Mercury Telecommunications Ltd have acquired all MIS operations and will take over all DNS hosting, Webhosting and dialup accounts previously handled by Manawatu Internet Services Ltd. I am aware that almost all MIS/MFN customers have been with us for a long time, so I have been at pains to ensure that the best deal has been struck for our customers. For 95% of MIS dialup clients, the transition will be seamless. The exceptions are those people running Windows 3.* or Macintosh machines, as these machines have nameserver settings manually entered and will need to be edited. Please contact me for more details if you feel you will need assistance to change things. There are also 5-10 account names which clash with existing Quicksilver account names so changes may need to be made for checking mail - we're still working out how to resolve this small problem. Noone will have any changes made to their email address. As a great benefit of the changeover, national dialup coverage will again be available and Mercury also offer some very good toll deals. The changeover of dialup access will take place during the coming week and official notice from Mercury Telecommunications will be sent by paper mail to all MIS/MFN clients shortly. If you have any queries, please contact me by email, or by phone. I extend my thanks to all clients for their support over the years and I hope that you will all continue to support your new ISP - they _will_ provide you with continued good service and support. Alan Brown Director, Manawatu Internet Services. -- end of forwarded message -- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

What's up at ORBS
by Andy Linton 31 May '01

31 May '01

Looking at www.orbs.org this morning (as I frequently do (;-)) I see: Due to circumstances beyond our control, the ORBS website is no longer available. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 5

FW: BLOCK: ORBS down?
by Juha Saarinen 31 May '01

31 May '01

-----Original Message----- From: Bill Maloy [mailto:Bill.Maloy(a)GOLDINC.COM] Sent: Friday, 1 June 2001 14:12 Subject: Re: BLOCK: ORBS down? > I downloaded the ORBS output_current.txt database on the May 22, 2001. Umm ... Data Size Updated ---------------------------------------------- ---------- ------------ http://homepages.tcp.co.uk/~rjb/in_curr.zip 1346297 2001/05/26 http://www.tlh.com.ar/spambusters/in_curr.zip 1346297 2001/05/26 http://orbsdata.1st.net/inputs.zip 4861634 2001/05/26 http://www.tlh.com.ar/spambusters/inputs.zip 376540 2001/05/27 http://homepages.tcp.co.uk/~rjb/out_curr.zip 1143119 2001/05/26 http://orbsdata.1st.net/out_curr.zip 1143119 2001/05/26 http://orbs.southcot.com/outputs.zip 3681170 2001/05/26 http://homepages.tcp.co.uk/~rjb/manual.zip 69842 2001/05/26 http://www.tlh.com.ar/spambusters/manual.zip 69842 2001/05/26 http://orbs.southcot.com/ok.zip 10806456 2001/03/21 -- Bill Maloy (brm4) And no, akcf1.xtra.co.nz, the right-angle-bracket is NOT part of the URL. "GET /db.orbs.dorkslayers.com.1998.11.30.gz> HTTP/1.0" 404 540 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Asiaonline Peering
by Chris Hellberg 30 May '01

30 May '01

This trace is coming from a netgate-connected PC via DSL to iconz.: odysseus(a)ns1:~$ traceroute www.iconz.co.nz traceroute to www.iconz.co.nz (210.48.1.113), 30 hops max, 38 byte packets 1 gateway (192.168.100.2) 1.214 ms 1.058 ms 1.001 ms 2 172.18.0.37 (172.18.0.37) 18.447 ms 16.481 ms 16.707 ms 3 172.18.4.2 (172.18.4.2) 28.454 ms 18.017 ms 17.485 ms 4 asiaonlinenz.ape.net.nz (192.203.154.44) 18.131 ms 18.229 ms 18.473 ms 5 202.14.100.33 (202.14.100.33) 19.081 ms 18.982 ms 18.945 ms 6 202.14.100.33 (202.14.100.33) 19.144 ms !A * * >From what I can gather there's peering between the two at ape. If reverse name look-ups aren't reliable enough to go to, the number of hops has certainly decreased so I'll go on that. :) Chris --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 9

NZ BGP stats
by Joe Abley 30 May '01

30 May '01

I'd like to collect some BGP data from NZ ISPs to see if I can see the same trends in RIB growth, de-aggregation and multi-homing that other people are seeing in other parts of the world. An NZ perspective might be interestingly different because of the history of pervasive peering that is absent from other environments. If possible, I'd like to take as full a BGP feed as possible from as many people as possible. Something like this, in fact: router bgp xxxx neighbor 202.89.128.76 description jabley(a)automagic.org neighbor 202.89.128.76 remote-as 65517 neighbor 202.89.128.76 ebgp-multihop 254 neighbor 202.89.128.76 send-community or perhaps protocols { bgp { group jabley { type external; description "jabley(a)automagic.org"; peer-as 65517; multihop ttl 254; neighbor 202.89.128.76; } } if that suits you better. If anybody thinks they might be happy to send me some data like this for a while, please let me know. Thanks! Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 9

Prefix's
by James Tyson 30 May '01

30 May '01

ip prefix-list attica-networks description contact: noc(a)noc.attica.net.nz ip prefix-list attica-networks permit 202.50.60.0/22 ip prefix-list attica-networks permit 202.50.170.0/24 ip prefix-list attica-networks permit 202.180.64.0/18 ip prefix-list attica-networks permit 210.55.5.0/24 ip prefix-list attica-networks permit 210.55.111.0/24 ip prefix-list attica-networks permit 210.55.157.0/24 ip prefix-list attica-networks permit 210.55.202.0/24 ip prefix-list attica-networks permit 210.55.254.0/24 policy-options { policy-statement attica-networks { term accept { from { # contact: noc(a)noc.attica.net.nz route-filter 202.50.60.0/22 exact; route-filter 202.50.170.0/24 exact; route-filter 202.180.64.0/18 exact; route-filter 210.55.5.0/24 exact; route-filter 210.55.111.0/24 exact; route-filter 210.55.157.0/24 exact; route-filter 210.55.202.0/24 exact; route-filter 210.55.254.0/24 exact; } then accept; } term reject { then reject; } } } 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

New improved prefix list :)
by David Robb 28 May '01

28 May '01

Now with free steak knives! [1] ip prefix-list ihug-networks seq 5 permit 202.36.94.0/23 le 24 ip prefix-list ihug-networks seq 10 permit 202.37.129.0/24 ip prefix-list ihug-networks seq 15 permit 202.37.136.0/24 ip prefix-list ihug-networks seq 20 permit 202.37.182.0/24 ip prefix-list ihug-networks seq 25 permit 202.37.194.0/24 ip prefix-list ihug-networks seq 30 permit 202.49.59.0/24 ip prefix-list ihug-networks seq 35 permit 202.49.88.0/23 le 24 ip prefix-list ihug-networks seq 40 permit 202.49.148.0/23 le 24 ip prefix-list ihug-networks seq 45 permit 202.49.176.0/23 le 24 ip prefix-list ihug-networks seq 50 permit 202.49.180.0/23 le 24 ip prefix-list ihug-networks seq 55 permit 202.49.186.0/24 ip prefix-list ihug-networks seq 60 permit 202.49.240.0/22 le 24 ip prefix-list ihug-networks seq 65 permit 202.49.249.0/24 ip prefix-list ihug-networks seq 70 permit 202.49.252.0/22 le 24 ip prefix-list ihug-networks seq 75 permit 202.50.84.0/24 ip prefix-list ihug-networks seq 80 permit 202.50.103.0/24 ip prefix-list ihug-networks seq 85 permit 202.50.255.0/24 ip prefix-list ihug-networks seq 90 permit 203.109.128.0/17 le 24 ip prefix-list ihug-networks seq 95 permit 203.173.128.0/17 le 24 ip prefix-list ihug-networks seq 100 permit 210.55.184.0/24 ip prefix-list ihug-networks seq 105 permit 210.55.203.0/24 ip prefix-list ihug-networks seq 110 permit 210.55.248.0/21 le 24 As you can see, these allow for variable masks. If anyone requires specific prefixes, let me know and I'll see what I can do. We change them from time to time, and its easier this way. [1] Ok, I was kidding about the steak knives. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 11

Search engines
by Jean-Francois Pirus 28 May '01

28 May '01

As anybody noticed any recent excess local search engine traffic. Since saturday we suddenly seem to be 'heavily indexed' by 203.97.86.133 (aka: ASDF Search NZ) and 210.48.127.49 (aka: kupe.searchnz.co.nz). It's quite obvious on our traffic graph between midnight and 6:30 am. One of them is obviously behing a 256K pipe. jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Clearfield Software Ltd Phone (+64-9) 358 2081 4th Floor 8-10 Whitaker Place Fax (+64-9) 358 2083 P O Box 2348 Auckland, New Zealand ------------------------------------------------------------------------ --------- 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 "Size Core" Phone lines
by Chris Rigby 28 May '01

28 May '01

I just had to deal with Telecom over a customer of ours who was having trouble getting connected and I was wondering if anyone here had experience with or had heard of the excuse Telecom gave me. The customer in question lives on Wahiki Island and cannot connect to our pool at anything greater than 13200 (if that). After excluding all the usual problems (bad lines, bad modem etc etc) we opened a fault with Telecom who quite happily informed us that the reason it wouldn't connect at a decent speed was that the homeowner was on "Size Core" lines instead of normal phone lines, due to being so remote. When pressed for an explanation the person in question could only tell me that "It was a method for making 8 home lines go over a single normal line". They said they couldn't give me a better explanation and didn't want to hand me to someone who could. And that was pretty much that. Has anyone else had any experience with this sort of technology (or lack of it) and could anyone shed anymore light on the widespereadness of it's use and if it's going to become more so. Chris Rigby Senior Systems Engineer IHUG - Into the Internet --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 7

SkillMap(tm) Assessment and Development Guidebooks
by Frontline Learning 27 May '01

27 May '01

How do you help a salesperson improve his or her selling ability if you don't know which SPECIFIC skills, habits or attitudes need to be developed or enhanced? How do you help ANY employee improve productivity unless you focus on developing SPECIFIC new abilities and behaviors? You and I have not met, but because youre a respected business professional with an interest in improving employee productivity, I would like to offer you a free preview of Frontline Learning's new SkillMap(tm) Assessment and Development Guidebooks. These new resources can help you bring added value to your current training initiatives by targeting each employee's individual development needs. This is a truly unique approach to training, and if you're open to learning more, please read on. If this is NOT an area of interest for you, I won't take up any more of your time, and I wish you continued success. Please note - upon receipt of this message you have automatically been removed from our email marketing list. You will not receive further communication from Frontline Learning unless you proactively respond to the message that follows. Kindest regards, David Kirkeby VP, Business Development Frontline Learning MORE ABOUT SKILLMAPS ... SkillMaps are available focusing on Sales, Customer Service, Team Building, Emotional Intelligence and Professional Communication. For example, the Professional Selling SkillMap helps salespeople, sales managers and trainers pinpoint the specific selling skills, habits and attitudes they should focus on for improved performance. It includes an assessment of selling skills in 20 categories, providing a graphical representation of each individuals unique selling strengths and growth opportunities. SkillMaps can be easily integrated into your existing training program or used as a stand-alone training tool for facilitated group training sessions, self-paced individual learning and one-on-one coaching. Based upon extensive research and field validation, each skill assessment measures strengths and growth opportunities in a broad range of skill categories. Upon completion of the Assessment, a Development Guidebook provides helpful tips, methods and strategies focused on each respondents specific development needs. A Facilitation and Coaching Guide provides detailed instructions for administering the Assessment along with fully scripted 1-hour workshops (one for each skill category) including handouts, overhead masters and PowerPoint® presentations. Audio programs are available for each skill category to provide post-training skill reinforcement or enhance the effectiveness of self-paced learning and one-on-one coaching. SkillMaps and other learning resources are available exclusively through our network of Affiliates - you can visit www.frontlinelearning.com for more information on any of our SkillMaps and our Affiliate program. You can request a free preview at: http://www.frontlinelearning.com/contactus1.htm I appreciate the time you've taken to read through this, and again, wish you continued success. Sincerely, David Kirkeby 763-404-9555 Please note - upon receipt of this message you have automatically been removed from our email marketing list. You will not receive further communication from Frontline Learning unless you proactively respond to this message. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1