- NZNOG - lists.nznog.org

Update to Ihug Time Servers.
by Simon Lyall 22 Apr '04

22 Apr '04

[ This email is being sent to NZNOG and Bcc'd to about 100 people who have notified me that they are using Ihug's Time Servers. Apologies for any duplicates or errors. ] Ihug has made a small change to it's NTP servers which may affect people using them, Specifically: tk4.ihug.co.nz is going to be eliminated on 1st May 2004 tk3.ihug.co.nz had it's IP permanently moved yesterday (to 203.109.252.5) tk1.ihug.co.nz and tk2.ihug.co.nz are unchanged. If you are using tk4 then you will need to update your configuration, if you are using tk3 then you will need to ensure your NTP daemon is using it's new IP. Please use DNS of these machines in the config rather than IPs where possible. Please email me if you have any further questions. Also, If you are running a NTP server on a permanently connected machine you might want to look at joining the pool.ntp.org project , See http://www.pool.ntp.org/ for details. Currently New Zealand has around 5 servers in the project. -- Simon Lyall, | System Admin | Work: simon.lyall(a)ihug.co.nz Senior Engineer, | Network Admin | Home: simon(a)darkmere.gen.nz Ihug Ltd, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz

5 6

New Cisco Vulnerability - SNMP
by Gordon Smith 20 Apr '04

20 Apr '04

This came out today. Affected IOS's are 12.x series, including 12.3.6 http://www.cisco.com/warp/public/707/cisco-sa-20040420-snmp.shtml Page also lists which releases have been fixed - 12.3.x due mid May Cheers, Gordon

1 0

SANOG IV, Kathmandu, Nepal, 23-30 July 2004
by Joe Abley 18 Apr '04

18 Apr '04

[forwarded on behalf of the organisers] --- SANOG IV 23-30 July, 2004 Kathmandu, Nepal SANOG IV Program and Registration Announcement South Asian Network Operators Group (SANOG) IV program and agenda are now published on http://www.sanog.org/sanog4/. The registration has also now been opened. SANOG IV is being held at the Radisson Hotel in Kathmandu, Nepal from 23-30 July, 2004. You can refer to www.sanog.org for details. Program and Agenda: SANOG IV program incorporates the following Three hands-on workshops: 23-27 July, 2004 - Open Source IP Services for ISP, by NSRC - ISP Routing Workshop, by Cisco - DNS / DNSSec Workshop, by APNIC Eight Tutorials 28-29 July, 2004 - Anti-SPAM tutorial - Juniper Routing Workshop - VOIP technology and SIP Deployment - Internet Routing Registry Tutorial - Internet Exchange Point - Exim Mail Server - PGP mini Tutorial - APNIC Internet Resource Management Four Birds-of-a-Feather : 28-20 July, 2004 - Internet Exchange Point - ISP/NSP Security - West Asia BoF - PGP Key-Signing Party Full Day Conference Program : 30 July, 2004 - Regional Updates - Routing Practices - Application Deployment - Security Additional Programs: (28-30 July, 2004) - APCAUCE tutorials and meeting - APNIC Regional policy update - APNIC and RIPE NCC hostmaster Consultation - Regional Telecom/Internet Policy Session We expect a huge turn out from the region at this SANOG meeting owing to the popularity at previous meets. We also welcome participants from West Asia, with the newly established collaboration with the RIPE NCC. With the co-hosting of APCAUCE meeting, we also expect a larger participation from the entire Asia Pacific region. We hope you would be able to make it to this meeting. The meeting is open to everyone from the operational community, and thus anyone who needed a reason to visit Kathmandu now has one. You can register for SANOG by sending in the form available at www.sanog.org/sanog4. Online registration will open in May.

1 0

on the scrounge for a Cisco 3548 for APE.
by Simon Blake 18 Apr '04

18 Apr '04

Hi folks The active hardware at APE currently comprises a Cisco 3548 and 3508 pair. For the usual reasons, (and as part of some upcoming outages - more on this later), I'd like to replicate this. I have a spare 3508, but I'd really like a matching 3548 to go with it. So, the question, does anybody know of anybody in NZ who might have one they'd like to sell? They're no longer available from Cisco, so I thought I'd try the circle of friends first, before molesting the usual suspects (who'll doubtless try and sell me something newer and shinier). Cheers Si

1 0

CheckPoint Software
by Tim John - Domainz 16 Apr '04

16 Apr '04

Hi all, Can anyone recommend a reseller of Checkpoint software as I need a quote for upgrading. Also, does anyone have any experience between Checkpoint and PIX platforms ? I have very little experience of either so some 'pro' and 'con' arguments would be really helpful to me. Cheers, Tim

2 1

Issues with BIND
by Drew Broadley 15 Apr '04

15 Apr '04

I am having issues with a SINGLE domain "corrupt.co.nz", every other domain is fine! Here's the deal: Bind logs return nothing like they usually would saying there was an error with the domain. I can dig to ALL of my AUTH NS servers, and get the records returned no problemo. I can use XTRA, DTS (and a few others have used their own DNS servers) and get returned results without any SERVFAIL errors. I try to dig anything to the PARADISE NS servers (203.96.152{4,12}) and I get mixed results. I get www.corrupt.co.nz and corrupt.co.nz, but none of my overly important records (home.corrupt.co.nz, mail.corrupt.co.nz) It returns SERVFAIL id:2 whenever I try to request anything other then www.corrupt.co.nz / corrupt.co.nz via PARADISES NS Servers Any ideas? I have contacted soa(a)paradise.net.nz but god knows how long that will take to be processed. - Drew

5 6

Re: [nznog] Issues with BIND
by Mark Goldfinch 15 Apr '04

15 Apr '04

On Fri, 16 Apr 2004, Drew Broadley wrote: > I try to dig anything to the PARADISE NS servers (203.96.152{4,12}) and > I get mixed results. > > I get www.corrupt.co.nz and corrupt.co.nz, but none of my overly > important records (home.corrupt.co.nz, mail.corrupt.co.nz) > > It returns SERVFAIL id:2 whenever I try to request anything other then > www.corrupt.co.nz / corrupt.co.nz via PARADISES NS Servers ns1.dns.net.nz lists the nameservers for corrupt.co.nz as being: ns.iplay.net.nz. ns2.iplay.net.nz ns3.iplay.net.nz iplay nameservers list: ns1.iplay.net.nz. ns2.iplay.net.nz. ns3.iplay.net.nz. Which is okayish, however not entirely certain how badly this will affect things, ask the iplay servers about their own zone and you get a SERVFAIL for anything for within iplay.net.nz. You may want to ensure that the iplay nameservers reply for their own zone, otherwise bind may cache the SERVFAIL result for iplay records and then do the same for any zones which depend upon iplay records. Best Regards, --- Mark Goldfinch Senior Systems Administrator TelstraClear Ltd

1 0

RE: [nznog] Routing protocols
by Gordon Smith 15 Apr '04

15 Apr '04

> -----Original Message----- > From: Donald Neal [mailto:Donald.Neal(a)telecom.co.nz] > Sent: Friday, 16 April 2004 8:34 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Routing protocols > > > > In the words of Iljitsch van Beijnum's book "BGP", which I was reading > over Easter (I know, I'm a sad person): > > "If you are implementing a large-scale IP network or have unusual > requirements, you should definitely read up on all the > protocols so you > can make an informed decision. However, most small-to-medium sized > networks running just IP should go ahead and select OSPF: it does the > job, doesn't have any huge disadvantages, and is readily available." > > - Donald Neal > > Donald Neal | "I suspect most samba > Technical Specialist | developers are already > Operations Engineering | technically insane. Of course, > Integration & Services Divn. | since many of them are > Alcatel NZ Ltd | Australians you can't tell." > All opinions mine only. | - Linus Torvalds > > -------------------------------------------------------------- > ---------------- > "This communication, including any attachments, is confidential. > If you are not the intended recipient, you should not read > it - please contact me immediately, destroy it, and do not > copy or use any part of this communication or disclose > anything about it. Thank you. Please note that this > communication does not designate an information system for > the purposes of the Electronic Transactions Act 2002." > -------------------------------------------------------------- > ---------------- > What a terrible thing to be reading over easter :-) One advantage of using IS-IS is that if you're running both IPv4 and IPv6 on a network, you only need to run the one IGP for both. Doing both woth OSPF requires OSPFv2 and OSPFv3 :-( I did see a very good presentation some time ago (which may very well have been the AOL one that Joe mentioned) that detailed the transition to IS-IS where the network was live at the time. From memory, the primary reason for the change was the desire to move to an MPLS-capable network. Cheers, Gordon

1 0

RE: [nznog] Routing protocols
by Donald Neal 15 Apr '04

15 Apr '04

>> >> Yes... If you're thinking what I'm thinking, IS-IS is covered in the >> CCNP, CCDP and CCIP certification (and recertification) exams. And >> these are definites in the exam (not maybes). >> > http://www.cisco.com/warp/public/10/wwtraining/certprog/testing/current_ exams/642-801.html > Hey look on the bright side - at least you don't have to learn about > SNA for CCDP anymore. Um, given that CCIP is aimed at large ISP's or telcos, including IS-IS in it would seem to make sense. The funny thing is that IS-IS is included in the CCNP recertification exam, but _not_ the CCIP recertification exam. - Donald Neal Donald Neal | "I suspect most samba Technical Specialist | developers are already Operations Engineering | technically insane. Of course, Integration & Services Divn. | since many of them are Alcatel NZ Ltd | Australians you can't tell." All opinions mine only. | - Linus Torvalds ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

Routing protocols
by nznog 15 Apr '04

15 Apr '04

What routing protocols do people use on their networks? Particularly inside. Does anyone in the world actually use IS-IS ? I am not interested in what network runs what, just how many networks run various protocols. Rough idea of network size would be nice, and any partcular reasons you prefer one to the other. thanks for satisfying my curiosity JM -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBD2JfrwRBACWgDlX/IoNxdk15KpELdl6Sou4cU0sbaBinYV7X12SoR3YljuM lJlhgtoahIdUkqOuvDmX1AUNY2a80sidbTA48B0QUzYrGnktPoBxz4O29LKm49t3 Ojoqj0AsnC6HB37N5pScATqMbXME8hkjACHvukSUvgjHiPRYaMz7WQ2W0wCg3t09 ErzU4f+J+8fExfcd8B1+ce0EAIsc5GlVeK6hTBf3XyTRFbLD0C2m+BZGamrpngmb ito2vhKxbxTHLR/Qy2nbvN4bT42CCnf4v5MguPepqbMT8V6hxXKxxUzJx3A67x6m 7e0Qag4TLopc7f7mY5bTk1yY2mjAg1b+uVEuxMxGVtFkm586aOpmQVfAAgtffsrl CLTlA/94q8gjqHk8A9funzsjlZKft1+Z+NpGObfw9M9cC7c8RJAdK8kusH7/oKb2 Yq9NsSSdULJiqZaKkH4aCV55yvDnF3b6BZQOGvqpYuSACSJoX+fEwASGL0Qq0Jym ykaxwyNKqvUdxuYb9TPU01O3OpTyAvI0DsyjJ+KGS9h9mZwPX7QtSmFtZXMgTWFo ZXIgKGg0eDByKSA8c2NvdXNlckBwYXJhZGlzZS5uZXQubno+iF0EExECAB0FAj2J frwFCQPCZwAFCwcKAwQDFQMCAxYCAQIXgAAKCRAlRgQ5B5O8vFi8AJsG0xt5FRG1 F10FJFblBhmtc4//vwCgnUmaClr8+F+qe4Rm9wnYqWyjF4S0JUphbWVzIE1haGVy IDxqYW1lcy5tYWhlckBpcmQuZ292dC5uej6IXQQTEQIAHQUCPYmWnwUJA8JnAAUL BwoDBAMVAwIDFgIBAheAAAoJECVGBDkHk7y8MvUAnRxhOIq1IAo239VFcBfN2IdZ XEehAJ9U0BB2ZZ8PjNWI1yvjzJ5P3B5lv7QhSmFtZXMgWCA8c2NvdXNlckBwYXJh ZGlzZS5uZXQubno+iF0EExECAB0FAj22c0sFCQPCZwAFCwcKAwQDFQMCAxYCAQIX gAAKCRAlRgQ5B5O8vNLkAKDZ4x+lDWYoBPVViuX37Tbd51golgCgiciBW3djy3wV 11Jdz3x38O5JwRW5Ag0EPYl+yhAIAL7K7wrwGjvgRRS+rh5hW8JJbrYQn0BvajTs Vm/OvtA5QdJN1zqBNBlGCM1OivxASjAZEmpUYMAnBcUjNicXaIu/WoB0AUPSmkZ7 4NHyWoU12cbHZw6pZno4OZ9DpwSIsOkaP5rDB8oaj9b9/nziuxBm3oqmKN64ohcN oSOFJ/4+66vEDM8I1p+4pvb2Jj5JYRS/5+piJEaBUFttHofRWkF34vnxR3c+MjY7 NSVWbu3EWtJV+se+MLeSdDZxzt4v7XD7wE/lt9xq9IlyOryQvRhqrduaYc0ABItd eashGzyDXeUCFhsyFszZG51cAP6FiYQiD9ztwNHUKhLzjcqDJTMAAwYIAL1D9sdU 8+BI3jH1HhPiM8VLq1zii8ksRw77iUthpfe7xMp8qhiachMdXnIMYlIskEiFP3nt BycQlPYBNOV96YEhnBngiBXbC40xgxXSkpJh24Fu6GbXAlLMnahkQeRSMjAcDJuh bNcYfwm+PE86g9XyLCDVByzSQ+bRY7Dof+Sjgtod4Ds4tYA3R3qgYE0Co1dtrf4z b58PlnaSAq9wVtMD0G8Da/n5MC8jsAcHZahfBqmwvKsGENH8zFVwsAeKDjQv075m tO+V96QxCMYuvJeVWWYvL/bIR2zya9yD6RCWds1IBljUIwLI+Ox4Dd3LfBT1Y2g3 x8DNsYXPOCPYWCyITAQYEQIADAUCPYl+ygUJA8JnAAAKCRAlRgQ5B5O8vA6DAJ4v ulRjiKp8UZ5iqCSFvboQRoM4zgCcCunR39pnorxd2ZxIi+miFuPx75U= =siNl -----END PGP PUBLIC KEY BLOCK-----

2 1