- NANOG - lists.nanog.org

Phase 5 Upgrade Completed!
by Ittai Hershman 18 Dec '93

18 Dec '93

I am pleased to announce that this morning, we successfully completed the Phase 5 ANSNet deployment. The major changes accomplished in this upgrade were: o Upgrade of all DS3/HSSI router serial interface adapters (T3 CNSS and ENSS) to support full DS3 bandwidth. The router adapter bus interface cards were also upgraded to double the packet switching rates per interface. o The T3 DSUs on each DS3 interface were replaced with T3Plus BMX45 bandwidth managers on T3 CNSS-CNSS circuits and Larscom Access-T45 DSUs on a T3 ENSS-CNSS circuit. o The architecture for interconnection among CNSS routers at each MCI POP location was upgraded to a common FDDI ring from the original point-to-point links architecture. As a result of this upgrade, we have 17 backbone links and 21 customer attachments running at full T3: Seattle - Denver Backbone Link Seattle - San Francisco Backbone Link San Francisco - Chicago Backbone Link San Francisco - Los Angeles Backbone Link Los-Angeles - Albuquerque Backbone Link Albuquerque - Houston Backbone Link Houston - Atlanta Backbone Link Atlanta - Greensboro Backbone Link * Wash DC - Greensboro Backbone Link * New York - Wash DC Backbone Link Houston - St. Louis Backbone Link Denver - St. Louis Backbone Link St. Louis - Chicago Backbone Link Chicago - Cleveland Backbone Link Cleveland - New York Backbone Link * Hartford - Cleveland Backbone Link * New York - Hartford Backbone Link ENSS128 at Palo Alto (BARRnet, Stanford University) ENSS129 at Champaign (UIUC, CICnet) ENSS130 at Argonne (Argonne National Lab, CICNet) ENSS131 at Ann Arbor (ANS AA, Michnet, CICnet, etc.) ENSS132 at Pittsburgh (PSCnet, PREPnet, CMU, etc.). * ENSS133 at Ithaca (PSI, Cornell) * ENSS134 at Cambridge (NEARnet, Alternet, MIT) ENSS135 at San Diego (CERFnet, SDSC, etc.) * ENSS136 at College Park (SURAnet, Alternet, MAE-East, U of M, etc). ENSS137 at Princeton (Princeton University, JVNCnet) ENSS138 at Atlanta (Georgia Tech, SURAnet) ENSS139 at Houston (Sesquinet, Rice University) ENSS140 at Lincoln (MIDnet, Westnet, etc.) ENSS141 at Boulder (Westnet, NCAR, U of Colorado, etc.) ENSS142 at Salt Lake City (WestNet, U of Utah, etc.) ENSS143 at Seattle (NorthWestNet, U of Washington, etc.) ENSS144 at Moffett Field (FIX-West) * ENSS145 at College Park (FIX-East) * ENSS146 at Arlington (ARPA) ENSS172 at Albuquerque (Phillips Laboratory) ENSS179 at Albuquerque (Sandia National Labs) (*) upgraded this morning during Step 6 (of 6) of the deployment. Happy holidays to all from all of us at ANS, -Ittai

1 0

results of survey (so far)
by epg 17 Dec '93

17 Dec '93

On Dec 5, Merit sent a survey to the ASs that peer with the NSFNET/ANSnet asking a lot of questions about BGP4. (The survey is appended to the end of this message.) Of the 28 organizations that we hoped would respond, 15 did. Of the 15, 9 point default at the NSFNET/ANSnet. Of the 6 which don't point default, 4 will have BGP4 by January '94. All 15 responded that they did NOT want proxy aggregation done by the NSFNET/ ANSnet. Since we haven't asked folks if we could publish info about their networks, all respondents remain anonymous :-) --Elise ---------------------Survey------------------------ Date: Sun, 5 Dec 93 14:04:51 EST From: epg(a)merit.edu To: regional-techs(a)merit.edu During early January, we are planning on deploying new router software on NSFNET/ANSnet based upon Gated. This software will support the BGP4 protocol and will interoperate with the older rcp_routed software. We currently expect this software to be fully deployed by mid-January, and this will make the NSFNET/ANSnet capable of supporting CIDR routing. Once NSFNET/ANSnet starts accepting CIDR aggregates, any networks that peer with NSFNET/ANSnet will need to either accept CIDR aggregates (via BGP4 on their routers) or default to NSFNET/ANSnet. The purpose of this questionnaire is to identify any problems with these options, and help plan for a smooth transition. Will a representative of each routing peer please complete the following questionnaire and return it to ie(a)merit.edu before December 10. Thank you for your cooperation. 1. Name of Your Network: 2. The AS number(s) of your Network: 3. Routing information currently imported from NSFNET/ANSnet: a) default only (y/n) b) default + specific routes (y/n) c) explicit routes only - no default (y/n) 4. If you import explicit routes from NSFNET/ANSnet, is it a requirement for your routing design (y/n)? 5. When NSFNET/ANSnet becomes CIDR capable, do you expect to be able to peer via BGP4 and accept CIDR aggregates? (y/n) if yes: a) What kind of router do you plan to use? b) What software release will you use? c) When do you plan to advertise aggregates to NSFNET/ANSnet? (qt/yr) if no: a) Can you generate or accept a default route that points to NSFNET/ANSnet? (y/n) b) When do you expect to peer with the NSFNET/ANSnet via BGP4? (qt/yr or never) 6. If you can not generate or accept a default route that points to NSFNET/ANSnet, can you suggest an alternate routing plan? 7. Do you expect NSFNET/ANSnet to do proxy aggregation for any explicit routes that you announce? 8. Do you still expect to use EGP protocol to peer with NSFNET/ANSnet? (y/n) if yes: a) Do you have plans to migrate to BGP? (y/n) b) When do you expect to migrate to BGP? (qt/yr) c) Which version of BGP will you deploy? (2,3,4)

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 17 Dec '93

17 Dec '93

------------------------------------------------------------------------------ NOTICE: This "nwg" report, plus the reports "ans_core.now", "country.now" and "net-comp.now" will be modified to use aggregate notation on January 4. See below for details. ------------------------------------------------------------------------------ The following additions have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00EST : Total = Class A+Class B+Class C Configured Networks 20935 = 27 4213 16695 Added Networks 177 = 0 7 170 Deleted Networks 1 = 0 0 1 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 145.49 NLAKZO03 C:NL D:12/17/93 1:1133 2:1800 3:1240 148.127 ENTERGY C:US D:12/17/93 1:279 2:86 151.188 FCPS C:US D:12/17/93 1:297 2:372 163.123 AWP C:CA D:12/17/93 1:602 2:601 3:603 163.191 ILLINOIS C:US D:12/17/93 1:267 2:1225 3:266 165.1 AP C:US D:12/17/93 1:2149 2:174 166.93 ROCKYMTN C:US D:12/17/93 1:1332 192.22.3 APPLICON-C-22-3 C:US D:12/17/93 1:209 2:210 192.22.4 APPLICON-C-22-4 C:US D:12/17/93 1:209 2:210 192.36.221 FFA2 C:SE D:12/17/93 1:1800 2:1879 3:1133 4:1240 192.54.101 UMD-UNCON C:US D:12/17/93 1:86 2:279 192.68.147 SCT-NET C:US D:12/17/93 1:2551 192.77.152 ANS-CNET2 C:US D:12/17/93 1:1324 192.109.13 UNIBT-LAN-A C:DE D:12/17/93 1:293 2:291 192.109.19 UNIBT-LAN-B C:DE D:12/17/93 1:293 2:291 192.109.202 UNIBT-LAN-C C:DE D:12/17/93 1:293 2:291 192.114.121 ANKOR-NET C:IL D:12/17/93 1:2149 2:174 192.124.254 TROPOS C:DE D:12/17/93 1:293 2:291 192.134.60 FNET-U-BG3 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 192.139.115 FPMINET C:CA D:12/17/93 1:601 2:603 3:602 192.154.81 BBT1 C:US D:12/17/93 1:81 192.154.82 BBT2 C:US D:12/17/93 1:81 192.154.83 BBT3 C:US D:12/17/93 1:81 192.154.84 BBT4 C:US D:12/17/93 1:81 192.154.85 BBT5 C:US D:12/17/93 1:81 192.154.86 BBT6 C:US D:12/17/93 1:81 192.154.87 BBT7 C:US D:12/17/93 1:81 192.154.88 BBT8 C:US D:12/17/93 1:81 192.154.89 BBT9 C:US D:12/17/93 1:81 192.154.90 BBT10 C:US D:12/17/93 1:81 192.160.231 ARCS C:AT D:12/17/93 1:1133 2:1800 3:1240 192.188.251 NBN-NET1 C:US D:12/17/93 1:1240 2:1800 192.216.227 ISI-C-216-227 C:US D:12/17/93 1:200 2:201 192.216.228 ISI-C-216-228 C:US D:12/17/93 1:200 2:201 192.231.73 TESSI-1 C:US D:12/17/93 1:1240 2:1800 192.231.74 TESSI-2 C:US D:12/17/93 1:1240 2:1800 192.234.213 LDC-CA C:US D:12/17/93 1:200 2:201 192.234.214 LDC-CA2 C:US D:12/17/93 1:200 2:201 192.244.209 SUNCS-NET2 C:JP D:12/17/93 1:1240 2:1800 192.244.210 SUNCS-NET3 C:JP D:12/17/93 1:1240 2:1800 192.244.211 SUNCS-NET4 C:JP D:12/17/93 1:1240 2:1800 192.244.212 SUNCS-NET5 C:JP D:12/17/93 1:1240 2:1800 192.244.213 SUNCS-NET6 C:JP D:12/17/93 1:1240 2:1800 192.244.214 SUNCS-NET7 C:JP D:12/17/93 1:1240 2:1800 192.244.215 SUNCS-NET8 C:JP D:12/17/93 1:1240 2:1800 192.244.216 SUNCS-NET9 C:JP D:12/17/93 1:1240 2:1800 192.244.217 SUNCS-NET10 C:JP D:12/17/93 1:1240 2:1800 192.244.218 SUNCS-NET11 C:JP D:12/17/93 1:1240 2:1800 192.244.219 SUNCS-NET12 C:JP D:12/17/93 1:1240 2:1800 192.244.220 SUNCS-NET13 C:JP D:12/17/93 1:1240 2:1800 192.244.221 SUNCS-NET14 C:JP D:12/17/93 1:1240 2:1800 192.244.222 SUNCS-NET15 C:JP D:12/17/93 1:1240 2:1800 192.244.223 SUNCS-NET16 C:JP D:12/17/93 1:1240 2:1800 193.51.113 FNET-CIRAD9 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.51.118 FNET-CIRAD14 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.52.232 FR-UNIV-BG01 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.52.234 FR-UNIV-BG03 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.52.249 FR-UNIV-BG18 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.52.250 FR-UNIV-BG19 C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.54.43 IUTB-NANCY-G C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.54.44 CNRS-LETORT C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.54.46 FR-CIRIL-ADM C:FR D:12/17/93 1:1800 2:1240 3:1133 4:1674 193.64.173 VARIAN1 C:FI D:12/17/93 1:701 2:1800 193.84.88 MFFUK-A-C-84-88 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.89 MFFUK-A-C-84-89 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.90 MFFUK-A-C-84-90 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.91 MFFUK-A-C-84-91 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.96 MPO-C-84-96 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.97 MPO-C-84-97 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.98 MPO-C-84-98 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.84.99 MPO-C-84-99 C:CZ D:12/17/93 1:1133 2:1800 3:1240 193.87.10 SASKE-SK-C-87-10 C:SK D:12/17/93 1:1133 2:1800 3:1240 193.87.11 SASKE-SK-C-87-11 C:SK D:12/17/93 1:1133 2:1800 3:1240 193.100.241 GLASNOST C:DE D:12/17/93 1:701 2:1800 193.104.116 FR-PARALLAX C:FR D:12/17/93 1:701 2:1800 193.106.225 FR-DSTM2 C:FR D:12/17/93 1:701 2:1800 193.140.21 9EYLUL-NET-C-140-21 C:TR D:12/17/93 1:1800 2:1240 193.140.22 9EYLUL-NET-C-140-22 C:TR D:12/17/93 1:1800 2:1240 193.140.23 9EYLUL-NET-C-140-23 C:TR D:12/17/93 1:1800 2:1240 193.140.24 9EYLUL-NET-C-140-24 C:TR D:12/17/93 1:1800 2:1240 193.170.140 VIE-EBS1 C:AT D:12/17/93 1:1133 2:1800 3:1240 193.170.141 VIE-EBS2 C:AT D:12/17/93 1:1133 2:1800 3:1240 193.170.156 HTL-LEONDING C:AT D:12/17/93 1:1133 2:1800 3:1240 193.226.2 RO-EARN-C-226-2 C:RO D:12/17/93 1:1133 2:1800 3:1240 193.226.3 RO-EARN-C-226-3 C:RO D:12/17/93 1:1133 2:1800 3:1240 193.226.47 IMT-NET C:RO D:12/17/93 1:1133 2:1800 3:1240 193.226.57 RO-IC C:RO D:12/17/93 1:1133 2:1800 3:1240 198.5.163 CFCOM C:US D:12/17/93 1:701 2:702 198.22.29 TXCOMMERCEAJ C:US D:12/17/93 1:114 2:1700 198.22.44 CORSOF C:US D:12/17/93 1:560 2:281 3:701 198.30.95 OAR95 C:US D:12/17/93 1:600 198.30.194 OAR194 C:US D:12/17/93 1:600 198.30.195 OAR195 C:US D:12/17/93 1:600 198.30.196 OAR196 C:US D:12/17/93 1:600 198.59.68 WESTNET-C-59-68 C:US D:12/17/93 1:209 2:210 198.60.29 WESTNET-C-60-29 C:US D:12/17/93 1:210 2:209 198.60.152 EAC C:US D:12/17/93 1:210 2:209 198.60.217 WESTNET-C-60-217 C:US D:12/17/93 1:210 2:209 198.71.16 MFI1 C:US D:12/17/93 1:2551 198.76.14 CIES C:US D:12/17/93 1:86 2:279 198.76.20 NDU-C-76-20 C:US D:12/17/93 1:86 2:279 198.76.21 NDU-C-76-21 C:US D:12/17/93 1:86 2:279 198.85.80 SYNESIS1 C:US D:12/17/93 1:81 198.86.24 JCSD1 C:US D:12/17/93 1:81 198.93.28 INTEROP-US-4 C:US D:12/17/93 1:200 2:201 198.93.29 INTEROP-US-5 C:US D:12/17/93 1:200 2:201 198.93.30 INTEROP-US-6 C:US D:12/17/93 1:200 2:201 198.93.31 INTEROP-US-7 C:US D:12/17/93 1:200 2:201 198.112.90 MVLC C:US D:12/17/93 1:560 2:281 3:701 198.145.72 WDN-C-145-72 C:US D:12/17/93 1:1240 2:1800 198.145.73 WDN-C-145-73 C:US D:12/17/93 1:1240 2:1800 198.145.74 WDN-C-145-74 C:US D:12/17/93 1:1240 2:1800 198.152.2 ATT-ELS-152-2 C:US D:12/17/93 1:2386 198.152.3 ATT-ELS-152-3 C:US D:12/17/93 1:2386 198.152.4 ATT-ELS-152-4 C:US D:12/17/93 1:2386 198.162.11 TELOSENG C:CA D:12/17/93 1:602 2:601 3:603 198.162.16 CYBERNET-C-162-16 C:CA D:12/17/93 1:602 2:601 3:603 198.162.17 CYBERNET-C-162-17 C:CA D:12/17/93 1:602 2:601 3:603 198.162.18 CYBERNET-C-162-18 C:CA D:12/17/93 1:602 2:601 3:603 198.162.19 CYBERNET-C-162-19 C:CA D:12/17/93 1:602 2:601 3:603 198.162.24 INSINCNETI-C-162-24 C:CA D:12/17/93 1:602 2:601 3:603 198.162.25 INSINCNETI-C-162-25 C:CA D:12/17/93 1:602 2:601 3:603 198.162.26 INSINCNETI-C-162-26 C:CA D:12/17/93 1:602 2:601 3:603 198.162.27 INSINCNETI-C-162-27 C:CA D:12/17/93 1:602 2:601 3:603 198.162.28 INSINCNETI-C-162-28 C:CA D:12/17/93 1:602 2:601 3:603 198.162.29 INSINCNETI-C-162-29 C:CA D:12/17/93 1:602 2:601 3:603 198.162.30 INSINCNETI-C-162-30 C:CA D:12/17/93 1:602 2:601 3:603 198.162.31 INSINCNETI-C-162-31 C:CA D:12/17/93 1:602 2:601 3:603 198.174.221 TIESNET19-C-174-221 C:US D:12/17/93 1:267 2:1225 3:266 4:555 198.186.218 USDANET9 C:US D:12/17/93 1:114 2:1700 198.187.4 NET-DPA-CA-GOV1 C:US D:12/17/93 1:200 2:201 198.187.5 NET-DPA-CA-GOV2 C:US D:12/17/93 1:200 2:201 198.187.6 NET-DPA-CA-GOV3 C:US D:12/17/93 1:200 2:201 198.187.7 NET-DPA-CA-GOV4 C:US D:12/17/93 1:200 2:201 198.206.181 XYLAN-C-206-181 C:US D:12/17/93 1:1740 198.211.215 STRATA215 C:US D:12/17/93 1:2551 198.211.216 STRATA216 C:US D:12/17/93 1:2551 198.232.205 LHCA2 C:US D:12/17/93 1:279 2:86 198.252.149 IAINET C:US D:12/17/93 1:560 2:281 3:701 199.0.19 SPRINT-C-0-19 C:CA D:12/17/93 1:1800 2:1240 199.2.22 SPRINT-C-2-22 C:US D:12/17/93 1:1240 2:1800 199.2.48 CYBERSPACE-NET1 C:US D:12/17/93 1:1240 2:1800 199.3.20 CYBERSPACE-NET2 C:US D:12/17/93 1:1240 2:1800 199.4.1 TTOOL-C-4-1 C:US D:12/17/93 1:2149 2:174 199.4.64 NBN-NET-C-4-64 C:US D:12/17/93 1:1240 2:1800 199.4.65 NBN-NET-C-4-65 C:US D:12/17/93 1:1240 2:1800 199.5.136 FVRL-1 C:US D:12/17/93 1:1331 199.29.138 PSINET-C-29-138 C:US D:12/17/93 1:2149 2:174 199.29.139 PSINET-C-29-139 C:US D:12/17/93 1:2149 2:174 199.29.140 PSINET-C-29-140 C:US D:12/17/93 1:2149 2:174 199.29.141 PSINET-C-29-141 C:US D:12/17/93 1:2149 2:174 199.29.143 PSINET-C-29-143 C:US D:12/17/93 1:2149 2:174 199.29.144 PSINET-C-29-144 C:US D:12/17/93 1:2149 2:174 199.29.145 PSINET-C-29-145 C:US D:12/17/93 1:2149 2:174 199.29.146 PSINET-C-29-146 C:US D:12/17/93 1:2149 2:174 199.29.147 PSINET-C-29-147 C:US D:12/17/93 1:2149 2:174 199.29.148 PSINET-C-29-148 C:US D:12/17/93 1:2149 2:174 199.29.149 PSINET-C-29-149 C:US D:12/17/93 1:2149 2:174 199.29.150 PSINET-C-29-150 C:US D:12/17/93 1:2149 2:174 199.29.151 PSINET-C-29-151 C:US D:12/17/93 1:2149 2:174 199.29.152 PSINET-C-29-152 C:US D:12/17/93 1:2149 2:174 199.29.153 PSINET-C-29-153 C:US D:12/17/93 1:2149 2:174 199.29.154 PSINET-C-29-154 C:US D:12/17/93 1:2149 2:174 199.29.155 PSINET-C-29-155 C:US D:12/17/93 1:2149 2:174 199.29.156 PSINET-C-29-156 C:US D:12/17/93 1:2149 2:174 199.29.157 PSINET-C-29-157 C:US D:12/17/93 1:2149 2:174 199.29.158 PSINET-C-29-158 C:US D:12/17/93 1:2149 2:174 199.29.159 PSINET-C-29-159 C:US D:12/17/93 1:2149 2:174 199.29.160 PSINET-C-29-160 C:US D:12/17/93 1:2149 2:174 199.29.161 PSINET-C-29-161 C:US D:12/17/93 1:2149 2:174 199.88.16 ASC2-C-88-16 C:US D:12/17/93 1:279 2:86 200.9.66 ABDL-ANSP C:BR D:12/17/93 1:293 2:291 200.9.185 AEG-SP-ANSP C:BR D:12/17/93 1:293 2:291 202.11.120 DICNET120 C:JP D:12/17/93 1:1240 2:1800 202.11.121 DICNET121 C:JP D:12/17/93 1:1240 2:1800 202.11.122 DICNET122 C:JP D:12/17/93 1:1240 2:1800 202.11.123 DICNET123 C:JP D:12/17/93 1:1240 2:1800 ------------------------------------------------------------ ABDL-Associacao Brasileira para Desenvolvimento de Liderancas, Av. Prof. Luciano Gualberto, 908 - Sala D 47, Sao Paulo, SP, 05508-900, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------- 200.9.66 ABDL-ANSP (BR) AT&T EasyLink Services, 307 Middletown-Lincroft Road, Lincroft, NJ 07738, USA 1:2386 INS-AS --------- 198.152.2 ATT-ELS-152-2 (US) 198.152.3 ATT-ELS-152-3 (US) 198.152.4 ATT-ELS-152-4 (US) Advanced Network & Services, Inc., 100 Clearbrook Rd., Elmsford, NY 10523, USA 1:1324 ANS New York City - DNSS 35 ---------- 192.77.152 ANS-CNET2 (US) Akzo NV, P.O. Box 20, NL - 5340 BH Oss, NETHERLANDS 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ------ 145.49 NLAKZO03 (NL) Alabama Supercomputer Network, 686 Discovery Dr, Huntsville, AL 35806, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) --------- 199.88.16 ASC2-C-88-16 (US) Alberta Wheat Pool, P.O. Box 2700, Calgary, AB, T2P 2P5, CANADA 1:602 CA*net in Montreal 2:601 CA*net in Toronto 3:603 CA*net in Quebec ------- 163.123 AWP (CA) Ankor Computers Ltd., Atidim industrial park, Tel Aviv, 61580, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 192.114.121 ANKOR-NET (IL) Applicon, 829 Middlesex Turnpike, Billerica, MA 01821, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 -------- 192.22.3 APPLICON-C-22-3 (US) 192.22.4 APPLICON-C-22-4 (US) Area Cooperative Educational Service, 205 Skiff Street, Hamden, CT 06517-1095, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.140 PSINET-C-29-140 (US) 199.29.144 PSINET-C-29-144 (US) 199.29.145 PSINET-C-29-145 (US) 199.29.146 PSINET-C-29-146 (US) 199.29.147 PSINET-C-29-147 (US) 199.29.148 PSINET-C-29-148 (US) 199.29.149 PSINET-C-29-149 (US) 199.29.150 PSINET-C-29-150 (US) 199.29.151 PSINET-C-29-151 (US) 199.29.152 PSINET-C-29-152 (US) 199.29.153 PSINET-C-29-153 (US) 199.29.154 PSINET-C-29-154 (US) 199.29.155 PSINET-C-29-155 (US) 199.29.156 PSINET-C-29-156 (US) 199.29.157 PSINET-C-29-157 (US) 199.29.158 PSINET-C-29-158 (US) 199.29.159 PSINET-C-29-159 (US) Associacao Escola Graduada de Sao Paulo, Av. Pres. Giovanni Gronchi 4710, Sao Paulo, SP, 05724-002, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) --------- 200.9.185 AEG-SP-ANSP (BR) Associated Press, 50 Rockefeller Plaza, New York, NY 10020, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----- 165.1 AP (US) Automated Business Development, One Bromfield Street, Boston, MA 02108-5176, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.139 PSINET-C-29-139 (US) Better Image Productions, 1631 N. First St., San Jose, CA 95112, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------- 199.2.22 SPRINT-C-2-22 (US) BroadBand Technologies, Inc., 4024 Stirrup Creek Drive, Durham, NC 27709, USA 1:81 CONCERT ---------- 192.154.81 BBT1 (US) 192.154.82 BBT2 (US) 192.154.83 BBT3 (US) 192.154.84 BBT4 (US) 192.154.85 BBT5 (US) 192.154.86 BBT6 (US) 192.154.87 BBT7 (US) 192.154.88 BBT8 (US) 192.154.89 BBT9 (US) 192.154.90 BBT10 (US) CIRAD, 42 rue Sheffer, 75116 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN-EBONE 4:1674 CERN-EBONE Backup AS ---------- 193.51.113 FNET-CIRAD9 (FR) 193.51.118 FNET-CIRAD14 (FR) CIRIL, Chateau du Montet, 54500 Vandoeuvre, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN-EBONE 4:1674 CERN-EBONE Backup AS --------- 193.54.46 FR-CIRIL-ADM (FR) CNRS - Laboratoire Maurice Letort, 405, rue de Vandoeuvre, 54600 Villers les Nancy, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN-EBONE 4:1674 CERN-EBONE Backup AS --------- 193.54.44 CNRS-LETORT (FR) California Department of Personel Administration, 1515 S Street, Sacramento, CA 95814, USA 1:200 BARRNet 2:201 BARRNet --------- 198.187.4 NET-DPA-CA-GOV1 (US) 198.187.5 NET-DPA-CA-GOV2 (US) 198.187.6 NET-DPA-CA-GOV3 (US) 198.187.7 NET-DPA-CA-GOV4 (US) Centre de Calcul de l'Universite de Bourgogne, BP 138, 21004 Dijon CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN-EBONE 4:1674 CERN-EBONE Backup AS ---------- 192.134.60 FNET-U-BG3 (FR) 193.52.232 FR-UNIV-BG01 (FR) 193.52.234 FR-UNIV-BG03 (FR) 193.52.249 FR-UNIV-BG18 (FR) 193.52.250 FR-UNIV-BG19 (FR) Cleveland Advanced Management, 4600 Prospect Avenue, Cleveland, OH 44103-4314, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.138 PSINET-C-29-138 (US) Computer Centre, Charles University, Malostranske nam. 25, Prague 1, CZECH REPUBLIC 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific --------- 193.84.88 MFFUK-A-C-84-88 (CZ) 193.84.89 MFFUK-A-C-84-89 (CZ) 193.84.90 MFFUK-A-C-84-90 (CZ) 193.84.91 MFFUK-A-C-84-91 (CZ) Consolidated Freightways, Inc., PO Box 4845, Portland, OR 97208-4845, USA 1:701 Alternet 2:702 Alternet --------- 198.5.163 CFCOM (US) Cornerstone Software, Inc., 11 Trafalgar Square, Nashua, NH 03063, USA 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:701 Alternet --------- 198.22.44 CORSOF (US) Council for the Int'l Exchange of Scholars, 3007 Tilden Street, Washington, DC 20008, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) --------- 198.76.14 CIES (US) Cyberspace Communications, 300 Queen Anne Ave N #396, Seattle, WA 98109, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------- 199.2.48 CYBERSPACE-NET1 (US) 199.3.20 CYBERSPACE-NET2 (US) Daido Institute of Technology, 2-21, Daido-cho, Minami-ku, Nagoya 457, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 202.11.120 DICNET120 (JP) 202.11.121 DICNET121 (JP) 202.11.122 DICNET122 (JP) 202.11.123 DICNET123 (JP) Datastream International / France, 25 Avenue Marceau, 75116 Paris CEDEX, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ----------- 193.106.225 FR-DSTM2 (FR) Eastern Arizona College, Computer Center, Thatcher, AZ 85552-0769, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ---------- 198.60.152 EAC (US) Entergy Corporation, 200 Westbank Expressway, Gretna, LA 70053, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------- 148.127 ENTERGY (US) FFA, Box 11021, S-161 11 Bromma, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN-EBONE 4:1240 ICM-Pacific ---------- 192.36.221 FFA2 (SE) Fairfax County Public Schools, 3701 Franconia Road, Alexandria, VA 22310, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------- 151.188 FCPS (US) Forest Pest Management Institute, 1219 Queen Street East, Sault Ste. Marie,, ON, P6A 5M7, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Quebec 3:602 CA*net in Montreal ----------- 192.139.115 FPMINET (CA) Fort Vancouver Regional Library, 1007 E. Mill Plain Blvd., Vancouver, WA 98663, USA 1:1331 ANS Seattle - DNSS 91 --------- 199.5.136 FVRL-1 (US) Glasnost GmbH, Rankestr. 31, 10789 Berlin, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ----------- 193.100.241 GLASNOST (DE) Hoehere Technische Bundeslehranstalt Leonding, Limesstrasse 12 - 14, A-4060 Leonding, AUSTRIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ----------- 193.170.156 HTL-LEONDING (AT) HookUp Communications Corp., 220-50 Westmount Rd. North, Waterloo, ON, N2L 2R5, CANADA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------- 199.0.19 SPRINT-C-0-19 (CA) IUT B, Le Montet, 54601 Villers les Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN-EBONE 4:1674 CERN-EBONE Backup AS --------- 193.54.43 IUTB-NANCY-G (FR) Imaging Automation Inc., 7 Henry Clay Drive, Merrimack, NH 03054, USA 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:701 Alternet ----------- 198.252.149 IAINET (US) Institut fuer Troposphaerenforschung Leipzig, Permoser Str. 15, Leipzig, D-04303, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ----------- 192.124.254 TROPOS (DE) Institute for Microtechnology, Romanian Academy, Splaiul Independentei 313, Sector 6, ROMANIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ---------- 193.226.47 IMT-NET (RO) Institute of Experimental Physics, Slovak Academy of Sciences, B. Nemcovej 3, Kosice, SLOVAKIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific --------- 193.87.10 SASKE-SK-C-87-10 (SK) 193.87.11 SASKE-SK-C-87-11 (SK) Integrated Network Services Inc., 1700 - 555 West Hastings Street, Vancouver, BC, V6B 4N5, CANADA 1:602 CA*net in Montreal 2:601 CA*net in Toronto 3:603 CA*net in Quebec ---------- 198.162.24 INSINCNETI-C-162-24 (CA) 198.162.25 INSINCNETI-C-162-25 (CA) 198.162.26 INSINCNETI-C-162-26 (CA) 198.162.27 INSINCNETI-C-162-27 (CA) 198.162.28 INSINCNETI-C-162-28 (CA) 198.162.29 INSINCNETI-C-162-29 (CA) 198.162.30 INSINCNETI-C-162-30 (CA) 198.162.31 INSINCNETI-C-162-31 (CA) Integrated Systems, Inc, 3260 Jay Street, Santa Clara, CA 95054, USA 1:200 BARRNet 2:201 BARRNet ----------- 192.216.227 ISI-C-216-227 (US) 192.216.228 ISI-C-216-228 (US) InterComp, Dionisie Lupu 72, Bucharest 1, ROMANIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ---------- 193.226.57 RO-IC (RO) Interop, Inc, 303 Vintage Park Dr, Foster City, CA 94404, USA 1:200 BARRNet 2:201 BARRNet --------- 198.93.28 INTEROP-US-4 (US) 198.93.29 INTEROP-US-5 (US) 198.93.30 INTEROP-US-6 (US) 198.93.31 INTEROP-US-7 (US) Iris Associates, One Technology Park, Westford, MA 01886, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.160 PSINET-C-29-160 (US) Jones County Schools, 320 W. Jones, P.O. Box 187, Trenton, NC 28585, USA 1:81 CONCERT --------- 198.86.24 JCSD1 (US) L. H. Rosenberg & Associates, 13010 Heil Manor Dr, Reisterstown, MD 21136, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.143 PSINET-C-29-143 (US) Legislative Data Center, 1100 J Street, Suite 200, Sacramento, CA 95814, USA 1:200 BARRNet 2:201 BARRNet ----------- 192.234.213 LDC-CA (US) 192.234.214 LDC-CA2 (US) Marger Johnson McCollom & Stolowitz, Inc., 621 SW Morrison Street #650, Portland, OR 97205, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 198.145.72 WDN-C-145-72 (US) 198.145.73 WDN-C-145-73 (US) 198.145.74 WDN-C-145-74 (US) Merrimack Valley Library Consortium, Elm Square, Andover, MA 01810, USA 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:701 Alternet ---------- 198.112.90 MVLC (US) Miller Freeman, 411 Borel Ave. #100, San Mateo, CA 94402, USA 1:2551 NETCOM --------- 198.71.16 MFI1 (US) Ministry of Industry and Trade, Politickych veznu 20, Prague 1, CZECH REPUBLIC 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific --------- 193.84.96 MPO-C-84-96 (CZ) 193.84.97 MPO-C-84-97 (CZ) 193.84.98 MPO-C-84-98 (CZ) 193.84.99 MPO-C-84-99 (CZ) National Defense University, Ft. McNair, Bldg. 62, Washington, DC 20319-6000, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) --------- 198.76.20 NDU-C-76-20 (US) 198.76.21 NDU-C-76-21 (US) New York Academy of Medicine, 1216 Fifth Avenue, New York, NY 10029, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.141 PSINET-C-29-141 (US) North Bay Network, Inc., 20 Minor Ct., San Rafael, CA 94903, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 192.188.251 NBN-NET1 (US) 199.4.64 NBN-NET-C-4-64 (US) 199.4.65 NBN-NET-C-4-65 (US) OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA 1:600 OARNET, Cleveland, OH ---------- 198.30.194 OAR194 (US) 198.30.195 OAR195 (US) 198.30.196 OAR196 (US) 198.30.95 OAR95 (US) Oest. Forschungsz. Seibersdorf, Abt. IT, A-2444 Seibersorf, AUSTRIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ----------- 192.160.231 ARCS (AT) Parallax Software Technologies, 5 rue Bellini, 92806 Puteaux CEDEX, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ----------- 193.104.116 FR-PARALLAX (FR) Research Institute for Informatics, Bd. Miciurin 8-10, Sector 1, Bucharest 71316, ROMANIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific --------- 193.226.2 RO-EARN-C-226-2 (RO) 193.226.3 RO-EARN-C-226-3 (RO) Science Applications International, 6 Fortune Drive, Billerica, MA 01821, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.29.161 PSINET-C-29-161 (US) Simane University, Information Processing Center, 1060, Nishikawatu-cho, Matsue-shi, Shimane-Ken 690, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 192.244.209 SUNCS-NET2 (JP) 192.244.210 SUNCS-NET3 (JP) 192.244.211 SUNCS-NET4 (JP) 192.244.212 SUNCS-NET5 (JP) 192.244.213 SUNCS-NET6 (JP) 192.244.214 SUNCS-NET7 (JP) 192.244.215 SUNCS-NET8 (JP) 192.244.216 SUNCS-NET9 (JP) 192.244.217 SUNCS-NET10 (JP) 192.244.218 SUNCS-NET11 (JP) 192.244.219 SUNCS-NET12 (JP) 192.244.220 SUNCS-NET13 (JP) 192.244.221 SUNCS-NET14 (JP) 192.244.222 SUNCS-NET15 (JP) 192.244.223 SUNCS-NET16 (JP) Spectrum Online Systems Inc, 2860 South Circle Drive, Colorado Springs, CO 80906, USA 1:1332 ANS Denver - DNSS 99 ------ 166.93 ROCKYMTN (US) State of Illinois, 120 W. Jefferson St., Springfield, IL 62702, USA 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT ------- 163.191 ILLINOIS (US) State of Louisiana, Louisiana Health Care Authority, P. O. Box 3947, Baton Rouge, LA 70804, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ----------- 198.232.205 LHCA2 (US) StrataCom Inc., CA, USA 1:2551 NETCOM ----------- 198.211.215 STRATA215 (US) 198.211.216 STRATA216 (US) Synesis Development Inc., 5226 Greens Dairy Road, Raleigh, NC 27604, USA 1:81 CONCERT --------- 198.85.80 SYNESIS1 (US) Systems Control Technologies, 2300 Geng Rd., Palo Alto, CA 94303, USA 1:2551 NETCOM ---------- 192.68.147 SCT-NET (US) TIES, 1935 West County Road B2, Roseville, MN 55113, USA 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ----------- 198.174.221 TIESNET19-C-174-221 (US) Telos Engineering Inc, 130-13120 Vanier Place, Richmond, BC, V6V 2J2, CANADA 1:602 CA*net in Montreal 2:601 CA*net in Toronto 3:603 CA*net in Quebec ---------- 198.162.11 TELOSENG (CA) Test Systems Strategies, Inc., 8205 SW Creekside Place, Beaverton, OR 97005, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 192.231.73 TESSI-1 (US) 192.231.74 TESSI-2 (US) Texas Department of Commerce, P.O. Box 12728, Austin, TX 78711, USA 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network --------- 198.22.29 TXCOMMERCEAJ (US) Thermatool Corp, 31 Commerce Street, East Haven, CT 06512, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------- 199.4.1 TTOOL-C-4-1 (US) USDA OIRM, 3825 East Mulberry St, Ft. Collins, CO 80524, USA 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network ----------- 198.186.218 USDANET9 (US) Universitaet Bayreuth, Hochschulrechenzentrum, Universitaetsstrasse 30, Bayreuth, D-95440, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ---------- 192.109.13 UNIBT-LAN-A (DE) 192.109.19 UNIBT-LAN-B (DE) 192.109.202 UNIBT-LAN-C (DE) University of Maryland, Computer Science Center, College Park, MD 20742-2411, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ---------- 192.54.101 UMD-UNCON (US) Varian-Dosetek Oy, Tiet{j{ntie 14, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ---------- 193.64.173 VARIAN1 (FI) Vienna University, Computer Center, Universitaetsstrasse 7, A-1010 Vienna, AUSTRIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ----------- 193.170.140 VIE-EBS1 (AT) 193.170.141 VIE-EBS2 (AT) Westnet, 3645 Marine Street, Boulder, CO 80309-0455, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 --------- 198.59.68 WESTNET-C-59-68 (US) Westnet, 3645 Marine Street, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ---------- 198.60.217 WESTNET-C-60-217 (US) 198.60.29 WESTNET-C-60-29 (US) Wimsey Information Inc., 225B Evergreen Drive, Port Moody, BC, V3H 1S1, CANADA 1:602 CA*net in Montreal 2:601 CA*net in Toronto 3:603 CA*net in Quebec ---------- 198.162.16 CYBERNET-C-162-16 (CA) 198.162.17 CYBERNET-C-162-17 (CA) 198.162.18 CYBERNET-C-162-18 (CA) 198.162.19 CYBERNET-C-162-19 (CA) XYLAN Corporation, 9310 Topanga Canyon Blvd, Chatsworth, CA 91311, USA 1:1740 CERFnet ----------- 198.206.181 XYLAN-C-206-181 (US) 9 Eylul University, Fen Edebiyat Faculty, Izmir, 35000, TURKEY 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 193.140.21 9EYLUL-NET-C-140-21 (TR) 193.140.22 9EYLUL-NET-C-140-22 (TR) 193.140.23 9EYLUL-NET-C-140-23 (TR) 193.140.24 9EYLUL-NET-C-140-24 (TR) ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- UPCOMING REPORT CHANGES: (Updated 12/9/93) CIDRIZATION: On January 4, we will convert all Policy Routing DataBase (PRDB) output to CIDR notation. All occurrences of network numbers ("x.x.x") on output will be replaced by aggregate notation ("x.x.x/len"). If you are currently using ans_core.now, country.now, or net-comp.now, you can find the new versions of these reports now in the files ans_core.cidr, country.cidr, and net-comp.cidr in the nic.merit.edu:nsfnet/announced.networks directory. On January 4 these new formats will replace the existing "*.now" files, and the current format files will be moved to "*.old" files for one month. The report you are reading now ("nwg" report) and all "whois -h prdb.merit.edu" output will be converted to use aggregate notation on January 4 as well. "nets.unl.now" and "nets.tag.now" will not change, because they all ready include prefix length information. NWG: MORE DETAIL ON DELETED NETWORKS. The report you are reading now ("nwg" report) will also be modified some time in the future to explicitly list which networks have been *deleted* from the PRDB, as well as those that have been added. The syntax has not yet been determined, but we'd like to make sure that it is easy to visually distinguish added networks from deleted ones. NWG: SORTING LONG FORMAT BY COUNTRY: There has been a suggestion to sort the long form of the network listing in this report by country, instead of simply alphabetically by organization to make it easier to scan for networks in your own area. We will do this if there are no objections. Comments? The archived discussion list "db-disc(a)merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request(a)merit.edu" to subscribe. --Dale Johnson (dsj(a)merit.edu) -------------------------------------------------------------------------- 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 nic.merit.edu 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.net.README, template.gate, and template.as. In order to more efficiently process your requests, we have moved to a system which requires the use of template.net (NACR) version 7.0 ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Enke Chen Merit/NSFNET enke(a)merit.edu --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

CERT Advisory - Solaris System Startup Vulnerability
by CERT Advisory 16 Dec '93

16 Dec '93

============================================================================= CA-93:19 CERT Advisory December 16, 1993 Solaris System Startup Vulnerability ----------------------------------------------------------------------------- The CERT Coordination Center has received information concerning a vulnerability in the system startup scripts on Solaris 2.x and Solaris x86 systems. The changes described below will be integrated into the upcoming Solaris release. ----------------------------------------------------------------------------- I. Description If fsck(8) fails during system boot, a privileged shell is run on the system console. This behavior can represent a security vulnerability if users, who would normally not have root access, have physical access to the console at boot time. An attacker can force the failure to occur. II. Impact This vulnerability allows anyone with physical access to the system console to gain root access. III. Solution A simple change to each of two system scripts can be used to close this potential security hole. The new behavior will cause the system to run the privileged shell only if the user at the console enters the correct root password. If you wish to make the change on your own systems, edit both /sbin/rcS and /sbin/mountall, changing every occurrence of: /sbin/sh < /dev/console to: /sbin/sulogin < /dev/console As distributed by Sun, /sbin/rcS contains one occurrence of this string, at line 152; and /sbin/mountall contains two, one at line 66 and one at line 250. Once these changes are made, sulogin will request the root password in the event fsck(8) fails, before starting a privileged shell. The success or failure of sulogin will be logged in /var/adm/sulog. --------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Sun Microsystems, Inc. for their support in responding to this problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact the CERT Coordination Center or your representative in Forum of Incident Response and Security Teams (FIRST). Internet E-mail: cert(a)cert.org Telephone: 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are 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 info.cert.org.

1 0

CERT Advisory - SunOS/Solbourne loadmodule and modload Vulnerability
by CERT Advisory 15 Dec '93

15 Dec '93

============================================================================= CA-93:18 CERT Advisory December 15, 1993 SunOS/Solbourne loadmodule and modload Vulnerability ----------------------------------------------------------------------------- The CERT Coordination Center has received information concerning a vulnerability in /usr/etc/modload and $OPENWINHOME/bin/loadmodule in Sun Microsystems, Inc. SunOS 4.1.1, 4.1.2, 4.1.3, and 4.1.3c and OpenWindows 3.0 on all sun4 and Solbourne Computer, Inc. architectures. The problem does not exist in Solaris 2.x, Solaris x86, and sun3 architectures (OpenWindows 3.0 was not released for the sun3 architecture). Sun has produced a patch for these vulnerabilities for sun4 architectures. It is available through your local Sun Answer Center as well as through anonymous FTP from the ftp.uu.net system in the /systems/sun/sun-dist directory or from the ftp.eu.net system in the /sun/fixes directory. Solbourne has announced a workaround that is included below. Please note that this advisory supersedes CERT Advisory CA-91:22 "SunOS OpenWindows Vulnerability". ----------------------------------------------------------------------------- I. Description loadmodule(8) and modload(8) can be exploited to execute a user's program using the effective UID of root. II. Impact This vulnerability allows a local user to gain root access. III. Solution A. SunOS Solution Obtain and install the appropriate patches according to the instructions included with the patches. Module Patch ID Filename ---------- --------- --------------- loadmodule 100448-02 100448-02.tar.Z BSD Checksum = 19410 5 MD5 Checksum = 0215910cf65e055ed3042070bd961a22 modload 101200-02 101200-02.tar.Z BSD Checksum = 41677 28 MD5 Checksum = 626ab2917204eb6e6eb5f165cca3e908 B. Solbourne Solution Solbourne systems do not support the "loadmodule" functionality. This vulnerability can be fixed on Solbourne systems by removing the setuid bit: chmod 0755 /usr/openwin/bin/loadmodule The modload program does not need to replaced or changed. --------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Sun Microsystems, Inc. and Solbourne Computers, Inc. for their support in responding to this problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact the CERT Coordination Center or your representative in Forum of Incident Response and Security Teams (FIRST). Internet E-mail: cert(a)cert.org Telephone: 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are 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 info.cert.org.

1 0

Network analysis.
by hwb＠upeksa.sdsc.edu 15 Dec '93

15 Dec '93

Over the last few years we have spent a considerable amount of effort at SDSC/UCSD to analyze traffic characteristics of wide area networks. While we were able to just scratch the surface with what is doable and useful, particularly for network planning, engineering, and research, we are getting to a point where it would be useful for us to learn what kind of statistics people currently collect, what they are doing with those statistics, and what kind of statistical objects and analysis they think would make their network work better (make it more manageable, planable, or whatever). So, we are interested in finding out for various operational infrastructures in the U.S. as well as the international Internet community, the following questions: (1) what kind of statistics do you collect? (2) how long of a history do you keep? (3) what is the volume of statistics being generated per day/week/month? (4) what are you doing with them in terms of post processing? Just for operational purposes? In depth analysis? Research, e.g., for published papers? (5) what kind of additional statistics and analysis would you find useful for your network? (6) anything else worth mentioning? We would like to compile a list from the submitted responses, for everyone's benefit. Specifically now with the beginning of much more formalization of network engineering and operational groups that have a strong emphasis on real infrastructure, it may be interesting to find out what the statistics and network analysis requirements are for operational environments, and whether some more of our work could be of value to the Internet community. For example, now that the basic fabric is workable, can we pull things together better in some way or another, e.g., by having a better, and perhaps day-to-day operational, understanding of international flows. If you want more details about what we are doing with network analysis and so, drop me a not and I will send you more information. Hans-Werner

1 0

Phase 5 Step 6 Schedule
by Ittai Hershman 14 Dec '93

14 Dec '93

In the final step of the Phase 5 deployment, we will be upgrading both the Washington DC CNSS and connected sites and the Hartford CNSS and its connected sites. Since a number of providers (PSI, Alternet, and NEARnet) have dual attachment connectivity via these two CNSSs, we have staggered the upgrades to minimize loss of NSFNET Backbone Service connectivity. The following is our detailed schedule for Phase 5 Step 6: 11:00pm 12/17 CE on site at Hartford/Washington POPs 12:00am 12/18 C51, C59 Upgrade 01:00am 12/18 CE on site C40(revisit) E133 E134 01:30am 12/18 C48, C40, E133, E134 Upgrade 03:00am 12/18 CE on site E146 03:30am 12/18 C49, C57, E146 Upgrade 05:00am 12/18 CE on site C32(revisit) 05:30am 12/18 C56, C32 Upgrade 07:00am 12/18 CE on site C72(revisit) E145 E136 07:30am 12/18 C58, C72, E145, E136 Upgrade Please note that the Step 6 window is scheduled from Midnight to 11:30am on Saturday, December 18th. -Ittai

1 0

Re: A Report of the Resource Allocation Committee
by cook＠path.net 14 Dec '93

14 Dec '93

Interesting RAC report. This focuses on the magic formula implied during the fall of 1990 when the MERIT partners and Steve "gave" ANS to the world. ANS would somehow leverage the backing of IBM and MCI into the creation "infrastructure" that would pay wonderful dividends to the research and education community. From January 1991 to the present - a three year period, NSF has poured approximately 30 million into the running of ANS via its payments to MERIT. >From what I hear the money in the infrastructure pool after *3* years is probably LESS than $200,000. Hardly a significant pay back on 30 million of federal funds. HERE is the ONE demonstrable way in which ANS actually returns something to the network. Yet it does so behind closed doors and keeps its one charitable activity on the profit making side of the company where it is not required to submitt to public scrutiny. Why? Makes no sense. What is ANS hiding by doing this? What would ANS have to loose by 1. explaining exactly how funds are placed in the pool and 2. announcing the value of the pool every quarter? I asked Joel Maloff to explain this to me in October. He did so but the time was limited and I do not feel I have a thorough understanding. But why explain it just to me? Why not accept questions and put out the details in a press release. I asked Joel whether every time ANS connected a customer that customer paid 2,000 or 4,000 surcharge to the "inf. pool"? Answer: no. If the customer was connected to a core nodal router, nothing was paid to the pool. If to an end nodal router, I believe something went into the pool. Only problem is I am not aware that ANS has any attachments connected to ENSS nodes. The other instance apparently was when a commercial customer of a regional wanted blessing to send its packets across the ANS backbone. It got this blessing via an annual (?) contribution to the pool which has nothing to do with the existence or absence of CO+RE profits despite the fact that the pool is run by CO+RE. When a commercial customer makes a contribution to the pool why shouldn't it be announced to the community? How would ANS be harmed by full disclosure? And if ANS won't disclose, why won't NSF fulfill its oversight duties by monitoring and disclosure?? I mean the NAME of the NSF represenative on the pool apparently is classified? All other members of RAC were listed by name. Why not NSF?

2 1

Re: A Report of the Resource Allocation Committee
by Brock N. Meeks 14 Dec '93

14 Dec '93

Nice work on the RAC. Now, Peter, how about telling us how much money is in the infrastructure pool as of this date? Thanks, Brock Meeks reporter Communications Daily

1 0

A Report of the Resource Allocation Committee
by Peter O'Neil 14 Dec '93

14 Dec '93

A REPORT OF THE RESOURCE ALLOCATION COMMITTEE December 14, 1993 During November, the Resource Allocation Committee ("RAC") met in Chicago to act on a number of proposals it received from the research and education ("R&E") community seeking funds from those accumulated in the Infrastructure Pool. The following summary of the RAC actions is being released to the general Internet Community. RECENT DECISIONS To facilitate decision-making with regard to the distribution of Pool funds, the RAC found it necessary to define the term "infrastructure". The members adopted the definition of infrastructure as including: physical components, software and tools, programmatic elements, and human resource components which support the R&E mission of the NSFNET program. The RAC believes this definition of infrastructure is consistent with the High Performance Computing & Communications legislation, the pending National Information Infrastructure bills, and the Clinton Administration's vision as defined in "The National Information Infrastructure: Agenda for Action" released in September 1993. After reviewing and discussing several proposals, the RAC approved two proposals to receive Pool funds: The first is entitled "Inter-Regional Problem Tracking and Reporting", submitted by William Yundt, Director Networking & Communication Systems at Stanford University and Executive Director of BARRNet, the Bay Area Regional Research Network. The proposal will provide for a common trouble ticketing system for use by all RAC members. Such a commonly used tool is expected to offer a fundamental improvement for the Internet/ NSFNET by increasing the service consistency and coherence of the overall R&E networking enterprise. It also seeks to improve the responsiveness of widely distributed and differing network operations in reporting and resolving problems and making problem state information consistent and available throughout the network. A second, entitled "Bits and Mortar: Building the Information Infrastructure for Health Care", submitted by Laura Breeden, Executive Director of FARNET, the Federation of American Research Networks and Eric Hood, President of FARNET and Executive Director and CEO of NorthWestNet. The proposal will bring national leaders from the medical research, academic, and clinical health care community together with Internet service providers, government agency representatives, developers of software and services, and medical instrument vendors. The representatives attending the workshop will be those who must cooperate to create a telecommunications infrastructure for medical and life science researchers and clincial health care providers. There is also an expectation that our nation's citizens will use networks to better educate themselves about their health. The workshop discussions will focus on practical, near-term uses for Internet-based technology in the conduct of health and life sciences research and in the delivery of health care and patient information. Such a workshop is expected to play a catalytic role for Internet service providers by affording them the opportunity to learn about the network infrastructure, capacity requirements, and service demands that will be placed on their networks to support bursty image traffic, transport of sensitive or proprietary data, and other life science applications and services. BACKGROUND Representatives of a majority of Regional Networks and ANS CO+RE Systems, Inc. ("ANS CO+RE"), agreed that they would contribute to an Infrastructure Pool a portion of the fees that they collected from entities (a) to whom they provide network attachments, and (b) that did not agree to comply with a Research and Education Acceptable Use Policy (e.g., the AUP of ANS or NSF). It was agreed that the funds in the Infrastructure Pool would be used to improve the infrastructure of ANS and the Regional Networks under the direction of a committee (the Resource Allocation Committee). The basic objective of the Infrastructure Pool and the RAC was "to ensure that ANS, ANS CO+RE, and the participating networks receive sufficient funds to cover the costs of handling traffic exchanges with commercial subscribers." In these Agreements, the RAC is given broad authority to set the criteria and processes for distribution of the fund. The National Science Foundation ("NSF") was kept apprised of the various discussions and agreements by which the Infrastructure Pool and the RAC were conceived and implemented. The NSF is a non-voting member of the RAC. The current members of the RAC are: Eric Aupperle, Merit, Inc. James Luckett, NYSERNet Guy Almes, ANS Maurice Mitchell, NevadaNet Thomas Bajzek, PREPnet Jeffrey Ogden, MichNet Alison Brown, OARnet Glenn Ricart, SURAnet Patrick Burns, WestNet John Rugo, NEARnet Dennis Fazio, MRNet Thomas Sandoski, Concert Douglas Gale, MIDnet Michael Staman, CICnet Farrell Gerbode, Sesquinet William Yundt, BARRNet Eric Hood, NorthWestNet NSF Representative Further questions and comments can be referred to: Peter O'Neil Chair, Resource Allocation Committee 914.789.5329 oneil(a)ans.net

1 0