- Test - lists.nanog.org

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 24 Feb '92

24 Feb '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: no additions. Total NSFNET T1 announced networks: 4733 T3 Network: 125 T1 configured CERFnet (AS 1740) networks (not listed here) have been added to the T3 database. Total NSFNET T3 announced networks: 2217 The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - 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(a)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 nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

3 3

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 21 Feb '92

21 Feb '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 192.101.197 ECAN 590 European Center for Advanced Networking (EBM ECAN), Tiergartenstr. 8, D-6900 Heidelberg, GERMANY 155.225 CITNET-B 297 372 The Citadel, Computer Center, Charleston, SC 29409, USA 192.147.26 BCM-TEST-B 750 756 Baylor College of Medicine, Texas Medical Center, Houston, TX 77030, USA 192.138.24 AMEDD-HCSSA 184 164 Health Care Systems Support Activity,2455 NE 410, Ste 150, San Antonio, TX 78217, USA 192.93.238 FNET-CICBX2 590 Centre Interuniversitaire de Calcul de Bordeaux, 351, cours de la Liberation, 33405 Talence CEDEX, FRANCE 192.93.13 FNET-CEMES 1238 CEMES-LOE, BP 4347, F-31055 Toulouse CEDEX, FRANCE 192.86.167 OMPT 1238 Observatoire Midi pyrenees, 14 avenue Edouard Belin, 31400 Toulouse, FRANCE 192.84.220 HQ-NET 750 756 HQ-Interaktive Mediensysteme, Schusterinsel 7, D-7858 Weil am Rhein, GERMANY 192.70.193 GEOWASH-NET1 209 210 Colorado SuperNet, Inc., Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA 192.70.112 FNET-CNET194 1238 FNET, Institut National de Recherche en Informatique et Automatique, Domaine de Voluceau, Rocquencourt, BP 105, F-78153 Le Chesnay CEDEX, FRANCE 192.65.174 TJHSST 86 279 Thomas Jefferson High School for Science and Technology, 6560 Braddock Road,, Alexandria, VA 22312, USA 192.54.152 FNET-INSA-ROUEN 590 I.N.S.A. (Institut National Des Sciences Appliquees) de Rouen, BP 8; F-76131 Mont Saint Aignan, FRANCE 192.16.239 DRE-NET5 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.238 DRE-NET4 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.237 DRE-NET3 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.236 DRE-NET2 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.235 DRE-NET1 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.234 DRE-DOC1 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.16.233 TCCCS-NET1 174 750 Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA 192.12.239 CU-ACS 209 210 University of Colorado, Computing and Network Services, 3645 Marine St., Boulder, CO 80309-0455, USA 158.80 BAKER 233 177 G-1050 West Bristol Road, Baker College, USA 157.229 SSH-NET 1206 204 Shadyside Hospital, 5230 Centre Avenue, Pittsburgh, PA 15232, USA 157.159 INT-EVRY 1238 I.N.T.= Institut National des Telecoms, I.N.T. Centre de Calcul, 9 rue Charles Fourier, 91011 EVRY FRANCE 157.138 UNIVENET 590 Universita' degli Studi - Venezia, Dorsoduro 3861 30123 VENEZIA ITALY 155.2 ANSER 184 164 ANSER Information Technology Division, Arlington, VA 22202, USA 153.92 CCC-NET 750 756 Conware Computer Consulting, Killisfeldstrasse 64, W-7500 Karlsruhe 41, GERMANY 153.42 MESSIAH-NET 1206 204 Messiah College, Grantham, PA 17027, USA 150.189 VZ-NET5 1250 Consejo Nacional de Inverstiaciones Cientificas y Technoligia (CONICIT) , Officina de Informatica, Apartado 70617, Caracas, VENEZUELA 150.188 VZ-NET4 1250 Consejo Nacional de Inverstiaciones Cientificas y Technoligia (CONICIT), Officina de Informatica, Apartado 70617, Caracas, VENEZUELA 150.187 VZ-NET3 1250 Consejo Nacional de Inverstiaciones Cientificas y Technoligia (CONICIT), Officina de Informatica, Apartado 70617, Caracas, VENEZUELA 150.186 VZ-NET2 1250 Consejo Nacional de Inverstiaciones Cientificas y Technoligia (CONICIT), Officina de Informatica, Apartado 70617, Caracas, VENEZUELA 150.185 VZ-NET1 1250 Consejo Nacional de Inverstiaciones Cientificas y Technoligia (CONICIT), Officina de Informatica, Apartado 70617, Caracas, VENEZUELA 150.104 SBACIP 86 279 School Board of Alachua County, Information Resources, 620 East University Avenue, Gainesville, FL 36201-5498, USA 150.100 SINET1 1240 National Center for Science Information System, JAPAN 150.99 SINET 1240 National Center for Science Information System, JAPAN 149.236 BAM-LAN 750 756 Bruker Analytische Messtechnik GmbH, Am Silberstreifen, D-W-7512 Rheinstetten 4, GERMANY 147.250 ENSTA 1238 701 Ecole Nationale Superieure de Techniques Avancees - ENSTA, 32 Boulevard Victor, 75015 Paris, FRANCE 147.174 SELUNET 86 279 Southeastern Louisiana University, P.O. Box 430, Hammond, LA 70402, USA 144.118 DREXELSUBNET 1206 204 Telecommunications & Networking Group, Office of Computing Services, Drexel University, Philadelphia, PA 19104-2884, USA 141.44 TUMD 750 756 Technische Universitaet Magdeburg, Universitaetsrechenzent rum, Universitaetsplatz 2, PSF 4120, D-O-3010 Magdeburg, GERMANY 137.201 MICRON 210 209 Micron Technology, 2805 E. Columbia Road, Boise, ID 83706, USA 137.9 ANDREWS-NET1 184 164 Andrews Air Force Base, Camp Springs, MD 20331, USA Total NSFNET T1 announced networks: 4733 T1 special additions: AS# NSS Gate IP Protocol Description ---- ---- ------------ ---------- ------------- 1740 6 132.249.16.13 EGP cisco systems 1740 6 132.249.16.15 EGP cisco systems T3 Network: Network IP: 141.44 Network Name: TUMD Location: Technische Universitaet Magdeburg, Universitaetsrechenzentrum, Universitaetsplatz 2, PSF 4120, D-O-3010 Magdeburg, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 144.118 Network Name: DREXELSUBNET Location: Telecommunications & Networking Group, Office of Computing Services, Drexel University, Philadelphia, PA 19104-2884, USA Country Code: US 1:1206 PSCNET Network IP: 147.168 Network Name: NAVSWC-NET Location: Naval Surface Warfare Center, White Oak Laboratory, Silver Spring, MD 20903-5000, USA Country Code: US 1:86 ENSS 136, College Park 2:279 Georgia Tech Network IP: 147.174 Network Name: SELUNET Location: Southeastern Louisiana University, P.O. Box 430, Hammond, LA 70402, USA Country Code: US 1:86 ENSS 136, College Park 2:279 Georgia Tech Network IP: 149.236 Network Name: BAM-LAN Location: Bruker Analytische Messtechnik GmbH, Am Silberstreifen, D-W-7512 Rheinstetten 4, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 150.104 Network Name: SBACIP Location: School Board of Alachua County, Information Resources, 620 East University Avenue, Gainesville, FL 36201-5498, USA Country Code: US 1:86 ENSS 136, College Park 2:279 Georgia Tech Network IP: 153.42 Network Name: MESSIAH-NET Location: Messiah College, Grantham, PA 17027, USA Country Code: US 1:1206 PSCNET Network IP: 153.92 Network Name: CCC-NET Location: Conware Computer Consulting, Killisfeldstrasse 64, W-7500 Karlsruhe 41, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 157.229 Network Name: SSH-NET Location: Shadyside Hospital, 5230 Centre Avenue, Pittsburgh, PA 15232, USA Country Code: US 1:1206 PSCNET Network IP: 158.80 Network Name: BAKER Location: G-1050 West Bristol Road, Baker College, USA Country Code: US 1:237 MERIT network Network IP: 192.16.233 Network Name: TCCCS-NET1 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.234 Network Name: DRE-DOC1 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.235 Network Name: DRE-NET1 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.236 Network Name: DRE-NET2 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.237 Network Name: DRE-NET3 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.238 Network Name: DRE-NET4 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.16.239 Network Name: DRE-NET5 Location: Defense Research Establishment Ottawa, Shirley Bay, Ottawa, Ontario, CANADA Country Code: CA 1:174 NYSERNET Regional Network / PSI Network IP: 192.58.225 Network Name: NCRDS3 Location: U.S. Geological Survey, 809 National Center, Reston, VA 22092 Country Code: US 1:201 BARRNet Network IP: 192.65.174 Network Name: TJHSST Location: Thomas Jefferson High School for Science and Technology, 6560 Braddock Road, Alexandria, VA 22312, USA Country Code: US 1:86 ENSS 136, College Park 2:279 Georgia Tech Network IP: 192.84.220 Network Name: HQ-NET Location: HQ-Interaktive Mediensysteme, Schusterinsel 7, D-7858 Weil am Rhein, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.147.26 Network Name: BCM-TEST-B Location: Baylor College of Medicine, Texas Medical Center, Houston, TX 77030, USA Country Code: US 1:1700 Rice University, Houston, TX Total NSFNET T3 announced networks: 2090 T3 special additions: AS Number: 1740 AS Notes: CERFnet AS Country Code: US Gate: 132.249.32.13 - longboard.sdsc.edu ENSS 135 - San Diego The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - 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(a)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 nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ************** -B. Sue Blair Merit Network Operations

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 20 Feb '92

20 Feb '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: no additions. Total NSFNET T1 announced networks: 4691 T3 Network: 646 T1 configured NYSERNET Regional Network / PSI (AS 174) networks (not listed here) have been added to the T3 database. 47 T1 configured Georgia Tech (AS 279) networks (not listed here) have been added to the T3 database. Total NSFNET T3 announced networks: 2070 The following T3 gate has been added: AS Number: 279 AS Notes: Georgia Tech AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.138 - Georgia Tech Georgia Tech Gate: 192.76.181.1 - GIT1 Georgia Tech, 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. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - 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(a)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 nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

1 0

CSU/DSU selection
by Vince Fuller 20 Feb '92

20 Feb '92

We at BARRNet are considering re-evaluating the T1 CSU/DSUs that we use in an effort to find a more cost-effective solution to connecting small sites which want T1 connectivity (we currently use Cylinks, which might be thought of as the "cadillac" of CSU/DSUs - many features, kinda pricey...) To this end, I'd appreciate hearing about experience that other networks have had with T1 CSU/DSUs made by various manufacturers. The following evaluation criteria are of particular interest: - Cost per unit (list price, price we can expect to get, discount plans offered, if any) - Does manufacuturer offer multi-unit "nest" (and if so, cost) - Framing options (D4 vs. ESF, etc.) - Line encoding options (AMI vs. B8ZS, etc.) - Maximum effective bandwidth (1344 vs. 1536); if full-T1, what scheme is used to guarentee one's density requirement is met Responses to vaf(a)stanford.edu - I'll summarize if there is interest. --Vince

1 0

OSI Survey for Regionals attached to the Internet
by skh 19 Feb '92

19 Feb '92

Below is a survey on OSI usage in the Internet. Could you take a moment and fill out this survey? It may look long, but it should only take a few minutes to fill out. Your answers will help the people working on OSI in the Internet plan our next work. Thank you for your help! Please send it in as soon as possible. We'd like to get all responses back within a week. Thank-you, Susan Hares IETF NOOP chair Survey on OSI in Your Network Purpose for Survey: The IETF Network OSI Operational Working Group wants to find out details on OSI use their is in the Internet. The results of the survey will be published as an FYI document for the Internet. Any people answering the Survey will be sent electronic copies of the FYI document on the results of the survey. As people beginning to use OSI on the Internet, the will be able to refer to this document to find out who supports the ISO CLNP layer across the Internet. Timeframe for Survey: Please return this survey by February 27th, 1992. Results will be published as a paper for the NOOP group by March 7th, 1992. Send responses to skh(a)merit.edu. Introduction to the Survey: Questions 1-6 are for those who route Connection Network Layer Packets (CLNP ISO 8473) or DECNET Phase 5 traffic on their network. Questions 7-8 are for those who do not yet route CLNP or DECNET Phase 5. 1.) Do you support the routing of Connection Network Layer Protocol (CLNP (ISO 8473)) packets on your network? If so, 1.1) What number of routers do you have in your network? How many of these routers pass CLNP packets? 1.2) What router vendors do you use in your network? What router vendors do you use in the routers that are passing CLNP packets? 1.3) What type of intra-domain routing do you do within your network? IS-IS? Cisco IGRP based OSI? static? 1.4) What type of inter-domain routing do you do? Cisco poor-man's Inter-domain routing? static? 1.5) Would you be interested in the new ISO Inter-Domain Routing Protocol (IDRP (ISO CD 10747)) when it becomes available? 1.6) Do you consider the OSI service to be: Production - guaranteed delivery and high level of service, Experimental - guaranteed delivery, but service not at highest level Prototype - A first offerings of CLNP which is limited to a few sites, or Pilot - For demonstrations and Pilot projects only? Please select the category nearest to your service. You may include other comments to further qualify this service level. 1.7) If you are running both IP and CLNP, What do you consider your IP service - Production, Experimental, Prototype, or Pilot? 1.8) What amount of traffic do you pass per day, per week and per month? 2.) Are you now routing DECNET Phase 5 traffic on your system? If you are routing DECNET Phase 5: a.) What type of routers are you using? (manufacturer and model? b.) How many routers do you have? c.) What type of hosts are sending traffic? d.) How many DECNET Phase 5 hosts do you have? 3.) Do you currently attach one or more OSI vendor company to your network? Do any of these companies send OSI traffic across the network? If so, 3.1) How many OSI companies are attached to your network? 3.2) How many of these OSI companies send application data regularly? 3.3) What are the companies attached to your network? 3.4) What applications are these companies using? It would be helpful to list the applications by company if that is possible. 3.5) Would any of these companies be interested in "Pilot" projects to try exchanging OSI applications with those people on the Internet. 4.) Do you support OSI applications at your network site? If so, 4.1) What applications do you support? Do you support: X.500 X.400 FTAM VT Xwindows SQL based applications CMIP (please answer yes or no to each applications) others - please list with company 4.2) For each of the applications you answered yes to above please indicate: a.) equipment the application runs on b.) does it run over CLNP/TP4 stack or TCP/IP stack c.) what vendor supplies the software d.) any comments on how easy it is to use e.) Is your application based on ISODE? If so what version of ISODE? 4.3) Are you a part of a Pilot Project or testing group for this application? 4.4) Would you be willing to be a part of a Pilot Project or testing group for this application? 4.5) Do you have a set of routers or hosts which could form a "test bed" at your site? 4.6) Would you be willing to allow this test bed (either a short term or long term basis) to join with other test beds at other networks to test out new software in the Internet? 4.6) Would you be willing to have a "test bed" at your site if additional funding for this was available? Would you be willing on either a short term or long term basis to allow 5.) Do you have any of the following network tools on your routers? a.) OSI ping (or echo function) b.) OSI traceroute c.) OSI table dump What routers have these functions? How would you rate the User Interface to these network tools - poor, fair, good, or excellent? 6.) Do you have any of the following network tools on your hosts? a.) OSI ping (or echo function) b.) OSI traceroute c.) OSI table dump What hosts have these functions? How would you rate the User Interface to these network tools - poor, fair, good, or excellent? 7.) If you do not support switching CLNP packets today, a.) Will you need to route DECNET Phase 5 in the future? b.) Will you route CLNP packets if you had clients that required OSI service? c.) Will you route CLNP packets only when IS-IS was supported on all your routers? (please indicate what types of routers you use in your network) d.) Will you need network tools (that supported an osi ping, osi traceroute, and osi routing table dump) to support CLNP in your network? e.) Will you require both clients and IS-IS supported on all your routers (b and c above) f.) Will you require that you have OSI clients, IS-IS on all your routers, and OSI network tools (b, c and d above) Please answer yes or no to items a thru e. Additional comments are also welcome. 8.) If you do not currently use an OSI application at your site, please answer the following: 8.1) Would you be interested in X.500? In X.500 over TCP/IP? In X.500 over CLNP? 8.2) Would you be interested in X.400? in X.400 over TCP/IP? In X.400 over CLNP? 8.3) Would you be interested in FTAM over ISO Transport Class 4 (TP4) and CLNP? 8.4) Would you be interested in FTAM over ISO transport Class 0 (TP0) and X.25? 8.5) Would be interested in VT over TP and CLNP? 8.6) Would you be interested in trying out TCP over CLNP? 8.7) Would you be interested in trying out X-windows over CLNP?

1 0

Re: The CIX and the NSFNET regionals - a dilemma
by Allen Cole 19 Feb '92

19 Feb '92

Marty writes ------------ >We see similiar problems, functional capability for interactive >applications like telnet is MUCH better through the CIX than through >the NSFNet. When "SaltLakeCity" has its normal problems (we've seen >about a dozen in January, and we're not looking really) then it goes >through the roof. An update. There have been circuit problem for a couple of the circuits into Salt Lake. After a 24 hour test period the problem has been isolated to the tail circuits at Salt Lake. Fortunately a new fiber local loop has been recently installed here. That will probably make a difference. cole(a)cc.utah.edu

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 18 Feb '92

18 Feb '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 129.11 LEEDS 274 60 Leeds University, Leeds LS2 9JT, UNITED KINGDOM 133.13 UNIV-RYUKYU 372 297 The University of the Ryukyus, JAPAN 133.16 KYOUTOINSTECH 372 297 Kyouto Institute of Technology, JAPAN 133.22 KIDNET 372 297 Kyushu Institute of Design, JAPAN 133.35 NINES 372 297 Information Processing Center Niigara University, JAPAN 133.37 OITA-UNIV 372 297 Oita University, JAPAN 133.42 WAKAYAMA-U 372 297 Wakayama University, JAPAN 133.68 NITECH 372 297 Nagoya Institute of Technology, JAPAN 133.85 TOYOTA-CTNET 372 297 Toyota College of Technology, JAPAN 133.94 KURUMEINET 372 297 Kurme Institute of Technology, JAPAN 133.95 KUMAMOTO-UNI 372 297 Kumamoto University Computer Center, JAPAN 133.107 HSK-NET 372 297 Hitachi Software Engineering Co., LTD., JAPAN 133.112 SOUM-NETR-1 372 297 SOUM Corporation, JAPAN 133.123 FORETUNE-LAN 372 297 Foretune Co., Ltd., JAPAN 133.130 TRAD-NET 372 297 Trad Techologies Corp., JAPAN 133.186 JAPANB-INET10C 372 297 Japan Inet, JAPAN 134.122 PHOENIX 560 281 Phoenix Technologies, Ltd., 38 Sidney Street, Cambridge, MA 02139 150.12 HIT-NETWORK 372 297 Himeji Institute of Technology, JAPAN 150.61 CANON-NET 372 297 CANON INC., JAPAN 150.65 FRONTNET 372 297 Japan Advanced Institute of Science and Technology, JAPAN 150.69 KIT 372 297 Kyushu Institute of Technology, JAPAN 150.88 HITACHI-CABL 372 297 Hitachi Cable, LTD., JAPAN 192.50.101 KNCTNET 372 297 Kumamoto National College of Technology, JAPAN 192.133.16 CSCNET 93 Chadron State College, Computer Center, 1000 S Main St., Chadron NE 69337 Total NSFNET T1 announced networks: 4691 T3 Network: Network IP: 134.122 Network Name: PHOENIX Location: Phoenix Technologies, Ltd., 38 Sidney Street, Cambridge, MA 02139 Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Total NSFNET T3 announced networks: 1377 The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - 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(a)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 nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

1 0

CERT Advisory - Internet Intruder Activity
by CERT Advisory 17 Feb '92

17 Feb '92

=========================================================================== CA-92:03 CERT Advisory February 17, 1992 Internet Intruder Activity --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information regarding a significant intrusion incident on the Internet. Systems administrators should be aware that many systems on the Internet have been compromised due to this activity. To identify whether your systems have been affected by the activity we recommend that all system administrators check for the signs of intrusion detailed in this advisory. This advisory describes the activities that have been identified as part of this particular incident. This does not address the possibility that systems may have been compromised due to other, unrelated intrusion activity. --------------------------------------------------------------------------- I. Description The intruders gained initial access to a host by discovering a password for a user account on the system. They then attempted to become root on the compromised system. II. Impact Having gained root access on a system, the intruders installed trojan binaries that captured account information for both local and remote systems. They also installed set-uid root shells to be used for easy root access. III. Solution A. Check your systems for signs of intrusion due to this incident. 1. Check the su, ftpd, and ftp binaries (for example, "/bin/su", "/usr/ucb/ftp" and "/usr/etc/in.ftpd" on Sun systems) against copies from distribution media. 2. Check for the presence of any of the following files: "/usr/etc/..." (dot dot dot), "/var/crash/..." (dot dot dot), "/usr/etc/.getwd", "/var/crash/.getwd", or "/usr/kvw/..." (dot dot dot). 3. Check for the presence of "+" in the "/etc/hosts.equiv" file. 4. Check the home directory for each entry in the "/etc/passwd" file for the presence of a ".rhosts" file containing "+ +" (plus space plus). 5. Search the system for the presence of the following set-uid root files: "wtrunc" and ".a". 6. Check for the presence of the set-uid root file "/usr/lib/lpx". B. Take the following steps to secure your systems. 1. Save copies of the identified files to removable media. 2. Replace any modified binaries with copies from distribution media. 3. Remove the "+" entry from the "/etc/hosts.equiv" file and the "+ +" (plus space plus) entry from any ".rhosts" files. 4. Remove any of the set-uid root files that you find, which are mentioned in A5 or A6 above. 5. Change every password on the system. 6. Inspect the files mentioned in A2 above for references to other hosts. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: cert(a)cert.sei.cmu.edu Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) 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.sei.cmu.edu (192.88.209.5).

1 0

CERFnet Weekly Report for the week of Monday, February 10, 1992.
by Donna Bigley 17 Feb '92

17 Feb '92

############################################################################### This is the CERFnet weekly activity report for the period of Monday, February 10th through Sunday, February 16th, 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: 16-february-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab(a)cerf.net or help(a)cerf.net ****************************************************************************** NETWORK OUTAGES: SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: SAT. 2-8-92 01:19 TIME ENDED: TIME ELAPSED: (Intermittent Outages) REASON: Telco persuing problems in Korea. SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: MON. 2-10-92 11:14 TIME ENDED: TUE. 2-11-92 06:32 TIME ELAPSED: 19 hours 18 min. REASON: Power Outage SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: TUE. 2-11-92 07:29 TIME ENDED: TUE. 2-11-92 07:51 TIME ELAPSED: 22 min. REASON: Unknown SITE: GA SITES AFFECTED: GA TIME STARTED: TUE. 2-11-92 07:31 TIME ENDED: TUE. 2-11-92 07:50 TIME ELAPSED: 19 min. REASON: CERFnet/Site Scheduled Maintenance SITE: CIT SITES AFFECTED: CIT Dial n' CERF, OXY, Disney, Claremont, Cadam, SCAQMD and Los Nettos. TIME STARTED: WED. 2-12-92 08:44 TIME ENDED: WED. 2-12-92 09:06 TIME ELAPSED: 22 min. REASON: CERFnet Scheduled Maintenance SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: WED. 2-12-92 20:06 TIME ENDED: THU. 2-13-92 00:38 TIME ELAPSED: 4 hours 32 min. REASON: Unknown SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: THU. 2-13-92 04:24 TIME ENDED: THU. 2-13-92 08:23 TIME ELAPSED: 3 hours 59 min. REASON: Power Outage SITE: AGI SITES AFFECTED: AGI TIME STARTED: THU. 2-13-92 08:51 TIME ENDED: THU. 2-13-92 10:19 TIME STARTED: THU. 2-13-92 10:43 TIME ENDED: THU. 2-13-92 11:08 TIME ELAPSED: 1 hour 53 min. REASON: Power Outage SITE: GA SITES AFFECTED: GA TIME STARTED: THU. 2-13-92 04:31 TIME ENDED: THU. 2-13-92 07:30 TIME ELAPSED: 2 hours 59 min. REASON: Power Outage SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: THU. 2-13-92 23:55 TIME ENDED: FRI. 2-14-92 16:46 TIME ELAPSED: 16 hours 51 min. (Intermittent Access) REASON: Link Failure SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: FRI. 2-14-92 06:34 TIME ENDED: FRI. 2-14-92 10:29 TIME ELAPSED: 3 hours 55 min. REASON: Link Failure SITE: McDonnell Douglas SITES AFFECTED: McDonnell Douglas TIME STARTED: SAT. 2-15-92 22:32 TIME ENDED: SAT. 2-15-92 22:50 TIME ELAPSED: 18 min. REASON: Unknown SITE: McDonnell Douglas SITES AFFECTED: McDonnell Douglas TIME STARTED: SUN. 2-16-92 02:46 TIME ENDED: SUN. 2-16-92 06:25 TIME STARTED: SUN. 2-16-92 11:27 TIME ENDED: MON. 2-17-92 06:29 TIME ELAPSED: 23 hours 21 min. (Intermittent Access) REASON: Unknown ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK * Capacities for sites off of Caltech are unavailable. LINK SPEED CAPACITY PEAK HOUR (PDT) SDSC/CALTECH 1.544 mbps 12.1% 15:00 SDSC/UCI 1.544 mbps 05.0% 15:00 SDSC/UCLA 1.544 mbps 05.1% 14:00 SDSC/UCOP 1.544 mbps 04.5% 10:00 SDSC/UCR 1.544 mbps 00.7% 10:00 UCI/UCLA 1.544 mbps 00.8% 02:00 SDSC/UCR 512 kbps 02.1% 10:00 UCLA/UCSB 512 kbps 05.7% 16:00 SDSC/AGI 1.544 mbps 00.1% 20:00 SDSC/BIOSYM 1.544 mbps 00.1% 16:00 SDSC/GA 1.544 mbps 00.1% 08:00 SDSC/GD 1.544 mbps 01.9% 11:00 SDSC/SAIC 1.544 mbps 01.1% 14:00 SDSC/SDSU 1.544 mbps 01.9% 10:00 UCI/CSU CO(SWRL) 1.544 mbps 02.1% 10:00 UCOP/APPLE 1.544 mbps 00.7% 12:00 UCOP/CISCO 1.544 mbps 00.2% 15:00 UCR/LLUMC 1.544 mbps 00.01% 14:00 SDSC/AJS 56 kbps 01.5% 08:00 SDSC/KOREA 56 kbps 10.2% 18:00 SDSC/QUALCOMM 56 kbps 05.5% 05:00 SDSC/SCIH 56 kbps 06.1% 03:00 SDSC/USD 56 kbps 07.1% 17:00 SDSC/USIU 56 kbps 00.6% 15:00 SDSC/XEROX 56 kbps 00.7% 17:00 UCI/CMD 56 kbps 06.1% 20:00 UCI/EMULEX 56 kbps 01.2% 16:00 UCI/FULLERTON 56 kbps 01.4% 13:00 UCI/HUGHES 56 kbps 07.9% 11:00 UCI/MTI 56 kbps 05.8% 17:00 UCI/SPARTA 56 kbps 02.4% 09:00 UCI/UNOCAL 56 kbps 06.8% 22:00 UCLA/ISX 56 kbps 00.9% 10:00 UCLA/PEPPERDINE 56 kbps 02.4% 06:00 UCLA/QUOTRON 56 kbps 04.3% 13:00 UCLA/SMC 56 kbps 00.8% 15:00 UCOP/FARALLON 56 kbps 04.2% 11:00 UCOP/INTEL 56 kbps 15.9% 15:00 UCOP/LSIL 56 kbps 07.1% 21:00 UCOP/NETLABS 56 kbps 14.2% 20:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Feb. 17, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 04 days 15 hours 17 minutes [CERFnet Scheduled Maintenance] SDSC Drzog [132.249.16.13] Up: 64 days 08 hours 25 minutes SDSC Hang10 [132.249.16.15] Up: 10 days 09 hours 52 minutes UCI [128.200.1.101] Up: 38 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 09 days 13 hours 42 minutes UCOP [134.24.52.112] Up: 08 days 08 hours 57 minutes UCR [134.24.108.105] Up: 93 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 03 days 13 hours 54 minutes [Power Outage] APPLE [134.24.70.200] Up: 112 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 14 days 06 hours 48 minutes CISCO Systems [134.24.54.200] Up: 75 days 14 hours 09 minutes CSUCO/SWRL [130.150.102.200] Up: 33 days 12 hours 46 minutes GA [134.24.221.200] Up: 03 days 16 hours 45 minutes [Power Outage] GD [134.24.60.200] Up: 46 days 04 hours 14 minutes LLUMC [134.24.208.200] Up: 89 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 43 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 59 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 69 days 16 hours 31 minutes UCSB [134.24.107.107] Up: 89 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 30 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 12 days 13 hours 01 minutes CLAREMONT [134.24.206.109] Up: 03 days 14 hours 02 minutes [Unscheduled Outage] CMD [134.24.218.200] Up: 20 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 05 days 20 hours 03 minutes [Power Outage] DISNEY [134.24.207.211] Up: 18 days 00 hours 33 minutes EMULEX [134.24.209.212] Up: 64 days 15 hours 48 minutes FARALLON [134.24.56.200] Up: 05 days 15 hours 03 minutes [Unsheduled Site Maintenance] FULLERTON [134.24.214.217] Up: 62 days 15 hours 33 minutes HUGHES [134.24.204.200] Up: 94 days 07 hours 21 minutes INTEL [134.24.55.200] Up: 50 days 03 hours 19 minutes LSIL [134.24.72.200] Up: 08 days 13 hours 08 minutes MTI [134.24.216.100] Up: 44 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 72 days 15 hours 07 minutes OXY [134.24.205.108] Up: 03 days 19 hours 45 minutes [Unknown] PEPPERDINE [134.24.203.218] Up: 43 days 13 hours 24 minutes QUALCOMM [134.24.200.201] Up: 04 days 09 hours 37 minutes [Power Outage] QUOTRON [134.24.230.202] Up: 84 days 13 hours 44 minutes SANTA MONICA [134.24.210.219] Up: 38 days 01 hours 22 minutes SCI-HOR [134.24.109.205] Up: 80 days 11 hours 15 minutes SERI/KOREA [134.24.223.200] Up: 146 days 00 hours 00 minutes SPARTA [134.24.215.200] Up: 03 days 19 hours 09 minutes [Power Outage] UNOCAL [134.24.217.200] Up: 25 days 14 hours 24 minutes USD [134.24.201.106] Up: 18 days 15 hours 45 minutes USIU [134.24.222.215] Up: 225 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 109 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 33 days 04 hours 51 minutes DNC-UCI [134.24.2.2] Up: 40 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 25 days 12 hours 38 minutes DNC-CALTECH [134.24.4.2] Up: 18 days 16 hours 28 minutes DNC-UCOP [134.24.5.2] Up: 08 days 08 hours 58 minutes

1 0

[Merit Network Operations Center: 02/14/92 NSS 8 Princeton Unreachable 20:26 - ? EDT]
by skennedy＠BBN.COM 15 Feb '92

15 Feb '92

Circuit problems should not affect connectivity to a host across an ethernet? Are there two NSS-8 outages? As we reported (NN TT# 2642), the T1-EPSP at MIT is down. Drops pings... Sean Kennedy NEARnet ------- Forwarded Message Received: from nic.near.net by LABS-N.BBN.COM id aa10008; 14 Feb 92 20:54 EST Received: from nic.near.net by nic.near.net id aa25834; 14 Feb 92 20:52 EST Received: from merit.edu by nic.near.net id aa25830; 14 Feb 92 20:52 EST Return-Path: <noc(a)merit.edu> Received: by merit.edu (5.65/1123-1.0) id AA06457; Fri, 14 Feb 92 20:49:57 -0500 Received: by merit.edu (5.65/1123-1.0) id AA06453; Fri, 14 Feb 92 20:49:55 -0500 Date: Fri, 14 Feb 92 20:49:55 -0500 From: Merit Network Operations Center <noc(a)merit.edu> Message-Id: <9202150149.AA06453(a)merit.edu> To: nsr(a)merit.edu Subject: 02/14/92 NSS 8 Princeton Unreachable 20:26 - ? EDT 02/14/92 NSS 8 Princeton Unreachable 20:26 - ? EDT due to circuit problems. Michele Davis MERIT/NSFNet ------- End of Forwarded Message

1 0