- NZNOG - lists.nznog.org

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 05 Aug '01

05 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