- ripe-list - mailman.ripe.net

RIPE23: getting visa
by RIPE NCC Staff 19 Dec '95

19 Dec '95

Dear RIPE meeting attendees, This letter is intended for all of you who need a visa to come to Italy for the 23rd RIPE meeting. Since getting visas takes generally more time then one expects I would suggest you apply for a visa as fast as possible. On request, we can send you an invitation. If you want us to send an invitation, please tell us how many days and which days you are planning to stay. If, after the RIPE meeting, you want to stay some additional days we can invite you for some 'technical meetings' after the RIPE meeting (wink wink ;-). Furthermore, please give also your full name, birth date and passport number. If we mention these data in our invitation to you, it could facilitate getting visa. If you have any further questions, don't hesitate to contact us, preferrably at <ncc(a)ripe.net>. Kind regards, Roderik Muit RIPE NCC

1 0

RIPE23: registration form
by RIPE NCC Staff 19 Dec '95

19 Dec '95

23rd RIPE meeting Registration reservation form Amsterdam, The Netherlands January 29th-31st, 1996 %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL meeting registrations is fully automated. To register for the meeting, please complete the registration form and send it to <meeting(a)ripe.net>. PLEASE FILL THIS OUT AS SPECIFIED. Please add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). Note this is what will be used for your badge if you have requested one and for the attendee list so please take care to fill it in correctly. You will receive a notification message that your request has been processed. If however, you have any questions about the meeting or your registration form, please send your completed form to <ncc(a)ripe.net>. ============================================================================== %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL (remember this is on list and badge) e.g. John Doe Mary-Beth Walton # NAME [ ] 2) I already have a RIPE badge from a previous meeting and will take it with me to the meeting. If yes please enter Y in the box below. If no please enter N in the box below. # BADGE [ ] 3) Your Organisation/Institution # ORG [ ] 4) Your e-mail address # EMAIL [ ] 5) Country code of organisation e.g. IT FR EU # CTRY [ ] %END

1 0

RIPE23: announcement
by RIPE NCC Staff 19 Dec '95

19 Dec '95

R I P E meeting announcement ============================ (This announcement can also be viewed using "finger meeting(a)ncc.ripe.net") This is to announce that the 23rd RIPE meeting will take place: Dates: 29th January, 1996 start: 10:00 (*) 30th January, 1996 31st January, 1996 end: 15:30 (*) * times subject to change (may vary +/- 1 hour). For exact times, look at ftp://ftp.ripe.net/ripe/Next-Meeting/announcement shortly before the meeting Venue: CWI Kruislaan 413 1098 SJ Amsterdam The Netherlands Host: NIKHEF Registration: Please use the registration form (which will follow in a separate mail) to give notice of your coming as soon as possible. General meeting overview: ------------------------- - Before the working group meetings, on Wednesday 29th, there will be an EOF (European Operators Forum) meeting. The exact starting time will probably be known shortly before the RIPE meeting. It will end 12:30. - Wednesday 29th, 14:00-18:00 and Thursday 30th, 09:00-12:30, there will be various RIPE working groups sessions. The schedule of the previous meeting follows below for reference; the schedule of this meeting is not known yet. - Thursday 30th, 14:00-18:00 and Friday 31st, 09:00-15:30 (*), the plenary session will take place, with reports from the RIPE NCC, reports from the working group meetings and other presentations. General information: -------------------- Currency (checked 18 December 1995): 1 UK pound = Hfl 2.5 1 ECU = Hfl 2.1 1 US$ = Hfl 1.6 More information about Amsterdam: --------------------------------- Websurfers may take a look at: <> http://www.xxlink.nl/cities/amsterdam <> http://pmwww.cs.vu.nl/amsterdam/index.html Appended to this announcement: ------------------------------ <> directions to the meeting place Documents to follow (separate mail messages): --------------------------------------------- <> details of hotels in Amsterdam close to meeting venue <> registration form for attendance at the meeting <> getting visa for the meeting, if you need one ================================================================== CWI: How do I get there? ------------------------- To ease any possible confusion, two postscript maps can be found in the RIPE document store. One shows the bus and tram stops around the meeting site and the other is a more general map of the area. Both maps are available by ftp: ftp.ripe.net:ripe/Next-Meeting/area-map.ps ftp.ripe.net:ripe/Next-Meeting/area-map.ps.Z ftp.ripe.net:ripe/Next-Meeting/local-transport-map.ps ftp.ripe.net:ripe/Next-Meeting/local-transport-map.ps.Z *PLEASE NOTE: The number 69 and 169 now end at Amstel station rather than Muiderpoort station. The number 15 now connects the Amstel station with Muiderpoort station. >From Amsterdam airport (Schiphol): o Take the train from the airport railway station to the Central Railway station. >From the Central Railway station: o Change to the stop train to Utrecht, to Amersfoort, or to Lelystad. Next station is the 'Muiderpoort' railway station. or o Take tramway number 9 till the stop at the corner of Middenweg and Kruislaan (15 min ride) o Walk down the Kruislaan in the direction of the railway bridge. Cross under the bridge and continue. Take the 2nd entrance left and proceed to the entrance marked NIKHEF-H. (15 min walk all together). or o Take bus 22 in the direction 'Indische Buurt' to the stop at the 'Muiderpoort Station' and take bus 66. >From the RAI Railway station: o From the RAI station take the city bus number 69 or CN bus number 169 in the direction `Amstel Station'. >From the Amstel Railway station: o From the Amstel station take the city bus number 15 the direction `Muiderpoort Station' to the stop on the corner of Kruislaan and Linnaeusparkweg (15 min ride, ask the driver where to get of) or proceed to 'Muiderpoort Station' and take bus 66. o Walk down the Kruislaan in the direction of the railway bridge as described above. >From the Muiderpoort Railway station: o Take bus 66 (5-10 minutes ride). At the exit of the railway station turn to the left, pass through the tunnel, cross the tram rails and the street running parallel to the railway. The stop for bus 66 is at your left hand (right side of the broad street). The bus passes twice broad railway bridges. Get off at the second stop after the second passage, pass through the gate at the left, follow the road passing under the building, then turn to the left, where you will find the main entrance of NIKHEF-H. Taxi from the airport: o 15 min ride o fl. 50 appr. Other connections to and from the NIKHEF site: tram 6 from Leidseplein tram 10 to Leidseplein tram 14 to and from Dam Square bus 66 to and from Muiderpoortstation Timetable bus 66 >From Muiderpoortstation (Monday - Friday): 7.00 7.15 7.30 7.45 8.00 8.15 8.30 8.45 9.00 9.15 9.30 10.00 10.30 11.00 11.30 12.00 12.30 13.00 13.30 14.00 14.30 15.00 15.30 15.45 16.00 16.15 16.30 16.45 17.00 17.15 17.30 17.45 18.00 >From NIKHEF to Muiderpoortstation (Monday - Friday): 7.08 7.23 7.38 7.53 8.08 8.23 8.38 8.53 9.08 9.23 9.38 10.08 10.38 11.08 11.38 12.08 12.38 13.08 13.38 14.08 14.38 23.08 23.38 23.53 16.08 16.23 16.38 16.53 17.08 17.23 17.38 17.53 18.08 Bus 66 is operated in conjunction with bus 61. Therefore the bus does not always show the correct linenumber. In case of doubt ask the driver or your fellow-passengers.

1 0

URGENT CERT message -- CERT#7023
by CERT Coordination Center 18 Dec '95

18 Dec '95

============================================================================= Alert to Network Service Providers - Widespread attacks on Internet sites CERT Coordination Center December 18, 1995 ============================================================================= Over the last several weeks, the CERT Coordination Center has been working on related incidents where the intruders have launched widespread attacks against Internet sites. Due to the scope of this incident, we ask that you alert your customers/constituency as soon as possible, and urge them to take action to ensure that systems are protected against these attacks. Please feel free to redistribute this message. Hundreds of sites have been attacked, and many of the attacks have been successful, resulting in root compromises at the targeted sites. We are working directly with the root-compromised sites. We continue to receive reports, and we believe that more attacks are going undetected. ************************************************************************** NOTE -- all of the vulnerabilities exploited in this attack are known, and are addressed by CERT advisories. ************************************************************************** The MO of the attacks and advisories that address these vulnerabilities are listed below. We cannot emphasize enough the importance of taking the actions suggested in these advisories and README files. - using automated tools to scan sites for NFS and NIS vulnerabilities * CA-94:15.NFS.Vulnerabilities and CA-94:15.README * CA-92:13.SunOS.NIS.vulnerability - exploiting the rpc.ypupdated vulnerability to gain root access * CA-95:17.rpc.ypupdated.vul and CA-95:17.README - exploiting the loadmodule vulnerability to gain root access * CA-93:18.SunOS.Solbourne.loadmodule.modload.vulnerability, CA-95:12.sun.loadmodule.vul and CA-95:12.README - installing Trojan horse programs and packet sniffers * CA-94:01.ongoing.network.monitoring.attacks and CA-94:01.README - launching IP spoofing attacks * CA-95:01.IP.spoofing and CA-95:01.README The CERT advisories and README files are available from: ftp://info.cert.org:/pub/cert_advisories Please feel free to forward this alert to other providers of Internet services, in addition to notifying your customers/constituents of this attack. We will also be launching CERT advisory CA-95:18.widespread.attacks this morning. I have appended a copy of this advisory below. Communicating with us - ---------------------- Warning: For sensitive information, use encrypted email. You will find the CERT public PGP key at the end of this document. If you would prefer to use DES, please call the CERT hotline: +1 412 268 7090 to exchange a DES key over the phone. If you or one of your customers find a compromise, please complete and return the Incident Reporting Form (IRF) appended below. This completed form will help us better assist you. Because of our workload, we must ask you not to send log files of activity, but we would be happy to work with you as needed on how to interpret data that you may collect. If you see activity that indicates an attack is in progress, we encourage you to contact your customer, or other sites involved or their service provider. We will also be happy to provide guidance and advice, if needed, on how to handle incidents and work with law enforcement. CERT Public Key - ---------------------- - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6 mQCNAi2a4WoAAAEEAN0IPkqCmoGRud0Kts3g4ZGgZ4zyqY8C5VTOgUcqU+D2U1so 21K6dxj/lewKFduXtNpqDeg6C0wR6GIMJ2jWLU4GUEq0xHohioWGGg5O3QTvCpN3 rnLIKO9urv4Wjgkp1n1ys7xcOYl5jb7kuhdlXs3kNgKi4zBB5XVP+x0t4w7BAAUR tChDRVJUIENvb3JkaW5hdGlvbiBDZW50ZXIgPGNlcnRAY2VydC5vcmc+iQCVAgUQ LZrkOXVP+x0t4w7BAQEI3QP/d9gl7GD52Pd8KbsBMb0hiploigL8kZW1Q1fVsIm1 cO9xumU89CLf2jrN+IdrIMpVWAO3DyJjZooZTaJBg/9jjv3HltHTq/XFD5c+WYlM G+fQZVuR8qu8+D8P8pPbNVm94wxj9fyKO39/dnub1UfjDedJBtt+zgMJmstADkOv QBM= =N6E5 - -----END PGP PUBLIC KEY BLOCK----- Incident Reporting Form - ---------------------- Please complete this form if you are reporting a compromise. CERT(sm) Coordination Center Incident Reporting Form CERT has developed the following form in an effort to facilitate our interaction with members of the Internet community. We would appreciate your completing the form included below in as much detail as possible. The information is optional, but the more information you can provide, the better we will be able to assist you. Note that our policy is to keep confidential any information you provide unless we receive your permission to release that information. (See questions 8 and 11 below.) Please feel free to duplicate any section as required. Please return this form to cert(a)cert.org. If you are unable to e-mail this form, please send it via FAX. Our FAX telephone number is +1 412-268-6989. Thank you for your cooperation and help. 1) Incident number (after assigned by CERT): 2) Reporting site information Organizational Name (e.g. CERT Coordination Center): Domain Name (e.g. cert.org) 3) Your contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (for CERT internal use only): 4) Additional contact information (if available) Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (for CERT internal use only): 5) Compromised host(s) at your site (one entry per host please) Hostname: IP address: Vendor: Hardware: OS: Version: Security patches applied: 6) Please list the other sites compromised that you have notified, and the contact information for each site (one entry per site please) Hostname: IP address: Contact information: Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, for CERT internal use only): 7) Please list the other sites compromised that you have not yet notified (one entry per site please) Hostname: IP address: Contact information (if available): Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): 8) Would you be willing to contact these sites if CERT provided you the relevant contact information (Yes/No): Or, can CERT give your contact information to these sites when we contact them (Yes/No): 9) Incident category (Yes/No) Probe: Prank: Mail Spoofing: Break-in: Installed Trojan Horse: Intruder gained root access: NIS (yellow pages) attack: NFS attack: TFTP attack: FTP attack: Telnet attack: Rlogin or rsh attack: Product vulnerability: Worm: Virus: Other (please specify): 10) Are you currently using (Yes/No/Periodically) COPS (The Computer Oracle and Password System): TCP access control using packet filtering: Host access control via modified daemons or wrappers: Crack: Tripwire: Proactive password checkers (e.g. npasswd, passwd+): Shadow passwords: Other (please specify): 11) Miscellaneous Please specify any other incident response team(s) you have contacted Team: Contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): If you have not contacted another incident response team, could we give them your contact information (Yes/No): Please specify any law enforcement agency(ies) you have contacted Agency: Contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): If you have not contacted any law enforcement agency, could we give them your contact information, if necessary (Yes/No): 12) Detailed description of incident (e.g. method of intrusion, etc) 13) What assistance would you like from CERT? Copyright 1995 Carnegie Mellon University This form may be reproduced and distributed without permission provided it is used for noncommercial purposes and the CERT Coordination Center is acknowledged. CERT is a service mark of Carnegie Mellon University. ============================================================================= CA-95:18 CERT Advisory December 18, 1995 Widespread Attacks on Internet Sites ----------------------------------------------------------------------------- Over the last several weeks, the CERT Coordination Center has been working on a set of incidents in which the intruders have launched widespread attacks against Internet sites. Hundreds of sites have been attacked, and many of the attacks have been successful, resulting in root compromises at the targeted sites. We continue to receive reports, and we believe that more attacks are going undetected. ********************************************************************** All the vulnerabilities exploited in these attacks are known, and are addressed by CERT advisories (see Section III). ********************************************************************** We urge everyone to obtain these advisories and take action to ensure that systems are protected against these attacks. Also, please feel free to redistribute this message. As we receive additional information relating to this advisory, we will place it in ftp://info.cert.org/pub/cert_advisories/CA-95:18.README We encourage you to check our README files regularly for updates on advisories that relate to your site. ----------------------------------------------------------------------------- I. Description Intruders are doing the following: - using automated tools to scan sites for NFS and NIS vulnerabilities - exploiting the rpc.ypupdated vulnerability to gain root access - exploiting the loadmodule vulnerability to gain root access - installing Trojan horse programs and packet sniffers - launching IP spoofing attacks II. Impact Successful exploitation of the vulnerabilities can result in unauthorized root access. III. Solution The CERT staff urges you to immediately take the steps described in the advisories and README files listed below. Note that it is important to check README files as they contain updated information we received after the advisory was published. a. Using automated tools to scan sites for NFS and NIS vulnerabilities * CA-94:15.NFS.Vulnerabilities * CA-94:15.README * CA-92:13.SunOS.NIS.vulnerability b. Exploiting the rpc.ypupdated vulnerability to gain root access * CA-95:17.rpc.ypupdated.vul * CA-95:17.README c. Exploiting the loadmodule vulnerability to gain root access * CA-93:18.SunOS.Solbourne.loadmodule.modload.vulnerability * CA-95:12.sun.loadmodule.vul * CA-95:12.README d. Installing Trojan horse programs and packet sniffers * CA-94:01.ongoing.network.monitoring.attacks * CA-94:01.README e. Launching IP spoofing attacks * CA-95:01.IP.spoofing * CA-95:01.README The CERT advisories and README files are available from ftp://info.cert.org/pub/cert_advisories If you find a compromise, please complete the Incident Reporting Form that we have provided in the appendix of this advisory, and return the form to cert(a)cert.org. This completed form will help us better assist you. Note: Because of our workload, we must ask you not to send log files of activity, but we would be happy to work with you as needed on how to interpret data that you may collect. Also, the CERT staff can provide guidance and advice, if needed, on how to handle incidents and work with law enforcement. If you see activity that indicates an attack is in progress, we encourage you to contact other sites involved and the service providers, as well as the CERT Coordination Center. --------------------------------------------------------------------------- Contacting the CERT Coordination Center For sensitive information, please use encrypted email. The CERT public PGP key is available from ftp://info.cert.org/pub/CERT_PGP.key If you prefer to use DES, please call the CERT hotline +1 412 268 7090 to exchange a DES key over the phone. Other CERT contact information: Internet email: cert(a)cert.org Telephone: +1 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. Fax: +1 412-268-6989 Postal address: CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 USA CERT advisories and bulletins are posted on the USENET newsgroup comp.security.announce. If you would like to have future advisories and bulletins mailed to you or to a mail exploder at your site, please send mail to cert-advisory-request(a)cert.org. Past CERT publications, information about FIRST representatives, and other information related to computer security are available from ftp://info.cert.org/pub/ Copyright 1995 Carnegie Mellon University This material may be reproduced and distributed without permission provided it is used for noncommercial purposes and the copyright statement is included. CERT is a service mark of Carnegie Mellon University. .............................................................................. Appendix: Incident Reporting Form (also available from ftp://info.cert.org/pub/incident.reporting.form) CERT(sm) Coordination Center Incident Reporting Form CERT has developed the following form in an effort to facilitate our interaction with members of the Internet community. We would appreciate your completing the form included below in as much detail as possible. The information is optional, but the more information you can provide, the better we will be able to assist you. Note that our policy is to keep confidential any information you provide unless we receive your permission to release that information. (See questions 8 and 11 below.) Please feel free to duplicate any section as required. Please return this form to cert(a)cert.org. If you are unable to e-mail this form, please send it via FAX. Our FAX telephone number is +1 412-268-6989. Thank you for your cooperation and help. 1) Incident number (assigned by CERT): CERT# 2) Reporting site information Organizational Name (e.g. CERT Coordination Center): Domain Name (e.g. cert.org) 3) Your contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (for CERT internal use only): 4) Additional contact information (if available) Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (for CERT internal use only): 5) Compromised host(s) at your site (one entry per host please) Hostname: IP address: Vendor: Hardware: OS: Version: Security patches applied: 6) Please list the other sites compromised that you have notified, and the contact information for each site (one entry per site please) Hostname: IP address: Contact information: Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, for CERT internal use only): 7) Please list the other sites compromised that you have not yet notified (one entry per site please) Hostname: IP address: Contact information (if available): Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): 8) Would you be willing to contact these sites if CERT provided you the relevant contact information (Yes/No): Or, can CERT give your contact information to these sites when we contact them (Yes/No): 9) Incident category (Yes/No) Probe: Prank: Mail Spoofing: Break-in: Installed Trojan Horse: Intruder gained root access: NIS (yellow pages) attack: NFS attack: TFTP attack: FTP attack: Telnet attack: Rlogin or rsh attack: Product vulnerability: Worm: Virus: Other (please specify): 10) Are you currently using (Yes/No/Periodically) COPS (The Computer Oracle and Password System): TCP access control using packet filtering: Host access control via modified daemons or wrappers: Crack: Tripwire: Proactive password checkers (e.g. npasswd, passwd+): Shadow passwords: Other (please specify): 11) Miscellaneous Please specify any other incident response team(s) you have contacted Team: Contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): If you have not contacted another incident response team, could we give them your contact information (Yes/No): Please specify any law enforcement agency(ies) you have contacted Agency: Contact information Name: E-mail address: Telephone number: FAX number (optional): Pager number (optional): Home telephone number (optional, CERT internal use only): If you have not contacted any law enforcement agency, could we give them your contact information, if necessary (Yes/No): 12) Detailed description of incident (e.g. method of intrusion, etc) 13) What assistance would you like from CERT? Copyright 1995 Carnegie Mellon University This form may be reproduced and distributed without permission provided it is used for noncommercial purposes and the CERT Coordination Center is acknowledged. CERT is a service mark of Carnegie Mellon University.

1 0

Hostcount for November 1995
by Mirjam Kuehne 04 Dec '95

04 Dec '95

Dear all, Here comes the hostcount for November 1995. The table shows an increase since last month of over 71,000 (or 3.7%) to a total of 1,999,997 (!) hosts in the DNS in Europe. We leave the 2 Million boundary as a Christmas present :-) The german zone shows a decrease again of more than 13,000 hosts. The reason is that two zones that usually show a very high host number are not listed this time. This means almost 35,000 hosts are missing. We have one new zone: md (Republic of Moldova) that starts with 10 hosts in 5 zones. The UK shows again the highest increase with over 23,000 hosts more than in October. The hostcount can also be found under ftp://ftp.ripe.net/ripe/hostcount/ The graphical version of the hostcount can be found at ftp://ftp.ripe.net/ripe/hostcount/RIPE-Hostcount-{Mo,Qu}.eps The translation of the country codes can be found at ftp://ftp.ripe.net/iso3166-countrycodes I would like to thank all people who help me to create the hostcount every month by counting hosts locally: at Gerhard Winkler <Gerhard.Winkler(a)univie.ac.at> be Herman Moons <Herman.Moons(a)CS.kuleuven.ac.be> ch Christoph Graf <graf(a)chx400.switch.ch> cy Panagiotis Tzounakis <pj(a)ics.forth.gr> cz Jiri Orsag <Jiri.Orsag(a)eunet.cz> de Peter Koch <pk(a)TechFak.Uni-Bielefeld.DE> dk Robert Martin-Legene <robert(a)dknet.dk> es Jose Sanchez-Seco <jose.sanchez(a)rediris.es> fi Petri Ojala <ojala(a)eunet.fi> fr Benoit Grange <grange(a)sagres.inria.fr> gr Panagiotis Tzounakis <pj(a)ics.forth.gr> hr Ivan Maric <Ivan.Maric(a)stribor.srce.hr> ie Mike Norris <mnorris(a)dalkey.hea.ie> il Sason Levi <sason(a)NetVision.net.il> it Antonio_Blasco Bonito <bonito(a)nis.garr.it> no Havard Eidnes <Havard.Eidnes(a)runit.sintef.no> pt Graca Carvalho <fccn(a)dns.pt> ru Andrey Dobrotsvetov <adbr(a)argo.net.kiae.su> sk Ivan Lescak <Ivan.Lescak(a)Slovakia.EU.net> Lubos Elias <Lubos.Elias(a)uakom.sk> tr Yener Yigit <yener(a)knidos.cc.metu.edu.tr> uk JANET NOSC <hostmaster(a)nic.ja.net> If you have any questions, please don't hesitate to contact me. Kind regards, Mirjam Kuehne RIPE NCC RIPE DNS Hostcount Previous Count : Thu Oct 31 1995 This Count : Thu Nov 30 1995 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 4 1 0 1 0 am 2 45 2 43 - 29 at 1135 55744 1601 54143 + 2679 az 3 15 0 15 0 be 1026 29242 806 28436 + 229 bg 51 918 45 873 + 40 by 7 18 1 17 + 11 ch 1068 80850 1018 79832 + 1107 cy 31 407 12 395 + 32 cz 373 21155 328 20827 + 1844 de 5499 429219 18471 410748 -13526 dk 838 50944 868 50076 + 3396 dz 2 16 0 16 0 ee 150 3704 53 3651 + 2739 eg 10 678 16 662 + 112 es 1116 53077 870 52207 + 5302 fi 1317 148863 3594 145269 + 4571 fo 14 469 0 469 - 2 fr 2199 138837 3656 135181 +15358 gb 1 35 0 35 + 3 ge 10 53 0 53 + 3 gr 353 7390 446 0 - 6944 hr 120 2957 634 2323 + 36 hu 209 15337 274 15063 + 1216 ie 313 13883 145 13738 + 1833 il 547 24639 313 24326 + 508 is 145 8131 73 8058 + 228 it 2237 72338 4525 67813 + 4727 li 17 70 3 67 + 27 lt 31 377 1 376 + 29 lu 86 2008 24 1984 + 328 lv 45 1266 30 1236 + 132 ma 2 199 0 199 - 3 md 5 10 0 10 + 10 mk 12 117 28 89 - 1 mt 8 89 13 76 + 52 nl 1585 168629 2592 166037 + 6846 no 1655 83558 3190 80368 + 2569 pl 743 23493 1624 21869 + 980 pt 332 12181 953 11228 + 998 ro 78 1283 30 1253 - 83 ru 384 9813 868 8945 + 605 se 2461 144484 4656 139828 + 8859 si 168 5161 192 4969 + 575 sk 124 2997 112 2885 - 22 su 402 10516 441 10075 + 285 tn 3 81 4 77 + 2 tr 151 5310 79 5231 + 395 ua 137 2253 424 1829 - 22 uk 8259 464325 37230 427095 +23583 va 1 1 0 1 0 yu 3 0 0 0 0 ============================================================ 35472 2097186 90245 1999997 +71617

1 0

(no subject)
by hidalgo＠unitru.edu.pe 25 Nov '95

25 Nov '95

Help

1 0

Corrected Hostcount for October 1995
by Mirjam Kuehne 08 Nov '95

08 Nov '95

Dear all, In the hostcount I have sent yesterday was a mistake: The IT domain showed the figures for September. Please find below the corrected version. The new figures for IT also changed the totals. We can now see an increase of 5.4%. The new files can be found at the usual place: ftp://ftp.ripe.net/ripe/hostcount/ ftp://ftp.ripe.net/ripe/hostcount/RIPE-Hostcount-{Mo,Qu}.eps Kind Regards, Mirjam Kuehne RIPE NCC RIPE DNS Hostcount Previous Count : Mon Sep 30 1995 This Count : Thu Oct 31 1995 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 4 1 0 1 0 am 5 74 2 72 + 10 at 1031 53197 1733 51464 + 2353 az 3 15 0 15 0 be 918 28998 791 28207 + 1322 bg 56 884 51 833 + 57 by 1 6 0 6 - 2 ch 843 79663 938 78725 + 2092 cy 29 374 11 363 + 88 cz 341 19301 318 18983 - 292 de 5191 437726 13452 424274 +22422 dk 773 47607 927 46680 + 4098 dz 2 16 0 16 0 ee 46 947 35 912 - 2158 eg 9 564 14 550 + 264 es 989 47749 844 46905 + 7368 fi 1218 143918 3220 140698 + 7378 fo 14 471 0 471 0 fr 2068 123212 3389 119823 - 3398 gb 1 32 0 32 + 1 ge 10 50 0 50 + 38 gr 353 7390 446 6944 + 204 hr 112 2859 572 2287 - 2 hu 197 14272 425 13847 + 1306 ie 111 12023 118 11905 + 1600 il 501 24141 323 23818 + 2006 is 138 7904 74 7830 + 2 it 2152 67936 4850 63086 + 5161 li 11 41 1 40 - 7 lt 29 348 1 347 + 19 lu 81 1673 17 1656 - 13 lv 39 1142 38 1104 + 262 ma 2 202 0 202 + 202 mk 12 116 26 90 + 7 mt 3 27 3 24 + 21 nl 1453 161665 2474 159191 + 6063 no 1528 80965 3166 77799 + 3087 pl 720 22453 1564 20889 + 1951 pt 315 11254 1024 10230 + 479 ro 103 1366 30 1336 + 157 ru 393 8994 654 8340 + 1373 se 2171 135384 4415 130969 + 7276 si 156 4566 172 4394 + 499 sk 123 2952 45 2907 + 333 su 403 10245 455 9790 + 903 tn 3 77 2 75 + 6 tr 148 4905 69 4836 - 56 ua 144 2284 433 1851 + 22 uk 7394 438838 35326 403512 +23489 va 1 1 0 1 0 yu 3 0 0 0 0 ============================================================ 32351 2010828 82448 1928380 +97991

1 0

Hostcount for October 1995
by Mirjam Kuehne 08 Nov '95

08 Nov '95

Dear all, Here is the hostcount for October 1995. The table shows an increase since last month of almost 93,000 (or 5.1%) to a total of over 1,900,000 hosts in the DNS in Europe. The UK shows the highest increase with over 23,000 hosts more than in September. The hostcount can also be found under ftp://ftp.ripe.net/ripe/hostcount/ The graphical version of the hostcount can be found at ftp://ftp.ripe.net/ripe/hostcount/RIPE-Hostcount-{Mo,Qu}.eps I would like to thank all people who help me to create the hostcount every month by counting hosts locally: at Wilfried Woeber <Wilfried.Woeber(a)CC.UniVie.ac.at> be Herman Moons <Herman.Moons(a)CS.kuleuven.ac.be> ch Christoph Graf <graf(a)chx400.switch.ch> cy Panagiotis Tzounakis <pj(a)ics.forth.gr> cz Jiri Orsag <Jiri.Orsag(a)eunet.cz> de Peter Koch <pk(a)TechFak.Uni-Bielefeld.DE> dk Robert Martin-Legene <robert(a)dknet.dk> es Jose Sanchez-Seco <jose.sanchez(a)rediris.es> fi Petri Ojala <ojala(a)eunet.fi> fr Benoit Grange <grange(a)sagres.inria.fr> gr Panagiotis Tzounakis <pj(a)ics.forth.gr> hr Ivan Maric <Ivan.Maric(a)stribor.srce.hr> ie Mike Norris <mnorris(a)dalkey.hea.ie> il Sason Levi <sason(a)NetVision.net.il> it Antonio_Blasco Bonito <bonito(a)nis.garr.it> no Havard Eidnes <Havard.Eidnes(a)runit.sintef.no> pt Graca Carvalho <fccn(a)dns.pt> ru Andrey Dobrotsvetov <adbr(a)argo.net.kiae.su> sk Ivan Lescak <Ivan.Lescak(a)Slovakia.EU.net> Lubos Elias <Lubos.Elias(a)uakom.sk> tr Yener Yigit <yener(a)knidos.cc.metu.edu.tr> uk Duncan Rogerson <D.Rogerson(a)nosc.ja.net> If you have any questions, please don't hesitate to contact me. Kind regards, Mirjam Kuehne RIPE NCC RIPE DNS Hostcount Previous Count : Mon Sep 30 1995 This Count : Thu Oct 31 1995 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 4 1 0 1 0 am 5 74 2 72 + 10 at 1031 53197 1733 51464 + 2353 az 3 15 0 15 0 be 918 28998 791 28207 + 1322 bg 56 884 51 833 + 57 by 1 6 0 6 - 2 ch 843 79663 938 78725 + 2092 cy 29 374 11 363 + 88 cz 341 19301 318 18983 - 292 de 5191 437726 13452 424274 +22422 dk 773 47607 927 46680 + 4098 dz 2 16 0 16 0 ee 46 947 35 912 - 2158 eg 9 564 14 550 + 264 es 989 47749 844 46905 + 7368 fi 1218 143918 3220 140698 + 7378 fo 14 471 0 471 0 fr 2068 123212 3389 119823 - 3398 gb 1 32 0 32 + 1 ge 10 50 0 50 + 38 gr 353 7390 446 6944 + 204 hr 112 2859 572 2287 - 2 hu 197 14272 425 13847 + 1306 ie 111 12023 118 11905 + 1600 il 501 24141 323 23818 + 2006 is 138 7904 74 7830 + 2 it 1879 62586 4661 57925 0 li 11 41 1 40 - 7 lt 29 348 1 347 + 19 lu 81 1673 17 1656 - 13 lv 39 1142 38 1104 + 262 ma 2 202 0 202 + 202 mk 12 116 26 90 + 7 mt 3 27 3 24 + 21 nl 1453 161665 2474 159191 + 6063 no 1528 80965 3166 77799 + 3087 pl 720 22453 1564 20889 + 1951 pt 315 11254 1024 10230 + 479 ro 103 1366 30 1336 + 157 ru 393 8994 654 8340 + 1373 se 2171 135384 4415 130969 + 7276 si 156 4566 172 4394 + 499 sk 123 2952 45 2907 + 333 su 403 10245 455 9790 + 903 tn 3 77 2 75 + 6 tr 148 4905 69 4836 - 56 ua 144 2284 433 1851 + 22 uk 7394 438838 35326 403512 +23489 va 1 1 0 1 0 yu 3 0 0 0 0 ============================================================ 32078 2005478 82259 1923219 +92830

2 2

BTnet Ticket BTNET.951106 1653 CLOSED
by Nigel Titley 06 Nov '95

06 Nov '95

Ticket Number: BTNET.951106 1653 Ticket Status: CLOSED Ticket Type: UNSCHEDULED Ticket Source: BT Ticket Scope: Router Site/Line: UK Transit Router Ticket Owner: BTnet NOC Problem Fixer: NOC Ticket Opened: 951106 16:53 GMT Problem Started: 950906 12:00 Closed: 951106 20:45 GMT Ended: 951106 19:34 GMT Problem Description: A serial card in the telehouse-transit.bt.net router is showing signs of failure which are causing transit lines to be dropped for short periods. Affected: All BTnet customers Actions: Card replaced and links moved back. Router seems stable.

1 0

BTnet Ticket BTNET.951106 1653
by Nigel Titley 06 Nov '95

06 Nov '95

Ticket Number: BTNET.951106 1653 Ticket Status: OPEN Ticket Type: UNSCHEDULED Ticket Source: BT Ticket Scope: Router Site/Line: UK Transit Router Ticket Owner: BTnet NOC Problem Fixer: NOC Ticket Opened: 951106 1653 GMT Problem Started: 950906 12:00 Closed: Ended: Problem Description: A serial card in the telehouse-transit.bt.net router is showing signs of failure which are causing transit lines to be dropped for short periods. Affected: All BTnet customers Actions: We are moving the US MCI link, the EBONE link and the DANTE/IBDNS link to an alternative card until the faulty card can be replaced. Time to fix: 15 minutes to move links. 4 hours to fix card.

1 0