- NZNOG - lists.nznog.org

Re: BGP at NZIX. Mmm.
by craig＠laptop.iprolink.co.nz 07 Feb '99

07 Feb '99

> Looks like another good reason to use a routing protocol that can be filtered > at NZIX :) But the article said it had only one in a million chance of happening. Apparently the latest version of IOS supports the following: redistribute static odds 1:1000000 ignore-filters -Craig --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

BGP at NZIX. Mmm.
by Joe Abley 06 Feb '99

06 Feb '99

http://www.idg.co.nz/nzweb/ca6a.html Looks like another good reason to use a routing protocol that can be filtered at NZIX :) Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZ Promiscuous Mail Relay Survey
by Joe Abley 06 Feb '99

06 Feb '99

Hi again, Further to my message on this subject the other day, I decided to send an informational note to postmaster addresses at hosts that I had found to be relays. Some readers of this list will have received copies. Although I have received quite a bit of positive feedback from the notes I sent out, it seems that I have inadvertantly upset some people. If you are one of them, then sorry - I didn't mean to intrude. I have put some information about the survey (and a list of the frequently- asked questions so far) at: http://www.patho.gen.nz/~jabley/survey.html Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NZ promiscuous relay survey
by Joe Abley 05 Feb '99

05 Feb '99

Last night I performed a crude survey in an attempt to find out something about the proportion of SMTP mail relays which permit promiscuous relaying in NZ. The methodology is by no means flawless, but it might give an idea of the scope of the problem. If anything, the proportion of mail relays which are open is understated, due to: + an incomplete list of mail relays in NZ to check; + a rather nasty SMTP implementation hacked together for this purpose that isn't very flexible and makes various poor assumptions; + mail relays which were broken at the time of the test; + mail relays which _will_ relay my mail back to be counted, but which haven't yet. Anyway, here are the results -- comments welcome! Out of 3751 MX hosts that we tried to use as a relay: + 269 (7%) accepted our message, but later bounced it + 1208 (32%) relayed our message OF the messages that were relayed: + 929 (76%) were from hosts named under co.nz + 33 (2%) were from hosts named under net.nz + 72 (5%) were from hosts named under govt.nz + 15 (1%) were from hosts named under ac.nz + 22 (1%) were from hosts named under school.nz + 0 (0%) were from hosts named under iwi.nz + 8 (0%) were from hosts named under gen.nz + 38 (3%) were from hosts named under org.nz + 1 (0%) were from hosts named under mil.nz I will not publish the list of MX hosts that did or did not permit relaying in this experiment. If you'd like to enquire about whether an MX host that you maintain relayed our message, please contact me directly. Methodology: 1. Zone transfers were performed for the NZ second-level domains co.nz, ac.nz, mil.nz, gen.nz, org.nz, school.nz, iwi.nz, and net.nz. 2. For every key in each of these zonefiles with an NS record, the key was extracted. A unique list of keys with NS records was generated. 3. MX records for each key were harvested from the DNS and a unique list of mail exchangers to be tested was produced. 4. A message with envelope sender jabley(a)patho.gen.nz and envelope recipient relayed(a)patho.gen.nz was sent by connecting to each relay and talking SMTP. Each message contained a random key which was stored in a local database. 5. Every time a message was received with a matching key in the body text and addressed to relayed(a)patho.gen.nz, the local database was updated indicating that the MX host in question permitted the relay. 6. All SMTP connections were made from tardis.patho.gen.nz (203.97.2.226) between 0500, Feb 5 1999 and 1400, Feb 6 1999. 7. MX hosts which specifically (intentionally) permit mail relaying from tardis.patho.gen.nz were excluded from summary reports. --------- 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: Traceroutes
by craig＠laptop.iprolink.co.nz 04 Feb '99

04 Feb '99

Hi. > I suspect many of you know of the DIGEX site which allows you to > traceroute (and other things) from a web page [...] My favorite "Address" to use with DIGEX (select "bgp"): regex _MYASNUMBER_ Obtaining a full BGP table dump is left as an exercise for the reader :-) -Craig --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

The APRICOT Week at a Glance ( Version 1.1 ) - The Asia Pacific Internet Festival of 1999
by Barry Raveendran Greene 01 Feb '99

01 Feb '99

[Apologies for the Duplications] !! Early Bird Sign up ends on 12 Feb! !! !! REGISTER NOW by Going to the on-line to !! !! http://www.apng.org/apricot/apricot.html !! !! and save $50 USD on registration cost !! The APRICOT Week at a Glance ( Version 1.1 ) The Asia Pacific Internet Festival of 1999 Venue: SunTec City Convention Centre, downtown Singapore Dates: 28 February 1999 to 7 March 1999 URL: http://www.apng.org/apricot99 (in English, Japanese, Korean, and Chinese) APRICOT'99 will consist of two days of tutorials (1-2 March 1999) and seminars followed by three days of conferences consisting of concurrent Technical, Business, Education, Policy and other tracks. (3-5 March 1999) In addition to other back-to-back meetings of Asia Pacific Internet organizations APNG, APNIC, APIA, APTLD, and their respective working groups, and other Internet conferences such as Internet World Asia @ Singapore 1999 and Singapore LINUX Conference 1999, APRICOT'99 will be hosting within its conference tracks: * ICANN Meeting, the Internet Corporation for Assigned Names and Numbers, the successor organization to IANA. (3 March 1999) * APPLe Policy Track * Women in IT BoF * APNG Education Track * APSIRC WG (Security CERTs and FIRSTs in Asia and Pacific) * Regional Internet eXchange Point (IXP) Update BOF * APIA Business Track In it's tradition of empowering the Internet community, APRICOT'99 will again offer unique tutorials that vital to an ISP's operations. These tutorials are presented by an instructor team that is the top %1 of the ISP Community. Through APRICOT, they are offering the ISP and Telco community knowledge, experience, and information that is not available in any other forum. Some of the material is unique - one time only at APRICOT'99. For example, "Tools Used at DIGEX and Verio to Manage Their Networks" by Randy Bush & Ed Kern, is unique in that the internal network techniques and tools of two US Tier 1 ISPs will be shared with any who come to the tutorial. New and existing ISPs/Telcos can learn from the first hand experience gained from two gurus and apply them to their networks. Here is a list of the APRICOT Tutorials: "ISP System Administration" by Barbara L. Dijker & Evi Nemeth "Sendmail Configuration and Operation" (Updated for Sendmail 8.9) by Eric Allman "Internet QoS and Traffic Management" by Geoff Huston "Internet Exchanges: The State of the Art" by Bill Manning "Designing Scaleable IP Networks" by Justin W. Newton "Optical Internetworking" by Marty Schulman "VoIP Standards Efforts and Impacts" by Scott Bradner "Routing Policy Specification Language and Analysis Tools" by David Kessens and Cengiz Alaettinoglu "Deploying VPN's and Secure Extranets" by Bruce Perlmutter "Managing Acceptable Use" by Barbara L. Dijker "Promoting Routability" by Philip Smith "Voice and Telephony Over IP" by Drew Freyman "IPv6: The New Version of the Internet Protocol" by Steve Deering "Tools Used at Digex and Verio to Manage Their Networks" by Randy Bush & Ed Kern "Security in All Seven Layers" by Gene Deutsch "Safeguarding The Business Process: E-Commerce Security" by Dr. Kelly Jones "Broadband Wireless Local Loop" by Dewyane Hendricks "Cable Modem Protocols and Technology" by Mark Laubach "APNIC Member Training: Address Policy & Administration" by Anne Lord & Paul Wilson ---------------------------------------------------------------------------- Note that all room numbers refer to those at the SunTec City - Singapore International Convention and Exhibition Center (SICEC) Date Time Room Event ---------------------------------------------------------------------------- MR 204 APNG I18n/XDSL WG (APNG WG SLAP Sunday, 28 0800-1230 cancelled) Feb MR 205 vacant 1300-1800 MR 209 APNG Disability SWG ENABLE'99 Symposium ---------------------------------------------------------------------------- 0900-1800 MR 208, 209, 8 APRICOT Tutorials 306, 308-314 MR204 APNG AP-ISOC Meeting (unconfirmed) 0800-1230 MR205 APNG APSIRC WG Meeting Monday, 1 Mar MR307 APNG-APTLD Meeting on Internationalisation of the DNS MR 206 APTLD Workshop on DNS Policy 1330-1800 MR 307 APNG General Meeting APNG Chairman's Commission 1830-2130 MR 307 Critical Infrastructure Protection ---------------------------------------------------------------------------- 0900-1800 MR 208, 209, 8 APRICOT Tutorials 306, 308-314 ICANN Board Committee Meetings Tuesday, 2 0800-1800 MR 204-207 (closed door) Mar 0800-1230 MR 307 APTLD Country Reports Track 1330-1800 MR 307 APTLD Membership General Meeting Evening To be APRICOT Opening Reception determined (unplanned) ---------------------------------------------------------------------------- APRICOT Opening and Plenary 0900-0945: MR 201 Keynote: Professor Dave Farber 0945-1300: MR 201 ICANN Open Track Wednesday, 3 1330-1700 MR 205 ICANN Open Track Mar 1330-1700 MR 202,203 2 APRICOT Technical Tracks 1330-1700 MR 208 APRICOT Business Track APRICOT BOF 1800 - 1930 To be - Peering/Exchanges determined - Y2K ---------------------------------------------------------------------------- APRICOT Plenary Keynote 0900-1000 MR 205 Chris Moore Van Jacobson Thursday, 4 1030-1700 MR 202,203 2 APRICOT Technical Tracks Mar 1030-1700 MR 208 APRICOT APNG Educational Track APRICOT BoFs 1800 - 1930 To be - iDNS determined - PGP signing - Women in IT BOF ---------------------------------------------------------------------------- APRICOT Plenary Keynote Ms Esther Dyson, ICANN 0900-1000 MR 208 Mr Leong Kheng Thai, Director General, Telecommunications Friday, 5 Authority of Singapore Mar 1030-1700 MR 208 APRICOT APPLe Policy Track 1030-1700 MR 202, 203 APRICOT Technical Track 1030-1700 MR 204 APNIC Executive Council Meeting Evening To be APRICOT Social Event(unplanned) determined ---------------------------------------------------------------------------- Saturday, 6 0800-1800 MR 202 APNIC Annual General meeting Mar 0800-1800 MR 201 APIA AGM ---------------------------------------------------------------------------- APRICOT Home Page http://www.apng.org/apricot99/index.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ APRICOT (Asia & Pacific Rim Internet Conference on Operational Technologies) Singapore March 1 - 5, 1999 -- The Annual ISP Operations and Business Summit in Asia and Pacific -- http://www.apricot.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

Traceroutes
by Michael Newbery 01 Feb '99

01 Feb '99

I suspect many of you know of the DIGEX site which allows you to traceroute (and other things) from a web page, but I was recently made aware of a whole page of similar sites, allowing traceroutes from almost anywhere in the world. DIGEX has proved most useful in the past in finding oddball misconfigurations, such as routes that go OUT one way and BACK quite another. <http://www.traceroute.org/> <http://nitrous.digex.net> -- Michael Newbery Technology Manager Saturn Communications Tel: +64-4-939 5102 Mobile:021-642 957 Fax:+64-4-939 5100 "There were no survivors sir. We'll have to find another test market." --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic
by Warwick GLENDENNING 27 Jan '99

27 Jan '99

> > On Mon, Jan 25, 1999 at 01:05:11PM +1300, Warwick GLENDENNING wrote: > > We(Waikato) currently still use OSPF on NZIX to collect NZ > routes. And this > > is vital to our traffic metering. A new metering system is > being built to > > use BGP4 to download NZ routes from our traffic provider. > Once this has been > > done, we will be very keen to download NZ routes from major > ISPs on NZIX and > > OSPF can be decommissioned. > > Supposing that a general agreement to move to BGP was made > earlier than > your planned roll-out - presumably as long as Telecom were > able to make > the NZ table available on OSPF to you, your requirements > would be satisifed? > This is true. > There is no particular necessity for us all to speak OSPF, > right? I would > assume that your particular requirements were an issue > between you and your > service provider, and not a general exchange issue. > > Just exploring ideas :) > This is true too. We only provide layer 2 connectivity. ISPs on NZIX don't have to follow some certain routing protocol. It should depend on their interest. But it should be said that Kawaihiko had multiple service providers and NZIX was the place where most of domestic traffic got exchanged. It's why Waikato has used OSPF to collect NZ routes from NZIX. Since Kawaihiko network broke up, we have been trying to build a new way to meter traffic. It will be appreciated very much if Clear can keep OSPF running until we have rolled out the new metering system. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

IOS configuration lint script
by Joe Abley 26 Jan '99

26 Jan '99

[This message has also been posted.] Hi, At various times I have been involved in maintaining routers with lots of (sub)interfaces, and lots of static routes pointing down those subinterfaces. Unfortunately, a simple "show run" on a router produces a listing with all the static routes listed together, and all the subinterfaces listed separately. On a router with a lot of static routes and a lot of connected networks, this becomes a bit of a headache - you end up with static routes hanging around long after the subinterface has been removed, and spring cleaning usually results at least a couple of confused and unhappy users for whom inbound traffic is now spiralling off somewhere else. Even when this kind of configuration is made automatically (from a database which enforces referential integrity), the odd quick-fix static route added at some time might well hang around for years after it has stopped being useful. I have often wished that I could do a "show run" which would group IOS configuration by customer. Now I can! Hooray! Take an IOS configuration file (as tftp'd or rsh'd somewhere, or perhaps retrieved using ciscoconfd) and pass it through this awk script. The configuration will be re-sorted, so that: + most configuration comes first + (sub)interface configuration comes next, with corresponding static routes + all other static routes come next + "end" The static routes corresponding to a connected (sub)interface are hence shown grouped with that subinterface. All static routes that don't point at a connected network are listed separately right at the end, where they can be scruitinised and (if appropriate) removed. Example: The following stripped-down configuration: version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 172.16.0.0 255.255.0.0 192.168.24.6 ip route 172.18.0.0 255.255.0.0 192.168.24.2 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! end When run through ios-lint.awk, we get: ! generated by cisco_lint.awk ! version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! ip route 172.18.0.0 255.255.0.0 192.168.24.2 ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! ip route 172.16.0.0 255.255.0.0 192.168.24.6 ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ! ! ! The following static routes do not point to a connected interface. ! Some of these might be worth looking at more closely :) ! ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! end Much nicer :) Anyway, sorry about all the bandwidth - script is at: http://www.patho.gen.nz/pub/users/jabley/ios-lint.awk Feedback welcome. Share and enjoy. Joe -- Joe Abley <jabley(a)clear.co.nz> I am not speaking for CLEAR. In fact, Network Architect, CLEAR Net I'm not speaking at all. I'm typing. --------- 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: BGP over NZIX
by Warwick GLENDENNING 25 Jan '99

25 Jan '99

Hi Felix Your email implies that you are waiting only for Waikato to implement BGP at NZIX. This does not appear to be a fair call, as no one else on the mailing list that Joe Abley posted to has made any comment on whether they would BGP peer or not at NZIX and especially the largest ISP in NZ Telecom. Regards Warwick -----Original Message----- From: tossan(a)us.ibm.com [mailto:tossan(a)us.ibm.com] Sent: Tuesday, 26 January 1999 08:19 To: WarwickG(a)waikato.ac.nz Cc: abley(a)clear.co.nz; nznog(a)list.waikato.ac.nz; lindsayp(a)agresearch.cri.nz; p.wilson(a)comnet.co.nz; steve(a)webmasters.co.nz; bpearson(a)telstra.co.nz; colinb(a)nz1.ibm.com; skatta(a)nz1.ibm.com; bowden(a)nz1.ibm.com; cholmes(a)telstra.co.nz Subject: BGP over NZIX IBM Global Network position re peering protocol, as explained earlier in teleconf, is we peer exclusively using BGP-4. We see no nationale in using OSPF to collect and distribute interprovider routes. In fact we have started to use BGP Communities within our global Internet BB to direct routes which previously was done by OSPF, thus further reducing OSPF role. Under the NZIX switching network we wish to pursue BGP peerings with all ISPs there who are capable, including Waikato. We await for Waikato to fully implement its BGP capability. Felix Tossan ---------------------- Forwarded by Felix Tossan/White Plains/IBM on 01/25/99 01:59 PM --------------------------- Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> on 01/24/99 07:05:11 PM To: "'Joe Abley'" <jabley(a)clear.co.nz>, Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> cc: nznog(a)list.waikato.ac.nz, "'lindsayp(a)agresearch.cri.nz'" <lindsayp(a)agresearch.cri.nz>, "'p.wilson(a)comnet.co.nz'" <p.wilson(a)comnet.co.nz>, "'steve(a)webmasters.co.nz'" <steve(a)webmasters.co.nz>, Felix Tossan/White Plains/IBM, bpearson(a)telstra.co.nz, colinb(a)nz1.ibm.com, skatta(a)nz1.ibm.com, bowden(a)nz1.ibm.com, cholmes(a)telstra.co.nz Subject: RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- 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