- NZNOG - lists.nznog.org

FW: [O/T] T1 -> E1 converter
by Gary Wicks 12 Sep '00

12 Sep '00

Shameless plug for our company, who can probably provide what you want! We have all sorts of technical equipment for hire, may have what you need or can source it. Call our sales office on 0800 832 473 or email t&msales(a)techrentals.co.nz Also rent computers/network equipment short or long term if anyone is interested, we have supplied major ISP's with servers, etc.... Gary Wicks Managing Director Tech-Rentals NZ Ltd Email: garyw(a)techrentals.co.nz -----Original Message----- From: owner-nznog(a)list.waikato.ac.nz [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of K. Anand Lal Sent: Friday, 8 September 2000 4:46 p.m. To: nznog(a)list.waikato.ac.nz Subject: [O/T] T1 -> E1 convertor I need a T1 -> E1 convertor for carrying out a few tests, and I don't want to spend $9000 to buy one. So far I haven't managed to find anyone in NZ that rents this gear out. Suggestions? Cheers, ----------------------------------------------------------- K. Anand Lal | ph: +64.9.3592767 Senior Network & Systems Engineer | +1.310.7399323 AS7657 | fax: +64.9.3581518 | noc: +64.9.3592708 ----------------------------------------------------------- --------- 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

DOMAINZ Review Terms of Reference
by DPF 08 Sep '00

08 Sep '00

I have been asked by ISOCNZ Council to draft up terms of reference for the independent review of DOMAINZ's new DRS or Domain Registration System. As this list would comprise a large proportion of the major agents and users I am seeking feedback on the draft terms before I send them formally to Council next week. Feedback is welcome to the list or direct to me. DRAFT TERM OF REFERENCE OF INDEPENDENT REVIEW The review is to be comprehensive and focus not just on the technical issue of the implementation of the DRS but the entire project from conception to the present day. The reviewer should include sections on, but not feel limited to: - system design - system implementation - risk management - governance - documentation - communications - technical issues - and most importantly recommendations Specific aspects that should be covered (but not limited to) are - final cost vs budgeted cost and reasons for any variations - details of responsibilities between ISOCNZ, DOMAINZ Board, DOMAINZ staff and any contractors including who approved and who recommended key details - A full listing of reported user problems with the new system, the reasons for them, have they been remedied and whether they were foreseeable. The lack of notification of zone changes to especially be covered - Details of consultation and feedback over the entirety of the project and how, if at all, this was fed into the final system. - A clear summary of what the perceived benefits of the new system were to various stakeholders (ISOCNZ, ISPs, Agents and users) and what input the stakeholders had into the fundamental concepts behind the design - What documentation was prepared for users of the systems, including ISPs and Agents, and the adequacy of such documentation The reviewer should at a minimum consult with (including traveling to interview if necessary) the following people and groups - DOMAINZ Board, DOMAINZ staff, ISOCNZ Councillors and Technical Committee, Contractors working on the project, major NZ based ISPs and Agents. Submissions from any interested party (including domain name holders) should also be called for. The principles of natural justice should be adhered to and any allegations or opinions should be put to the other parties concerned for their comment. The reviewer's report will be made public. If there is any evidence which can not legally be made public this should be referred to in the public report, but not detailed. A fuller report, if necessary, which includes confidential information shall go to the DOMAINZ Board only. DPF ________________________________________________________________________ <david at farrar dot com> NZ Usenet FAQs - http://www.dpf.ac.nz/usenet/nz ICQ 29964527 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Remote hands in Santa Clara, California.
by Rob Isaac 04 Sep '00

04 Sep '00

Folks, I've got a colo that needs to be dismantled in Santa Clara, California, USA. I'm having some trouble with the contractors we had arranged to do it, so I'm considering using someone else. Anyone have any clueful friends in the area, or have some contractors they might have used before? TIA. <R>< --------- 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 31 Aug '00

31 Aug '00

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. At last count the list had just under 170 subscribers, with the count growing by around five each month. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations (nor the administrator) is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ To search the archive, see http://list.waikato.ac.nz/archives/search.html (and remember to select nznog). Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog There are at present no restrictions on who may subscribe to the list, or even on who may post to the list. Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Other Activities NZNOG does not at present have other regular activities than this mailing list, though some Auckland subscribers have been known to meet over beer. Some subscribers are likely to attend the NetForum NZ 2000 conference in Hamilton in the first week of October. For further details of the conference, see http://www.uniforum.org.nz/netforum/ . 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

MEDIA: Sydney Morning Herald - Telstra Blacklist Story. (fwd)
by Alan Brown 27 Aug '00

27 Aug '00

---------- Forwarded message ---------- Date: Mon, 28 Aug 2000 14:42:56 +0900 From: Glenn Barry <gbarry(a)SYDNEY.NET> Subject: MEDIA: Sydney Morning Herald - Telstra Blacklist Story. Posted just for the record and future reference: http://www.smh.com.au/news/0008/28/bizcom/bizcom1.html ============================= Telstra on black list because of spamming Junk mail over the Net arouses strong passions. Kevin Morrison explores the issues. Telstra has long boasted that it wants to become a major player in the Internet world butmany in cyberspace accuse Telstra of harbouring the Internet community's number one enemy, spammers. "Spam" unsolicited emails have become the vehicle of 21st century snake-oil salesmen, offering various schemes and services, to millions of recipients. Spam clogs up email in-boxes, slows down Internet traffic and overloads the systems of Internet service providers, hence the unpopularity of its perpetrators. "They can really cause havoc because systems get overloaded and it is impossible to get off a spam list, so people get annoyed as the junk can take hours to clear," said one Internet user, who did not want to be named because of concerns that he would be targeted by spammers. Being the telecommunications carrier that transports the spam, Telstra has landed in hot water among the Internet community. Over the past three months Telstra has been among the most unpopular Internet organisations on "anti-spam" information Web site Spamcop (web address http://spamcop.net) "Telstra serves a country of 20 million people and yet it has been the most complained about network for several months. So Telstra has not got a good reputation in the Internet world," the Internet user said. Anti-spam groups such as ORBS and MAPS have formed to fight these rogues of the Net, with a mission to drive them off the Internet. The most effective way to do that is to cut off links to the telecommunications operator that allows spammers to connect to their network. The anti-spam groups have achieved some measure of success. In March US Internet backbone carrier AGIS (Apex Global Internet Services) was forced into bankruptcy after it became an outcast in the Internet community over its refusal to rid its network of spammers. "The anti-spam organisations should not be underestimated," the Internet user said. Last week ORBS temporarily put a black ban on Telstra, which meant that the 200 plus Internet service providers that subscribe to ORBS from around the world would not receive email coming from the Telstra network. Given that Telstra is the largest carrier of Internet traffic in Australia that means a lot of emails sent last week were bounced back to their senders, including messages sent from The Sydney Morning Herald email system to New Zealand-based ORBS administrator Mr Alan Brown. Mr Brown said Telstra had been put on the ORBS black list because of its slowness to disconnect notorious spammers. Mr Brown said Telstra's treatment of two alleged spammers, Mr Phil Basten and Mr Dean Westbury, who are directors of company named Global Web Solutions, had triggered the ORBS action. Telstra spokesman Mr Stuart Gray acknowledged the two men were spammers and that Telstra had cut their connection to its Big Pond service. Despite Telstra claims that the pair were disconnected, Messrs Basten and Westbury were still operating late last week. "They are playing the game of multiple names, multiple identities, and they keep on popping up. But it is hard to know that they are going to be spammers when they first set up," Mr Gray said. The two men are also being watched by the Australian Securities and Investment Commission. "We are monitoring some of the activities of these gentlemen," an ASIC spokeswoman said. However, Mr Basten told the Herald that he was not a spammer and that he and Mr Westbury provided Web-hosting services and programs that allowed customers to bulk mail. He said that some of his customers appeared to be spammers. "We didn't know anything about it. It looks like there are four out of about 100 customers that have been spamming and we had no way of knowing. "The first thing I knew about it was when Telstra closed down our service and that has cost us a lot of money. So I am going to get our lawyers and try and get that money back from Telstra," Mr Basten said. A Telstra spokesman said that they had enough evidence to prove that Mr Basten and Mr Westbury were spammers. Australia's Internet carriers have not been as active as their US counterparts in stamping out spamming. In the US, where spamming activities first started, ISPs have become more active in cutting spammers from their network, issuing heavy fines and strict conditions that customers must adhere to. Both Telstra and Optus claim to have stringent anti-spam policies on their networks, prohibiting users from carrying out "unacceptable Internet behaviour such as spamming." However, Mr Brown said both carriers had been very slow to react to spamming. "Optus have not responded to any complaints that I have made to them. The Cable & Wireless group worldwide has a bad reputation in the Internet community where they are known as Clueless and Witless," Mr Brown said. With the Internet increasingly moving to wireless platforms, such as WAP on mobile phones, spamming is expected to spread even further unless carriers jump on it. With several carriers expected to participate in the mobile Internet space, the choices will increase for spammers. --------- 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: WIX Route Reflectors
by James Tyson 21 Aug '00

21 Aug '00

> So, let me get this straight. He gets troubles when he receives routes > from you directly, and then again via the route server? Yeah. Turns out he's running some horrible system based on gated. > Which means that the other 40 odd peers of the route servers will no > longer have direct paths to xtra's networks (of that 40, maybe half are on > private ASN, so can't easily peer directly with xtra), and vice versa. > I'm happy to not send updates we receive from xtra on to users xtra peer > directly with, but I need you to tell me who those peers are. If you > don't want us to send Xtra updates Plain, I'll knock 'em on the head > immediately. Personally, I'd hope that was a better solution that just > dropping the route server peering completely (it's what we do for > Paradise and Netlink, for example). What we have been doing in the past (and what we are doing now, for that matter) is to add our routes into the mix, but not learn anything from the route reflectors. > Thats going to be a tad pointless, when you've dropped your peer, and > Matthew currently has his peering down! Can you cut and paste some > examples of where the route server is doing something wrong? 'praps you > could give me a call on 025 XXX XXX, or let me know your number, and I'll > call you. Yeah, I realised that just after I sent you the last mail. However, allowing routes from the WIX route reflectors to enter our network raises trust issues. The problem being, I know of you, Mr Blake, but I'm afraid I don't know you (god I love that line, thank's Chris Roberts for giving us the wing commander movie!). I would rather under-utilise our WIX connection by using only explicit domestic peering with other large peers, whom I know how to contact, than use route reflectors, both of which are under a completely different routing domain, and can potentially have conflicting policies with mine. This is not, however, a personal attack on yourself, your administrative abilities, or your network, but merely a statement of fact. I cannot allow routes from unknown and untrusted sources to be injected into my AS unless stringent measures are undertaken on your part to ensure the sanity of said advertisements. I will however allow our network to learn routes from you if you are able to give documented evidence that every route is under the strict control of the WIX. In an effort to help, I am willing to send you a prefix-list of Xtra's networks. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

ICMP broadcast amplifier list (fwd)
by Alan Brown 21 Aug '00

21 Aug '00

For those not on Bugtraq. ---------- Forwarded message ---------- Date: Mon, 21 Aug 2000 18:40:39 -0700 From: Troy Davis <troy(a)NACK.NET> To: BUGTRAQ(a)SECURITYFOCUS.COM Subject: ICMP broadcast amplifier list netscan.org has rechecked all routed /24s for ICMP directed broadcasts (smurf amplification) and made public the complete list of misconfigured networks. The probes ran from 8/18-8/21. The results are queryable and downloadable at http://netscan.org Cheers, Troy --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

None
by None 17 Aug '00

17 Aug '00

JAA25389 for <nznog(a)list.waikato.ac.nz>; Fri, 18 Aug 2000 09:55:31 +1200 Received: from localhost [127.0.0.1]=20 by uber.samizdat.co.nz with esmtp (Exim 3.12 #1 (Debian)) id 13PXd8-0007OO-00; Fri, 18 Aug 2000 09:55:18 +1200 Date: Fri, 18 Aug 2000 09:55:18 +1200 (NZST) From: James Tyson <james(a)samizdat.co.nz> Sender: eugene(a)uber.samizdat.co.nz To: David Zanetti <dave2(a)earthling.net> cc: nznog(a)list.waikato.ac.nz Subject: Re: Bizzareness and Oddity with IOS In-Reply-To: <Pine.LNX.4.10.10008180939580.13987-100000(a)wakko.wetstring.net= > Message-ID: <Pine.LNX.4.21.0008180953350.28229-100000(a)uber.samizdat.co.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=3DUS-ASCII > Hmmm.. very odd, 12.0(4)T with IP/FW leaked memory like there was no > tomorrow on our 3640 :) 12.0(7)T with the same features doesn't leak > memory (that I've noticed) and doesn't drop static routes either.. >=20 > Although they are different hardware platforms, so perhaps that'll make > the difference. I will obtain said image and try that :) We have found pretty much every IOS 12 release up until 12.0([10..11])S has been either unstable, leaked memory, or had some bug with one of the interface types we are running. That's on our 7500's though. Our 7200 VXR is running 11S and is as happy as larry, and has been for some time. James Tyson --- Samizdat New Media Solutions =20 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Weird BGP community stuff
by James Tyson 17 Aug '00

17 Aug '00

We have a router in Christchurch that seems to be sending community attributes to an EBGP peer, even though the neighbor statements dont contain the send-community argument. Does anyone know whats causing it? The router is running version 12.0(7)S1 on a 7500 series chasis. Also, on a somewhat related note, all domestic routes learned over WIX are being tagged with the community 9325:100, which is all cool. Our wix router does this: IPNWN1-B1#sh ip bgp 202.10.80.0 BGP routing table entry for 202.10.80.0/20, version 457621 Paths: (1 available, best #1, table Default-IP-Routing-Table) Advertised to non peer-group peers: 202.27.158.248 202.27.176.3 202.27.176.6 202.27.176.7 202.27.176.12 203.96.111.254 9718 202.7.0.78 from 202.7.0.78 (202.10.65.24) Origin IGP, metric 0, localpref 100, valid, external, best Community: 9325:100 The christchurch router says this: IPNCH1-B6#sh ip bgp 202.10.80.0 BGP routing table entry for 202.10.80.0/20, version 82178 Paths: (1 available, best #1) Advertised to non peer-group peers: 202.36.174.82 9718 202.7.0.78 (metric 179712) from 202.27.176.4 (202.27.185.135) Origin IGP, metric 0, localpref 100, valid, internal, best Community: 611123300 ^^^^^^^^^ - what is this?!?!? shouldnt it be 9325:100?? Any ideas anyone has would be helpful. James Tyson --- Samizdat New Media Solutions --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

RE: Weird BGP community stuff
by Ben Martel 17 Aug '00

17 Aug '00

James, Your 611123300 wierdo is actually just another way of representing 9325:100. It is really two sixteen bit values added together eg. 9325*65536 = 611123200 + 100 = 611123300 ( your answer) To change this representation you need to enter the IOS command: ip bgp-community new-format Cheers Ben > -----Original Message----- > From: James Tyson [mailto:james(a)samizdat.co.nz] > Sent: Friday, 18 August 2000 4:18 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: Weird BGP community stuff > > > > We have a router in Christchurch that seems to be sending > community > attributes to an EBGP peer, even though the neighbor > statements dont > contain the send-community argument. Does anyone know whats > causing it? > > The router is running version 12.0(7)S1 on a 7500 series chasis. > > Also, on a somewhat related note, all domestic routes learned > over WIX are > being tagged with the community 9325:100, which is all cool. Our wix > router does this: > > IPNWN1-B1#sh ip bgp 202.10.80.0 > BGP routing table entry for 202.10.80.0/20, version 457621 > Paths: (1 available, best #1, table Default-IP-Routing-Table) > Advertised to non peer-group peers: > 202.27.158.248 202.27.176.3 202.27.176.6 202.27.176.7 202.27.176.12 > 203.96.111.254 > 9718 > 202.7.0.78 from 202.7.0.78 (202.10.65.24) > Origin IGP, metric 0, localpref 100, valid, external, best > Community: 9325:100 > > The christchurch router says this: > > IPNCH1-B6#sh ip bgp 202.10.80.0 > BGP routing table entry for 202.10.80.0/20, version 82178 > Paths: (1 available, best #1) > Advertised to non peer-group peers: > 202.36.174.82 > 9718 > 202.7.0.78 (metric 179712) from 202.27.176.4 (202.27.185.135) > Origin IGP, metric 0, localpref 100, valid, internal, best > Community: 611123300 > ^^^^^^^^^ - what is this?!?!? shouldnt it be > 9325:100?? > > Any ideas anyone has would be helpful. > > James Tyson --- > Samizdat New Media Solutions > > > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0