From sgoldste@cise.cise.nsf.gov Tue Sep 1 07:21:46 1992 Received: from cise.cise.nsf.gov by merit.edu (5.65/1123-1.0) id AA19934; Tue, 1 Sep 92 07:21:46 -0400 Received: by cise.cise.nsf.gov id ; Tue, 1 Sep 92 07:21:06 -0400 Message-Id: <9209011121.AA12945@cise.cise.nsf.gov> To: George Brett , "Brewster E. Kahle,WIAS" Cc: cert@sei.cmu.edu, scottw@nic.ddn.mil (Scott Williamson), nsfnet-cert Subject: security hole in swais, FYI Date: Tue, 01 Sep 92 07:20:58 EDT From: Steve Goldstein--Ph +1-202-357-9717 George and Brewster, Please take note of this and act accordingly. (Thanks for the heads-up, Scott! I took the liberty of alerting the CERT with a cc: The community of serving organizations should be notified and the fix provided, when proven. If I'm behind the power curve, and if you have already done this, please excuse my misplaced zeal.) Thanks, Steve G. ------- Forwarded Message From: scottw@nic.ddn.mil (Scott Williamson) Message-Id: <9208312050.AA22641@nic.ddn.mil> Subject: Re: WAIS on DDN To: sgoldste@cise.cise.nsf.gov (Steve Goldstein--Ph +1-202-357-9717) Date: Mon, 31 Aug 92 16:50:13 EDT In-Reply-To: <9208282127.AA06081@cise.cise.nsf.gov>; from "Steve Goldstein--Ph +1-202-357-9717" at Aug 28, 92 5:27 pm X-Mailer: ELM [version 2.3 PL2] Steve, We have the login wais disabled. There is a security whole in the swais interface that you can drive a truck through. We are working on a fix so that we reactivate this feature. Mark Kosters has informed RIPE of the problem with an explanation of how one could get in. He also suggested the fix. Scott > > > >SG> And, folks, what you really want to see is NIC databases accessible > >SG> with WAIS, so's you don't have to use their search fields, > >SG>but can > >SG> use any search string (e.g., telephone number, city, etc.) > >SG>NIC.DDN.MIL > >SG> has just brought up a WAIS server, and RIPE NCC has had one > >SG>up for a while > >SG> (wais.ripe.net). These are REALLY neat, as in "who does networking > >SG>in > >SG> Dresden?" --SG > > > >I've managed to telnet to wais.nic.ddn.mil (192.112.38.103) > >but don't know the login/password. Can you advise? > > > Sorry. I did it with a WAIS client. I just tried logging in a telnet > session with user=wais, password=, > but nothing worked. Ought not be passworded! > > Scott? > > --SG > >Ripe works fine. > > > >Regards, > >Peter Scott > ------- End of Forwarded Message - - - - - - - - - - - - - - - - - From rty Tue Sep 1 09:06:27 1992 Received: by merit.edu (5.65/1123-1.0) id AA23746; Tue, 1 Sep 92 09:06:51 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA23708; Tue, 1 Sep 92 09:06:27 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA12739; Tue, 1 Sep 92 09:06:25 EDT Date: Tue, 1 Sep 92 09:06:25 EDT Message-Id: <9209011306.AA12739@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 146.107 Network Name: GSF-NET Location: GSF - Forschungszentrum fuer Umwelt und Gesundheit GmbH, Rechenzentrum, Ingolstaedter Landstrasse 1, D-W-8042 Neuherberg, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 155.33 Network Name: NEASTU-NET2 Location: Northeastern University, 360 Huntington Avenue, Boston, MA 02115, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 161.80 Network Name: EPANESC Location: U.S. Environmental Protection Agency, Highway 54 & Alexander Dr., Research Triangle Park, NC 27711, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 161.130 Network Name: MUHSCNET Location: University of Missouri-Columbia, Campus Computing, 200 Heinkel Bldg., Columbia, MO 65211, USA Country Code: US 1:93 Midnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.70.213 Network Name: GREBYN-NET Location: Grebyn Corporation, P.O. Box 497, Vienna, VA 22183-0497, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.77.167 Network Name: ANS-CNET17 Location: ANS-Reston, 1875 Campus Commons Drive, Campus South Building, 2nd Floor - Suite 220, Reston, Virgina, 22091, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.109.42 Network Name: POP-BERLIN Location: IN, Stephanstr. 7, D-W-1000 Berlin 21, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.148.167 Network Name: SPRITEL Location: SPRI, S.A., Programa SPRITEL, Parque Tecnologico, Edificio 103, E-48016 ZAMUDIO (VIZCAYA), SPAIN Country Code: ES 1:590 EASInet Regional Network Network IP: 192.187.8 Network Name: ARL-VA-US1 Location: University of Southern California / Information Sciences Institute, 4001 N. Fairfax Dr., Ste 670, Arlington, VA 22203, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.190.3 Network Name: LANCITY-NET Location: LANcity Company, 100 Brickstone Square, Andover, MA 01810, USA Country Code: US 1:1384 NEARnet Regional Network 2:1383 NEARnet Regional Network 3:560 NEARnet Regional Network 4:281 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.32 Network Name: GUPS-NET-1 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.33 Network Name: GUPS-NET-2 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.34 Network Name: GUPS-NET-3 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.35 Network Name: GUPS-NET-4 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.36 Network Name: GUPS-NET-5 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.37 Network Name: GUPS-NET-6 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.38 Network Name: GUPS-NET-7 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.39 Network Name: GUPS-NET-8 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.40 Network Name: GUPS-NET-9 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.41 Network Name: GUPS-NET-10 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.42 Network Name: GUPS-NET-11 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.43 Network Name: GUPS-NET-12 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.44 Network Name: GUPS-NET-13 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.45 Network Name: GUPS-NET-14 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.46 Network Name: GUPS-NET-15 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.96.47 Network Name: GUPS-NET-16 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Total configured T1 networks: 6385 T3 Network: ---------- Network IP: 129.125 Network Name: RUGNET Location: RUG University, Paddepoel-terrein, Landleven 1, Groningen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 130.89 Network Name: UTNET Location: University Twente, Postbox 217, 7500 AE Enschede, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 130.112 Network Name: ECN-NET Location: Netherlands Energy Research Foundation ECN, Westerduinweg 3, 1755 Le Petten, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 130.115 Network Name: EURNET Location: Erasmus University Rotterdam, Burg. Oudlaan 50, 3062 PA Rotterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 130.161 Network Name: DUNET Location: Technische Universiteit Delft, Wippolder, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 131.155 Network Name: TUENET1 Location: Eindhoven University of Technology, Den Dolech 2, Eindhoven, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 131.174 Network Name: NUNET Location: University of Nijmegen, Computer and Communications Department, Faculty of Science, Toernooiveld 1, 6525 ED, Nijmegen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 131.211 Network Name: RUUNET Location: Universiteit Utrecht, Budapestlaan 8, NL- 3584 CD Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 132.229 Network Name: RUL-NL Location: Leiden University, Leiden, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 136.231 Network Name: DELFTHYDRAUL Location: Delft Hydraulics Network De Voorst, P.O. Box 152, NL-8300 AD Emmeloord, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 137.17 Network Name: NLRNET Location: National Aerospace Laboratory, Voorsterweg 31, 8316 PR Marknesse, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 137.56 Network Name: KUBNET-B Location: Tilburg University, Hogeschoollaan 225, Tilburg, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 137.120 Network Name: MAASNET Location: Rijks Universiteit Limburg, p/a Rekencentrum, P.O. Box 616, NL-6200 MD Maastricht, Holland, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 137.224 Network Name: WAU-NET Location: Wageningen Agricultural University, Dreyenplein 2, 6703 HB Wageningen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 139.63 Network Name: PTT-RESEARCH Location: PTT Research, Dr. Neher Laboratorium, St. Paulusstraat 4, P.O. Box 421, 2260 AK Leidschendam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.1 Network Name: NIOZ Location: Nederlands Instituut voor Onderzoek der Zee, Landsdiep 4, Den Hoorn - Texel, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.2 Network Name: IJSELLAN Location: Rijkshogeschool Ijseland, Gibsonstraat 10, Deventer, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.3 Network Name: DELFTGEOT Location: Grondmechanica Delft, Stieltjesway 2, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.5 Network Name: CADANSNET Location: Stichting CADANS, Catharijnesingel 52, Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.9 Network Name: DELFTHYDRO Location: Waterloopkundig Laboratorium, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.18 Network Name: UVANET1 Location: University of Amsterdam, Turfdraagsterpad 9, NL - 1012 XT Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.23 Network Name: KNMI-NET Location: Royal Netherlands Meteorological Institute, P.O. Box 201, 3730 AE DE BILT, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.24 Network Name: HRONET Location: Hogeschool Rotterdam & Omstreken, Rochussenstraat 125, 3015 EJ Rotterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.25 Network Name: IAMPET-IPNET Location: Institute for Advanced Materials, SURFnet BV, P.O. Box Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.30 Network Name: AMSMSS Location: Koninklijke/Shell-Laborotorium Amsterdam, P.O.Box 3003, NL - 1003 AA Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 145.36 Network Name: ESPIP1 Location: Elsevier Science Publishers BV, P.O. Box 211, NL-1000 AE Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 146.107 Network Name: GSF-NET Location: GSF - Forschungszentrum fuer Umwelt und Gesundheit GmbH, Rechenzentrum, Ingolstaedter Landstrasse 1, D-W-8042 Neuherberg, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 147.12 Network Name: MARSUR Location: Maritime Research Institute Netherlands MARIN, Hageweg 2, NL-6708 PM Wageningen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 155.33 Network Name: NEASTU-NET2 Location: Northeastern University, 360 Huntington Avenue, Boston, MA 02115, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 161.80 Network Name: EPANESC Location: U.S. Environmental Protection Agency, Highway 54 & Alexander Dr., Research Triangle Park, NC 27711, USA Country Code: US 1:81 CONCERT Network IP: 161.130 Network Name: MUHSCNET Location: University of Missouri-Columbia, Campus Computing, 200 Heinkel Bldg., Columbia, MO 65211, USA Country Code: US 1:93 ENSS 140, Lincoln, Nebraska Network IP: 192.16.185 Network Name: IKONET Location: NIKHEF section K, Science Park Watergraafsmeer, Kruislaan 407-415, NL-1009 Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.186 Network Name: HEF-DOMAIN Location: NIKHEF section H, Science Park Watergraafsmeer, Kruislaan 407-415, NL-1009 Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.188 Network Name: SARA-LAN Location: Stichting Academisch Rekencentrum, Science Park Watergraafsmeer, Kruislaan 407-415, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.189 Network Name: AMOLF Location: FOM Institute for Atomic and Molecular Physics, Science Park Watergraafsmeer, Kruislaan 407-415, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.194 Network Name: IKO-DOMAIN Location: NIKHEF section K, Science Park Watergraafsmeer, Kruislaan 407-415, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.195 Network Name: HEF-ANNEXNET Location: NIKHEF section H, Science Park Watergraafsmeer, Kruislaan 407-415, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.16.199 Network Name: HEFNET Location: Local Ethernet, NIKHEF section H, Science Park Watergraafsmeer, Kruislaan 407-415, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.31.125 Network Name: DUNET-A Location: Technische Universiteit Delft, Wippolder, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.31.126 Network Name: DUNET-B Location: Technische Universiteit Delft, Wippolder, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.31.127 Network Name: DUNET-C Location: Technische Universiteit Delft, Wippolder, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.31.128 Network Name: DUNET-D Location: Technische Universiteit Delft, Wippolder, Delft, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.113 Network Name: AMC-NET Location: University of Amsterdam, Academic Computing Services Amsterdam, P.O. Box 4613, 1009 AP Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.114 Network Name: NKI Location: Netherlands Cancer Research Institute, P.O. Box 4613, 1009 AP Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.123 Network Name: UVA-PHYS Location: Universiteit van Amsterdam, Vakgroup Experimentele Fysica, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.124 Network Name: RIJNH Location: FOM Instituut voor Plasmafysica "Rijnhuizen", c/o SARA - Academic Computing Services Amsterdam, P.O. Box 4613,1009 AP Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.125 Network Name: AMC-NET2 Location: University of Amsterdam, Academic Medical Center - Amsterdam, Kruislaan 415, NL-1098 SJ Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.126 Network Name: RIJNH2 Location: Euratom - FOM Association, FOM Institute for Plasmaphysics "Rijnhuizen", P.O. Box 1207, NL-3430 BE Nieuwegein, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.42.127 Network Name: SWIDOC Location: Sociaal Wetenschappelijk Informatie en Documentatie Centrum, Herengracht 410-412, NL-1017 BX Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.65.81 Network Name: SIPLAN Location: SURFnet BV, Godebaldkwartier 24, Hoog Catharijne, Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.70.213 Network Name: GREBYN-NET Location: Grebyn Corporation, P.O. Box 497, Vienna, VA 22183-0497, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.77.167 Network Name: ANS-CNET17 Location: ANS-Reston, 1875 Campus Commons Drive, Campus South Building, 2nd Floor - Suite 220, Reston, Virgina, 22091, USA Country Code: US 1:1934 ANS, Reston, Virginia Network IP: 192.87.1 Network Name: NFRA Location: Netherlands Foundation for Research in Astronomy, Oude Hogeveensedijk 4, Dwingeloo, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.5 Network Name: SNET-AT-KUN Location: SURFnet at KU Nijmegen, Geert Grooteplein Zuid 41, Nijmegen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.17 Network Name: UTLEEUWARDEN Location: University Twente, Postbox 217, 7500 AE Enschede, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.30 Network Name: RARE-SEC-LAN Location: RARE Secretariat, Singel 466-468, NL-1017 AW, Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.32 Network Name: SLIP-NET Location: SURFnet SLIP Network / SARA, Kruislaan 415, NL-1098 SJ Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.33 Network Name: NKIRTCLIN Location: Nederlands Kanker Instituut, Afdeling Radiotherapie, Plesmanlaan 121, NL-1066 CX Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.34 Network Name: NKIRT Location: Nederlands Kanker Instituut, Afdeling Radiotherapie, NL-1066 CX Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.36 Network Name: SNET-AT-TUD Location: SURFnet IP LAN at TUDelft, SURFnet BV, P.O. Box 19035, NL-3501 DA Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.45 Network Name: RIPE-NCC Location: RIPE Network Coordination Centre, Kruislaan 413, NL-1098 SJ Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.46 Network Name: SNET-AT-RUU Location: SURFnet IP LAN at Rijks University - Utrecht, NL-3584 CD Utrech, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.49 Network Name: ROB-IPNET Location: Rijksdienst voor het Oudheidkundig Bodemonderzoek, Kerkstraat 1, NL-3811 CV Amersfoort, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.50 Network Name: SWETS Location: Swets & Zeitlinger BV, P.O. Box 855, NL-2160 SZ Lisse, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.109.42 Network Name: POP-BERLIN Location: IN, Stephanstr. 7, D-W-1000 Berlin 21, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 192.187.8 Network Name: ARL-VA-US1 Location: University of Southern California / Information Sciences Institute, 4001 N. Fairfax Dr., Ste 670, Arlington, VA 22203, USA Country Code: US 1:1972 DARPA Network IP: 192.190.3 Network Name: LANCITY-NET Location: LANcity Company, 100 Brickstone Square, Andover, MA 01810, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 193.96.32 Network Name: GUPS-NET-1 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.33 Network Name: GUPS-NET-2 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.34 Network Name: GUPS-NET-3 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.35 Network Name: GUPS-NET-4 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.36 Network Name: GUPS-NET-5 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.37 Network Name: GUPS-NET-6 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.38 Network Name: GUPS-NET-7 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.39 Network Name: GUPS-NET-8 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.40 Network Name: GUPS-NET-9 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.41 Network Name: GUPS-NET-10 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.42 Network Name: GUPS-NET-11 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.43 Network Name: GUPS-NET-12 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.44 Network Name: GUPS-NET-13 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.45 Network Name: GUPS-NET-14 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.46 Network Name: GUPS-NET-15 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 193.96.47 Network Name: GUPS-NET-16 Location: Garmhausen & Partner Service GmbH, Alte Bottroper Str. 39, D-W-4300 Essen 11, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Total configured T3 networks: 5676 The following T3 routers have also been added: AS Number: 1664 AS Notes: Mead Data Central AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.193 - Mead Data Central, Miamisburg, Ohio - ENSS193 Miamisburg, Ohio, USA Gate: 192.73.216.1 - meaddata-gateway.jvnc.net Mead Data Central, Miamisburg, OH AS Number: 1810 AS Notes: NEARnet-2 AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.134 - bo-enss Boston, Mass Gate: 192.54.222.1 - w91-cisco-external-ether.mit.edu NEARnet, Boston, MA AS Number: 1972 AS Notes: DARPA AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.146 - DARPA Arlington, VA Gate: 192.187.8.2 - unknown, DARPA DARPA, Arlington, VA ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET --Steve Widmayer Merit/NSFNET - - - - - - - - - - - - - - - - - From brewster@quake.think.com Tue Sep 1 09:29:45 1992 Received: from Quake.Think.COM by merit.edu (5.65/1123-1.0) id AA24553; Tue, 1 Sep 92 09:29:45 -0400 Received: by quake.think.com (4.1/SMI-4.0) id AA17908; Tue, 1 Sep 92 06:29:20 PDT Date: Tue, 1 Sep 92 06:29:20 PDT Message-Id: <9209011329.AA17908@quake.think.com> From: Brewster Kahle Sender: brewster@quake.think.com To: scottw@nic.ddn.mil Cc: jcurran@NNSC.NSF.NET, jonathan@think.com Cc: ghb@concert.net, sgoldste@cise.cise.nsf.gov Cc: cert@sei.cmu.edu, nsfnet-cert In-Reply-To: Steve Goldstein--Ph +1-202-357-9717's message of Tue, 01 Sep 92 07:20:58 EDT <9209011121.AA12945@cise.cise.nsf.gov> Subject: security hole in swais, FYI Scott, There seems to be a problem with swais, could you please explain? We have been running it under a chroot for over a year now with no known problems. I am the project leader of WAIS and oversaw its development, so I would like to make sure this problem is understood and extinguished. John Curran of NNSC wrote the original version, Jonathan has been the maintainer of it and extender. Just to take a guess, are you running it for public login without doing a chroot? -brewster Date: Tue, 01 Sep 92 07:20:58 EDT From: Steve Goldstein--Ph +1-202-357-9717 George and Brewster, Please take note of this and act accordingly. (Thanks for the heads-up, Scott! I took the liberty of alerting the CERT with a cc: The community of serving organizations should be notified and the fix provided, when proven. If I'm behind the power curve, and if you have already done this, please excuse my misplaced zeal.) Thanks, Steve G. ------- Forwarded Message From: scottw@nic.ddn.mil (Scott Williamson) Message-Id: <9208312050.AA22641@nic.ddn.mil> Subject: Re: WAIS on DDN To: sgoldste@cise.cise.nsf.gov (Steve Goldstein--Ph +1-202-357-9717) Date: Mon, 31 Aug 92 16:50:13 EDT In-Reply-To: <9208282127.AA06081@cise.cise.nsf.gov>; from "Steve Goldstein--Ph +1-202-357-9717" at Aug 28, 92 5:27 pm X-Mailer: ELM [version 2.3 PL2] Steve, We have the login wais disabled. There is a security whole in the swais interface that you can drive a truck through. We are working on a fix so that we reactivate this feature. Mark Kosters has informed RIPE of the problem with an explanation of how one could get in. He also suggested the fix. Scott > > > >SG> And, folks, what you really want to see is NIC databases accessible > >SG> with WAIS, so's you don't have to use their search fields, > >SG>but can > >SG> use any search string (e.g., telephone number, city, etc.) > >SG>NIC.DDN.MIL > >SG> has just brought up a WAIS server, and RIPE NCC has had one > >SG>up for a while > >SG> (wais.ripe.net). These are REALLY neat, as in "who does networking > >SG>in > >SG> Dresden?" --SG > > > >I've managed to telnet to wais.nic.ddn.mil (192.112.38.103) > >but don't know the login/password. Can you advise? > > > Sorry. I did it with a WAIS client. I just tried logging in a telnet > session with user=wais, password=, > but nothing worked. Ought not be passworded! > > Scott? > > --SG > >Ripe works fine. > > > >Regards, > >Peter Scott > ------- End of Forwarded Message - - - - - - - - - - - - - - - - - From marten@ripe.net Tue Sep 1 09:46:59 1992 Received: from ncc.ripe.net by merit.edu (5.65/1123-1.0) id AA25335; Tue, 1 Sep 92 09:46:59 -0400 Received: from rijp.ripe.net by ncc.ripe.net with SMTP id AA16477 (5.65a/NCC-2.8); Tue, 1 Sep 1992 15:46:24 +0200 Message-Id: <9209011346.AA16477@ncc.ripe.net> To: Brewster Kahle Cc: scottw@nic.ddn.mil, jcurran@nnsc.nsf.net, jonathan@think.com, ghb@concert.net, sgoldste@cise.cise.nsf.gov, cert@sei.cmu.edu, nsfnet-cert Subject: Re: security hole in swais, FYI In-Reply-To: Your message of Tue, 01 Sep 92 06:29:20 PDT. <9209011329.AA17908@quake.think.com> From: Marten Terpstra X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Tue, 01 Sep 92 15:46:22 +0200 Sender: Marten.Terpstra@ripe.net Brewster Kahle writes: * * Scott, * * There seems to be a problem with swais, could you please explain? * * We have been running it under a chroot for over a year now with no known * problems. I am the project leader of WAIS and oversaw its development, so * I would like to make sure this problem is understood and extinguished. * * John Curran of NNSC wrote the original version, Jonathan has been the * maintainer of it and extender. * * Just to take a guess, are you running it for public login without doing a * chroot? * * -brewster Hi all, Mark Kosters from GSI notified us of the problem. Using swais you can pipe the output of a search into any command. You can do this by typing 'c' or '|' on the output of a search. Since we are running swais as a public service for people without their own wais client this can be quite harmful. Mark demonstrated that he could start a shell, list /etc/passwd and so on. We are running swais under userID nobody, so too much harm cannot be done, but still, we decided to disable the 'c' and '|' keys as commands. We are running the thing without a chroot though. The offending parts can be found in screen_ui.c. This is however with wais-8-b4, don't know about b5. Commenting out: case '|' : ; case 'c' : pipe_command(question); state=UNKNOWN; return(SHOWRESULTS); in screen_ui.c does the trick, as far as we can see. It would be nice if there was a compile time option to switch to swais in "safe" mode, like some pagers have. Also if you are offering this as a public service, make sure that the pipe commands and shell escapes in the pager swais uses are disabled ... Cheers, -Marten ------------------------------------------------------------------------------ Marten Terpstra | RIPE Network Coordination Centre phone: +31 20 592 5065 | PO BOX 41882, fax: +31 20 592 5090 | NL-1098 SJ Amsterdam, Internet: marten@ripe.net | The Netherlands ------------------------------------------------------------------------------ - - - - - - - - - - - - - - - - - From jcurran@nic.near.net Tue Sep 1 10:38:35 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA27876; Tue, 1 Sep 92 10:38:35 -0400 Message-Id: <9209011438.AA27876@merit.edu> To: Marten Terpstra Cc: Brewster Kahle , scottw@nic.ddn.mil, jonathan@think.com, ghb@concert.net, sgoldste@cise.cise.nsf.gov, cert@sei.cmu.edu, nsfnet-cert, nnsc@nnsc.nsf.net From: jcurran@nnsc.nsf.net Subject: Re: security hole in swais, FYI In-Reply-To: Your message of Tue, 01 Sep 92 15:46:22 +0200. <9209011346.AA16477@ncc.ripe.net> Date: Tue, 01 Sep 92 10:38:12 -0400 Sender: jcurran@nic.near.net -------- ] From: Marten Terpstra ] Subject: Re: security hole in swais, FYI ] Date: Tue, 01 Sep 92 15:46:22 +0200 ] ] ] Hi all, ] ] Mark Kosters from GSI notified us of the problem. Using swais you can pipe ] the output of a search into any command. You can do this by typing 'c' or '|' ] on the output of a search. ] ] Since we are running swais as a public service for people without their own ] wais client this can be quite harmful. Mark demonstrated that he could start ] a shell, list /etc/passwd and so on. ] ] We are running swais under userID nobody, so too much harm cannot be done, ] but still, we decided to disable the 'c' and '|' keys as commands. ] We are running the thing without a chroot though. ] ] The offending parts can be found in screen_ui.c. This is however with ] wais-8-b4, don't know about b5. ] ] Commenting out: ] ] case '|' : ; ] case 'c' : pipe_command(question); ] state=UNKNOWN; ] return(SHOWRESULTS); ] ] in screen_ui.c does the trick, as far as we can see. ] It would be nice if there was a compile time option to switch to swais in ] "safe" mode, like some pagers have. ] ] Also if you are offering this as a public service, make sure that the pipe ] commands and shell escapes in the pager swais uses are disabled ... This is *not* a safe method for offering anonymous "wais" service. Both NNSC.NSF.NET and QUAKE.THINK.COM are running it under a "chroot" file system thereby preventing access to any files not explicitely placed in the wais user directory. SWAIS was never intended to be run as an interactive service (if it were, I would have certainly designed it differently). Instead, it is designed to be run as yet another WAIS client, under a validated user name. Making it available via telnet is something that we did to develop interest in WAIS. Please do not setup a anonymous wais account to run it unless you provide it with a restricted filesystem. Not only do the pipe and pager commands pose a threat, but it is also possible for folks to use the source routines to access files. If you need details on how to setup a seperate filesystem for providing anonymous wais service, send mail to "nnsc@nnsc.nsf.net". John Curran NSF Network Service Center - - - - - - - - - - - - - - - - - From jonathan@quake.think.com Tue Sep 1 13:02:39 1992 Received: from Quake.Think.COM by merit.edu (5.65/1123-1.0) id AA04172; Tue, 1 Sep 92 13:02:39 -0400 Received: from tremor.quake.think.com by quake.think.com (4.1/SMI-4.0) id AA21292; Tue, 1 Sep 92 10:02:12 PDT Received: by tremor.quake.think.com (4.1/SMI-4.1) id AA21577; Tue, 1 Sep 92 10:02:05 PDT Date: Tue, 1 Sep 92 10:02:05 PDT Message-Id: <9209011702.AA21577@tremor.quake.think.com> From: Jonny Goldman Sender: jonathan@quake.think.com To: Marten.Terpstra@ripe.net Cc: brewster@Think.COM, scottw@nic.ddn.mil, jcurran@nnsc.nsf.net, ghb@concert.net, sgoldste@cise.cise.nsf.gov, cert@sei.cmu.edu, nsfnet-cert In-Reply-To: Marten Terpstra's message of Tue, 01 Sep 92 15:46:22 +0200 <9209011346.AA16477@ncc.ripe.net> Subject: security hole in swais, FYI From: Marten Terpstra Date: Tue, 01 Sep 92 15:46:22 +0200 Mark Kosters from GSI notified us of the problem. Using swais you can pipe the output of a search into any command. You can do this by typing 'c' or '|' on the output of a search. We've known about this. The solution is to run swais under a chroot, with a very limited bin directory. This is how swais is run on Quake, and we've had no evidence of any tampering. Since we are running swais as a public service for people without their own wais client this can be quite harmful. Mark demonstrated that he could start a shell, list /etc/passwd and so on. We are running swais under userID nobody, so too much harm cannot be done, but still, we decided to disable the 'c' and '|' keys as commands. We are running the thing without a chroot though. The offending parts can be found in screen_ui.c. This is however with wais-8-b4, don't know about b5. Commenting out: case '|' : ; case 'c' : pipe_command(question); state=UNKNOWN; return(SHOWRESULTS); in screen_ui.c does the trick, as far as we can see. It would be nice if there was a compile time option to switch to swais in "safe" mode, like some pagers have. I believe Jim Fulton's version allows this, but I'll check to make sure. Also if you are offering this as a public service, make sure that the pipe commands and shell escapes in the pager swais uses are disabled ... I've done this by using a special .cshrc, but I just thought of a way that could be defeated. Hmmm, I want users to be able to use a limited set of commands. Perhaps swais needs a "secure" command list. - Jonny G - - - - - - - - - - - - - - - - - From marten@ripe.net Wed Sep 2 04:04:59 1992 Received: from ncc.ripe.net by merit.edu (5.65/1123-1.0) id AA04855; Wed, 2 Sep 92 04:04:59 -0400 Received: from rijp.ripe.net by ncc.ripe.net with SMTP id AA17625 (5.65a/NCC-2.8); Wed, 2 Sep 1992 10:04:24 +0200 Message-Id: <9209020804.AA17625@ncc.ripe.net> To: Jonny Goldman Cc: brewster@think.com, scottw@nic.ddn.mil, jcurran@nnsc.nsf.net, ghb@concert.net, sgoldste@cise.cise.nsf.gov, cert@sei.cmu.edu, nsfnet-cert Subject: Re: security hole in swais, FYI In-Reply-To: Your message of Tue, 01 Sep 92 10:02:05 PDT. <9209011702.AA21577@tremor.quake.think.com> From: Marten Terpstra X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Wed, 02 Sep 92 10:04:23 +0200 Sender: Marten.Terpstra@ripe.net Jonny Goldman writes: * From: Marten Terpstra * Date: Tue, 01 Sep 92 15:46:22 +0200 * * We've known about this.The solution is to run swais under a chroot, with a * very limited bin directory. This is how swais is run on Quake, and we've * had no evidence of any tampering. The version I have (b4) does not have a chroot in it. Currently we are running without the mail and pipe options ... The loss of a pipe option is no problem, the mail option is. * I've done this by using a special .cshrc, but I just thought of a way that * could be defeated. Hmmm, I want users to be able to use a limited set of * commands. Perhaps swais needs a "secure" command list. A secure command list would be very nice, or perhaps like other programs a simple compile time enable/disable flag for each command. Pagers like "less" have something along these lines. Anyway, let us know if something more "safe" comes along. Cheers, -Marten - - - - - - - - - - - - - - - - - From schmid@refuge.Colorado.EDU Wed Sep 2 10:08:21 1992 Received: from refuge.Colorado.EDU by merit.edu (5.65/1123-1.0) id AA16490; Wed, 2 Sep 92 10:08:21 -0400 Received: by refuge.Colorado.EDU with SMTP id AA13813 (5.65b/cu-ida-1.4.3 for nsfnet-cert@merit.edu); Wed, 2 Sep 92 08:06:48 -0600 Message-Id: <9209021406.AA13813@refuge.Colorado.EDU> To: Marten Terpstra Subject: Re: security hole in swais, FYI Cc: brewster@think.com, scottw@nic.ddn.mil, jcurran@nnsc.nsf.net, ghb@concert.net, sgoldste@cise.cise.nsf.gov, cert@sei.cmu.edu, nsfnet-cert, tmr@refuge.Colorado.EDU In-Reply-To: Your message of Wed, 02 Sep 92 10:04:23 +0100 Date: Wed, 02 Sep 92 08:06:48 CDT From: "Peter Schmid - UnixOps" -------- yet another of these WAIS thingies. FYI. res. -- pete Jonny Goldman writes: * From: Marten Terpstra * Date: Tue, 01 Sep 92 15:46:22 +0200 * * We've known about this.The solution is to run swais under a chroot, wit h a * very limited bin directory. This is how swais is run on Quake, and we' ve * had no evidence of any tampering. The version I have (b4) does not have a chroot in it. Currently we are running without the mail and pipe options ... The loss of a pipe option is no problem, the mail option is. * I've done this by using a special .cshrc, but I just thought of a way t hat * could be defeated. Hmmm, I want users to be able to use a limited set of * commands. Perhaps swais needs a "secure" command list. A secure command list would be very nice, or perhaps like other programs a simple compile time enable/disable flag for each command. Pagers like "less " have something along these lines. Anyway, let us know if something more "safe" comes along. Cheers, -Marten -------- - - - - - - - - - - - - - - - - - From jwabik@msc.edu Wed Sep 2 13:28:07 1992 Received: from noc.msc.edu by merit.edu (5.65/1123-1.0) id AA24578; Wed, 2 Sep 92 13:28:07 -0400 Received: from sniper.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA12475; Wed, 2 Sep 92 12:28:01 -0500 Received: by sniper.msc.edu (5.65/MSC/v3.1r(920220)) id AA02344; Wed, 2 Sep 92 12:28:03 -0500 From: jwabik@msc.edu (Jeff Wabik) Message-Id: <9209021728.AA02344@sniper.msc.edu> Subject: Remote Gear Support .. To: regional-techs Date: Wed, 2 Sep 92 12:28:01 CDT X-Mailer: ELM [version 2.3 PL11] I've been poking around (thru the Black Box catalog, for example) for equipment to help us support our remote network gear located near the NSS to which we attach. I've had little success at finding the right pieces. I'm wondering if any of you have implemented any of these (listed below) solutions, and if so, where you found the equipment to do it; then subsequent sucess/failure information. Not in any particular order, here are the functions I'd like to be able to perform remotely.. This is a "grandiose wish list", as it were. * Software switchable dial-up access to serial ports on all gear (several ports): To Device 1 +-------------> |+------------> || To Device 2 Phone line +-------+ +---------+++ . -----------------| Modem |---| Magic Box | . +-------+ +-----------+ . || To Device (n-1) |+------------> +-------------> To Device (n) In this scenario, I dial into the modem to the "magic box", and give it some character code or sequence to attach me to the specified port. I can escape back to the magic-box and request subsequent connections without having to redial. [Black box has one of these for 4 ports, but I hear its not too good. Any experiences?] * Power Cycle any of "n" pieces of remote hardware via RS232 interface and ASCII selection. Ideally, this box attaches to one of the ports of the serial switch above, and asks me which piece of the "n" attached pieces of hardware should be cycled. [Black box has one of these for a single piece of equipment. It requires a dedicated phone line, and uses telco tones to trigger a cycle.] * T1 line switch: Incoming T1 +--------+ +-----------+ | |-----------------| CSU/DSU 1 |----> To router 1 -----------------| Switch | +-----------+ | |-----------------| CSU/DSU 2 |----> To router 2 +--------+ +-----------+ ^ | V RS232 Input Ideally, this box also attaches to one of the ports on the n-by serial switch above, and has some sort of menu or ASCII code line selection mechanism. Being a software guy, I thought about wiring this up using a switch for RS232 from Black Box.. Hardware people informed me that this wasn't a good idea. Again, these are the thoughts on my mind... and an "ideal wish list". I'd appreciate hearing about any implementations or similar tools that you have experience with. Thanks! -Jeff -- Jeff Wabik E/Mail: jwabik@msc.edu Minnesota Supercomputer Center AT&T: +1 612 626 0211 Minneapolis, MN FAX: +1 612 624 6550 - - - - - - - - - - - - - - - - - From e-krol@uiuc.edu Wed Sep 2 14:09:41 1992 Received: from ux1.cso.uiuc.edu by merit.edu (5.65/1123-1.0) id AA26337; Wed, 2 Sep 92 14:09:41 -0400 Received: from [128.174.33.50] (rail.cso.uiuc.edu) by ux1.cso.uiuc.edu with SMTP id AA28476 (5.67a8/IDA-1.5 for ); Wed, 2 Sep 1992 13:09:22 -0500 Date: Wed, 2 Sep 1992 13:09:22 -0500 Message-Id: <199209021809.AA28476@ux1.cso.uiuc.edu> To: regional-techs, jwabik@msc.edu (Jeff Wabik) From: e-krol@uiuc.edu Sender: krol@ux1.cso.uiuc.edu Subject: Re: Remote Gear Support .. At 2 Sep 12:28 CDT, Jeff Wabik wrote: > > >I've been poking around (thru the Black Box catalog, for example) for >equipment to help us support our remote network gear located near the >NSS to which we attach. I've had little success at finding the >right pieces. I'm wondering if any of you have implemented any of >these (listed below) solutions, and if so, where you found the >equipment to do it; then subsequent sucess/failure information. > >Not in any particular order, here are the functions I'd like to be able >to perform remotely.. This is a "grandiose wish list", as it were. > > * Software switchable dial-up access to serial ports > on all gear (several ports): > To Device 1 > +-------------> > |+------------> > || To Device 2 > Phone line +-------+ +---------+++ . >-----------------| Modem |---| Magic Box | . > +-------+ +-----------+ . > || To Device (n-1) > |+------------> > +-------------> > To Device (n) > > In this scenario, I dial into the modem to the "magic box", > and give it some character code or sequence to attach me to > the specified port. I can escape back to the magic-box > and request subsequent connections without having to > redial. [Black box has one of these for 4 ports, but I hear > its not too good. Any experiences?] > CICnet did just this. There was a 4 port I thought black box code controled switch. There was one port to the cisco router and one to each of the csu ports. The switch had like and esc, ctlz, n where n was 1 - 4 saying switch to port 1-4. Otherwise it was transparent. ------------------------- Ed Krol 217-333-7886 University of Illinois 1304 W. Springfield Urbana, IL 61801 Maturity is a measure of ones ability to deal with Ambiguity - - - - - - - - - - - - - - - - - From long@nic.near.net Wed Sep 2 14:20:57 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA26965; Wed, 2 Sep 92 14:20:57 -0400 Message-Id: <9209021820.AA26965@merit.edu> To: regional-techs Subject: Re: Remote Gear Support ... Date: Wed, 02 Sep 92 14:20:53 -0400 From: Dan Long Yes--we've run into the problem with the 4 and 8-way COS switches too. Always connect to an unused port before hanging up.... Dan ------- Forwarded Message To: Jeff Wabik cc: nearnet-ops Subject: Re: Remote Gear Support .. In-reply-to: Your message of Wed, 02 Sep 92 12:28:01 -0500. <9209021728.AA02344@sniper.msc.edu> Date: Wed, 02 Sep 92 14:15:19 -0400 From: "Dan Long" From: Jeff Wabik Subject: Remote Gear Support .. Date: Wed, 2 Sep 92 12:28:01 CDT I've been poking around (thru the Black Box catalog, for example) for equipment to help us support our remote network gear located near the NSS to which we attach. I've had little success at finding the right pieces. I'm wondering if any of you have implemented any of these (listed below) solutions, and if so, where you found the equipment to do it; then subsequent sucess/failure information. We've done all this stuff with (almost) stock Black Box gear. I'll fax you a copy of a diagram of a setup we actually implemented when we had a T1 line going to Princeton and wanted to be able to power cycle the gear, access various console ports, and switch a T1 line from one DSU/CSU to another. It all worked fine. Not in any particular order, here are the functions I'd like to be able to perform remotely.. This is a "grandiose wish list", as it were. * Software switchable dial-up access to serial ports on all gear (several ports): To Device 1 +-------------> |+------------> || To Device 2 Phone line +-------+ +---------+++ . -----------------| Modem |---| Magic Box | . +-------+ +-----------+ . || To Device (n-1) |+------------> +-------------> To Device (n) In this scenario, I dial into the modem to the "magic box", and give it some character code or sequence to attach me to the specified port. I can escape back to the magic-box and request subsequent connections without having to redial. [Black box has one of these for 4 ports, but I hear its not too good. Any experiences?] We do this with their 4-way or 8-way switch. There's also a (nicer) box from Newbridge called the 1008 Mainstreet Data Controller ($1100) (703-834-3600). * Power Cycle any of "n" pieces of remote hardware via RS232 interface and ASCII selection. Ideally, this box attaches to one of the ports of the serial switch above, and asks me which piece of the "n" attached pieces of hardware should be cycled. [Black box has one of these for a single piece of equipment. It requires a dedicated phone line, and uses telco tones to trigger a cycle.] We use the black box LOR-II and we just change a wire on the relay to make it be Normally-Closed instead of Normally-Open. Works great. Power goes off as long as you stay connected to the appropriate serial port on the switch. Be aware of the LOR's load limitations, however. Another option (which I haven't tested is: Heathkit/Radio Shack sell the BSR wireless controlers which has an RS-232C interface. These devices communicate over the AC power lines and can operate relays wich can switch an inductive load of up to 20 Amps - which is sufficent for the devices we would use. The problem with this technology is that if the power lines have a lot of noise, the units may not respond to commands. The benifit is they are small, cheap, and work well. * T1 line switch: Incoming T1 +--------+ +-----------+ | |-----------------| CSU/DSU 1 |----> To router 1 -----------------| Switch | +-----------+ | |-----------------| CSU/DSU 2 |----> To router 2 +--------+ +-----------+ ^ | V RS232 Input Ideally, this box also attaches to one of the ports on the n-by serial switch above, and has some sort of menu or ASCII code line selection mechanism. Being a software guy, I thought about wiring this up using a switch for RS232 from Black Box.. Hardware people informed me that this wasn't a good idea. This may not be a good idea (may even be illegal) but we needed to do it and it worked like a champ (saved our asses at least once). We used a Black Box tone-activated-talking switch and wired the 4-wire T1 line up to it. It operates based on touch-tone input (not RS232). Since we only wanted one phone line, then we put the equivalent of an ASD-4 (they used to have a 2-port version called a Call Distribution Switch) in front to select either the TATS or the modem/8-way box. And we put security codes on the TATS and modem (a security modem from black box) so random people couldn't toy with our gear. Again, these are the thoughts on my mind... and an "ideal wish list". I'd appreciate hearing about any implementations or similar tools that you have experience with. Works for us. Your mileage may vary. Good luck. Regards, Dan ------- End of Forwarded Message - - - - - - - - - - - - - - - - - From tom@nisca.acs.ohio-state.edu Wed Sep 2 14:11:18 1992 Received: from nisca.acs.ohio-state.edu by merit.edu (5.65/1123-1.0) id AA26541; Wed, 2 Sep 92 14:11:18 -0400 Received: by nisca.acs.ohio-state.edu (5.65/3.910306) id AA20627; Wed, 2 Sep 92 14:11:14 -0400 From: Tom Easterday Message-Id: <9209021811.AA20627@nisca.acs.ohio-state.edu> Subject: Re: Remote Gear Support .. To: jwabik@msc.edu (Jeff Wabik) Date: Wed, 2 Sep 92 14:11:13 EDT Cc: regional-techs In-Reply-To: <9209021728.AA02344@sniper.msc.edu>; from "Jeff Wabik" at Sep 2, 92 12:28 pm X-Mailer: ELM [version 2.3 PL0] > I've been poking around (thru the Black Box catalog, for example) for > equipment to help us support our remote network gear located near the > NSS to which we attach. I've had little success at finding the > right pieces. I'm wondering if any of you have implemented any of > these (listed below) solutions, and if so, where you found the > equipment to do it; then subsequent sucess/failure information. > > Not in any particular order, here are the functions I'd like to be able > to perform remotely.. This is a "grandiose wish list", as it were. > > * Software switchable dial-up access to serial ports > on all gear (several ports): > To Device 1 > +-------------> > |+------------> > || To Device 2 > Phone line +-------+ +---------+++ . > -----------------| Modem |---| Magic Box | . > +-------+ +-----------+ . > || To Device (n-1) > |+------------> > +-------------> > To Device (n) > > In this scenario, I dial into the modem to the "magic box", > and give it some character code or sequence to attach me to > the specified port. I can escape back to the magic-box > and request subsequent connections without having to > redial. [Black box has one of these for 4 ports, but I hear > its not too good. Any experiences?] CICNet has been using this setup since its inception (1988 or so). We use the Black Box 4 and 8 port Code Operated Switches. Up until recently we have relied on the site at which the equipment sits to supply the modem. We only require 1200 bps. In short: ****DON'T DO IT*****!!!!! Ok, now that I feel better, in all fairness, I know that part of our problems have been the hodge-podge of modems that are out there. We are now in the process of installing the same modems everywhere. Currently the setup works about 60% of the time. There are really flaky things that go on though with the COS's themselves. If a COS is set on an active port for whatever reason (and it seems to happen occasionally for no reason) the modem will not answer because it sees activity on its DTE port. We are very careful when logging out of the COS to set it to an unused port before breaking the connection with the modem. Otherwise the next time we try to dial in it may not work. I cannot guess how much of our problem is the modem and how much is the COS but I do know that it is a combination of both. > > * Power Cycle any of "n" pieces of remote hardware via RS232 > interface and ASCII selection. Ideally, this box attaches > to one of the ports of the serial switch above, and asks me > which piece of the "n" attached pieces of hardware should be > cycled. [Black box has one of these for a single piece of > equipment. It requires a dedicated phone line, and uses > telco tones to trigger a cycle.] Yeah, I have wished for that too at times. We have always relied on site personnel to power cycle stuff for us. As we move things into unmanned sites we will have to consider something like this. > > * T1 line switch: > > > Incoming T1 +--------+ +-----------+ > | |-----------------| CSU/DSU 1 |----> To router 1 > -----------------| Switch | +-----------+ > | |-----------------| CSU/DSU 2 |----> To router 2 > +--------+ +-----------+ > ^ > | > V > RS232 Input > > Ideally, this box also attaches to one of the ports on the > n-by serial switch above, and has some sort of menu or > ASCII code line selection mechanism. Being a software guy, > I thought about wiring this up using a switch for RS232 from > Black Box.. Hardware people informed me that this wasn't > a good idea. > > I have heard of patch panels for various interface standards (like v.35, rs449, etc) that are async controllable (ie, the "Switch" you describe) that would allow you do to this. Presumably they would be designed to handle the nastiness that goes on when you slam a digital signal back and forth through a switch. You might check with ADC who make oodles of patch panels for manageable models. I used to use other ADC patch panels in a previous life and in general they were well designed and reliable. ADC's number is 800-733-5511 (Portland, OR). > Again, these are the thoughts on my mind... and an "ideal wish list". > I'd appreciate hearing about any implementations or similar tools > that you have experience with. > We are currently evaluating a cheap terminal server to replace the COS for our out-of-band access. Lantronix makes a TS for about $1200 (Univ price). Although a bit more expensive then the COS, it provides much more flexibility (like begin able to telnet to dumb async devices when the network is up, and being able to have multiple sessions going which makes realtime debugging of problems easier). I would be interested if anyone knows of any cheaper TS out there. Tom - - - - - - - - - - - - - - - - - From @CORNELLC.cit.cornell.edu:craig@icp.net Wed Sep 2 14:53:01 1992 Received: from CORNELLC.CIT.CORNELL.EDU by merit.edu (5.65/1123-1.0) id AA28372; Wed, 2 Sep 92 14:53:01 -0400 Received: from dns.cit.cornell.edu by CORNELLC.cit.cornell.edu (IBM VM SMTP V2R2) with TCP; Wed, 02 Sep 92 14:49:06 EDT Received: from icm1.icp.net by dns.cit.cornell.edu (4.1/2.0) id AA07090; Wed, 2 Sep 92 14:49:04 EDT Received: by icm1.icp.net (4.1/SMI-4.1) id AA04633; Wed, 2 Sep 92 14:58:22 EST Date: Wed, 2 Sep 92 14:58:22 EST From: craig@icp.net (Craig A. Haney) Message-Id: <9209021958.AA04633@icm1.icp.net> To: jwabik@msc.edu, tom@nisca.acs.ohio-state.edu Subject: Re: Remote Gear Support .. Cc: regional-techs > We are currently evaluating a cheap terminal server to replace the COS for > our out-of-band access. Lantronix makes a TS for about $1200 (Univ price). > Although a bit more expensive then the COS, it provides much more flexibility > (like begin able to telnet to dumb async devices when the network is up, > and being able to have multiple sessions going which makes realtime debugging > of problems easier). I would be interested if anyone knows of any cheaper > TS out there. > > Tom About this time last year I was using the Lantronix and Hughes/CMC terminal Server. The Lantronix was advertised as able to do many different type of connectivity, but I didn't like the support and the performance and quality were not as good as the Hughes. I had good field support and ROM upgrades. The software which came with the Lantronix was buggy. Then again it was trying to run on an AT&T 3B2 600G (oh my!). craig@icp.net 703 904 2084 - - - - - - - - - - - - - - - - - From tom@nisca.acs.ohio-state.edu Wed Sep 2 15:00:47 1992 Received: from nisca.acs.ohio-state.edu by merit.edu (5.65/1123-1.0) id AA28720; Wed, 2 Sep 92 15:00:47 -0400 Received: by nisca.acs.ohio-state.edu (5.65/3.910306) id AA21019; Wed, 2 Sep 92 15:00:41 -0400 From: Tom Easterday Message-Id: <9209021900.AA21019@nisca.acs.ohio-state.edu> Subject: Re: Remote Gear Support .. To: craig@icp.net (Craig A. Haney) Date: Wed, 2 Sep 92 15:00:41 EDT Cc: regional-techs, jwabik@msc.edu In-Reply-To: <9209021958.AA04633@icm1.icp.net>; from "Craig A. Haney" at Sep 2, 92 2:58 pm X-Mailer: ELM [version 2.3 PL0] > > About this time last year I was using the Lantronix and Hughes/CMC > terminal Server. The Lantronix was advertised as able to do many > different type of connectivity, but I didn't like the support and > the performance and quality were not as good as the Hughes. > I had good field support and ROM upgrades. > The software which came with the Lantronix was buggy. Then > again it was trying to run on an AT&T 3B2 600G (oh my!). > > craig@icp.net > 703 904 2084 > How much does the Hughes go for? BTW, the Lantronix has improved quite a bit since last year (I looked at them too then also). The only problem I have seen so far is that they have a 2 byte (yes, 2 byte) serial line buffer which can easily be overrun if you have dumb (aka, no flow control) serial devices. - - - - - - - - - - - - - - - - - From @CORNELLC.cit.cornell.edu:craig@icp.net Wed Sep 2 15:20:09 1992 Received: from CORNELLC.CIT.CORNELL.EDU by merit.edu (5.65/1123-1.0) id AA29533; Wed, 2 Sep 92 15:20:09 -0400 Received: from dns.cit.cornell.edu by CORNELLC.cit.cornell.edu (IBM VM SMTP V2R2) with TCP; Wed, 02 Sep 92 15:20:02 EDT Received: from icm1.icp.net by dns.cit.cornell.edu (4.1/2.0) id AA07189; Wed, 2 Sep 92 15:19:53 EDT Received: by icm1.icp.net (4.1/SMI-4.1) id AA04756; Wed, 2 Sep 92 15:29:09 EST Date: Wed, 2 Sep 92 15:29:09 EST From: craig@icp.net (Craig A. Haney) Message-Id: <9209022029.AA04756@icm1.icp.net> To: craig@icp.net, tom@nisca.acs.ohio-state.edu Subject: Re: Remote Gear Support .. Cc: jwabik@msc.edu, regional-techs > About this time last year I was using the Lantronix and Hughes/CMC > terminal Server. The Lantronix was advertised as able to do many > different type of connectivity, but I didn't like the support and > the performance and quality were not as good as the Hughes. > I had good field support and ROM upgrades. > The software which came with the Lantronix was buggy. Then > again it was trying to run on an AT&T 3B2 600G (oh my!). > > craig@icp.net > 703 904 2084 > How much does the Hughes go for? BTW, the Lantronix has improved quite a bit since last year (I looked at them too then also). The only problem I have seen so far is that they have a 2 byte (yes, 2 byte) serial line buffer which can easily be overrun if you have dumb (aka, no flow control) serial devices. I remember the GSA price for the Navy was something like $1000 - $1300. FYI: The original reason for the terminal server was to do network printing from an AT&T 3B2 600 System V.3.2 on 10Base-T. I wrote some code to integrate with the System V print spooler called 'netlp' to print to a RAW TCP socket on the terminal server. The results were very good. The serial port on the Laser could be throttled as wide as the terminal server could handle. Now the Navy Medical data services center can print anywhere over IP on their network. craig@icp.net - - - - - - - - - - - - - - - - - From prue@ISI.EDU Wed Sep 2 17:35:35 1992 Received: from venera.isi.edu by merit.edu (5.65/1123-1.0) id AA05308; Wed, 2 Sep 92 17:35:35 -0400 Received: from fji.isi.edu by venera.isi.edu (5.65c/5.65+local-6) id ; Wed, 2 Sep 1992 14:35:33 -0700 Date: Wed, 2 Sep 92 14:35:26 PDT From: prue@ISI.EDU Posted-Date: Wed, 2 Sep 92 14:35:26 PDT Message-Id: <9209022135.AA02272@fji.isi.edu> Received: by fji.isi.edu (4.1/4.0.3-4) id ; Wed, 2 Sep 92 14:35:26 PDT To: jwabik@msc.edu Subject: Re: Remote Gear Support .. Cc: Postel@ISI.EDU, Prue@ISI.EDU, regional-techs From jwabik@msc.edu Wed Sep 2 10:33:07 1992 Subject: Remote Gear Support .. To: regional-techs@merit.edu I've been poking around (thru the Black Box catalog, for example) for equipment to help us support our remote network gear located near the NSS to which we attach. I've had little success at finding the right pieces. I'm wondering if any of you have implemented any of these (listed below) solutions, and if so, where you found the equipment to do it; then subsequent sucess/failure information. Not in any particular order, here are the functions I'd like to be able to perform remotely.. This is a "grandiose wish list", as it were. * Software switchable dial-up access to serial ports on all gear (several ports): To Device 1 +-------------> |+------------> || To Device 2 Phone line +-------+ +---------+++ . -----------------| Modem |---| Magic Box | . +-------+ +-----------+ . || To Device (n-1) |+------------> +-------------> To Device (n) In this scenario, I dial into the modem to the "magic box", and give it some character code or sequence to attach me to the specified port. I can escape back to the magic-box and request subsequent connections without having to redial. [Black box has one of these for 4 ports, but I hear its not too good. Any experiences?] * Power Cycle any of "n" pieces of remote hardware via RS232 interface and ASCII selection. Ideally, this box attaches to one of the ports of the serial switch above, and asks me which piece of the "n" attached pieces of hardware should be cycled. [Black box has one of these for a single piece of equipment. It requires a dedicated phone line, and uses telco tones to trigger a cycle.] Los Nettos as built a remote access system much like you describe. We use a Newbridge 1080 8 port ASCII async switch, a 9600 bps modem and a Dataprobe K10-A power relay. The Newbridge switch has the ability to configure any or all of their ports as source ports or destination ports or both source and destination ports. A CSU/DSU console is a destination port, while a local console terminal may only be a source port. You configure the switch with port speeds and many other port characteristics. Both source and destination ports can have password protection by option. The device has up to 128 bytes of buffering and can do speed conversion with two types of flow control. It has several options for responding to and providing control leads. It also does data format conversion. It has other options I have not mentioned as well. If 8 ports are not enough one can connect two or more together. The best part is that we get the Newbridge 1080 switch for about $650 each. The switch is configured with lots of parameters for each port. This configuration is maintained during power outages. The Dataprobe K10-A we use is a modified unit from what they have in their catalogue. Our version kills the power to an AC plug if we raise a control lead. Power remains on if there is a low signal or no signal. We plug a power strip into the power relay, plug our router and all of the CSU/DSU's. We thus power cycle everything all at once. We plug a cable between the switch and the power relay. When we select the power relay port our equipment is powered down. Because the switch port fails a DTE-DCE control lead handshake the switch aborts the connection to the power relay device and power is restored automatically. I wanted to be able to power cycle things individually but the only thing I found was a device which is no longer manufactured. I think it was an X-10 or something like that. The Dataprobe K10-A's cost about $150 each. We use NEC 9631 modems which have worked reliably at 9600, even cross country. Two of our Los Nettos members have duplicated our Los Nettos Remote Console Access (RCK) systems for their own corporate networks. I use Cisco routers. I connect both the console port and the AUX port to the switch. In this way I can telnet to the Cisco AUX port and talk to the switch and the CSU/DSU's. I can even connect to the modem through this telnet connection and dial a remote location without leaving my workstation. You can't appreciate how much easier it is to get T1's repaired when you can see both CSU/DSUs on an sick line until you've done it a few times. You can tell the phone company real time which half of a line will test good through a double loop somewhere in the middle. With our CSU/DSUs we can send the phone company a quasi-random signal their test equipment can look at. Testing in this mode goes so much quicker. * T1 line switch: Incoming T1 +--------+ +-----------+ | |-----------------| CSU/DSU 1 |----> To router 1 -----------------| Switch | +-----------+ | |-----------------| CSU/DSU 2 |----> To router 2 +--------+ +-----------+ ^ | V RS232 Input Ideally, this box also attaches to one of the ports on the n-by serial switch above, and has some sort of menu or ASCII code line selection mechanism. Being a software guy, I thought about wiring this up using a switch for RS232 from Black Box.. Hardware people informed me that this wasn't a good idea. I believe that a T1 line switch violates the T1 tarifs. The first thing the T1 is suppose to see is a CSU to protect the network from the customer equipment. I would like to hear that I am wrong because I have wanted to do just the same thing on multiple occasions. Again, these are the thoughts on my mind... and an "ideal wish list". I'd appreciate hearing about any implementations or similar tools that you have experience with. Thanks! -Jeff Cisco AGS+ routers come with an environmental monitor card. This card tests the power and the temperature and puts constant updates out as ASCII async data. If we connected that to the switch we could remotely receive this data when we selected that switch port as well. What I would like is to have the protocol used on the CSU/DSU port be more computer friendly. With our Datatel CSU/DSUs it is diffucult to teach a computer program how to interpret the output display. The data is context and position dependent. The base display format is unknown but dependent on how it was left from last time. There is no way to force the console port into a base mode where one can know that sending certain inputs to the console port will deliver a specific output, or initiate a loop without looking at the console output for feedback each step of the way. I would like an interface that would be easy to do testing under program control with a minimum of code development. I think some new CSU/DSUs have or will have this in the future. Of course these are the most expensive models. Give me a call if you have any specific questions. Walt Prue Los Nettos 310-822-1511 - - - - - - - - - - - - - - - - - From hfl@cert.org Thu Sep 3 16:54:35 1992 Received: from shamu.cert.org by merit.edu (5.65/1123-1.0) id AA25207; Thu, 3 Sep 92 16:54:35 -0400 Received: from localhost.cert.org by shamu.cert.org (4.1/2.3) id AA03964; Thu, 3 Sep 92 16:53:30 EDT Message-Id: <9209032053.AA03964@shamu.cert.org> To: schmid@refuge.colorado.edu, Marten.Terpstra@ripe.net, brewster@think.com, scottw@nic.ddn.mil, jcurran@nnsc.nsf.net, ghb@concert.net, sgoldste@cise.cise.nsf.gov, nsfnet-cert, jonathan@think.com, tmr@refuge.colorado.edu Cc: cert@cert.org Subject: Re: security hole in swais, FYI Date: Thu, 03 Sep 92 16:53:30 EDT From: hfl@cert.org Thanks very much for keeping us informed on this one. Howard Lipson, Computer Security Researcher Computer Emergency Response Team Software Engineering Institute Carnegie Mellon University Pittsburgh, Pa. 15213-3890 Internet E-mail: cert@cert.org (monitored during business hours) Telephone: (412) 268-7090 (answers 24 hour a day) - - - - - - - - - - - - - - - - - From rty Fri Sep 4 12:01:02 1992 Received: by merit.edu (5.65/1123-1.0) id AA05376; Fri, 4 Sep 92 12:01:19 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA05364; Fri, 4 Sep 92 12:01:02 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA23281; Fri, 4 Sep 92 12:01:01 EDT Date: Fri, 4 Sep 92 12:01:01 EDT Message-Id: <9209041601.AA23281@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 132.80 Network Name: NG-CONC1 Location: National Guard Bureau, The Pentagon, Washington, DC 20310, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 134.39 Network Name: CTCNET1 Location: Communications Technology Center, 3860 159th NE, Suite 150, Redmond, WA 98052, USA Country Code: US 1:754 T1-T3 Network Interconnect (Houston, TX) 2:751 T1-T3 Network Interconnect (San Diego, CA) 3:750 T1-T3 Network Interconnect (Ann Arbor, MI) 4:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 149.246 Network Name: SIENKE-LAN Location: Siemens AG, OeN NKE A2, Postfach 700078, D-W-8000 Muenchen 70, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 155.37 Network Name: UCHC-NET Location: Univ. of Connecticut Health Center, MC 3405, Neuroscience Center, 263 Farmington Avenue, Farmington, CT 06030, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 155.178 Network Name: FAA Location: FAA Technical Center, Atlantic City Airport, NJ 08405, USA Country Code: US 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 158.125 Network Name: DEPT-LUT-AC Location: Lougborough University, Loughborough, Leicestershire LE11 3TU, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 159.77 Network Name: DISA-EUROPE Location: DISA-EUROPE/DEKC, Unit 30403, APO AE 09131 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 161.133 Network Name: DELTACOLLEGE Location: Delta College, 6263 Mackinaw Road, University Center, MI 48710, USA Country Code: US 1:233 Merit Regional Network 2:237 Merit Regional Network 3:177 Merit Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 163.125 Network Name: CFT-NET Location: Creative Friendly Technologies, Inc., 6226 East Sligh Avenue, Tampa, FL 33617-1905, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 163.150 Network Name: SBCSS Location: San Bernardino County Superintendent of Schools, 601 North "E" Street, San Bernardino, CA 92410-3093, USA Country Code: US 1:195 SDSC Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 163.228 Network Name: MMM-DOM2 Location: 3M Corporation, 3M Center, Building 224-4n-27, St. Paul, MN 55144-1000, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 163.229 Network Name: SC92-NET Location: Minnesota Supercomputer Center, 1200 Washington Avenue South, Minneapolis, MN 55415, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.6.10 Network Name: HPLB-HP Location: Hewlett-Packard Company, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.6.135 Network Name: HP-CUP1 Location: Hewlett-Packard Company, Information Networks Division, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.6.136 Network Name: HP-ATL Location: Hewlett-Packard Company, Information Networks Division, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.74.216 Network Name: DOESAN Location: Department of Energy, San Francisco Field Office, 1333 Broadway Room 608, Oakland, CA 94612, USA Country Code: US 1:291 Energy Science Network (FIX-West) 2:293 Energy Science Network (FIX-East) Network IP: 192.76.135 Network Name: TOOLSNET Location: Tools GmbH, Kessenicher Str. 108, D-W-5300 Bonn 1, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.102.158 Network Name: FHG-ISST-NET Location: Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.124.140 Network Name: MAK Location: Mak Technologies, 380 Green Street, Cambridge, MA 02139, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.129.41 Network Name: SIEFUERTH Location: Siemens Fuerth, Fuerth, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.146.195 Network Name: CSD Location: United Technologies, Chemical Systems, 600 Metcalf Road, San Jose, CA 95138-9121, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.140 Network Name: AEAEN-LAN Location: HQUSAREUR, DCSENG, Unit 29351, APO AE 09014 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.156.221 Network Name: IBMNET6 Location: IBM Industrial Technology Center, 1311 Mamaroneck Ave., White Plains, NY 10605, USA Country Code: US 1:1206 PSCNET Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.187.135 Network Name: NETCOM38 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.94 Network Name: NET-CTAENG Location: CTA INC., 5670 Greenwood Plaza Blvd. Suite 200, Englewood, CO 80111, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.130 Network Name: CUMBERLAND Location: Cumberland College, CIS Dept., Walnut Street, Williamsburg, KY 40769, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.188.177 Network Name: AUSTINEA-NET Location: Oak Ridge National Labs, Austin East High School, 2800 Martin Luther King, Jr. Ave., Knoxville, TN 37914, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.178 Network Name: CRAIGMON-NET Location: Oak Ridge National Labs, Craigmont High School, 3333 Covington Pike, Memphis, TN 38128, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.179 Network Name: CENTRLHS-NET Location: Oak Ridge National Labs, Central High School, 1115 Highway 62, P.O. Box 303, Wartburg, TN 37887, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.180 Network Name: GILESCOU-NET Location: Oak Ridge National Labs, Giles County High School, 200 Sheila Frost Drive, Pulaski, TN 38478, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.182 Network Name: HORACEMA-NET Location: Oak Ridge National Labs, Horace Maynard High School, P.O. Box 246, Maynardville, TN 37807, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.183 Network Name: SOUTHSID-NET Location: Oak Ridge National Labs, South Side High School, 44 Harts Bridge Rd., Jackson, TN 38301, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.190.8 Network Name: HKS-WEST-NET Location: Hibbett, Karlson, and Sorensen Inc., 1080 Main Street, Pawtucket, RI 02860, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.190.254 Network Name: CAMPBELLSVIL Location: Campbellsville College, 200 West College Streeet, Campbellsville, KY 42718, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.193.194 Network Name: CITICORP-C1 Location: Citicorp Global Information Network, Floor 43, 1 Court Square, Long Island City, NY 11120-0001, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.195.29 Network Name: ROANOKE-NET Location: IBM Electronic Vendor Support, 9 Village Circle, Roanoke, TX 76262, USA Country Code: US 1:754 T1-T3 Network Interconnect (Houston, TX) 2:751 T1-T3 Network Interconnect (San Diego, CA) 3:750 T1-T3 Network Interconnect (Ann Arbor, MI) 4:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.195.153 Network Name: ACUSD-1 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.195.154 Network Name: ACUSD-2 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.195.155 Network Name: ACUSD-3 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.195.167 Network Name: AMOCO-NET Location: AMOCO Corporation, Tulsa Data Center, 519 South Boston, Tulsa, OK 74102-4605, USA Country Code: US 1:754 T1-T3 Network Interconnect (Houston, TX) 2:751 T1-T3 Network Interconnect (San Diego, CA) 3:750 T1-T3 Network Interconnect (Ann Arbor, MI) 4:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.206.38 Network Name: ENT-IMG Location: CST Entertainment Imaging, Inc., 6171 W. Century Blvd., Los Angeles, CA 90045, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.21 Network Name: USE Location: Uni-Ops Systems East, 2035 E. 46th St., Indianapolis, IN 46205, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Total configured T1 networks: 6427 T3 Network: ---------- Network IP: 128.58 Network Name: SLCS-BNET Location: Schlumberger Laboratory for Computer Science, 8311 North RR 620, P.O. Box 200015, Austin, TX 78720-0015, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 3:114 SESQUINET Regional Network 4:200 BARRNet Network IP: 129.87 Network Name: SLBSDRNET Location: Schlumberger-Doll Research, Old Quarry Road, Ridgefield, CT 06788-4108, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 3:114 SESQUINET Regional Network 4:200 BARRNet Network IP: 130.37 Network Name: VU-NET Location: Vrije University, De Boelelaan 1081, 1081 HV Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) 43:701 Alternet Network IP: 132.80 Network Name: NG-CONC1 Location: National Guard Bureau, The Pentagon, Washington, DC 20310, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 134.39 Network Name: CTCNET1 Location: Communications Technology Center, 3860 159th NE, Suite 150, Redmond, WA 98052, USA Country Code: US 1:1331 ANS Seattle - DNSS 91 Network IP: 149.246 Network Name: SIENKE-LAN Location: Siemens AG, OeN NKE A2, Postfach 700078, D-W-8000 Muenchen 70, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 155.37 Network Name: UCHC-NET Location: Univ. of Connecticut Health Center, MC 3405, Neuroscience Center, 263 Farmington Avenue, Farmington, CT 06030, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 155.178 Network Name: FAA Location: FAA Technical Center, Atlantic City Airport, NJ 08405, USA Country Code: US 1:1800 ICM (FIX-East) Network IP: 158.125 Network Name: DEPT-LUT-AC Location: Lougborough University, Loughborough, Leicestershire LE11 3TU, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) Network IP: 159.77 Network Name: DISA-EUROPE Location: DISA-EUROPE/DEKC, Unit 30403, APO AE 09131 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 161.133 Network Name: DELTACOLLEGE Location: Delta College, 6263 Mackinaw Road, University Center, MI 48710, USA Country Code: US 1:237 MERIT network 2:233 MERIT network Network IP: 163.125 Network Name: CFT-NET Location: Creative Friendly Technologies, Inc., 6226 East Sligh Avenue, Tampa, FL 33617-1905, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 163.150 Network Name: SBCSS Location: San Bernardino County Superintendent of Schools, 601 North "E" Street, San Bernardino, CA 92410-3093, USA Country Code: US 1:195 SDSC Regional network Network IP: 163.228 Network Name: MMM-DOM2 Location: 3M Corporation, 3M Center, Building 224-4n-27, St. Paul, MN 55144-1000, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 163.229 Network Name: SC92-NET Location: Minnesota Supercomputer Center, 1200 Washington Avenue South, Minneapolis, MN 55415, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 192.6.10 Network Name: HPLB-HP Location: Hewlett-Packard Company, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.6.135 Network Name: HP-CUP1 Location: Hewlett-Packard Company, Information Networks Division, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.6.136 Network Name: HP-ATL Location: Hewlett-Packard Company, Information Networks Division, 19420 Homestead Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.31.231 Network Name: VUCS-AMS Location: Vrije University, Department of Computer Science and Mathematics, De Boelelaan 1081, 1081 HV Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) 43:701 Alternet Network IP: 192.33.36 Network Name: VUPHYS-AMS Location: Vrije University, Department Physics and Astronomy, De Boelelaan 1081, 1081 HV Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) 43:701 Alternet Network IP: 192.42.96 Network Name: SWIVAX Location: University of Amsterdam, 1016 BS Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) 43:701 Alternet Network IP: 192.42.115 Network Name: SARA-NET Location: SARA - Academic Computing Services Amsterdam, P.O. Box 4613, 1009 AP Amsterdam, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) 43:701 Alternet Network IP: 192.76.135 Network Name: TOOLSNET Location: Tools GmbH, Kessenicher Str. 108, D-W-5300 Bonn 1, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 192.102.158 Network Name: FHG-ISST-NET Location: Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.124.140 Network Name: MAK Location: Mak Technologies, 380 Green Street, Cambridge, MA 02139, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.129.41 Network Name: SIEFUERTH Location: Siemens Fuerth, Fuerth, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.146.195 Network Name: CSD Location: United Technologies, Chemical Systems, 600 Metcalf Road, San Jose, CA 95138-9121, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.153.140 Network Name: AEAEN-LAN Location: HQUSAREUR, DCSENG, Unit 29351, APO AE 09014 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.156.221 Network Name: IBMNET6 Location: IBM Industrial Technology Center, 1311 Mamaroneck Ave., White Plains, NY 10605, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 192.187.135 Network Name: NETCOM38 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.188.94 Network Name: NET-CTAENG Location: CTA INC., 5670 Greenwood Plaza Blvd. Suite 200, Englewood, CO 80111, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.188.130 Network Name: CUMBERLAND Location: Cumberland College, CIS Dept., Walnut Street, Williamsburg, KY 40769, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.188.177 Network Name: AUSTINEA-NET Location: Oak Ridge National Labs, Austin East High School, 2800 Martin Luther King, Jr. Ave., Knoxville, TN 37914, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.188.178 Network Name: CRAIGMON-NET Location: Oak Ridge National Labs, Craigmont High School, 3333 Covington Pike, Memphis, TN 38128, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.188.179 Network Name: CENTRLHS-NET Location: Oak Ridge National Labs, Central High School, 1115 Highway 62, P.O. Box 303, Wartburg, TN 37887, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.188.180 Network Name: GILESCOU-NET Location: Oak Ridge National Labs, Giles County High School, 200 Sheila Frost Drive, Pulaski, TN 38478, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.188.182 Network Name: HORACEMA-NET Location: Oak Ridge National Labs, Horace Maynard High School, P.O. Box 246, Maynardville, TN 37807, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.188.183 Network Name: SOUTHSID-NET Location: Oak Ridge National Labs, South Side High School, 44 Harts Bridge Rd., Jackson, TN 38301, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.190.8 Network Name: HKS-WEST-NET Location: Hibbett, Karlson, and Sorensen Inc., 1080 Main Street, Pawtucket, RI 02860, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.190.254 Network Name: CAMPBELLSVIL Location: Campbellsville College, 200 West College Streeet, Campbellsville, KY 42718, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.193.194 Network Name: CITICORP-C1 Location: Citicorp Global Information Network, Floor 43, 1 Court Square, Long Island City, NY 11120-0001, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.195.29 Network Name: ROANOKE-NET Location: IBM Electronic Vendor Support, 9 Village Circle, Roanoke, TX 76262, USA Country Code: US 1:1956 IBMEVS-AS Network IP: 192.195.153 Network Name: ACUSD-1 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet Network IP: 192.195.154 Network Name: ACUSD-2 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet Network IP: 192.195.155 Network Name: ACUSD-3 Location: University of San Diego Academic Computing, 5998 Alcala Park, Serra Hall Room 188, San Diego, CA 92110, USA Country Code: US 1:1740 CERFnet Network IP: 192.195.167 Network Name: AMOCO-NET Location: AMOCO Corporation, Tulsa Data Center, 519 South Boston, Tulsa, OK 74102-4605, USA Country Code: US 1:1330 ANS St. Louis - DNSS 83 Network IP: 192.206.38 Network Name: ENT-IMG Location: CST Entertainment Imaging, Inc., 6171 W. Century Blvd., Los Angeles, CA 90045, USA Country Code: US 1:1740 CERFnet Network IP: 192.207.21 Network Name: USE Location: Uni-Ops Systems East, 2035 E. 46th St., Indianapolis, IN 46205, USA Country Code: US 1:701 Alternet 2:702 Alternet Total configured T3 networks: 5721 The following T3 Routers have also been added: AS Number: 114 AS Notes: SESQUINET Regional Network AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.139 - Rice University Houston, TX Gate: 128.241.0.88 - rice4 Rice University, Houston, TX AS Number: 600 AS Notes: OARNET, Cleveland, OH AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.168 - ENSS 168 - OARnet Cleveland, OH Gate: 192.88.195.3 - gwcsp3.oar.net OARNET, Cleveland, OH AS Number: 1757 AS Notes: Mead Data Central AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.193 - Mead Data Central, Miamisburg, Ohio - ENSS193 Miamisburg, Ohio, USA Gate: 192.73.216.3 - peer.meaddata.com Mead Data Central, Miamisburg, OH ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET --Steve Widmayer Merit/NSFNET - - - - - - - - - - - - - - - - - From rty Tue Sep 8 05:32:28 1992 Received: by merit.edu (5.65/1123-1.0) id AA00249; Tue, 8 Sep 92 05:32:34 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA00243; Tue, 8 Sep 92 05:32:28 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA25268; Tue, 8 Sep 92 05:32:27 EDT Date: Tue, 8 Sep 92 05:32:27 EDT Message-Id: <9209080932.AA25268@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database, and routes should be in effect as of 08:00 EDT. T1 Network: ---------- Network IP: 133.34 Network Name: YNU Location: Yokohama National University, Information Processing Center, Tokiwadai 156, Hodogaya-ku, Yokohama 240, JAPAN Country Code: JP 1:1240 USSPRINT - Palo Alto, CA Network IP: 139.153 Network Name: STIRUNIV-LAN Location: University of Stirling, Stirling, FK9 4LA, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 141.241 Network Name: KING-AC Location: Kingston University, Penrhyn Road, Kingston-upon-Thames, Surrey KT1 2EE, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 150.162 Network Name: UFSC-ANSC Location: Universidade Federal de Santa Catarina, Nucleo de Processamento de Dados, Campus Universitario Trindade - CP 88049, Santa Catarina, BRAZIL Country Code: BR 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 155.230 Network Name: KPNU-NET Location: Kyungpook National University, San-Gyuk-3-Dong, Puk-Gu, Taegu, KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 159.202 Network Name: IDSCORPNET Location: IDS Financial Services, IDS Tower-10, OP4/288, Mineapolis, MN 55440, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.102.218 Network Name: CNTRCOLL-NET Location: Centre College, Olin Hall, Room 30, 700 West Walnut Street, Danville, KY 40422, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.152.99 Network Name: UHC-NET Location: United HealthCare Corporation, 9900 Bren Road East, Minnetonka, MN 55343, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.187.134 Network Name: NETCOM37 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.67 Network Name: NET-CRHS Location: Cranston High School, 845 Park Avenue, Cranston, RI 02910, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.208.128 Network Name: NETBLK-MSSTATE-128 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.129 Network Name: NETBLK-MSSTATE-129 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.130 Network Name: NETBLK-MSSTATE-130 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.131 Network Name: NETBLK-MSSTATE-131 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.132 Network Name: NETBLK-MSSTATE-132 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.133 Network Name: NETBLK-MSSTATE-133 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.134 Network Name: NETBLK-MSSTATE-134 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.135 Network Name: NETBLK-MSSTATE-135 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.136 Network Name: NETBLK-MSSTATE-136 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.137 Network Name: NETBLK-MSSTATE-137 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.208.138 Network Name: NETBLK-MSSTATE-138 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6447 T3 Network: ---------- Network IP: 139.153 Network Name: STIRUNIV-LAN Location: University of Stirling, Stirling, FK9 4LA, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) Network IP: 141.241 Network Name: KING-AC Location: Kingston University, Penrhyn Road, Kingston-upon-Thames, Surrey KT1 2EE, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) Network IP: 155.230 Network Name: KPNU-NET Location: Kyungpook National University, San-Gyuk-3-Dong, Puk-Gu, Taegu, KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 159.202 Network Name: IDSCORPNET Location: IDS Financial Services, IDS Tower-10, OP4/288, Mineapolis, MN 55440, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.102.218 Network Name: CNTRCOLL-NET Location: Centre College, Olin Hall, Room 30, 700 West Walnut Street, Danville, KY 40422, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.152.99 Network Name: UHC-NET Location: United HealthCare Corporation, 9900 Bren Road East, Minnetonka, MN 55343, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.187.134 Network Name: NETCOM37 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.188.67 Network Name: NET-CRHS Location: Cranston High School, 845 Park Avenue, Cranston, RI 02910, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.208.128 Network Name: NETBLK-MSSTATE-128 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.129 Network Name: NETBLK-MSSTATE-129 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.130 Network Name: NETBLK-MSSTATE-130 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.131 Network Name: NETBLK-MSSTATE-131 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.132 Network Name: NETBLK-MSSTATE-132 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.133 Network Name: NETBLK-MSSTATE-133 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.134 Network Name: NETBLK-MSSTATE-134 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.135 Network Name: NETBLK-MSSTATE-135 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.136 Network Name: NETBLK-MSSTATE-136 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.137 Network Name: NETBLK-MSSTATE-137 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.208.138 Network Name: NETBLK-MSSTATE-138 Location: Mississippi State University, PO Drawer CC, Mississippi State University, MS 39762, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Total configured T3 networks: 5739 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From donnab@CERF.NET Tue Sep 8 18:33:30 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA01869; Tue, 8 Sep 92 18:33:30 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA12360; Tue, 8 Sep 92 15:33:52 PDT Date: Tue, 8 Sep 92 15:33:52 PDT From: Donna Bigley Message-Id: <9209082233.AA12360@nic.cerf.net> To: help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, August 31, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, August 31st through Sunday, September 6th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 6-sept-92.txt All times are in Pacific Daylight Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 1273 SITE: CITOH SITES AFFECTED: CITOH TIME STARTED: Mon 08-31-92 01:48 TIME ENDING: Mon 08-31-92 09:01 TIME ELAPSED: 7 hours, 13 min REASON: Equipment Trouble TICKET #: 1274 SITE: MARK V SITES AFFECTED: MARK V TIME STARTED: Mon 08-31-92 07:13 TIME ENDING: Mon 08-31-92 08:43 TIME ELAPSED: 1 hour, 30 min REASON: Equipment Trouble TICKET #: 1277 SITE: CADAM SITES AFFECTED: CADAM TIME STARTED: Mon 08-31-92 18:34 TIME ENDING: Mon 08-31-92 21:29 TIME ELAPSED: 2 hours, 55 min (Intermittent Access) REASON: Unscheduled Outage TICKET #: 1268 SITE: HUGHES-CIT SITES AFFECTED: HUGHES-CIT TIME STARTED: Tue 09-01-92 00:09 TIME ENDING: Tue 09-01-92 01:36 TIME ELAPSED: 1 hour, 27 min REASON: CERF/Vendor Scheduled Maintenance TICKET #: 1290 SITE: CADAM SITES AFFECTED: CADAM TIME STARTED: Fri 09-04-92 11:52 TIME ENDING: Fri 09-04-92 12:12 TIME ELAPSED: 20 min REASON: Unknown (Cisco Box Didn't Restart) TICKET #: 1293 SITE: IRVINE COMPILER SITES AFFECTED: IRVINE COMPILER TIME STARTED: Fri 09-04-92 14:14 TIME ENDING: Fri 09-04-92 15:23 TIME ELAPSED: 1 hour 9 min REASON: Software Trouble TICKET #: 1291 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: Sat 09-05-92 08:36 TIME ENDING: Sat 09-05-92 16:12 TIME ELAPSED: 7 hours 36 min. REASON: Link Failure (Cisco Box Didn't Reset and Contacted Worldcom) TICKET #: 1292 SITE: CICESE SITES AFFECTED: CICESE TIME STARTED: Sat 09-05-92 10:01 TIME ENDING: Sat 09-05-92 17:28 TIME ELAPSED: 7 hours 27 min. REASON: Vendor Scheduled Maintenance TICKET #: 1240 SITE: SDSC-CIT T1 SITES AFFECTED: SDSC-CIT T1 TIME STARTED: Sat 09-05-92 22:08 TIME ENDING: Sat 09-05-92 22:11 TIME ELAPSED: 3 min. REASON: Vender Schedule Maintenance (MCI Maintenance) TICKET #: 1291 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: Sun 09-06-92 03:59 TIME ENDING: Sun 09-06-92 10:26 TIME STARTED: Sun 09-06-92 17:59 TIME ENDING: Sun 09-06-92 20:14 TIME ELAPSED: 8 hours 42 min. REASON: Link Failure (Between IDMC and the Earth Station in Korea) TICKET #: 1282 SITE: UCOP-SDSC T1 SITES AFFECTED: UCOP-SDSC T1 TIME STARTED: Sun 09-06-92 04:57 TIME ENDING: Sun 09-06-92 04:58 TIME ELAPSED: 1 min. REASON: Vendor Scheduled Maintenance (MCI Maintenance) TICKET #: 1282 SITE: UCI-SDSC T1 SITES AFFECTED: UCI-SDSC T1 TIME STARTED: Sun 09-06-92 06:21 TIME ENDING: Sun 09-06-92 06:24 TIME ELAPSED: 3 min. REASON: Vendor Scheduled Maintenance (MCI Maintenance) ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps 00.1% 15:00 SDSC/GA 10.000 mbps 00.2% 02:00 SDSC/CALTECH 1.544 mbps 10.9% 06:00 SDSC/UCI 1.544 mbps 06.7% 15:00 SDSC/UCLA 1.544 mbps 08.0% 15:00 SDSC/UCOP 1.544 mbps 04.8% 06:00 UCI/UCLA 1.544 mbps 01.2% 15:00 SDSC/UCR 512 kbps 03.0% 14:00 UCLA/UCSB 512 kbps 09.3% 15:00 CALTECH/HUGHES 1.544 mbps 00.4% 00:00 SDSC/AGI 1.544 mbps 00.1% 08:00 SDSC/BIOSYM 1.544 mbps 00.5% 12:00 SDSC/GD 1.544 mbps 01.4% 10:00 SDSC/SAIC 1.544 mbps 02.0% 12:00 SDSC/SEASPACE 1.544 mbps 00.2% 09:00 UCI/CSU CO(SWRL) 1.544 mbps 03.4% 15:00 UCI/MDC 1.544 mbps 02.9% 07:00 UCLA/GETTY 1.544 mbps 00.1% 13:00 UCOP/APPLE 1.544 mbps 01.2% 11:00 UCOP/CISCO 1.544 mbps 00.2% 06:00 UCR/LLUMC 1.544 mbps 00.4% 07:00 CALTECH/AJS 56 kbps 01.4% 14:00 CALTECH/CADAM 56 kbps 00.7% 20:00 CALTECH/CITY OF HOPE 56 kbps 00.5% 17:00 CALTECH/CLAREMONT 56 kbps 21.9% 06:00 CALTECH/DISNEY 56 kbps 05.4% 14:00 CALTECH/OXY 56 kbps 06.1% 18:00 CALTECH/SCAQMD 56 kbps 00.4% 06:00 SDSC/API 56 kbps 07.5% 20:00 SDSC/CICESE 56 kbps 02.5% 09:00 SDSC/KOREA 56 kbps 08.7% 00:00 SDSC/QUALCOMM 56 kbps 11.9% 16:00 SDSC/REDE-RIO 56 kbps 12.2% 14:00 SDSC/SCIH 56 kbps 09.0% 15:00 SDSC/SDG&E 56 kbps 00.1% 17:00 SDSC/USD 56 kbps 06.5% 08:00 SDSC/USIU 56 kbps 04.4% 17:00 UCI/BECKMAN 56 kbps 06.6% 06:00 UCI/CCCD 56 kbps 05.6% 03:00 UCI/CMD 56 kbps 01.6% 17:00 UCI/EMULEX 56 kbps 02.0% 10:00 UCI/FULLERTON 56 kbps 02.0% 13:00 UCI/HUGHES 56 kbps 13.2% 16:00 UCI/ICC 56 kbps 05.2% 20:00 UCI/MTI 56 kbps 03.5% 06:00 UCI/SPARTA 56 kbps 04.5% 06:00 UCI/UNOCAL 56 kbps 08.0% 13:00 UCLA/CRSS 56 kbps 00.6% 16:00 UCLA/DATAPRODUCTS 56 kbps 01.1% 15:00 UCLA/GTE 56 kbps 02.9% 08:00 UCLA/ISX 56 kbps 03.2% 16:00 UCLA/LITTON 56 kbps 00.5% 13:00 UCLA/PEPPERDINE 56 kbps 00.9% 13:00 UCLA/QUOTRON 56 kbps 07.0% 21:00 UCLA/SMC 56 kbps 05.1% 16:00 UCOP/FARALLON 56 kbps 04.5% 14:00 UCOP/INTEL 56 kbps 17.1% 16:00 UCOP/LSIL 56 kbps 07.2% 19:00 UCOP/NETLABS 56 kbps 49.4% 14:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PDT on Sept. 7, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 57 days 11 hours 37 minutes SDSC LongBoard [134.24.99.254] Up: 83 days 08 hours 21 minutes SDSC Drzog [132.249.16.13] Up: 116 days 14 hours 24 minutes SDSC Hang10 [132.249.16.15] Up: 116 days 14 hours 24 minutes UCI [128.200.1.101] Up: 43 days 15 hours 24 minutes UCLA [128.97.130.10] Up: 154 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 166 days 16 hours 38 minutes UCR [134.24.108.105] Up: 57 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 57 days 09 hours 43 minutes APPLE [134.24.70.200] Up: 315 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 87 days 07 hours 13 minutes CISCO Systems [134.24.54.200] Up: 05 days 17 hours 26 minutes [Equipment Trouble] CSUCO/SWRL [130.150.102.200] Up: 37 days 18 hours 22 minutes GA [134.24.20.10] Up: 57 days 12 hours 14 minutes GD [134.24.60.200] Up: 129 days 16 hours 18 minutes GETTY [134.24.235.200] Up: 24 days 07 hours 02 minutes HUGHES_CIT [134.24.103.200] Up: 38 days 13 hours 53 minutes LLUMC [134.24.208.200] Up: 36 days 13 hours 45 minutes MDC [134.24.65.200] Up: 16 days 08 hours 00 minutes SAIC [134.24.53.208] Up: 116 days 14 hours 10 minutes UCSB [134.24.107.107] Up: 74 days 15 hours 45 minutes CERF 56 AJS [134.24.225.101] Up: 26 days 13 hours 24 minutes API [134.24.224.200] Up: 73 days 13 hours 18 minutes BECKMAN [134.24.237.200] Up: 96 days 12 hours 10 minutes CADAM [134.24.229.200] Up: 09 days 06 hours 23 minutes CCCD [134.24.219.200] Up: 70 days 19 hours 14 minutes CICESE [134.24.227.200] Up: 110 days 09 hours 44 minutes CITY_OF_HOPE [134.24.233.200] Up: 14 days 23 hours 42 minutes CLAREMONT [134.24.206.109] Up: 33 days 21 hours 38 minutes CMD [134.24.218.200] Up: 02 days 07 hours 29 minutes [Equipment Trouble] CRSS [134.24.232.200] Up: 32 days 12 hours 16 minutes DATAPRODUCTS [134.24.211.200] Up: 159 days 13 hours 01 minutes DISNEY [134.24.207.211] Up: 20 days 19 hours 57 minutes EMULEX [134.24.209.212] Up: 08 days 07 hours 37 minutes FARALLON [134.24.56.200] Up: 34 days 15 hours 51 minutes FULLERTON [134.24.214.217] Up: 70 days 17 hours 55 minutes GTE [134.24.212.200] Up: 175 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 29 days 16 hours 21 minutes INTEL [134.24.73.200] Up: 162 days 11 hours 34 minutes ICC [134.24.238.200] Up: 60 days 08 hours 39 minutes LITTON [134.24.213.200] Up: 16 days 13 hours 29 minutes LSIL [134.24.72.200] Up: 124 days 08 hours 26 minutes MTI [134.24.216.100] Up: 12 days 08 hours 48 minutes NETLABS [134.24.71.200] Up: 39 days 09 hours 33 minutes OXY [134.24.205.108] Up: 06 days 17 hours 15 minutes [Equipment Trouble] PEPPERDINE [134.24.203.218] Up: 149 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 07 days 01 hours 48 minutes QUOTRON [134.24.230.202] Up: 14 days 06 hours 06 minutes REDE_RIO [134.24.112.200] Up: 09 days 14 hours 32 minutes SANTA MONICA [134.24.210.219] Up: 39 days 13 hours 40 minutes SCAQMD [134.24.234.200] Up: 262 days 14 hours 27 minutes SCI-HOR [134.24.109.205] Up: 117 days 06 hours 02 minutes SDG&E [134.24.226.200] Up: 96 days 13 hours 39 minutes SEASPACE [134.24.80.200] Up: 151 days 11 hours 26 minutes SERI/KOREA [134.24.223.200] Up: 12 days 01 hours 41 minutes SPARTA [134.24.215.200] Up: 160 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 185 days 01 hours 57 minutes USD [134.24.201.106] Up: 27 days 17 hours 00 minutes USIU [134.24.222.215] Up: 428 days 17 hours 07 minutes DIAL n' CERF Plus 14.4 CITOH [161.1.1.1] Up: 10 days 11 hours 41 minutes MARKV [192.122.251.6] Up: 10 days 01 hours 14 minutes PEREGRINE [192.72.253.97] Up: 02 days 15 hours 06 minutes [New Installation] DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 38 days 11 hours 19 minutes DNC-UCI [134.24.2.2] Up: 43 days 15 hours 25 minutes DNC-UCLA [134.24.3.2] Up: 02 days 15 hours 05 minutes [Equipment Trouble] DNC-CALTECH [134.24.4.2] Up: 10 days 01 hours 14 minutes DNC-UCOP [134.24.5.2] Up: 69 days 04 hours 29 minutes CIT-NETBLAZER [130.152.104.1] Up: 59 days 13 hours 47 minutes SDSC-NETBLAZER [192.102.249.25] Up: 02 days 15 hours 05 minutes [CERFnet Site Activity] UCI-NETBLAZER [134.24.92.2] Up: 11 days 06 hours 44 minutes UCLA-NETBLAZER [134.24.93.2] Up: 18 days 06 hours 54 minutes UCOP-NETBLAZER [134.24.250.2] Up: 166 days 23 hours 54 minutes - - - - - - - - - - - - - - - - - From mak Thu Sep 10 23:07:17 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA27859; Thu, 10 Sep 92 23:07:17 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA28221; Thu, 10 Sep 92 23:07:16 EDT Date: Thu, 10 Sep 92 23:07:16 EDT From: mak Message-Id: <9209110307.AA28221@home.merit.edu> To: regional-techs Subject: August Backbone Engineering Report ANSNET/NSFNET Backbone Engineering Report August 1992 Jordan Becker, ANS Mark Knopper, Merit becker@ans.net mak@merit.edu T3 Backbone Status ================== The system software and routing software for the T3 routers has stabilized. The new RS/960 FDDI card has completed testing and deployment schedules are in progress. A new system software build with support for 10,000 routes maintained locally on the smart-card interfaces is being tested on the T3 Research Network. Planning is now underway for dismantling of the T1 backbone which is targeted for November. Several steps to be completed prior to dismantling the T1 backbone include support for OSI CLNP transport over the T3 backbone, and the deployment of the redundant backup circuit plan for the T3 ENSS gateways at each regional network. Further activities in support of the Phase IV upgrade to the T3 backbone are in progress. Backbone Traffic and Routing Statistics ======================================= The total inbound packet count for the T1 network during August was 3,903,906,145, down 17.9% from July. 298,961,253 of these packets entered from the T3 network. The total inbound packet count for the T3 network was 13,051,979,670, up 1.3% from July. 129,835,094 of these packets entered from the T1 network. The combined total inbound packet count for the T1 and T3 networks (less cross network traffic) was 16,527,089,468 down 3.1% from July. Reports on T3 backbone byte counts for June, July and August were incorrect due to SNMP reporting problems. These will be corrected soon in reports available on the nis.nsf.net machine. The totals for June, July, and August are 2.279, 2.546, and 2.548 trillion, respectively. As of August 31, the number of networks configured in the NSFNET Policy Routing Database was 6360 for the T1 backbone, and 5594 for the T3 backbone. Of these, 1233 networks were never announced to the T1 backbone and 1102 were never announced to the T3 backbone. For the T1, the maximum number of networks announced to the backbone during the month (from samples collected every 15 minutes) was 4866; on the T3 the maximum number of announced networks was 4206. Average announced networks on 8/31 were 4817 to T1, and 4161 to T3. New FDDI Interface Adapter for ENSS Nodes ========================================= We have a new RS960 FDDI adapter for the RS/6000 router that provides much improved reliability and performance. It was our hope that the new RS960 FDDI interface adapter targeted to upgrade the older 'Hawthorne' technology FDDI adapters in the the T3 ENSS routers would be ready for deployment in early August. However several serious bugs were encountered during testing in late July, and the upgrade has been delayed by more than a month. Fortunately we have corrected or worked around all of these known remaining bugs. We are re-running our full suite of regression tests, and a full set of stress tests on the T3 test network during the labor day weekend. Pending the successful completion of our tests, we expect that the first set of FDDI adapter upgrades on the production T3 ENSS nodes could begining during the week of 9/7. We would like to begin planning for the installation of these new interface adapters at ENSS128 (Palo Alto), ENSS135 (San Diego), ENSS129 (Champaign), and ENSS132 (Pittsburgh). We will develop plans for any further FDDI deployments after these first 4 installations have been successfully completed. Dismantling the T1 Backbone =========================== The current target for dismantling the T1 backbone is November '92. This can be accomplished once the remaining networks using the T1 backbone have been cut over to the T3 backbone (these are: ESnet, EASInet, Mexican Networks at Boulder, and CA*net); an OSI CLNP transport capability over the T3 backbone is in place; the T3 ENSS nodes are backed up by additional T1 circuits terminating at alternate backbone POPs; and the network-to-network source/destination pair statistics matrix is available on the T3 backbone. These activities are described below. Since the RCP nodes on the T1 backbone are experiencing further congestion and performance problems due to the growth in networks, we are planning to reduce the number of networks announced to the T1 nodes by the T3 interconnect gateways. This will eliminate the use of the T3 to back up the T1 for those networks yet to cut over, in the event of a failure in the T1 network. Remaining Network Cutovers -------------------------- The ESnet cutover is waiting for a new version of software to be configured for the ESnet router peers at FIX-West and FIX-East. The Mexican autonomous system will be cut over soon, pending communication with the folks in Mexico. We are developing a plan that will allow EASInet to peer directly with the T3 network. The plan for CA*net is to remove the RT from the token ring on the NSS nodes at Seattle, Princeton and Ithaca, configure them to run the CA*net kernel and gated, and peer directly across the ethernet to the T3 ENSS at these sites. OSI Support Plan ---------------- In order to dismantle the T1 backbone, we need to support the transport of OSI (CLNP) packets across the T3 network. Because we would like to target dismantling of the T1 backbone for sometime in late 1992 and the T3 backbone software for support of OSI is still in test, we would like to proceed with a phased (multi-step) migration for support of OSI switching over the T3 network in order to ensure network stability as we introduce OSI software support. The migration plan involves several steps: 1. Convert RT/PC EPSP routers that reside on the shared ENSS LAN into OSI packet encapsulators. This would be done at the 8 or so sites where there are regionals that currently support OSI switching services. OSI traffic is encapsulated in an IP packet on the RT router and forwarded as an IP packet across the T3 network to a destination RT de-encapsulator. This software already exists and can support the migration of OSI traffic off of the T1 backbone, with no software changes required to the T3 backbone. This software is entering test now and could be running in production by early October. 2. Introduce new RS/6000 OSI encapsulator systems that are the running AIX 3.2 operating system with native CLNP support. These machines will replace the RT OSI encapsulators on the shared ENSS LAN. As the CLNP software gets more stable, the RS/6000 system can begin to support non-encapsulated dynamic OSI routing. There are still no changes required to the production T3 network software in this step. This step could occur sometime in the mid- fall. 3. Deploy the AIX 3.2 operating system and native CLNP switching software on the T3 routers across the backbone. The experience gained in step#2 above will facilitate this migration. This step is expected sometime in January 1993. T1 ENSS Backup Circuits ----------------------- The T1 backbone is currently providing backup connectivity in the event of a problem with the T3 backbone. Since the T3 ENSS nodes are currently singly-connected to a CNSS at an MCI POP, the single T3 circuit and CNSS node represent a single point of failure. As a backup plan, each T3 ENSS will be connected to a new T1 circuit which terminates at a different backbone POP CNSS. This will allow bypass recovery in the event of circuit or CNSS failure. We are executing a test plan on the test network to measure internal routing convergence times and end-user observations during a backup transition. These circuits are being ordered now and are expected to be in place by late October. Network Source/Destination Statistics ------------------------------------- During the migration to the smart card forwarding technology (RS960/T960) we temporarily lost the ability to collect network source/destination pair traffic statistics. This is because packets were no longer passing through the RS/6000 system processor where the statistics collection application software ran. We are now testing new software for near-term deployment that will allow us to continue to collect statistics for each network source/destination pair. These statistics include packets_in, packets_out, bytes_in, and bytes_out. The statistics will be cached on the RS960 and T960 interfaces and uploaded to the RS/6000 system for processing and transmission to a central collection machine. Increase Routing Table Sizes on T3 Network ========================================== We continue to experience an increase in ANSNET/NSFNET advertised networks, (see Backbone Traffic and Routing Statistics, above) The current on-card routing table size on the T3 router RS960 card (T3/FDDI) and T960 card (T1/ethernet) supports 6,000 destination networks with up to 4 alternate routes per destination. The current on-card routing tables are managing on the order of 12K routes (including alternate routes to the same destination). We are now testing new software for the RS960 and T960 interfaces that will be deployed shortly that supports up to 10,000 destination networks with up to 4 alternate routes per destination. This software will be deployed on the T3 network in the near future. We also continue to work on support for on-card route caching which will significantly increase the upper limit on the number of routes to unique destination networks that may be supported. This software will be available with the AIX 3.2 operating system release of the router software in early 1Q93. Phase-IV T3 Network Upgrade Status ================================== The scheduled upgrades to the T3 backbone discussed in the July report are continuing on schedule and will allow the dismantling of the T1 backbone. The major features of this plan include: 1) T3 ENSS FDDI interface upgrades to new RS/960 card. This is currently being scheduled at 4 regional sites. 2) T3 ENSS backup connections are being installed. A T1 circuit will be installed at each T3 ENSS to allow a backup connection to a different CNSS. This will provide some redundancy in the case of T3 circuit or primary CNSS failure. These circuits are scheduled for cutin in October. 3) T3 DSU PROM upgrades. A problem was uncovered in testing the new DSU firmware. The new firmware supports additional SNMP function and fixes a few non-critical bugs. Since this problem was uncovered, a fix has been provided. However the testnet has been occupied with FDDI and other system testing since then. Therefore the upgrades to the DSUs that were scheduled to begin on 9/14 will be postponed until early October. 4) The existing set of CNSS routers in the Washington D.C. area will be moved to an MCI POP in downtown Washington D.C. on 9/12 for closer proximity to several ENSS locations. The tail circuits of the existing network attachments to this POP will be reduced to local access circuits only. 5) The installation of a new CNSS in Atlanta is scheduled for 9/26 to reduce the GA Tech T3 tail to local access only, and provide expansion capability in the southeast. T3 Network Performance Enhancements =================================== The general approach to engineering the T3 network has been to prioritze enhancements that improve stability rather than performance. Since the T3 network RS960 upgrade in May '92, the stability of the network has become very good, and we have been able to spend more resources focusing on the performance of the network, which has also improved significantly. With the upcoming deployment of the new RS960 FDDI adapter, we expect to observe higher peak bandwidth utilization across the T3 network, and higher aggregate packet traffic rates. In anticipation of this, we have conducted some baseline performance measurements on the T3 network that serve as a basis for continued tuning and improvement over time. T3 Network Delay ---------------- In order to analyze the delay across the T3 ANSNET, we start by measuring the delay incurred by each T3 router hop, and then measure the circuit propagation delay across all backbone circuits. We have MCI T3 circuit route mileage figures which can be calibrated with PING measurements to determine how much each hop through a T3 router adds to the round trip time. A set of round trip delay measurements was made using a special version of PING that records timestamps using the AIX system clock with microsecond precision. The technical details of the measurements may be described in a future report on the subject. The end result is that the round trip transit delay across a T3 router was measured to be about 0.33 ms (0.165ms one way delay), with a maximum variance between all samples on the same router of 0.03 ms. The T3 routers currently experience very little variance in delay at the current load on the T3 network. The T3 router transit hop delay is therefore negligible compared to the T3 circuit mileage propagation delay. It turns out that the round trip delay between the Washington POP and the San Franciso POP can be 77ms for packets traversing the southern route (Washington->Greensboro->Houston->Los Angeles->San Francisco) or 67ms for packets traversing the northern route (Washington- >New York->Cleveland->Chicago->San Francisco). During the timeframe of "Hawthorne" technology routers, it was appropriate to choose internal routing metrics that balanced load across redundant T3 paths, and minimized transit traffic on the routers. However now with RS960 technology, the requirement for load-balancing, minimizing transit traffic and hop count, and maintaining equal cost paths is no longer justified. With the introduction of the new Atlanta CNSS, we will explore adjustment of the internal T3 link metrics to minmize round-trip latency ENSS<->ENSS. This will improve overall network performance as perceived by end users. The summary on T3 network latency is: (1) Delays due to multiple hops in the T3 network are measurable, but not large enough to matter a whole lot. The observed T3 ANSNET one way delay associated with a single T3 router hop is 0.165mS per router (1.35mS cross country one way delay due to 8 router hops). This is neglible compared with the cross-country propogation delays (e.g. 35ms one way). It would require the addition of 30 T3 routers to a path to add 10 ms to the unloaded round trip time, given constant circuit mileage. Delays introduced by extra router hops are negligible compared to circuit mileage delays. (2) For small packets, like the default for ping and traceroute, the round trip delay is mostly dependent on circuit mileage, and is relatively independent of bandwidth (for T1 and beyond, at least). (3) All T3 links within the network are maintained at equal cost link metrics regardless of physical mileage. This was designed during the timeframe when RS/6000 routers were switching packets through the system processor, and hop count, and transit traffic through the router were important quantities to minimize. With the introduction of pure adapter level switching (e.g. no RS/6000 system processor involved in switching user datagrams), minimizing hop count and router transit traffic become less important. Minimizing overall ENSS<->ENSS delay becomes more important. (4) The T3 ANSNET maintains two different physical circuit routes between Washington D.C. and Palo Alto. Each of these routes represent equal cost paths, and therefore will split the traffic load between them. However one of these physical routes is about 600 miles longer than the other. This can introduce problems involving asymmetric routes internal to the T3 network, and sub-optimal latency. The T3 ANSNET circuits are physically diverse to avoid large scale network failures in the event of a fiber cut. Compromising physical route diversity is not planned. However some reduction of real T3 circuit mileage (and therefore about 5mS of delay) might be possible on the ANSNET with the installation of the Atlanta POP CNSS in September. ANS is conducting a review with MCI to determine whether the Washington->Greensboro->Houston->Los Angeles->Hayward physical route can be reduced in total circuit miles without compromising route network diversity. This might be possible as part of the plan to co-locate equipment within Atlanta. T3 Network Throughput --------------------- The RS960 adapter technology will support up to five T3 interfaces per router, with an individual T3 interface operating at switching rates in excess of 10K packets per second in each direction. The unit and system tests performed prior to the April '92 network upgrade required the CNSS routers to operate at 50KPPS+ aggregate switching rates, and 22Mbps+ in each direction with an average packet size of 270 bytes on a particular RS960 interface. The router has also been configured and tested in the lab to saturate a full 45Mbps T3 link. The performance that is currently observed by individual end users on the T3 network is largely determined by their access to the network. Access may be via an ethernet or an FDDI local area network. Many users have reported peak throughput observations up to 10Mbps across the T3 network using ethernet access. Several of the T3 network attachments support an FDDI local area network interface which, unfortunately, does not result in more than 14Mbps peak throughput across the T3 backbone right now. With the new RS960 FDDI adapter to be introduced in September, end-to-end network throughput may exceed 22Mbps in each direction (limited by the T3 adapter). The initial RS960 FDDI card software will support a 4000 byte MTU that will be increased later on with subsequent performance tuning. Further performance enhancements will be administered to the T3 backbone in the fall and winter to further approach peak 45Mbps switching rates for end-user applications. - - - - - - - - - - - - - - - - - From rty Fri Sep 11 07:06:20 1992 Received: by merit.edu (5.65/1123-1.0) id AA15416; Fri, 11 Sep 92 07:06:30 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA15406; Fri, 11 Sep 92 07:06:20 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA09513; Fri, 11 Sep 92 07:06:19 EDT Date: Fri, 11 Sep 92 07:06:19 EDT Message-Id: <9209111106.AA09513@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database, and routes should be in effect by 08:00 EDT. T1 Network: ---------- Network IP: 133.28 Network Name: KAINS-NET Location: Kanazawa University, Kodatsuno 2-40-20, Kanazawa-shi, Ishikawa 920, JAPAN Country Code: JP 1:1240 USSPRINT - Palo Alto, CA Network IP: 137.54 Network Name: VERNET Location: University of Virginia, Gilmer Hall, Charlottesville, VA 22903, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.62 Network Name: FHD-STGT Location: Fachhochschule fuer Druck, Nobelstr. 10 7000 Stuttgart 80, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.68 Network Name: BRAVE Location: Berufsakademie Ravensburg, Ravensburg, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.79 Network Name: FH-OFFENBURG Location: Fachhochschule Offenburg, Offenburg, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.192 Network Name: ICLDATA Location: ICL Data Oy, Kutomontie 18 C, SF-00380 Helsinki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 142.137 Network Name: ETS-NET Location: Ecole de Technologie Superieur, 4750 Henri-Julien St., Montreal, Quebec, CANADA Country Code: CA 1:603 CA*net router in Quebec 2:601 CA*net router in Toronto 3:602 CA*net router in Montreal Network IP: 155.31 Network Name: ERAU-FLORIDA Location: Academic Computing, Embry-Riddle Aeronautical University, 600 S. Clyde Morris Blvd., Daytona Beach, FL 32114-3900, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 155.44 Network Name: HMCO-NET Location: Houghton Mifflin Company, One Beacon Street, Boston, MA 02108, USA Country Code: US 1:1384 NEARnet Regional Network 2:1383 NEARnet Regional Network 3:560 NEARnet Regional Network 4:281 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 160.129 Network Name: VUMC Location: Vanderbilt University Medical Center, B-131 VUH, Vanderbilt University Hospital, Nashville, TN 37232-7330, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 160.143 Network Name: HURRICANE Location: Gateway Operations Center, Fort Richie, LA, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 160.144 Network Name: SENECA-NET2 Location: Management Information Systems, Commander, Seneca Army Depot, Building 115, Romulus, NY 14541-5001, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 161.13 Network Name: TXSWU Location: Southwestern University, Office of Information Systems, A. Frank Smith Library Center, Georgetown, TX 78626, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 163.152 Network Name: KUCCNET Location: Korea University, Anam-Dong, Sungbuk-Ku, Seoul 136-701, KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.86.93 Network Name: FALLSCH-GW6 Location: MTMC, 5611 Columbia Pike, Attn: ASQNG-OP-TS, Falls Church, VA 22041-5050, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.87.128 Network Name: HSBOS1 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:1800 ICM (FIX-East) Network IP: 192.87.129 Network Name: HSBOS2 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:1800 ICM (FIX-East) Network IP: 192.87.130 Network Name: HSBOS3 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:1800 ICM (FIX-East) Network IP: 192.87.131 Network Name: HSBOS4 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:1800 ICM (FIX-East) Network IP: 192.98.8 Network Name: OTOLNET Location: Oulu Institute of Technology, Kotkantie 1, SF-90250 Oulu, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.42 Network Name: OSITECHNET Location: Ositech Oy, Tekniikantie 12, SF-02150 Espoo, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.43 Network Name: MDATANET Location: Microdata Oy, Kuusisaarentie 3, SF-00340 Helsinki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.80 Network Name: TYT-SJK0 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.81 Network Name: TYT-SJK1 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.82 Network Name: TYT-SJK2 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.83 Network Name: TYT-SJK3 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.84 Network Name: TYT-SJK4 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.85 Network Name: TYT-SJK5 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.86 Network Name: MAKES-SJK1 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.98.87 Network Name: MAKES-SJK2 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.124.245 Network Name: IOW-NETWORK Location: Institut fuer Meeresforschung Warnemuende, Seestrasse 15, D-0-2530 Warnemuende, GERMANY Country Code: DE 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 192.134.146 Network Name: FR-IUSTI-EDU Location: IUSTI - Centre Universitaire de St Jerome, Avenue escadrille normandie niemem, F-13397 Marseille, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.134.147 Network Name: FR-IUSTI-REC Location: IUSTI - Centre Universitaire de St Jerome, Avenue escadrille normandie niemem, F-13397 Marseille, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.135.188 Network Name: ERRC Location: Eastern Regional Research Center, USDA-ARS-ERRC, 600 East Mermaid Lane, Philadelphia, PA 19118, USA Country Code: US 1:1206 PSCNET Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.150.148 Network Name: WICAT Location: Wicat Systems, 1875 South State Street, MS 9, Orem, UT 84058, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) 2:209 Westnet Regional Network (Colorado Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.165.147 Network Name: SE-RGRHU Location: Counsil for University Education, Box 45501, S-104 30 Stockholm, SWEDEN Country Code: SE 1:1800 ICM (FIX-East) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.188.199 Network Name: EPFL-NET1 Location: Enoch-Pratt Free Library, 400 Cathedral Street, Baltimore, MD 21201-4484, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.188.252 Network Name: URBAN-NET Location: The Urban Institute, 2100 M Street, NW, Washington, DC 20037, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.195.231 Network Name: CIESIN-START Location: CIESIN Consortium, Suite 805, 1825 K Street, NW, Washington, DC 20006, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.195.232 Network Name: CIESIN-DC Location: CIESIN Consortium, Suite 805, 1825 K Street, NW, Washington, DC 20006, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.133 Network Name: WN-AZ Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) 2:209 Westnet Regional Network (Colorado Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.134 Network Name: WN-ID Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) 2:209 Westnet Regional Network (Colorado Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.135 Network Name: WN-TEST1 Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.136 Network Name: WN-TEST2 Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.137 Network Name: WN-SHOW Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6491 T3 Network: ---------- AS 278 (Mexican Networks at NCAR) was added to the T3 database, with three primary networks (not listed here). Network IP: 137.54 Network Name: VERNET Location: University of Virginia, Gilmer Hall, Charlottesville, VA 22903, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 141.62 Network Name: FHD-STGT Location: Fachhochschule fuer Druck, Nobelstr. 10 7000 Stuttgart 80, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 141.68 Network Name: BRAVE Location: Berufsakademie Ravensburg, Ravensburg, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 141.79 Network Name: FH-OFFENBURG Location: Fachhochschule Offenburg, Offenburg, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 141.192 Network Name: ICLDATA Location: ICL Data Oy, Kutomontie 18 C, SF-00380 Helsinki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 155.31 Network Name: ERAU-FLORIDA Location: Academic Computing, Embry-Riddle Aeronautical University, 600 S. Clyde Morris Blvd., Daytona Beach, FL 32114-3900, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 155.44 Network Name: HMCO-NET Location: Houghton Mifflin Company, One Beacon Street, Boston, MA 02108, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 160.129 Network Name: VUMC Location: Vanderbilt University Medical Center, B-131 VUH, Vanderbilt University Hospital, Nashville, TN 37232-7330, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 160.143 Network Name: HURRICANE Location: Gateway Operations Center, Fort Richie, LA, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 160.144 Network Name: SENECA-NET2 Location: Management Information Systems, Commander, Seneca Army Depot, Building 115, Romulus, NY 14541-5001, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 161.13 Network Name: TXSWU Location: Southwestern University, Office of Information Systems, A. Frank Smith Library Center, Georgetown, TX 78626, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 163.152 Network Name: KUCCNET Location: Korea University, Anam-Dong, Sungbuk-Ku, Seoul 136-701, KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.86.93 Network Name: FALLSCH-GW6 Location: MTMC, 5611 Columbia Pike, Attn: ASQNG-OP-TS, Falls Church, VA 22041-5050, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.87.128 Network Name: HSBOS1 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.129 Network Name: HSBOS2 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.130 Network Name: HSBOS3 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.87.131 Network Name: HSBOS4 Location: Hogeschool 's Hertogenbosch, P.O. Box 90109, NL - 5200 MA 's Hertogenbosh, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.98.8 Network Name: OTOLNET Location: Oulu Institute of Technology, Kotkantie 1, SF-90250 Oulu, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.42 Network Name: OSITECHNET Location: Ositech Oy, Tekniikantie 12, SF-02150 Espoo, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.43 Network Name: MDATANET Location: Microdata Oy, Kuusisaarentie 3, SF-00340 Helsinki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.80 Network Name: TYT-SJK0 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.81 Network Name: TYT-SJK1 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.82 Network Name: TYT-SJK2 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.83 Network Name: TYT-SJK3 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.84 Network Name: TYT-SJK4 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.85 Network Name: TYT-SJK5 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.86 Network Name: MAKES-SJK1 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.98.87 Network Name: MAKES-SJK2 Location: University of Tampere, TYT Seinaejoki, Box 147, SF-60101 Seinaejoki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) Network IP: 192.134.146 Network Name: FR-IUSTI-EDU Location: IUSTI - Centre Universitaire de St Jerome, Avenue escadrille normandie niemem, F-13397 Marseille, FRANCE Country Code: FR 1:1800 ICM (FIX-East) Network IP: 192.134.147 Network Name: FR-IUSTI-REC Location: IUSTI - Centre Universitaire de St Jerome, Avenue escadrille normandie niemem, F-13397 Marseille, FRANCE Country Code: FR 1:1800 ICM (FIX-East) Network IP: 192.135.188 Network Name: ERRC Location: Eastern Regional Research Center, USDA-ARS-ERRC, 600 East Mermaid Lane, Philadelphia, PA 19118, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 192.150.148 Network Name: WICAT Location: Wicat Systems, 1875 South State Street, MS 9, Orem, UT 84058, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 192.165.147 Network Name: SE-RGRHU Location: Counsil for University Education, Box 45501, S-104 30 Stockholm, SWEDEN Country Code: SE 1:1800 ICM (FIX-East) Network IP: 192.188.199 Network Name: EPFL-NET1 Location: Enoch-Pratt Free Library, 400 Cathedral Street, Baltimore, MD 21201-4484, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.188.252 Network Name: URBAN-NET Location: The Urban Institute, 2100 M Street, NW, Washington, DC 20037, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.195.231 Network Name: CIESIN-START Location: CIESIN Consortium, Suite 805, 1825 K Street, NW, Washington, DC 20006, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.195.232 Network Name: CIESIN-DC Location: CIESIN Consortium, Suite 805, 1825 K Street, NW, Washington, DC 20006, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.207.133 Network Name: WN-AZ Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 192.207.134 Network Name: WN-ID Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 192.207.135 Network Name: WN-TEST1 Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.207.136 Network Name: WN-TEST2 Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.207.137 Network Name: WN-SHOW Location: Westnet, University of Colorado, 3645 Marine Street, Boulder, CO 80303-0455, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Total configured T3 networks: 5782 The following T3 Routers have also been added: AS Number: 278 AS Notes: Mexican Networks at NCAR AS Country Code: MX ANS: No BkBn: 690 NSS: 140.222.141 - ENSS141 Boulder, CO Gate: 192.43.244.8 - ram-gw.ucar.edu ENSS141, Boulder, CO ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From jrugo@nic.near.net Fri Sep 11 08:11:07 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA17987; Fri, 11 Sep 92 08:11:07 -0400 Message-Id: <9209111211.AA17987@merit.edu> To: mak Cc: regional-techs Subject: Re: August Backbone Engineering Report In-Reply-To: Your message of Thu, 10 Sep 92 23:07:16 -0400. <9209110307.AA28221@home.merit.edu> Date: Fri, 11 Sep 92 08:11:05 -0400 From: jrugo@nic.near.net Jordan, I notice that there was no mention in your report of the serious outage NEARnet experienced early in the month. Do such outages get reported via some other mechanism? - John - - - - - - - - - - - - - - - - - From becker@ans.net Sun Sep 13 19:01:13 1992 Received: from [147.225.1.3] by merit.edu (5.65/1123-1.0) id AA03025; Sun, 13 Sep 92 19:01:13 -0400 Received: by interlock.ans.net id AA111774 (InterLock SMTP Gateway 1.1); Sun, 13 Sep 1992 19:00:52 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Sun, 13 Sep 1992 19:00:52 -0400 Date: Sun, 13 Sep 92 18:59:45 EDT From: Jordan Becker To: jrugo@nic.near.net Cc: regional-techs, Mark Knopper Subject: August Backbone Engineering Report Message-Id: > Jordan, > > I notice that there was no mention in your report of the serious > outage NEARnet experienced early in the month. Do such outages get > reported via some other mechanism? > > - John John, We generally do not report specific outages in the monthly engineering report, unless they are causes or effects of changes in network software/hardware. With respect to the outage you describe, there were two routing problems which surfaced at the beginning of the month that caused some outages. We inadvertantly neglected to include these. Thanks for pointing this out. To clarify: a bug in the EGP protocol code of our T3 rcp_routed software induced a serious outage at both NEARnet and SESQUInet on 8/11, and resulted in at least one change to the T3-rcp_routed software. This occured at about the same time that we exceeded the 8KB EGP update size in outbound network announcements, which caused problems with a few regional routers, and complicated the diagnosis of the T3 routing software bug. As an aside, we have been maintaining a current set of release notes on the T3 network routing software that describes the bug fixes and changes in each release. This is available via anonymous on ftp.ans.net in the file /pub/info/T3-rcp_routed/Release-Notes. We hope that people find this information useful and welcome feedback from the community. Finally, our practice for outage reporting has been to post real time T3/T1 outage reports involving regional network and service provider attachments to the NSR mailing list and provide additional information on the regional-techs and nwg mailing lists. Jordan - - - - - - - - - - - - - - - - - From mak Sun Sep 13 22:22:05 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA08997; Sun, 13 Sep 92 22:22:05 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA13996; Sun, 13 Sep 92 22:22:04 EDT From: mak Message-Id: <9209140222.AA13996@home.merit.edu> To: regional-techs, fepg@fnc.gov Subject: It's a girl!!!! Date: Sun, 13 Sep 92 22:22:03 -0400 Hi. Jessica Yu's baby was born last week on September 8! Mark > From: smj@merit.edu > To: ndsb@merit.edu, netadmin@um.cc.umich.edu, pod-g@merit.edu > > > Jessica has just delivered a 6 lb 10oz baby girl. Both her > and the baby are doing fine. I just talked with her husband. > She is at UM Womens Hospital. > > -sue - - - - - - - - - - - - - - - - - From jrugo@nic.near.net Mon Sep 14 08:13:19 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA23999; Mon, 14 Sep 92 08:13:19 -0400 Message-Id: <9209141213.AA23999@merit.edu> To: Jordan Becker Cc: regional-techs, Mark Knopper Subject: Re: August Backbone Engineering Report In-Reply-To: Your message of Sun, 13 Sep 92 18:59:45 -0400. Date: Mon, 14 Sep 92 08:13:12 -0400 From: jrugo@nic.near.net Jordan, Thanks for your note. I'd like to discuss how NEARnet and ANS could improve our communication the next time we meet. I think regular reports, at the level of engineering and operations, are a good means of exchanging information between organizations and between the technical and managerial staff of those organizations. - John - - - - - - - - - - - - - - - - - From donnab@CERF.NET Mon Sep 14 17:19:24 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA18239; Mon, 14 Sep 92 17:19:24 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA20293; Mon, 14 Sep 92 14:19:52 PDT Date: Mon, 14 Sep 92 14:19:52 PDT From: Donna Bigley Message-Id: <9209142119.AA20293@nic.cerf.net> To: help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, September 7, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, September 7th through Sunday, September 13th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 13-sept-92.txt All times are in Pacific Daylight Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 1294 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: TUE. 09-08-92 15:07 TIME ENDED: TUE. 09-08-92 15:28 TIME ELAPSED: 21 min. REASON: Site Scheduled Maintenance TICKET #: 1299 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: THU. 09-10-92 15:44 TIME ENDED: THU. 09-10-92 15:59 TIME STARTED: THU. 09-10-92 18:11 TIME ENDED: THU. 09-10-92 18:18 TIME ELAPSED: 22 min. REASON: Unknown TICKET #: 1296 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: FRI. 09-11-92 18:15 TIME ENDED: FRI. 09-11-92 18:41 TIME ELAPSED: 26 min. REASON: Site Scheduled Maintenance (Korean Holiday) TICKET #: 1301 SITE: CICESE SITES AFFECTED: CICESE TIME STARTED: FRI. 09-11-92 11:28 TIME ENDED: MON. 09-14-92 TIME ELAPSED: Still Down REASON: Unscheduled Outage TICKET #: 1303 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: SAT. 09-12-92 19:54 TIME ENDED: SUN. 09-13-92 10:39 TIME ELAPSED: 14 hours 45 min. (Intermittent Access) REASON: Link Failure (Bad Carrier System) TICKET #: 1302 SITE: PEREGRINE SITES AFFECTED: PEREGRINE TIME STARTED: SUN. 09-13-92 12:24 TIME ENDED: MON. 09-14-92 TIME ELAPSED: Still Down REASON: Power Outage TICKET #: 1307 SITE: CSUCO/SWRL SITES AFFECTED: CSUCO/SWRL TIME STARTED: SUN. 09-13-92 20:04 TIME ENDED: SUN. 09-13-92 21:22 TIME ELAPSED: 1 hour 18 min. REASON: Ticket Still Open TICKET #: 1306 SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: SUN. 09-13-92 23:58 TIME ENDED: MON. 09-14-92 00:02 TIME ELAPSED: 4 min. REASON: Site Scheduled Maintenance ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps 00.2% 20:00 SDSC/GA 10.000 mbps 00.1% 02:00 SDSC/CALTECH 1.544 mbps 11.4% 16:00 SDSC/UCI 1.544 mbps 10.0% 11:00 SDSC/UCLA 1.544 mbps 08.4% 16:00 SDSC/UCOP 1.544 mbps 05.4% 11:00 UCI/UCLA 1.544 mbps 01.0% 11:00 SDSC/UCR 512 kbps 05.3% 11:00 UCLA/UCSB 512 kbps 10.3% 16:00 CALTECH/HUGHES 1.544 mbps 00.1% 09:00 SDSC/AGI 1.544 mbps 00.1% 13:00 SDSC/BIOSYM 1.544 mbps 01.3% 08:00 SDSC/GD 1.544 mbps 01.6% 08:00 SDSC/SAIC 1.544 mbps 00.9% 16:00 SDSC/SEASPACE 1.544 mbps 00.3% 09:00 UCI/CSU CO(SWRL) 1.544 mbps 03.1% 20:00 UCI/MDC 1.544 mbps 05.2% 11:00 UCLA/GETTY 1.544 mbps 00.1% 10:00 UCOP/APPLE 1.544 mbps 01.3% 14:00 UCOP/CISCO 1.544 mbps 00.2% 11:00 UCR/LLUMC 1.544 mbps 00.4% 18:00 CALTECH/AJS 56 kbps 01.7% 16:00 CALTECH/CADAM 56 kbps 00.4% 20:00 CALTECH/CITY OF HOPE 56 kbps 07.1% 18:00 CALTECH/CLAREMONT 56 kbps 27.1% 20:00 CALTECH/DISNEY 56 kbps 07.0% 11:00 CALTECH/OXY 56 kbps 04.9% 08:00 CALTECH/SCAQMD 56 kbps 00.4% 20:00 SDSC/API 56 kbps 11.5% 20:00 SDSC/CICESE 56 kbps 03.9% 15:00 SDSC/KOREA 56 kbps 10.7% 21:00 SDSC/QUALCOMM 56 kbps 10.4% 18:00 SDSC/REDE-RIO 56 kbps 10.7% 13:00 SDSC/SCIH 56 kbps 08.1% 11:00 SDSC/SDG&E 56 kbps 01.0% 14:00 SDSC/USD 56 kbps 07.4% 12:00 SDSC/USIU 56 kbps 04.0% 20:00 UCI/BECKMAN 56 kbps 05.2% 21:00 UCI/CCCD 56 kbps 07.8% 03:00 UCI/CMD 56 kbps 01.5% 20:00 UCI/EMULEX 56 kbps 01.6% 16:00 UCI/FULLERTON 56 kbps 01.9% 16:00 UCI/HUGHES 56 kbps 13.8% 10:00 UCI/ICC 56 kbps 09.3% 20:00 UCI/MTI 56 kbps 04.1% 11:00 UCI/SPARTA 56 kbps 05.3% 14:00 UCI/UNOCAL 56 kbps 20.5% 20:00 UCLA/CRSS 56 kbps 00.4% 09:00 UCLA/DATAPRODUCTS 56 kbps 03.7% 16:00 UCLA/GTE 56 kbps 06.4% 16:00 UCLA/ISX 56 kbps 02.1% 16:00 UCLA/LITTON 56 kbps 00.2% 16:00 UCLA/PEPPERDINE 56 kbps 01.1% 16:00 UCLA/QUOTRON 56 kbps 06.4% 21:00 UCLA/SMC 56 kbps 05.1% 16:00 UCOP/FARALLON 56 kbps 05.0% 15:00 UCOP/INTEL 56 kbps 21.8% 16:00 UCOP/LSIL 56 kbps 10.3% 20:00 UCOP/NETLABS 56 kbps 15.9% 20:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PDT on Sept. 14, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 64 days 11 hours 37 minutes SDSC LongBoard [134.24.99.254] Up: 90 days 08 hours 21 minutes SDSC Drzog [132.249.16.13] Up: 123 days 14 hours 24 minutes SDSC Hang10 [132.249.16.15] Up: 123 days 14 hours 24 minutes UCI [128.200.1.101] Up: 50 days 15 hours 24 minutes UCLA [128.97.130.10] Up: 161 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 173 days 16 hours 38 minutes UCR [134.24.108.105] Up: 64 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 64 days 09 hours 43 minutes APPLE [134.24.70.200] Up: 322 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 94 days 07 hours 13 minutes CISCO Systems [134.24.54.200] Up: 03 days 11 hours 26 minutes [Site Activity] CSUCO/SWRL [130.150.102.200] Up: 44 days 18 hours 22 minutes GA [134.24.20.10] Up: 04 days 12 hours 00 minutes [Equipment Trouble] GD [134.24.60.200] Up: 136 days 16 hours 18 minutes GETTY [134.24.235.200] Up: 31 days 07 hours 02 minutes HUGHES_CIT [134.24.103.200] Up: 45 days 13 hours 53 minutes LLUMC [134.24.208.200] Up: 43 days 13 hours 45 minutes MDC [134.24.65.200] Up: 23 days 08 hours 00 minutes SAIC [134.24.53.208] Up: 123 days 14 hours 10 minutes UCSB [134.24.107.107] Up: 81 days 15 hours 45 minutes CERF 56 AJS [134.24.225.101] Up: 33 days 13 hours 24 minutes API [134.24.224.200] Up: 80 days 13 hours 18 minutes BECKMAN [134.24.237.200] Up: 103 days 12 hours 10 minutes CADAM [134.24.229.200] Up: 16 days 06 hours 23 minutes CCCD [134.24.219.200] Up: 77 days 19 hours 14 minutes CICESE [134.24.227.200] Up: Still Down [Unscheduled Outage - See Ticket #1301] CITY_OF_HOPE [134.24.233.200] Up: 02 days 06 hours 33 minutes [Equipment Trouble] CLAREMONT [134.24.206.109] Up: 40 days 21 hours 38 minutes CMD [134.24.218.200] Up: 09 days 07 hours 29 minutes CRSS [134.24.232.200] Up: 39 days 12 hours 16 minutes DATAPRODUCTS [134.24.211.200] Up: 166 days 13 hours 01 minutes DISNEY [134.24.207.211] Up: 27 days 19 hours 57 minutes EMULEX [134.24.209.212] Up: 15 days 07 hours 37 minutes FARALLON [134.24.56.200] Up: 41 days 15 hours 51 minutes FULLERTON [134.24.214.217] Up: 77 days 17 hours 55 minutes GTE [134.24.212.200] Up: 182 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 36 days 16 hours 21 minutes INTEL [134.24.73.200] Up: 169 days 11 hours 34 minutes ICC [134.24.238.200] Up: 67 days 08 hours 39 minutes LITTON [134.24.213.200] Up: 23 days 13 hours 29 minutes LSIL [134.24.72.200] Up: 131 days 08 hours 26 minutes MTI [134.24.216.100] Up: 19 days 08 hours 48 minutes NETLABS [134.24.71.200] Up: 46 days 09 hours 33 minutes OXY [134.24.205.108] Up: 13 days 17 hours 15 minutes PEPPERDINE [134.24.203.218] Up: 156 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 00 days 00 hours 14 minutes [Site Scheduled Maintenance - See Ticket #1306] QUOTRON [134.24.230.202] Up: 21 days 06 hours 06 minutes REDE_RIO [134.24.112.200] Up: 05 days 08 hours 44 minutes [Site Scheduled Maintenance - See Ticket #1294] SANTA MONICA [134.24.210.219] Up: 46 days 13 hours 40 minutes SCAQMD [134.24.234.200] Up: 06 days 12 hours 34 minutes [Equipment Trouble] SCI-HOR [134.24.109.205] Up: 124 days 06 hours 02 minutes SDG&E [134.24.226.200] Up: 103 days 13 hours 39 minutes SEASPACE [134.24.80.200] Up: 158 days 11 hours 26 minutes SERI/KOREA [134.24.223.200] Up: 02 days 05 hours 58 minutes [Site Scheduled Maintenance - See Ticket #1296] SPARTA [134.24.215.200] Up: 167 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 192 days 01 hours 57 minutes USD [134.24.201.106] Up: 34 days 17 hours 00 minutes USIU [134.24.222.215] Up: 435 days 17 hours 07 minutes DIAL n' CERF Plus 14.4 CITOH [161.1.1.1] Up: 17 days 11 hours 41 minutes MARKV [192.122.251.6] Up: 17 days 01 hours 14 minutes PEREGRINE [192.72.253.97] Up: Still Down [Power Outage - See Ticket #1302] DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 45 days 11 hours 19 minutes DNC-UCI [134.24.2.2] Up: 50 days 15 hours 25 minutes DNC-UCLA [134.24.3.2] Up: 09 days 15 hours 05 minutes DNC-CALTECH [134.24.4.2] Up: 17 days 01 hours 14 minutes DNC-UCOP [134.24.5.2] Up: 76 days 04 hours 29 minutes CIT-NETBLAZER [130.152.104.1] Up: 66 days 13 hours 47 minutes SDSC-NETBLAZER [192.102.249.25] Up: 09 days 15 hours 05 minutes UCI-NETBLAZER [134.24.92.2] Up: 18 days 06 hours 44 minutes UCLA-NETBLAZER [134.24.93.2] Up: 25 days 06 hours 54 minutes UCOP-NETBLAZER [134.24.250.2] Up: 173 days 23 hours 54 minutes - - - - - - - - - - - - - - - - - From rty Tue Sep 15 06:59:12 1992 Received: by merit.edu (5.65/1123-1.0) id AA14415; Tue, 15 Sep 92 06:59:18 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA14409; Tue, 15 Sep 92 06:59:12 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA24796; Tue, 15 Sep 92 06:59:11 EDT Date: Tue, 15 Sep 92 06:59:11 EDT Message-Id: <9209151059.AA24796@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database, and routes should be in effect by 08:00 EDT. T1 Network: ---------- Network IP: 128.12 Network Name: SU-NET Location: Stanford University, Pine Hall 115, Stanford, CA 94305, USA Country Code: US 1:32 BARRNet 2:200 BARRNet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 136.162 Network Name: CRSI Location: Cray Research Superservers, Inc., 655-E Lone Oak Drive, Eagan, MN 55121, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 137.14 Network Name: AF-CONC-NET17 Location: 12th Communications Squadron/SCOUB, Building 379, Room 9, RANDOLPH Air Force Base, TX 78148, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 138.196 Network Name: DUPONT-ESNET Location: Du Pont Research & Development, Scientific Computing Division, Wilmington, DE 19880-0320, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 140.247 Network Name: HARVARD-COLL Location: Harvard University, 10 Ware Street, Cambridge, MA 02138, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 142.150 Network Name: ERINDALE-NET Location: University of Toronto Erindale Campus Network, University of Toronto, 4 Bancroft Ave., Rm. 102, Toronto, Ontario, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 145.20 Network Name: OUH-NL Location: Open Universiteit, PO Box 2960, NL-6401 DL Heerlen, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network Network IP: 147.233 Network Name: OPENU2-NET Location: Open University, Tel-Aviv, ISRAEL Country Code: IL 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.52.161 Network Name: TADNET Location: Tadpole Technology PLC, 330 Science Park, Milton Road, Cambridge CB4 4WQ, UNITED KINGDOM Country Code: GB 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.65.144 Network Name: SLXSYSLAN Location: Specialix International PLC, 3 Wintersells Road, Byfleet, Surrey KT14 7LF, UNITED KINGDOM Country Code: GB 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.75.72 Network Name: CRC-DOC Location: GTA, Department of Communications, 360 Laurier St, 7th Fl, Ottawa, Ontario, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 192.106.222 Network Name: SEM-TO Location: Systems & Management S.p.A., Via Alfieri, 19, I-10100 TORINO, ITALY Country Code: IT 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.139.232 Network Name: MOHAWKC Location: Mohawk College of Applied Arts and Technology, RM C107B, 135 Fennel Ave. W., Hamilton, Ontario, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 192.153.153 Network Name: COLLOQUIUM Location: Fleet Digital Solutions Ltd., 6/7 Steeple Square, Kilbarchan, Strathclyde, Scotland PA10 2JD, UNITED KINGDOM Country Code: GB 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.154.38 Network Name: UNC-IMS-NET Location: UNC Institute of Marine Science, 3407 Arendell Street, Morehead City, NC 28557, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 192.154.39 Network Name: DUML-NET Location: Duke University Marine Laboratory, Piver's Island, Beaufort, NC 28516, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 192.154.40 Network Name: NOAA-CIFO-NET Location: National Oceanic and Atmospheric Administration, Piver's Island, Beaufort, NC 28516, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 192.154.41 Network Name: BARTON-NET Location: Barton College, Lee Street, Wilson, NC 27893, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 192.154.42 Network Name: ECS3-LAN Location: UNC Educational Computing Service, PO Box 12035, Research Triangle Park, NC 27709, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:81 CONCERT Network IP: 192.160.185 Network Name: ASPENTECNET2 Location: Aspentech UK Ltd., Sheraton House, Castle Park, Cambridge CB3 0AX, UNITED KINGDOM Country Code: GB 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.195.196 Network Name: UMASSP Location: University of Massachusetts, Data Processing Center, Whitmore Building, Room 150, Amherst, MA 01003, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.207.104 Network Name: WSIPC-DMZ Location: Washington School Information Processing Cooperative, 2000 200th Place, SE, Lynnwood, WA 98036, USA Country Code: US 1:754 T1-T3 Network Interconnect (Houston, TX) 2:751 T1-T3 Network Interconnect (San Diego, CA) 3:750 T1-T3 Network Interconnect (Ann Arbor, MI) 4:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 193.128.2 Network Name: ALEX Location: Alex Technologies Ltd., Watermans Yard, 32A The Mall, Ealing, London CA 94025, UNITED KINGDOM Country Code: GB 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Total configured T1 networks: 6514 The following peers have also been configured on the T1: AS Number: 32 AS Notes: BARRNet AS Country Code: US ANS: No BkBn: 145 NSS: 129.140.13 - Palo Alto, California Gate: 192.31.49.202 - SU-CAMPUS.BARRNET.NET BARRNet, Palo Alto, California AS Number: 297 AS Notes: Nasa Science Network (FIX-East) AS Country Code: US ANS: No BkBn: 145 NSS: 129.140.9 - FIX-East, College Park, MD Gate: 192.80.214.243 - sura2.nsn.nasa.gov Nasa Science Network (FIX-East) T3 Network: ---------- Network IP: 128.12 Network Name: SU-NET Location: Stanford University, Pine Hall 115, Stanford, CA 94305, USA Country Code: US 1:32 BARRNet 2:200 BARRNet 3:201 BARRNet Network IP: 136.162 Network Name: CRSI Location: Cray Research Superservers, Inc., 655-E Lone Oak Drive, Eagan, MN 55121, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 137.14.15 Network Name: RANDOLPH3 Location: 12th Communications Squadron/SCOUB, Building 379, Room 9, RANDOLPH Air Force Base, TX 78148, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 138.196 Network Name: DUPONT-ESNET Location: Du Pont Research & Development, Scientific Computing Division, Wilmington, DE 19880-0320, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 140.247 Network Name: HARVARD-COLL Location: Harvard University, 10 Ware Street, Cambridge, MA 02138, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 147.233 Network Name: OPENU2-NET Location: Open University, Tel-Aviv, ISRAEL Country Code: IL 1:174 NYSERNet Regional Network / PSI Network IP: 192.52.161 Network Name: TADNET Location: Tadpole Technology PLC, 330 Science Park, Milton Road, Cambridge CB4 4WQ, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:702 Alternet Network IP: 192.65.144 Network Name: SLXSYSLAN Location: Specialix International PLC, 3 Wintersells Road, Byfleet, Surrey KT14 7LF, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:702 Alternet Network IP: 192.106.222 Network Name: SEM-TO Location: Systems & Management S.p.A., Via Alfieri, 19, I-10100 TORINO, ITALY Country Code: IT 1:701 Alternet Network IP: 192.153.153 Network Name: COLLOQUIUM Location: Fleet Digital Solutions Ltd., 6/7 Steeple Square, Kilbarchan, Strathclyde, Scotland PA10 2JD, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:702 Alternet Network IP: 192.154.38 Network Name: UNC-IMS-NET Location: UNC Institute of Marine Science, 3407 Arendell Street, Morehead City, NC 28557, USA Country Code: US 1:81 CONCERT Network IP: 192.154.39 Network Name: DUML-NET Location: Duke University Marine Laboratory, Piver's Island, Beaufort, NC 28516, USA Country Code: US 1:81 CONCERT Network IP: 192.154.40 Network Name: NOAA-CIFO-NET Location: National Oceanic and Atmospheric Administration, Piver's Island, Beaufort, NC 28516, USA Country Code: US 1:81 CONCERT Network IP: 192.154.41 Network Name: BARTON-NET Location: Barton College, Lee Street, Wilson, NC 27893, USA Country Code: US 1:81 CONCERT Network IP: 192.154.42 Network Name: ECS3-LAN Location: UNC Educational Computing Service, PO Box 12035, Research Triangle Park, NC 27709, USA Country Code: US 1:81 CONCERT Network IP: 192.160.185 Network Name: ASPENTECNET2 Location: Aspentech UK Ltd., Sheraton House, Castle Park, Cambridge CB3 0AX, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:702 Alternet Network IP: 192.195.196 Network Name: UMASSP Location: University of Massachusetts, Data Processing Center, Whitmore Building, Room 150, Amherst, MA 01003, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.207.104 Network Name: WSIPC-DMZ Location: Washington School Information Processing Cooperative, 2000 200th Place, SE, Lynnwood, WA 98036, USA Country Code: US 1:1331 ANS Seattle - DNSS 91 Network IP: 193.128.2 Network Name: ALEX Location: Alex Technologies Ltd., Watermans Yard, 32A The Mall, Ealing, London CA 94025, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:702 Alternet Total configured T3 networks: 5800 The following peers have also been configured on the T3: AS Number: 32 AS Notes: BARRNet AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.128 - pa-enss Palo Alto, California Gate: 192.31.48.202 - SU-CAMPUS.BARRNET.NET BARRNet, Palo Alto, California AS Number: 297 AS Notes: Nasa Science Network (FIX-East) AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.145 - FIX-East College Park, MD Gate: 192.80.214.243 - sura2.nsn.nasa.gov Nasa Science Network (FIX-East) ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From vaf@Valinor.Stanford.EDU Wed Sep 16 18:58:12 1992 Received: from Valinor.Stanford.EDU by merit.edu (5.65/1123-1.0) id AA01259; Wed, 16 Sep 92 18:58:12 -0400 Received: by Valinor.Stanford.EDU (5.65/inc-1.0) id AA20131; Wed, 16 Sep 92 15:58:10 -0700 Date: Wed, 16 Sep 92 15:58:09 PDT From: Vince Fuller To: regional-techs Office: Spruce Hall F15, (415) 723-6860 Usmail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Anyone renting a car at DTW for the MERIT seminar? Message-Id: Is there anyone attending the MERIT seminar who is renting a car from Detroit Metro airport with an arrival time of around 9:00PM on Sunday the 21st? I'm scheduled in on Northwest flight 344 arriving at 9:09PM and would be happy to pay gas/mileage in exchange for a ride from the airport (my arrival time should guarentee that I just miss the 9:00 bus...) Thanks, --Vince - - - - - - - - - - - - - - - - - From skw Fri Sep 18 08:20:05 1992 Received: by merit.edu (5.65/1123-1.0) id AA19662; Fri, 18 Sep 92 08:20:19 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA19588; Fri, 18 Sep 92 08:20:05 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA24391; Fri, 18 Sep 92 08:20:04 EDT Date: Fri, 18 Sep 92 08:20:04 EDT Message-Id: <9209181220.AA24391@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following additions have been made to the NSFNET policy-based routing database: T1 Network: ---------- 174 networks were moved from primary TWBnet: 7:274 8:60, to primary NASA: 7:297 8:372 9:274 10:60. Network IP: 137.14 Network Name: AF-CONC-NET17 Location: 12th Communications Squadron/SCOUB, Building 379, Room 9, RANDOLPH Air Force Base, TX 78148, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 148.4 Network Name: LIUNET1 Location: Long Island University/C.W. Post Campus, Academic Computing Center, Greenvale, NY 11548, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 155.35 Network Name: LEGENT-NET Location: Legent Corporation, 114 Turnpike Road, Westboro, MA 01581, USA Country Code: US 1:1206 PSCNET Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 158.115 Network Name: NET-MPCN Location: Minnesota Research and Education Network, Inc., 322 S. Warwick St., St. Paul, MN 55105, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 159.183 Network Name: PA-SSHE Location: State System of Higher Education, Office of the Chancellor, 301 Market St., 6th Floor, P.O. Box 809, Harrisburg, PA 17108, USA Country Code: US 1:1206 PSCNET Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.5.74 Network Name: MSC-CNETS-74 Location: Minnesota Supercomputer Center, Inc., 1200 Washington Avenue South, Minneapolis, MN 55415, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.77.160 Network Name: ANS-CNET10 Location: Unix Expo, Jacob K. Javits Convention Center, 11th Ave and 34th Street, New York, NY, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.182 Network Name: WSUNET3 Location: Washington State University, Intercollegiate Center for Nursing Education, West 2917 Fort George Wright Drive, Spokane, WA 99204-5277, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.128 Network Name: LARSE2-NET Location: Larse Corporation, 4600 Patrick Henry Drive, Santa Clara, CA 95052-8138, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.129 Network Name: LARSE3-NET Location: Larse Corporation, 4600 Patrick Henry Drive, Santa Clara, CA 95052-8138, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.207.18 Network Name: DELMAR-NET Location: Del Mar College, Computing Services, 101 Baldwin, Corpus Christi, TX 78404-3897, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.215.1 Network Name: NETBLK-CERFNET-1 Location: CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.215.2 Network Name: NETBLK-CERFNET-2 Location: CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA Country Code: US 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6526 T3 Network: ---------- Network IP: 137.14 Network Name: AF-CONC-NET17 Location: 12th Communications Squadron/SCOUB, Building 379, Room 9, RANDOLPH Air Force Base, TX 78148, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 145.20 Network Name: OUH-NL Location: Open Universiteit, PO Box 2960, NL-6401 DL Heerlen, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 148.4 Network Name: LIUNET1 Location: Long Island University/C.W. Post Campus, Academic Computing Center, Greenvale, NY 11548, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 155.35 Network Name: LEGENT-NET Location: Legent Corporation, 114 Turnpike Road, Westboro, MA 01581, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 158.115 Network Name: NET-MPCN Location: Minnesota Research and Education Network, Inc., 322 S. Warwick St., St. Paul, MN 55105, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 159.183 Network Name: PA-SSHE Location: State System of Higher Education, Office of the Chancellor, 301 Market St., 6th Floor, P.O. Box 809, Harrisburg, PA 17108, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 192.5.74 Network Name: MSC-CNETS-74 Location: Minnesota Supercomputer Center, Inc., 1200 Washington Avenue South, Minneapolis, MN 55415, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 192.77.160 Network Name: ANS-CNET10 Location: Unix Expo, Jacob K. Javits Convention Center, 11th Ave and 34th Street, New York, NY, USA Country Code: US 1:1324 ANS New York City - DNSS 35 Network IP: 192.138.182 Network Name: WSUNET3 Location: Washington State University, Intercollegiate Center for Nursing Education, West 2917 Fort George Wright Drive, Spokane, WA 99204-5277, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.203.128 Network Name: LARSE2-NET Location: Larse Corporation, 4600 Patrick Henry Drive, Santa Clara, CA 95052-8138, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.203.129 Network Name: LARSE3-NET Location: Larse Corporation, 4600 Patrick Henry Drive, Santa Clara, CA 95052-8138, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.207.18 Network Name: DELMAR-NET Location: Del Mar College, Computing Services, 101 Baldwin, Corpus Christi, TX 78404-3897, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.215.1 Network Name: NETBLK-CERFNET-1 Location: CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA Country Code: US 1:1740 CERFnet Network IP: 192.215.2 Network Name: NETBLK-CERFNET-2 Location: CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA Country Code: US 1:1740 CERFnet Total configured T3 networks: 5813 The following T3 routers have also been added: AS Number: 1997 AS Notes: IBM Dallas Engineering & Scientific AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.188 - IBM Dallas IBM, Dallas, TX Gate: 192.203.134.3 - peer.tcs.dfw.ibm.com IBM, Dallas, TX ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu - - - - - - - - - - - - - - - - - From skw Tue Sep 22 04:12:10 1992 Received: by merit.edu (5.65/1123-1.0) id AA07016; Tue, 22 Sep 92 04:12:16 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA07010; Tue, 22 Sep 92 04:12:10 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA05157; Tue, 22 Sep 92 04:12:09 EDT Date: Tue, 22 Sep 92 04:12:09 EDT Message-Id: <9209220812.AA05157@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following additions have been made to the NSFNET policy-based routing database, and will be installed on the T1 and T3 backbones by 08:00 EDT: T1 Network: ---------- Network IP: 137.239 Network Name: COMMODORE Location: Commodore Buisness Machines, 1200 Wilson Drive, West Chester, PA 19380, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 144.203 Network Name: BARRA Location: BARRA, 1995 University Avenue, Berkeley, CA 94704, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 146.122 Network Name: SDRC Location: Structural Dynamics Research Corporation, 2000 Eastman Drive, Milford, OH 45150, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 150.232 Network Name: NEURONET-B Location: Presbyterian-University Hospital, Room 9402, 230 Lothrop Street, Pittsburgh, PA 15213, USA Country Code: US 1:1206 PSCNET Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 150.253 Network Name: MCAD-NET Location: MCAD Computer Center, 2501 Stevens Avenue South, Minneapolis, MN 55404, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 152.65 Network Name: SJUNET1 Location: Saint John's University - College of Saint Benedict, Academic Computing - VAX Services, Science Center Room 018, Collegeville, MN 56321, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 152.148 Network Name: CASCADE Location: Cascade Communications Corporation, Unit 3A, 239 Littleton Road, Westford, MA 01886, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 157.150 Network Name: UN-NET Location: United Nations, 1st Ave. and 42nd St., NY, NY 10017, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 163.239 Network Name: SOGANG-NET Location: Sogang University, Seoul, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.86.157 Network Name: ORACLE-SLIP8 Location: Oracle Corporation, 400 Oracle Parkway, 4th Floor, Redwood Shores, CA 94065, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.92.123 Network Name: ACS Location: Applied Computing Systems, 2075 Trinity Drive, Suite Lower Level, Los Alamos, NM 87544, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.135.134 Network Name: ALERCE-NET Location: Berkeley Software Design, Inc., 685 Partridge Ave., Menlo Park, CA 94025 USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.153.141 Network Name: DECAEULAN Location: Defense Commissary Agency-Europe, CMR 404, Box 1168, APO, AE 09052, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.188.104 Network Name: ACET Location: The MITRE Corporation, 7525 Colshire Drive, McLean, VA, 22102 USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.203.138 Network Name: CHEJUNET Location: Cheju National University Computing Center, Cheju National University Computing Center, Cheju, 690-121, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.139 Network Name: CHONBUKNET Location: Chonbuk National University Computing Center, Chonbuk National Uiversity Computing Center, Chonju 560-190, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.140 Network Name: CHONNAMNET Location: Chonnam National University Computing Center, Gwangju 500-070, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.141 Network Name: CHUNGBUKNET Location: Cheju National University Computing Center, Chungbuk National University Computing Center, Cheongju, 690-121, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.142 Network Name: GSUCNET Location: Kyungsang National University Computing Center, Kyungsang National University Computing Center, Chinju, 660-300, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.143 Network Name: PUSANNET Location: Pusan National University Computing Center, Pusan, 609-390, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.144 Network Name: KANGWONNET Location: Kangwon National University Computing Center, Kangwon National University Computing Center, Chuncheon, 200-092, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.145 Network Name: KONKUKNET Location: Konkuk University Computing Center, Seoul, 1330140, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.146 Network Name: KOOKMINNET Location: Kookman University Computing Center, Seoul, 136-702, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.89 Network Name: C4 Location: C4 Network Inc., 518 17th St., Suite 1400, Denver, CO 80202, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.103 Network Name: SET Location: Systems Engineering Technologies, 1440 Antero Drive, Loveland, CO 80538, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.207.245 Network Name: MR-SLIPNET Location: Minnesota Regional Network, 511 11th Avenue South, Box 212, Minneapolis, MN 55415, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6552 The following T1 routers have also been added: AS Number: 189 AS Notes: BARRNet AS Country Code: US ANS: No BkBn: 145 NSS: 129.140.13 - Palo Alto, California Gate: 192.31.49.189 - SU-DEC.BARRNET.NET Palo Alto, CA T3 Network: ---------- Network IP: 133.28 Network Name: KAINS-NET Location: Kanazawa University, Kodatsuno 2-40-20, Kanazawa-shi, Ishikawa 920, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 133.34 Network Name: YNU Location: Yokohama National University, Information Processing Center, Tokiwadai 156, Hodogaya-ku, Yokohama 240, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 136.187 Network Name: NACSIS-NET Location: National Center for Science Information System, Network Operations Department, 3-29-1 Otsuka, Bunkyo-ku, Tokyo 112, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 137.239 Network Name: COMMODORE Location: Commodore Buisness Machines, 1200 Wilson Drive, West Chester, PA 19380, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 144.203 Network Name: BARRA Location: BARRA, 1995 University Avenue, Berkeley, CA 94704, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 146.122 Network Name: SDRC Location: Structural Dynamics Research Corporation, 2000 Eastman Drive, Milford, OH 45150, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 147.157 Network Name: TCNET-JP Location: Tsukuba College of Technology, 4-12 Kasuga, Tsukuba-shi, Ibaraki-ken, 305, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 150.99 Network Name: SINET Location: National Center for Science Information System, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 150.100 Network Name: SINET1 Location: National Center for Science Information System, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 150.232 Network Name: NEURONET-B Location: Presbyterian-University Hospital, Room 9402, 230 Lothrop Street, Pittsburgh, PA 15213, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 150.253 Network Name: MCAD-NET Location: MCAD Computer Center, 2501 Stevens Avenue South, Minneapolis, MN 55404, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 152.65 Network Name: SJUNET1 Location: Saint John's University - College of Saint Benedict, Academic Computing - VAX Services, Science Center Room 018, Collegeville, MN 56321, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 152.148 Network Name: CASCADE Location: Cascade Communications Corporation, Unit 3A, 239 Littleton Road, Westford, MA 01886, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 157.1 Network Name: OP-NACSIS Location: NACSIS (National Center for Science Information Systems), Otsuka 3-29-1, Bunkyo-ku, Tokyo 112, JAPAN Country Code: JP 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 157.150 Network Name: UN-NET Location: United Nations, 1st Ave. and 42nd St., NY, NY 10017, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 163.239 Network Name: SOGANG-NET Location: Sogang University, Seoul, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.86.157 Network Name: ORACLE-SLIP8 Location: Oracle Corporation, 400 Oracle Parkway, 4th Floor, Redwood Shores, CA 94065, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.92.123 Network Name: ACS Location: Applied Computing Systems, 2075 Trinity Drive, Suite Lower Level, Los Alamos, NM 87544, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.135.134 Network Name: ALERCE-NET Location: Berkeley Software Design, Inc., 685 Partridge Ave., Menlo Park, CA 94025 USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.153.141 Network Name: DECAEULAN Location: Defense Commissary Agency-Europe, CMR 404, Box 1168, APO, AE 09052, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.157.64 Network Name: ICMNET-1 Location: Sprint, Government Systems Division, 13221 Woodland Park Road, Herndon, VA 22071, USA Country Code: US 1:1240 FIX-W.ICM.NET 2:1800 ICM (FIX-East) Network IP: 192.188.104 Network Name: ACET Location: The MITRE Corporation, 7525 Colshire Dr., McLean, VA 22102, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.203.138 Network Name: CHEJUNET Location: Cheju National University Computing Center, Cheju National University Computing Center, Cheju, 690-121, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.139 Network Name: CHONBUKNET Location: Chonbuk National University Computing Center, Chonbuk National University Computing Center, Chonju 560-190, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.140 Network Name: CHONNAMNET Location: Chonnam National University Computing Center, Gwangju 500-070, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.141 Network Name: CHUNGBUKNET Location: Cheju National University Computing Center, Chungbuk National University Computing Center, Cheongju, 690-121, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.142 Network Name: GSUCNET Location: Kyungsang National University Computing Center, Kyungsang National University Computing Center, Chinju, 660-300, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.143 Network Name: PUSANNET Location: Pusan National University Computing Center, Pusan, 609-390, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.144 Network Name: KANGWONNET Location: Kangwon National University Computing Center, Kangwon National University Computing Center, Chuncheon, 200-092, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.145 Network Name: KONKUKNET Location: Konkuk University Computing Center, Seoul, 1330140, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.203.146 Network Name: KOOKMINNET Location: Kookman University Computing Center, Seoul, 136-702, REPUBLIC OF KOREA Country Code: KR 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.207.89 Network Name: C4 Location: C4 Network Inc., 518 17th St., Suite 1400, Denver, CO 80202, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.207.103 Network Name: SET Location: Systems Engineering Technologies, 1440 Antero Drive, Loveland, CO 80538, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.207.245 Network Name: MR-SLIPNET Location: Minnesota Regional Network, 511 11th Avenue South, Box 212, Minneapolis, MN 55415, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Total configured T3 networks: 5847 The following T3 routers have also been added: AS Number: 189 AS Notes: BARRNet AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.128 - pa-enss Palo Alto, California Gate: 192.31.49.189 - SU-DEC.BARRNET.NET Palo Alto, CA AS Number: 1240 AS Notes: FIX-W.ICM.NET AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.144 - FIX-West NASA Ames, Palo Alto, CA Gate: 192.52.195.16 - FIX-W.ICM.NET FIX-West, Palo Alto, CA ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From cert-advisory-request@cert.org Tue Sep 22 15:46:21 1992 Received: from tictac.cert.org by merit.edu (5.65/1123-1.0) id AA01354; Tue, 22 Sep 92 15:46:21 -0400 Received: by tictac.cert.org (5.65/2.5) id AA16804; Tue, 22 Sep 92 15:36:23 -0400 Message-Id: <9209221936.AA16804@tictac.cert.org> From: CERT Advisory Date: Tue, 22 Sep 92 15:35:21 EDT To: cert-advisory@cert.org Subject: CERT Advisory - VMS Monitor Vulnerability Organization: Computer Emergency Response Team 412-268-7090 CA-92:16 CERT Advisory September 22, 1992 VMS Monitor Vulnerability --------------------------------------------------------------------------- The CERT Coordination Center has received information concerning a potential vulnerability with Digital Equipment Corporation's VMS Monitor. This vulnerability is present in V5.0 through V5.4-2 but has been corrected in V5.4-3 through V5.5-1. The Software Security Response Team at Digital has provided the following information concerning this vulnerability. NOTE: Digital suggests that customers who are unable to upgrade their systems implement the workaround described below. For additional information, please contact your local Digital Equipment Corporation customer service representative. Beginning of Text provided by Digital Equipment Corporation ============================================================================== SSRT-0200 PROBLEM: Potential Security Vulnerability Identified in Monitor SOURCE: Digital Equipment Corporation AUTHOR: Software Security Response Team - U.S. Colorado Springs USA PRODUCT: VMS Symptoms Identified On: VMS, Versions 5.0, 5.0-1, 5.0-2, 5.1, 5.1-B, 5.1-1, 5.1-2, 5.2, 5.2-1, 5.3, 5.3-1, 5.3-2, 5.4, 5.4-1, 5.4-2 ******************************************************* SOLUTION: This problem is not present in VMS V5.4-3 (released in October 1991) through V5.5-1 (released in July, 1992.) ******************************************************* Copyright (c) Digital Equipment Corporation, 1992 All Rights Reserved. Published Rights Reserved Under The Copyright Laws Of The United States. ------------------------------------------------------------------------------- PROBLEM/IMPACT: ------------------------------------------------------------------------------- Unauthorized privileges may be expanded to authorized users of a system under certain conditions, via the Monitor utility. Should a system be compromised through unauthorized access, there is a risk of potential damage to a system environment. This problem will not permit unauthorized access entry, as individuals attempting to gain unauthorized access will continue to be denied through the standard VMS security mechanisms. ------------------------------------------------------------------------------- SOLUTION: ------------------------------------------------------------------------------- This potential vulnerability does not exist in VMS V5.4-3 (released in October 1991) and later versions of VMS through V5.5-1. Digital strongly recommends that you upgrade to a minimum of VMS V5.4-3, and further, to the latest release of VMS V5.5-1. (released in July, 1992) ------------------------------------------------------------------------------ INFORMATION: ------------------------------------------------------------------------------- If you cannot upgrade at this time Digital recommends that you implement a workaround (examples attached below) to avoid any potential vulnerability. As always, Digital recommends that you periodically review your system management and security procedures. Digital will continue to review and enhance the security features of its products and work with customers to maintain and improve the security and integrity of their systems. ------------------------------------------------------------------------------- WORKAROUND ------------------------------------------------------------------------------- A suggested workaround would be to remove the installed image SYS$SHARE:SPISHR.EXE via VMS INSTALL and/or restrict the use of the MONITOR utility to "privileged" system administrators. Below are the examples of doing both; [1] To disable the MONITOR utility the image SYS$SHARE:SPISHR.EXE should be deinstalled. From a privileged account; For cluster configurations; --------------------------- $ MC SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO INSTALL REMOVE SYS$SHARE:SPISHR.EXE SYSMAN> DO RENAME SYS$SHARE:SPISHR.EXE SPISHR.HOLD SYSMAN> EXIT For non-VAXcluster configurations; --------------------------------- $INSTALL INSTALL>REMOVE SYS$SHARE:SPISHR.EXE INSTALL>EXIT $RENAME SYS$SHARE:SPISHR.EXE SPISHR.HOLD [2] If you wish to restrict access to the MONITOR command so that only a limited number of authorized (or privileged) persons are granted access to the utility, one method might be to issue the following example commands; From a privileged account; For cluster configurations; --------------------------- $ MC SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO INSTALL REMOVE SYS$SHARE:SPISHR.EXE SYSMAN> DO SET FILE/ACL=(ID=*,ACCESS=NONE) SYS$SHARE:SPISHR.EXE SYSMAN> DO SET FILE/ACL=(ID=SYSTEM,ACCESS=READ+EXECUTE) SYS$SHARE:SPISHR.EXE SYSMAN> DO INSTALL ADD SYS$SHARE:SPISHR.EXE/OPEN/HEADER/SHARE/PROTECT SYSMAN> EXIT $ THIS WILL IMPACT the MONITOR UTILITY FOR REMOTE MONITORING. LOCAL MONITORING WILL CONTINUE TO WORK FOR PERSONS HOLDING THE ID's GRANTED ACL ACCESS. see additional note(s) below For non-VAXcluster configurations; ---------------------------------- $ INSTALL INSTALL>REMOVE SYS$SHARE:SPISHR.EXE INSTALL>EXIT $ SET FILE /ACL=(ID=*,ACCESS=NONE) SYS$SHARE:SPISHR.EXE $ SET FILE /ACL=(ID=SYSTEM,ACCESS=READ+EXECUTE) SYS$SHARE:SPISHR.EXE $ INSTALL INSTALL>ADD SYS$SHARE:SPISHR.EXE/OPEN/HEADER/SHARE/PROTECT INSTALL>EXIT $ IN THE ABOVE EXAMPLES, THE "SET FILE /ACL" LINE SHOULD BE REPEATED FOR ALL ACCOUNTS THAT ARE REQUIRED/ALLOWED TO USE THE DCL MONITOR COMMAND. NOTE: The ID -SYSTEM- is an example, and should be substituted as necessary with valid user ID's that are associated with accounts you wish to grant access to. =========================================================================== End of Text provided by Digital Equipment Corporation --------------------------------------------------------------------------- CERT wishes to thank Teun Nijssen of CERT-NL (the SURFnet CERT, in the Netherlands) for bringing this security vulnerability to our attention. We would also like to thank Digital Equipment Corporation's Software Security Response Team for providing information on this vulnerability. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: cert@cert.org Telephone: 412-268-7090 (24-hour hotline) CERT personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.org (192.88.209.5). - - - - - - - - - - - - - - - - - From klong@sura.net Wed Sep 23 11:50:49 1992 Received: from mizzou.sura.net by merit.edu (5.65/1123-1.0) id AA12044; Wed, 23 Sep 92 11:50:49 -0400 Received: by mizzou.sura.net (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA21690; Wed, 23 Sep 92 11:50:44 -0400 Date: Wed, 23 Sep 92 11:50:44 -0400 From: klong@sura.net Message-Id: <9209231550.AA21690@mizzou.sura.net> To: regional-techs Subject: FYI From klong Wed Sep 23 11:48:30 1992 To: status@sura.net Subject: GIT2 Status: R 09/23/92 The Cisco router at Georgia Tech (GIT2) will be undergoing diagnostics. This could be disruptive for those networks primary to AS279 (SURA South). We apologize for any inconvenience this may cause. Kim Long SURAnet Operations - - - - - - - - - - - - - - - - - From donnab@CERF.NET Wed Sep 23 12:36:31 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA14059; Wed, 23 Sep 92 12:36:31 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA14538; Wed, 23 Sep 92 09:37:09 PDT Date: Wed, 23 Sep 92 09:37:09 PDT From: Donna Bigley Message-Id: <9209231637.AA14538@nic.cerf.net> To: help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, September 14, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, September 14th through Sunday, September 20th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 20-sept-92.txt All times are in Pacific Daylight Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 1301 SITE: CICESE SITES AFFECTED: CICESE TIME STARTED: FRI. 09-11-92 11:28 TIME ENDED: THU. 09-17-92 13:39 TIME STARTED: THU. 09-17-92 18:07 (Intermittent Access) TIME ENDED: TIME ELAPSED: Still Down REASON: Ticket Still Open TICKET #: 1302 SITE: PEREGRINE SITES AFFECTED: PEREGRINE TIME STARTED: SUN. 09-13-92 12:24 TIME ENDED: TUE. 09-15-92 15:33 TIME ELAPSED: 2 days 3 hours 9 min. REASON: Power Outage TICKET #: 1307 SITE: CSUCO/SWRL SITES AFFECTED: CSUCO/SWRL TIME STARTED: SUN. 09-13-92 20:04 TIME ENDED: SUN. 09-13-92 21:22 TIME ELAPSED: 1 hour 18 min. REASON: Unknown TICKET #: 1312 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: TUE. 09-15-92 09:58 TIME ENDED: TUE. 09-15-92 10:15 TIME STARTED: TUE. 09-15-92 10:30 TIME ENDED: TUE. 09-15-92 13:36 TIME STARTED: TUE. 09-15-92 14:39 TIME ENDED: TUE. 09-15-92 15:13 TIME ELAPSED: 3 hours 57 min. REASON: Link Failure (MCI Equipment Trouble) TICKET #: 1313 SITE: NetLabs SITES AFFECTED: NetLabs TIME STARTED: WED. 09-16-92 08:39 TIME ENDED: WED. 09-16-92 08:47 TIME STARTED: WED. 09-16-92 11:26 (Telco Testing) TIME ENDED: WED. 09-16-92 11:38 TIME ELAPSED: 20 min. REASON: Unknown TICKET #: 1316 SITE: SPARTA SITES AFFECTED: SPARTA TIME STARTED: WED. 09-16-92 11:28 TIME ENDED: WED. 09-16-92 12:15 TIME ELAPSED: 47 min. REASON: Unknown TICKET #: 1314 SITE: CLAREMONT SITES AFFECTED: CLAREMONT TIME STARTED: WED. 09-16-92 17:16 TIME ENDED: WED. 09-16-92 17:22 TIME ELAPSED: 6 min. REASON: Power Outage TICKET #: 1324 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: THU. 09-17-92 00:02 TIME ENDED: THU. 09-17-92 00:12 TIME STARTED: THU. 09-17-92 01:16 TIME ENDED: THU. 09-17-92 01:33 TIME ELAPSED: 37 min. REASON: Unknown TICKET #: 1326 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: FRI. 09-18-92 09:30 TIME ENDED: FRI. 09-18-92 09:56 TIME ELAPSED: 26 min. (Intermittent Access) REASON: Link Failure (Local Line Trouble in Rio) TICKET #: 1338 SITE: UCI SITES AFFECTED: UCI DIAL N' CERF, UCI NetBlazer, CITOH, CCCD, HUGHES, FULLERTON, EMULEX, UNOCAL, CSUCO/SWRL, MTI, SPARTA, CMD, MDC, BECKMAN, AND IRVINE COMPILER. TIME STARTED: SAT. 09-19-92 TIME ENDED: SAT. 09-19-92 07:03 TIME ELAPSED: REASON: Power Outage TICKET #: 1329 SITE: CITOH SITES AFFECTED: CITOH TIME STARTED: SAT. 09-19-92 07:03 TIME ENDED: SUN. 09-20-92 14:06 TIME ELAPSED: 1 day 7 hours 3 min. REASON: Power Outage/Equipment Trouble (UCI Power Outage) (NetBlazer Rebooted) TICKET #: 1330 SITE: UCI-CIT T3 SITES AFFECTED: UCI-CIT T3 TIME STARTED: SAT. 09-19-92 07:03 TIME ENDED: TIME ELAPSED: Still Down REASON: Ticket Still Open TICKET #: 1336 SITE: SDSC-UCLA T1 SITES AFFECTED: SDSC-UCLA T1 TIME STARTED: SAT. 09-19-92 21:37 TIME ENDED: SAT. 09-19-92 21:40 TIME ELAPSED: 3 min. REASON: Vendor Scheduled Maintenance (MCI Telco) TICKET #: 1336 SITE: SDSC-UCOP T1 SITES AFFECTED: SDSC-UCOP T1 TIME STARTED: SAT. 09-19-92 21:35 TIME ENDED: SAT. 09-19-92 21:39 TIME ELAPSED: 4 min. REASON: Vendor Scheduled Maintenance (MCI Telco) TICKET #: 1325 SITE: CALTECH-SDSC T1 SITES AFFECTED: CALTECH-SDSC T1 TIME STARTED: SAT. 09-19-92 22:00 TIME ENDED: SUN. 09-20-92 03:00 TIME ELAPSED: 2 min. REASON: Vendor Scheduled Maintenance (MCI Telco) TICKET #: 1318 SITE: CLAREMONT SITES AFFECTED: CLAREMONT TIME STARTED: SUN. 09-20-92 TIME ENDED: SUN. 09-20-92 08:38 TIME ELAPSED: REASON: Site Scheduled Maintenance ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps 00.2% 16:00 SDSC/GA 10.000 mbps 00.1% 02:00 SDSC/CALTECH 1.544 mbps 20.6% 15:00 SDSC/UCI 1.544 mbps 14.4% 15:00 SDSC/UCLA 1.544 mbps 13.9% 15:00 SDSC/UCOP 1.544 mbps 09.5% 15:00 UCI/UCLA 1.544 mbps 01.6% 15:00 SDSC/UCR 512 kbps 02.5% 19:00 UCLA/UCSB 512 kbps 17.2% 15:00 CALTECH/HUGHES 1.544 mbps 00.2% 08:00 SDSC/AGI 1.544 mbps 00.2% 18:00 SDSC/BIOSYM 1.544 mbps 00.4% 15:00 SDSC/GD 1.544 mbps 01.9% 15:00 SDSC/SAIC 1.544 mbps 01.3% 09:00 SDSC/SEASPACE 1.544 mbps 01.6% 17:00 UCI/CSU CO(SWRL) 1.544 mbps 05.5% 15:00 UCI/MDC 1.544 mbps 03.1% 07:00 UCLA/GETTY 1.544 mbps 00.2% 14:00 UCOP/APPLE 1.544 mbps 01.7% 09:00 UCOP/CISCO 1.544 mbps 00.2% 15:00 UCR/LLUMC 1.544 mbps 00.6% 07:00 CALTECH/AJS 56 kbps 01.9% 15:00 CALTECH/CADAM 56 kbps 00.4% 09:00 CALTECH/CITY OF HOPE 56 kbps 11.2% 15:00 CALTECH/CLAREMONT 56 kbps 37.1% 15:00 CALTECH/DISNEY 56 kbps 13.5% 15:00 CALTECH/OXY 56 kbps 10.7% 15:00 CALTECH/SCAQMD 56 kbps 10.4% 16:00 SDSC/API 56 kbps 06.3% 19:00 SDSC/CICESE 56 kbps 01.4% 14:00 SDSC/KOREA 56 kbps 15.0% 01:00 SDSC/QUALCOMM 56 kbps 22.7% 15:00 SDSC/REDE-RIO 56 kbps 82.9% 17:00 SDSC/SCIH 56 kbps 03.7% 15:00 SDSC/SDG&E 56 kbps 00.1% 18:00 SDSC/USD 56 kbps 08.7% 15:00 SDSC/USIU 56 kbps 03.7% 09:00 UCI/BECKMAN 56 kbps 07.2% 19:00 UCI/CCCD 56 kbps 05.2% 03:00 UCI/CMD 56 kbps 00.6% 15:00 UCI/EMULEX 56 kbps 04.6% 17:00 UCI/FULLERTON 56 kbps 12.2% 16:00 UCI/HUGHES 56 kbps 20.2% 15:00 UCI/ICC 56 kbps 04.9% 22:00 UCI/MTI 56 kbps 04.7% 01:00 UCI/SPARTA 56 kbps 10.5% 15:00 UCI/UNOCAL 56 kbps 12.6% 15:00 UCLA/CRSS 56 kbps 00.3% 15:00 UCLA/DATAPRODUCTS 56 kbps 00.9% 06:00 UCLA/GTE 56 kbps 09.8% 15:00 UCLA/ISX 56 kbps 00.7% 15:00 UCLA/LITTON 56 kbps 00.3% 22:00 UCLA/PEPPERDINE 56 kbps 01.9% 19:00 UCLA/QUOTRON 56 kbps 06.4% 19:00 UCLA/SMC 56 kbps 08.5% 15:00 UCOP/FARALLON 56 kbps 06.3% 10:00 UCOP/INTEL 56 kbps 39.4% 15:00 UCOP/LSIL 56 kbps 08.6% 15:00 UCOP/NETLABS 56 kbps 10.4% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PDT on Sept. 21, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 71 days 11 hours 37 minutes SDSC LongBoard [134.24.99.254] Up: 97 days 08 hours 21 minutes SDSC Drzog [132.249.16.13] Up: 130 days 14 hours 24 minutes SDSC Hang10 [132.249.16.15] Up: 130 days 14 hours 24 minutes UCI [128.200.1.101] Up: 01 days 17 hours 12 minutes [Power Outage - See Ticket #1338] UCLA [128.97.130.10] Up: 168 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 180 days 16 hours 38 minutes UCR [134.24.108.105] Up: 71 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 71 days 09 hours 43 minutes APPLE [134.24.70.200] Up: 01 days 11 hours 19 minutes [Unknown] BIOSYM [134.24.57.200] Up: 101 days 07 hours 13 minutes CISCO Systems [134.24.54.200] Up: 10 days 11 hours 26 minutes CSUCO/SWRL [130.150.102.200] Up: 51 days 18 hours 22 minutes GA [134.24.20.10] Up: 00 days 00 hours 12 minutes [Equipment Trouble] GD [134.24.60.200] Up: 143 days 16 hours 18 minutes GETTY [134.24.235.200] Up: 38 days 07 hours 02 minutes HUGHES_CIT [134.24.103.200] Up: 00 days 11 hours 11 minutes [Unknown] LLUMC [134.24.208.200] Up: 50 days 13 hours 45 minutes MDC [134.24.65.200] Up: 30 days 08 hours 00 minutes SAIC [134.24.53.208] Up: 130 days 14 hours 10 minutes UCSB [134.24.107.107] Up: 88 days 15 hours 45 minutes CERF 56 AJS [134.24.225.101] Up: 40 days 13 hours 24 minutes API [134.24.224.200] Up: 87 days 13 hours 18 minutes BECKMAN [134.24.237.200] Up: 110 days 12 hours 10 minutes CADAM [134.24.229.200] Up: 23 days 06 hours 23 minutes CCCD [134.24.219.200] Up: 84 days 19 hours 14 minutes CICESE [134.24.227.200] Up: Still Down [Ticket Still Open - See Ticket #1301] CITY_OF_HOPE [134.24.233.200] Up: 00 days 06 hours 38 minutes [Equipment Trouble] CLAREMONT [134.24.206.109] Up: 00 days 15 hours 37 minutes [Site Scheduled Maintenance - See Ticket #1318] CMD [134.24.218.200] Up: 16 days 07 hours 29 minutes CRSS [134.24.232.200] Up: 46 days 12 hours 16 minutes DATAPRODUCTS [134.24.211.200] Up: 173 days 13 hours 01 minutes DISNEY [134.24.207.211] Up: 34 days 19 hours 57 minutes EMULEX [134.24.209.212] Up: 22 days 07 hours 37 minutes FARALLON [134.24.56.200] Up: 48 days 15 hours 51 minutes FULLERTON [134.24.214.217] Up: 84 days 17 hours 55 minutes GTE [134.24.212.200] Up: 189 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 43 days 16 hours 21 minutes INTEL [134.24.73.200] Up: 176 days 11 hours 34 minutes ICC [134.24.238.200] Up: 74 days 08 hours 39 minutes LITTON [134.24.213.200] Up: 30 days 13 hours 29 minutes LSIL [134.24.72.200] Up: 138 days 08 hours 26 minutes MTI [134.24.216.100] Up: 26 days 08 hours 48 minutes NETLABS [134.24.71.200] Up: 53 days 09 hours 33 minutes OXY [134.24.205.108] Up: 20 days 17 hours 15 minutes PEPPERDINE [134.24.203.218] Up: 163 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 07 days 00 hours 14 minutes QUOTRON [134.24.230.202] Up: 28 days 06 hours 06 minutes REDE_RIO [134.24.112.200] Up: 12 days 08 hours 44 minutes SANTA MONICA [134.24.210.219] Up: 53 days 13 hours 40 minutes SCAQMD [134.24.234.200] Up: 03 days 11 hours 32 minutes [Site Activity] SCI-HOR [134.24.109.205] Up: 131 days 06 hours 02 minutes SDG&E [134.24.226.200] Up: 110 days 13 hours 39 minutes SEASPACE [134.24.80.200] Up: 165 days 11 hours 26 minutes SERI/KOREA [134.24.223.200] Up: 09 days 05 hours 58 minutes SPARTA [134.24.215.200] Up: 174 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 199 days 01 hours 57 minutes USD [134.24.201.106] Up: 41 days 17 hours 00 minutes USIU [134.24.222.215] Up: 442 days 17 hours 07 minutes DIAL n' CERF Plus 14.4 CITOH [161.1.1.1] Up: 00 days 10 hours 09 minutes [Power Outage/Equipment Trouble - See Ticket #1329] MARKV [192.122.251.6] Up: 24 days 01 hours 14 minutes PEREGRINE [192.72.253.97] Up: 05 days 13 hours 51 minutes [Power Outage - See Ticket #1302] DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 52 days 11 hours 19 minutes DNC-UCI [134.24.2.2] Up: 01 days 17 hours 12 minutes [Power Outage - See Ticket #1338] DNC-UCLA [134.24.3.2] Up: 16 days 15 hours 05 minutes DNC-CALTECH [134.24.4.2] Up: 24 days 01 hours 14 minutes DNC-UCOP [134.24.5.2] Up: 83 days 04 hours 29 minutes CIT-NETBLAZER [130.152.104.1] Up: 73 days 13 hours 47 minutes SDSC-NETBLAZER [192.102.249.25] Up: 16 days 15 hours 05 minutes UCI-NETBLAZER [134.24.92.2] Up: 01 days 17 hours 12 minutes [Power Outage - See Ticket #1338] UCLA-NETBLAZER [134.24.93.2] Up: 32 days 06 hours 54 minutes UCOP-NETBLAZER [134.24.250.2] Up: 180 days 23 hours 54 minutes - - - - - - - - - - - - - - - - - From klong@sura.net Wed Sep 23 13:56:44 1992 Received: from mizzou.sura.net by merit.edu (5.65/1123-1.0) id AA17402; Wed, 23 Sep 92 13:56:44 -0400 Received: by mizzou.sura.net (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA22074; Wed, 23 Sep 92 13:56:43 -0400 Date: Wed, 23 Sep 92 13:56:43 -0400 From: klong@sura.net Message-Id: <9209231756.AA22074@mizzou.sura.net> To: regional-techs, status@sura.net Subject: GIT2 diagnostics 09/23/92 Testing will begin now for an undetermined amount 14:00 of time. Thank you for your patience. Kim Long SURAnet Operations - - - - - - - - - - - - - - - - - From klong@sura.net Wed Sep 23 14:09:14 1992 Received: from mizzou.sura.net by merit.edu (5.65/1123-1.0) id AA17889; Wed, 23 Sep 92 14:09:14 -0400 Received: by mizzou.sura.net (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA22129; Wed, 23 Sep 92 14:09:13 -0400 Date: Wed, 23 Sep 92 14:09:13 -0400 From: klong@sura.net Message-Id: <9209231809.AA22129@mizzou.sura.net> To: regional-techs, status@sura.net Subject: ICM gateway at SURAnet 09/23/92 The ICM gateway at SURAnet is down for maintenance. 14:10 We have no estimated uptime on this outage. Kim Long SURAnet Operations - - - - - - - - - - - - - - - - - From skw Wed Sep 23 22:20:14 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA06126; Wed, 23 Sep 92 22:20:14 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA18393; Wed, 23 Sep 92 22:20:12 EDT Date: Wed, 23 Sep 92 22:20:12 EDT From: skw Message-Id: <9209240220.AA18393@home.merit.edu> To: regional-techs Subject: New NSFNET template.net wording Hi. Below is the new and improved template.net form which incorporates the fine suggestions from Piet and others. Thanks, and keep the suggestions coming. A full copy of template.net with additional explanatory info can be pulled from: nis.nsf.net:nsfnet/announced.networks/template.net --Steve Widmayer Merit/NSFNET *********************************************************************** [nis.nsf.net:nsfnet/announced.networks/template.net] Version 5.4 23 Sep 1992 NSFNET Configuration Request Template for the NSFNET policy-based routing data base ---- Network Announcement Change Request ---- This template is to request announcement of networks to the NSFNET backbone. Configuration requests may only be submitted by the designated Routing contacts for the Autonomous Systems of the NSFNET. Configuration requests should be submitted to nsfnet-admin@merit.edu. Please read the explanation at the bottom of this form if you are unfamiliar with its contents. ***************************************************************************** ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone, agree that traffic from these networks that will transit the NSFNET backbone complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. Inbound Announcements Add/Del Network: to NSFNET or Change T1, T3 ----------------------- --------- Network Number/Name or both 1st AS# 2nd AS# 3rd AS# A/D/C Country ------------------- -------- ------- ------- ------- --------- ------- Network Name: Organization Name: Organization Address: Additional Comments (optional): ***************************************************************************** - - - - - - - - - - - - - - - - - From rty Fri Sep 25 07:04:38 1992 Received: by merit.edu (5.65/1123-1.0) id AA11901; Fri, 25 Sep 92 07:04:47 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA11895; Fri, 25 Sep 92 07:04:38 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA19232; Fri, 25 Sep 92 07:04:37 EDT Date: Fri, 25 Sep 92 07:04:37 EDT Message-Id: <9209251104.AA19232@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following additions have been made to the NSFNET policy-based routing database, and routes should be in effect by 08:00 EDT. T1 Network: ---------- Network IP: 146.180 Network Name: SBCOC Location: SBC/OC Services, L.P., 141 W. Jackson, 8th Floor, Chicago, IL 60604, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 158.12 Network Name: WRF-MIL Location: US Army Laboratory Command/Harry Diamond Lab, Dawson Beach Road, Woodbridge, VA 22191, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 2:184 Milnet (FIX-East) 3:164 Milnet (FIX-West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.67.113 Network Name: PSCI-NETS Location: Boeing Computer Support Services, P.O. Box 9022, Marshall Space Flight Center, AL 35812, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.67.119 Network Name: PSCI-NETS1 Location: Boeing Computer Support Services, P.O. Box 9022, Marshall Space Flight Center, AL 35812, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.85.154 Network Name: GM-EDS153 Location: EDS, 750 Tower Drive, 1st Floor, Troy, MI 48089-7019, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.93.98 Network Name: INRA-LAON Location: INRA, rue Fernand Christ, BP 101, 02004 Laon CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.93.99 Network Name: INRA-MONS Location: INRA, Domaine Brunehaut, Estrees-Mons, 80200 Peronne, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.93.119 Network Name: SI-INPG Location: Institut National Polytechnique de Grenoble Services Informatiques, 46 Av. Felix Viallet, F-38031 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.93.120 Network Name: ENSGI Location: ENSGI, 46 Av. Felix Viallet, F-38031 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.108.68 Network Name: WZBERLIN-LAN Location: Wissenschaftszentrum Berlin, DV, Reichpietschufer 50, D-W-1000 Berlin 30, GERMANY Country Code: DE 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 192.124.234 Network Name: TENET-POP-15 Location: University of Texas System, Services Building, Austin, TX 78712, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.134.107 Network Name: INRA-GRENBL Location: INRA, Laboratoire de Recherches et Etudes Economiques, BP 47 X, 38040 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.134.112 Network Name: INRA-INA-INF Location: INRA, Institut National Agronomique Paris-Grignon, 16 rue Claude Bernard, 75231 Paris CEDEX 05, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.156.188 Network Name: AMPERSAND-NET Location: Ampersand, Inc., 66 Tadmuck Road, Suite 6, Westford, MA 01886, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.188.249 Network Name: SBEI Location: SBE, Inc., 2400 Bisso Lane, Concord, CA 94520, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.190.4 Network Name: MSI1-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.190.5 Network Name: MSI2-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.190.12 Network Name: MSI3-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.195.245 Network Name: UMI-DMZ Location: University Microfilms, Inc., 300 North Zeeb Road, Ann Arbor, MI 48106, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.167 Network Name: PAE-NET Location: PAE Associates, 9056 Arlington Blvd., Fairfax, VA 22031, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.207.105 Network Name: PRODIGY-DMZ Location: Prodigy Services Company, 445 Hamilton Avenue, White Plains, NY 10601, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.16 Network Name: SES-C011 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.17 Network Name: SES-C012 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.18 Network Name: SES-C013 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.19 Network Name: SES-C014 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.20 Network Name: SES-C015 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.21 Network Name: SES-C016 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.22 Network Name: SES-C017 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.23 Network Name: SES-C018 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.24 Network Name: SES-C019 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.25 Network Name: SES-C020 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6582 T3 Network: ---------- Network IP: 146.180 Network Name: SBCOC Location: SBC/OC Services, L.P., 141 W. Jackson, 8th Floor, Chicago, IL 60604, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 158.12 Network Name: WRF-MIL Location: US Army Laboratory Command/Harry Diamond Lab, Dawson Beach Road, Woodbridge, VA 22191, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 2:184 Milnet (FIX-East) 3:164 Milnet (FIX-West) Network IP: 192.67.113 Network Name: PSCI-NETS Location: Boeing Computer Support Services, P.O. Box 9022, Marshall Space Flight Center, AL 35812, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.67.119 Network Name: PSCI-NETS1 Location: Boeing Computer Support Services, P.O. Box 9022, Marshall Space Flight Center, AL 35812, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.85.154 Network Name: GM-EDS153 Location: EDS, 750 Tower Drive, 1st Floor, Troy, MI 48089-7019, USA Country Code: US 1:1325 ANS Cleveland - DNSS 43 Network IP: 192.93.98 Network Name: INRA-LAON Location: INRA, rue Fernand Christ, BP 101, 02004 Laon CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.93.99 Network Name: INRA-MONS Location: INRA, Domaine Brunehaut, Estrees-Mons, 80200 Peronne, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.93.119 Network Name: SI-INPG Location: Institut National Polytechnique de Grenoble Services Informatiques, 46 Av. Felix Viallet, F-38031 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.93.120 Network Name: ENSGI Location: ENSGI, 46 Av. Felix Viallet, F-38031 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.124.234 Network Name: TENET-POP-15 Location: University of Texas System, Services Building, Austin, TX 78712, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 192.134.107 Network Name: INRA-GRENBL Location: INRA, Laboratoire de Recherches et Etudes Economiques, BP 47 X, 38040 Grenoble CEDEX, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.134.112 Network Name: INRA-INA-INF Location: INRA, Institut National Agronomique Paris-Grignon, 16 rue Claude Bernard, 75231 Paris CEDEX 05, FRANCE Country Code: FR 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.156.188 Network Name: AMPERSAND-NET Location: Ampersand, Inc., 66 Tadmuck Road, Suite 6, Westford, MA 01886, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.188.249 Network Name: SBEI Location: SBE, Inc., 2400 Bisso Lane, Concord, CA 94520, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.190.4 Network Name: MSI1-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.190.5 Network Name: MSI2-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.190.12 Network Name: MSI3-NET Location: Molecular Simulations Inc., 16 New England Executive Park, Burlington, MA 01803-5297, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.195.245 Network Name: UMI-DMZ Location: University Microfilms, Inc., 300 North Zeeb Road, Ann Arbor, MI 48106, USA Country Code: US 1:1975 University Microfilms, Inc. Network IP: 192.203.167 Network Name: PAE-NET Location: PAE Associates, 9056 Arlington Blvd., Fairfax, VA 22031, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.207.105 Network Name: PRODIGY-DMZ Location: Prodigy Services Company, 445 Hamilton Avenue, White Plains, NY 10601, USA Country Code: US 1:1324 ANS New York City - DNSS 35 Network IP: 192.225.16 Network Name: SES-C011 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.17 Network Name: SES-C012 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.18 Network Name: SES-C013 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.19 Network Name: SES-C014 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.20 Network Name: SES-C015 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.21 Network Name: SES-C016 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.22 Network Name: SES-C017 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.23 Network Name: SES-C018 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.24 Network Name: SES-C019 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.225.25 Network Name: SES-C020 Location: Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Total configured T3 networks: 5858 The following T3 routers have also been added: AS Number: 1975 AS Notes: University Microfilms, Inc. AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.190 - UMI, Ann Arbor, MI - ENSS190 Ann Arbor, MI Gate: 192.195.245.2 - charon.umi.com University Microfilms, Inc., Ann Arbor, MI AS Number: 2002 AS Notes: IBM-PV-AS AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.205 - IBM Packet Video White Plains, NY Gate: 192.231.10.2 - gate name unknown IBM Packet Video, White Plains, NY The following T3 Core Backbone routers have also been added: NSS IP: 140.222.104 (T3 PROD C-NSS #104 in BkBn AS 690) Name: ATU-T3-B Location: Atlanta, Georgia NSS IP: 140.222.105 (T3 PROD C-NSS #105 in BkBn AS 690) Name: ATU-T3-C1 Location: Atlanta, Georgia NSS IP: 140.222.107 (T3 PROD C-NSS #107 in BkBn AS 690) Name: ATU-T1-C1 Location: Atlanta, Georgia ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From rty Tue Sep 29 04:18:21 1992 Received: by merit.edu (5.65/1123-1.0) id AA01284; Tue, 29 Sep 92 04:18:34 -0400 From: "Riaz Taherzadeh-Yazdian" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA01279; Tue, 29 Sep 92 04:18:21 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA17760; Tue, 29 Sep 92 04:18:20 EDT Date: Tue, 29 Sep 92 04:18:20 EDT Message-Id: <9209290818.AA17760@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following additions have been made to the NSFNET policy-based routing database, and routes should be in effect by 08:00 EDT. T1 Network: ---------- Network IP: 131.135 Network Name: DRES-NET2 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNet Regional Network / PSI 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 140.211 Network Name: OSSHENET Location: Oregon State System of Higher Education, Administrative Services Building, Room B210, Oregon State University, Corvallis, OR 97331, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 149.141 Network Name: ROCKWELL Location: Rockwell International Corporation, Information Systems Center, 2201 Seal Beach Boulevard, P.O. Box 2515, Seal Beach, CA 90740, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 149.149 Network Name: TNTECH Location: Tennessee Technological University, Computer Center, P.O. Box 5071, Cookeville, TN 38505, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 152.158 Network Name: ANS-BNET3 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.77.164 Network Name: ANS-CNET14 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.77.165 Network Name: ANS-CNET15 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.84.121 Network Name: FARINON Location: Harris Corporation, Farinon Division, 1691 Bayport Avenue, San Carlos, CA 94070-5307, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.87.59 Network Name: SNET-STOA Location: SURFnet Meetings, P.O. Box 19035, NL-3501 DA Utrecht, NETHERLANDS Country Code: NL 1:590 EASInet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:1800 ICM (FIX-East) Network IP: 192.146.158 Network Name: GSFC3 Location: NASA Goddard Space Flight Center, Greenbelt, MD 20771, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.161.1 Network Name: HARRIS-COMM1 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.161.2 Network Name: HARRIS-COMM2 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.161.3 Network Name: HARRIS-COMM3 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.161.4 Network Name: HARRIS-COMM4 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.190.9 Network Name: RWU-NET Location: Roger Williams University, Acedemic Computing, 1 Old Ferry Road, Bristol, RI 02809-2921, USA Country Code: US 1:1384 NEARnet Regional Network 2:1383 NEARnet Regional Network 3:560 NEARnet Regional Network 4:281 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.190.252 Network Name: FERRUM-NET Location: Ferrum College, Ferrum, VA 24088, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.203.133 Network Name: PROTOOLS Location: Protools, 14976 N.W. Greenbrier Parkway, Beaverton, OR 97006, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.202 Network Name: OTC-SW Location: Oakland Schools, Oakland Technical Center, 1000 Beck Rd., Wixom, MI 48393, USA Country Code: US 1:233 Merit Regional Network 2:237 Merit Regional Network 3:177 Merit Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.211.32 Network Name: NETBLK-AIDT-32 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.211.34 Network Name: NETBLK-AIDT-34 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.211.38 Network Name: NETBLK-AIDT-38 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.211.42 Network Name: NETBLK-AIDT-42 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.222.32 Network Name: NETBLK-SEATTLEU-NET-32 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.222.33 Network Name: NETBLK-SEATTLEU-NET-33 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.222.34 Network Name: NETBLK-SEATTLEU-NET-34 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.222.35 Network Name: NETBLK-SEATTLEU-NET-35 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.225.67 Network Name: GSFC8 Location: NASA Goddard Space Flight Center, Greenbelt, MD 20771, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.229.32 Network Name: VERDIX-32 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.33 Network Name: VERDIX-33 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.34 Network Name: VERDIX-34 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.35 Network Name: VERDIX-35 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.36 Network Name: VERDIX-36 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.37 Network Name: VERDIX-37 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.38 Network Name: VERDIX-38 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.39 Network Name: VERDIX-39 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.40 Network Name: VERDIX-40 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.41 Network Name: VERDIX-41 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.42 Network Name: VERDIX-42 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.43 Network Name: VERDIX-43 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.44 Network Name: VERDIX-44 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.45 Network Name: VERDIX-45 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.46 Network Name: VERDIX-46 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.47 Network Name: VERDIX-47 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.48 Network Name: VERDIX-48 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.49 Network Name: VERDIX-49 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.50 Network Name: VERDIX-50 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.51 Network Name: VERDIX-51 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.52 Network Name: VERDIX-52 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.53 Network Name: VERDIX-53 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.54 Network Name: VERDIX-54 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.55 Network Name: VERDIX-55 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.56 Network Name: VERDIX-56 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.57 Network Name: VERDIX-57 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.58 Network Name: VERDIX-58 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.59 Network Name: VERDIX-59 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.60 Network Name: VERDIX-60 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.61 Network Name: VERDIX-61 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.62 Network Name: VERDIX-62 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.229.63 Network Name: VERDIX-63 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.231.8 Network Name: PV-EN-GBG Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.231.9 Network Name: PV-EN-MLF Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.231.10 Network Name: PV-EN-SHARED Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Total configured T1 networks: 6640 T3 Network: ---------- Network IP: 45 Network Name: Show-Net-A Location: Interop '92 Fall, Moscone Convention Center, San Francisco, CA, USA Country Code: US 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 131.135 Network Name: DRES-NET2 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNet Regional Network / PSI Network IP: 140.211 Network Name: OSSHENET Location: Oregon State System of Higher Education, Administrative Services Building, Room B210, Oregon State University, Corvallis, OR 97331, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 149.141 Network Name: ROCKWELL Location: Rockwell International Corporation, Information Systems Center, 2201 Seal Beach Boulevard, P.O. Box 2515, Seal Beach, CA 90740, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 149.149 Network Name: TNTECH Location: Tennessee Technological University, Computer Center, P.O. Box 5071, Cookeville, TN 38505, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 152.158 Network Name: ANS-BNET3 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.77.164 Network Name: ANS-CNET14 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.77.165 Network Name: ANS-CNET15 Location: Advanced Network & Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.84.121 Network Name: FARINON Location: Harris Corporation, Farinon Division, 1691 Bayport Avenue, San Carlos, CA 94070-5307, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.87.59 Network Name: SNET-STOA Location: SURFnet Meetings, P.O. Box 19035, NL-3501 DA Utrecht, NETHERLANDS Country Code: NL 42:1800 ICM (FIX-East) Network IP: 192.146.158 Network Name: GSFC3 Location: NASA Goddard Space Flight Center, Greenbelt, MD 20771, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.161.1 Network Name: HARRIS-COMM1 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.161.2 Network Name: HARRIS-COMM2 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.161.3 Network Name: HARRIS-COMM3 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.161.4 Network Name: HARRIS-COMM4 Location: Harris Corporation, 1025 West Nasa Blvd., Melbourne, FL 32919, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.190.9 Network Name: RWU-NET Location: Roger Williams University, Acedemic Computing, 1 Old Ferry Road, Bristol, RI 02809-2921, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 43:701 Alternet Network IP: 192.190.252 Network Name: FERRUM-NET Location: Ferrum College, Ferrum, VA 24088, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.133 Network Name: PROTOOLS Location: Protools, 14976 N.W. Greenbrier Parkway, Beaverton, OR 97006, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.203.202 Network Name: OTC-SW Location: Oakland Schools, Oakland Technical Center, 1000 Beck Rd., Wixom, MI 48393, USA Country Code: US 1:237 MERIT network 2:233 MERIT network Network IP: 192.211.32 Network Name: NETBLK-AIDT-32 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.211.34 Network Name: NETBLK-AIDT-34 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.211.38 Network Name: NETBLK-AIDT-38 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.211.42 Network Name: NETBLK-AIDT-42 Location: Alabama Industrial Development Training, One Technology Ct., Montgomery, AL 35116-3200, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.222.32 Network Name: NETBLK-SEATTLEU-NET-32 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.222.33 Network Name: NETBLK-SEATTLEU-NET-33 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.222.34 Network Name: NETBLK-SEATTLEU-NET-34 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.222.35 Network Name: NETBLK-SEATTLEU-NET-35 Location: Seattle University, Broadway & Madison, Seattle, WA 98122, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.225.67 Network Name: GSFC8 Location: NASA Goddard Space Flight Center, Greenbelt, MD 20771, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.229.32 Network Name: VERDIX-32 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.33 Network Name: VERDIX-33 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.34 Network Name: VERDIX-34 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.35 Network Name: VERDIX-35 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.36 Network Name: VERDIX-36 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.37 Network Name: VERDIX-37 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.38 Network Name: VERDIX-38 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.39 Network Name: VERDIX-39 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.40 Network Name: VERDIX-40 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.41 Network Name: VERDIX-41 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.42 Network Name: VERDIX-42 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.43 Network Name: VERDIX-43 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.44 Network Name: VERDIX-44 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.45 Network Name: VERDIX-45 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.46 Network Name: VERDIX-46 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.47 Network Name: VERDIX-47 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.48 Network Name: VERDIX-48 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.49 Network Name: VERDIX-49 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.50 Network Name: VERDIX-50 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.51 Network Name: VERDIX-51 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.52 Network Name: VERDIX-52 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.53 Network Name: VERDIX-53 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.54 Network Name: VERDIX-54 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.55 Network Name: VERDIX-55 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.56 Network Name: VERDIX-56 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.57 Network Name: VERDIX-57 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.58 Network Name: VERDIX-58 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.59 Network Name: VERDIX-59 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.60 Network Name: VERDIX-60 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.61 Network Name: VERDIX-61 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.62 Network Name: VERDIX-62 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.229.63 Network Name: VERDIX-63 Location: Verdix Corporation, 205 Van Buren Street, Herndon, VA 22070, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 192.231.8 Network Name: PV-EN-GBG Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.231.9 Network Name: PV-EN-MLF Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.231.10 Network Name: PV-EN-SHARED Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:2002 IBM-PV-AS Total configured T3 networks: 5920 The following T3 routers have also been added: AS Number: 1333 AS Notes: ANS Atlanta - DNSS 107 AS Country Code: US ANS: Yes BkBn: 690 NSS: 140.222.107 - ATU-T1-C1 Atlanta, Georgia Gate: 192.103.73.6 - ATU-AGS Atlanta, GA ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Riaz Taherzadeh-Yazdian Merit/NSFNET rty@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu - - - - - - - - - - - - - - - - - From donnab@CERF.NET Tue Sep 29 14:04:23 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA26274; Tue, 29 Sep 92 14:04:23 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA03608; Tue, 29 Sep 92 11:05:03 PDT Date: Tue, 29 Sep 92 11:05:03 PDT From: Donna Bigley Message-Id: <9209291805.AA03608@nic.cerf.net> To: help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, Sept. 21, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, September 21st through Sunday, September 27th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 27-sept-92.txt All times are in Pacific Daylight Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 1301 SITE: CICESE SITES AFFECTED: CICESE TIME STARTED: FRI. 09-11-92 11:28 TIME ENDED: THU. 09-17-92 13:39 TIME STARTED: THU. 09-17-92 18:07 (Intermittent Access) TIME ENDED: WED. 09-23-92 21:34 (SAT NET reinstalled modem) TIME ELAPSED: 12 days 5 hours 38 min. REASON: Unscheduled Outage/Link Failure TICKET #: 1330 SITE: UCI-CIT T3 SITES AFFECTED: UCI-CIT T3 TIME STARTED: SAT. 09-19-92 07:03 TIME ENDED: THU. 09-24-92 15:52 TIME ELAPSED: 5 days 8 hours 49 min. REASON: Link Failure (CALTECH side of the circuit) TICKET #: 1339 SITE: MARKV SITES AFFECTED: MARKV TIME STARTED: TUE. 09-22-92 11:11 TIME ENDED: THU. 09-24-92 10:38 TIME ELAPSED: 1 day 23 hours 27 min. REASON: Equipment Trouble TICKET #: 1341 SITE: COAST COMMUNITY COLLEGE DISTRICT SITES AFFECTED: COAST COMMUNITY COLLEGE DISTRICT TIME STARTED: WED. 09-23-92 05:30 TIME ENDED: WED. 09-23-92 06:32 TIME ELAPSED: 1 hour 2 min. REASON: Unknown TICKET #: 1342 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: WED. 09-23-92 16:17 TIME ENDED: WED. 09-23-92 17:42 TIME ELAPSED: 1 hour 25 min. (MCI Link Failure between Lodi and N.Y.) REASON: Link Failure TICKET #: 1300 SITE: CALTECH SITES AFFECTED: CALTECH DIAL N' CERF, CALTECH NetBlazer, AJA, COH, OXY, DISNEY, CLAREMONT, CADAM, SCAQMD, and HUGHES-CIT. TIME STARTED: THU. 09-24-92 10:25 TIME ENDED: THU. 09-24-92 10:40 TIME ELAPSED: 15 min. (New Router Installed) REASON: CERFnet Scheduled Maintenance TICKET #: 1339 SITE: MARKV SITES AFFECTED: MARKV TIME STARTED: THU. 09-24-92 16:33 TIME ENDED: FRI. 09-25-92 10:19 TIME STARTED: FRI. 09-25-92 13:24 TIME ENDED: FRI. 09-25-92 13:57 TIME STARTED: SAT. 09-26-92 16:58 TIME ENDED: SUN. 09-27-92 17:22 TIME ELAPSED: 1 day 18 hours 43 min. REASON: Site Scheduled Maintenance TICKET #: 1343 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: THU. 09-24-92 17:41 TIME ENDED: THU. 09-24-92 17:58 TIME ELAPSED: 17 min. (Worldcom Unknown) REASON: Unknown (Cisco Box didn't restart) TICKET #: 1345 SITE: HUGHES SITES AFFECTED: HUGHES TIME STARTED: THU. 09-24-92 19:21 TIME ENDED: FRI. 09-25-92 10:42 TIME ELAPSED: 15 hours 21 min. REASON: Site Activity (UCI Side) TICKET #: 1344 SITE: CERFnet SITES AFFECTED: ALL CERFnet Backbones, Sites, and peering with CIX, ESNET, and CSUnet. TIME STARTED: THU. 09-24-92 21:20 TIME ENDED: THU. 09-24-92 23:26 TIME ELAPSED: 2 hours 6 min. (MCI outage in San Diego) REASON: Link Failure TICKET #: 1340 SITE: IRVINE COMPILER CORPORATION SITES AFFECTED: IRVINE COMPILER CORPORATION TIME STARTED: FRI. 09-25-92 04:55 TIME ENDED: FRI. 09-25-92 11:00 TIME ELAPSED: 6 hours 5 min. REASON: Equipment Trouble TICKET #: 1347 SITE: McDonnell Douglas SITES AFFECTED: McDonnell Douglas TIME STARTED: FRI. 09-25-92 10:40 TIME ENDED: FRI. 09-25-92 14:49 TIME ELAPSED: 4 hours 9 min. REASON: Site Activity (Loopback Set) TICKET #: 1319 SITE: UCOP SITES AFFECTED: UCOP DIAL N' CERF, UCOP NETBLAZER, CIX, NETLABS, LSIL, INTEL, CISCO, APPLE AND FARALLON. TIME STARTED: FRI. 09-25-92 14:00 TIME ENDED: FRI. 09-25-92 14:08 TIME ELAPSED: 8 min. (Router Upgrade) REASON: CERFnet Scheduled Maintenance TICKET #: 1351 SITE: CALTECH-SDSC T1 SITES AFFECTED: CALTECH-SDSC T1 TIME STARTED: SAT. 09-26-92 09:17 TIME ENDED: SAT. 09-26-92 09:23 TIME ELAPSED: 6 min. (CERFnet) REASON: Site Activity TICKET #: 1352 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: SAT. 09-26-92 13:09 TIME ENDED: MON. 09-28-92 05:06 TIME ELAPSED: 1 day 15 hours 57 min. REASON: Ticket Still Open ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps 00.1% 16:00 SDSC/GA 10.000 mbps 00.1% 02:00 SDSC/CALTECH 1.544 mbps 16.0% 16:00 SDSC/UCI 1.544 mbps 06.8% 16:00 SDSC/UCLA 1.544 mbps 12.9% 16:00 SDSC/UCOP 1.544 mbps 06.1% 16:00 UCI/UCLA 1.544 mbps 01.8% 16:00 SDSC/UCR 512 kbps 03.1% 07:00 UCLA/UCSB 512 kbps 16.3% 16:00 CALTECH/HUGHES 1.544 mbps 02.0% 10:00 SDSC/AGI 1.544 mbps 00.2% 17:00 SDSC/BIOSYM 1.544 mbps 00.3% 14:00 SDSC/GD 1.544 mbps 02.1% 09:00 SDSC/SAIC 1.544 mbps 01.4% 16:00 SDSC/SEASPACE 1.544 mbps 03.1% 16:00 UCI/CSU CO(SWRL) 1.544 mbps 04.5% 16:00 UCI/MDC 1.544 mbps 02.0% 15:00 UCLA/GETTY 1.544 mbps 00.1% 16:00 UCOP/APPLE 1.544 mbps 01.2% 10:00 UCOP/CISCO 1.544 mbps 00.2% 19:00 UCR/LLUMC 1.544 mbps 00.5% 07:00 CALTECH/AJS 56 kbps 02.0% 13:00 CALTECH/CADAM 56 kbps 01.4% 09:00 CALTECH/CITY OF HOPE 56 kbps 01.0% 09:00 CALTECH/CLAREMONT 56 kbps 28.4% 16:00 CALTECH/DISNEY 56 kbps 08.1% 15:00 CALTECH/OXY 56 kbps 09.3% 13:00 CALTECH/SCAQMD 56 kbps 00.7% 16:00 SDSC/API 56 kbps 07.1% 20:00 SDSC/CICESE 56 kbps 05.1% 14:00 SDSC/KOREA 56 kbps 14.8% 21:00 SDSC/QUALCOMM 56 kbps 13.8% 22:00 SDSC/REDE-RIO 56 kbps 07.9% 10:00 SDSC/SCIH 56 kbps 03.9% 10:00 SDSC/SDG&E 56 kbps 04.1% 21:00 SDSC/USD 56 kbps 06.9% 09:00 SDSC/USIU 56 kbps 03.4% 20:00 UCI/BECKMAN 56 kbps 06.4% 16:00 UCI/CCCD 56 kbps 06.2% 13:00 UCI/CMD 56 kbps 00.8% 16:00 UCI/EMULEX 56 kbps 02.5% 16:00 UCI/FULLERTON 56 kbps 11.2% 23:00 UCI/HUGHES 56 kbps 23.2% 16:00 UCI/ICC 56 kbps 05.9% 21:00 UCI/MTI 56 kbps 05.3% 06:00 UCI/SPARTA 56 kbps 09.3% 06:00 UCI/UNOCAL 56 kbps 12.2% 16:00 UCLA/CRSS 56 kbps 00.3% 16:00 UCLA/DATAPRODUCTS 56 kbps 01.4% 13:00 UCLA/GTE 56 kbps 06.2% 16:00 UCLA/ISX 56 kbps 03.7% 17:00 UCLA/LITTON 56 kbps 00.3% 10:00 UCLA/PEPPERDINE 56 kbps 01.8% 12:00 UCLA/QUOTRON 56 kbps 87.5% 23:00 UCLA/SMC 56 kbps 02.3% 14:00 UCOP/FARALLON 56 kbps 08.8% 16:00 UCOP/INTEL 56 kbps 28.2% 10:00 UCOP/LSIL 56 kbps 08.8% 16:00 UCOP/NETLABS 56 kbps 12.9% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PDT on Sept. 28, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 03 days 12 hours 32 minutes [CERFnet Scheduled Maintenance- See Ticket #1300] SDSC LongBoard [134.24.99.254] Up: 104 days 08 hours 21 minutes SDSC Drzog [132.249.16.13] Up: 137 days 14 hours 24 minutes SDSC Hang10 [132.249.16.15] Up: 137 days 14 hours 24 minutes UCI [128.200.1.101] Up: 03 days 07 hours 47 minutes [CERFnet Site Activity] UCLA [128.97.130.10] Up: 175 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 02 days 10 hours 08 minutes [CERFnet Scheduled Maintenance- See Ticket #1319] UCR [134.24.108.105] Up: 78 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 78 days 09 hours 43 minutes APPLE [134.24.70.200] Up: 08 days 11 hours 19 minutes BIOSYM [134.24.57.200] Up: 108 days 07 hours 13 minutes CISCO Systems [134.24.54.200] Up: 17 days 11 hours 26 minutes CSUCO/SWRL [130.150.102.200] Up: 58 days 18 hours 22 minutes GA [134.24.20.10] Up: 07 days 00 hours 12 minutes GD [134.24.60.200] Up: 150 days 16 hours 18 minutes GETTY [134.24.235.200] Up: 45 days 07 hours 02 minutes HUGHES_CIT [134.24.103.200] Up: 07 days 11 hours 11 minutes LLUMC [134.24.208.200] Up: 57 days 13 hours 45 minutes MDC [134.24.65.200] Up: 37 days 08 hours 00 minutes SAIC [134.24.53.208] Up: 137 days 14 hours 10 minutes UCSB [134.24.107.107] Up: 03 days 10 hours 33 minutes [Unknown] CERF 56 AJS [134.24.225.101] Up: 47 days 13 hours 24 minutes API [134.24.224.200] Up: 94 days 13 hours 18 minutes BECKMAN [134.24.237.200] Up: 117 days 12 hours 10 minutes CADAM [134.24.229.200] Up: 30 days 06 hours 23 minutes CCCD [134.24.219.200] Up: 91 days 19 hours 14 minutes CICESE [134.24.227.200] Up: 131 days 09 hours 43 minutes CITY_OF_HOPE [134.24.233.200] Up: 00 days 16 hours 38 minutes [Equipment Trouble] CLAREMONT [134.24.206.109] Up: 05 days 07 hours 31 minutes [Power Outage] CMD [134.24.218.200] Up: 23 days 07 hours 29 minutes CRSS [134.24.232.200] Up: 53 days 12 hours 16 minutes DATAPRODUCTS [134.24.211.200] Up: 180 days 13 hours 01 minutes DISNEY [134.24.207.211] Up: 41 days 19 hours 57 minutes EMULEX [134.24.209.212] Up: 29 days 07 hours 37 minutes FARALLON [134.24.56.200] Up: 55 days 15 hours 51 minutes FULLERTON [134.24.214.217] Up: 91 days 17 hours 55 minutes GTE [134.24.212.200] Up: 196 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 02 days 13 hours 34 minutes [Site Acitivty - See Ticket #1345] INTEL [134.24.73.200] Up: 183 days 11 hours 34 minutes ICC [134.24.238.200] Up: 03 days 13 hours 15 minutes [Equipment Trouble - See Ticket #1340] LITTON [134.24.213.200] Up: 37 days 13 hours 29 minutes LSIL [134.24.72.200] Up: 145 days 08 hours 26 minutes MTI [134.24.216.100] Up: 33 days 08 hours 48 minutes NETLABS [134.24.71.200] Up: 60 days 09 hours 33 minutes OXY [134.24.205.108] Up: 03 days 12 hours 16 minutes [Unknown] PEPPERDINE [134.24.203.218] Up: 170 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 14 days 00 hours 14 minutes QUOTRON [134.24.230.202] Up: 35 days 06 hours 06 minutes REDE_RIO [134.24.112.200] Up: Still Down at the time. [Ticket Still Open - See Ticket #1352] SANTA MONICA [134.24.210.219] Up: 60 days 13 hours 40 minutes SCAQMD [134.24.234.200] Up: 05 days 07 hours 55 minutes [Equipment Trouble] SCI-HOR [134.24.109.205] Up: 138 days 06 hours 02 minutes SDG&E [134.24.226.200] Up: 117 days 13 hours 39 minutes SEASPACE [134.24.80.200] Up: 172 days 11 hours 26 minutes SERI/KOREA [134.24.223.200] Up: 16 days 05 hours 58 minutes SPARTA [134.24.215.200] Up: 181 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 206 days 01 hours 57 minutes USD [134.24.201.106] Up: 48 days 17 hours 00 minutes USIU [134.24.222.215] Up: 449 days 17 hours 07 minutes DIAL n' CERF Plus 14.4 CITOH [161.1.1.1] Up: 07 days 10 hours 09 minutes MARKV [192.122.251.6] Up: 00 days 14 hours 00 minutes [Site Scheduled Maintenance - See ticket #1339] PEREGRINE [192.72.253.97] Up: 12 days 13 hours 51 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 06 days 04 hours 58 minutes [Unknown] DNC-UCI [134.24.2.2] Up: 08 days 17 hours 12 minutes DNC-UCLA [134.24.3.2] Up: 04 days 12 hours 09 minutes [Equipment Trouble] DNC-CALTECH [134.24.4.2] Up: 03 days 13 hours 36 minutes [CERFnet Scheduled Maintenance- See Ticket #1300] DNC-UCOP [134.24.5.2] Up: 90 days 04 hours 29 minutes CIT-NETBLAZER [130.152.104.1] Up: 03 days 08 hours 35 minutes [CERFnet Scheduled Maintenance- See Ticket #1300] SDSC-NETBLAZER [192.102.249.25] Up: 03 days 04 hours 39 minutes [Unknown] UCI-NETBLAZER [134.24.92.2] Up: 08 days 17 hours 12 minutes UCLA-NETBLAZER [134.24.93.2] Up: 39 days 06 hours 54 minutes UCOP-NETBLAZER [134.24.250.2] Up: 187 days 23 hours 54 minutes - - - - - - - - - - - - - - - - - From mak Tue Sep 29 15:22:42 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA29784; Tue, 29 Sep 92 15:22:42 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA07120; Tue, 29 Sep 92 15:22:37 EDT Date: Tue, 29 Sep 92 15:22:37 EDT From: mak Message-Id: <9209291922.AA07120@fox.merit.edu> To: regional-techs Subject: ANS to CIX Interconnection To: Regional, Midlevel and Federal Network Operators From: Mark Knopper Merit/NSFNET Internet Engineering Subject: ANS to CIX Interconnection Plan Hi. Enclosed is a note from ANS describing their plan for the CIX to ANS network interconnection. Please let me know if you have questions or comments. Mark --------Forwarded Message To: Mark Knopper From: Jordan Becker Subject: ANS-CIX Interconnection Plan Mark, Here is a description of the routing and configuration plan for the CIX to ANS connection. Please forward this to regionals, midlevels, etc. as appropriate. Jordan ----------------------------------- During an upcoming T3 network router configuration update window, there will be about 94 new networks configured in the policy routing database to support the interconnection between ANS CO+RE and the CIX. A new ANSNET router, ENSS187 has been connected via a T1 link to the CIX router. This new ENSS (AS1957) peers via BGP with the CIX router (AS1280). Ethernet ------- T1 ------------ | --------| | cix |----------------| enss187 |-----| | | | ags+ | | | |-----| Cnss11| ------- ------------ | | | | |-------- 1280 BGP 1957 BGP 690 There will be initially 987 networks announced to the T3 system via the CIX (AS1280). Most of these networks have previously been configured in the policy routing database and are already announced to the NSFNET backbone service at other T3 ENSS nodes. About 94 of these networks are not already announced to the T3 system via other ENSS nodes and will be announced via AS1280 for the first time. All CIX networks announced via AS1280 will be considered as ANS CO+RE services (commercial restriction free). An ASCII text file listing of all ANS CO+RE announced network numbers, network names, AS numbers and available service provider information is maintained by ANS and may be retrieved via anonymous ftp from FTP.ANS.NET as /pub/info/co+re/core.nets or NIS.NSF.NET as /nsfnet/core.nets. Updates to this file will be made a few days prior to any configuration updates for the T3 backbone that involve the CIX (AS1280). One of the new networks originates in the former Soviet Union, and traffic between US Government sponsored networks and the former Soviet Union is prohibited at this time. Therefore accordingly, the ANSNET will not re-distribute or announce any routes to this network. Note that the 94 new networks will potentially be generating traffic which does not comply with the NSFNET Acceptable Use Policy. The new network numbers will be announced by the ANSNET to the peer networks that are both ANS CO+RE and CIX members. Those regionals or midlevels who are using default routing to point their traffic to the NSFNET backbone may wish to explicitly prohibit traffic between their users and these new networks if their internal policies require it. This may be done by either internal means (eg. informing users), or by filtering in routers operated by the midlevel network. Regionals may contact Merit to discuss other options for blocking this traffic if required. - - - - - - - - - - - - - - - - - From bjp@sura.net Tue Sep 29 17:46:28 1992 Received: from ragnarok.sura.net by merit.edu (5.65/1123-1.0) id AA06182; Tue, 29 Sep 92 17:46:28 -0400 From: bjp@sura.net Received: by ragnarok.sura.net for regional-techs@merit.edu (5.65b/(SURAnet $Revision: 1.29 $)) id AA09786; Tue, 29 Sep 92 17:46:24 -0400 Date: Tue, 29 Sep 92 17:46:24 -0400 Message-Id: <9209292146.AA09786@ragnarok.sura.net> To: mak, regional-techs Subject: ANS to CIX Interconnection > Note that the 94 new networks will potentially be generating > traffic which does not comply with the NSFNET Acceptable Use Policy. > The new network numbers will be announced by the ANSNET to the peer > networks that are both ANS CO+RE and CIX members. Those regionals or > midlevels who are using default routing to point their traffic to the > NSFNET backbone may wish to explicitly prohibit traffic between their > users and these new networks if their internal policies require it. > This may be done by either internal means (eg. informing users), or > by filtering in routers operated by the midlevel network. Regionals > may contact Merit to discuss other options for blocking this traffic > if required. Is there a reason why complete information is in the ENSS rather than the CNSS? My understanding of the agreement is that it is for the benefit of ANSnet and the CIX, so why should the regionals have to adjust the way they are set up? I'm not just saying this to be contrary (Honest). I am really interested in knowing why this method was chosen. As others have pointed out it move the burden of enforcing policy restriction to individual AS pairs. Comments? I am also interested in hearing what people pointing default at NSFnet plan to do? Brad Passwaters (301)(982-3214) SURAnet Operations bjp@sura.net - - - - - - - - - - - - - - - - - From rick@uunet.uu.net Tue Sep 29 23:19:35 1992 Received: from rodan.UU.NET by merit.edu (5.65/1123-1.0) id AA19289; Tue, 29 Sep 92 23:19:35 -0400 Received: by rodan.UU.NET (5.61/UUNET-mail-drop) id AA09352; Tue, 29 Sep 92 23:19:33 -0400 Date: Tue, 29 Sep 92 23:19:33 -0400 From: rick@uunet.uu.net (Rick Adams) Message-Id: <9209300319.AA09352@rodan.UU.NET> To: mak, regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: your article <"our.mail.ops".9209291922.AA07120@fox.merit.edu> News-Path: uunet!uunet!wendy-fate!nobody > One of the new networks originates in the former Soviet Union, > and traffic between US Government sponsored networks and the former > Soviet Union is prohibited at this time. Therefore accordingly, the > ANSNET will not re-distribute or announce any routes to this network. Well, the obvious question is what does this have to do with anything? The whole point of the CIX is to not have to screw around with outdated government policy. So, either ANS CO+RE isn't REALLY the commericial separate entity it claims to be or the above statement makes no sense and should be retracted. Which is it? ---rick - - - - - - - - - - - - - - - - - From piet@mcsun.EU.net Wed Sep 30 04:20:51 1992 Received: from mcsun.EU.net by merit.edu (5.65/1123-1.0) id AA28955; Wed, 30 Sep 92 04:20:51 -0400 Received: by mcsun.EU.net with SMTP id AA12460 (5.65b/CWI-2.177); Wed, 30 Sep 1992 09:20:47 +0100 Message-Id: <9209300820.AA12460@mcsun.EU.net> From: Piet.Beertema@mcsun.EU.net To: mak In-Reply-To: Your message of Tue, 29 Sep 92 15:22:37 EDT . <9209291922.AA07120@fox.merit.edu> Subject: Re: ANS to CIX Interconnection Cc: regional-techs Date: Wed, 30 Sep 1992 09:20:47 +0100 Sender: piet@mcsun.EU.net One of the new networks originates in the former Soviet Union, and traffic between US Government sponsored networks and the former Soviet Union is prohibited at this time. Therefore accordingly, the ANSNET will not re-distribute or announce any routes to this network. Announcing a route to a particular network is nothing more than saying "hey, look, you can reach this network via me". If the party receiving the announcement is not willing or allowed to communicate with that network, it can filter out the announcement; and it might even make a deal with the announcer to filter out the announcement. But that's quite something else than the presented general "we won't announce this network" approach. Piet - - - - - - - - - - - - - - - - - From mak Wed Sep 30 15:11:57 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA23015; Wed, 30 Sep 92 15:11:57 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA00861; Wed, 30 Sep 92 15:11:56 EDT From: mak Message-Id: <9209301911.AA00861@fox.merit.edu> To: rick@uunet.uu.net (Rick Adams) Cc: regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Tue, 29 Sep 92 23:19:33 EDT." <9209300319.AA09352@rodan.UU.NET> Date: Wed, 30 Sep 92 15:11:55 -0400 > From: rick@uunet.uu.net (Rick Adams) > To: mak@merit.edu, regional-techs@merit.edu > > > One of the new networks originates in the former Soviet Union, > > and traffic between US Government sponsored networks and the former > > Soviet Union is prohibited at this time. Therefore accordingly, the > > ANSNET will not re-distribute or announce any routes to this network. > > Well, the obvious question is what does this have to do with anything? > The whole point of the CIX is to not have to screw around with > outdated government policy. Rick, It is our understanding that Merit and ANS are prohibited from allowing any traffic to flow between the US and networks in the xSU. This is the law, not a policy however outdated. This is an unfortunate situation in my view, because a number of regionals have expressed interested in communicating with people and systems in Russia and other xSU countries. But until we hear that laws or their interpretation have been changed we will not be passing any traffic to or from this network. > > So, either ANS CO+RE isn't REALLY the commericial separate entity it > claims to be or the above statement makes no sense and should be retracted. > > Which is it? > > ---rick Again the xSU network announcement will not be passed to ANS CO+RE customers either so I guess this doesn't have to do with anything either.... Mark - - - - - - - - - - - - - - - - - From rick@uunet.uu.net Wed Sep 30 15:28:47 1992 Received: from rodan.UU.NET by merit.edu (5.65/1123-1.0) id AA23694; Wed, 30 Sep 92 15:28:47 -0400 Received: by rodan.UU.NET (5.61/UUNET-mail-drop) id AA09187; Wed, 30 Sep 92 15:28:45 -0400 From: rick@uunet.uu.net (Rick Adams) Message-Id: <9209301928.AA09187@rodan.UU.NET> Subject: Re: ANS to CIX Interconnection To: mak Date: Wed, 30 Sep 92 15:28:44 EDT Cc: rick@uunet.UU.NET, regional-techs In-Reply-To: <9209301911.AA00861@fox.merit.edu>; from "mak@merit.edu" at Sep 30, 92 3:11 pm X-Mailer: ELM [version 2.3 PL10] Neither I nor my attorneys are aware of any such law. Please quote the specific law or retract your claim. We bothered to reseach the issue. Did you? - - - - - - - - - - - - - - - - - From mak Wed Sep 30 16:05:59 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA25410; Wed, 30 Sep 92 16:05:59 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA00927; Wed, 30 Sep 92 16:05:56 EDT From: mak Message-Id: <9209302005.AA00927@fox.merit.edu> To: bjp@sura.net Cc: regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Tue, 29 Sep 92 17:46:24 EDT." <9209292146.AA09786@ragnarok.sura.net> Date: Wed, 30 Sep 92 16:05:55 -0400 > From: bjp@sura.net > To: mak@merit.edu, regional-techs@merit.edu > Is there a reason why complete information is in the ENSS rather than the CNS S? > My understanding of the agreement is that it is for the benefit of ANSnet > and the CIX, so why should the regionals have to adjust the way they are set > up? I'm not just saying this to be contrary (Honest). I am really > interested in knowing why this method was chosen. As others have pointed > out it move the burden of enforcing policy restriction to individual > AS pairs. Comments? Brad, You are correct that our interpretation of the AUP situation is that the burden is on the regionals/midlevels to enforce the policies as they apply to their institutions. This can be done by simply issuing a public statement to all users that people should only use the NSFNET for purposes of research and education. Or it can be done a bit more drastically by filtering out routes. The actual implementation of filters needs to be done in the regional's peer router when default routing is used. Does this help? > > I am also interested in hearing what people pointing default at NSFnet > plan to do? Some are not going to filter at all, some are going to implement static routes to "black holes", and others have yet to talk to us. > > Brad Passwaters (301)(982-3214) > SURAnet Operations bjp@sura.net > > --Mark - - - - - - - - - - - - - - - - - From bjp@sura.net Wed Sep 30 16:52:59 1992 Received: from ragnarok.sura.net by merit.edu (5.65/1123-1.0) id AA27380; Wed, 30 Sep 92 16:52:59 -0400 From: bjp@sura.net Received: by ragnarok.sura.net for regional-techs@merit.edu (5.65b/(SURAnet $Revision: 1.29 $)) id AA13640; Wed, 30 Sep 92 16:52:58 -0400 Date: Wed, 30 Sep 92 16:52:58 -0400 Message-Id: <9209302052.AA13640@ragnarok.sura.net> To: mak Subject: Re: ANS to CIX Interconnection Cc: regional-techs >>Is there a reason why complete information is in the ENSS rather than the >> CNSS? >> My understanding of the agreement is that it is for the benefit of ANSnet >> and the CIX, so why should the regionals have to adjust the way they are set >> up? I'm not just saying this to be contrary (Honest). I am really >> interested in knowing why this method was chosen. As others have pointed >> out it move the burden of enforcing policy restriction to individual >> AS pairs. Comments? > > Brad, > You are correct that our interpretation of the AUP situation is that > the burden is on the regionals/midlevels to enforce the policies as > they apply to their institutions. This can be done by simply issuing > a public statement to all users that people should only use the > NSFNET for purposes of research and education. Or it can be done > a bit more drastically by filtering out routes. The actual > implementation of filters needs to be done in the regional's > peer router when default routing is used. > Does this help? It does provide something of a clarification BUT I still have many questions. Does this mean that NSFnet will now take NACRs for any network and we no longer need to claim that people will abide by the AUP? This seems to me to be a radical change in policy. What is the reason for this shift? If people are still bound by the AUP and regionals can not submit NACRs for non AUP sites than it appears to me that we now have two classes of citizens on the Net. Those that can transmit any kind of packet and make the rest of the people bear the burden of preventing traffic we don't want and those of us who can't :-( I can understand that Merit does not want to enforce specific regional access policys *but* the regionals have been able to count on getting traffic that fits a specific AUP requirement from the NSFnet. This is no longer true. Can you tell me how this change benefits the regionals or even NSFnet? Can you tell me why you aren't keeping complete information in the CNSSs instead of the ENSSs? I can't see the problem you are solving by engaging in this activity. Brad Passwaters (301)(982-3214) SURAnet Operations bjp@sura.net - - - - - - - - - - - - - - - - - From medin@nsipo.nasa.gov Wed Sep 30 17:35:49 1992 Received: from cincsac.arc.nasa.gov by merit.edu (5.65/1123-1.0) id AA29056; Wed, 30 Sep 92 17:35:49 -0400 Received: Wed, 30 Sep 92 14:35:48 PDT from localhost.arc.nasa.gov by cincsac.arc.nasa.gov (4.1/1.5T) Message-Id: <9209302135.AA24051@cincsac.arc.nasa.gov> To: mak Cc: bjp@sura.net, regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Wed, 30 Sep 92 16:05:55 EDT." <9209302005.AA00927@fox.merit.edu> Date: Wed, 30 Sep 92 14:35:47 -0700 From: "Milo S. Medin" (NASA ARC NSI Office) Mark, the issue as I see it is that the current plan for implementing CIX connectivity is a change from the previous policy, and that you are now shifting responsibility for ensuring this filtering from your routers to the regionals, which for the regional, may involve significant administrative load, and which is the organization best capable of dealing with that administrative load. Further, there is also the issue that this plan does not appear to have been developed in a cooperative fashion with the regionals and other peers networks as a whole, as past shifts of functionality and responsibility between the backbone and regionals were done. I think there is not uniform consensus that the approach described is the best way of accomplishing the end goal, which also hasn't been described in a very explicit way, and is complicated by goals that NSF has and potentially other goals that ANS itself has. I'm not saying there is a conflict here, just that the precise goals and objectives do not appear to be well understood by all parties involved. This of course leads to confusion, which in turn will impede progress on any approach selected. It's hard to judge when you've got a good design if you don't understand what the requirements for the design are! Please feel free to correct me if I'm off base here. This is just my perception at this point, and I'm really not trying to throw stones, just trying to make sure evryone is working together on getting the job done right. Thanks, Milo - - - - - - - - - - - - - - - - - From mak Wed Sep 30 21:55:24 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA08547; Wed, 30 Sep 92 21:55:24 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA02933; Wed, 30 Sep 92 21:55:24 EDT From: mak Message-Id: <9210010155.AA02933@home.merit.edu> To: "Milo S. Medin" (NASA ARC NSI Office) Cc: bjp@sura.net, regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Wed, 30 Sep 92 14:35:47 PDT." <9209302135.AA24051@cincsac.arc.nasa.gov> Date: Wed, 30 Sep 92 21:55:23 -0400 Milo, You may be overestimating the problem. This is only an issue for regionals who are using default. If you are routing via explicit announcements from the backbone, it is a simple matter for us to filter out the AS 1957 announcement to exclude this traffic. Or alternatively you can do this in your peer router. For regionals using default, it isn't possible to prevent traffic from being sent from the regional to the CIX. One might think that it would be possible to prevent traffic in the other direction by filtering the announcement of that regional's networks by the backbone to the CIX. But this is also not possible since the CIX member networks are pointing default at the NSFNET backbone. So routing will be asymmetric but it will work. I can make available a postscript picture of the whole routing situation, if that would help. As far as whether this process has been open or not, first I should say that this is not really a Merit/NSFNET issue. It is an agreement between ANS (our subcontractor) and the CIX. As NSFNET service provider we are trying to facilitate this interconnection for the benefit of regionals. We were involved in the discussions of routing design (in fact Jessica Yu provided quite a lot of consulting with this) but the requirements were laid out by ANS and CIX. BARRnet and NEARnet were involved, as they are both ANS and CIX members and will make use of this interconnection. In any case we haven't made the change yet and I am certainly open to constructive (or even other types of) suggestions. We are currently working on verifying the integrity of the list of nets within AS 1957 and finalizing the confirmations with the current AS's for the database. The actual configuration date is at least a week or two away. Let me know if this helps or not. Mark > From: "Milo S. Medin" (NASA ARC NSI Office) > To: mak@merit.edu > CC: bjp@sura.net, regional-techs@merit.edu > > > > Mark, the issue as I see it is that the current plan for implementing > CIX connectivity is a change from the previous policy, and that you are > now shifting responsibility for ensuring this filtering from your routers > to the regionals, which for the regional, may involve significant > administrative load, and which is the organization best capable of dealing > with that administrative load. > > Further, there is also the issue that this plan does not appear to have been > developed in a cooperative fashion with the regionals and other peers network s > as a whole, as past shifts of functionality and responsibility between > the backbone and regionals were done. > > I think there is not uniform consensus that the approach described is the > best way of accomplishing the end goal, which also hasn't been described > in a very explicit way, and is complicated by goals that NSF has and > potentially other goals that ANS itself has. I'm not saying there is a confl ict > here, just that the precise goals and objectives do not appear to be well > understood by all parties involved. This of course leads to confusion, which > in turn will impede progress on any approach selected. It's hard to judge > when you've got a good design if you don't understand what the requirements > for the design are! > > Please feel free to correct me if I'm off base here. This is just my > perception at this point, and I'm really not trying to throw stones, just > trying to make sure evryone is working together on getting the job done > right. > > Thanks, > Milo > > - - - - - - - - - - - - - - - - - From mak Wed Sep 30 22:18:04 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA09374; Wed, 30 Sep 92 22:18:04 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA03218; Wed, 30 Sep 92 22:18:04 EDT From: mak Message-Id: <9210010218.AA03218@home.merit.edu> To: rick@uunet.uu.net (Rick Adams) Cc: regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Wed, 30 Sep 92 15:28:44 EDT." <9209301928.AA09187@rodan.UU.NET> Date: Wed, 30 Sep 92 22:18:03 -0400 > From: rick@uunet.uu.net (Rick Adams) > To: mak@merit.edu > CC: rick@uunet.UU.NET, regional-techs@merit.edu > > > > Neither I nor my attorneys are aware of any such law. > > Please quote the specific law or retract your claim. > > We bothered to reseach the issue. Did you? > Rick, We are looking into it, but feel that we need explicit confirmation by an attorney or government official before we can allow this traffic. NSF has explicitly instructed us not to allow traffic between some xSU countries and federally-sponsored networks. Other types of networks may actually be allowed as you say but we are taking the conservative approach. Mark - - - - - - - - - - - - - - - - - From medin@nsipo.nasa.gov Wed Sep 30 22:24:48 1992 Received: from cincsac.arc.nasa.gov by merit.edu (5.65/1123-1.0) id AA09706; Wed, 30 Sep 92 22:24:48 -0400 Received: Wed, 30 Sep 92 19:24:48 PDT from localhost.arc.nasa.gov by cincsac.arc.nasa.gov (4.1/1.5T) Message-Id: <9210010224.AA24578@cincsac.arc.nasa.gov> To: mak Cc: bjp@sura.net, regional-techs Subject: Re: ANS to CIX Interconnection In-Reply-To: Your message of "Wed, 30 Sep 92 21:55:23 EDT." <9210010155.AA02933@home.merit.edu> Date: Wed, 30 Sep 92 19:24:48 -0700 From: "Milo S. Medin" (NASA ARC NSI Office) Mark, the main problem for us is if you don't filter out the 97 some odd nets out of the AS 1957 routes you send us. If you are willing to do that, then we still don't have any new administrative load, and from NSI's point of view, we're happy. Did I read your statement right? If so, we'd definitely like to take you up on this offer! You say: "For regionals using default, it isn't possible to prevent traffic from being sent from the regional to the CIX." This is true, given a certain set of assumptions, such as that the ENSS and CNSS's having the same set of routes. If the ENSS did not install the 97 nets etc, in it's routing table, then since it didn't have default, it would generate net unreachable messages and the traffic wouldn't flow. Given that I thought this kind of thing was possible given your implementation and use of IBGP and such, then this shouldn't be that hard. Again, please correct me if I'm offbase here. You certainly could argue that this sort of thing is necessary for ANS to serve it's member network's needs for CO+RE service. The real question is whether or not it is possible to do this and not increase the administrative load of non-participating regionals under your NSFNET agreement. The key to resolving the latter question is how much flexibility you guys have with the import and export of routing information into the routing tables of the ENSS's, and to be honest, I have only peripheral knowledge of the current way routes are sent around inside the T3 system (not because you guys are being secretive, just that I haven't been following this very closely due to work load problems). Thanks, Milo - - - - - - - - - - - - - - - - - From rick@uunet.uu.net Wed Sep 30 23:01:08 1992 Received: from rodan.UU.NET by merit.edu (5.65/1123-1.0) id AA11089; Wed, 30 Sep 92 23:01:08 -0400 Received: by rodan.UU.NET (5.61/UUNET-mail-drop) id AA01412; Wed, 30 Sep 92 23:01:07 -0400 From: rick@uunet.uu.net (Rick Adams) Message-Id: <9210010301.AA01412@rodan.UU.NET> Subject: Re: ANS to CIX Interconnection To: mak Date: Wed, 30 Sep 92 23:01:06 EDT Cc: rick@uunet.UU.NET, regional-techs In-Reply-To: <9210010218.AA03218@home.merit.edu>; from "mak@merit.edu" at Sep 30, 92 10:18 pm X-Mailer: ELM [version 2.3 PL10] So what you're saying then is that you are not an independant entity and are require to follow federal policy. NSF has a policy against it. that has nothing to do with legality. NSF also has a policy against carrying commercial traffic? Did you adopt that? You are not being conservative. You're way into paranoid. So, to sum up, ANS is discriminating against users of a network because of their natural origin and there is no basis in law to support this position. Pretty xenophobic for a group that claims to be an international provider. - - - - - - - - - - - - - - - - -