- NZNOG - lists.nznog.org

US Terrorist Attacks
by Chris Wedgwood 12 Sep '01

12 Sep '01

As most of you will know my now, there have been a number of terrorist attacks in the US. All phone circuits over here are overloaded and email is about the only thing left working after popular new sites have collapsed under the load. Any communications to and from the East Cost of the US are suffering something terrible... email still works but thats about it for many places. Watching this live is truly chilling... --cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 6

Julian Angelo
by Matthew Poole 11 Sep '01

11 Sep '01

Gee, what a short period of reform. Following on from Messr Angelo's request that his "history" be removed from the archives of NZNOG, he's back again. With a vengance. i4free's abuse mailbox currently has about 26 e-mails in it, and at least 18 of them are regarding the latest spam campaign by NZ's most notorious e-mail figure. We're certainly looking forward to closing all his accounts. Again. NOT! -- Matthew Poole "Ever wondered why cemetaries raise the cost of burials then blame it on the cost of living?" --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 21

Re: Julian Angelo
by Mark Foster 10 Sep '01

10 Sep '01

Where the hell did that come from? As the person who did all of the closing of Julians accounts LAST time he did this over the I4free network, I know exactly what Matt is going on about. I dont see anything libelious in what Matthew has just said. Dont turn this into something its not. Its simply a case of Julian Angelo again shooting himself in the foot - libel is not libel when reported thruthfully. Lets not start a sparring match where one neednt be. Mark. At 02:02 11/09/2001 -0400, you wrote: >you should not be uttering this sort of spew on a public list - unless of >course you consider libel and slander charges against yourself and your >company to be a good thing. > >your expressing a certain amount of planned malice - and that don't look >right. > >regards >joe > > On Tue, 11 Sep 2001, Matthew Poole wrote: > > > > > Gee, what a short period of reform. > > Following on from Messr Angelo's request that his "history" be removed > > from the archives of NZNOG, he's back again. With a vengance. > > i4free's abuse mailbox currently has about 26 e-mails in it, and at least > > 18 of them are regarding the latest spam campaign by NZ's most notorious > > e-mail figure. > > We're certainly looking forward to closing all his accounts. Again. NOT! > > > > > >-- >Joe Baptista > >The dot.GOD Registry, Limited >The Executive Plaza, Suite 908 >150 West 51st Street Tel: 1 (208) 330-4173 >Manhattan Island NYC 10019 USA Fax: 1 (208) 293-9773 > >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Raptor firewalls
by Brian Gibbons 10 Sep '01

10 Sep '01

>From: "Brodie Davis" <brodie.davis(a)voyager.co.nz> >As what that does is break the 3 way handshake for tcp >connections (it responds to a SYN with a ACK and a >incorrect acknoledgement number). >It(raptor) only behaves this way with the netscreen box, not with >my RH box sitting out in the wild. ( i have packet dumps of the traffic) Logic says that if you have a known good config and a broken config then compare the difference. What is the difference between the SYN packet from the RH box and the SYN packet from netscreen. Potential differences include TCP options, normally just MSS, but are there others? Source IP/Port? IP Options? ------ Hehe, how many years before we start seeing postings about "appliance problems" >Hi, is anyone else having weird problems talking to raptor firewalls. Hi, is anyone else having wierd problems with F&P SmartFridges >What is happening is that we are running netscreen firewalls (hardware >appliances) and we can't talk to any raptor firewall with its syn flood >protection on. What is happening is we are running Panasonic KXH-234 Set Top boxes connected to Sky, unfortunately everytime the user switches to the Sports channel the F&P SmartFridge pops up on screen to confirm an online order for three trays of Red :) Any clues? Cheers 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

Raptor firewalls
by Brodie Davis 10 Sep '01

10 Sep '01

Hi, is anyone else having weird problems talking to raptor firewalls. What is happening is that we are running netscreen firewalls (hardware appliances) and we can't talk to any raptor firewall with its syn flood protection on. As what that does is break the 3 way handshake for tcp connections (it responds to a SYN with a ACK and a incorrect acknoledgement number). It(raptor) only behaves this way with the netscreen box, not with my RH box sitting out in the wild. ( i have packet dumps of the traffic) (i haven't had a chance to observe how it deals with PIX and checkpoint.) Is that traffic pattern an addition to the TCP standard or is it completly non standard coms. (I found rfc 0793/ STD0007 that defines what i expect, but i can't see any additions to the standard supporting the Axent/Symantic way). Anyone got any thoughts? Cheers, Brodie --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

mta.xtra.co.nz doesn't accept SMTP connects?
by Juha Saarinen 05 Sep '01

05 Sep '01

Noticed lots of mail to Xtra customers stuck in the mail queue on one of ours swervers... doesn't seem like mta.xtra.co.nz is working properly: $ telnet mta.xtra.co.nz. 25 Trying 203.96.92.132... telnet: connect to address 203.96.92.132: Operation timed out telnet: Unable to connect to remote host -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

14 31

radius diag command max6000
by John Lynch 05 Sep '01

05 Sep '01

Any one out there remember the command to put the max6000 into radius debug mode, did it a few weeks ago, now it's gone from my head ...... ?????? 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

2 5

Responses to Letter from ING
by David Farrar 04 Sep '01

04 Sep '01

I'm inquiring if any ISP or like body knows of any business who responded to ING's letter and either changed their mind or now wishes they changed their mind? TVNZ are doing an article on the letter and would like to be able to interview someone who was taken in by it or at the minimum who was going to take it up until they sought advice. Also any indications from ISPs as to how many calls they have recived about the letter would be useful. If you know of anyone can you pass on their contact details to me or alternatively get them to contact me by e-mail or on 04 471 9353, preferably by midday tomorrow. Ta 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

clear.co.nz seems to be rejecting mail
by Dan Langille 04 Sep '01

04 Sep '01

FWIW: it appears that Clear are rejecting mail to clear.co.nz but not to clear.net.nz: ----- The following addresses had permanent fatal errors ----- <postmaster(a)clear.co.nz> ----- Transcript of session follows ----- ... while talking to kakapo.clear.co.nz.: >>> DATA <<< 554 SPAM-Relay detected 554 <postmaster(a)clear.co.nz>... Service unavailable I've emailed postmaster(a)clear.net.nz but just in case mail start building up on your servers, you know why.. -- Dan Langille - DVL Software Limited FreshPorts - http://freshports.org/ - the place for ports --------- 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: mta.xtra.co.nz doesn't accept SMTP connects?
by Greg Clare 03 Sep '01

03 Sep '01

hmmm... an analogy is perhaps called for... Customer: Arrrgh, my telephone is dead! Telecom (in a publicly posted statement): Technicians are currently working on this issue. Customer: If they knew my telephone was dead, why the F@#&! didn't they phone and tell me??? > -----Original Message----- > From: Nicholas Lee [mailto:nj.lee(a)plumtree.co.nz] > Sent: Tuesday, 4 September 2001 2:58 pm > To: Mark Foster > Cc: Nznog(a)List. Waikato. Ac. Nz > Subject: Re: mta.xtra.co.nz doesn't accept SMTP connects? > > On Tue, Sep 04, 2001 at 01:40:24PM +1200, Mark Foster wrote: > > > > For NZ's Biggest ISP theyre remarkably quiet... > > Maybe because they aren't getting any mail? > > Nicholas > --------- --------- 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: mta.xtra.co.nz doesn't accept SMTP connects?
by Ewen McNeill 03 Sep '01

03 Sep '01

In message <21773.999569321(a)daedalus.co.nz>, Don Stokes writes: >Mark Foster <blakjak(a)blakjak.net> wrote: >>Simons Idea of setting up some servers as Secondary MX isnt a silly idea >>but I need to ask the questions: > >Actually, secondary MXs usually are a silly idea, if the MX can't >actually do anything useful with the mail apart from queuing it. All >they do is take a whole bunch of mail that would otherwise queue at the >client end mail server, and put them in one big queue. Secondary MXes (that can only queue and attempt onward delivery) are about "concentration of pain"; instead of the pain being spread across all the mail servers trying to deliver to the one that is down, it's concentrated in the secondary MX(es). This concentration of pain was more useful in the days when there were quite a few slow, not always up, links trying to deliver mail (especially dial-on-demand type links; uucp tended to be smarthosted once things got to a point that it mattered). Now that the common mode of mail delivery is basically two tier (clients deliver to their ISP's smart host, that smarthost is always connected and "easily" able to retry the mail often enough") there's less advantage in concentrating the pain. Especially weighed against some of the disadvantages you mention (eg, don't get "trouble sending" bounces early if sender end has low timeouts on those, but secondary MX doesn't). Except perhaps when the pain lasts a long time (hours, if not days), and causes a fair amount of trouble to a lot of people/mail servers. Like Xtra at the moment from what I've seen on nznog. BTW, has anyone considered that the reason that no one from Xtra has spoken up is that their outgoing mail is having trouble as well as their incoming mail? :-) Ewen --------- 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: mta.xtra.co.nz doesn't accept SMTP connects?
by Simon Byrnand 03 Sep '01

03 Sep '01

At 02:26 PM 4/09/01 +1200, Simon Lyall wrote: >On Tue, 4 Sep 2001, Don Stokes wrote: >> Most mailers have a hard time with huge queues of undeliverable mail, so >> such an MX is not going to be as efficient at dealing with the backlog >> when the primary comes back up as just leaving the mail where it is on >> client servers. > >The thing is it moves the load from our smtp servers (which last time I >looked had a lot of undelived emails for xtra customers) onto a machine >run by Xtra. Due to the amount of queued email on our servers we have had >to start taking actions to prevent delays of email to other sites. Yup. Not having a backup MX makes xtra's problem everyone elses problem instead. >You can also optimise the backup MX server for dealing with a large queue >to a single destination rather than a constrant stream of email to many >destinations. There are also other tricks you can run depending on your >mail software and network setup. Not to mention that mail servers around the country trying to connect to xtra's all the time wastes other peoples bandwidth. With a backup MX the mail queuing and retrying would be occuring between their backup and primary MX which in all likelyhood would be internal traffic (perhaps even on the same switched ethernet) rather than over national links. Dequeuing when the problem was resolved would be faster and more efficient than waiting for various random servers around the country to retry. >The anoying bit is that Xtra has not acknowledged this in public at all, >we are getting our customers blaming us for delays in email getting to >Xtra addresses. Well actually, they have acknowledged the problem on their website, (I was surprised, I was expecting the standard "There are no knon problems with the Xtra network") so short of making a public annoucement on TV and radio I don't see what else they could do to raise awareness to the average user :) Regards, Simon --------- 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: mta.xtra.co.nz doesn't accept SMTP connects?
by Michael Bordignon 03 Sep '01

03 Sep '01

> -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Tuesday, 4 September 2001 1:20 PM > To: 'Simon Byrnand'; 'Dylan Reeve' > Subject: RE: mta.xtra.co.nz doesn't accept SMTP connects? > > > pop3.xtra.co.nz == mta.xtra.co.nz > then again they might be doing some type of port forwarding on that box? --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

The New Zealand Network Operators' Group
by Donald Neal 02 Sep '01

02 Sep '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. 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. 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 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. Post-only Mailing List An address from which you wish to post, but which will not receive messages from the list, may be subscribed to nznog-postonly. You will presumably want to have another address subscribed to the main nznog list. 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

RE: Wireless LAN equipment
by Greg Clare 02 Sep '01

02 Sep '01

Just another thought for ya... If it is a single story house and you can get under the house, then what I did was simply drill a small hole through the chipboard floor (just big enough for the Cat5 cable to get through), at the very edge of the carpet, right next to the skirting board. A small hole in the floor at the edge of the carpet line is invisible to anyone making a visual inspection (unless you get the carpet caught in the electric drill and rip a huge chunk of wool out... try to avoid this!). Then, if you don't want to screw Cat-5 outlets to your skirting board, just crimp the RJ45 plugs directly onto the leads that come up from under the floor so you can plug the leads straight into your RJ45 device. When you move, just cut the plug off one end of each lead and pull them back through, the little holes are left hidden by the carpet. PS: Going under the house also saves getting your lungs full of glass fibre. Greg > -----Original Message----- > Anyway, this is how a real pro (yep, that's me!) would do it: you get > your Cat-5 ready and then, get into the ceiling! Brilliant > eh? Tends to > work the best on old vullahs, where you can crawl around, breathing in > the remnants of some extremely hirsute sheep (or glass wool), and drop > the cable through the ventilation shafts or the holes for the > chandeliers-wotsits. Honest, it looks really neat and tidy -- > much nicer > than sticky tape all over the place. Watch out you don't put a foot > wrong though, and step through the ceiling. Lots of > cable-laying novices > perish every year that way. > > -- > Juha --------- 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: Speed of the list
by Ewen McNeill 01 Sep '01

01 Sep '01

In message <20010829125016.S7096(a)wilbur.katipo.co.nz>, Dean Pemberton writes: >[nznog; messages take a while to come out] >I can remember some guy from BSDi talking at uniforum in 98 about how sendmail >was crap at this. [addresses that don't resolve, etc, can kill whole list] Not to rain on anyone's parade, but most mailing list software injects messages in queue mode (to avoid an explosion of MTA processes trying to send the messages out immediately (in the background)). This then relies on the MTA queue processing to shift the messages out. Has anyone checked how often the queue is run on the relevant server? If it's every 30 minutes it'd pretty much exactly explain the times reported. If it's every 15 minutes (a common default with sendmail), then 15-minutes plus isn't that unlikely to happen given the right circumstances. For a mailing list of a few hundred addresses, it should be a walk in the park for most MTAs, sendmail included. Ewen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

Wireless LAN equipment
by Richard Stevenson 31 Aug '01

31 Aug '01

Hi all In the interests of keeping my soon-to-be-landlord happy, I'm looking at building a wireless LAN rather than making holes in the 13-month-old house I'm about to move into. Can anyone recommend any particular equipment, suppliers, sources of information? It'll only be a small network to start with - five systems, though it'll grow; I have a nasty habit of accumulating junk :P Many thanks Richard -- Richard Stevenson, Systems Specialist, Xtra Limited Phone: +64 9 355 5231 Mobile: +64 25 290 3101 Pager: +64 26 100 155 "Visual $ANYTHING" just screams out "100% suckage or your money back". -- Tanuki the Raccoon-dog, in the Monastery --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

9 9

This is not London calling
by Juha Saarinen 31 Aug '01

31 Aug '01

pts/1 juha(a)vimfuego:~$ ping news.bbc.co.uk ping: unknown host news.bbc.co.uk Kerrap. Jetstream? Or somewhere else? bash-2.05$ ping news.bbc.co.uk PING newswww.bbc.net.uk (212.58.226.40): 56 data bytes 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 420b 0 0000 01 01 8ae0 210.48.100.42 212.58.226.40 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 420d 0 0000 01 01 8ade 210.48.100.42 212.58.226.40 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 420e 0 0000 01 01 8add 210.48.100.42 212.58.226.40 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 420f 0 0000 01 01 8adc 210.48.100.42 212.58.226.40 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 4210 0 0000 01 01 8adb 210.48.100.42 212.58.226.40 36 bytes from 202.84.249.66: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 4211 0 0000 01 01 8ada 210.48.100.42 212.58.226.40 Hrrmmm... bash-2.05$ traceroute 212.58.226.40 traceroute to 212.58.226.40 (212.58.226.40), 30 hops max, 40 byte packets 1 210.48.100.1 (210.48.100.1) 1.975 ms 2.543 ms 1.746 ms 2 s0.ts9.ak.nz.asiaonline.net (210.48.2.1) 12.198 ms 12.155 ms 14.796 ms 3 f1-0.gw2.ak.nz.asiaonline.net (202.14.100.254) 53.810 ms 12.707 ms 12.221 ms 4 f0-0.gw1.ak.nz.asiaonline.net (210.48.1.1) 12.617 ms 12.623 ms 13.230 ms 5 g0-1-0-221.b4.sxb.tsnz.net (203.98.4.205) 13.391 ms 13.481 ms 12.665 ms 6 GE0-0-0.nzsx-core1.Auckland.telstra.net (203.98.4.3) 16.891 ms 22.031 ms 18.472 ms 7 GigabitEthernet4-0-0.nzsx-core2.Auckland.net.reach.com (203.50.126.58) 26.852 ms 26.061 ms 22.163 ms 8 202.84.249.129 (202.84.249.129) 153.251 ms 153.572 ms 146.691 ms 9 202.84.249.66 (202.84.249.66) 227.914 ms 228.862 ms 224.985 ms 10 202.84.249.65 (202.84.249.65) 229.739 ms 221.260 ms 231.744 ms 11 202.84.249.66 (202.84.249.66) 309.732 ms 308.025 ms 305.737 ms 12 202.84.249.65 (202.84.249.65) 307.482 ms 300.437 ms 319.887 ms 13 202.84.249.66 (202.84.249.66) 456.585 ms 383.322 ms 377.616 ms 14 202.84.249.65 (202.84.249.65) 375.120 ms 377.874 ms 376.425 ms 15 202.84.249.66 (202.84.249.66) 453.441 ms 454.953 ms 457.326 ms 16 202.84.249.65 (202.84.249.65) 458.146 ms 454.757 ms 449.970 ms 17 202.84.249.66 (202.84.249.66) 536.290 ms 532.411 ms 533.366 ms 18 202.84.249.65 (202.84.249.65) 530.822 ms 592.469 ms 526.726 ms 19 202.84.249.66 (202.84.249.66) 602.030 ms 601.476 ms 607.230 ms 20 202.84.249.65 (202.84.249.65) 605.603 ms 627.870 ms 605.202 ms 21 202.84.249.66 (202.84.249.66) 682.281 ms 687.296 ms 675.443 ms 22 202.84.249.65 (202.84.249.65) 680.571 ms 679.806 ms 677.157 ms 23 202.84.249.66 (202.84.249.66) 755.965 ms 775.068 ms 757.381 ms 24 202.84.249.65 (202.84.249.65) 758.296 ms 754.893 ms 764.393 ms 25 202.84.249.66 (202.84.249.66) 833.034 ms 834.038 ms 832.465 ms 26 202.84.249.65 (202.84.249.65) 833.672 ms 832.952 ms 836.438 ms 27 202.84.249.66 (202.84.249.66) 910.692 ms 911.639 ms 910.117 ms 28 202.84.249.65 (202.84.249.65) 906.542 ms 908.851 ms 908.012 ms 29 202.84.249.66 (202.84.249.66) 991.594 ms 986.891 ms 987.188 ms 30 202.84.249.65 (202.84.249.65) 988.047 ms 985.131 ms 1053.931 ms bash-2.05$ whois -h whois.apnic.net 202.84.249.65 % Rights restricted by copyright. See http://www.apnic.net/db/dbcopyright.html % (whois6.apnic.net) inetnum: 202.84.248.0 - 202.84.251.255 netname: FIJI-HK descr: Fiji descr: 41/F, Telecom Tower descr: Taikoo Place, Quarry Bay descr: HK country: HK admin-c: AC11-HK tech-c: PW6-HK rev-srv: rs.hkt.net rev-srv: nsx.hkt.com notify: dbmon(a)apnic.net mnt-by: MAINT-HKT changed: wwong(a)hkt.net 960814 source: APNIC person: Aurea Cheung address: 41/F, Telecom Tower address: Taikoo Place, Quarry Bay address: HK phone: +852-28830025 fax-no: +852-29625290 nic-hdl: AC11-HK notify: dbmon(a)apnic.net mnt-by: MAINT-HKT changed: wwong(a)hkt.net 960814 source: APNIC person: Philip Watt address: 41/F, Telecom Tower address: Taikoo Place, Quarry Bay address: HK phone: +679-311300 nic-hdl: PW6-HK notify: dbmon(a)apnic.net mnt-by: MAINT-HKT changed: wwong(a)hkt.net 960814 source: APNIC -- Juha Saarinen --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

FW: Wireless LAN equipment
by Steven Perich 30 Aug '01

30 Aug '01

> Security, both physical and systems, is of utmost importance. The couch > might seem a perfect place to rack mount your equipment however it is by no > means secure. I would recommend mounting the switch and any other equipment > in a lockable cabinet, such as the oven (true geeks don't cook) and running > cable through a duct drilled through the back of it. Additionally, > electronic locking systems can be bolted to the hinged door and survelliance > installed throughout the kitchen. And the warmer drawer makes an ideal > place to store a change notebook, extra patch leads, etc. Oh! I almost forgot. After you've mounted your switch/router/firewall etc in your oven cum 19" rack, you can take advantage of the convenient Window Kit already installed. As well as being able to look in and watch the Pretty Blinking Lights(tm) at your convenience, you could install a neon light stick (such as http://www.thinkgeek.com/stuff/fun-stuff/3738.shtml) and wire it up to the oven's light switch! Other enhancements; lining the inside of the oven with black speaker box carpet and buying a small tubular lava lamp and strategically place it for maximum effect. :-) BTW: What the hell's this? http://www.eurus.dti.ne.jp/~yoshi-w/audio/zoom2/auto9.jpg Reckon it might end up on our shores in about 5 years time? Steve --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Wireless LAN equipment
by Sharpe, Russell 30 Aug '01

30 Aug '01

Hi Richard, If you only need 2Meg, rather than 11Meg, there are hundreds of 2M cards on the market cheap, which you could use in an "Ad Hoc" or Personal Area Network of about 20 metres. I have a couple that I could fire off to you if you so desire (I haven't the drivers, but I know that you are resourceful) Russell Sharpe -----Original Message----- From: Richard Stevenson [mailto:richard.stevenson(a)team.xtra.co.nz] Sent: Friday, 31 August 2001 17:02 To: nznog(a)list.waikato.ac.nz Subject: Wireless LAN equipment Hi all In the interests of keeping my soon-to-be-landlord happy, I'm looking at building a wireless LAN rather than making holes in the 13-month-old house I'm about to move into. Can anyone recommend any particular equipment, suppliers, sources of information? It'll only be a small network to start with - five systems, though it'll grow; I have a nasty habit of accumulating junk :P Many thanks Richard -- Richard Stevenson, Systems Specialist, Xtra Limited Phone: +64 9 355 5231 Mobile: +64 25 290 3101 Pager: +64 26 100 155 "Visual $ANYTHING" just screams out "100% suckage or your money back". -- Tanuki the Raccoon-dog, in the Monastery --------- 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

TSNZ international routes stuffed... again?
by Juha Saarinen 30 Aug '01

30 Aug '01

# ping www.above.net ping: unknown host www.above.net # ping www.mfnx.net ping: unknown host www.mfnx.net ... but, a few seconds later: # ping www.mfnx.net PING hs-d1.s.mfnx.net (64.125.31.9) from 192.168.1.1 : 56(84) bytes of data. --- hs-d1.s.mfnx.net ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss # ping www.above.net PING www.above.net (207.126.96.163) from 192.168.1.1 : 56(84) bytes of data. --- www.above.net ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss Happens quite frequently these days. -- 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 2

TSNZ <-> Above.net stuffed...
by Juha Saarinen 30 Aug '01

30 Aug '01

AFAICT. Anyone else seeing this? -- 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

[msa@samurai.sfo.dead-dog.com: Re: BGP Instability]
by Joe Abley 30 Aug '01

30 Aug '01

----- Forwarded message from "Majdi S. Abbas" <msa(a)samurai.sfo.dead-dog.com> ----- Delivered-To: jabley-nanog(a)automagic.org Delivered-To: nanog-outgoing(a)trapdoor.merit.edu Delivered-To: nanog(a)trapdoor.merit.edu Delivered-To: nanog(a)merit.edu Date: Thu, 30 Aug 2001 15:25:34 -0700 From: "Majdi S. Abbas" <msa(a)samurai.sfo.dead-dog.com> To: Mark Borchers <mborchers(a)splitrock.net> Cc: "'nanog(a)merit.edu'" <nanog(a)merit.edu> Subject: Re: BGP Instability User-Agent: Mutt/1.2i In-Reply-To: <CA47B6D616C0D211B92E0008C7C5657C115C1757(a)hscmpxsrvcl01>; from mborchers(a)splitrock.net on Thu, Aug 30, 2001 at 04:47:50PM -0500 Precedence: bulk Errors-To: owner-nanog-outgoing(a)merit.edu X-Loop: nanog On Thu, Aug 30, 2001 at 04:47:50PM -0500, Mark Borchers wrote: > Currently seeing unusually high numbers of routes being > dampened (~11K). The common denominator seems to be AS 4637 > in the as-path of most of the dampened prefixes. Is any > further information known? Yes. Telstra/4637 is leaking what appears to be a full table to many peers and at least two of their transit providers (that I've talked to). I called an engineer at Telstra and they expect to have this resolved soon. --msa ----- End forwarded message ----- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Speed of the list
by Dean Pemberton 29 Aug '01

29 Aug '01

Is it just me or is the list taking REALLY long to deliver things lately? Here is the message that I sent [lines removed] Aug 28 18:25:00 wilbur qmail: 998979900.410497 new msg 113746 Aug 28 18:25:00 wilbur qmail: 998979900.416632 starting delivery 57885: msg 113746 to remote nj.lee(a)plumtree.co.nz Aug 28 18:25:00 wilbur qmail: 998979900.416792 starting delivery 57886: msg 113746 to remote juha(a)saarinen.org Aug 28 18:25:00 wilbur qmail: 998979900.416836 starting delivery 57887: msg 113746 to remote nznog(a)list.waikato.ac.nz Aug 28 18:25:00 wilbur qmail: 998979900.832619 delivery 57887: success: 130.217.76.30_accepted_message./Remote_host_said:_250_2.0.0_ f7S6P0Y23521_Message_accepted_for_delivery/ Aug 28 18:25:01 wilbur qmail: 998979901.629689 delivery 57885: success: 203.79.82.83_accepted_message./Remote_host_said:_250_ok_9989 79901_qp_8921/ Aug 28 18:25:01 wilbur qmail: 998979901.759181 delivery 57886: success: 203.79.82.14_accepted_message./Remote_host_said:_250_OK_id=1 5bcJ3-0001YW-00/ Aug 28 18:25:01 wilbur qmail: 998979901.759326 end msg 113746 And here is when the list sent it out Aug 28 18:55:18 wilbur qmail: 998981718.390982 new msg 113746 Aug 28 18:55:18 wilbur qmail: 998981718.391126 info msg 113746: bytes 8254 from <owner-nznog(a)list.waikato.ac.nz> qp 26679 uid 64011 Aug 28 18:55:18 wilbur qmail: 998981718.392633 status: local 1/10 remote 0/20 Aug 28 18:55:18 wilbur qmail: 998981718.402411 new msg 115443 Aug 28 18:55:18 wilbur qmail: 998981718.402568 info msg 115443: bytes 8368 from <owner-nznog(a)list.waikato.ac.nz> qp 26682 uid 1004 Aug 28 18:55:18 wilbur qmail: 998981718.404193 status: local 2/10 remote 0/20 Aug 28 18:55:18 wilbur qmail: 998981718.404215 delivery 57919: success: did_0+1+0/qp_26682/ Aug 28 18:55:18 wilbur qmail: 998981718.404236 status: local 1/10 remote 0/20 Aug 28 18:55:18 wilbur qmail: 998981718.404256 end msg 113746 Aug 28 18:55:18 wilbur qmail: 998981718.411992 delivery 57920: success: did_1+0+0/ Aug 28 18:55:18 wilbur qmail: 998981718.412124 status: local 0/10 remote 0/20 Aug 28 18:55:18 wilbur qmail: 998981718.412146 end msg 115443 That took a long time. Dean --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

12 22

www.jetstream.co.nz branding Xtra after Telecom Web Site Change
by Craig Whitmore 29 Aug '01

29 Aug '01

Hi everyone... I've noticed after Telecom have revamped their new web site they are now pushing alot for Xtra on the Jetstream Web Site (http://www.jetstream.co.nz) Before the change.. it used to be "ISP Neutral", but now.. its Xtra, Xtra, Xtra :-( I don't know what other people (ISP's including) think.. but I think it should be back to how it was, not pushing any particular ISP, but explaining the service and then giving a list of ISP's to go to get Jetstream from. The First sentence "Get fast Internet access with JetStream. Join Xtra - New Zealand's leading Internet Service Provider." makes it look like Xtra is the only ISP who can offer the service. then "Get online with Xtra"... etc etc Even the links to order it.. make it look like Xtra only as it asks if you want as part of SkyFi as you can only get SkyFi by using Xtra as your ISP I talk for myself with these comments, not anyone I work with/for Thanks Craig Whitmore http://www.nzdsl.co.nz New Zealand DSL Information --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 8

fastnet... dns problems
by Chris Wedgwood 28 Aug '01

28 Aug '01

Sadly, I am still inflicted with Fastnet (ASB Bank's banking service) which by-and-large works most of the time except when I need it. Anyhow... I tried this a few minutes ago (www.asbank.co.nz) and couldn't get very very far, www.fastnet.co.nz works and closer examination shows the name-servers for asbbank.co.nz don't reply with anything useful for it... [1] So here is something fun... the name-servers are dead (or very lame at best), it's early in the morning (I tried this initially earlier this morning) and phones don't work... with no DNS, I can't email. Anyone know of a magic number to call? --cw [1] Insert standard rant, al la RFC2182 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

Hotmail ?
by Simon Byrnand 28 Aug '01

28 Aug '01

Anybody else having problems reaching hotmail ? I've been getting a TTL exceeded from p1-1.akbr2.global-gateway.net.nz (or similar) for the last 20 minutes or so, and yet all the other international sites I can think of seem fine.... Regards, Simon --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

6 7

Hmmm... a new one
by Juha Saarinen 27 Aug '01

27 Aug '01

I can only get to Xtra (from my Paradise ADSL connection) and then only barely: pts/0 juha(a)vimfuego:~$ ping www.xtra.co.nz PING xtra.co.nz (202.27.184.102) from 192.168.1.1 : 56(84) bytes of data. 64 bytes from 202.27.184.102: icmp_seq=0 ttl=246 time=30.164 msec 64 bytes from 202.27.184.102: icmp_seq=1 ttl=246 time=29.964 msec 64 bytes from 202.27.184.102: icmp_seq=2 ttl=246 time=29.970 msec 64 bytes from 202.27.184.102: icmp_seq=3 ttl=246 time=29.963 msec 64 bytes from 202.27.184.102: icmp_seq=4 ttl=246 time=29.968 msec 64 bytes from 202.27.184.102: icmp_seq=5 ttl=246 time=29.965 msec 64 bytes from 202.27.184.102: icmp_seq=6 ttl=246 time=29.936 msec --- xtra.co.nz ping statistics --- 76 packets transmitted, 8 packets received, 89% packet loss round-trip min/avg/max/mdev = 29.936/29.984/30.164/0.222 ms Can't see much of Paradise's network though: traceroute to 203.96.152.4 (203.96.152.4), 30 hops max, 38 byte packets 1 router (192.168.1.254) 1.796 ms 1.217 ms 1.371 ms 2 203-79-82-254.adsl-wns.paradise.net.nz (203.79.82.254) 22.081 ms 13.806 ms 16.697 ms 3 192.168.253.225 (192.168.253.225) 16.174 ms 16.354 ms 20.505 ms 4 kelly.ipnet2.paradise.net.nz (203.96.155.158) 22.172 ms 23.855 ms 19.808 ms 5 * * * 6 * * * 7 * * * pts/0 juha(a)vimfuego:~$ /usr/sbin/traceroute www.xtra.co.nz traceroute to xtra.co.nz (202.27.184.102), 30 hops max, 38 byte packets 1 router (192.168.1.254) 1.692 ms 1.201 ms 1.299 ms 2 203-79-82-254.adsl-wns.paradise.net.nz (203.79.82.254) 16.065 ms 14.954 ms 16.323 ms 3 192.168.253.225 (192.168.253.225) 16.985 ms 18.801 ms 20.093 ms 4 kelly.ipnet2.paradise.net.nz (203.96.155.158) 22.139 ms 18.807 ms 20.254 ms 5 203.96.152.3 (203.96.152.3) 20.158 ms 21.324 ms 20.173 ms 6 202.37.246.73 (202.37.246.73) 30.569 ms 31.820 ms 30.200 ms 7 202.50.245.105 (202.50.245.105) 31.149 ms 32.478 ms 30.773 ms 8 202.37.246.82 (202.37.246.82) 30.229 ms 33.314 ms 30.280 ms 9 202.37.245.46 (202.37.245.46) 31.539 ms 34.646 ms 30.416 ms 10 * * * 11 * * * Someone pulled the plugs out of Kelly? -- 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: Hotmail ?
by Simon Green 27 Aug '01

27 Aug '01

No problems for me (connected through ihug) -- simon >From: Simon Byrnand <simon(a)igrin.co.nz> >To: nznog(a)list.waikato.ac.nz >Subject: Hotmail ? >Date: Tue, 28 Aug 2001 13:37:18 +1200 > >Anybody else having problems reaching hotmail ? > >I've been getting a TTL exceeded from p1-1.akbr2.global-gateway.net.nz (or >similar) for the last 20 minutes or so, and yet all the other international >sites I can think of seem fine.... > >Regards, >Simon > > >--------- >To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz >where the body of your message reads: >unsubscribe nznog _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BNZ Buyline
by John Lynch 27 Aug '01

27 Aug '01

At the moment, I am writting the code in C, with Secure Remote for the link to the BNZ. In the long term I intent to use freeswan IPSEC, with linux. Thanks to all thouse who responded, (given me hope at least !!!) I understand that the work you guys have done may be copyrighted by you various companys, but for those of you that aren't, any code snippets would be 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 0

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

13 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