- NZNOG - lists.nznog.org

BNZ Buyline client interface ??????
by John Lynch 24 Aug '01

24 Aug '01

Hi has anyone out there written a BNZ buyline client interface ? At this point I have downloaded the source code and written a client that sends a purchase message to the test system we have been setup on. The server responds with NX invalid currency code. The instructions I have received clearly states that a currency code must be included with a purchase request. I do not see anywhere in the supplied code provisions for including this information, to implement this myself it's seems to me I would have to change the supplied code right down at the packet construction level. I am sure this is not necessary and have missed something simple. Any help much appreciated. John Lynch System Administrator (string and tape specialist) Wise Net --------- 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: Anyone know a realiable .COM registry?
by david＠farrar.com 24 Aug '01

24 Aug '01

> On Fri, Aug 24, 2001 at 02:30:55AM +0000, david(a)farrar.com wrote: > > NSI are awful. You may find NSI will make it very hard to trasnfer > > your domain elsewhere. Good Luck. > > Actually, when transferring a gTLD domain the new registrar can > initiate the transfer. Register.com provide a web interface to > this, which is painless and doesn't involve interacting with NSI > in any frustrating way. Unfortunately NSI have unilaterally changed the rules. They now automatically cancel all tranfsers unless the name holder contact responds positively to an e- mail from NSI asking if they are happy with the change. The ICANN Registrars mailing list has more details. Registrars are having hundreds and thousands of requests cancelled by NSI. NSI claim you have five days to respond but often their e-mails don't go out until Day 4 etc. SOme registrants have tried three times to transfer with no luck. DPF --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 7

Re: Anyone know a realiable .COM registry?
by david＠farrar.com 23 Aug '01

23 Aug '01

> Does anyone know of a _reliable_ .COM registry? NZ based would be good but > not essential. Who do others use? Are you happy with them? Are their fees > reasonable? I use register.com and have found them good. They are not the chapeast around but no problems with them. > We are finding Network Solutions to e not worth the money. For the second > time in as many years they have deactivated one of our domains for non > payment of fees. In both cases the fees _had_ been paid. In this latest > episode we even paid twice just to (vainly) try to stop it from being > deactivated. NSI are awful. You may find NSI will make it very hard to trasnfer your domain elsewhere. Good Luck. DPF --------- 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: Anyone know a realiable .COM registry?
by Denis Gordon 23 Aug '01

23 Aug '01

Before everyone starts running off for a well earned weekend I'd just like to say a big THANKS to all those who responded to my call for help - at a dizzying pace. NSI have changed our domain's status to paid & say it'll be live again "within 24 hours" - let's not rush this :( Thank you all. Denis -----Original Message----- From: Denis Gordon [mailto:denis(a)dcc.govt.nz] Sent: Friday, 24 August 2001 2:17pm To: 'NZNOG List' Cc: Mike Harte Subject: Anyone know a realiable .COM registry? Does anyone know of a _reliable_ .COM registry? NZ based would be good but not essential. Who do others use? Are you happy with them? Are their fees reasonable? We are finding Network Solutions to e not worth the money. For the second time in as many years they have deactivated one of our domains for non payment of fees. In both cases the fees _had_ been paid. In this latest episode we even paid twice just to (vainly) try to stop it from being deactivated. This time has really hurt as it's where our main website lives. Their solution to getting it reactivated was "pay us again so we have a transaction we can find in our system"! So if anyone knows of a good reliable .COM registry please let me know asap. thanks Denis Gordon Network Administrator Information Systems Technical Support Dunedin City Council 50 The Octagon, PO Box 5045, Dunedin, New Zealand Ph: +64-3-474 3566 Fax: +64-3-474 3503 Mobile: 025 84 55 83 Email: denis(a)dcc.govt.nz WWW: http://www.CityOfDunedin.com/ --------- 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: Anyone know a realiable .COM registry?
by Peter Mott 23 Aug '01

23 Aug '01

At 24/08/2001 14:36, you wrote: >I understand Peter Mott & 2day.com provide this sort of service... they're >near me, in the occasionally sunny and warm North Shore of Auckland. Whilst we are accredited, we are not operational sorry. Its not that far away however :-) - PWM "Hell, there are no rules here - we're trying to accomplish something!" Thomas A. Edison --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Anyone know a realiable .COM registry?
by Denis Gordon 23 Aug '01

23 Aug '01

Does anyone know of a _reliable_ .COM registry? NZ based would be good but not essential. Who do others use? Are you happy with them? Are their fees reasonable? We are finding Network Solutions to e not worth the money. For the second time in as many years they have deactivated one of our domains for non payment of fees. In both cases the fees _had_ been paid. In this latest episode we even paid twice just to (vainly) try to stop it from being deactivated. This time has really hurt as it's where our main website lives. Their solution to getting it reactivated was "pay us again so we have a transaction we can find in our system"! So if anyone knows of a good reliable .COM registry please let me know asap. thanks Denis Gordon Network Administrator Information Systems Technical Support Dunedin City Council 50 The Octagon, PO Box 5045, Dunedin, New Zealand Ph: +64-3-474 3566 Fax: +64-3-474 3503 Mobile: 025 84 55 83 Email: denis(a)dcc.govt.nz WWW: http://www.CityOfDunedin.com/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

UPDATE: Xtra broken?
by Ben Martel 22 Aug '01

22 Aug '01

Hi all, Spoke to XTRA and they are now correctly announcing 202.49.143/24 at APE to CLEAR, this has corrected the Australia routing spacial anomily :). ~ben =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Ben Martel Ph: +64 9 9124067 CLEAR Net Development Fax:+64 9 9125008 Mob:+64 21 541202 =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 6

Cisco 2610 thru put
by Peter Mott 21 Aug '01

21 Aug '01

Does anybody have any experience with how much bandwidth you can realistically route through a 2610 before it starts to huff and puff? ie, Will it cope with 2x 2meg frame ccts running flat out - PWM "Hell, there are no rules here - we're trying to accomplish something!" Thomas A. Edison --------- 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: UPDATE: Xtra broken?
by Phill Groom 21 Aug '01

21 Aug '01

Sort of related to this thread; http://michael.toren.net/code/tcptraceroute/ Quite cool! 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: XTRA network having problems?
by Ben Martel 21 Aug '01

21 Aug '01

Hey, > The original poster was questioning whether the site was up, > since it was > unreachable with ICMP. > By blocking all ICMP, such things as MTU path discovery are > also broken - > just like Hotmail. The original poster is aware of how blocking ICMP breaks things. In fact I am the indirect recipient of a 'display time on the wall alarm clock' for people who cant turn their heads at night (due to drunkeness generally), on the basis of fixing some American site that was broken because of it. I was actually trying to query (obviously not successfully - well Joe got it!) why the routing to one of the resolved addresses for www.nbnz.co.nz is being dropped by Xtra on their border router @ APE. Secondly why the hell the traffic should go through Australia to get their in the first place. TIA ~benm --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

XTRA network having problems?
by Ben Martel 21 Aug '01

21 Aug '01

Hey all, Anybody noticed if XTRA is having problems??? ~benm noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (210.55.168.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 0.681 ms 0.605 ms 0.620 ms 2 cs2-e4-4-acld.auckland.clix.net.nz (203.167.224.55) 1.295 ms 0.618 ms 0.616 ms 3 ba2-fe0-1-0-acld.auckland.clix.net.nz (203.97.9.177) 1.695 ms 1.342 ms 0.994 ms 4 xtra.ape.net.nz (192.203.154.60) 2.068 ms 3.037 ms 2.400 ms 5 202-37-237-229.dds.xtra.co.nz (202.37.237.229) 11.157 ms 14.180 ms 12.818 ms ^C noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (202.49.143.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 1.027 ms 0.643 ms 0.591 ms 2 core1-fe6-1-0-acld.auckland.clix.net.nz (203.97.2.241) 0.828 ms 0.832 ms 0.748 ms 3 b1-atm2-0-1-wcms.sydney.clix.net.nz (203.97.83.222) 24.861 ms 24.981 ms 24.879 ms 4 500.Serial0-1-1.GW2.SYD2.ALTER.NET (203.166.90.77) 25.304 ms 25.446 ms 25.532 ms 5 422.at-6-0-0.XR1.SYD2.Alter.Net (210.80.3.93) 25.821 ms 26.227 ms 26.369 ms 6 0.SO-5-0-0.XR1.SYD4.ALTER.NET (210.80.33.222) 26.798 ms 26.203 ms 26.783 ms 7 0.SO-0-0-1.XR2.SYD3.ALTER.NET (210.80.33.10) 26.120 ms 26.265 ms 26.196 ms 8 412.ATM8-0-0.GW1.SYD3.Alter.Net (210.80.3.158) 26.766 ms 27.052 ms 27.655 ms 9 500.ATM1-0.BORDER3.SYD.OZEMAIL.NET.AU (203.166.16.38) 29.680 ms 28.339 ms 27.345 ms 10 border1-fe0-0.syd.ozemail.net.au (203.108.190.150) 29.397 ms 27.699 ms 28.171 ms 11 203.108.1.237 (203.108.1.237) 125.545 ms 44.672 ms 47.893 ms 12 atm0-1-0-2.bdr1.hay.connect.com.au (210.8.219.234) 32.714 ms 41.311 ms 50.258 ms 13 f4-0-0-2.sybr1.netgate.net.nz (202.50.116.113) 59.829 ms 36.707 ms 35.536 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (202.49.143.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 0.804 ms 0.591 ms 0.574 ms 2 core1-fe6-1-0-acld.auckland.clix.net.nz (203.97.2.241) 0.868 ms 1.181 ms 0.835 ms 3 b1-atm2-0-1-wcms.sydney.clix.net.nz (203.97.83.222) 26.398 ms 24.848 ms 25.311 ms 4 500.Serial0-1-1.GW2.SYD2.ALTER.NET (203.166.90.77) 25.351 ms 25.321 ms 25.193 ms 5 422.at-6-0-0.XR1.SYD2.Alter.Net (210.80.3.93) 26.074 ms 25.617 ms 25.889 ms 6 0.SO-5-0-0.XR1.SYD4.ALTER.NET (210.80.33.222) 26.125 ms 26.219 ms 26.750 ms 7 0.SO-0-0-1.XR2.SYD3.ALTER.NET (210.80.33.10) 26.163 ms 26.097 ms 26.047 ms 8 412.ATM8-0-0.GW1.SYD3.Alter.Net (210.80.3.158) 27.231 ms 27.047 ms 27.093 ms 9 500.ATM1-0.BORDER3.SYD.OZEMAIL.NET.AU (203.166.16.38) 27.965 ms 27.783 ms 28.140 ms 10 border1-fe0-0.syd.ozemail.net.au (203.108.190.150) 28.064 ms 28.494 ms 28.159 ms 11 203.108.1.237 (203.108.1.237) 38.559 ms 29.714 ms 35.737 ms 12 atm0-1-0-2.bdr1.hay.connect.com.au (210.8.219.234) 36.318 ms 34.299 ms 32.086 ms 13 f4-0-0-2.sybr1.netgate.net.nz (202.50.116.113) 32.040 ms 31.104 ms 30.982 ms 14 * * * 15 * *^C noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (210.55.168.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 0.663 ms 0.619 ms 0.612 ms 2 cs2-e4-4-acld.auckland.clix.net.nz (203.167.224.55) 0.698 ms 0.654 ms 1.278 ms 3 ba2-fe0-1-0-acld.auckland.clix.net.nz (203.97.9.177) 0.899 ms 1.329 ms 0.946 ms 4 xtra.ape.net.nz (192.203.154.60) 1.588 ms 3.299 ms 2.391 ms 5 203.96.111.218 (203.96.111.218) 11.624 ms 11.308 ms 11.742 ms 6 * 202-37-237-133.dds.xtra.co.nz (202.37.237.133) 87.635 ms 106.486 ms ^C noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (210.55.168.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 0.678 ms 0.607 ms 0.834 ms 2 cs2-e4-4-acld.auckland.clix.net.nz (203.167.224.55) 0.776 ms 0.646 ms 0.613 ms 3 ba2-fe0-1-0-acld.auckland.clix.net.nz (203.97.9.177) 0.855 ms 1.131 ms 0.718 ms 4 xtra.ape.net.nz (192.203.154.60) 3.019 ms 2.365 ms 1.725 ms 5 203.96.111.218 (203.96.111.218) 42.603 ms 41.431 ms 47.360 ms 6 203.96.111.217 (203.96.111.217) 60.746 ms 66.191 ms 78.594 ms 7 203.96.111.218 (203.96.111.218) 154.869 ms 159.711 ms * ^C noc% traceroute www.nbnz.co.nz traceroute to www.nbnz.co.nz (210.55.168.70), 30 hops max, 40 byte packets 1 cs-red-vrrp.auckland.clix.net.nz (203.167.224.53) 0.672 ms 0.634 ms 1.264 ms 2 cs2-e4-4-acld.auckland.clix.net.nz (203.167.224.55) 0.895 ms 0.643 ms 0.652 ms 3 ba2-fe0-1-0-acld.auckland.clix.net.nz (203.97.9.177) 1.304 ms 1.809 ms 1.085 ms 4 xtra.ape.net.nz (192.203.154.60) 2.856 ms 2.155 ms 1.760 ms 5 202-37-237-229.dds.xtra.co.nz (202.37.237.229) 70.480 ms 57.187 ms 36.798 ms 6 *^C noc% ~ben =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Ben Martel Ph: +64 9 9124067 CLEAR Net Development Fax:+64 9 9125008 Mob:+64 21 541202 =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 12

CLEAR Net Tempest
by Neil 16 Aug '01

16 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

11 13

Cisco pages about code Red.
by Roger De Salis 16 Aug '01

16 Aug '01

Apologies if you have seen this multiple times. It is a little more complete than previous posted items. - R Cisco Technical Assistance Center News Flash - August 16, 2001 http://www.cisco.com/tac -------------------------------------------- "Code Red" Worm Update ____________________________________________ Dear Cisco Customer, For the most up-to-date information on the "Code Red" worm, visit the Cisco TAC Web Site "'Code Red' Technical Tips" page. Be sure to check this page for new and updated documents. The "'Code Red' Technical Tips" page can be reached at: http://www.cisco.com/tac/newsflash/codered_tt_08162001.html ISSUES REGARDING THE "CODE RED" WORM There are three main issues to deal with regarding the "Code Red" worm: 1. The worm infects and replicates through a vulnerability in the Microsoft Internet Information Server (IIS). This creates an infection exposure for Cisco products that embed or run on IIS. This exposure can be dealt with by applying Microsoft patches to the IIS servers. These patches are available at: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security… 2. The earlier versions of the worm launched Denial of Service (DoS) attacks from the infected servers targeted at the White House Web Site. These DoS attacks can create high volumes of Internet-bound traffic. 3. The most recent variant of the worm creates high volumes of traffic on local networks, which may disrupt general network performance. The majority of the calls the Cisco TAC is receiving from customers are not due to Cisco products being infected by the worm; rather, many customers are experiencing the indirect impact that is caused by the messaging storms that occur because infected IIS servers are generating large amounts of network traffic while attempting to infect other IIS servers. This network traffic may cause networking equipment to become overloaded, which results in slow response, reloads, and other types of network equipment failures. Workarounds for the affected equipment, where applicable, are available at the "Cisco Security Advisory: 'Code Red' Worm" page, which can be found at: http://www.cisco.com/tac/newsflash/codered_secadvisory_08162001.html UNDERSTANDING THE "CODE RED" WORM A malicious self-replicating program known as the "Code Red" worm is targeted at systems running the Microsoft IIS. Several Cisco products are installed or provided on targeted systems. Additionally, the behavior of the worm can cause problems for other network devices. The following Cisco products are vulnerable to infection because they run affected versions of Microsoft IIS: * Cisco CallManager * Cisco Unity Server * Cisco uOne * Cisco ICS 7750 * Cisco Building Broadband Service Manager * Cisco IP/VC 3540 Application Server Other Cisco products may also be adversely affected by the "Code Red" worm. Please read "Cisco Security Advisory: 'Code Red' Worm" for further details. This advisory can be accessed at: http://www.cisco.com/tac/newsflash/codered_secadvisory_08162001.html All updates and workarounds are available under the "Featured Links" section of the Cisco TAC Web Home Page, which can be reached at: http://www.cisco.com/tac/newsflash/featured_links_08162001.html To access the documents directly, go to the "'Code Red' Technical Tips" page. This page can be reached at: http://www.cisco.com/tac/newsflash/codered_tt_08162001.html You can prevent the infection of servers and stop the spread of the worm by applying a Microsoft patch to vulnerable servers. This patch is available at: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security… Once infected, a system may require additional repair due to the damage caused by the worm. This is also documented on the Microsoft Web Site at: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsoluti… ADDITIONAL RESOURCES The Cisco TAC Web Site "'Code Red' Technical Tips" page includes new and updated documents with details about how the worm virus impacts Cisco networks, and what you can do to protect your network. These additional resources include: * "Cisco Security Advisory: 'Code Red' Worm - Customer Impact" * "The Network-Based Application Recognition and Access Control Lists for Blocking the 'Code Red' Worm at Network Ingress Points" * "Dealing with 'mallocfail' and High CPU Utilization Resulting From the 'Code Red' Worm" * "How to Filter 'Code Red' on Cisco Cache and Content Engines" CISCO PRODUCT SECURITY INCIDENT PROCEDURES Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, registering to receive security information from Cisco, and handling press inquiries regarding Cisco security notices is available at: http://www.cisco.com/tac/newsflash/prod_security_08162001.html Sincerely, Cisco TAC -- \_ Roger De Salis rdesalis(a)cisco.com </' 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 ` By 2003, every home should have a Terabyte file server, a 10Mbps Internet Connection, a decent firewall and no M$ taxes. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Auckland Wireless Cards
by J S Russell 14 Aug '01

14 Aug '01

Short notice, but: Does anyone on this list in Auckland have any late-model hermes based PCMCIA wireless networking cards, which I would borrow for a few hours today, and come and pick up fairly immediately. CBD location preferred. JSR -- John S Russell | Operations Manager | "Evil, much like good, is it's own reward." Attica/Callplus 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

early daylight saving
by Joe Abley 14 Aug '01

14 Aug '01

If daylight saving is brought forward this year, I guess we'd need a new 2001-only rule in the unix timezone database. The copy I have in my OpenBSD source tree says updates should get sent to tz(a)elsie.nci.nih.gov. Is there some standard government protocol for notifying changes in daylight-saving time to other relevant agencies, like IATA? Just interested :) Joe http://www.nzherald.co.nz/storydisplay.cfm?storyID=207726&thesection=news&t… Daylight saving idea to beat cuts 15.08.2001 By VERNON SMALL deputy political reporter An early start to daylight saving is possible if the electricity crisis deepens. The radical idea, coming as energy savings fall below the required 10 per cent, could cut power use by extending daylight into the evening peak time. A spokesman for Energy Minister Pete Hodgson said the minister had an open mind on the suggestion, put forward by one industry player. The proposal would be explored over the next two weeks, but Mr Hodgson would not say whose idea it was because the person had requested anonymity. A rough estimate by electricity market company M-Co showed an overall power reduction of 3.5 per cent in the first week of daylight saving last year. For the past three years, the reduction in the first week averaged 2 per cent. More important, in the first week of daylight saving, peak evening consumption, between 5 pm and 8 pm, dropped 7.5 per cent last year and an average of 5.5 per cent over the past three years. Peak morning demand, between 7 am and 9 am, fell by smaller amounts. "If you can keep it lighter later, the lights come on later and you save power," said M-Co's general manager of communications, Jane Tronson. Decreasing demand in peak times could also reduce potential price spikes. Act energy spokesman Gerry Eckhoff called for clocks to be put forward as early as September 1 rather than the due date of October 7. That would save power because people would eat dinner earlier and might use the barbecue instead of the electric stove, the MP said. "I guess if they sit down to dinner and watch the news at 5 pm instead of 6 pm it is still a wee bit warmer." Even a small amount of saving on lighting could accumulate across the country. There could be bigger savings in the North, where twilight lasts less time than in the South. But Federated Farmers energy spokesman Tom Lambie firmly rejected the suggestion. "We are in the busiest time of year in full flight with calving. The last thing people want to do is get up in the dark. The first daylight hours are precious for getting on with the job." A study in California, which has suffered rolling blackouts, found that daylight saving saved only small amounts of power but caused significant reductions in peak use. However, Mr Eckhoff said California had a big demand for power for air-conditioning rather than heating. The icy blast sweeping NZ from the south has caused another hiccup in the power-saving effort. Snowfalls and a cold southerly change meant savings dropped to 6.5 per cent on Monday. In the past seven days, average savings have been 9.4 per cent. However, M-Co admitted yesterday that the power saving figure published for Saturday was incorrect. The actual saving was 7.3 per cent, not 1.8 per cent as it reported. Meanwhile, one power company is trying to boost the everyone-pull-together power-saving message by offering yet another cash incentive - this time with a twist. Contact Energy, one of the four big electricity generators, which also has about 22 per cent of the retail market, will give up to $400,000 to worthy causes in regions where power consumption is cut by 10 per cent over the next month. Contact chief executive Stephen Barrett said regions must save at least 4 per cent to get any money. Those that missed the 10 per cent target but still made savings would be rewarded on a sliding scale. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Firewalling on Cisco router?
by PhoneNet 14 Aug '01

14 Aug '01

Can anyone give some suggestions on the best way to firewall a system using a Cisco router.... a friend on another list I'm on has been charged with moving a system .... some of the misfortunes he has been faced with so far are (Don't Laugh): 1.They had no list of thier machine names, 2. No IP addresses, 3. moved token ring to ethernet. 4. They had hubs, but no patch cables.... They get the Cisco router today and are moving tomorrow. Initally they will just use a very restrictive set of Cisco filters and NAT. It has bee nsuggested he use either Checkpoint or Cisco Pix, both standalone machines. Any comments? Ian Cousins PhoneNet --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Max 6000 R2 Settings
by Craig Whitmore 13 Aug '01

13 Aug '01

If anyone is kind enough to be running a Max6000 with R2, could you please send me a copy of the Settings for the E1's so they will work with R2 :-) I set up the first 4000's at IHUG on PRI's years and years ago, about I don't know the "right" settings to R2's :-( Also. if anyone has a suggestion on most stable firmware for the 6000? 7.2? 8.1? 9.0? It would be great. Sig Mode=NEW ZEALAND Switch Type=CAS Framing Mode=G.703 etc etc etc Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

4 5

Orcon Internet Updated Prefix List
by root 13 Aug '01

13 Aug '01

For those people who are Peering with Orcon Internet Please Note the Updated Prefix Lists. (210.54.56.0/21 is added from previous prefix-lists) ip prefix-list ORCON-networks description Orcon Internet <noc(a)orcon.net.nz> ip prefix-list ORCON-networks permit 202.14.20.0/22 le 24 ip prefix-list ORCON-networks permit 202.27.76.0/23 le 24 ip prefix-list ORCON-networks permit 202.27.140.0/22 le 24 ip prefix-list ORCON-networks permit 202.27.188.128/25 ip prefix-list ORCON-networks permit 210.27.250.0/24 ip prefix-list ORCON-networks permit 210.54.13.0/24 ip prefix-list ORCON-networks permit 210.54.142.0/23 le 24 ip prefix-list ORCON-networks permit 210.54.148.0/23 le 24 ip prefix-list ORCON-networks permit 210.55.8.0/24 ip prefix-list ORCON-networks permit 210.55.12.0/22 le 24 ip prefix-list ORCON-networks permit 210.55.18.0/24 ip prefix-list ORCON-networks permit 210.55.199.0/24 ip prefix-list ORCON-networks permit 210.54.56.0/21 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

2 1

Re: CLEAR Net Tempest
by Mark Foster 13 Aug '01

13 Aug '01

Well youre talking about mathematical stuff which I let go over my head years ago. :P Fair enough; I defer to those with higher skills than myself. I spose nows not a good time to mention im job hunting? :P Anyone need a Senior Helpdesk or Junior NOC type person? ... *shrug* :) Mark. At 09:55 14/08/2001 +1200, Matthew G Brown wrote: >All loss can be calculated . ( Within reason ) > >The exact frequency of the ISM band channel is avai on manafacture WWW sites. > >Cable Loss - http://www.timesmicrowave.com ( If your a LMR person ) >Connector Loss - http://www.tessco.com or http://www.timesmicrowave.com >* NB: I use Shuners conenctors over Times anyday >Insertion Loss - See Antenna manafacture > >Free Space Loss (isotropic):FSL (isotropic) = 20Log10(Frequency in MHz) + >20Log10 (Distance in Miles) + 36.6 > >Then you can check your operating margin, I run with 10db+ anything less and >you asking to get your head run over by a bare naked lady > >SOM = RX Signal Level - RX Sensitivity > >RX Signal Level = TX Power - TX Cable Loss + TX Antenna Gain - FSL + RX >Antenna Gain - RX Cable Loss > *Snip* --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Max 6000 won't Assign ip from second ip pool
by John Lynch 12 Aug '01

12 Aug '01

Hi I was wondering if any one out there has ever got the Ascend-Assign-IP-Pool radius attribute to work with a max 6000. I have just set up ip pool 2 on the max and am now trying to get an ip assigned from this new pool for a test user. I am using the radiusd-cistron 1.6.1-0.1 debian linux package for radius auth, the TAOS on the max is 9.0.0. I can login just fine but the win95 pc I am dialing in with is still assigned and ip address from pool 1. here is the debug info from radius : radrecv: Request from host ca1bd0fc code=1, id=233, length=123 User-Name = "testlynch" Password = "l\012\307\203\375\367\204\272\317\313\236\275\205f{\201" NAS-IP-Address = 202.27.208.252 NAS-Port-Id = 20202 NAS-Port-Type = Async Service-Type = Framed-User Framed-Protocol = PPP Called-Station-Id = "3700055" Acct-Session-Id = "343972952" Vendor-Specific = "V529:T197:L6::T0:L0:]\300" Vendor-Specific = "V529:T255:L6::T0:L0:\305\353" users: Matched testlynch at 51 auth: Local Sending Ack of id 233 to ca1bd0fc (nas maxbox) Service-Type = Framed-User Framed-Protocol = PPP Framed-Address = 255.255.255.254 Framed-Netmask = 255.255.255.255 Ascend-Assign-IP-Pool = 2 Ascend-Maximum-Channels = 1 Ascend-Idle-Limit = 1200 Login OK: [testlynch] (from nas maxbox/S20202) Here is the debug info from the maxbox (not the same session as above but you get the picture) : authenticating <9:testlynch> with PAP RADIF 1:49:20> _radiusRequest: id 202, user name <9:testlynch> RADIF: not sending NULL State-Attribute for VSA RADIF: not sending NULL State-Attribute for VSA RADIF: _radiusReq: socket 6 len 123 ipaddr 202.27.208.65 port 65534->1812 RADIF:_radiusReq: id 202 <9:testlynch>, starting timer (10 sec) _receivedResponse :1, addrPoolAcked : 0 RADIF: _radCallback: buf=b0aaee80 from 202.27.208.65 1812 RADIF: _radCallback, authcode = 2, id 202 RADIF: _radCallback: id 202, killing timer RADIF: Authentication Ack RADIF: vendor 0 attr 6, len 6, 00 00 00 02 RADIF: vendor 0 attr 7, len 6, 00 00 00 01 RADIF: callMgmtType set to 2. RADIF: vendor 0 attr 8, len 6, ff ff ff fe RADIF: vendor 0 attr 9, len 6, ff ff ff ff RADIF: vendor 0 attr 218, len 6, 00 00 00 02 RADIF: vendor 0 attr 235, len 6, 00 00 00 01 RADIF: vendor 0 attr 244, len 6, 00 00 04 b0 Disposing of tunnel info object b0ab8a80. RADIF:_freeInfoClassSess RADIF: radius type Acct ID = 93 RADIF:sending to 202.27.208.242 1813 _receivedResponse :1, addrPoolAcked : 0 RADIF: _radCallback: buf=b0aab400 from 202.27.208.242 1813 RADIF: _radProcAcctRsp: user:<9:testlynch>, ID=93 RADIF:_freeInfoClassSess RADIF: _radCallback: processed acct server type=0 RADIF: radius type Auth ID = 203 any help would be much appreciated. John Lynch System Administrator (string and tape specialist) Wise Net --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

2 1

NZNOG List Change Now Effective
by Donald Neal 12 Aug '01

12 Aug '01

NZNOG People, Postings for the NZNOG list should now be accepted only from addresses subscribed to one of the following lists: nznog - this list nznog-digest - the digest version of this list nznog-postonly - a list which exists only to allow addresses subscribed to it to post to the nznog list. Messages will not normally be sent to addresses subscibed to nznog-postonly. To subscribe new addresses to one or more of these lists, send email to majordomo(a)list.waikato.ac.nz where each line of the body of the message has the form subscribe <list name> to subscribe the address from which that message is being sent, or subscribe <list name> <address> to subscribe a different address. More than one subscription request may be sent in the same message. Donald Neal List Administrator --------- 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: CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi all, Sorry about the Spam, I have the displeasure of being on the end of one of these links (the mail client did not get the signoff from the smtp server so it tried again). Neil Fincham Integral LTD ----- Original Message ----- From: Olderon To: Neil Sent: Monday, August 13, 2001 4:47 PM Subject: Re: CLEAR Net Tempest is there something wrong with your mail? youve sent that same email 4times. 4:23 4:28 4:29 4:36 ----- Original Message ----- From: Neil To: nznog(a)list.waikato.ac.nz Sent: Monday, August 13, 2001 4:18 PM Subject: CLEAR Net Tempest Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0

CLEAR Net Tempest
by Neil 12 Aug '01

12 Aug '01

Hi All, Has anyone else had any problems with Clear's 802.11 wireless internet service (http://www.clear.net.nz/services/tempest.html) as a source of interference? They have just done a rollout in Rotorua and totally stoped 3 separate wireless networks that had been running together nicely for the past year or two. Clear have told me that Rotorua is the only place that this has happened in and are being very slow to do anything about it so if this has happened to you could you let me know. Neil Fincham Integral LTD.

1 0

Code red logging
by Simon Byrnand 12 Aug '01

12 Aug '01

Thought those of you playing Code Red Detective may find the following URL of some use :) http://salfter.dyndns.org/codered.shtml Regards, Simon --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

Abuse@xtra.co.nz now guilty of abuse?
by PhoneNet 11 Aug '01

11 Aug '01

If anyone at Xtra is reading this list please get them to fix the autoresponder for messages to abuse(a)xtra.co.nz... I've now had 5 identical replies over a period of 3 days to my complaint re spam.... Perhaps they think they are supposed to be the abusers? Ian Cousins PhoneNet --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Fwd: Code red infected customers
by Steve Phillips 10 Aug '01

10 Aug '01

FYI, these are the IP's I've collected to date that are in the NZ domain, some of these will be on dynamic dialup accounts, if you would like the actual log entries which should include times they were online let me know, i'll probably clear off the log files and restart the collection at a later date as the time on the server was out by an hour <self fwap> >Date: Sat, 11 Aug 2001 18:57:54 +1200 >From: root <root(a)hangover.nz.asiaonline.net> >To: steve(a)nz.asiaonline.net >Subject: Code red infected customers > >Code Red Infected customers on our network trying to infect remote sites.. > > >202.154.128.18 : 18.128.154.202.IN-ADDR.ARPA domain name pointer >ak-d18.connections.net.nz >202.180.111.174 : 174.111.180.202.IN-ADDR.ARPA domain name pointer >202-180-111-174.nas3.chc.attica.net.nz >202.180.111.18 : 18.111.180.202.IN-ADDR.ARPA domain name pointer >202-180-111-18.nas3.chc.attica.net.nz >202.180.111.77 : 77.111.180.202.IN-ADDR.ARPA domain name pointer >202-180-111-77.nas3.chc.attica.net.nz >202.180.111.95 : 95.111.180.202.IN-ADDR.ARPA domain name pointer >202-180-111-95.nas3.chc.attica.net.nz >202.180.68.127 : 127.68.180.202.IN-ADDR.ARPA domain name pointer >202-180-68-127.nas1.wgn.attica.net.nz >202.180.68.40 : 40.68.180.202.IN-ADDR.ARPA domain name pointer >202-180-68-40.nas1.wgn.attica.net.nz >202.180.69.248 : 248.69.180.202.IN-ADDR.ARPA domain name pointer >202-180-69-248.ipn1.attica.net.nz >202.180.71.36 : 36.71.180.202.IN-ADDR.ARPA domain name pointer >202-180-71-36.nas4.akl.attica.net.nz >202.180.90.163 : 163.90.180.202.IN-ADDR.ARPA domain name pointer >202-180-90-163.nas7.akl.attica.net.nz >202.37.167.38 : 38.167.37.202.IN-ADDR.ARPA domain name pointer >nwp-38.world-net.co.nz >202.37.68.193 : 193.68.37.202.IN-ADDR.ARPA domain name pointer >nw3-193.world-net.co.nz >202.49.144.221 : 221.144.49.202.IN-ADDR.ARPA domain name pointer >storefrontmail.viatx.com >202.49.144.225 : 225.144.49.202.IN-ADDR.ARPA domain name pointer >stage.viatx.com >202.50.111.114 : >202.50.111.91 : >202.50.111.97 : >203.109.193.163 : 163.193.109.203.IN-ADDR.ARPA domain name pointer >203-109-193-163.ihug.net >203.109.203.103 : 103.203.109.203.IN-ADDR.ARPA domain name pointer >203-109-203-103.nzl.ihugultra.co.nz >203.167.132.64 : 64.132.167.203.IN-ADDR.ARPA domain name pointer >203-167-132-64.dialup.clear.net.nz >203.167.161.144 : 144.161.167.203.IN-ADDR.ARPA domain name pointer >203-167-161-144.dialup.clear.net.nz >203.167.164.208 : 208.164.167.203.IN-ADDR.ARPA domain name pointer >203-167-164-208.dialup.clear.net.nz >203.167.166.71 : 71.166.167.203.IN-ADDR.ARPA domain name pointer >203-167-166-71.dialup.clear.net.nz >203.167.171.155 : 155.171.167.203.IN-ADDR.ARPA domain name pointer >203-167-171-155.dialup.clear.net.nz >203.167.214.50 : >203.167.247.214 : 214.247.167.203.IN-ADDR.ARPA domain name pointer >cf4-acld.auckland.clix.net.nz >203.167.254.136 : 136.254.167.203.IN-ADDR.ARPA domain name pointer >napr-m36.dialup.inhb.co.nz >203.79.102.72 : 72.102.79.203.IN-ADDR.ARPA domain name pointer >203-79-102-72.tnt14.paradise.net.nz >203.79.103.179 : 179.103.79.203.IN-ADDR.ARPA domain name pointer >203-79-103-179.tnt14.paradise.net.nz >203.96.106.59 : 59.106.96.203.IN-ADDR.ARPA domain name pointer >203-96-106-59.dialup.xtra.co.nz >203.96.110.172 : 172.110.96.203.IN-ADDR.ARPA domain name pointer >203-96-110-172.dialup.xtra.co.nz >203.96.110.66 : 66.110.96.203.IN-ADDR.ARPA domain name pointer >203-96-110-66.dialup.xtra.co.nz >203.96.62.201 : 201.62.96.203.IN-ADDR.ARPA domain name pointer >203-96-62-201-tollfree.actrix.co.nz >203.96.62.53 : 53.62.96.203.IN-ADDR.ARPA domain name pointer >203-96-62-53-tollfree.actrix.co.nz >203.97.85.108 : 108.85.97.203.IN-ADDR.ARPA domain name pointer >a004-m001-u108.chch.clear.net.nz >210.48.102.170 : 170.102.48.210.IN-ADDR.ARPA domain name pointer >ip-210-48-102-170.iconz.net.nz >210.48.103.150 : 150.103.48.210.IN-ADDR.ARPA domain name pointer >ip-210-48-103-150.iconz.net.nz >210.48.103.4 : 4.103.48.210.IN-ADDR.ARPA domain name pointer >ip-210-48-103-4.iconz.net.nz >210.48.81.19 : 19.81.48.210.IN-ADDR.ARPA domain name pointer >p19.pool1.staticadsl.iconz.net.nz >210.54.121.65 : 65.121.54.210.IN-ADDR.ARPA domain name pointer >210-54-121-65.adsl.xtra.co.nz >210.54.199.115 : 115.199.54.210.IN-ADDR.ARPA domain name pointer >210-54-199-115.dialup.xtra.co.nz >210.54.201.186 : 186.201.54.210.IN-ADDR.ARPA domain name pointer >210-54-201-186.dialup.xtra.co.nz >210.54.201.49 : 49.201.54.210.IN-ADDR.ARPA domain name pointer >210-54-201-49.dialup.xtra.co.nz >210.54.217.216 : 216.217.54.210.IN-ADDR.ARPA domain name pointer >ppp-15.satlan.co.nz >210.54.221.186 : 186.221.54.210.IN-ADDR.ARPA domain name pointer >210-54-221-186.ipnets.xtra.co.nz >210.54.221.194 : 194.221.54.210.IN-ADDR.ARPA domain name pointer >210-54-221-194.ipnets.xtra.co.nz >210.54.224.235 : 235.224.54.210.IN-ADDR.ARPA domain name pointer >210-54-224-235.adsl.xtra.co.nz >210.54.229.174 : 174.229.54.210.IN-ADDR.ARPA domain name pointer >210-54-229-174.dialup.xtra.co.nz >210.54.233.174 : 174.233.54.210.IN-ADDR.ARPA domain name pointer >210-54-233-174.adsl.xtra.co.nz >210.54.242.194 : 194.242.54.210.IN-ADDR.ARPA domain name pointer >210-54-242-194.adsl.xtra.co.nz >210.54.247.251 : 251.247.54.210.IN-ADDR.ARPA domain name pointer >smtp.carolineeve.co.nz >210.54.254.97 : 97.254.54.210.IN-ADDR.ARPA domain name pointer >210-54-254-97.adsl.xtra.co.nz >210.54.76.237 : 237.76.54.210.IN-ADDR.ARPA domain name pointer >210-54-76-237.dialup.xtra.co.nz >210.54.77.98 : 98.77.54.210.IN-ADDR.ARPA domain name pointer >210-54-77-98.dialup.xtra.co.nz >210.54.80.49 : 49.80.54.210.IN-ADDR.ARPA domain name pointer >210-54-80-49.adsl.xtra.co.nz >210.54.80.78 : 78.80.54.210.IN-ADDR.ARPA domain name pointer >210-54-80-78.adsl.xtra.co.nz >210.54.8.148 : >210.54.83.179 : 179.83.54.210.IN-ADDR.ARPA domain name pointer >210-54-83-179.adsl.xtra.co.nz >210.54.84.137 : 137.84.54.210.IN-ADDR.ARPA domain name pointer >210-54-84-137.adsl.xtra.co.nz >210.54.84.211 : 211.84.54.210.IN-ADDR.ARPA domain name pointer >210-54-84-211.adsl.xtra.co.nz >210.54.89.14 : 14.89.54.210.IN-ADDR.ARPA domain name pointer >smtp.insteplimited.com >14.89.54.210.IN-ADDR.ARPA domain name pointer smtp.hanmerinstitute.com >210.54.98.43 : 43.98.54.210.IN-ADDR.ARPA domain name pointer >210-54-98-43.dialup.xtra.co.nz >210.54.99.167 : 167.99.54.210.IN-ADDR.ARPA domain name pointer >210-54-99-167.dialup.xtra.co.nz >210.55.103.213 : 213.103.55.210.IN-ADDR.ARPA domain name pointer >port55-103-213.jetstart.win.co.nz >210.55.106.10 : 10.106.55.210.IN-ADDR.ARPA domain name pointer >ip210-55-106-10.ip.maxnet.co.nz >210.55.106.136 : 136.106.55.210.IN-ADDR.ARPA domain name pointer >ip210-55-106-136.ip.maxnet.co.nz >210.55.123.35 : 35.123.55.210.IN-ADDR.ARPA domain name pointer >210-55-123-35.dialup.xtra.co.nz >210.55.146.39 : 39.146.55.210.IN-ADDR.ARPA domain name pointer >210-55-146-39.dialup.xtra.co.nz >210.55.146.83 : 83.146.55.210.IN-ADDR.ARPA domain name pointer >210-55-146-83.dialup.xtra.co.nz >210.55.159.221 : 221.159.55.210.IN-ADDR.ARPA domain name pointer >210-55-159-221.ipnets.xtra.co.nz >210.55.159.222 : 222.159.55.210.IN-ADDR.ARPA domain name pointer >210-55-159-222.ipnets.xtra.co.nz >210.55.178.166 : 166.178.55.210.IN-ADDR.ARPA domain name pointer >210-55-178-166.dialup.xtra.co.nz >210.55.228.173 : 173.228.55.210.IN-ADDR.ARPA domain name pointer >adsl-173.world-net.co.nz >210.55.57.45 : 45.57.55.210.IN-ADDR.ARPA domain name pointer >210-55-57-45.adsl.xtra.co.nz >210.55.9.105 : >210.86.24.203 : 203.24.86.210.IN-ADDR.ARPA domain name pointer >210-86-24-203.adsl.xtra.co.nz >210.86.24.254 : 254.24.86.210.IN-ADDR.ARPA domain name pointer >210-86-24-254.adsl.xtra.co.nz >210.86.25.142 : 142.25.86.210.IN-ADDR.ARPA domain name pointer >210-86-25-142.adsl.xtra.co.nz > >Total customers Code Red infected so far counted at : 79 -- Steve Systems Admin, Asia Online (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

Code Red errata
by Brodie Davis 09 Aug '01

09 Aug '01

Has any one else noticed a big drop of traffic related to this. my stats for this week have been so far (pretty low.. but as i only have 2 world viewable port 80's) Monday : 37 (ids was playing up so only partial records) Tuesday : 599 Wednesyday : 511 Today (from 8am) : nill I am just wondering is this the norm.. or I am just lucky. (or has AoL started filting this now?) Cheers, Brodie --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 10

Vote Result and NZNOG List Changes
by Donald Neal 09 Aug '01

09 Aug '01

NZNOG People, Voting has now closed on the following proposed addition to this list's acceptable use policy: 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. A total of seventy votes were recieved, with all votes cast in favour of the change. This change is therefore now in effect. During the afternoon of Monday, 13 August, I intend to change the nznog list's settings so that postings will be accepted only from addresses subscribed to one of the following lists: nznog - this list nznog-digest - the digest version of this list nznog-postonly - a new list which exists only to allow addresses subscribed to it to post to the nznog list. Messages will not normally be sent to addresses subscibed to nznog-postonly. To subscribe new addresses to one or more of these lists, send email to majordomo(a)list.waikato.ac.nz where each line of the body of the message has the form subscribe <list name> to subscribe the address from which that message is being sent, or subscribe <list name> <address> to subscribe a different address. More than one subscription request may be sent in the same message. Donald Neal List Administrator --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Given the current topic of discussion in here...
by Chris Rigby 09 Aug '01

09 Aug '01

I though this slashdot article might be on interest. http://slashdot.org/articles/01/08/09/1758200.shtml 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

1 0

[OT] 802.11 and stuff
by James Tyson 08 Aug '01

08 Aug '01

Hi all Just a couple of quick questions to you folks that know so much about 802.11. Firstly, do I really need a base station? I have my new ibook here and I want to grab the airport card to use with the Cisco Aironet base station at work, but I was thinking is it possible to just throw an orinoco card or something in my Linux box gateway and use that in place of a base station while I am at home? If not, does anyone know of any base stations in the sub $500 range that work reasonably? I am not really that worried about WEP and SSID while I am at home, because I will set my DHCP server up to only assign my card an IP address and use an encrypted tunnel to get to the net. 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

8 9

Looking for DialUp RAS Equipment
by Craig Whitmore 08 Aug '01

08 Aug '01

Has anyone got any Spare RAS Equipment they are willing to sell Such as: Cisco 5200/5300/5800 etc (Or Modem Cards to put in them) USR/3Com TotalControl Equipment (or any Cards for the Chassis such as netserver/Quads etc) Shiva LANRover (Whole thing or Spare Modems etc) Max Ascend 4000/6000/3000/TNT? Anything else that will take R2's and work reasonable. If you have any of the above please let me know with estimated price for Sale. Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

2 1

Re: Code Red errata
by Steve Phillips 08 Aug '01

08 Aug '01

At 11:20 9/08/2001, James McGlinn wrote: >Is it possible to filter on part of the shell code payload? At least one >CR variant doesn't request default.ida - rendering it useless (I assume), >but that should let you see those hits, and allow genuine default.ida >requests through... yep, the way the filter works is you can enter any string up to 32 characters in length, I used default.ida as it was easier to type, once i had it working and had tested it I was going to parse it on the shell code string :) -- Steve Systems Admin, Asia Online (NZ) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: Proposed Change to Acceptable Use Policy
by Donald Neal 08 Aug '01

08 Aug '01

NZNOG People, Voting is now under way on the following proposed addition to the list''s acceptable use policy. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Votes on this change to me (not the list!) by midday tomorrow, Friday 10 August, please. I have so far received fifty-eight votes, and have acknowledged all of them. If you have not received email saying your vote has been recorded, it is not likely that it has been recorded. My access to email between now and some time tomorrow morning may be little variable, as I am engaged in moving offices. This is therefore likely to be the last reminder of the vote. If the change is approved, I intend to make the changes necessary to restrict posting to pre-submitted addresses only on Monday, 13 August. Donald Neal List Administrator --------- 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: Proposed Change to Acceptable Use Policy
by Donald Neal 07 Aug '01

07 Aug '01

NZNOG People, Voting is now under way on the following proposed addition to the list''s acceptable use policy. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Votes on this change to me (not the list!) by midday, Friday 10 August, please. I have so far received thirty votes, and have acknowledged all of them. If you have not received email saying your vote has been recorded, it is not likely that it has been recorded. 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

spammer
by Michael Coates 07 Aug '01

07 Aug '01

Hello Is there a list in NZ I can get a spammer put onto to block them from sending emails with viruses attached? Thanks

3 2

Code Red Stats
by Craig Whitmore 07 Aug '01

07 Aug '01

I've been running a running couter of hits on 1 machine take logs from 500 IP addresses's (2 C Classes). Its Hits/sec has gone up from yesterday from about 3.4->6.9 and growing fast :-( Total Seconds = 8878 Total Unique Machines Infected = 6380 Total Hits = 51169 Total Hits/Sec = 6.89 Also I have it emailing the owners of the Unique IP addresses (automaticlly) (with an ugly script) and telling that their machines are infected and so far have had many happy people repling thanking me. (But the Number of infected machines still increases :-( ) This is only from 2 C Class Addresses.. I can't imagine how many hits/sec NZ is getting in Total from Overseas.. There have only been a few infected machines from inside NZ (mostly from Xtra and WorldNet Dialups) Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

1 0

TCP Header Definition help request "Window"
by Mike Sutton [ awacs ] 07 Aug '01

07 Aug '01

TCP Header Could an expert tell me "how" the "window" value is generated and "what" explicitly it means... Appreciate your help as my reference books don't help and I have not been able to locate a precise definition on the Net. Michael Sutton --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 7

root.exe
by Dylan Reeve 07 Aug '01

07 Aug '01

Any ISPs had a look through their proxy logs for "root.exe" or "cmd.exe" so far? I bet there will be a few... Going to go after people for 'hacking'? -- Dylan Reeve - dylan(a)wibble.net "Um, yeah." --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Code Red: NZ vs Canada
by Dan Langille 06 Aug '01

06 Aug '01

I can give you two lots of stats, one from a NZ server, the other from a Canada server: http://www.langille.org/stats-red-worm/ - in Wellington http://www.freebsddiary.org/stats-red-worm/ - in Ottawa Both are updated every 30 minutes, 15 minutes after and after the hour. -- Dan Langille pgpkey - finger dan(a)unixathome.org | http://unixathome.org/finger.php --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 5

Whazzup w/ Ihug?
by Juha Saarinen 06 Aug '01

06 Aug '01

http://www.internettrafficreport.com/cgi-bin/tr_chartpage.pl?203.98.56.1 70 -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 5

Re: Code Red Weirdness
by Mark Foster 06 Aug '01

06 Aug '01

[Tue Aug 7 13:56:39 2001] [error] [client 203.199.60.10] Invalid URI in request XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXX%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u9090%u8190%u00c3%u0003%u 8b00%u531b%u53ff%u0078%u0000%u00=a HTTP/1.0 Ive had just one today, in the last half hour. None prior to that Did someone try to write a variant and screw up or maybe one of the infectees got weird? At 13:58 7/08/2001 +1200, you wrote: >[Tue Aug 7 13:57:14 2001] [error] [client 203.228.144.15] Invalid URI in >request >XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX%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 started getting these. no default.ida?. > >Has the worm turned, again? > > >Tim J. Shackleton ------------------+ +- Business http://www.netlink.co.nz/ >Networks Admin/Programmer ----------+ +- Personal http://www.netnet.net.nz/ >Netlink LTD -- DDI +64 4 922 8476 --+ +------------- Pager 64 +26 253 4356 >+64 29 650 476 -- Cellular ---------+ +------------------------------------ >---- "Cold silence has a tendency to atrophy any sense of compassion" ----- > >--------- >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

5 4

Code Red Stats
by Neil 06 Aug '01

06 Aug '01

Hi All, After about 30 second's of thinking about how to get rrdtool or mrgt to display what Code Red is up to on my server I decided to use webalizer instead. It defiantly gives you a better view on what is going on, have a look at http://203.97.86.130/codered/usage_200108.html . I have put the script in the cron.hourly directory so check back as often as you like. Neil Fincham Integral LTD.

6 8

Re: Code Red - Network Impact?
by Mark Davies 06 Aug '01

06 Aug '01

From: "Barry Raveendran Greene" <bgreene(a)cisco.com> Date: Mon, 6 Aug 2001 05:18:53 -0700 > Is anyone seeing router impact caused by all the bogus queries sent out by > Code Red? Just wondering if there could be some side effects. We had the cpu running at 100% on our border router till we tuned the access-lists to deal with traffic to port 80 early. cheers mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

Internet issues for discussion at APEC TEL24
by Frank March 06 Aug '01

06 Aug '01

I have previously posted information about APEC TEL24 to this list inviting people to join the NZ delegation. As a reminder: the meeting will take place 19-21 September in Jeju, Korea. It will be preceeded by two days (17,18 September) of workshops on various areas. I will be there for all five days. Details at http://www.apectel24.org/. Please feel free to pass the contents of this email on to anyone you think may be interested. One workshop area is 'Internet issues'. The first draft of the programme is as follows. I invite anyone to send to me **(off-line)** comments about any of the matters mentioned. Note that this was the first forum to raise the issue of international Internet charging (and that matter is still hanging around). There is an invitation to comment on agenda matters and I will probably take that up in 10 days or so. >From the organisers..... "The Workshop will consist of two parts. The FIRST part will consist of three presentations (20 minutes each) about the following topics: 1.- Presentation about the Current State of the Debate on Internet Issues. 2.- Presentation about the development of traffic flows within and between Latin American countries and other regions. 3.- Presentation about the situation of small ISP's in the Asia-Pacific region. The SECOND part will consist of an open-floor moderated discussion between the delegates. We suggest the following topics. Please we will appreciate if you could indicate your first three issues of more interest: 1.- APEC Contribution to promoting Internet access in the Asia-Pacific Region 2.- Traffic Exchange Models (Current and Next Generation) How is Internet traffic exchanged? What financial mechanisms are in place for the exchange of Internet traffic and how are they encouraging Internet development? What are the trends in content location and how do these factors influence Internet traffic patterns and financial arrangements? 3.- Global Capacity Availability and Trading What are the recent developments in large-scale bandwidth provision? What are the recent developments in retail internet service provision? How do global capacity relate to Internet traffic exchange? 4.- Local Internet Interconnection What are the main principles of the new interconnection frameworks? How much progress has been made in developing interconnection frameworks appropriate to the exchange of Internet traffic? 5.- Role for Regulators Is there a role for regulators? What are the policy implications for some of the directions Internet traffic exchange will take with next generation Internet architecture? 6.- Users Needs How do users view current developments in Internet traffic exchange? How does the financial community view the current state of play? User Needs - IP-based services and content providers. 7.- WTO What is the current state of the debate? How negotiating frameworks from different countries compare? What is the treatment of Internet services in the negotiating frameworks? 8.- Internet Connectivity What policy and regulatory reforms are required to stimulate Internet development and address the international digital divide? What regulatory barriers exist to the development of the Internet including infrastructures such as international connectivity, domestic teledensity and Internet exchange points? How can economies maximise the benefits of their Internet development including lower costs for infrastructure service? (development funds) 9.- Costs and Prices What is going to replace the international settlements system in the new environment? How are countries adapting to the changes in settlement rates? 10.- Quality Voice over IP " 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 --------- 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: Code Red - Network Impact?
by Mark Davies 06 Aug '01

06 Aug '01

From: Chris Wedgwood <cw(a)f00f.org> Date: Tue, 7 Aug 2001 11:15:46 +1200 > What IOS version? Are you running compiled ACLs? Don't know, no. Its not actually my box I just get to look at it occasionally when they have issues. > That seems to help a > fair bit if your CPU bound due to access-list activity. I just looked up the docs on compiled access-lists and the reference I found implied that they were only available on 7200's and bigger boxes. > Also, you can > try "show access-list blah" and reorder the most frequent terms to > nearer the top. I've cleaned the lists up several times in the past (as well as they could be) but they keep adding more ugliness to them. cheers mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Code Red - Network Impact?
by Barry Raveendran Greene 06 Aug '01

06 Aug '01

Hi Folks, Is anyone seeing router impact caused by all the bogus queries sent out by Code Red? Just wondering if there could be some side effects. Barry --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 5

Re: Code Red - Network Impact?
by Mark Davies 06 Aug '01

06 Aug '01

From: Chris Wedgwood <cw(a)f00f.org> Date: Tue, 7 Aug 2001 10:46:27 +1200 > On Tue, Aug 07, 2001 at 10:36:51AM +1200, Mark Davies wrote: > We had the cpu running at 100% on our border router till we tuned > the access-lists to deal with traffic to port 80 early. > Ouch... what kind of router? Where was all the CPU being spent? A cisco 2600 with a rather ugly set of access-lists having to deal with the probes for an entire Class B net. I was somewhat surprised that it couldn't deal with it as it was only about 100 probes a second (this was last Friday). Tweaking the access-lists got the load down to about 40-50%. cheers mark --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

RE: Code Red V3!?
by Lindsay Druett 06 Aug '01

06 Aug '01

You must be a Bob Jones Fan.... "Location, location, location...." Those poor souls that are topologically near NT servers that have been infected are getting hammered :/ If you're getting hammered, you live in a bad neighbourhood, time to cleanup or move :) --------- 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: NZIX is gone!
by Rob Edkins 06 Aug '01

06 Aug '01

Arron wrote: > Them were the glory days ... New Zealand's routing table in IGRP (no not EIGRP), 24 routers connected via Coax and a 1.5Mbps Frame Relay link to the US.< ...and you tell the kids today that, and they doooooon't believe yer! ;-) Rob __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZIX is gone !!!
by Lindsay Druett 05 Aug '01

05 Aug '01

Hi, As of 10:45am this morning the last router (HNCR1) was turned off, and by 11:45am NZIX (as far as University of Waikato is concerned) has been fully dismantled. As most providers most providers have stopped peering with NZIX late last year, I thought it would be worth making note that as of this morning, NZIX is now part of New Zealand internet's history books, and is no longer in existence. Kind Regards, Lindsay. Lindsay Druett, CCNA, CCDA, NZTC (Elect.) Network Engineer, Network and Development, Information and Technology Services, University of Waikato, Hamilton, New Zealand. lindsayd(a)waikato.ac.nz Phone 64-7-838 4999 Fax 64-7-838 4416 Mobile 025-276 0700 <<Lindsay Druett.vcf>>

3 2

Wellington 2
by Dean Pemberton 05 Aug '01

05 Aug '01

Well wellington wasn't so dead afterall. Turns out that all we needed as a 1.5 metre tall whip antenna bolted to the top of Simon Blakes car. Yes we have photos I'll get them developed when I get back to Oz. Dean --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 20

smtp.xtra.co.nz --- sick?
by Chris Wedgwood 05 Aug '01

05 Aug '01

I'm seeing funnies to smtp.xtra.co.nz --- basically some connections when sending email are terribly slow, while others work perfectly well. Does anyone know if this address is a load-balancer or something? If that's the case then it might be a host behind it is a bit sick or something... I'm seeing 10 second delays or more between having received a TCP ACK and getting an SMTP ACK back. The helpdesk didn't seem too interested, I didn't even ask if they wanted to see my packet dumps[1] :) --cw [1] Another outstanding pickup line. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Code Red V3!?
by Mark Foster 05 Aug '01

05 Aug '01

http://www.idg.net.nz/webhome.nsf/UNID/3B65B7D06B08DB2DCC256AA00001AF76!ope… -.-. --.- Mark Foster - markf(a)intermech.co.nz IT Manager, Intermech Ltd +64-21-499-368 / +64-9-525-2220 http://www.intermech.co.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: NZIX is gone !!!
by Lindsay Druett 05 Aug '01

05 Aug '01

John Houlker will be touched... Everybody should turn off all their routers for a minute, as a mark of resepect. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Different Code Red?
by Juha Saarinen 05 Aug '01

05 Aug '01

I'm getting lots of hits on my home box, unfortunately. 142 since August 1 is the latest count. :-( Noticed that the GET requests look different now: 203.231.234.229 - - [05/Aug/2001:11:46:35 +1200] "GET /default.ida?XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXX%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9 090%u6858%ucbd3%u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531b%u53ff%u0 078%u0000%u00=a HTTP/1.0" 404 283 "-" "-" Whereas earlier on, they looked like this: 65.192.84.7 - - [05/Aug/2001:06:51:26 +1200] "GET /default.ida?NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNN%u9090%u68 58%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u90 90%u8190%u00c3%u0003%u8b00% u531b%u53ff%u0078%u0000%u00=a HTTP/1.0" 400 330 "-" "-" -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

15 27

idg.net.nz --- IMHO privacy implications of archives are debatable (Paul Brislen)
by Chris Wedgwood 04 Aug '01

04 Aug '01

In light of recent comments WRT a certain IDG article I find: http://www.idg.net.nz/webhome.nsf/UNID/EA33E2992D04A5C0CC256A9E0010FACC!ope… Ah, internet. Bane and boon of my life. What would I do without you, dear old friend? Well, for a start, I wouldn't be following a language tutor's advice quite so often. He told me there are two steps to learning a foreign language. Step one: open mouth. Step two: insert foot. [...] Most entertaining of all, however, is that when I rewrote the story for Computerworld it changed the story as it appears on the web. The old version ("Newsgroups could be breaching privacy act") was effectively replaced with a new one ("Privacy issue over mailing list archives") in a single Orwellian moment. Ironic, really, when you consider the story in the first place was triggered by a question about whether an archive could or should be changed to remove old postings. Pretty reasonable comments this time, certainly worth reading. --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

Globe.NET (www.globe.net.nz) Mail Server full
by Craig Whitmore 04 Aug '01

04 Aug '01

If anyone has any contacts for Globe.NET (www.globe.net.nz) (I've tried their 0508 number and no answer) can you please contact them and tell them that their mail server has no space left on its Disk. Thanks Craig Whitmore Orcon Internet http://www.orcon.net.nz

1 0

CodeRed Worm Stats
by Brian Gibbons 04 Aug '01

04 Aug '01

>From: Craig Whitmore >I just did some graphs of the codered worms attacking over today.. and have a look at >http://www.nzdsl.co.nz/codered >Anyone got any similar stats?? Similar stats from one of our boxes that does nothing all day except ignore ARP broadcasts on it's LAN segment. http://www.outersite.co.nz/codered.html This is probably ho hum for many, however I pity those that pay per MB. At NZ retail rates a box infected with CodeRed could easily burn bandwidth at $300 per hour, fairly scary to come back Monday to find your box has burnt $15,000 over the weekend. BG --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Increase in Code Red activity?
by Brian Gibbons 04 Aug '01

04 Aug '01

We have noticed a large increase (10 fold) in CodeRed activity since bang on midnight last night. The probe rate seems to have now leveled off at one probe per IP address every three minutes. This activity was actually noticed from monitoring of broadcast traffic on an ethernet LAN (TCP SYN to Black hole LAN IP address). If WorldNet are listening, these two systems are hitting us regularly 210.55.74.165 210.55.76.51 Cheers BG. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

CodeRed Worm Stats
by Craig Whitmore 04 Aug '01

04 Aug '01

I just did some graphs of the codered worms attacking over today.. and have a look at http://www.nzdsl.co.nz/codered The last batch of attacks started about 11pm last night.. This is from 2 completely different networks in NZ and the results where about the Same The 1st graph is 1 Machine only and the 2nd Graph is a C Class. Pretty Scary.. Anyone got any similar stats?? The worse offenders are a couple of machines @ worldnet so far. Thanks Craig Whitmore Orcon Internet http://www.nzdsl.co.nz

1 0

FW: Alert: New version of Code Red, XXXX
by Chris Woodrow 04 Aug '01

04 Aug '01

Cross posted from the NTBugtraq list -----Original Message----- From: Russ [mailto:Russ.Cooper(a)RC.ON.CA] Sent: Sunday, 5 August 2001 3:48 p.m. To: NTBUGTRAQ(a)LISTSERV.NTBUGTRAQ.COM Subject: Alert: New version of Code Red, XXXX -----BEGIN PGP SIGNED MESSAGE----- Just a quick FYI, there is a new version of Code Red which appears to be spreading rather rapidly. - - Appears to be a new re-write. - - Drops some sort of remote access trojan. - - Turns off System File Checker (Windows File Protection.) - - Moves CMD.EXE to the scripts directory in IIS - - Looks like the way they make the entry into code very differently than before. - - If your IDS is looking for "NNNN", forget it (but then you should have been shot if you used this string anyway) Cheers, Russ - Surgeon General of TruSecure Corporation/NTBugtraq Editor p.s. if we don't respond right away its because we're now going to go and light the fireworks here at my retreat. Might as well have lots of fireworks tonight! -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.2 iQCVAwUBO2zCARBh2Kw/l7p5AQH95wQAqjGp7vRYK8SYky/ydyU1wxBmCe2c8Mpd DBdxrv+TY9112ZuH663ZspUOXThS9oeEyT4sdbVYNv8Z28nMipbioyTXYa5dw8po 21tkilo6ZoGX+AmKJ6Kz7WDvMpHpEfzDr3JHGtxuev0/rclXeRSN4urypMR3YnRz uw5ZW/F3U/I= =OhCV -----END PGP SIGNATURE----- ---------------------------------------------------------------------------- Delivery co-sponsored by Trend Micro ============================================================================ TREND MICRO REAL-TIME VIRUS ALERTS If you would like to know about a virus outbreak before CNN and ZDNet get Trend Micro Virus Info Feed FREE. Simply copy and paste a small piece of code to give your visitors a real-time top 10 list and the latest virus advisories. Setup takes just 10 minutes and requires no server-side code on your Web site. All content is updated automatically from Trend Micro's Web site. http://www.antivirus.com/banners/tracking.asp?si=8&bi=237&ul=/syndication/ vinfo/ ---------------------------------------------------------------------------- --------- 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: Different Code Red?
by Thomas Salmen 04 Aug '01

04 Aug '01

For those who havn't seen yet - -----BEGIN PGP SIGNED MESSAGE----- Just a quick FYI, there is a new version of Code Red which appears to be spreading rather rapidly. - - Appears to be a new re-write. - - Drops some sort of remote access trojan. - - Turns off System File Checker (Windows File Protection.) - - Moves CMD.EXE to the scripts directory in IIS - - Looks like the way they make the entry into code very differently than before. - - If your IDS is looking for "NNNN", forget it (but then you should have been shot if you used this string anyway) Cheers, Russ - Surgeon General of TruSecure Corporation/NTBugtraq Editor p.s. if we don't respond right away its because we're now going to go and light the fireworks here at my retreat. Might as well have lots of fireworks tonight! -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.2 iQCVAwUBO2zCARBh2Kw/l7p5AQH95wQAqjGp7vRYK8SYky/ydyU1wxBmCe2c8Mpd DBdxrv+TY9112ZuH663ZspUOXThS9oeEyT4sdbVYNv8Z28nMipbioyTXYa5dw8po 21tkilo6ZoGX+AmKJ6Kz7WDvMpHpEfzDr3JHGtxuev0/rclXeRSN4urypMR3YnRz uw5ZW/F3U/I= =OhCV -----END PGP SIGNATURE----- Quite exciting really, isn't it? Regards, Thomas Salmen System Administrator Radionet Ltd. 1/72 Paul Matthews Road Albany, Auckland, New Zealand Ph: +64 9 414 0300 ext 718 -----Original Message----- From: Dan Langille [mailto:dan(a)langille.org] Sent: Sunday, 5 August 2001 4:00 p.m. To: Juha Saarinen Cc: nznog(a)list.waikato.ac.nz Subject: Re: Different Code Red? On 5 Aug 2001, at 11:53, Juha Saarinen wrote: > I'm getting lots of hits on my home box, unfortunately. 142 since August > 1 is the latest count. :-( > > Noticed that the GET requests look different now: [snip] Some look different: [dan(a)dev:/var/log] $ grep -c "default.ida?X" /var/log/httpd-access.log 12 [dan(a)dev:/var/log] $ grep -c "default.ida?N" /var/log/httpd-access.log 116 [dan(a)dev:/var/log] $ grep -c "default.ida" /var/log/httpd-access.log 128 The above represents the last 24 hours EST. All hits were against the IP address, not against any known domain (i.e. the HTTP headers did not include a domain name). -- Dan Langille pgpkey - finger dan(a)unixathome.org | http://unixathome.org/finger.php --------- 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

Code Red v. II
by Juha Saarinen 03 Aug '01

03 Aug '01

Arrghhh... three times as many hits: pts/0 juha(a)vimfuego:/mnt/hdb6/home/juha$ grep -c default.ida /var/log/httpd/access_log 54 -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

The Wellington Wander
by Dean Pemberton 02 Aug '01

02 Aug '01

Ok the numbers are in. Wellington scored much less usage on the wireless front Well less on the 'being able to pick up with a dinky antenna on the sidewalk' front I happen to know for certain that there are wireless stations out there that I missed Wellington seems to have a few hot spots rather than a general level of wireless. It does score higher on the security side though. Of the 17 networks that I saw, 9 were using WEP The ones that weren't however did try valiantly to give me IP addresses and invite me onto their networks. This kinda freaked me out (this is not an intrusion attempt remember) so I ended up disabling all protocols on that interface In the spirit of Tim Allen I think I need more power. So I'm on the lookout for a larger antenna, and I think I know just the place to get one on loan =) Later Dean --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 8

Re: Dean's Wireless Walkabout
by Dean Pemberton 02 Aug '01

02 Aug '01

HAHAHAHA ROFLMAO Choccie Fish for Joe here. Yes of course I mean 802.11 hahaha - I'm still laughing at that cock up. So how many people were worried that I could see their Vlans from the street? Dean On Wed, Aug 01, 2001 at 10:48:38PM +1200, Joe Lewis wrote: > > Hi, umm feel free to shoot me down but don't you mean 802.11(b)? > > --- > Joe Lewis > > On Wed, 1 Aug 2001, Dean Pemberton wrote: > > > > > Hi all; > > > > Yes this might be a first, I'm going to drag the topic BACK to something network related. > > > > I happen to be in Auckland today. Flew in for customer chit chat which will happen tommorow. > > Had a spare afternoon and no one to see so I thought I might do the geek thing and see how little old Auckland was getting along with it's wireless networking. > > > > SO, I slapped the 802.1Q card into the laptop and strapped the GPS onto the outside of my backpack and went for a walk. > > > > I walked down Queen Street from the top to the water, and then back up to Albert St to Wellesley then back up Symonds to my hotel. > > > > Well. Auckland sure is brimming with wireless. But the concern (and I spose the reason that I posted this at all) was that most of it is insecure. > > > > Now I'm a good guy. I don't want to get access to anything, god knows I see enough internet as it is. I just wanted to see how many places had embraced the 802.1Q fad. > > > > So all in all 29 networks jumped out and grabbed me as I was walking past. only 4 of them were using WEP. > > Now because I didn't actually try to gain access to any of them, I have no idea what the internal security of them is like. But I'm not expecting much. > > > > I don't think I sniffed anything off the sky tower, I was only using the small antenna on the card. > > > > So if you run a wireless network in the center of Auckland and you were using the strategy of "Oh it will never make it down to the street" Then you are wrong and you might like to put some more security on. > > > > I thought about mailing my networklist out as well. But I decided against it. Mainly because it has exact GPS locations and network names. It would make easy pickings for anyone who wanted to gain access. > > If you want to mail me privatly with your network name and/or card MAC address then I will give you a yes or no answer. > > > > Dont feel alone though. I've done the same in North Sydney and come up with similar numbers. > > > > Next week wellington. > > > > Have fun > > > > 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

6 10

Proposed Change to Acceptable Use Policy
by Donald Neal 02 Aug '01

02 Aug '01

NZNOG People, It is not always obvious, but this list does have an acceptable use policy. Here it is: ---------- 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. ---------- This has served us well enough for a number of years. I now propose the following addition: 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Votes on this change to me (not the list!) by midday, Friday 10 August, please. In the interim, I intend to proceed as I outlined previously. I shall issue formal warnings for irrelevant or abusive postings, and shall act to block postings as soon as a third warning within thirty days is issued to any individual. To avoid any appearance of retrospective action, I shall start counting warnings only from the appearance of this posting to the list. NB: This wiping of the slate excludes persons who have during the last week threatened me with legal action or have threatened to approach my employers to get them to influence my issuing of warnings for inappropriate posting. I consider that those involved have received far more warning than most people already. If a majority of votes cast support the change, this will become permanent practice, and the list will switch in the near future to accepting postings only from addresses supplied in advance. If the majority oppose it, we shall return to relying on people's goodwill. Unless someone else has a better idea? Donald --------- 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 Address Management software.
by Steve Lang 02 Aug '01

02 Aug '01

Hiya. > Solarwinds (solarwinds.net) have a pretty cool suite of tools > that include > among others, IP management tools. They cost, but if you have > real buisiness > needs they are more cost effective than other commercial > solutions (Ci$co > included), and will quickly justify the cost. I had found them as well. Useful, and not that expensive when compared with others. > Network Address Recovery (This pings all IP address ranges > that you tell it > on a predetermined regular period (default 4 Hours), and > reports on the last > time an IP address was seen on the network) > There is a sample screen shot @ > http://solarwinds.net/Tools/Network_Discovery/Network_Address_ > Recovery/NetAd > Rec-1.gif I tested this, it looked quite good, but it's insistence at pinging things was annoying. > DHCP Scope Monitor (Requires Micro$soft DHCP and SNMP with > obviously NOT > public as the community string) Eeek. That would be interesting. Cheers and thanx. --------- 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 Address Management software.
by Steve Lang 02 Aug '01

02 Aug '01

Hiya all. 'Been lurking here for a while now, and actually have something worth saying now! I'm looking into IP Address Management packages. I've grazed through google, and a few others, and found pointers to many. It seems that there are a few packages that purport to allow people to manage IP Address space, but many of them focus on the integration of DHCP/DNS. Now, for what I'm after at the moment, this isn't an issue, and all I really want is something that can document allocations and what they're used for. There are some packages that don't exist now, and a couple that have changed hands within the last few years. An understanding of VLSM/CIDR etc. is required, although maybe not an understanding, but an allowance to docuement super/subnets. What do you, the contributors to this list use? And yes, I've done the spreadsheet thing to death... Cheers - -------------------------------------------------------------------------- Steve Lang Telephone: +64-9-309-7918 Consultant DDI: +64-9-307-5584 Optimation New Zealand Limited. Mobile: +64-25-864-653 P.O.Box 106104 Fax: +64-9-309-7919 Auckland E-mail: steve.lang(a)optimation.co.nz New Zealand Web: www.optimation.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 4

M1122 --- spontaneously corrupting flash
by Chris Wedgwood 01 Aug '01

01 Aug '01

Anyone out there inflicted with an M1122? I am, and for the second time to me, and third time in total (once at my old work) have had these modem die completely... Investigation (via console) has shown, in every single case, the flash has gotten corrupted or something, as image.exe (the firmware that is booted from ROM) is either corrupt or deleted. The worst thing is, the console refused to respond, which really sucks, as it means I can't revert to the previous image or put a new one on it. To make life even more interesting, the phone lines here are pretty spectacular, modems barely work and when they do, they drop about every 10 minutes or so even when you lock the modulation to v34 in an attempt to make things more reliable. --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: Crap
by Donald Neal 01 Aug '01

01 Aug '01

>>> "Matt Camp" <gargoyle(a)noise.net.nz> 08/01/01 08:55 >>> >I'd like to ask that this list is immediatly changed to drop non-member >submissions, and that Joe and Jeff are removed. >There is off topic conversation, and then there is pointless, induced, >drivel. NZNOG People, I'm not willing to get involved in a process of deciding for myself that one poster's five postings are cause for blocking, and someone else's are not. And the balance of the (admittedly small) number of emails I got on the subject last month was against restricting postings. On the other hand, I'm not at all happy with this list's s/n ratio. I have this morning sent to a number of posters requests not to send further inappropriate postings to this list. If these result in much improved behaviour, well and good. If not, I plan to move to a practice familiar to followers of cricket. Friendly warnings for misbehaviour may be given. Formal warnings follow. Too many formal warnings and you are asked to retire from the match. And yes, that would mean a move to restricting postings to addresses previously supplied, if not necessarily subscribed. Comments on that plan to the list, please. If it seems to me necessary to implement it I plan to put it to a vote as a set of additions to the AUP. When that might happen depends on postings. - 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

10 13

Code Red Early warning for SANS
by Jeff Williams 01 Aug '01

01 Aug '01

All, For your interest on Code Red Worm... See: http://www.digitalisland.net/codered/ for hour to hour reports... I also have an Eradicator if anyone is interested... Regards, -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Dean's Wireless Walkabout
by Dean Pemberton 01 Aug '01

01 Aug '01

Hi all; Yes this might be a first, I'm going to drag the topic BACK to something network related. I happen to be in Auckland today. Flew in for customer chit chat which will happen tommorow. Had a spare afternoon and no one to see so I thought I might do the geek thing and see how little old Auckland was getting along with it's wireless networking. SO, I slapped the 802.1Q card into the laptop and strapped the GPS onto the outside of my backpack and went for a walk. I walked down Queen Street from the top to the water, and then back up to Albert St to Wellesley then back up Symonds to my hotel. Well. Auckland sure is brimming with wireless. But the concern (and I spose the reason that I posted this at all) was that most of it is insecure. Now I'm a good guy. I don't want to get access to anything, god knows I see enough internet as it is. I just wanted to see how many places had embraced the 802.1Q fad. So all in all 29 networks jumped out and grabbed me as I was walking past. only 4 of them were using WEP. Now because I didn't actually try to gain access to any of them, I have no idea what the internal security of them is like. But I'm not expecting much. I don't think I sniffed anything off the sky tower, I was only using the small antenna on the card. So if you run a wireless network in the center of Auckland and you were using the strategy of "Oh it will never make it down to the street" Then you are wrong and you might like to put some more security on. I thought about mailing my networklist out as well. But I decided against it. Mainly because it has exact GPS locations and network names. It would make easy pickings for anyone who wanted to gain access. If you want to mail me privatly with your network name and/or card MAC address then I will give you a yes or no answer. Dont feel alone though. I've done the same in North Sydney and come up with similar numbers. Next week wellington. Have fun Dean --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 4

RE: Code Red (Take Two)
by Thomas Salmen 01 Aug '01

01 Aug '01

A little less of an impact this time then, huh? We've had two customers infected, both installs of which were less than a few days old. Seems that most admins (in NZ at least) have been rather better prepared this time round. Don't know if I can say the same for our friends overseas - many of the IPs that I have logged originate in Asia. Some in the States and Europe, but not as many. A few illegal, unpatched IIS installs, maybe... Must say, though, it was rather funny reading about the 'Code Red no-show' in the news this morning... Regards, Thomas Salmen System Administrator Radionet Ltd. 1/72 Paul Matthews Road Albany, Auckland, New Zealand Ph: +64 9 414 0300 ext 718 -----Original Message----- From: Thomas Salmen [mailto:thomas(a)radionet.co.nz] Sent: Thursday, 2 August 2001 2:12 p.m. To: nznog(a)list.waikato.ac.nz Subject: Code Red (Take Two) Just curious... have many people been affected by the second round of Code Red infections? We have seen plenty of inbound traffic here (well, the odd bit, anyway) but very few of our customers web servers have been hit - not like last time... Regards, 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 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Code Red (Take Two)
by Thomas Salmen 01 Aug '01

01 Aug '01

Just curious... have many people been affected by the second round of Code Red infections? We have seen plenty of inbound traffic here (well, the odd bit, anyway) but very few of our customers web servers have been hit - not like last time... Regards, 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

9 9

Hmm.
by David Robb 01 Aug '01

01 Aug '01

Is this true? http://www.bogusjourney.com/08018.html 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

13 25

(off topic) Stop with all the garbage please.
by stephen sheehan 01 Aug '01

01 Aug '01

Jeff, Dr Joe and all, I see myself as being fortunate to be a member of this mailing list, to here the wisdom of the local net Gods. It appears some of you do not share this view. I see this list as a valuable resource for the local net industry, and of late it seems to have deteriated into basicly a type of email chatroom for all sorts of off-topic bitching. So I am asking that you please have some respect for the intended purpose of this list and other list members. If you want to bitch to each other or discuss stuff that is not relavent, please do so by private email, as I am sure most of you have better things to do than sort through all the shit that has been posted to the list lately. Sorry for posting this off topic e-mail and sounding like a hypocrite and also adding to the large amount of crap alread on this list. Your sincerely Stephen Sheehan __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Alternative List
by Matt Camp 01 Aug '01

01 Aug '01

A while back an alternative list was proposed... most people seemed quite receptive to the idea... so it now exists. To subscribe, send a mail to majordomo(a)noise.net.nz with 'subscribe nznet' in the body. The alternative list is more informal, and more generally aimed at the NZ Networking industry. It may contain things such as details of used equipment for sale, and discussions which would be regarded as off topic here. Hopefully this will give us a place to discuss such things, and will keep the noise level down here somewhat. --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Crap
by Michael Bordignon 01 Aug '01

01 Aug '01

maybe uh, ending discussion of this completely off-topic discussion and refraining from replying to any further attempts to revive it may be productive? (including replying to this rhetorical post) Michael > i know this well and so does jeff. example - you filter me > out - or jeff > - or whomever it may be you choose to filter - then some third party > begins the drivel about jeff williams. well - you end up on > the receiving > end of the drivil from the third parties. in most cases > filtering ends up > causing confusion. you would essentially have to filter out > everyone who > is speaking about jeff williams - and that in my opinion is counter > productive. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Validation of INEGROUP.GOD Domain
by The dot.GOD Registry, Limited 01 Aug '01

01 Aug '01

Hello: This email will confirm that we have processed your domain registration request for: INEGROUP.GOD. Someone, hopefully you, has registered this domain with us. If not please let us know. You must now visit our web site to validate your domain and enter your validation ticket number. TICKET: 52396544d99665168490 Please click on the following URL to activate your new domain name now. https://secure.dot-god.com/god.nic/validate.cgi?inegroup=52396544d996651684… Or if the above URL does not work (some email systems may crop the URL) then please visit: https://secure.dot-god.com/cgi-bin/validate.cgi and enter the following information manually at the prompt: DOMAIN: inegroup TICKET: 52396544d99665168490 Regards hostmaster(a)dot-god.com http://www.dot-god.com/ The dot.GOD Registry, Limited Executive Plaza, Suite 908 150 West 51st Sreet New York, New York, 10019 US --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 5

RED WORM Virus
by Mike Conner 01 Aug '01

01 Aug '01

Has any one seen the worm yet? Mike Conner. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

Code Red growth stats (fwd)
by !Dr. Joe Baptista 31 Jul '01

31 Jul '01

my contribution to keeping this conference topical today. ---------- Forwarded message ---------- Date: Wed, 1 Aug 2001 09:44:05 -0700 From: k claffy <kc(a)ipn.caida.org> To: nanog(a)nanog.org Subject: Code Red growth stats (david moore with help from a bunch of elves) http://www.caida.org/analysis/security/code-red/aug1-live-hosts.gif was exponential till about an hour ago, we're not sure if leveling off is due to our monitor load or an actual peak in the data. log-scale version http://www.caida.org/analysis/security/code-red/aug1-live-hosts-log.gif will put on main caida home page later today and update every minute (you'll have to hit reload, and you won't actually notice changes at a minute granularity so please no per-minute cron jobs to reload :) ) note the corresponding graph for 19-20 july: http://www.caida.org/analysis/security/code-red/gifs/cumulative-ts.log.gif no per AS stats for this outbreak yet, also under construction. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Preemptive strike.
by Andrew Garrett 31 Jul '01

31 Jul '01

Yes, the name Andrew Garrett has been in the news lately. No, I'm not that Andrew Garrett. Yes, my employer is aware of the name similarity, and has investigated the difference between the two individuals, and is satisfied that we are different people. No, the New Zealand Stock Exchange has not hired a "known hacker". Yes, it is rather amusing. No, not very amusing when you're involved. Regards Andrew "sigh, no, not that one" Garrett --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 6

Re: nznog subscriber test (jwkckid1@ix.netcom.com)]
by Jeff Williams 31 Jul '01

31 Jul '01

Olderon and all, All I did was be sure to send my response along with my question to the list. I also send Andrew's response as well to the list as I am this one. It seems that perhaps that Andrew is not in agreement with your assessment. As such, it seems that the test was in and of itself a failure or misleading... ????? Olderon wrote: > Jeff. > That was an Intelligence test. you failed. > > "The easiest was for me to do this is to send each subscriber this > brief email and then examine any bounces and errors." > > See the word each? > > That email was sent to everyone on the list. If any of the email addresses > got bounced back or got errors then they would be deemed inactive and > removed from the list. > > ----- Original Message ----- > From: "Jeff Williams" <jwkckid1(a)ix.netcom.com> > To: <nznog(a)list.waikato.ac.nz> > Cc: "Chris Wedgwood" <cw(a)f00f.org> > Sent: Wednesday, August 01, 2001 3:06 PM > Subject: [Fwd: nznog subscriber test (jwkckid1(a)ix.netcom.com) > > > Chris, > > > > What is this all about? Why is My E-mail being singled out? > > > > -- > > Jeffrey A. Williams > > Spokesman for INEGroup - (Over 118k members strong!) > > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > > Information Network Eng. Group. INEG. INC. > > E-Mail jwkckid1(a)ix.netcom.com > > Contact Number: 972-447-1800 x1894 or 214-244-4827 > > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > > Regards, -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------- 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: [Fwd: nznog subscriber test (jwkckid1@ix.netcom.com)]
by Jeff Williams 31 Jul '01

31 Jul '01

Sheath and all, Thank you for this clarification. However it does not explain Andrew's response.... ????? sheath(a)paradise.net.nz wrote: > everyone got one with the email addy in the subject line to help with > recording the bounces. > > So each person got a test msg with their own email addy in it. > > SPH > > > Chris, > > > > What is this all about? Why is My E-mail being singled out? > > > > -- > > Jeffrey A. Williams > > Spokesman for INEGroup - (Over 118k members strong!) > > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > > Information Network Eng. Group. INEG. INC. > > E-Mail jwkckid1(a)ix.netcom.com > > Contact Number: 972-447-1800 x1894 or 214-244-4827 > > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > > Regards, -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------- 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: [Fwd: nznog subscriber test (jwkckid1@ix.netcom.com)]
by Donald Neal 31 Jul '01

31 Jul '01

>>> "Mark Foster" <blakjak(a)blakjak.net> 08/01/01 01:21 >>> >The list administrator sent every individual on the list an email in order >to analyse the bounces (if any). > >So therefore noone is 'singled out'. [...] No, I didn't. I'm advised of bounces automatically when they occur. The email in question appears to have originated from Chris Wedgwood. He will presumably now tell us why he sent it. - Donald Neal -- 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

Re: [Fwd: nznog subscriber test (jwkckid1@ix.netcom.com)]
by Jeff Williams 31 Jul '01

31 Jul '01

Andrew and all, I always read all my E-mail closely. What Bullshit? Andrew Garrett wrote: > 1. read the e-mail > 2. learn to not clog lists will bullshit. > > At 08:06 PM 7/31/01 -0700, you wrote: > >Chris, > > > > What is this all about? Why is My E-mail being singled out? > > > >-- > >Jeffrey A. Williams > >Spokesman for INEGroup - (Over 118k members strong!) > >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > >Information Network Eng. Group. INEG. INC. > >E-Mail jwkckid1(a)ix.netcom.com > >Contact Number: 972-447-1800 x1894 or 214-244-4827 > >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > >Return-Path: <cw+nznog-test-bounce-jwkckid1=ix.netcom.com(a)f00f.org> > >Received: from weta.f00f.org ([203.167.249.89]) > > by elektra (Earthlink/Netcom Mail Service) with ESMTP id > > tmejqq.lmr.37tiu4v > > for <jwkckid1(a)ix.netcom.com>; Tue, 31 Jul 2001 17:37:46 -0700 (PDT) > >Received: by weta.f00f.org (Postfix, from userid 1000) > > id 18BED159B7; Wed, 1 Aug 2001 12:38:14 +1200 (NZST) > >From: Chris Wedgwood <cw(a)f00f.org> > >To: jwkckid1(a)ix.netcom.com > >Subject: nznog subscriber test (jwkckid1(a)ix.netcom.com) > >X-NZNOG-USER: jwkckid1(a)ix.netcom.com > >Reply-To: cw+nznog-test-dont-reply(a)f00f.org > >Message-Id: <20010801003814.18BED159B7(a)weta.f00f.org> > >Date: Wed, 1 Aug 2001 12:38:14 +1200 (NZST) > >MIME-Version: 1.0 > > > >Firstly, my apologies for this brief intrusion. I'm currently testing > >which subscribers of nznog are invalid. > > > >The easiest was for me to do this is to send each subscriber this > >brief email and then examine any bounces and errors. > > > >If you have any questions, please feel free to contact me (create a > >new email, don't reply to this or use the subject above, as it may > >interfere with my primitive automagic filtering technique). > > > >I will post a summary of these results to nznog early next week if > >not sooner. > > > > > > > >Thanks, and once again my apologies for this interruption. > > > > --cw -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

[Fwd: nznog subscriber test (jwkckid1@ix.netcom.com)]
by Jeff Williams 31 Jul '01

31 Jul '01

Chris, What is this all about? Why is My E-mail being singled out? -- Jeffrey A. Williams Spokesman for INEGroup - (Over 118k members strong!) CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Contact Number: 972-447-1800 x1894 or 214-244-4827 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208

2 1

Broadband in Greenhithe?
by Juha Saarinen 31 Jul '01

31 Jul '01

Possible? A person there needs something quicker than dial-up for remote access etc. but was told that Jet{start|stream} isn't available in Greenhithe. The area is Black's Road, top of the ridge. Any advice would be appreciated... :-) -- Juha --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

New Zealand Network Operators' Group
by Donald Neal 31 Jul '01

31 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 around 260 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/ Any message sent to the list will be archived and made available on the web automatically. 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. A recent suggestion that posting be restructed to subscribers received little support. 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

IDGNet News: The fixed version
by IDGNetAdministrator＠idg.co.nz 26 Jul '01

26 Jul '01

This message has been sent to you by a user of IDGNet, New Zealand's leading I.T. information Website. Version as of 2:50 26/7/01 Privacy issue over mailing list archives Mailing lists that make archives of their postings publicly accessible on the internet could be in breach of the Privacy Act, according to an Auckland lawyer. http://www.idg.net.nz/webhome.nsf/UNID/29322B8165E1E256CC256A94001886CB?ope… For the latest in I.T. News, Reviews, Opinion and more visit http://idg.net.nz If you wish to block your email address from receiving further emails of this type please email nzwebmaster(a)idg.co.nz. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 4

FW: Help! Cistron major failure in production! (fwd)
by Matt Camp 25 Jul '01

25 Jul '01

Anyone had any experience with cistron radius? I'm suffering some sort of major magic weridy problem, if anyone has any ideas. --- Matt Camp ---------- Forwarded message ---------- Date: Wed, 25 Jul 2001 17:24:51 +1200 (NZST) From: Matt Camp <gargoyle(a)noise.net.nz> To: cistron-radius(a)lists.cistron.nl Subject: Help! Cistron major failure in production! I run a network of 4 cistron 1.6.3 servers on FreeBSD machines. This afternoon, all 4 of them stopped responding. Its as like the radiusd process isn't running. Neither our lucent NAS gear, radtest, or the various people who have proxys pointed at our servers get any response at all. The server logs, and console when running in -xxx mode show that the server starts, and then is just waiting for connections. Every 5 minutes, i propagate a new raddb/users file out from a central host. This system has worked fine for around 18 months now. On _ONE_ of the servers, if i restart it (totally. Kill and restart radiusd), the log shows "Wed Jul 25 17:21:38 2001: Info: Starting - reading configuration files ...", then there is nothing for approximately 4 minutes, after which it appears to process all the requests that have been sent to it during that time. (of course, most of them actually fail in reality since the NAS has long since dropped the call). Then it will run fine, up until it detects a new users file, and reloads the config files, at which point its back into total non-responsiveness until i manually restart it. This only works on one server. The other 3 don't come back at all, even after a restart. ANd they're all on the same config. (Which i rsync to them after making a change) radtest tests from localhost which normally work fine just act exactly as if the radiusd process isn't even running. I've tried everything i can think of, including the microsoft approach of power-cycling all machines involved. Load averages are normal, disk space is fine. Heaps of memory available. File descriptor loads seem ok, in that there are only around 100 or so connections to each box in total. (for the other services they run) Any ideas? This is urgent... I've got thousands customers who can't log in right now. --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 8

xtra rejecting mail from mailing lists?
by Simon Blake 25 Jul '01

25 Jul '01

Hi folks 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: Jul 25 21:49:03 wilbur qmail: 996054543.173139 delivery 2330: deferral: Connected_to_203.96.92.131_but_greeting_failed./Remote_host_said: _421_mta4-rme.xtra.co.nz_connection_refused_from_[203.97.152.50]/ It's a fairly unhelpful message from xtra, I assume it's some kind of antispam rate limiting thing - anybody know what they're up to? These things appear to get delivered later, since I've not had any grizzles about non delivery of mail (and there's nothing in the qmail queue). Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 13

RE: IDG article.
by David Buckingham 25 Jul '01

25 Jul '01

Privacy Act 1993 028 Commenced: 1 Jul 1993 VI: Codes of Practice and Exemptions from Information Privacy Principles Specific Exemptions 55 Certain personal information excluded 55. Certain personal information excluded---Nothing in principle 6 or principle 7 applies in respect of--- (a) Personal information in the course of transmission by post, telegram, cable, telex, facsimile transmission, electronic mail, or other similar means of communication; or (b) Evidence given or submissions made to--- (i) A Royal Commission; or (ii) A commission of inquiry appointed by an Order in Council made under the Commissions of Inquiry Act 1908,--- at any time before the report of the Royal Commission or commission of inquiry has been published or, in the case of evidence or submissions given or made in the course of a sitting open to the public, at any time before the Royal Commission or commission of inquiry has reported to the Governor-General; or (c) Evidence given or submissions made to a commission of inquiry or board of inquiry or court of inquiry or committee of inquiry appointed, pursuant to, and not by, any provision of an Act, to inquire into a specified matter; or (d) Information contained in any correspondence or communication that has taken place between the office of the Ombudsmen and any agency and that relates to any investigation conducted by an Ombudsman under the Ombudsmen Act 1975 or the Official Information Act 1982 or the Local Government Official Information and Meetings Act 1987, other than information that came into existence before the commencement of that investigation; or (e) Information contained in any correspondence or communication that has taken place between the office of the Commissioner and any agency and that relates to any investigation conducted by the Commissioner under this Act, other than information that came into existence before the commencement of that investigation. PRINCIPLE 6 Access to personal information (1) Where an agency holds personal information in such a way that it can readily be retrieved, the individual concerned shall be entitled--- (a) To obtain from the agency confirmation of whether or not the agency holds such personal information; and (b) To have access to that information. (2) Where, in accordance with subclause (1) (b) of this principle, an individual is given access to personal information, the individual shall be advised that, under principle 7, the individual may request the correction of that information. (3) The application of this principle is subject to the provisions of Parts IV and V of this Act. (This part is from section 6 of the act)... PRINCIPLE 7 Correction of personal information (1) Where an agency holds personal information, the individual concerned shall be entitled--- (a) To request correction of the information; and (b) To request that there be attached to the information a statement of the correction sought but not made. (2) An agency that holds personal information shall, if so requested by the individual concerned or on its own initiative, take such steps (if any) to correct that information as are, in the circumstances, reasonable to ensure that, having regard to the purposes for which the information may lawfully be used, the information is accurate, up to date, complete, and not misleading. (3) Where an agency that holds personal information is not willing to correct that information in accordance with a request by the individual concerned, the agency shall, if so requested by the individual concerned, take such steps (if any) as are reasonable in the circumstances to attach to the information, in such a manner that it will always be read with the information, any statement provided by that individual of the correction sought. (4) Where the agency has taken steps under subclause (2) or subclause (3) of this principle, the agency shall, if reasonably practicable, inform each person or body or agency to whom the personal information has been disclosed of those steps. (5) Where an agency receives a request made pursuant to subclause (1) of this principle, the agency shall inform the individual concerned of the action taken as a result of the request. -----Original Message----- From: owner-nznog(a)list.waikato.ac.nz [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Greg Clare Sent: Thursday, 26 July 2001 1:23 p.m. To: nznog(a)list.waikato.ac.nz Subject: RE: IDG article. Does this mean that what was originally reported and quoted as having been said by someone, has now been edited and changed? Does this constitute creative reporting? By chance does the article include an addendum to state that it has since been edited due to people or terms being mis-quoted... for the archive of course ;) Greg > -----Original Message----- > From: Simon Lyall [mailto:simon.lyall(a)ihug.co.nz] > Sent: Thursday, 26 July 2001 12:46 pm > To: nznog(a)list.waikato.ac.nz > Subject: IDG article. > > > Looks like they have gone through and changed all the mentions of > "newsgroups" to "mailing list" and changed other stuff around. > > This includes the the stuff in quotes. > > -- > 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 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

IDG article.
by Simon Lyall 25 Jul '01

25 Jul '01

Looks like they have gone through and changed all the mentions of "newsgroups" to "mailing list" and changed other stuff around. This includes the the stuff in quotes. -- 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: IDG article.
by Greg Clare 25 Jul '01

25 Jul '01

Does this mean that what was originally reported and quoted as having been said by someone, has now been edited and changed? Does this constitute creative reporting? By chance does the article include an addendum to state that it has since been edited due to people or terms being mis-quoted... for the archive of course ;) Greg > -----Original Message----- > From: Simon Lyall [mailto:simon.lyall(a)ihug.co.nz] > Sent: Thursday, 26 July 2001 12:46 pm > To: nznog(a)list.waikato.ac.nz > Subject: IDG article. > > > Looks like they have gone through and changed all the mentions of > "newsgroups" to "mailing list" and changed other stuff around. > > This includes the the stuff in quotes. > > -- > 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

1 0

prefix list update
by James Tyson 25 Jul '01

25 Jul '01

Can all Attica's BGP peers please update their filters: ip prefix-list attica-networks seq 5 permit 202.180.96.0/19 ip prefix-list attica-networks seq 10 permit 202.180.64.0/18 le 19 ip prefix-list attica-networks seq 15 permit 210.55.254.0/24 ip prefix-list attica-networks seq 20 permit 210.55.5.0/24 ip prefix-list attica-networks seq 25 permit 202.50.170.0/24 ip prefix-list attica-networks seq 30 permit 202.55.111.0/24 Cheers. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 5

RE: xtra rejecting mail from mailing lists?
by Jeremy Clyma 25 Jul '01

25 Jul '01

At 08:17 26/07/2001 +1200, Tech Support wrote: > >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..... ;) /sv_tui_ad Yeah. Right. Looks like its a transient error, one which could be caused by the backoff limits we've got in place. Simon, do you know how many concurrent smtp connections was your server attempting to open? --------- 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: 'we should all be uncomfortable with the extent to which luck..' (fwd)
by n.brownlee＠auckland.ac.nz 25 Jul '01

25 Jul '01

Hello all: You might find this article interesting reading ... Cheers, Nevil ------------------------------------------------------------- Nevil Brownlee Internet Researcher Phone: (858) 534 8338 CAIDA, San Diego ---------- Forwarded message ---------- Date: Tue, 24 Jul 2001 22:35:37 -0700 From: k claffy <kc(a)caida.org> To: nanog(a)nanog.org Cc: caida(a)caida.org Subject: 'we should all be uncomfortable with the extent to which luck..' 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